diff --git a/api/core/testing/org.meshtastic.core.testing/-robolectric-ble-bonding/index.html b/api/core/testing/org.meshtastic.core.testing/-robolectric-ble-bonding/index.html index 05a39fafc3..465f6f34cd 100644 --- a/api/core/testing/org.meshtastic.core.testing/-robolectric-ble-bonding/index.html +++ b/api/core/testing/org.meshtastic.core.testing/-robolectric-ble-bonding/index.html @@ -95,7 +95,7 @@

RobolectricBleBonding

-
object RobolectricBleBonding(source)

Reusable Robolectric helpers for driving Android Bluetooth bonding logic in androidHostTest source sets.

These let a unit test exercise the real AndroidBluetoothRepository.bond() (and any future BLE bonding code) without an emulator and without a production seam. They rely on two Robolectric behaviors (verified against Robolectric 4.16.x):

Isolation note: because the device cache is static and survives across tests in the same JVM, give each test a distinct MAC so bond-state cannot bleed between tests.

+
object RobolectricBleBonding(source)

Reusable Robolectric helpers for driving Android Bluetooth bonding logic in androidHostTest source sets.

These let a unit test exercise the real AndroidBluetoothRepository.bond() (and any future BLE bonding code) without an emulator and without a production seam. They rely on two Robolectric behaviors (verified against Robolectric 4.16.x):

Isolation note: because the device cache is static and survives across tests in the same JVM, give each test a distinct MAC so bond-state cannot bleed between tests.

diff --git a/api/feature/connections/org.meshtastic.feature.connections.ui.components/-connection-action-button.html b/api/feature/connections/org.meshtastic.feature.connections.ui.components/-connection-action-button.html index 99892d5b94..5a20ffb2ec 100644 --- a/api/feature/connections/org.meshtastic.feature.connections.ui.components/-connection-action-button.html +++ b/api/feature/connections/org.meshtastic.feature.connections.ui.components/-connection-action-button.html @@ -94,7 +94,7 @@

ConnectionActionButton

-
@Composable
fun ConnectionActionButton(onClick: () -> Unit, icon: ImageVector, text: String, modifier: Modifier = Modifier, style: ConnectionActionButtonStyle = ConnectionActionButtonStyle.Filled, enabled: Boolean = true, iconContentDescription: String? = null)(source)

Shared "icon + label" button used throughout the Connections screen. Centralises M3 sizing conventions (ButtonDefaults.IconSize, ButtonDefaults.IconSpacing, and the variant-appropriate *WithIconContentPadding) so every scan / add / empty-state affordance renders identically.

Parameters

iconContentDescription

accessibility label for the leading icon. Defaults to null because the visible text usually describes the action; override when the icon carries information the text does not.

+
@Composable
fun ConnectionActionButton(onClick: () -> Unit, icon: ImageVector, text: String, modifier: Modifier = Modifier, style: ConnectionActionButtonStyle = ConnectionActionButtonStyle.Filled, enabled: Boolean = true, iconContentDescription: String? = null)(source)

Shared "icon + label" button used throughout the Connections screen. Centralises M3 sizing conventions (ButtonDefaults.IconSize, ButtonDefaults.IconSpacing, and the variant-appropriate *WithIconContentPadding) so every scan / add / empty-state affordance renders identically.

Parameters

iconContentDescription

accessibility label for the leading icon. Defaults to null because the visible text usually describes the action; override when the icon carries information the text does not.

diff --git a/api/feature/connections/org.meshtastic.feature.connections.ui.components/index.html b/api/feature/connections/org.meshtastic.feature.connections.ui.components/index.html index f53f393d17..09b19d2c28 100644 --- a/api/feature/connections/org.meshtastic.feature.connections.ui.components/index.html +++ b/api/feature/connections/org.meshtastic.feature.connections.ui.components/index.html @@ -158,7 +158,7 @@
-
@Composable
fun ConnectionActionButton(onClick: () -> Unit, icon: ImageVector, text: String, modifier: Modifier = Modifier, style: ConnectionActionButtonStyle = ConnectionActionButtonStyle.Filled, enabled: Boolean = true, iconContentDescription: String? = null)

Shared "icon + label" button used throughout the Connections screen. Centralises M3 sizing conventions (ButtonDefaults.IconSize, ButtonDefaults.IconSpacing, and the variant-appropriate *WithIconContentPadding) so every scan / add / empty-state affordance renders identically.

+
@Composable
fun ConnectionActionButton(onClick: () -> Unit, icon: ImageVector, text: String, modifier: Modifier = Modifier, style: ConnectionActionButtonStyle = ConnectionActionButtonStyle.Filled, enabled: Boolean = true, iconContentDescription: String? = null)

Shared "icon + label" button used throughout the Connections screen. Centralises M3 sizing conventions (ButtonDefaults.IconSize, ButtonDefaults.IconSpacing, and the variant-appropriate *WithIconContentPadding) so every scan / add / empty-state affordance renders identically.

diff --git a/main/ar-rSA/user/discovery.html b/main/ar-rSA/user/discovery.html index 3b28d0555c..36b4b17e22 100644 --- a/main/ar-rSA/user/discovery.html +++ b/main/ar-rSA/user/discovery.html @@ -5,4 +5,4 @@ ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) -

Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:.

What to look for What it means
All hops show Good SNR (green) Healthy path — messages flow reliably
One hop shows a poor SNR (orange or red) Weak link — this relay segment is fragile
Many hops (4+) Long path — consider repositioning a node to shorten it
Different path on retry Mesh is adapting — multiple routes exist (this is good!)

💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network.

Troubleshooting with Traceroute

Neighbor Info

The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh.

Enabling Neighbor Info

  1. Navigate to Settings → Module configuration → Neighbor Info.
  2. Enable the module.
  3. Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
  4. Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air.

Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.

Viewing neighbor data

ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further.

Node list as a discovery tool

The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively.

Finding new nodes

Assessing connectivity

Infrastructure audit

See Nodes for full details on filtering and sorting options.

Tips for Mesh exploration

+

Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:.

What to look for What it means
All hops show Good SNR (green) Healthy path — messages flow reliably
One hop shows a poor SNR (orange or red) Weak link — this relay segment is fragile
Many hops (4+) Long path — consider repositioning a node to shorten it
Different path on retry Mesh is adapting — multiple routes exist (this is good!)

💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network.

Troubleshooting with Traceroute

Neighbor Info

The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh.

Enabling Neighbor Info

  1. Navigate to Settings → Module configuration → Neighbor Info.
  2. Enable the module.
  3. Set Update Interval. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
  4. Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air.

Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.

Viewing neighbor data

ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further.

Node list as a discovery tool

The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively.

Finding new nodes

Assessing connectivity

Infrastructure audit

See Nodes for full details on filtering and sorting options.

Tips for Mesh exploration

diff --git a/main/ar-rSA/user/mqtt.html b/main/ar-rSA/user/mqtt.html index 23da3e9fbe..b9b01bbd3c 100644 --- a/main/ar-rSA/user/mqtt.html +++ b/main/ar-rSA/user/mqtt.html @@ -1,2 +1,2 @@ MQTT | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 العربية
Meshtastic Docs ↗

🌐 العربية — Community translation View in English

MQTT

MQTT bridges your Meshtastic mesh network to the internet, enabling long-range communication beyond radio range.

Overview

The MQTT module connects your node to an MQTT broker, allowing:

  • Messages to reach nodes on different physical meshes via the internet
  • Integration with home automation and monitoring systems
  • Publishing node positions to the public Meshtastic map
  • Custom data pipelines for logging and alerting

How It Works 

[Your Node] → Radio → [Gateway Node with Wi-Fi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node]
-

A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh.

Configuration

Enabling MQTT

  1. Navigate to Settings → Module configuration → MQTT.
  2. Enable the MQTT module.
  3. Configure the broker connection:
Setting الوصف Default
Address MQTT broker hostname mqtt.meshtastic.org
Username Broker authentication meshdev
Password Broker authentication large4cats
Root topic Base topic for messages msh, which the radio rewrites to msh/<REGION> once you set a region
Encryption enabled Encrypt MQTT payload Enabled
JSON output enabled Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it Disabled
TLS enabled Secure connection to broker Disabled
Map reporting Report position to public map Disabled
Proxy to client enabled Relay MQTT through the connected phone Disabled

Connection Status and Test Connection

The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here.

Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason.

MQTT Proxy on This Phone

If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection.

ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them.

The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration.

Default Meshtastic Broker

The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing.

When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without).

🔒 Privacy: Messages on the public broker are readable by anyone subscribed. Always use channel encryption for private communications.

Private Broker

For better privacy and control, you can run your own MQTT broker:

  • Mosquitto (lightweight, open-source)
  • HiveMQ
  • EMQX

Configure your node to point to your private broker with appropriate credentials.

Map Reporting

When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.

Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.

Reports appear at meshmap.net and similar community map services.

🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published.

Direction الوصف
Uplink Messages from mesh → MQTT broker
Downlink Messages from MQTT broker → mesh

Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on.

Message Formats

MQTT carries two payload formats:

Format الوصف Use case
Protobuf Binary Meshtastic protobuf encoding Node-to-node mesh bridging
JSON Human-readable JSON on the /2/json/ topic Consumers outside the mesh (dashboards, home automation)

ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads.

Encryption & Privacy

Understanding the layered encryption model:

  1. Channel encryption happens on the mesh before MQTT. If your channel has a PSK, the MQTT payload is already encrypted — the broker and any subscribers see only the ciphertext.
  2. Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard.
  3. TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping.

🔒 Security: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications.

Best Practices

  • Use channel-level encryption (PSK) on channels that bridge to MQTT
  • Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes memory)
  • Use a private broker for sensitive deployments
  • Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh
  • Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back

Troubleshooting

MQTT Not Connecting

  • Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself.
  • Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces.
  • Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443).
  • DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly.

Messages Not Bridging

  • Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway.
  • Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage.
  • Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root.
  • Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway.
  • Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in.
+

A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh.

Configuration

Enabling MQTT

  1. Navigate to Settings → Module configuration → MQTT.
  2. Enable the MQTT module.
  3. Configure the broker connection:
Setting الوصف Default
Address MQTT broker hostname mqtt.meshtastic.org
Username Broker authentication meshdev
Password Broker authentication large4cats
Root topic Base topic for messages msh, which the radio rewrites to msh/<REGION> once you set a region
Encryption enabled Encrypt MQTT payload Enabled
JSON output enabled Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it Disabled
TLS enabled Secure connection to broker Disabled
Map reporting Report position to public map Disabled
Proxy to client enabled Relay MQTT through the connected phone Disabled

Connection Status and Test Connection

The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here.

Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason.

MQTT Proxy on This Phone

If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection.

ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them.

The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration.

Default Meshtastic Broker

The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing.

When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without).

🔒 Privacy: Messages on the public broker are readable by anyone subscribed. Always use channel encryption for private communications.

Private Broker

For better privacy and control, you can run your own MQTT broker:

Configure your node to point to your private broker with appropriate credentials.

Map Reporting

When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.

Turning it on opens a consent card. Turn on I agree. and choose a Map Publish Interval of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.

Reports appear at meshmap.net and similar community map services.

🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published.

Direction الوصف
Uplink Messages from mesh → MQTT broker
Downlink Messages from MQTT broker → mesh

Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on.

Message Formats

MQTT carries two payload formats:

Format الوصف Use case
Protobuf Binary Meshtastic protobuf encoding Node-to-node mesh bridging
JSON Human-readable JSON on the /2/json/ topic Consumers outside the mesh (dashboards, home automation)

ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads.

Encryption & Privacy

Understanding the layered encryption model:

  1. Channel encryption happens on the mesh before MQTT. If your channel has a PSK, the MQTT payload is already encrypted — the broker and any subscribers see only the ciphertext.
  2. Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard.
  3. TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping.

🔒 Security: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications.

Best Practices

Troubleshooting

MQTT Not Connecting

Messages Not Bridging

diff --git a/main/ar-rSA/user/settings-module-admin.html b/main/ar-rSA/user/settings-module-admin.html index 64875a1e2a..a30be8dd2c 100644 --- a/main/ar-rSA/user/settings-module-admin.html +++ b/main/ar-rSA/user/settings-module-admin.html @@ -1 +1 @@ - Settings — Modules & Admin | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 العربية
Meshtastic Docs ↗

🌐 العربية — Community translation View in English

Settings — Modules & Admin

Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.

💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.

Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:

A toggle setting in the on position

A dropdown setting, expanded to show its list of options

A text field setting with a value entered

A module settings card with its title and grouped controls

إعدادات الجهاز

Every module lives under Settings → Module configuration.

⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes.

MQTT module

Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.

Setting الوصف
MQTT enabled Toggle MQTT bridge
Address MQTT broker address
Username Authentication username
Password Authentication password
Encryption enabled Encrypt MQTT payloads
JSON output enabled Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS enabled Use secure connection
Root topic Base MQTT topic path
Proxy to client enabled Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy on this phone The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT
Map reporting Publish position to the public map — see the Map reporting group that follows

Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:

Setting الوصف
I agree. Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map reporting interval (seconds) How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered

See MQTT for a detailed usage guide including encryption, privacy, and broker setup.

Serial module

Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.

Setting الوصف
Serial enabled Activate serial communication
Echo enabled Echo received serial data back
Serial mode Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX GPIO pins for the serial connection
Serial baud rate Port speed
استغرق وقت طويل How long to wait before considering an incoming message complete
Override console serial port Take over the port the debug console normally uses

External Notification module

Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.

There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.

Setting الوصف
External notification enabled Master toggle for the module
Alert message LED / buzzer / vibra Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra Which outputs fire on a received bell character
Output LED (GPIO) Pin the LED is wired to
Output LED active high Whether the LED pin is active high or low
Output buzzer (GPIO) Pin the buzzer is wired to
Output vibra (GPIO) Pin the vibration motor is wired to
Use PWM buzzer Drive the buzzer with PWM, which allows tones rather than a single pitch
Use I2S as buzzer Send the alert through an I2S audio output instead
Output duration (milliseconds) How long a single alert lasts
Nag timeout (seconds) Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Ringtone The tone played on a PWM buzzer, in RTTTL. Can be imported from a file

Store & Forward module

Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.

Setting الوصف
Store & Forward enabled Activate store and forward
Heartbeat Periodically announce this node’s store-and-forward capability
Number of records Maximum stored messages
History return max Max messages to replay
History return window Time window for replay
Server Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)

💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.

Range Test module

⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.

Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.

Setting الوصف
Range test enabled Activate range testing
Sender message interval (seconds) Time between test transmissions, chosen from a dropdown of fixed intervals
Save .CSV in storage (ESP32 only) Log received test data to the node’s own filesystem. ESP32 hardware only

Telemetry module

Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).

Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.

Setting الوصف
Send Device Telemetry Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval How often to report battery, uptime and channel utilization
Environment metrics module enabled Report the attached environment sensors
Environment metrics update interval How often to report them
Environment metrics on-screen enabled Also show these readings on the device’s own display
Environment metrics use Fahrenheit Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Air quality metrics module enabled Report particulate and CO₂ sensor data
Air quality metrics update interval How often to report them
Power metrics module enabled Report the per-channel voltage and current readings
Power metrics update interval How often to report them
Power metrics on-screen enabled Also show power readings on the device’s display

See Telemetry & Sensors for supported sensors and configuration recommendations.

Canned Message module

Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.

Setting الوصف
Canned message enabled ⚠️ Deprecated in the protobuf schema
الرسائل Newline-separated list of messages
Send bell Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Rotary encoder #1 enabled Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port The three pins the encoder is wired to
Generate input event on Press / CW / CCW Which key event each encoder action produces
Up/Down/Select input enabled A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source ⚠️ Deprecated in the protobuf schema

Audio module

Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.

Setting الوصف
CODEC 2 enabled Activate audio module
CODEC2 sample rate Audio quality/bandwidth tradeoff
PTT pin GPIO pin for the push-to-talk button
I2S word select GPIO pin for I2S WS
I2S data in GPIO pin for I2S DIN
I2S data out GPIO pin for I2S DOUT
I2S clock GPIO pin for the I2S bit clock

ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.

Remote Hardware module

GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.

⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.

Setting الوصف
Remote Hardware enabled Activate remote GPIO access
Allow undefined pin access Allow access to any GPIO pin (security risk)
Available pins Up to 4 GPIO pins this node exposes for remote read/write

Neighbor Info module

Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.

Setting الوصف
Neighbor Info enabled Activate neighbor broadcasting
Update interval (seconds) How often to broadcast neighbor list
Transmit over LoRa Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name

See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.

Ambient Lighting module

Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.

Setting الوصف
LED state Turn the LED on or off
الحالي LED current limit (0–31)
Red / Green / Blue Individual color channel values (0–255)

Detection Sensor module

Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.

Setting الوصف
Detection Sensor enabled Activate detection sensor
GPIO pin to monitor GPIO pin connected to sensor
Detection trigger type How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Use INPUT_PULLUP mode Enable the pin’s internal pull-up resistor
Minimum broadcast (seconds) Minimum time between alert broadcasts
State broadcast (seconds) Periodic state broadcast interval
Send bell with alert message Include bell character in alerts
Friendly name Custom name for this sensor

Paxcounter module

People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.

Setting الوصف
Paxcounter enabled Activate people counting
Update interval (seconds) How often to report counts
Wi-Fi RSSI threshold Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE RSSI threshold The same cut-off for BLE advertisements (defaults to −80 dBm)

💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.

Status Message module

The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.

Mesh Beacon module

Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.

TAK module

Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.

الإدارة

Remote Administration

Remotely configure nodes that share your admin key:

  1. Select the target node in the node list.
  2. Navigate to Settings for that node.
  3. Modify configuration.
  4. Tap Save — changes are sent over the mesh.

⚠️ Important: Requires an admin key configured on both your node and the target node.

Device Actions

Settings → Administration holds five one-shot actions, each behind a confirmation dialog:

Action What it does
Set time Sends your phone’s clock to the node
إعادة التشغيل Restarts the node
Shutdown Powers the node down
Factory reset Returns every setting to its factory default
NodeDB reset Clears the node database. This dialog carries a Preserve Favorites? switch

⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.

Backup & Restore

Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.

Advanced

Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.

Clean Node Database

Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.

  • Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
  • Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.

The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.

Debug Panel

Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.

App Settings

The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:

Privacy

  • Allow analytics and crash reporting — opt in or out of diagnostics.
  • Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
  • Homoglyph encoding — how look-alike characters in names are handled.

Appearance

  • Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
  • Theme and Language.
  • Show full message timestamps.

Persistence

  • A cache limit for how much history is kept.
  • Export rangetest packets, Export all packets and Export node database.

On their own

  • Node Layout — how much detail each row of the node list shows.
  • Wi-Fi Provisioning for mPWRD-OS — see Connections.
  • Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
  • System AI — appears only where app functions are available; see App Functions.

A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.

حول

Settings → About carries the app’s own identity rather than the node’s:

Three sections:

  • What is Meshtastic? — a short description of the project.
  • Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
  • Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.

The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.

Acknowledgements

Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.

Troubleshooting remote admin

  • “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
  • Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
  • Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
+ Settings — Modules & Admin | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 العربية
Meshtastic Docs ↗

🌐 العربية — Community translation View in English

Settings — Modules & Admin

Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.

💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.

Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:

A toggle setting in the on position

A dropdown setting, expanded to show its list of options

A text field setting with a value entered

A module settings card with its title and grouped controls

إعدادات الجهاز

Every module lives under Settings → Module configuration.

⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes.

MQTT module

Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.

Setting الوصف
MQTT enabled Toggle MQTT bridge
Address MQTT broker address
Username Authentication username
Password Authentication password
Encryption enabled Encrypt MQTT payloads
JSON output enabled Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS enabled Use secure connection
Root topic Base MQTT topic path
Proxy to client enabled Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy on this phone The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT
Map reporting Publish position to the public map — see the Map reporting group that follows

Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:

Setting الوصف
I agree. Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered

See MQTT for a detailed usage guide including encryption, privacy, and broker setup.

Serial module

Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.

Setting الوصف
Serial enabled Activate serial communication
Echo enabled Echo received serial data back
Serial mode Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX GPIO pins for the serial connection
Serial baud rate Port speed
استغرق وقت طويل How long to wait before considering an incoming message complete
Override console serial port Take over the port the debug console normally uses

External Notification module

Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.

There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.

Setting الوصف
External notification enabled Master toggle for the module
Alert message LED / buzzer / vibra Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra Which outputs fire on a received bell character
Output LED (GPIO) Pin the LED is wired to
Output LED active high Whether the LED pin is active high or low
Output buzzer (GPIO) Pin the buzzer is wired to
Output vibra (GPIO) Pin the vibration motor is wired to
Use PWM buzzer Drive the buzzer with PWM, which allows tones rather than a single pitch
Use I2S as buzzer Send the alert through an I2S audio output instead
GPIO Output Duration How long a single alert lasts
Nag Timeout Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Ringtone The tone played on a PWM buzzer, in RTTTL. Can be imported from a file

Store & Forward module

Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.

Setting الوصف
Store & Forward enabled Activate store and forward
Heartbeat Periodically announce this node’s store-and-forward capability
Number of records Maximum stored messages
History return max Max messages to replay
History return window Time window for replay
Server Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)

💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.

Range Test module

⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.

Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.

Setting الوصف
Range test enabled Activate range testing
Sender Interval Time between test transmissions, chosen from a dropdown of fixed intervals
Save .CSV in storage (ESP32 only) Log received test data to the node’s own filesystem. ESP32 hardware only

Telemetry module

Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).

Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.

Setting الوصف
Send Device Telemetry Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval How often to report battery, uptime and channel utilization
Environment metrics module enabled Report the attached environment sensors
Environment metrics update interval How often to report them
Environment metrics on-screen enabled Also show these readings on the device’s own display
Environment metrics use Fahrenheit Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Air quality metrics module enabled Report particulate and CO₂ sensor data
Air quality metrics update interval How often to report them
Power metrics module enabled Report the per-channel voltage and current readings
Power metrics update interval How often to report them
Power metrics on-screen enabled Also show power readings on the device’s display

See Telemetry & Sensors for supported sensors and configuration recommendations.

Canned Message module

Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.

Setting الوصف
Canned message enabled ⚠️ Deprecated in the protobuf schema
الرسائل Newline-separated list of messages
Send bell Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Rotary encoder #1 enabled Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port The three pins the encoder is wired to
Generate input event on Press / CW / CCW Which key event each encoder action produces
Up/Down/Select input enabled A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source ⚠️ Deprecated in the protobuf schema

Audio module

Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.

Setting الوصف
CODEC 2 enabled Activate audio module
CODEC2 sample rate Audio quality/bandwidth tradeoff
PTT pin GPIO pin for the push-to-talk button
I2S word select GPIO pin for I2S WS
I2S data in GPIO pin for I2S DIN
I2S data out GPIO pin for I2S DOUT
I2S clock GPIO pin for the I2S bit clock

ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.

Remote Hardware module

GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.

⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.

Setting الوصف
Remote Hardware enabled Activate remote GPIO access
Allow undefined pin access Allow access to any GPIO pin (security risk)
Available pins Up to 4 GPIO pins this node exposes for remote read/write

Neighbor Info module

Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.

Setting الوصف
Neighbor Info enabled Activate neighbor broadcasting
Update Interval How often to broadcast neighbor list
Transmit over LoRa Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name

See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.

Ambient Lighting module

Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.

Setting الوصف
LED state Turn the LED on or off
الحالي LED current limit (0–31)
Red / Green / Blue Individual color channel values (0–255)

Detection Sensor module

Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.

Setting الوصف
Detection Sensor enabled Activate detection sensor
GPIO pin to monitor GPIO pin connected to sensor
Detection trigger type How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Use INPUT_PULLUP mode Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts Minimum time between alert broadcasts
State Broadcast Interval Periodic state broadcast interval
Send bell with alert message Include bell character in alerts
Friendly name Custom name for this sensor

Paxcounter module

People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.

Setting الوصف
Paxcounter enabled Activate people counting
Update Interval How often to report counts
WiFi Threshold (dBm) Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm) The same cut-off for BLE advertisements (defaults to −80 dBm)

💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.

Status Message module

The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.

Mesh Beacon module

Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.

TAK module

Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.

الإدارة

Remote Administration

Remotely configure nodes that share your admin key:

  1. Select the target node in the node list.
  2. Navigate to Settings for that node.
  3. Modify configuration.
  4. Tap Save — changes are sent over the mesh.

⚠️ Important: Requires an admin key configured on both your node and the target node.

Device Actions

Settings → Administration holds five one-shot actions, each behind a confirmation dialog:

Action What it does
Set time Sends your phone’s clock to the node
إعادة التشغيل Restarts the node
Shutdown Powers the node down
Factory reset Returns every setting to its factory default
NodeDB reset Clears the node database. This dialog carries a Preserve Favorites? switch

⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.

Backup & Restore

Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.

Advanced

Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.

Clean Node Database

Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.

  • Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
  • Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.

The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.

Debug Panel

Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.

App Settings

The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:

Privacy

  • Allow analytics and crash reporting — opt in or out of diagnostics.
  • Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
  • Homoglyph encoding — how look-alike characters in names are handled.

Appearance

  • Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
  • Theme and Language.
  • Show full message timestamps.

Persistence

  • A cache limit for how much history is kept.
  • Export rangetest packets, Export all packets and Export node database.

On their own

  • Node Layout — how much detail each row of the node list shows.
  • Wi-Fi Provisioning for mPWRD-OS — see Connections.
  • Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
  • System AI — appears only where app functions are available; see App Functions.

A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.

حول

Settings → About carries the app’s own identity rather than the node’s:

Three sections:

  • What is Meshtastic? — a short description of the project.
  • Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
  • Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.

The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.

Acknowledgements

Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.

Troubleshooting remote admin

  • “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
  • Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
  • Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
diff --git a/main/ar-rSA/user/settings-radio-user.html b/main/ar-rSA/user/settings-radio-user.html index d44beb6d60..5430de1a70 100644 --- a/main/ar-rSA/user/settings-radio-user.html +++ b/main/ar-rSA/user/settings-radio-user.html @@ -1 +1 @@ - Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 العربية
Meshtastic Docs ↗

🌐 العربية — Community translation View in English

Settings — Radio & User

Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How these screens work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting الوصف
Long Name Your display name (up to 39 characters)
Short Name 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Unmessageable Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur node (Ham) Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in.

Configuration

Device Config

On Settings → Device configuration → Device.

Setting الوصف Default
Device Role Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Rebroadcast Mode How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Node Info Broadcast Interval How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Double Tap as Button Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Enabled
LED Heartbeat Blink the status LED periodically Enabled
Time Zone POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it —
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to —

LoRa Config

On Settings → LoRa.

Setting الوصف Default
الجهة Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number Unset (must configure)
Presets Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Transmit Power Transmission power (dBm); 0 = max allowed for region 0 (region max)
Frequency Override Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Use Preset On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead From preset
Coding Rate Manual mode only: 5–8. More redundancy costs airtime From preset
Bandwidth Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Frequency Slot Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmit Enabled Turning this off makes the node receive-only On
Override Duty Cycle Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
Ignore MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok to MQTT Allow your packets to be forwarded to MQTT by gateways Off
RX Boosted Gain Extra receive gain on SX126x radios; costs a little current Off
PA fan disabled Turn off the power-amplifier fan on hardware that has one Off

The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set.

Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Speed SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a modem preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Display Config

On Settings → Device configuration → Display. These control the node’s own screen, not the app’s.

Setting الوصف
Screen on for How long the display stays lit before sleeping
Carousel interval How often the node cycles between screens on its own
Display mode Screen layout/density used by the firmware
Display units Metric or Imperial on the node’s screen
Use 12h clock format Show the node’s clock as 12-hour rather than 24-hour
Bold Heading Draw the screen’s heading text in bold
Flip screen Rotate the display 180° for an inverted mounting
OLED type Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED
Wake on tap or motion Light the screen when the node is tapped or moved
Compass orientation Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each
Always point north Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Position Config

On Settings → Device configuration → Position.

Setting الوصف
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the node asks its GPS for a fix
Broadcast Interval How often the position is shared with the mesh
Smart Position Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Fixed Position Use a manually entered latitude, longitude and altitude instead of the GPS
Position Flags A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Power Config

On Settings → Device configuration → Power.

Setting الوصف
Enable power saving mode Let the node sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the node stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC multiplier override ratio The correction factor itself, used only when the override is on
Battery INA_2XX I2C address Address of an external INA-series power sensor, if fitted

Network Config

On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node.

Setting الوصف
Wi-Fi enabled Enable the Wi-Fi node (ESP32 nodes)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Password Network password
Ethernet enabled Use a wired connection on hardware that has one
IPv4 mode DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP server Time synchronization server
rsyslog server Remote logging server

Network Config with a static IPv4 address entered

Bluetooth Config

On Settings → Device configuration → Bluetooth, on nodes with Bluetooth.

Setting الوصف
Bluetooth enabled Enable/disable BLE radio
Pairing mode Fixed PIN, Random PIN, or No PIN
Fixed PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Security Config

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

Setting الوصف
Public Key Your node’s public key (read-only)
Admin Key Keys permitted to administer this node remotely — up to three
Private Key Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it
Regenerate Private Key Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Serial console Serial console over the Stream API
Debug log API enabled Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth
Managed Mode Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.

+ Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 العربية
Meshtastic Docs ↗

🌐 العربية — Community translation View in English

Settings — Radio & User

Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How these screens work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting الوصف
Long Name Your display name (up to 39 characters)
Short Name 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Unmessageable Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur node (Ham) Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in.

Configuration

Device Config

On Settings → Device configuration → Device.

Setting الوصف Default
Device Role Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Rebroadcast Mode How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Node Info Broadcast Interval How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Double Tap as Button Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Enabled
LED Heartbeat Blink the status LED periodically Enabled
Time Zone POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it —
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to —

LoRa Config

On Settings → LoRa.

Setting الوصف Default
الجهة Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number Unset (must configure)
Presets Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Transmit Power (dBm) Transmission power; 0 = max allowed for region 0 (region max)
Frequency Override Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Use Preset On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead From preset
Coding Rate Manual mode only: 5–8. More redundancy costs airtime From preset
Bandwidth Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Frequency Slot Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmit Enabled Turning this off makes the node receive-only On
Override Duty Cycle Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
Ignore MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok to MQTT Allow your packets to be forwarded to MQTT by gateways Off
RX Boosted Gain Extra receive gain on SX126x radios; costs a little current Off
PA fan disabled Turn off the power-amplifier fan on hardware that has one Off

The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set.

Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Speed SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a modem preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Display Config

On Settings → Device configuration → Display. These control the node’s own screen, not the app’s.

Setting الوصف
Screen on for How long the display stays lit before sleeping
Carousel interval How often the node cycles between screens on its own
Display mode Screen layout/density used by the firmware
Display units Metric or Imperial on the node’s screen
Use 12h clock format Show the node’s clock as 12-hour rather than 24-hour
Bold Heading Draw the screen’s heading text in bold
Flip screen Rotate the display 180° for an inverted mounting
OLED type Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED
Wake on tap or motion Light the screen when the node is tapped or moved
Compass orientation Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each
Always point north Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Position Config

On Settings → Device configuration → Position.

Setting الوصف
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the node asks its GPS for a fix
Broadcast Interval How often the position is shared with the mesh
Smart Position Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Fixed Position Use a manually entered latitude, longitude and altitude instead of the GPS
Position Flags A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Power Config

On Settings → Device configuration → Power.

Setting الوصف
Enable power saving mode Let the node sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the node stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC multiplier override ratio The correction factor itself, used only when the override is on
Battery INA_2XX I2C address Address of an external INA-series power sensor, if fitted

Network Config

On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node.

Setting الوصف
Wi-Fi enabled Enable the Wi-Fi node (ESP32 nodes)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Password Network password
Ethernet enabled Use a wired connection on hardware that has one
IPv4 mode DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP server Time synchronization server
rsyslog server Remote logging server

Network Config with a static IPv4 address entered

Bluetooth Config

On Settings → Device configuration → Bluetooth, on nodes with Bluetooth.

Setting الوصف
Bluetooth enabled Enable/disable BLE radio
Pairing mode Fixed PIN, Random PIN, or No PIN
Fixed PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Security Config

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

Setting الوصف
Public Key Your node’s public key (read-only)
Admin Key Keys permitted to administer this node remotely — up to three
Private Key Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it
Regenerate Private Key Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Serial console Serial console over the Stream API
Debug log API enabled Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth
Managed Mode Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.

diff --git a/main/assets/css/just-the-docs-dark.css.map b/main/assets/css/just-the-docs-dark.css.map index d801b14c03..6c48179c4f 100644 --- a/main/assets/css/just-the-docs-dark.css.map +++ b/main/assets/css/just-the-docs-dark.css.map @@ -1 +1 @@ -{"version":3,"sourceRoot":"","sources":["../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/vendor/accessible-pygments/github-light.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/vendor/accessible-pygments/github-dark.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/vendor/normalize.scss/normalize.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/base.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/color_schemes/dark.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/support/mixins/_typography.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/support/mixins/_layout.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/support/_variables.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/layout.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/content.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/navigation.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/typography.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/labels.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/buttons.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/support/mixins/_buttons.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/search.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/tables.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/code.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/utilities/_colors.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/utilities/_layout.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/utilities/_typography.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/utilities/_lists.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/utilities/_spacing.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/print.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/skiptomain.scss","just-the-docs-dark.scss"],"names":[],"mappings":";AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAUA;EAAkB;;;AAClB;EAAgB;EAAiB;AACjC;EAAkB;EAAiB;AACnC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAkB;EAAiB;AACnC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAqB;AACtC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAoB;AACrC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAgB;EAAiB;AACjC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AChFlC;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAUA;EAAkB;;;AAClB;EAAa;EAAqB;;;AAClC;EAAgB;EAAgB;EAAqB;AACrD;EAAkB;EAAiB;AACnC;EAAkB;EAAiB;AACnC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAgB;EAAgB;EAAoB;AACpD;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAiB;EAAgB;EAAqB;AACtD;EAAiB;EAAgB;EAAqB;AACtD;EAAiB;EAAgB;EAAmB;EAAqB;AACzE;EAAkB;EAAgB;EAAqB;AACvD;EAAiB;EAAgB;EAAqB;AACtD;EAAiB;EAAgB;EAAmB;EAAqB;AACzE;EAAiB;EAAgB;EAA4B;AAC7D;EAAiB;EAAgB;EAAqB;AACtD;EAAkB;EAAgB;EAAmB;EAAqB;AAC1E;EAAiB;EAAiB;AAClC;EAAiB;EAAgB;EAAoB;AACrD;EAAiB;EAAgB;EAA4B;AAC7D;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAgB;EAAoB;AACrD;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAA0B;EAAgB;EAA6B;AACvE;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAgB;EAAoB;AACrD;EAAiB;EAAgB;EAAoB;AACrD;EAAiB;EAAgB;EAAoB;AACrD;EAAiB;EAAiB;AAClC;EAAiB;EAAgB;EAAoB;AACrD;EAAiB;EAAgB;EAAoB;AACrD;EAAiB;EAAgB;EAAoB;AACrD;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAgB;EAAoB;AACrD;EAAiB;EAAiB;AAClC;EAAgB;EAAiB;AACjC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAgB;EAAoB;AACrD;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AC1FlC;AAEA;AAAA;AAGA;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAAA;AAKA;EACE;EACA;EACA;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;EACA;;;AAGF;AAAA;AAAA;AAIA;AAAA;EAEE;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;AAAA;EAGE;EACA;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;EAEE;EACA;EACA;EACA;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAAA;AAKA;AAAA;AAAA;AAAA;AAAA;EAKE;EACA;EACA;EACA;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;AAEE;EACA;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;AAEE;EACA;;;AAGF;AAAA;AAAA;AAIA;AAAA;AAAA;AAAA;EAIE;;;AAGF;AAAA;AAAA;AAIA;AAAA;AAAA;AAAA;EAIE;EACA;;;AAGF;AAAA;AAAA;AAIA;AAAA;AAAA;AAAA;EAIE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAOA;EACE;EACA;EACA;EACA;EACA;EACA;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;EAEE;EACA;;;AAGF;AAAA;AAAA;AAIA;AAAA;EAEE;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AC1VF;EACE,cCJa;;;ADOf;EACE;;;AAGF;EACE;;AEmBA;EACE;;AClBA;EHHJ;IEyBI;;;;AFnBJ;EACE,aIfiB;EJgBjB;EACA,aIbiB;EJcjB,OIiBY;EJhBZ,kBIYY;EJXZ;;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAYE;;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAOE;EACA;EACA;EACA,aI1CyB;EJ2CzB,OIjBY;;;AJoBd;EACE;EACA;;;AAGF;EACE,OCzDW;ED0DX;;;AAGF;EACE;EACA,uBInCY;EJoCZ;;AAEA;EACE;;;AAIJ;EACE,aIvEiB;EJwEjB;EACA,aIvEiB;;;AJ0EnB;AAAA;EAEE;;;AAGF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;EACA;EACA,kBInEY;EJoEZ;;;AAIF;EACE;EAGA;EACA;EACA;EACA;;;AK7GF;EACE;EACA;EACA;EACA,kBD4BY;;ADpBV;EEZJ;IAOI;IACA;IACA,ODwFW;ICvFX;IACA;IACA;;;AFAA;EEZJ;IAgBI;IACA,WD+EQ;;;ADpFR;EEQF;IAEI,aD2ES;;;ADrFX;EEQF;IAQI;;;AAOF;EACE;EACA,kBDLQ;;ADpBV;EEuBA;IAKI;IACA,kBDTM;;;ACYR;EACE;;AFjCJ;EEgCE;IAII;;;;AAOV;EACE;;AF5CE;EE2CJ;IAII;IACA,WDyCY;;;;ACrChB;EACE,aDaK;ECZL,gBDYK;EDvDL,eCuDK;EDtDL,cCsDK;;ADlEH;EEoDJ;IFrCI,eCqDG;IDpDH,cCoDG;;;ADpEH;EEoDJ;IAOI,aDSG;ICRH,gBDQG;;;;ACJP;EACE;EACA;;AFlEE;EEgEJ;IAKI;IACA;IACA,QDmBY;;;;ACfhB;AAAA;AAAA;EAGE;;AF9EE;EE2EJ;AAAA;AAAA;IAMI,ODGQ;;;;ACCZ;EACE;;AAEA;EACE;;AFzFA;EEqFJ;IAQI;IACA,aDxBG;ICyBH,gBD7BG;IC8BH;IACA;;;;AAIJ;EACE;EACA,YDbc;ECcd;;AFxGE;EEqGJ;IAMI,QDjBY;ICkBZ,YDlBY;ICmBZ;;;;AAIJ;EACE;EACA;EACA;EACA;EACA,aDrDK;ECsDL,gBDtDK;ECuDL,ODnGY;EDVZ,eCuDK;EDtDL,cCsDK;;ADlEH;EEiHJ;IFlGI,eCqDG;IDpDH,cCoDG;;;AF/BL;EACE;;ACtCA;EEiHJ;IHvEI;IACA,aEhDuB;;;ADKvB;EEiHJ;IAcI,aD/DG;ICgEH,gBDhEG;;;;AC+EP;EACE;EACA;EACA,SDhFK;ECiFL;;;AFnJE;EEuJF;IACE;;;AAIJ;EACE;;;AAQF;EACE;;;AAOF;EACE;EACA;EACA;EACA,aD/GK;ECgHL,gBDhHK;EDvDL,eCuDK;EDtDL,cCsDK;;ADlEH;EE6KJ;IF9JI,eCqDG;IDpDH,cCoDG;;;AFvEL;EACE;;ACEA;EE6KJ;IH3KI;;;ACFA;EE6KJ;IAYI;IACA;;;;AAIJ;EACE,OD5HK;EC6HL,QD7HK;EC8HL,OJ3MW;;;AKCb;EACE,aFEoB;;AEApB;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAOE;;AAGF;EACE;EACA;;AAGF;AAAA;EAEE;;AAIA;EACE,YF+CC;;AE3CL;EACE;EACA;;AAEA;EACE;;AAEA;EACE;EACA;EACA;EACA,OFfM;EEgBN;EACA;;AJ1BN;EACE;;ACRA;EG2BE;IJfF;;;ACZA;EG2BE;IAUI;;;AAIJ;EACE;;AAGE;EACE;EACA;;AAOV;EACE;;AAGE;EACE;EACA;EACA,OF7CM;EE8CN;;AAMJ;EACE;;AAIJ;EACE;EACA;;AAKF;EACE;;AAGF;EACE;;AAGF;EACE;EACA;;AAGF;AAAA;EAEE;;AAGF;EACE;EACA;EACA;;AAEA;EACE;;AAIJ;EACE;EACA;EACA;;AAmBE;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EACE;;AASF;AAAA;AAAA;AAAA;AAAA;AAAA;EAEE;;AAKN;EACE;EACA;EACA,OFnFG;EEoFH;EACA,eFzFG;EE0FH,cF1FG;EE2FH;;AH1JA;EGmJF;IAUI;IACA;;;AAGF;EACE;EACA;EACA;EACA,OL/KO;EKgLP;;AAYF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EACE;;AAIJ;EACE;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAOE;EACA;EACA;;AAEA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAKE;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EACE;;AAIJ;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAWE,YF9JG;;;AG3EP;EACE;EACA;EACA;EACA;;AAEA;EACE;EACA;;ALoBF;EACE;;AClBA;EILF;IL2BE;;;ACtBA;EDOF;IACE;;;ACRA;EILF;ILiBE;;;AKPA;EACE;EACA,YH+DC;EG9DD,aHuDC;EGtDD,gBHsDC;EGrDD;EAEE,eH0DD;EGzDC,cHqDD;;ADlEH;EIKA;IAeI,YHgDD;IG/CC;IAEE,eH6CH;IG5CG,cH4CH;;;AGrCD;EACE,OHkCD;EGjCC,QHiCD;EGhCC;;AAGF;EACE;EACA;;AAGF;EAEE;EACA;;AASJ;EACE;EAEE;EAGF,OHUC;EGTD,QHSC;EGRD;EACA,ONzEO;;AEUT;EIsDA;IAYI,OHED;IGDC,QHCD;IGAC;;;AAGF;EACE;;AAQA;EACE;;AAKN;EACE;EACA,cHvBC;EGwBD;;AAEA;EACE;;AAEA;EACE,OH/EI;;AGkFN;EACE,OHnFI;;AGyFR;EAEI;;AAMJ;EACE;;;AAMR;EACE;EACA;EACA;EACA;EACA;;ALhIA;EACE;;ACEA;EIwHJ;ILtHI;;;ACFA;EIwHJ;IASI;IACA,YHhEG;IGiEH;;EAEA;IACE;;;;AAMJ;EACE;;AAEA;EACE;;AAGE;EACE,ON9JG;;AMiKL;EACE,ONlKG;;;AM2Kb;EACE;EACA;;ALtKA;EACE;;ACEA;EIiKJ;IL/JI;;;AKoKF;EACE;EACA;EACA;EACA;EACA;;AAGF;EACE;EACA;EACA;EACA;;AJlLA;EIiKJ;IAqBI,eHpHG;;;;ADlEH;EI4LJ;IAEI;;;;AAIJ;EACE;EACA,eHnIK;EGoIL;;;AAGF;EACE;;AL5MA;EACE;;ACEA;EIwMJ;ILtMI;;;AK0MF;EACE;;AAGF;EACE;EACA,cHlJG;EGmJH,aHnJG;EGoJH,OHpMU;EGqMV;;AAIA;EACE;;;ACrON;AAAA;EAEE;;ANoEA;AAAA;EACE;EACA,aElEuB;;ADKvB;EKXJ;AAAA;IN4EI;;;;AA5BF;AAAA;AAAA;EACE;;ACtCA;EKJJ;AAAA;AAAA;IN8CI;IACA,aEhDuB;;;;AFgCzB;AAAA;EACE;;AC5BA;EKEJ;AAAA;IN8BI;;;;AMzBJ;AAAA;EAEE;EACA;EACA;;ANdA;AAAA;EACE;;ACEA;EKOJ;AAAA;INLI;;;;AMcJ;EACE;;;ANVA;AAAA;EACE;;ACRA;EKoBJ;AAAA;INRI;;;;AAfF;AAAA;EACE;;ACEA;EKyBJ;AAAA;INvBI;;;;AALF;EACE;;ACEA;EK8BJ;IN5BI;;;;AMgCJ;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;ACvDF;AAAA;EAEE;EACA;EACA,cLoEK;EKnEL,aLmEK;EKlEL,OLiBM;EKhBN;EACA;EACA,kBL6BS;EK5BT;;APLA;AAAA;EACE;;ACEA;EMRJ;AAAA;IPUI;;;;AOKJ;EACE,kBL4BU;;;AKzBZ;EACE,kBLcW;;;AKXb;EACE,kBL4BQ;;;AKzBV;EACE,OLFY;EKGZ,kBLkBW;;;AMlDb;EACE;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA,OTRW;ESSX;EACA;EACA;EACA,kBNiBY;EMhBZ;EACA,eNyEc;EMxEd,YACE;EAEF;;AAEA;EACE;EACA;EACA;;AAGF;EAEE;;AAGF;EAEE;;AAGF;EAIE;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;AAKA;EAEE;EACA;EACA;EACA;EACA;;;AAKN;EACE,OTtEW;ESuEX;EACA;;AAEA;EAIE;EACA;EACA;EACA;;AAGF;EACE;EACA;EACA,YACE;;AAIJ;EAEE;;;AAIJ;ECnGE,OP0BM;EOzBN;EACA;EACA,YACE;;AAGF;EAEE,OPiBI;EOhBJ;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;;ADgFJ;ECvGE,OP0BM;EOzBN;EACA;EACA,YACE;;AAGF;EAEE,OPiBI;EOhBJ;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;;ADoFJ;EC3GE,OP0BM;EOzBN;EACA;EACA,YACE;;AAGF;EAEE,OPiBI;EOhBJ;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;;ADwFJ;EC/GE,OP0BM;EOzBN;EACA;EACA,YACE;;AAGF;EAEE,OPiBI;EOhBJ;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;;AD4FJ;EACE;EACA;EACA;EACA;EACA;EACA;EACA;;;AE3HF;EACE;EACA;EACA;EACA,QRgFM;EQ/EN,SRuEK;EQtEL;;ATME;ESZJ;IASI;IACA;IACA;IACA;IACA;;;;AAIJ;EACE;EACA;EACA,QR8DK;EQ7DL;EACA,eRmEc;EQlEd,YACE;EAEF;;ATdE;ESKJ;IAYI;IACA;IACA,WRwEmB;IQvEnB;IACA;IACA;IACA;;;;AAIJ;EACE;EACA;EACA;EACA;EACA;EACA,ORTY;EQUZ,kBRfY;EQgBZ;EACA;EACA;EACA;EACA;;ATvCE;ES2BJ;IAeI;IACA;IACA,kBRxBU;IQyBV;;;AAGF;EACE;EACA;;AAEA;EACE,OX/DO;;;AWoEb;EACE;EACA;EACA;EACA,cRIK;;ADlEH;ES0DJ;IAOI,cRGG;IQFH;;;AAGF;EACE;EACA;EACA;EACA,ORzDU;;;AQ6Dd;EACE;EACA;EACA;EACA;EACA;EACA;EACA,kBRjEY;EQkEZ,4BRRc;EQSd,2BRTc;EQUd,YACE;;ATxFA;ES6EJ;IAeI;IACA,ORFmB;IQGnB;;;;AAIJ;EACE;EACA,eRrCK;EQsCL;;AVpFA;EACE;;AClBA;ESkGJ;IV5EI;;;ACtBA;EDOF;IACE;;;ACRA;ESkGJ;IVtFI;;;;AUiGJ;EACE;EACA;;;AAGF;EACE;EACA;;AAEA;EAEE,kBX3Ha;;;AW+HjB;EACE;EACA,aR9DK;EQ+DL,gBR/DK;;ADhEH;ES4HJ;IAMI;IACA;IACA,eRpEG;IQqEH;;;;AAIJ;EACE;EACA;EACA;;AAEA;EACE;;AVxIF;EACE;;ACRA;ES8IF;IVlIE;;;ACZA;EDHF;IACE;;;ACEA;ES8IF;IV5IE;;;AUqJF;EACE,ORtFG;EQuFH,QRvFG;EQwFH,cR1FG;EQ2FH,OXrKS;EWsKT;;AAGF;EACE;;;AAIJ;EACE;EACA;;;AAGF;EACE;EACA;EACA;EACA,ORrJY;EQsJZ;EACA;;AV5LA;EACE;;ACYA;ESyKJ;IVjLI;;;;AU2LJ;EACE;EACA,aRrHK;EQsHL,gBRtHK;EQuHL,cRrHK;EQsHL,aRxHK;EQyHL,ORjKY;EQkKZ;EACA,aR/GO;EQgHP,mBR1KY;;AFrBZ;EACE;;ACEA;ESmLJ;IVjLI;;;ACFA;ESmLJ;IAaI;IACA;IACA,cRlIG;IQmIH;IACA;;;;AAIJ;EACE,YR1IK;;;AQ6IP;EACE;;;AAGF;EACE;;AV1MA;EACE;;ACRA;ESgNJ;IVpMI;;;;AUyMJ;EACE;EACA,ORrJK;EQsJL,QRtJK;EQuJL;EACA,ORnJK;EQoJL,QRpJK;EQqJL,kBRzMY;EQ0MZ;EACA;EACA,YACE;EAEF;EACA;;;AAGF;EACE;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA,YACE;;;AAMF;EACE;EACA;EACA;EACA;EACA;EACA;;AAGF;EACE,QRxLI;EQyLJ;;ATjQA;ES+PF;IAKI,ORzKiB;IQ0KjB,YACE;;;AAKN;EACE,kBRzPU;;ADnBV;ES2QF;IAII;;;AT/QF;ESmRF;IAEI;;;AAIJ;EACE;;AAGF;EACE;EACA;EACA;EACA,YACE;;ATlSF;ESwSA;IACE;IACA;IACA;;;AAIJ;EACE,aRxOI;;ADxEJ;ES+SF;IAII;;;;AC9TN;EACE;EACA;EACA;EACA,eT0EK;ESzEL;EACA,eTkFc;ESjFd,YACE;;;AAIJ;EACE;EACA;EACA;;;AAGF;AAAA;EAEE;EACA;EACA,kBTQY;ESPZ;EACA;;AXNA;AAAA;EACE;;ACRA;EUOJ;AAAA;IXKI;;;AWKF;AAAA;EACE;;;AAOE;AAAA;EAEE;;AAGF;EACE,gBTkCD;;;AS3BL;EACE;;;AC9CF;EACE;EACA;EACA,kBbDoB;EaEpB;EACA,eV+EY;;;AU1EhB;EACE,cVcY;;;AUqCd;AAAA;AAAA;EAGE;EACA,eVMK;EULL,kBbjEsB;EakEtB,eVgBc;EUfd;EACA;EACA;EACA;;AAIA;AAAA;AAAA;EACE,OVLG;EUMH;EACA;EACA;EACA;EACA,SVVG;EUWH;EACA;EACA,OVtDU;EUuDV;;AAEA;AAAA;AAAA;EACE,MV1DQ;;AU6DV;AAAA;AAAA;EACE;EACA;EACA;;AAGF;AAAA;AAAA;EACE;EACA;;AAMF;AAAA;AAAA;EACE;EACA;;;AASJ;EACE;EACA,SV/CG;EUgDH;EACA;EACA,eVtCY;;AUyCd;AAAA;EAEE;EACA;EACA;;;AAUJ;EACE;EACA,eVrEK;;AU6CL;EACE;EACA,SV/CG;EUgDH;EACA;EACA,eVtCY;;AUyCd;AAAA;EAEE;EACA;EACA;;;AAwBF;AAAA;EAEE;EACA,SVpFG;EUqFH;EACA;EACA,eV3EY;;;AUmFhB;EACE;EACA;EACA;EACA;;AAEA;AAAA;EAEE;EACA;EACA,kBb/KoB;EagLpB;;AZ9KF;AAAA;EACE;;ACEA;EWsKF;AAAA;IZpKE;;;AY8KF;EACE;EACA,eVjHG;EUkHH,cVlHG;;AUqHL;EACE;EACA;;;AAKJ;AAAA;EAEE,SV9HK;EU+HL,eV/HK;EUgIL;EACA;EACA,eVtHc;;AUwHd;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAIE;EACA;EACA;EACA;EACA;EACA;EACA;;;AAKJ;EACE;EACA;EACA;;;AAIF;AAAA;EAEE,YblOsB;EaqOpB,ObpOoB;;;Aa2OxB;EACE,Yb7OsB;;;AcLxB;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAKF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;ACvOF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAKF;EACE;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;;;AbrBE;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;AAQR;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAKF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AdhHA;EACE;;ACYA;EcZJ;IfII;;;;AAKF;EACE;;ACEA;EcRJ;IfUI;;;;AAKF;EACE;;ACRA;EcJJ;IfgBI;;;;AAKF;EACE;;AClBA;EcAJ;IfsBI;;;;AAKF;EACE;;AC5BA;EcIJ;If4BI;;;;AAKF;EACE;;ACtCA;EcQJ;IfkCI;IACA,aEhDuB;;;;AFqDzB;EACE;EACA,aEvDuB;;ADKvB;EcYJ;If0CI;;;;AAKF;EACE;EACA,aElEuB;;ADKvB;EcgBJ;IfiDI;;;;AAKF;EACE;EACA,aE7EuB;;ADKvB;EcoBJ;IfwDI;;;;AAKF;EACE;EACA,aExFuB;;ADKvB;EcwBJ;If+DI;;;;Ae3DJ;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE,abxDiB;;;Aa2DnB;EACE,ab1DyB;;;Aa6D3B;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AC/EF;EACE;EACA;EACA;;AAGE;EACE;;;ACLN;EACE;EACA;;;AAQA;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AhBlCA;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AAaN;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AhB7GA;EgBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhB/IJ;EgBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhB/IJ;EgBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhB/IJ;EgBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhB/IJ;EgBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AC3JR;EACE;AAAA;AAAA;AAAA;AAAA;AAAA;IAME;;EAGF;IACE;IACA;;EAGF;IACE;IACA;IACA;;EAGF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;;EAGF;IACE;;EAGF;IACE;IACA;;;ACvCJ;EACE;EACA;EACA;EACA;EACA;EACA;EACA;;;AAGF;AAAA;EAEE,OpBXW;EoBYX,kBjBkBY;EiBjBZ;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;;;ACpBF;EACE,kBlByBY;;;AkBtBd;EACI;EACA;EACA,elB4EY;EkB3EZ;EACA;;AAEA;EACI,OlB8BI;EkB7BJ;EACA;EACA;EACA;EACA;EACA;;AAGJ;EACE,OlBoBM;EkBnBN;EACA;EACA;EACA;EACA;;;AAIN;EACI;EACA;EACA,elBiDY;EkBhDZ;EACA;;AACA;EACE;EACA;EACA,OlBEM;EkBDN;EACA;EACA;EACA;EACA;;;AAIN;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAIJ;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAMJ;EACI;EACA;EACA,elBGY;EkBFZ;EACA;;AAEA;EACI,OlB/CG;EkBgDH;EACA;EACA;EACA;EACA;EACA;;AAGJ;EACE,OlBzDK;EkB0DL;EACA;EACA;EACA;EACA;;;AAIN;EACI;EACA;EACA,elBxBY;EkByBZ;EACA;;AACA;EACE;EACA;EACA,OlB3EK;EkB4EL;EACA;EACA;EACA;EACA;;;AAIN;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAIJ;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAMJ;EACI;EACA;EACA,elBtEY;EkBuEZ;EACA;;AAEA;EACI,OlBhHK;EkBiHL;EACA;EACA;EACA;EACA;EACA;;AAGJ;EACE,OlB1HO;EkB2HP;EACA;EACA;EACA;EACA;;;AAIN;EACI;EACA;EACA,elBjGY;EkBkGZ;EACA;;AACA;EACE;EACA;EACA,OlB5IO;EkB6IP;EACA;EACA;EACA;EACA;;;AAIN;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAIJ;EACE;EACA;;AAEA;EACE;;AAGF;EACE","sourcesContent":["/*\ngenerated by accessible-pygments \nCopyright (c) 2022, Quansight Labs\nLicensed under the BSD license, see LICENSE for details.\n--\ngenerated by Pygments \nCopyright 2006-2025 by the Pygments team.\nLicensed under the BSD license, see LICENSE for details.\n*/\n\n.highlight .hll { background-color: #0969da4a }\n.highlight .c { color: #6E7781 } /* Comment */\n.highlight .err { color: #CF222E } /* Error */\n.highlight .k { color: #CF222E } /* Keyword */\n.highlight .l { color: #953800 } /* Literal */\n.highlight .n { color: #8250DF } /* Name */\n.highlight .o { color: #116329 } /* Operator */\n.highlight .p { color: #24292F } /* Punctuation */\n.highlight .ch { color: #6E7781 } /* Comment.Hashbang */\n.highlight .cm { color: #6E7781 } /* Comment.Multiline */\n.highlight .cp { color: #6E7781 } /* Comment.Preproc */\n.highlight .cpf { color: #6E7781 } /* Comment.PreprocFile */\n.highlight .c1 { color: #6E7781 } /* Comment.Single */\n.highlight .cs { color: #6E7781 } /* Comment.Special */\n.highlight .gd { color: #0550AE } /* Generic.Deleted */\n.highlight .ge { font-style: italic } /* Generic.Emph */\n.highlight .gr { color: #CF222E } /* Generic.Error */\n.highlight .gh { color: #0550AE } /* Generic.Heading */\n.highlight .gs { font-weight: bold } /* Generic.Strong */\n.highlight .gu { color: #0550AE } /* Generic.Subheading */\n.highlight .kc { color: #0550AE } /* Keyword.Constant */\n.highlight .kd { color: #CF222E } /* Keyword.Declaration */\n.highlight .kn { color: #CF222E } /* Keyword.Namespace */\n.highlight .kp { color: #CF222E } /* Keyword.Pseudo */\n.highlight .kr { color: #CF222E } /* Keyword.Reserved */\n.highlight .kt { color: #CF222E } /* Keyword.Type */\n.highlight .ld { color: #953800 } /* Literal.Date */\n.highlight .m { color: #953800 } /* Literal.Number */\n.highlight .s { color: #0550AE } /* Literal.String */\n.highlight .na { color: #953800 } /* Name.Attribute */\n.highlight .nb { color: #953800 } /* Name.Builtin */\n.highlight .nc { color: #0550AE } /* Name.Class */\n.highlight .no { color: #0550AE } /* Name.Constant */\n.highlight .nd { color: #953800 } /* Name.Decorator */\n.highlight .ni { color: #116329 } /* Name.Entity */\n.highlight .ne { color: #8250DF } /* Name.Exception */\n.highlight .nf { color: #0550AE } /* Name.Function */\n.highlight .nl { color: #953800 } /* Name.Label */\n.highlight .nn { color: #24292F } /* Name.Namespace */\n.highlight .nx { color: #8250DF } /* Name.Other */\n.highlight .py { color: #0550AE } /* Name.Property */\n.highlight .nt { color: #116329 } /* Name.Tag */\n.highlight .nv { color: #953800 } /* Name.Variable */\n.highlight .ow { color: #8250DF } /* Operator.Word */\n.highlight .pm { color: #24292F } /* Punctuation.Marker */\n.highlight .w { color: #24292F } /* Text.Whitespace */\n.highlight .mb { color: #953800 } /* Literal.Number.Bin */\n.highlight .mf { color: #953800 } /* Literal.Number.Float */\n.highlight .mh { color: #953800 } /* Literal.Number.Hex */\n.highlight .mi { color: #953800 } /* Literal.Number.Integer */\n.highlight .mo { color: #953800 } /* Literal.Number.Oct */\n.highlight .sa { color: #0550AE } /* Literal.String.Affix */\n.highlight .sb { color: #0550AE } /* Literal.String.Backtick */\n.highlight .sc { color: #0550AE } /* Literal.String.Char */\n.highlight .dl { color: #0550AE } /* Literal.String.Delimiter */\n.highlight .sd { color: #0550AE } /* Literal.String.Doc */\n.highlight .s2 { color: #0550AE } /* Literal.String.Double */\n.highlight .se { color: #0550AE } /* Literal.String.Escape */\n.highlight .sh { color: #0550AE } /* Literal.String.Heredoc */\n.highlight .si { color: #0550AE } /* Literal.String.Interpol */\n.highlight .sx { color: #0550AE } /* Literal.String.Other */\n.highlight .sr { color: #0550AE } /* Literal.String.Regex */\n.highlight .s1 { color: #0550AE } /* Literal.String.Single */\n.highlight .ss { color: #0550AE } /* Literal.String.Symbol */\n.highlight .bp { color: #953800 } /* Name.Builtin.Pseudo */\n.highlight .fm { color: #0550AE } /* Name.Function.Magic */\n.highlight .vc { color: #953800 } /* Name.Variable.Class */\n.highlight .vg { color: #953800 } /* Name.Variable.Global */\n.highlight .vi { color: #953800 } /* Name.Variable.Instance */\n.highlight .vm { color: #953800 } /* Name.Variable.Magic */\n.highlight .il { color: #953800 } /* Literal.Number.Integer.Long */\n","/*\ngenerated by accessible-pygments \nCopyright (c) 2022, Quansight Labs\nLicensed under the BSD license, see LICENSE for details.\n--\ngenerated by Pygments \nCopyright 2006-2025 by the Pygments team.\nLicensed under the BSD license, see LICENSE for details.\n*/\n\n.highlight .hll { background-color: #6e7681 }\n.highlight { background: #0d1117; color: #E6EDF3 }\n.highlight .c { color: #8B949E; font-style: italic } /* Comment */\n.highlight .err { color: #F85149 } /* Error */\n.highlight .esc { color: #E6EDF3 } /* Escape */\n.highlight .g { color: #E6EDF3 } /* Generic */\n.highlight .k { color: #FF7B72 } /* Keyword */\n.highlight .l { color: #A5D6FF } /* Literal */\n.highlight .n { color: #E6EDF3 } /* Name */\n.highlight .o { color: #FF7B72; font-weight: bold } /* Operator */\n.highlight .x { color: #E6EDF3 } /* Other */\n.highlight .p { color: #E6EDF3 } /* Punctuation */\n.highlight .ch { color: #8B949E; font-style: italic } /* Comment.Hashbang */\n.highlight .cm { color: #8B949E; font-style: italic } /* Comment.Multiline */\n.highlight .cp { color: #8B949E; font-weight: bold; font-style: italic } /* Comment.Preproc */\n.highlight .cpf { color: #8B949E; font-style: italic } /* Comment.PreprocFile */\n.highlight .c1 { color: #8B949E; font-style: italic } /* Comment.Single */\n.highlight .cs { color: #8B949E; font-weight: bold; font-style: italic } /* Comment.Special */\n.highlight .gd { color: #FFA198; background-color: #490202 } /* Generic.Deleted */\n.highlight .ge { color: #E6EDF3; font-style: italic } /* Generic.Emph */\n.highlight .ges { color: #E6EDF3; font-weight: bold; font-style: italic } /* Generic.EmphStrong */\n.highlight .gr { color: #FFA198 } /* Generic.Error */\n.highlight .gh { color: #79C0FF; font-weight: bold } /* Generic.Heading */\n.highlight .gi { color: #56D364; background-color: #0F5323 } /* Generic.Inserted */\n.highlight .go { color: #8B949E } /* Generic.Output */\n.highlight .gp { color: #8B949E } /* Generic.Prompt */\n.highlight .gs { color: #E6EDF3; font-weight: bold } /* Generic.Strong */\n.highlight .gu { color: #79C0FF } /* Generic.Subheading */\n.highlight .gt { color: #FF7B72 } /* Generic.Traceback */\n.highlight .g-Underline { color: #E6EDF3; text-decoration: underline } /* Generic.Underline */\n.highlight .kc { color: #79C0FF } /* Keyword.Constant */\n.highlight .kd { color: #FF7B72 } /* Keyword.Declaration */\n.highlight .kn { color: #FF7B72 } /* Keyword.Namespace */\n.highlight .kp { color: #79C0FF } /* Keyword.Pseudo */\n.highlight .kr { color: #FF7B72 } /* Keyword.Reserved */\n.highlight .kt { color: #FF7B72 } /* Keyword.Type */\n.highlight .ld { color: #79C0FF } /* Literal.Date */\n.highlight .m { color: #A5D6FF } /* Literal.Number */\n.highlight .s { color: #A5D6FF } /* Literal.String */\n.highlight .na { color: #E6EDF3 } /* Name.Attribute */\n.highlight .nb { color: #E6EDF3 } /* Name.Builtin */\n.highlight .nc { color: #F0883E; font-weight: bold } /* Name.Class */\n.highlight .no { color: #79C0FF; font-weight: bold } /* Name.Constant */\n.highlight .nd { color: #D2A8FF; font-weight: bold } /* Name.Decorator */\n.highlight .ni { color: #FFA657 } /* Name.Entity */\n.highlight .ne { color: #F0883E; font-weight: bold } /* Name.Exception */\n.highlight .nf { color: #D2A8FF; font-weight: bold } /* Name.Function */\n.highlight .nl { color: #79C0FF; font-weight: bold } /* Name.Label */\n.highlight .nn { color: #FF7B72 } /* Name.Namespace */\n.highlight .nx { color: #E6EDF3 } /* Name.Other */\n.highlight .py { color: #79C0FF } /* Name.Property */\n.highlight .nt { color: #7EE787 } /* Name.Tag */\n.highlight .nv { color: #79C0FF } /* Name.Variable */\n.highlight .ow { color: #FF7B72; font-weight: bold } /* Operator.Word */\n.highlight .pm { color: #E6EDF3 } /* Punctuation.Marker */\n.highlight .w { color: #6E7681 } /* Text.Whitespace */\n.highlight .mb { color: #A5D6FF } /* Literal.Number.Bin */\n.highlight .mf { color: #A5D6FF } /* Literal.Number.Float */\n.highlight .mh { color: #A5D6FF } /* Literal.Number.Hex */\n.highlight .mi { color: #A5D6FF } /* Literal.Number.Integer */\n.highlight .mo { color: #A5D6FF } /* Literal.Number.Oct */\n.highlight .sa { color: #79C0FF } /* Literal.String.Affix */\n.highlight .sb { color: #A5D6FF } /* Literal.String.Backtick */\n.highlight .sc { color: #A5D6FF } /* Literal.String.Char */\n.highlight .dl { color: #79C0FF } /* Literal.String.Delimiter */\n.highlight .sd { color: #A5D6FF } /* Literal.String.Doc */\n.highlight .s2 { color: #A5D6FF } /* Literal.String.Double */\n.highlight .se { color: #79C0FF } /* Literal.String.Escape */\n.highlight .sh { color: #79C0FF } /* Literal.String.Heredoc */\n.highlight .si { color: #A5D6FF } /* Literal.String.Interpol */\n.highlight .sx { color: #A5D6FF } /* Literal.String.Other */\n.highlight .sr { color: #79C0FF } /* Literal.String.Regex */\n.highlight .s1 { color: #A5D6FF } /* Literal.String.Single */\n.highlight .ss { color: #A5D6FF } /* Literal.String.Symbol */\n.highlight .bp { color: #E6EDF3 } /* Name.Builtin.Pseudo */\n.highlight .fm { color: #D2A8FF; font-weight: bold } /* Name.Function.Magic */\n.highlight .vc { color: #79C0FF } /* Name.Variable.Class */\n.highlight .vg { color: #79C0FF } /* Name.Variable.Global */\n.highlight .vi { color: #79C0FF } /* Name.Variable.Instance */\n.highlight .vm { color: #79C0FF } /* Name.Variable.Magic */\n.highlight .il { color: #A5D6FF } /* Literal.Number.Integer.Long */\n","/*! normalize.css v8.0.1 | MIT License | github.com/necolas/normalize.css */\n\n/* Document\n ========================================================================== */\n\n/**\n * 1. Correct the line height in all browsers.\n * 2. Prevent adjustments of font size after orientation changes in iOS.\n */\n\nhtml {\n line-height: 1.15; /* 1 */\n text-size-adjust: 100%; /* 2 */\n}\n\n/* Sections\n ========================================================================== */\n\n/**\n * Remove the margin in all browsers.\n */\n\nbody {\n margin: 0;\n}\n\n/**\n * Render the `main` element consistently in IE.\n */\n\nmain {\n display: block;\n}\n\n/**\n * Correct the font size and margin on `h1` elements within `section` and\n * `article` contexts in Chrome, Firefox, and Safari.\n */\n\nh1 {\n font-size: 2em;\n margin: 0.67em 0;\n}\n\n/* Grouping content\n ========================================================================== */\n\n/**\n * 1. Add the correct box sizing in Firefox.\n * 2. Show the overflow in Edge and IE.\n */\n\nhr {\n box-sizing: content-box; /* 1 */\n height: 0; /* 1 */\n overflow: visible; /* 2 */\n}\n\n/**\n * 1. Correct the inheritance and scaling of font size in all browsers.\n * 2. Correct the odd `em` font sizing in all browsers.\n */\n\npre {\n font-family: monospace; /* 1 */\n font-size: 1em; /* 2 */\n}\n\n/* Text-level semantics\n ========================================================================== */\n\n/**\n * Remove the gray background on active links in IE 10.\n */\n\na {\n background-color: transparent;\n}\n\n/**\n * 1. Remove the bottom border in Chrome 57-\n * 2. Add the correct text decoration in Chrome, Edge, IE, Opera, and Safari.\n */\n\nabbr[title] {\n border-bottom: none; /* 1 */\n text-decoration: underline; /* 2 */\n text-decoration: underline dotted; /* 2 */\n}\n\n/**\n * Add the correct font weight in Chrome, Edge, and Safari.\n */\n\nb,\nstrong {\n font-weight: bolder;\n}\n\n/**\n * 1. Correct the inheritance and scaling of font size in all browsers.\n * 2. Correct the odd `em` font sizing in all browsers.\n */\n\ncode,\nkbd,\nsamp {\n font-family: monospace; /* 1 */\n font-size: 1em; /* 2 */\n}\n\n/**\n * Add the correct font size in all browsers.\n */\n\nsmall {\n font-size: 80%;\n}\n\n/**\n * Prevent `sub` and `sup` elements from affecting the line height in\n * all browsers.\n */\n\nsub,\nsup {\n font-size: 75%;\n line-height: 0;\n position: relative;\n vertical-align: baseline;\n}\n\nsub {\n bottom: -0.25em;\n}\n\nsup {\n top: -0.5em;\n}\n\n/* Embedded content\n ========================================================================== */\n\n/**\n * Remove the border on images inside links in IE 10.\n */\n\nimg {\n border-style: none;\n}\n\n/* Forms\n ========================================================================== */\n\n/**\n * 1. Change the font styles in all browsers.\n * 2. Remove the margin in Firefox and Safari.\n */\n\nbutton,\ninput,\noptgroup,\nselect,\ntextarea {\n font-family: inherit; /* 1 */\n font-size: 100%; /* 1 */\n line-height: 1.15; /* 1 */\n margin: 0; /* 2 */\n}\n\n/**\n * Show the overflow in IE.\n * 1. Show the overflow in Edge.\n */\n\nbutton,\ninput {\n /* 1 */\n overflow: visible;\n}\n\n/**\n * Remove the inheritance of text transform in Edge, Firefox, and IE.\n * 1. Remove the inheritance of text transform in Firefox.\n */\n\nbutton,\nselect {\n /* 1 */\n text-transform: none;\n}\n\n/**\n * Correct the inability to style clickable types in iOS and Safari.\n */\n\nbutton,\n[type=\"button\"],\n[type=\"reset\"],\n[type=\"submit\"] {\n appearance: button;\n}\n\n/**\n * Remove the inner border and padding in Firefox.\n */\n\nbutton::-moz-focus-inner,\n[type=\"button\"]::-moz-focus-inner,\n[type=\"reset\"]::-moz-focus-inner,\n[type=\"submit\"]::-moz-focus-inner {\n border-style: none;\n padding: 0;\n}\n\n/**\n * Restore the focus styles unset by the previous rule.\n */\n\nbutton:-moz-focusring,\n[type=\"button\"]:-moz-focusring,\n[type=\"reset\"]:-moz-focusring,\n[type=\"submit\"]:-moz-focusring {\n outline: 1px dotted ButtonText;\n}\n\n/**\n * Correct the padding in Firefox.\n */\n\nfieldset {\n padding: 0.35em 0.75em 0.625em;\n}\n\n/**\n * 1. Correct the text wrapping in Edge and IE.\n * 2. Correct the color inheritance from `fieldset` elements in IE.\n * 3. Remove the padding so developers are not caught out when they zero out\n * `fieldset` elements in all browsers.\n */\n\nlegend {\n box-sizing: border-box; /* 1 */\n color: inherit; /* 2 */\n display: table; /* 1 */\n max-width: 100%; /* 1 */\n padding: 0; /* 3 */\n white-space: normal; /* 1 */\n}\n\n/**\n * Add the correct vertical alignment in Chrome, Firefox, and Opera.\n */\n\nprogress {\n vertical-align: baseline;\n}\n\n/**\n * Remove the default vertical scrollbar in IE 10+.\n */\n\ntextarea {\n overflow: auto;\n}\n\n/**\n * 1. Add the correct box sizing in IE 10.\n * 2. Remove the padding in IE 10.\n */\n\n[type=\"checkbox\"],\n[type=\"radio\"] {\n box-sizing: border-box; /* 1 */\n padding: 0; /* 2 */\n}\n\n/**\n * Correct the cursor style of increment and decrement buttons in Chrome.\n */\n\n[type=\"number\"]::-webkit-inner-spin-button,\n[type=\"number\"]::-webkit-outer-spin-button {\n height: auto;\n}\n\n/**\n * 1. Correct the odd appearance in Chrome and Safari.\n * 2. Correct the outline style in Safari.\n */\n\n[type=\"search\"] {\n appearance: textfield; /* 1 */\n outline-offset: -2px; /* 2 */\n}\n\n/**\n * Remove the inner padding in Chrome and Safari on macOS.\n */\n\n[type=\"search\"]::-webkit-search-decoration {\n appearance: none;\n}\n\n/**\n * 1. Correct the inability to style clickable types in iOS and Safari.\n * 2. Change font properties to `inherit` in Safari.\n */\n\n::-webkit-file-upload-button {\n appearance: button; /* 1 */\n font: inherit; /* 2 */\n}\n\n/* Interactive\n ========================================================================== */\n\n/*\n * Add the correct display in Edge, IE 10+, and Firefox.\n */\n\ndetails {\n display: block;\n}\n\n/*\n * Add the correct display in all browsers.\n */\n\nsummary {\n display: list-item;\n}\n\n/* Misc\n ========================================================================== */\n\n/**\n * Add the correct display in IE 10+.\n */\n\ntemplate {\n display: none;\n}\n\n/**\n * Add the correct display in IE 10.\n */\n\n[hidden] {\n display: none;\n}\n","// Base element style overrides\n// stylelint-disable selector-no-type, selector-max-type, selector-max-specificity, selector-max-id\n\n:root {\n color-scheme: $color-scheme;\n}\n\n* {\n box-sizing: border-box;\n}\n\nhtml {\n scroll-behavior: smooth;\n\n @include fs-4;\n}\n\nbody {\n font-family: $body-font-family;\n font-size: inherit;\n line-height: $body-line-height;\n color: $body-text-color;\n background-color: $body-background-color;\n overflow-wrap: break-word;\n}\n\nol,\nul,\ndl,\npre,\naddress,\nblockquote,\ntable,\ndiv,\nhr,\nform,\nfieldset,\nnoscript .table-wrapper {\n margin-top: 0;\n}\n\nh1,\nh2,\nh3,\nh4,\nh5,\nh6,\n#toctitle {\n margin-top: 0;\n margin-bottom: 1em;\n font-weight: 500;\n line-height: $body-heading-line-height;\n color: $body-heading-color;\n}\n\np {\n margin-top: 1em;\n margin-bottom: 1em;\n}\n\na {\n color: $link-color;\n text-decoration: none;\n}\n\na:not([class]) {\n text-decoration: underline;\n text-decoration-color: $border-color;\n text-underline-offset: 2px;\n\n &:hover {\n text-decoration-color: rgba($link-color, 0.45);\n }\n}\n\ncode {\n font-family: $mono-font-family;\n font-size: 0.75em;\n line-height: $body-line-height;\n}\n\nfigure,\npre {\n margin: 0;\n}\n\nli {\n margin: 0.25em 0;\n}\n\nimg {\n max-width: 100%;\n height: auto;\n}\n\nhr {\n height: 1px;\n padding: 0;\n margin: $sp-6 0;\n background-color: $border-color;\n border: 0;\n}\n\n// adds a GitHub-style sidebar to blockquotes\nblockquote {\n margin: 10px 0;\n\n // resets user-agent stylesheets for blockquotes\n margin-block-start: 0;\n margin-inline-start: 0;\n padding-left: 1rem;\n border-left: 3px solid $border-color;\n}\n","$color-scheme: dark;\n$body-background-color: $grey-dk-300;\n$body-heading-color: $grey-lt-000;\n$body-text-color: $grey-lt-300;\n$link-color: lighten($blue-000, 10%);\n$nav-child-link-color: $grey-dk-000;\n$sidebar-color: $grey-dk-300;\n$base-button-color: $grey-dk-250;\n$btn-primary-color: $blue-200;\n$code-background-color: #0d1117; // github-dark bg color\n$code-linenumber-color: #e6edf3; // github-dark line number color\n$feedback-color: darken($sidebar-color, 3%);\n$table-background-color: $grey-dk-250;\n$search-background-color: $grey-dk-250;\n$search-result-preview-color: $grey-lt-300;\n$border-color: $grey-dk-200;\n\n@import \"./vendor/accessible-pygments/github-dark\";\n","@mixin fs-1 {\n & {\n font-size: $font-size-1 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-1-sm !important;\n }\n}\n\n@mixin fs-2 {\n & {\n font-size: $font-size-2 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-3 !important;\n }\n}\n\n@mixin fs-3 {\n & {\n font-size: $font-size-3 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-4 !important;\n }\n}\n\n@mixin fs-4 {\n & {\n font-size: $font-size-4 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-5 !important;\n }\n}\n\n@mixin fs-5 {\n & {\n font-size: $font-size-5 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-6 !important;\n }\n}\n\n@mixin fs-6 {\n & {\n font-size: $font-size-6 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-7 !important;\n line-height: $body-heading-line-height;\n }\n}\n\n@mixin fs-7 {\n & {\n font-size: $font-size-7 !important;\n line-height: $body-heading-line-height;\n }\n\n @include mq(sm) {\n font-size: $font-size-8 !important;\n }\n}\n\n@mixin fs-8 {\n & {\n font-size: $font-size-8 !important;\n line-height: $body-heading-line-height;\n }\n\n @include mq(sm) {\n font-size: $font-size-9 !important;\n }\n}\n\n@mixin fs-9 {\n & {\n font-size: $font-size-9 !important;\n line-height: $body-heading-line-height;\n }\n\n @include mq(sm) {\n font-size: $font-size-10 !important;\n }\n}\n\n@mixin fs-10 {\n & {\n font-size: $font-size-10 !important;\n line-height: $body-heading-line-height;\n }\n\n @include mq(sm) {\n font-size: $font-size-10-sm !important;\n }\n}\n","// Media query\n\n// Media query mixin\n// Usage:\n// @include mq(md) {\n// ..medium and up styles\n// }\n@mixin mq($name) {\n // Retrieves the value from the key\n $value: map-get($media-queries, $name);\n\n // If the key exists in the map\n @if $value {\n // Prints a media query based on the value\n @media (min-width: $value) {\n @content;\n }\n } @else {\n @warn \"No value could be retrieved from `#{$media-query}`. Please make sure it is defined in `$media-queries` map.\";\n }\n}\n\n// Responsive container\n\n@mixin container {\n padding-right: $gutter-spacing-sm;\n padding-left: $gutter-spacing-sm;\n\n @include mq(md) {\n padding-right: $gutter-spacing;\n padding-left: $gutter-spacing;\n }\n}\n","// Typography\n\n// prettier-ignore\n$body-font-family: system-ui, -apple-system, blinkmacsystemfont, \"Segoe UI\",\n roboto, \"Helvetica Neue\", arial, sans-serif, \"Segoe UI Emoji\" !default;\n$mono-font-family: \"SFMono-Regular\", menlo, consolas, monospace !default;\n$root-font-size: 16px !default; // DEPRECATED: previously base font-size for rems\n$body-line-height: 1.4 !default;\n$content-line-height: 1.6 !default;\n$body-heading-line-height: 1.25 !default;\n\n// Font size\n// `-sm` suffix is the size at the small (and above) media query\n\n$font-size-1: 0.5625rem !default;\n$font-size-1-sm: 0.625rem !default;\n$font-size-2: 0.6875rem !default; // h4 - uppercased!, h6 not uppercased, text-small\n$font-size-3: 0.75rem !default; // h5\n$font-size-4: 0.875rem !default;\n$font-size-5: 1rem !default; // h3\n$font-size-6: 1.125rem !default; // h2\n$font-size-7: 1.5rem !default;\n$font-size-8: 2rem !default; // h1\n$font-size-9: 2.25rem !default;\n$font-size-10: 2.625rem !default;\n$font-size-10-sm: 3rem !default;\n\n// Colors\n\n$white: #fff !default;\n$grey-dk-000: #959396 !default;\n$grey-dk-100: #5c5962 !default;\n$grey-dk-200: #44434d !default;\n$grey-dk-250: #302d36 !default;\n$grey-dk-300: #27262b !default;\n$grey-lt-000: #f5f6fa !default;\n$grey-lt-100: #eeebee !default;\n$grey-lt-200: #ecebed !default;\n$grey-lt-300: #e6e1e8 !default;\n$purple-000: #7253ed !default;\n$purple-100: #5e41d0 !default;\n$purple-200: #4e26af !default;\n$purple-300: #381885 !default;\n$blue-000: #2c84fa !default;\n$blue-100: #2869e6 !default;\n$blue-200: #264caf !default;\n$blue-300: #183385 !default;\n$green-000: #41d693 !default;\n$green-100: #11b584 !default;\n$green-200: #009c7b !default;\n$green-300: #026e57 !default;\n$yellow-000: #ffeb82 !default;\n$yellow-100: #fadf50 !default;\n$yellow-200: #f7d12e !default;\n$yellow-300: #e7af06 !default;\n$red-000: #f77e7e !default;\n$red-100: #f96e65 !default;\n$red-200: #e94c4c !default;\n$red-300: #dd2e2e !default;\n\n// Spacing\n\n$spacing-unit: 1rem; // 1rem == 16px\n\n$spacers: (\n sp-0: 0,\n sp-1: $spacing-unit * 0.25,\n sp-2: $spacing-unit * 0.5,\n sp-3: $spacing-unit * 0.75,\n sp-4: $spacing-unit,\n sp-5: $spacing-unit * 1.5,\n sp-6: $spacing-unit * 2,\n sp-7: $spacing-unit * 2.5,\n sp-8: $spacing-unit * 3,\n sp-9: $spacing-unit * 3.5,\n sp-10: $spacing-unit * 4,\n) !default;\n$sp-1: map-get($spacers, sp-1) !default; // 0.25 rem == 4px\n$sp-2: map-get($spacers, sp-2) !default; // 0.5 rem == 8px\n$sp-3: map-get($spacers, sp-3) !default; // 0.75 rem == 12px\n$sp-4: map-get($spacers, sp-4) !default; // 1 rem == 16px\n$sp-5: map-get($spacers, sp-5) !default; // 1.5 rem == 24px\n$sp-6: map-get($spacers, sp-6) !default; // 2 rem == 32px\n$sp-7: map-get($spacers, sp-7) !default; // 2.5 rem == 40px\n$sp-8: map-get($spacers, sp-8) !default; // 3 rem == 48px\n$sp-9: map-get($spacers, sp-9) !default; // 3.5 rem == 56px\n$sp-10: map-get($spacers, sp-10) !default; // 4 rem == 64px\n\n// Borders\n\n$border: 1px solid !default;\n$border-radius: 4px !default;\n$border-color: $grey-lt-100 !default;\n\n// Grid system\n\n$gutter-spacing: $sp-6 !default;\n$gutter-spacing-sm: $sp-4 !default;\n$nav-width: 16.5rem !default;\n$nav-width-md: 15.5rem !default;\n$nav-list-item-height: $sp-6 !default;\n$nav-list-item-height-sm: $sp-8 !default;\n$nav-list-expander-right: true;\n$content-width: 50rem !default;\n$header-height: 3.75rem !default;\n$search-results-width: $content-width - $nav-width !default;\n$transition-duration: 400ms;\n\n// Media queries in pixels\n\n$media-queries: (\n xs: 20rem,\n sm: 31.25rem,\n md: $content-width,\n lg: $content-width + $nav-width,\n xl: 87.5rem,\n) !default;\n","// The basic two column layout\n\n.side-bar {\n z-index: 0;\n display: flex;\n flex-wrap: wrap;\n background-color: $sidebar-color;\n\n @include mq(md) {\n flex-flow: column nowrap;\n position: fixed;\n width: $nav-width-md;\n height: 100%;\n border-right: $border $border-color;\n align-items: flex-end;\n }\n\n @include mq(lg) {\n width: calc((100% - #{$nav-width + $content-width}) / 2 + #{$nav-width});\n min-width: $nav-width;\n }\n\n & + .main {\n @include mq(md) {\n margin-left: $nav-width-md;\n }\n\n @include mq(lg) {\n // stylelint-disable function-name-case\n // disable for Max(), we want to use the CSS max() function\n margin-left: Max(\n #{$nav-width},\n calc((100% - #{$nav-width + $content-width}) / 2 + #{$nav-width})\n );\n // stylelint-enable function-name-case\n }\n\n .main-header {\n display: none;\n background-color: $sidebar-color;\n\n @include mq(md) {\n display: flex;\n background-color: $body-background-color;\n }\n\n &.nav-open {\n display: block;\n\n @include mq(md) {\n display: flex;\n }\n }\n }\n }\n}\n\n.main {\n margin: auto;\n\n @include mq(md) {\n position: relative;\n max-width: $content-width;\n }\n}\n\n.main-content-wrap {\n padding-top: $gutter-spacing-sm;\n padding-bottom: $gutter-spacing-sm;\n\n @include container;\n\n @include mq(md) {\n padding-top: $gutter-spacing;\n padding-bottom: $gutter-spacing;\n }\n}\n\n.main-header {\n z-index: 0;\n border-bottom: $border $border-color;\n\n @include mq(md) {\n display: flex;\n justify-content: space-between;\n height: $header-height;\n }\n}\n\n.site-nav,\n.site-header,\n.site-footer {\n width: 100%;\n\n @include mq(lg) {\n width: $nav-width;\n }\n}\n\n.site-nav {\n display: none;\n\n &.nav-open {\n display: block;\n }\n\n @include mq(md) {\n display: block;\n padding-top: $sp-8;\n padding-bottom: $gutter-spacing-sm;\n overflow-y: auto;\n flex: 1 1 auto;\n }\n}\n\n.site-header {\n display: flex;\n min-height: $header-height;\n align-items: center;\n\n @include mq(md) {\n height: $header-height;\n max-height: $header-height;\n border-bottom: $border $border-color;\n }\n}\n\n.site-title {\n flex-grow: 1;\n display: flex;\n height: 100%;\n align-items: center;\n padding-top: $sp-3;\n padding-bottom: $sp-3;\n color: $body-heading-color;\n\n @include container;\n\n @include fs-6;\n\n @include mq(md) {\n padding-top: $sp-2;\n padding-bottom: $sp-2;\n }\n}\n\n@if variable-exists(logo) {\n .site-logo {\n width: 100%;\n height: 100%;\n background-image: url($logo);\n background-repeat: no-repeat;\n background-position: left center;\n background-size: contain;\n }\n}\n\n.site-button {\n display: flex;\n height: 100%;\n padding: $gutter-spacing-sm;\n align-items: center;\n}\n\n@include mq(md) {\n .site-header .site-button {\n display: none;\n }\n}\n\n.site-title:hover {\n background-image: linear-gradient(\n -90deg,\n rgba($feedback-color, 1) 0%,\n rgba($feedback-color, 0.8) 80%,\n rgba($feedback-color, 0) 100%\n );\n}\n\n.site-button:hover {\n background-image: linear-gradient(\n -90deg,\n rgba($feedback-color, 1) 0%,\n rgba($feedback-color, 0.8) 100%\n );\n}\n\n.site-footer {\n position: absolute;\n bottom: 0;\n left: 0;\n padding-top: $sp-4;\n padding-bottom: $sp-4;\n\n @include container;\n\n @include fs-2;\n\n @include mq(md) {\n position: static;\n justify-self: end;\n }\n}\n\n.icon {\n width: $sp-5;\n height: $sp-5;\n color: $link-color;\n}\n","@charset \"UTF-8\";\n\n// Styles for rendered markdown in the .main-content container\n// stylelint-disable selector-no-type, max-nesting-depth, selector-max-compound-selectors, selector-max-type, selector-max-specificity, selector-max-id\n\n.main-content {\n line-height: $content-line-height;\n\n ol,\n ul,\n dl,\n pre,\n address,\n blockquote,\n .table-wrapper {\n margin-top: 0.5em;\n }\n\n a {\n overflow: hidden;\n text-overflow: ellipsis;\n }\n\n ul,\n ol {\n padding-left: 1.5em;\n }\n\n li {\n .highlight {\n margin-top: $sp-1;\n }\n }\n\n ol {\n list-style-type: none;\n counter-reset: step-counter;\n\n > li {\n position: relative;\n\n &::before {\n position: absolute;\n top: 0.2em;\n left: -1.6em;\n color: $grey-dk-000;\n content: counter(step-counter);\n counter-increment: step-counter;\n @include fs-3;\n\n @include mq(sm) {\n top: 0.11em;\n }\n }\n\n ol {\n counter-reset: sub-counter;\n\n > li {\n &::before {\n content: counter(sub-counter, lower-alpha);\n counter-increment: sub-counter;\n }\n }\n }\n }\n }\n\n ul {\n list-style: none;\n\n > li {\n &::before {\n position: absolute;\n margin-left: -1.4em;\n color: $grey-dk-000;\n content: \"•\";\n }\n }\n }\n\n .task-list-item {\n &::before {\n content: \"\";\n }\n }\n\n .task-list-item-checkbox {\n margin-right: 0.6em;\n margin-left: -1.4em;\n\n // The same margin-left is used above for ul > li::before\n }\n\n hr + * {\n margin-top: 0;\n }\n\n h1:first-of-type {\n margin-top: 0.5em;\n }\n\n dl {\n display: grid;\n grid-template: auto / 10em 1fr;\n }\n\n dt,\n dd {\n margin: 0.25em 0;\n }\n\n dt {\n grid-column: 1;\n font-weight: 500;\n text-align: right;\n\n &::after {\n content: \":\";\n }\n }\n\n dd {\n grid-column: 2;\n margin-bottom: 0;\n margin-left: 1em;\n\n blockquote,\n div,\n dl,\n dt,\n h1,\n h2,\n h3,\n h4,\n h5,\n h6,\n li,\n ol,\n p,\n pre,\n table,\n ul,\n .table-wrapper {\n &:first-child {\n margin-top: 0;\n }\n }\n }\n\n dd,\n ol,\n ul {\n dl:first-child {\n dt:first-child,\n dd:nth-child(2) {\n margin-top: 0;\n }\n }\n }\n\n .anchor-heading {\n position: absolute;\n right: -$sp-4;\n width: $sp-5;\n height: 100%;\n padding-right: $sp-1;\n padding-left: $sp-1;\n overflow: visible;\n\n @include mq(md) {\n right: auto;\n left: -$sp-5;\n }\n\n svg {\n display: inline-block;\n width: 100%;\n height: 100%;\n color: $link-color;\n visibility: hidden;\n }\n }\n\n .anchor-heading:hover,\n .anchor-heading:focus,\n h1:hover > .anchor-heading,\n h2:hover > .anchor-heading,\n h3:hover > .anchor-heading,\n h4:hover > .anchor-heading,\n h5:hover > .anchor-heading,\n h6:hover > .anchor-heading {\n svg {\n visibility: visible;\n }\n }\n\n summary {\n cursor: pointer;\n }\n\n h1,\n h2,\n h3,\n h4,\n h5,\n h6,\n #toctitle {\n position: relative;\n margin-top: 1.5em;\n margin-bottom: 0.25em;\n\n + table,\n + .table-wrapper,\n + .code-example,\n + .highlighter-rouge,\n + .sectionbody .listingblock {\n margin-top: 1em;\n }\n\n + p:not(.label) {\n margin-top: 0;\n }\n }\n\n > h1:first-child,\n > h2:first-child,\n > h3:first-child,\n > h4:first-child,\n > h5:first-child,\n > h6:first-child,\n > .sect1:first-child > h2,\n > .sect2:first-child > h3,\n > .sect3:first-child > h4,\n > .sect4:first-child > h5,\n > .sect5:first-child > h6 {\n margin-top: $sp-2;\n }\n}\n","// Main nav, breadcrumb, etc...\n// stylelint-disable selector-no-type, max-nesting-depth, selector-max-compound-selectors, selector-max-type, selector-max-specificity\n\n.nav-list {\n padding: 0;\n margin-top: 0;\n margin-bottom: 0;\n list-style: none;\n\n .nav-list-item {\n position: relative;\n margin: 0;\n\n @include fs-4;\n\n @include mq(md) {\n @include fs-3;\n }\n\n .nav-list-link {\n display: block;\n min-height: $nav-list-item-height-sm;\n padding-top: $sp-1;\n padding-bottom: $sp-1;\n line-height: #{$nav-list-item-height-sm - 2 * $sp-1};\n @if $nav-list-expander-right {\n padding-right: $nav-list-item-height-sm;\n padding-left: $gutter-spacing-sm;\n } @else {\n padding-right: $gutter-spacing-sm;\n padding-left: $nav-list-item-height-sm;\n }\n\n @include mq(md) {\n min-height: $nav-list-item-height;\n line-height: #{$nav-list-item-height - 2 * $sp-1};\n @if $nav-list-expander-right {\n padding-right: $nav-list-item-height;\n padding-left: $gutter-spacing;\n } @else {\n padding-right: $gutter-spacing;\n padding-left: $nav-list-item-height;\n }\n }\n\n &.external > svg {\n width: $sp-4;\n height: $sp-4;\n vertical-align: text-bottom;\n }\n\n &.active {\n font-weight: 600;\n text-decoration: none;\n }\n\n &:hover,\n &.active {\n color: darken($link-color, 5%);\n background-image: linear-gradient(\n -90deg,\n rgba($feedback-color, 1) 0%,\n rgba($feedback-color, 0.8) 80%,\n rgba($feedback-color, 0) 100%\n );\n }\n }\n\n .nav-list-expander {\n position: absolute;\n @if $nav-list-expander-right {\n right: 0;\n }\n\n width: $nav-list-item-height-sm;\n height: $nav-list-item-height-sm;\n padding: #{$nav-list-item-height-sm * 0.25};\n color: $link-color;\n\n @include mq(md) {\n width: $nav-list-item-height;\n height: $nav-list-item-height;\n padding: #{$nav-list-item-height * 0.25};\n }\n\n &:hover {\n background-image: linear-gradient(\n -90deg,\n rgba($feedback-color, 1) 0%,\n rgba($feedback-color, 0.8) 100%\n );\n }\n\n @if $nav-list-expander-right {\n svg {\n transform: rotate(90deg);\n }\n }\n }\n\n > .nav-list {\n display: none;\n padding-left: $sp-3;\n list-style: none;\n\n .nav-list-item {\n position: relative;\n\n .nav-list-link {\n color: $nav-child-link-color;\n }\n\n .nav-list-expander {\n color: $nav-child-link-color;\n }\n }\n }\n\n &.active {\n > .nav-list-expander svg {\n @if $nav-list-expander-right {\n transform: rotate(-90deg);\n } @else {\n transform: rotate(90deg);\n }\n }\n\n > .nav-list {\n display: block;\n }\n }\n }\n}\n\n.nav-category {\n padding: $sp-2 $gutter-spacing-sm;\n font-weight: 600;\n text-align: start;\n text-transform: uppercase;\n border-bottom: $border $border-color;\n @include fs-2;\n\n @include mq(md) {\n padding: $sp-2 $gutter-spacing;\n margin-top: $gutter-spacing-sm;\n text-align: start;\n\n &:first-child {\n margin-top: 0;\n }\n }\n}\n\n.nav-list.nav-category-list {\n > .nav-list-item {\n margin: 0;\n\n > .nav-list {\n padding: 0;\n\n > .nav-list-item {\n > .nav-list-link {\n color: $link-color;\n }\n\n > .nav-list-expander {\n color: $link-color;\n }\n }\n }\n }\n}\n\n// Aux nav\n\n.aux-nav {\n height: 100%;\n overflow-x: auto;\n @include fs-2;\n\n .aux-nav-list {\n display: flex;\n height: 100%;\n padding: 0;\n margin: 0;\n list-style: none;\n }\n\n .aux-nav-list-item {\n display: inline-block;\n height: 100%;\n padding: 0;\n margin: 0;\n }\n\n @include mq(md) {\n padding-right: $gutter-spacing-sm;\n }\n}\n\n// Breadcrumb nav\n\n.breadcrumb-nav {\n @include mq(md) {\n margin-top: -$sp-4;\n }\n}\n\n.breadcrumb-nav-list {\n padding-left: 0;\n margin-bottom: $sp-3;\n list-style: none;\n}\n\n.breadcrumb-nav-list-item {\n display: table-cell;\n @include fs-2;\n\n &::before {\n display: none;\n }\n\n &::after {\n display: inline-block;\n margin-right: $sp-2;\n margin-left: $sp-2;\n color: $grey-dk-000;\n content: \"/\";\n }\n\n &:last-child {\n &::after {\n content: \"\";\n }\n }\n}\n","// Typography\n// stylelint-disable selector-no-type, selector-max-type, selector-max-specificity, selector-max-id\n\nh1,\n.text-alpha {\n font-weight: 300;\n\n @include fs-8;\n}\n\nh2,\n.text-beta,\n#toctitle {\n @include fs-6;\n}\n\nh3,\n.text-gamma {\n @include fs-5;\n}\n\nh4,\n.text-delta {\n font-weight: 400;\n text-transform: uppercase;\n letter-spacing: 0.1em;\n\n @include fs-2;\n}\n\nh4 code {\n text-transform: none;\n}\n\nh5,\n.text-epsilon {\n @include fs-3;\n}\n\nh6,\n.text-zeta {\n @include fs-2;\n}\n\n.text-small {\n @include fs-2;\n}\n\n.text-mono {\n font-family: $mono-font-family !important;\n}\n\n.text-left {\n text-align: left !important;\n}\n\n.text-center {\n text-align: center !important;\n}\n\n.text-right {\n text-align: right !important;\n}\n","// Labels (not the form kind)\n\n// this :not() prevents a style clash with Mermaid.js's\n// diagram labels, which also use .label\n// for more, see https://github.com/just-the-docs/just-the-docs/issues/1272\n// and the accompanying PR\n.label:not(g),\n.label-blue:not(g) {\n display: inline-block;\n padding: 0.16em 0.56em;\n margin-right: $sp-2;\n margin-left: $sp-2;\n color: $white;\n text-transform: uppercase;\n vertical-align: middle;\n background-color: $blue-100;\n border-radius: 12px;\n\n @include fs-2;\n}\n\n.label-green:not(g) {\n background-color: $green-300;\n}\n\n.label-purple:not(g) {\n background-color: $purple-100;\n}\n\n.label-red:not(g) {\n background-color: $red-300;\n}\n\n.label-yellow:not(g) {\n color: $grey-dk-200;\n background-color: $yellow-200;\n}\n","// Buttons and things that look like buttons\n// stylelint-disable color-named\n\n.btn {\n display: inline-block;\n box-sizing: border-box;\n padding: 0.3em 1em;\n margin: 0;\n font-family: inherit;\n font-size: inherit;\n font-weight: 500;\n line-height: 1.5;\n color: $link-color;\n text-decoration: none;\n vertical-align: baseline;\n cursor: pointer;\n background-color: $base-button-color;\n border-width: 0;\n border-radius: $border-radius;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n appearance: none;\n\n &:focus {\n text-decoration: none;\n outline: none;\n box-shadow: 0 0 0 3px rgba(blue, 0.25);\n }\n\n &:focus:hover,\n &.selected:focus {\n box-shadow: 0 0 0 3px rgba(blue, 0.25);\n }\n\n &:hover,\n &.zeroclipboard-is-hover {\n color: darken($link-color, 2%);\n }\n\n &:hover,\n &:active,\n &.zeroclipboard-is-hover,\n &.zeroclipboard-is-active {\n text-decoration: none;\n background-color: darken($base-button-color, 1%);\n }\n\n &:active,\n &.selected,\n &.zeroclipboard-is-active {\n background-color: darken($base-button-color, 3%);\n background-image: none;\n box-shadow: inset 0 2px 4px rgba(0, 0, 0, 0.15);\n }\n\n &.selected:hover {\n background-color: darken(#dcdcdc, 5%);\n }\n\n &:disabled,\n &.disabled {\n &,\n &:hover {\n color: rgba(102, 102, 102, 0.5);\n cursor: default;\n background-color: rgba(229, 229, 229, 0.5);\n background-image: none;\n box-shadow: none;\n }\n }\n}\n\n.btn-outline {\n color: $link-color;\n background: transparent;\n box-shadow: inset 0 0 0 2px $grey-lt-300;\n\n &:hover,\n &:active,\n &.zeroclipboard-is-hover,\n &.zeroclipboard-is-active {\n color: darken($link-color, 4%);\n text-decoration: none;\n background-color: transparent;\n box-shadow: inset 0 0 0 3px $grey-lt-300;\n }\n\n &:focus {\n text-decoration: none;\n outline: none;\n box-shadow:\n inset 0 0 0 2px $grey-dk-100,\n 0 0 0 3px rgba(blue, 0.25);\n }\n\n &:focus:hover,\n &.selected:focus {\n box-shadow: inset 0 0 0 2px $grey-dk-100;\n }\n}\n\n.btn-primary {\n @include btn-color($white, $btn-primary-color);\n}\n\n.btn-purple {\n @include btn-color($white, $purple-100);\n}\n\n.btn-blue {\n @include btn-color($white, $blue-200);\n}\n\n.btn-green {\n @include btn-color($white, $green-300);\n}\n\n.btn-reset {\n background: none;\n border: none;\n margin: 0;\n text-align: inherit;\n font: inherit;\n border-radius: 0;\n appearance: none;\n}\n","// Colored button\n\n@mixin btn-color($fg, $bg) {\n color: $fg;\n background-color: darken($bg, 2%);\n background-image: linear-gradient(lighten($bg, 5%), darken($bg, 2%));\n box-shadow:\n 0 1px 3px rgba(0, 0, 0, 0.25),\n 0 4px 10px rgba(0, 0, 0, 0.12);\n\n &:hover,\n &.zeroclipboard-is-hover {\n color: $fg;\n background-color: darken($bg, 4%);\n background-image: linear-gradient((lighten($bg, 2%), darken($bg, 4%)));\n }\n\n &:active,\n &.selected,\n &.zeroclipboard-is-active {\n background-color: darken($bg, 5%);\n background-image: none;\n box-shadow: inset 0 2px 4px rgba(0, 0, 0, 0.15);\n }\n\n &.selected:hover {\n background-color: darken($bg, 10%);\n }\n}\n","// Search input and autocomplete\n\n.search {\n position: relative;\n z-index: 2;\n flex-grow: 1;\n height: $sp-10;\n padding: $sp-2;\n transition: padding linear #{$transition-duration * 0.5};\n\n @include mq(md) {\n position: relative !important;\n width: auto !important;\n height: 100% !important;\n padding: 0;\n transition: none;\n }\n}\n\n.search-input-wrap {\n position: relative;\n z-index: 1;\n height: $sp-8;\n overflow: hidden;\n border-radius: $border-radius;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n transition: height linear #{$transition-duration * 0.5};\n\n @include mq(md) {\n position: absolute;\n width: 100%;\n max-width: $search-results-width;\n height: 100% !important;\n border-radius: 0;\n box-shadow: none;\n transition: width ease $transition-duration;\n }\n}\n\n.search-input {\n position: absolute;\n width: 100%;\n height: 100%;\n padding: $sp-2 $gutter-spacing-sm $sp-2 #{$gutter-spacing-sm + $sp-5};\n font-size: 1rem;\n color: $body-text-color;\n background-color: $search-background-color;\n border-top: 0;\n border-right: 0;\n border-bottom: 0;\n border-left: 0;\n border-radius: 0;\n\n @include mq(md) {\n padding: $sp-2 $gutter-spacing-sm $sp-2 #{$gutter-spacing + $sp-5};\n font-size: 0.875rem;\n background-color: $body-background-color;\n transition: padding-left linear #{$transition-duration * 0.5};\n }\n\n &:focus {\n outline: 2px solid $link-color;\n outline-offset: -2px;\n\n + .search-label .search-icon {\n color: $link-color;\n }\n }\n}\n\n.search-label {\n position: absolute;\n display: flex;\n height: 100%;\n padding-left: $gutter-spacing-sm;\n\n @include mq(md) {\n padding-left: $gutter-spacing;\n transition: padding-left linear #{$transition-duration * 0.5};\n }\n\n .search-icon {\n width: #{$sp-4 * 1.2};\n height: #{$sp-4 * 1.2};\n align-self: center;\n color: $grey-dk-000;\n }\n}\n\n.search-results {\n position: absolute;\n left: 0;\n display: none;\n width: 100%;\n max-height: calc(100% - #{$sp-10});\n overflow-y: auto;\n background-color: $search-background-color;\n border-bottom-right-radius: $border-radius;\n border-bottom-left-radius: $border-radius;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n\n @include mq(md) {\n top: 100%;\n width: $search-results-width;\n max-height: calc(100vh - 200%) !important;\n }\n}\n\n.search-results-list {\n padding-left: 0;\n margin-bottom: $sp-1;\n list-style: none;\n @include fs-4;\n\n @include mq(md) {\n @include fs-3;\n }\n}\n\n.search-results-list-item {\n padding: 0;\n margin: 0;\n}\n\n.search-result {\n display: block;\n padding: $sp-1 $sp-3;\n\n &:hover,\n &.active {\n background-color: $feedback-color;\n }\n}\n\n.search-result-title {\n display: block;\n padding-top: $sp-2;\n padding-bottom: $sp-2;\n\n @include mq(sm) {\n display: inline-block;\n width: 40%;\n padding-right: $sp-2;\n vertical-align: top;\n }\n}\n\n.search-result-doc {\n display: flex;\n align-items: center;\n word-wrap: break-word;\n\n &.search-result-doc-parent {\n opacity: 0.5;\n @include fs-3;\n\n @include mq(md) {\n @include fs-2;\n }\n }\n\n .search-result-icon {\n width: $sp-4;\n height: $sp-4;\n margin-right: $sp-2;\n color: $link-color;\n flex-shrink: 0;\n }\n\n .search-result-doc-title {\n overflow: auto;\n }\n}\n\n.search-result-section {\n margin-left: #{$sp-4 + $sp-2};\n word-wrap: break-word;\n}\n\n.search-result-rel-url {\n display: block;\n margin-left: #{$sp-4 + $sp-2};\n overflow: hidden;\n color: $search-result-preview-color;\n text-overflow: ellipsis;\n white-space: nowrap;\n @include fs-1;\n}\n\n.search-result-previews {\n display: block;\n padding-top: $sp-2;\n padding-bottom: $sp-2;\n padding-left: $sp-4;\n margin-left: $sp-2;\n color: $search-result-preview-color;\n word-wrap: break-word;\n border-left: $border;\n border-left-color: $border-color;\n @include fs-2;\n\n @include mq(sm) {\n display: inline-block;\n width: 60%;\n padding-left: $sp-2;\n margin-left: 0;\n vertical-align: top;\n }\n}\n\n.search-result-preview + .search-result-preview {\n margin-top: $sp-1;\n}\n\n.search-result-highlight {\n font-weight: bold;\n}\n\n.search-no-result {\n padding: $sp-2 $sp-3;\n @include fs-3;\n}\n\n.search-button {\n position: fixed;\n right: $sp-4;\n bottom: $sp-4;\n display: flex;\n width: $sp-9;\n height: $sp-9;\n background-color: $search-background-color;\n border: 1px solid rgba($link-color, 0.3);\n border-radius: #{$sp-9 * 0.5};\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n align-items: center;\n justify-content: center;\n}\n\n.search-overlay {\n position: fixed;\n top: 0;\n left: 0;\n z-index: 1;\n width: 0;\n height: 0;\n background-color: rgba(0, 0, 0, 0.3);\n opacity: 0;\n transition:\n opacity ease $transition-duration,\n width 0s $transition-duration,\n height 0s $transition-duration;\n}\n\n.search-active {\n .search {\n position: fixed;\n top: 0;\n left: 0;\n width: 100%;\n height: 100%;\n padding: 0;\n }\n\n .search-input-wrap {\n height: $sp-10;\n border-radius: 0;\n\n @include mq(md) {\n width: $search-results-width;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n }\n }\n\n .search-input {\n background-color: $search-background-color;\n\n @include mq(md) {\n padding-left: 2.3rem;\n }\n }\n\n .search-label {\n @include mq(md) {\n padding-left: 0.6rem;\n }\n }\n\n .search-results {\n display: block;\n }\n\n .search-overlay {\n width: 100%;\n height: 100%;\n opacity: 1;\n transition:\n opacity ease $transition-duration,\n width 0s,\n height 0s;\n }\n\n @include mq(md) {\n .main {\n position: fixed;\n right: 0;\n left: 0;\n }\n }\n\n .main-header {\n padding-top: $sp-10;\n\n @include mq(md) {\n padding-top: 0;\n }\n }\n}\n","// Tables\n// stylelint-disable max-nesting-depth, selector-no-type, selector-max-type\n\n.table-wrapper {\n display: block;\n width: 100%;\n max-width: 100%;\n margin-bottom: $sp-5;\n overflow-x: auto;\n border-radius: $border-radius;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n}\n\ntable {\n display: table;\n min-width: 100%;\n border-collapse: separate;\n}\n\nth,\ntd {\n min-width: 7.5rem;\n padding: $sp-2 $sp-3;\n background-color: $table-background-color;\n border-bottom: $border rgba($border-color, 0.5);\n border-left: $border $border-color;\n\n @include fs-3;\n\n &:first-of-type {\n border-left: 0;\n }\n}\n\ntbody {\n tr {\n &:last-of-type {\n th,\n td {\n border-bottom: 0;\n }\n\n td {\n padding-bottom: $sp-3;\n }\n }\n }\n}\n\nthead {\n th {\n border-bottom: $border $border-color;\n }\n}\n","// Code and syntax highlighting\n// stylelint-disable selector-no-qualifying-type, declaration-block-semicolon-newline-after,declaration-block-single-line-max-declarations, selector-no-type, selector-max-type, scss/comment-no-empty\n\n// {% raw %}\n\n// This instruction applies to all queues not within 'pre' or 'figure', avoiding 'code' generated by the highlight.\n:not(pre, figure) {\n & > code {\n padding: 0.2em 0.15em;\n font-weight: 400;\n background-color: $code-background-color;\n border: $border $border-color;\n border-radius: $border-radius;\n }\n}\n\n// Avoid appearance of dark border around visited code links in Safari\na:visited code {\n border-color: $border-color;\n}\n\n// Content structure for highlighted code blocks using fences or Liquid\n//\n// ```[LANG]...```, no kramdown line_numbers:\n// div.[language-LANG.]highlighter-rouge > div.highlight > pre.highlight > code\n//\n// ```[LANG]...```, kramdown line_numbers = true:\n// div.[language-LANG.]highlighter-rouge > div.highlight > pre.highlight > code\n// > div.table-wrapper > table.rouge-table > tbody > tr\n// > td.rouge-gutter.gl > pre.lineno\n// | td.rouge-code > pre\n//\n// {% highlight LANG %}...{% endhighlight %}:\n// figure.highlight > pre > code.language-LANG\n//\n// {% highlight LANG linenos %}...{% endhighlight %}:\n// figure.highlight > pre > code.language-LANG\n// > div.table-wrapper > table.rouge-table > tbody > tr\n// > td.gutter.gl > pre.lineno\n// | td.code > pre\n//\n// ----...---- (AsciiDoc)\n// div.listingblock > div.content > pre.rouge.highlight\n//\n// fix_linenos removes the outermost pre when it encloses table.rouge-table\n//\n// See docs/index-test.md for some tests.\n//\n// No kramdown line_numbers: fences and Liquid highlighting look the same.\n// Kramdown line_numbers = true: fences have a wider gutter than with Liquid?\n\n// ```[LANG]...```\n// or in AsciiDoc:\n//\n// ----\n// ...\n// ----\n\n// the code may appear with 3 different types:\n// container \\ case: default case, code with line number, code with html rendering\n// top level: div.highlighter-rouge, figure.highlight, figure.highlight\n// second level: div.highlight, div.table-wrapper, pre.highlight\n// third level: pre.highlight, td.code, absent\n// last level: code, pre, code (optionality)\n// highlighter level: span, span, span\n// the spacing are only in the second level for case 1, 3 and in the third level for case 2\n// in AsciiDoc, there is a parent container that contains optionally a title and the content.\n\n// select top level container\ndiv.highlighter-rouge,\ndiv.listingblock > div.content,\nfigure.highlight {\n margin-top: 0;\n margin-bottom: $sp-3;\n background-color: $code-background-color;\n border-radius: $border-radius;\n box-shadow: none;\n -webkit-overflow-scrolling: touch;\n position: relative;\n padding: 0;\n\n // copy button (or other button)\n // the button appear only when there is a hover on the code or focus on button\n > button {\n width: $sp-3;\n opacity: 0;\n position: absolute;\n top: 0;\n right: 0;\n padding: $sp-3;\n border: none;\n background: none;\n color: $body-text-color;\n box-sizing: content-box;\n\n svg {\n fill: $body-text-color;\n }\n\n &:active {\n text-decoration: none;\n outline: none;\n opacity: 1;\n }\n\n &:focus {\n opacity: 1;\n outline: 2px solid $link-color;\n }\n }\n\n // the button can be seen by doing a simple hover in the code, there is no need to go over the location of the button\n &:hover {\n > button {\n cursor: copy;\n opacity: 1;\n }\n }\n}\n\n// setting the spacing and scrollbar on the second level for the first case\n// remove all space on the second and third level\n// this is a mixin to accommodate for the slightly different structures generated via Markdown vs AsciiDoc\n@mixin scroll-and-spacing($code-div, $pre-select) {\n #{$code-div} {\n overflow-x: auto;\n padding: $sp-3;\n margin: 0;\n border: 1px solid $body-text-color;\n border-radius: $border-radius;\n }\n\n #{$pre-select},\n code {\n padding: 0;\n margin: 0;\n border: 0;\n }\n}\n\n// for Markdown\ndiv.highlighter-rouge {\n @include scroll-and-spacing(\"div.highlight\", \"pre.highlight\");\n}\n\n// for AsciiDoc. we also need to fix the margins for its parent container.\ndiv.listingblock {\n margin-top: 0;\n margin-bottom: $sp-3;\n\n @include scroll-and-spacing(\"div.content\", \"div.content > pre\");\n}\n\n// {% highlight LANG %}...{% endhighlight %},\n// {% highlight LANG linenos %}...{% endhighlight %}:\n\n// setting the spacing and scrollbar on the second level for the thirt case\n// the css rule are apply only to the last code enviroment\n// setting the scroolbar\nfigure.highlight {\n pre,\n :not(pre) > code {\n overflow-x: auto;\n padding: $sp-3;\n margin: 0;\n border: 1px solid $body-text-color;\n border-radius: $border-radius;\n }\n}\n\n// ```[LANG]...```, kramdown line_numbers = true,\n// {% highlight LANG linenos %}...{% endhighlight %}:\n\n// setting the spacing and scrollbar on the thirt level for the second case\n.highlight .table-wrapper {\n padding: $sp-3 0;\n margin: 0;\n border: 0;\n box-shadow: none;\n\n td,\n pre {\n min-width: 0;\n padding: 0;\n background-color: $code-background-color;\n border: 0;\n\n @include fs-2;\n }\n\n td.gl {\n width: 1em;\n padding-right: $sp-3;\n padding-left: $sp-3;\n }\n\n pre {\n margin: 0;\n line-height: 2;\n }\n}\n\n// Code examples: html render of a code\n.code-example,\n.listingblock > .title {\n padding: $sp-3;\n margin-bottom: $sp-3;\n overflow: auto;\n border: 1px solid $border-color;\n border-radius: $border-radius;\n\n + .highlighter-rouge,\n + .sectionbody .listingblock,\n + .content,\n + figure.highlight {\n position: relative;\n margin-top: -$sp-4;\n border-right: 1px solid $border-color;\n border-bottom: 1px solid $border-color;\n border-left: 1px solid $border-color;\n border-top-left-radius: 0;\n border-top-right-radius: 0;\n }\n}\n\n// Mermaid diagram code blocks should be left unstyled.\ncode.language-mermaid {\n padding: 0;\n background-color: inherit;\n border: 0;\n}\n\n// Override OneDarkJekyll Colors for Code Blocks\n.highlight,\npre.highlight {\n background: $code-background-color; // Code Background\n // For Backwards Compatibility Before $code-linenumber-color was added\n @if variable-exists(code-linenumber-color) {\n color: $code-linenumber-color; // Code Line Numbers\n } @else {\n color: $body-text-color; // Code Line Numbers\n }\n}\n\n// Override OneDarkJekyll Colors for Code Blocks\n.highlight pre {\n background: $code-background-color; // Code Background\n}\n\n// {% endraw %}\n","// Utility classes for colors\n\n// Text colors\n\n.text-grey-dk-000 {\n color: $grey-dk-000 !important;\n}\n\n.text-grey-dk-100 {\n color: $grey-dk-100 !important;\n}\n\n.text-grey-dk-200 {\n color: $grey-dk-200 !important;\n}\n\n.text-grey-dk-250 {\n color: $grey-dk-250 !important;\n}\n\n.text-grey-dk-300 {\n color: $grey-dk-300 !important;\n}\n\n.text-grey-lt-000 {\n color: $grey-lt-000 !important;\n}\n\n.text-grey-lt-100 {\n color: $grey-lt-100 !important;\n}\n\n.text-grey-lt-200 {\n color: $grey-lt-200 !important;\n}\n\n.text-grey-lt-300 {\n color: $grey-lt-300 !important;\n}\n\n.text-blue-000 {\n color: $blue-000 !important;\n}\n\n.text-blue-100 {\n color: $blue-100 !important;\n}\n\n.text-blue-200 {\n color: $blue-200 !important;\n}\n\n.text-blue-300 {\n color: $blue-300 !important;\n}\n\n.text-green-000 {\n color: $green-000 !important;\n}\n\n.text-green-100 {\n color: $green-100 !important;\n}\n\n.text-green-200 {\n color: $green-200 !important;\n}\n\n.text-green-300 {\n color: $green-300 !important;\n}\n\n.text-purple-000 {\n color: $purple-000 !important;\n}\n\n.text-purple-100 {\n color: $purple-100 !important;\n}\n\n.text-purple-200 {\n color: $purple-200 !important;\n}\n\n.text-purple-300 {\n color: $purple-300 !important;\n}\n\n.text-yellow-000 {\n color: $yellow-000 !important;\n}\n\n.text-yellow-100 {\n color: $yellow-100 !important;\n}\n\n.text-yellow-200 {\n color: $yellow-200 !important;\n}\n\n.text-yellow-300 {\n color: $yellow-300 !important;\n}\n\n.text-red-000 {\n color: $red-000 !important;\n}\n\n.text-red-100 {\n color: $red-100 !important;\n}\n\n.text-red-200 {\n color: $red-200 !important;\n}\n\n.text-red-300 {\n color: $red-300 !important;\n}\n\n// Background colors\n\n.bg-grey-dk-000 {\n background-color: $grey-dk-000 !important;\n}\n\n.bg-grey-dk-100 {\n background-color: $grey-dk-100 !important;\n}\n\n.bg-grey-dk-200 {\n background-color: $grey-dk-200 !important;\n}\n\n.bg-grey-dk-250 {\n background-color: $grey-dk-250 !important;\n}\n\n.bg-grey-dk-300 {\n background-color: $grey-dk-300 !important;\n}\n\n.bg-grey-lt-000 {\n background-color: $grey-lt-000 !important;\n}\n\n.bg-grey-lt-100 {\n background-color: $grey-lt-100 !important;\n}\n\n.bg-grey-lt-200 {\n background-color: $grey-lt-200 !important;\n}\n\n.bg-grey-lt-300 {\n background-color: $grey-lt-300 !important;\n}\n\n.bg-blue-000 {\n background-color: $blue-000 !important;\n}\n\n.bg-blue-100 {\n background-color: $blue-100 !important;\n}\n\n.bg-blue-200 {\n background-color: $blue-200 !important;\n}\n\n.bg-blue-300 {\n background-color: $blue-300 !important;\n}\n\n.bg-green-000 {\n background-color: $green-000 !important;\n}\n\n.bg-green-100 {\n background-color: $green-100 !important;\n}\n\n.bg-green-200 {\n background-color: $green-200 !important;\n}\n\n.bg-green-300 {\n background-color: $green-300 !important;\n}\n\n.bg-purple-000 {\n background-color: $purple-000 !important;\n}\n\n.bg-purple-100 {\n background-color: $purple-100 !important;\n}\n\n.bg-purple-200 {\n background-color: $purple-200 !important;\n}\n\n.bg-purple-300 {\n background-color: $purple-300 !important;\n}\n\n.bg-yellow-000 {\n background-color: $yellow-000 !important;\n}\n\n.bg-yellow-100 {\n background-color: $yellow-100 !important;\n}\n\n.bg-yellow-200 {\n background-color: $yellow-200 !important;\n}\n\n.bg-yellow-300 {\n background-color: $yellow-300 !important;\n}\n\n.bg-red-000 {\n background-color: $red-000 !important;\n}\n\n.bg-red-100 {\n background-color: $red-100 !important;\n}\n\n.bg-red-200 {\n background-color: $red-200 !important;\n}\n\n.bg-red-300 {\n background-color: $red-300 !important;\n}\n","// Utility classes for layout\n\n// Display\n\n.d-block {\n display: block !important;\n}\n\n.d-flex {\n display: flex !important;\n}\n\n.d-inline {\n display: inline !important;\n}\n\n.d-inline-block {\n display: inline-block !important;\n}\n\n.d-none {\n display: none !important;\n}\n\n// Screenreader-only\n\n.sr-only {\n position: absolute;\n width: 1px;\n height: 1px;\n padding: 0;\n margin: -1px;\n overflow: hidden;\n clip: rect(0, 0, 0, 0);\n white-space: nowrap;\n border-width: 0;\n}\n\n@each $media-query in map-keys($media-queries) {\n @for $i from 1 through length($spacers) {\n @include mq($media-query) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .d-sm-block, .d-md-none, .d-lg-inline\n .d-#{$media-query}-block {\n display: block !important;\n }\n .d-#{$media-query}-flex {\n display: flex !important;\n }\n .d-#{$media-query}-inline {\n display: inline !important;\n }\n .d-#{$media-query}-inline-block {\n display: inline-block !important;\n }\n .d-#{$media-query}-none {\n display: none !important;\n }\n }\n }\n}\n\n// Horizontal alignment\n\n.float-left {\n float: left !important;\n}\n\n.float-right {\n float: right !important;\n}\n\n.flex-justify-start {\n justify-content: flex-start !important;\n}\n\n.flex-justify-end {\n justify-content: flex-end !important;\n}\n\n.flex-justify-between {\n justify-content: space-between !important;\n}\n\n.flex-justify-around {\n justify-content: space-around !important;\n}\n\n// Vertical alignment\n\n.v-align-baseline {\n vertical-align: baseline !important;\n}\n\n.v-align-bottom {\n vertical-align: bottom !important;\n}\n\n.v-align-middle {\n vertical-align: middle !important;\n}\n\n.v-align-text-bottom {\n vertical-align: text-bottom !important;\n}\n\n.v-align-text-top {\n vertical-align: text-top !important;\n}\n\n.v-align-top {\n vertical-align: top !important;\n}\n","// Utility classes for typography\n\n.fs-1 {\n @include fs-1;\n}\n\n.fs-2 {\n @include fs-2;\n}\n\n.fs-3 {\n @include fs-3;\n}\n\n.fs-4 {\n @include fs-4;\n}\n\n.fs-5 {\n @include fs-5;\n}\n\n.fs-6 {\n @include fs-6;\n}\n\n.fs-7 {\n @include fs-7;\n}\n\n.fs-8 {\n @include fs-8;\n}\n\n.fs-9 {\n @include fs-9;\n}\n\n.fs-10 {\n @include fs-10;\n}\n\n.fw-300 {\n font-weight: 300 !important;\n}\n\n.fw-400 {\n font-weight: 400 !important;\n}\n\n.fw-500 {\n font-weight: 500 !important;\n}\n\n.fw-700 {\n font-weight: 700 !important;\n}\n\n.lh-0 {\n line-height: 0 !important;\n}\n\n.lh-default {\n line-height: $body-line-height;\n}\n\n.lh-tight {\n line-height: $body-heading-line-height;\n}\n\n.ls-5 {\n letter-spacing: 0.05em !important;\n}\n\n.ls-10 {\n letter-spacing: 0.1em !important;\n}\n\n.ls-0 {\n letter-spacing: 0 !important;\n}\n\n.text-uppercase {\n text-transform: uppercase !important;\n}\n","// Utility classes for lists\n\n// stylelint-disable selector-max-type\n\n.list-style-none {\n padding: 0 !important;\n margin: 0 !important;\n list-style: none !important;\n\n li {\n &::before {\n display: none !important;\n }\n }\n}\n","// Utility classes for margins and padding\n\n// stylelint-disable block-opening-brace-space-after, block-opening-brace-space-before\n\n// Margin spacer utilities\n\n.mx-auto {\n margin-right: auto !important;\n margin-left: auto !important;\n}\n\n@for $i from 1 through length($spacers) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .m-0, .m-1, .m-2...\n .m-#{$scale} {\n margin: #{$size} !important;\n }\n .mt-#{$scale} {\n margin-top: #{$size} !important;\n }\n .mr-#{$scale} {\n margin-right: #{$size} !important;\n }\n .mb-#{$scale} {\n margin-bottom: #{$size} !important;\n }\n .ml-#{$scale} {\n margin-left: #{$size} !important;\n }\n\n .mx-#{$scale} {\n margin-right: #{$size} !important;\n margin-left: #{$size} !important;\n }\n\n .my-#{$scale} {\n margin-top: #{$size} !important;\n margin-bottom: #{$size} !important;\n }\n\n .mxn-#{$scale} {\n margin-right: -#{$size} !important;\n margin-left: -#{$size} !important;\n }\n .mx-#{$scale}-auto {\n margin-right: auto !important;\n margin-left: auto !important;\n }\n}\n\n@each $media-query in map-keys($media-queries) {\n @for $i from 1 through length($spacers) {\n @include mq($media-query) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .m-sm-0, .m-md-1, .m-lg-2...\n .m-#{$media-query}-#{$scale} {\n margin: #{$size} !important;\n }\n .mt-#{$media-query}-#{$scale} {\n margin-top: #{$size} !important;\n }\n .mr-#{$media-query}-#{$scale} {\n margin-right: #{$size} !important;\n }\n .mb-#{$media-query}-#{$scale} {\n margin-bottom: #{$size} !important;\n }\n .ml-#{$media-query}-#{$scale} {\n margin-left: #{$size} !important;\n }\n\n .mx-#{$media-query}-#{$scale} {\n margin-right: #{$size} !important;\n margin-left: #{$size} !important;\n }\n\n .my-#{$media-query}-#{$scale} {\n margin-top: #{$size} !important;\n margin-bottom: #{$size} !important;\n }\n\n .mxn-#{$media-query}-#{$scale} {\n margin-right: -#{$size} !important;\n margin-left: -#{$size} !important;\n }\n }\n }\n}\n\n// Padding spacer utilities\n\n@for $i from 1 through length($spacers) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .p-0, .p-1, .p-2...\n .p-#{$scale} {\n padding: #{$size} !important;\n }\n .pt-#{$scale} {\n padding-top: #{$size} !important;\n }\n .pr-#{$scale} {\n padding-right: #{$size} !important;\n }\n .pb-#{$scale} {\n padding-bottom: #{$size} !important;\n }\n .pl-#{$scale} {\n padding-left: #{$size} !important;\n }\n\n .px-#{$scale} {\n padding-right: #{$size} !important;\n padding-left: #{$size} !important;\n }\n\n .py-#{$scale} {\n padding-top: #{$size} !important;\n padding-bottom: #{$size} !important;\n }\n}\n\n@each $media-query in map-keys($media-queries) {\n @include mq($media-query) {\n @for $i from 1 through length($spacers) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .p-sm-0, .p-md-1, .p-lg-2...\n .p-#{$media-query}-#{$scale} {\n padding: #{$size} !important;\n }\n .pt-#{$media-query}-#{$scale} {\n padding-top: #{$size} !important;\n }\n .pr-#{$media-query}-#{$scale} {\n padding-right: #{$size} !important;\n }\n .pb-#{$media-query}-#{$scale} {\n padding-bottom: #{$size} !important;\n }\n .pl-#{$media-query}-#{$scale} {\n padding-left: #{$size} !important;\n }\n\n .px-#{$media-query}-#{$scale} {\n padding-right: #{$size} !important;\n padding-left: #{$size} !important;\n }\n\n .py-#{$media-query}-#{$scale} {\n padding-top: #{$size} !important;\n padding-bottom: #{$size} !important;\n }\n }\n }\n}\n","// stylelint-disable selector-max-specificity, selector-max-id, selector-max-type, selector-no-qualifying-type\n\n@media print {\n .site-footer,\n .site-button,\n #edit-this-page,\n #back-to-top,\n .site-nav,\n .main-header {\n display: none !important;\n }\n\n hr {\n margin-top: 1rem;\n margin-bottom: 1rem;\n }\n\n .side-bar {\n width: 100%;\n height: auto;\n border-right: 0 !important;\n }\n\n .site-header {\n border-bottom: 1px solid $border-color;\n }\n\n .site-title {\n font-size: 1rem !important;\n font-weight: 700 !important;\n }\n\n .text-small {\n font-size: 8pt !important;\n }\n\n pre.highlight {\n border: 1px solid $border-color;\n }\n\n .main {\n max-width: none;\n margin-left: 0;\n }\n}\n","// Skipnav\n// Skip to main content\n\na.skip-to-main {\n left: -999px;\n position: absolute;\n top: auto;\n width: 1px;\n height: 1px;\n overflow: hidden;\n z-index: -999;\n}\n\na.skip-to-main:focus,\na.skip-to-main:active {\n color: $link-color;\n background-color: $body-background-color;\n left: auto;\n top: auto;\n width: 30%;\n height: auto;\n overflow: auto;\n margin: 10px 35%;\n padding: 5px;\n border-radius: 15px;\n border: 4px solid $btn-primary-color;\n text-align: center;\n font-size: 1.2em;\n z-index: 999;\n}\n","\n@import \"./support/support\";\n@import \"./custom/setup\";\n@import \"./color_schemes/light\";\n\n@import \"./color_schemes/dark\";\n\n@import \"./modules\";\ndiv.opaque {\n background-color: $body-background-color;\n}\n\np.tip, blockquote.tip {\n border: 1px $green-300 solid;\n border-left: $border-radius solid $green-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n \n &::before {\n color: $green-300;\n content: \"Tip\";\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n \n > .tip-title {\n color: $green-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\np.tip-title, blockquote.tip-title {\n border: 1px $green-300 solid;\n border-left: $border-radius solid $green-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n > p:first-child {\n margin-top: 0;\n margin-bottom: 0;\n color: $green-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\nblockquote.tip {\n margin-left: 0;\n margin-right: 0;\n\n > p:first-child {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\nblockquote.tip-title {\n margin-left: 0;\n margin-right: 0;\n\n > p:nth-child(2) {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\n\n\np.note, blockquote.note {\n border: 1px $blue-300 solid;\n border-left: $border-radius solid $blue-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n \n &::before {\n color: $blue-300;\n content: \"Note\";\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n \n > .note-title {\n color: $blue-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\np.note-title, blockquote.note-title {\n border: 1px $blue-300 solid;\n border-left: $border-radius solid $blue-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n > p:first-child {\n margin-top: 0;\n margin-bottom: 0;\n color: $blue-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\nblockquote.note {\n margin-left: 0;\n margin-right: 0;\n\n > p:first-child {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\nblockquote.note-title {\n margin-left: 0;\n margin-right: 0;\n\n > p:nth-child(2) {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\n\n\np.warning, blockquote.warning {\n border: 1px $yellow-300 solid;\n border-left: $border-radius solid $yellow-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n \n &::before {\n color: $yellow-300;\n content: \"Warning\";\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n \n > .warning-title {\n color: $yellow-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\np.warning-title, blockquote.warning-title {\n border: 1px $yellow-300 solid;\n border-left: $border-radius solid $yellow-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n > p:first-child {\n margin-top: 0;\n margin-bottom: 0;\n color: $yellow-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\nblockquote.warning {\n margin-left: 0;\n margin-right: 0;\n\n > p:first-child {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\nblockquote.warning-title {\n margin-left: 0;\n margin-right: 0;\n\n > p:nth-child(2) {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\n\n@import \"./custom/custom\";\n\n\n"],"file":"just-the-docs-dark.css"} \ No newline at end of file +{"version":3,"sourceRoot":"","sources":["../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/vendor/accessible-pygments/github-light.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/vendor/accessible-pygments/github-dark.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/vendor/normalize.scss/normalize.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/base.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/color_schemes/dark.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/support/mixins/_typography.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/support/mixins/_layout.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/support/_variables.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/layout.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/content.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/navigation.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/typography.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/labels.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/buttons.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/support/mixins/_buttons.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/search.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/tables.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/code.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/utilities/_colors.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/utilities/_layout.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/utilities/_typography.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/utilities/_lists.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/utilities/_spacing.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/print.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/skiptomain.scss","just-the-docs-dark.scss"],"names":[],"mappings":";AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAUA;EAAkB;;;AAClB;EAAgB;EAAiB;AACjC;EAAkB;EAAiB;AACnC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAkB;EAAiB;AACnC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAqB;AACtC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAoB;AACrC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAgB;EAAiB;AACjC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AChFlC;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAUA;EAAkB;;;AAClB;EAAa;EAAqB;;;AAClC;EAAgB;EAAgB;EAAqB;AACrD;EAAkB;EAAiB;AACnC;EAAkB;EAAiB;AACnC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAgB;EAAgB;EAAoB;AACpD;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAiB;EAAgB;EAAqB;AACtD;EAAiB;EAAgB;EAAqB;AACtD;EAAiB;EAAgB;EAAmB;EAAqB;AACzE;EAAkB;EAAgB;EAAqB;AACvD;EAAiB;EAAgB;EAAqB;AACtD;EAAiB;EAAgB;EAAmB;EAAqB;AACzE;EAAiB;EAAgB;EAA4B;AAC7D;EAAiB;EAAgB;EAAqB;AACtD;EAAkB;EAAgB;EAAmB;EAAqB;AAC1E;EAAiB;EAAiB;AAClC;EAAiB;EAAgB;EAAoB;AACrD;EAAiB;EAAgB;EAA4B;AAC7D;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAgB;EAAoB;AACrD;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAA0B;EAAgB;EAA6B;AACvE;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAgB;EAAoB;AACrD;EAAiB;EAAgB;EAAoB;AACrD;EAAiB;EAAgB;EAAoB;AACrD;EAAiB;EAAiB;AAClC;EAAiB;EAAgB;EAAoB;AACrD;EAAiB;EAAgB;EAAoB;AACrD;EAAiB;EAAgB;EAAoB;AACrD;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAgB;EAAoB;AACrD;EAAiB;EAAiB;AAClC;EAAgB;EAAiB;AACjC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAgB;EAAoB;AACrD;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AC1FlC;AAEA;AAAA;AAGA;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAAA;AAKA;EACE;EACA;EACA;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;EACA;;;AAGF;AAAA;AAAA;AAIA;AAAA;EAEE;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;AAAA;EAGE;EACA;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;EAEE;EACA;EACA;EACA;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAAA;AAKA;AAAA;AAAA;AAAA;AAAA;EAKE;EACA;EACA;EACA;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;AAEE;EACA;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;AAEE;EACA;;;AAGF;AAAA;AAAA;AAIA;AAAA;AAAA;AAAA;EAIE;;;AAGF;AAAA;AAAA;AAIA;AAAA;AAAA;AAAA;EAIE;EACA;;;AAGF;AAAA;AAAA;AAIA;AAAA;AAAA;AAAA;EAIE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAOA;EACE;EACA;EACA;EACA;EACA;EACA;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;EAEE;EACA;;;AAGF;AAAA;AAAA;AAIA;AAAA;EAEE;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AC1VF;EACE,cCJa;;;ADOf;EACE;;;AAGF;EACE;;AEmBA;EACE;;AClBA;EHHJ;IEyBI;;;;AFnBJ;EACE,aIfiB;EJgBjB;EACA,aIbiB;EJcjB,OIiBY;EJhBZ,kBIYY;EJXZ;;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAYE;;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAOE;EACA;EACA;EACA,aI1CyB;EJ2CzB,OIjBY;;;AJoBd;EACE;EACA;;;AAGF;EACE,OCzDW;ED0DX;;;AAGF;EACE;EACA,uBInCY;EJoCZ;;AAEA;EACE;;;AAIJ;EACE,aIvEiB;EJwEjB;EACA,aIvEiB;;;AJ0EnB;AAAA;EAEE;;;AAGF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;EACA;EACA,kBInEY;EJoEZ;;;AAIF;EACE;EAGA;EACA;EACA;EACA;;;AK7GF;EACE;EACA;EACA;EACA,kBD4BY;;ADpBV;EEZJ;IAOI;IACA;IACA,ODwFW;ICvFX;IACA;IACA;;;AFAA;EEZJ;IAgBI;IACA,WD+EQ;;;ADpFR;EEQF;IAEI,aD2ES;;;ADrFX;EEQF;IAQI;;;AAOF;EACE;EACA,kBDLQ;;ADpBV;EEuBA;IAKI;IACA,kBDTM;;;ACYR;EACE;;AFjCJ;EEgCE;IAII;;;;AAOV;EACE;;AF5CE;EE2CJ;IAII;IACA,WDyCY;;;;ACrChB;EACE,aDaK;ECZL,gBDYK;EDvDL,eCuDK;EDtDL,cCsDK;;ADlEH;EEoDJ;IFrCI,eCqDG;IDpDH,cCoDG;;;ADpEH;EEoDJ;IAOI,aDSG;ICRH,gBDQG;;;;ACJP;EACE;EACA;;AFlEE;EEgEJ;IAKI;IACA;IACA,QDmBY;;;;ACfhB;AAAA;AAAA;EAGE;;AF9EE;EE2EJ;AAAA;AAAA;IAMI,ODGQ;;;;ACCZ;EACE;;AAEA;EACE;;AFzFA;EEqFJ;IAQI;IACA,aDxBG;ICyBH,gBD7BG;IC8BH;IACA;;;;AAIJ;EACE;EACA,YDbc;ECcd;;AFxGE;EEqGJ;IAMI,QDjBY;ICkBZ,YDlBY;ICmBZ;;;;AAIJ;EACE;EACA;EACA;EACA;EACA,aDrDK;ECsDL,gBDtDK;ECuDL,ODnGY;EDVZ,eCuDK;EDtDL,cCsDK;;ADlEH;EEiHJ;IFlGI,eCqDG;IDpDH,cCoDG;;;AF/BL;EACE;;ACtCA;EEiHJ;IHvEI;IACA,aEhDuB;;;ADKvB;EEiHJ;IAcI,aD/DG;ICgEH,gBDhEG;;;;AC+EP;EACE;EACA;EACA,SDhFK;ECiFL;;;AFnJE;EEuJF;IACE;;;AAIJ;EACE;;;AAQF;EACE;;;AAOF;EACE;EACA;EACA;EACA,aD/GK;ECgHL,gBDhHK;EDvDL,eCuDK;EDtDL,cCsDK;;ADlEH;EE6KJ;IF9JI,eCqDG;IDpDH,cCoDG;;;AFvEL;EACE;;ACEA;EE6KJ;IH3KI;;;ACFA;EE6KJ;IAYI;IACA;;;;AAIJ;EACE,OD5HK;EC6HL,QD7HK;EC8HL,OJ3MW;;;AKCb;EACE,aFEoB;;AEApB;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAOE;;AAGF;EACE;EACA;;AAGF;AAAA;EAEE;;AAIA;EACE,YF+CC;;AE3CL;EACE;EACA;;AAEA;EACE;;AAEA;EACE;EACA;EACA;EACA,OFfM;EEgBN;EACA;;AJ1BN;EACE;;ACRA;EG2BE;IJfF;;;ACZA;EG2BE;IAUI;;;AAIJ;EACE;;AAGE;EACE;EACA;;AAOV;EACE;;AAGE;EACE;EACA;EACA,OF7CM;EE8CN;;AAMJ;EACE;;AAIJ;EACE;EACA;;AAKF;EACE;;AAGF;EACE;;AAGF;EACE;EACA;;AAGF;AAAA;EAEE;;AAGF;EACE;EACA;EACA;;AAEA;EACE;;AAIJ;EACE;EACA;EACA;;AAmBE;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EACE;;AASF;AAAA;AAAA;AAAA;AAAA;AAAA;EAEE;;AAKN;EACE;EACA;EACA,OFnFG;EEoFH;EACA,eFzFG;EE0FH,cF1FG;EE2FH;;AH1JA;EGmJF;IAUI;IACA;;;AAGF;EACE;EACA;EACA;EACA,OL/KO;EKgLP;;AAYF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EACE;;AAIJ;EACE;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAOE;EACA;EACA;;AAEA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAKE;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EACE;;AAIJ;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAWE,YF9JG;;;AG3EP;EACE;EACA;EACA;EACA;;AAEA;EACE;EACA;;ALoBF;EACE;;AClBA;EILF;IL2BE;;;ACtBA;EDOF;IACE;;;ACRA;EILF;ILiBE;;;AKPA;EACE;EACA,YH+DC;EG9DD,aHuDC;EGtDD,gBHsDC;EGrDD;EAEE,eH0DD;EGzDC,cHqDD;;ADlEH;EIKA;IAeI,YHgDD;IG/CC;IAEE,eH6CH;IG5CG,cH4CH;;;AGrCD;EACE,OHkCD;EGjCC,QHiCD;EGhCC;;AAGF;EACE;EACA;;AAGF;EAEE;EACA;;AASJ;EACE;EAEE;EAGF,OHUC;EGTD,QHSC;EGRD;EACA,ONzEO;;AEUT;EIsDA;IAYI,OHED;IGDC,QHCD;IGAC;;;AAGF;EACE;;AAQA;EACE;;AAKN;EACE;EACA,cHvBC;EGwBD;;AAEA;EACE;;AAEA;EACE,OH/EI;;AGkFN;EACE,OHnFI;;AGyFR;EAEI;;AAMJ;EACE;;;AAMR;EACE;EACA;EACA;EACA;EACA;;ALhIA;EACE;;ACEA;EIwHJ;ILtHI;;;ACFA;EIwHJ;IASI;IACA,YHhEG;IGiEH;;EAEA;IACE;;;;AAMJ;EACE;;AAEA;EACE;;AAGE;EACE,ON9JG;;AMiKL;EACE,ONlKG;;;AM2Kb;EACE;EACA;;ALtKA;EACE;;ACEA;EIiKJ;IL/JI;;;AKoKF;EACE;EACA;EACA;EACA;EACA;;AAGF;EACE;EACA;EACA;EACA;;AJlLA;EIiKJ;IAqBI,eHpHG;;;;ADlEH;EI4LJ;IAEI;;;;AAIJ;EACE;EACA,eHnIK;EGoIL;;;AAGF;EACE;;AL5MA;EACE;;ACEA;EIwMJ;ILtMI;;;AK0MF;EACE;;AAGF;EACE;EACA,cHlJG;EGmJH,aHnJG;EGoJH,OHpMU;EGqMV;;AAIA;EACE;;;ACrON;AAAA;EAEE;;ANoEA;AAAA;EACE;EACA,aElEuB;;ADKvB;EKXJ;AAAA;IN4EI;;;;AA5BF;AAAA;AAAA;EACE;;ACtCA;EKJJ;AAAA;AAAA;IN8CI;IACA,aEhDuB;;;;AFgCzB;AAAA;EACE;;AC5BA;EKEJ;AAAA;IN8BI;;;;AMzBJ;AAAA;EAEE;EACA;EACA;;ANdA;AAAA;EACE;;ACEA;EKOJ;AAAA;INLI;;;;AMcJ;EACE;;;ANVA;AAAA;EACE;;ACRA;EKoBJ;AAAA;INRI;;;;AAfF;AAAA;EACE;;ACEA;EKyBJ;AAAA;INvBI;;;;AALF;EACE;;ACEA;EK8BJ;IN5BI;;;;AMgCJ;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;ACvDF;AAAA;EAEE;EACA;EACA,cLoEK;EKnEL,aLmEK;EKlEL,OLiBM;EKhBN;EACA;EACA,kBL6BS;EK5BT;;APLA;AAAA;EACE;;ACEA;EMRJ;AAAA;IPUI;;;;AOKJ;EACE,kBL4BU;;;AKzBZ;EACE,kBLcW;;;AKXb;EACE,kBL4BQ;;;AKzBV;EACE,OLFY;EKGZ,kBLkBW;;;AMlDb;EACE;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA,OTRW;ESSX;EACA;EACA;EACA,kBNiBY;EMhBZ;EACA,eNyEc;EMxEd,YACE;EAEF;;AAEA;EACE;EACA;EACA;;AAGF;EAEE;;AAGF;EAEE;;AAGF;EAIE;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;AAKA;EAEE;EACA;EACA;EACA;EACA;;;AAKN;EACE,OTtEW;ESuEX;EACA;;AAEA;EAIE;EACA;EACA;EACA;;AAGF;EACE;EACA;EACA,YACE;;AAIJ;EAEE;;;AAIJ;ECnGE,OP0BM;EOzBN;EACA;EACA,YACE;;AAGF;EAEE,OPiBI;EOhBJ;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;;ADgFJ;ECvGE,OP0BM;EOzBN;EACA;EACA,YACE;;AAGF;EAEE,OPiBI;EOhBJ;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;;ADoFJ;EC3GE,OP0BM;EOzBN;EACA;EACA,YACE;;AAGF;EAEE,OPiBI;EOhBJ;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;;ADwFJ;EC/GE,OP0BM;EOzBN;EACA;EACA,YACE;;AAGF;EAEE,OPiBI;EOhBJ;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;;AD4FJ;EACE;EACA;EACA;EACA;EACA;EACA;EACA;;;AE3HF;EACE;EACA;EACA;EACA,QRgFM;EQ/EN,SRuEK;EQtEL;;ATME;ESZJ;IASI;IACA;IACA;IACA;IACA;;;;AAIJ;EACE;EACA;EACA,QR8DK;EQ7DL;EACA,eRmEc;EQlEd,YACE;EAEF;;ATdE;ESKJ;IAYI;IACA;IACA,WRwEmB;IQvEnB;IACA;IACA;IACA;;;;AAIJ;EACE;EACA;EACA;EACA;EACA;EACA,ORTY;EQUZ,kBRfY;EQgBZ;EACA;EACA;EACA;EACA;;ATvCE;ES2BJ;IAeI;IACA;IACA,kBRxBU;IQyBV;;;AAGF;EACE;EACA;;AAEA;EACE,OX/DO;;;AWoEb;EACE;EACA;EACA;EACA,cRIK;;ADlEH;ES0DJ;IAOI,cRGG;IQFH;;;AAGF;EACE;EACA;EACA;EACA,ORzDU;;;AQ6Dd;EACE;EACA;EACA;EACA;EACA;EACA;EACA,kBRjEY;EQkEZ,4BRRc;EQSd,2BRTc;EQUd,YACE;;ATxFA;ES6EJ;IAeI;IACA,ORFmB;IQGnB;;;;AAIJ;EACE;EACA,eRrCK;EQsCL;;AVpFA;EACE;;AClBA;ESkGJ;IV5EI;;;ACtBA;EDOF;IACE;;;ACRA;ESkGJ;IVtFI;;;;AUiGJ;EACE;EACA;;;AAGF;EACE;EACA;;AAEA;EAEE,kBX3Ha;;;AW+HjB;EACE;EACA,aR9DK;EQ+DL,gBR/DK;;ADhEH;ES4HJ;IAMI;IACA;IACA,eRpEG;IQqEH;;;;AAIJ;EACE;EACA;EACA;;AAEA;EACE;;AVxIF;EACE;;ACRA;ES8IF;IVlIE;;;ACZA;EDHF;IACE;;;ACEA;ES8IF;IV5IE;;;AUqJF;EACE,ORtFG;EQuFH,QRvFG;EQwFH,cR1FG;EQ2FH,OXrKS;EWsKT;;AAGF;EACE;;;AAIJ;EACE;EACA;;;AAGF;EACE;EACA;EACA;EACA,ORrJY;EQsJZ;EACA;;AV5LA;EACE;;ACYA;ESyKJ;IVjLI;;;;AU2LJ;EACE;EACA,aRrHK;EQsHL,gBRtHK;EQuHL,cRrHK;EQsHL,aRxHK;EQyHL,ORjKY;EQkKZ;EACA,aR/GO;EQgHP,mBR1KY;;AFrBZ;EACE;;ACEA;ESmLJ;IVjLI;;;ACFA;ESmLJ;IAaI;IACA;IACA,cRlIG;IQmIH;IACA;;;;AAIJ;EACE,YR1IK;;;AQ6IP;EACE;;;AAGF;EACE;;AV1MA;EACE;;ACRA;ESgNJ;IVpMI;;;;AUyMJ;EACE;EACA,ORrJK;EQsJL,QRtJK;EQuJL;EACA,ORnJK;EQoJL,QRpJK;EQqJL,kBRzMY;EQ0MZ;EACA;EACA,YACE;EAEF;EACA;;;AAGF;EACE;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA,YACE;;;AAMF;EACE;EACA;EACA;EACA;EACA;EACA;;AAGF;EACE,QRxLI;EQyLJ;;ATjQA;ES+PF;IAKI,ORzKiB;IQ0KjB,YACE;;;AAKN;EACE,kBRzPU;;ADnBV;ES2QF;IAII;;;AT/QF;ESmRF;IAEI;;;AAIJ;EACE;;AAGF;EACE;EACA;EACA;EACA,YACE;;ATlSF;ESwSA;IACE;IACA;IACA;;;AAIJ;EACE,aRxOI;;ADxEJ;ES+SF;IAII;;;;AC9TN;EACE;EACA;EACA;EACA,eT0EK;ESzEL;EACA,eTkFc;ESjFd,YACE;;;AAIJ;EACE;EACA;EACA;;;AAGF;AAAA;EAEE;EACA;EACA,kBTQY;ESPZ;EACA;;AXNA;AAAA;EACE;;ACRA;EUOJ;AAAA;IXKI;;;AWKF;AAAA;EACE;;;AAOE;AAAA;EAEE;;AAGF;EACE,gBTkCD;;;AS3BL;EACE;;;AC9CF;EACE;EACA;EACA,kBbDoB;EaEpB;EACA,eV+EY;;;AU1EhB;EACE,cVcY;;;AUqCd;AAAA;AAAA;EAGE;EACA,eVMK;EULL,kBbjEsB;EakEtB,eVgBc;EUfd;EACA;EACA;EACA;;AAIA;AAAA;AAAA;EACE,OVLG;EUMH;EACA;EACA;EACA;EACA,SVVG;EUWH;EACA;EACA,OVtDU;EUuDV;;AAEA;AAAA;AAAA;EACE,MV1DQ;;AU6DV;AAAA;AAAA;EACE;EACA;EACA;;AAGF;AAAA;AAAA;EACE;EACA;;AAMF;AAAA;AAAA;EACE;EACA;;;AASJ;EACE;EACA,SV/CG;EUgDH;EACA;EACA,eVtCY;;AUyCd;AAAA;EAEE;EACA;EACA;;;AAUJ;EACE;EACA,eVrEK;;AU6CL;EACE;EACA,SV/CG;EUgDH;EACA;EACA,eVtCY;;AUyCd;AAAA;EAEE;EACA;EACA;;;AAwBF;AAAA;EAEE;EACA,SVpFG;EUqFH;EACA;EACA,eV3EY;;;AUmFhB;EACE;EACA;EACA;EACA;;AAEA;AAAA;EAEE;EACA;EACA,kBb/KoB;EagLpB;;AZ9KF;AAAA;EACE;;ACEA;EWsKF;AAAA;IZpKE;;;AY8KF;EACE;EACA,eVjHG;EUkHH,cVlHG;;AUqHL;EACE;EACA;;;AAKJ;AAAA;EAEE,SV9HK;EU+HL,eV/HK;EUgIL;EACA;EACA,eVtHc;;AUwHd;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAIE;EACA;EACA;EACA;EACA;EACA;EACA;;;AAKJ;EACE;EACA;EACA;;;AAIF;AAAA;EAEE,YblOsB;EaqOpB,ObpOoB;;;Aa2OxB;EACE,Yb7OsB;;;AcLxB;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAKF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;ACvOF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAKF;EACE;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;;;AbrBE;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;AAQR;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAKF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AdhHA;EACE;;ACYA;EcZJ;IfII;;;;AAKF;EACE;;ACEA;EcRJ;IfUI;;;;AAKF;EACE;;ACRA;EcJJ;IfgBI;;;;AAKF;EACE;;AClBA;EcAJ;IfsBI;;;;AAKF;EACE;;AC5BA;EcIJ;If4BI;;;;AAKF;EACE;;ACtCA;EcQJ;IfkCI;IACA,aEhDuB;;;;AFqDzB;EACE;EACA,aEvDuB;;ADKvB;EcYJ;If0CI;;;;AAKF;EACE;EACA,aElEuB;;ADKvB;EcgBJ;IfiDI;;;;AAKF;EACE;EACA,aE7EuB;;ADKvB;EcoBJ;IfwDI;;;;AAKF;EACE;EACA,aExFuB;;ADKvB;EcwBJ;If+DI;;;;Ae3DJ;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE,abxDiB;;;Aa2DnB;EACE,ab1DyB;;;Aa6D3B;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AC/EF;EACE;EACA;EACA;;AAGE;EACE;;;ACLN;EACE;EACA;;;AAQA;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AhBlCA;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AAaN;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AhB7GA;EgBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhB/IJ;EgBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhB/IJ;EgBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhB/IJ;EgBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhB/IJ;EgBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AC3JR;EACE;AAAA;AAAA;AAAA;AAAA;AAAA;IAME;;EAGF;IACE;IACA;;EAGF;IACE;IACA;IACA;;EAGF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;;EAGF;IACE;;EAGF;IACE;IACA;;;ACvCJ;EACE;EACA;EACA;EACA;EACA;EACA;EACA;;;AAGF;AAAA;EAEE,OpBXW;EoBYX,kBjBkBY;EiBjBZ;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;;;ACpBF;EACE,kBlByBY;;;AkBtBd;EACI;EACA;EACA,elB4EY;EkB3EZ;EACA;;AAEA;EACI,OlB8BI;EkB7BJ;EACA;EACA;EACA;EACA;EACA;;AAGJ;EACE,OlBoBM;EkBnBN;EACA;EACA;EACA;EACA;;;AAIN;EACI;EACA;EACA,elBiDY;EkBhDZ;EACA;;AACA;EACE;EACA;EACA,OlBEM;EkBDN;EACA;EACA;EACA;EACA;;;AAIN;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAIJ;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAMJ;EACI;EACA;EACA,elBGY;EkBFZ;EACA;;AAEA;EACI,OlB/CG;EkBgDH;EACA;EACA;EACA;EACA;EACA;;AAGJ;EACE,OlBzDK;EkB0DL;EACA;EACA;EACA;EACA;;;AAIN;EACI;EACA;EACA,elBxBY;EkByBZ;EACA;;AACA;EACE;EACA;EACA,OlB3EK;EkB4EL;EACA;EACA;EACA;EACA;;;AAIN;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAIJ;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAMJ;EACI;EACA;EACA,elBtEY;EkBuEZ;EACA;;AAEA;EACI,OlBhHK;EkBiHL;EACA;EACA;EACA;EACA;EACA;;AAGJ;EACE,OlB1HO;EkB2HP;EACA;EACA;EACA;EACA;;;AAIN;EACI;EACA;EACA,elBjGY;EkBkGZ;EACA;;AACA;EACE;EACA;EACA,OlB5IO;EkB6IP;EACA;EACA;EACA;EACA;;;AAIN;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAIJ;EACE;EACA;;AAEA;EACE;;AAGF;EACE","sourcesContent":["/*\ngenerated by accessible-pygments \nCopyright (c) 2022, Quansight Labs\nLicensed under the BSD license, see LICENSE for details.\n--\ngenerated by Pygments \nCopyright 2006-2025 by the Pygments team.\nLicensed under the BSD license, see LICENSE for details.\n*/\n\n.highlight .hll { background-color: #0969da4a }\n.highlight .c { color: #6E7781 } /* Comment */\n.highlight .err { color: #CF222E } /* Error */\n.highlight .k { color: #CF222E } /* Keyword */\n.highlight .l { color: #953800 } /* Literal */\n.highlight .n { color: #8250DF } /* Name */\n.highlight .o { color: #116329 } /* Operator */\n.highlight .p { color: #24292F } /* Punctuation */\n.highlight .ch { color: #6E7781 } /* Comment.Hashbang */\n.highlight .cm { color: #6E7781 } /* Comment.Multiline */\n.highlight .cp { color: #6E7781 } /* Comment.Preproc */\n.highlight .cpf { color: #6E7781 } /* Comment.PreprocFile */\n.highlight .c1 { color: #6E7781 } /* Comment.Single */\n.highlight .cs { color: #6E7781 } /* Comment.Special */\n.highlight .gd { color: #0550AE } /* Generic.Deleted */\n.highlight .ge { font-style: italic } /* Generic.Emph */\n.highlight .gr { color: #CF222E } /* Generic.Error */\n.highlight .gh { color: #0550AE } /* Generic.Heading */\n.highlight .gs { font-weight: bold } /* Generic.Strong */\n.highlight .gu { color: #0550AE } /* Generic.Subheading */\n.highlight .kc { color: #0550AE } /* Keyword.Constant */\n.highlight .kd { color: #CF222E } /* Keyword.Declaration */\n.highlight .kn { color: #CF222E } /* Keyword.Namespace */\n.highlight .kp { color: #CF222E } /* Keyword.Pseudo */\n.highlight .kr { color: #CF222E } /* Keyword.Reserved */\n.highlight .kt { color: #CF222E } /* Keyword.Type */\n.highlight .ld { color: #953800 } /* Literal.Date */\n.highlight .m { color: #953800 } /* Literal.Number */\n.highlight .s { color: #0550AE } /* Literal.String */\n.highlight .na { color: #953800 } /* Name.Attribute */\n.highlight .nb { color: #953800 } /* Name.Builtin */\n.highlight .nc { color: #0550AE } /* Name.Class */\n.highlight .no { color: #0550AE } /* Name.Constant */\n.highlight .nd { color: #953800 } /* Name.Decorator */\n.highlight .ni { color: #116329 } /* Name.Entity */\n.highlight .ne { color: #8250DF } /* Name.Exception */\n.highlight .nf { color: #0550AE } /* Name.Function */\n.highlight .nl { color: #953800 } /* Name.Label */\n.highlight .nn { color: #24292F } /* Name.Namespace */\n.highlight .nx { color: #8250DF } /* Name.Other */\n.highlight .py { color: #0550AE } /* Name.Property */\n.highlight .nt { color: #116329 } /* Name.Tag */\n.highlight .nv { color: #953800 } /* Name.Variable */\n.highlight .ow { color: #8250DF } /* Operator.Word */\n.highlight .pm { color: #24292F } /* Punctuation.Marker */\n.highlight .w { color: #24292F } /* Text.Whitespace */\n.highlight .mb { color: #953800 } /* Literal.Number.Bin */\n.highlight .mf { color: #953800 } /* Literal.Number.Float */\n.highlight .mh { color: #953800 } /* Literal.Number.Hex */\n.highlight .mi { color: #953800 } /* Literal.Number.Integer */\n.highlight .mo { color: #953800 } /* Literal.Number.Oct */\n.highlight .sa { color: #0550AE } /* Literal.String.Affix */\n.highlight .sb { color: #0550AE } /* Literal.String.Backtick */\n.highlight .sc { color: #0550AE } /* Literal.String.Char */\n.highlight .dl { color: #0550AE } /* Literal.String.Delimiter */\n.highlight .sd { color: #0550AE } /* Literal.String.Doc */\n.highlight .s2 { color: #0550AE } /* Literal.String.Double */\n.highlight .se { color: #0550AE } /* Literal.String.Escape */\n.highlight .sh { color: #0550AE } /* Literal.String.Heredoc */\n.highlight .si { color: #0550AE } /* Literal.String.Interpol */\n.highlight .sx { color: #0550AE } /* Literal.String.Other */\n.highlight .sr { color: #0550AE } /* Literal.String.Regex */\n.highlight .s1 { color: #0550AE } /* Literal.String.Single */\n.highlight .ss { color: #0550AE } /* Literal.String.Symbol */\n.highlight .bp { color: #953800 } /* Name.Builtin.Pseudo */\n.highlight .fm { color: #0550AE } /* Name.Function.Magic */\n.highlight .vc { color: #953800 } /* Name.Variable.Class */\n.highlight .vg { color: #953800 } /* Name.Variable.Global */\n.highlight .vi { color: #953800 } /* Name.Variable.Instance */\n.highlight .vm { color: #953800 } /* Name.Variable.Magic */\n.highlight .il { color: #953800 } /* Literal.Number.Integer.Long */\n","/*\ngenerated by accessible-pygments \nCopyright (c) 2022, Quansight Labs\nLicensed under the BSD license, see LICENSE for details.\n--\ngenerated by Pygments \nCopyright 2006-2025 by the Pygments team.\nLicensed under the BSD license, see LICENSE for details.\n*/\n\n.highlight .hll { background-color: #6e7681 }\n.highlight { background: #0d1117; color: #E6EDF3 }\n.highlight .c { color: #8B949E; font-style: italic } /* Comment */\n.highlight .err { color: #F85149 } /* Error */\n.highlight .esc { color: #E6EDF3 } /* Escape */\n.highlight .g { color: #E6EDF3 } /* Generic */\n.highlight .k { color: #FF7B72 } /* Keyword */\n.highlight .l { color: #A5D6FF } /* Literal */\n.highlight .n { color: #E6EDF3 } /* Name */\n.highlight .o { color: #FF7B72; font-weight: bold } /* Operator */\n.highlight .x { color: #E6EDF3 } /* Other */\n.highlight .p { color: #E6EDF3 } /* Punctuation */\n.highlight .ch { color: #8B949E; font-style: italic } /* Comment.Hashbang */\n.highlight .cm { color: #8B949E; font-style: italic } /* Comment.Multiline */\n.highlight .cp { color: #8B949E; font-weight: bold; font-style: italic } /* Comment.Preproc */\n.highlight .cpf { color: #8B949E; font-style: italic } /* Comment.PreprocFile */\n.highlight .c1 { color: #8B949E; font-style: italic } /* Comment.Single */\n.highlight .cs { color: #8B949E; font-weight: bold; font-style: italic } /* Comment.Special */\n.highlight .gd { color: #FFA198; background-color: #490202 } /* Generic.Deleted */\n.highlight .ge { color: #E6EDF3; font-style: italic } /* Generic.Emph */\n.highlight .ges { color: #E6EDF3; font-weight: bold; font-style: italic } /* Generic.EmphStrong */\n.highlight .gr { color: #FFA198 } /* Generic.Error */\n.highlight .gh { color: #79C0FF; font-weight: bold } /* Generic.Heading */\n.highlight .gi { color: #56D364; background-color: #0F5323 } /* Generic.Inserted */\n.highlight .go { color: #8B949E } /* Generic.Output */\n.highlight .gp { color: #8B949E } /* Generic.Prompt */\n.highlight .gs { color: #E6EDF3; font-weight: bold } /* Generic.Strong */\n.highlight .gu { color: #79C0FF } /* Generic.Subheading */\n.highlight .gt { color: #FF7B72 } /* Generic.Traceback */\n.highlight .g-Underline { color: #E6EDF3; text-decoration: underline } /* Generic.Underline */\n.highlight .kc { color: #79C0FF } /* Keyword.Constant */\n.highlight .kd { color: #FF7B72 } /* Keyword.Declaration */\n.highlight .kn { color: #FF7B72 } /* Keyword.Namespace */\n.highlight .kp { color: #79C0FF } /* Keyword.Pseudo */\n.highlight .kr { color: #FF7B72 } /* Keyword.Reserved */\n.highlight .kt { color: #FF7B72 } /* Keyword.Type */\n.highlight .ld { color: #79C0FF } /* Literal.Date */\n.highlight .m { color: #A5D6FF } /* Literal.Number */\n.highlight .s { color: #A5D6FF } /* Literal.String */\n.highlight .na { color: #E6EDF3 } /* Name.Attribute */\n.highlight .nb { color: #E6EDF3 } /* Name.Builtin */\n.highlight .nc { color: #F0883E; font-weight: bold } /* Name.Class */\n.highlight .no { color: #79C0FF; font-weight: bold } /* Name.Constant */\n.highlight .nd { color: #D2A8FF; font-weight: bold } /* Name.Decorator */\n.highlight .ni { color: #FFA657 } /* Name.Entity */\n.highlight .ne { color: #F0883E; font-weight: bold } /* Name.Exception */\n.highlight .nf { color: #D2A8FF; font-weight: bold } /* Name.Function */\n.highlight .nl { color: #79C0FF; font-weight: bold } /* Name.Label */\n.highlight .nn { color: #FF7B72 } /* Name.Namespace */\n.highlight .nx { color: #E6EDF3 } /* Name.Other */\n.highlight .py { color: #79C0FF } /* Name.Property */\n.highlight .nt { color: #7EE787 } /* Name.Tag */\n.highlight .nv { color: #79C0FF } /* Name.Variable */\n.highlight .ow { color: #FF7B72; font-weight: bold } /* Operator.Word */\n.highlight .pm { color: #E6EDF3 } /* Punctuation.Marker */\n.highlight .w { color: #6E7681 } /* Text.Whitespace */\n.highlight .mb { color: #A5D6FF } /* Literal.Number.Bin */\n.highlight .mf { color: #A5D6FF } /* Literal.Number.Float */\n.highlight .mh { color: #A5D6FF } /* Literal.Number.Hex */\n.highlight .mi { color: #A5D6FF } /* Literal.Number.Integer */\n.highlight .mo { color: #A5D6FF } /* Literal.Number.Oct */\n.highlight .sa { color: #79C0FF } /* Literal.String.Affix */\n.highlight .sb { color: #A5D6FF } /* Literal.String.Backtick */\n.highlight .sc { color: #A5D6FF } /* Literal.String.Char */\n.highlight .dl { color: #79C0FF } /* Literal.String.Delimiter */\n.highlight .sd { color: #A5D6FF } /* Literal.String.Doc */\n.highlight .s2 { color: #A5D6FF } /* Literal.String.Double */\n.highlight .se { color: #79C0FF } /* Literal.String.Escape */\n.highlight .sh { color: #79C0FF } /* Literal.String.Heredoc */\n.highlight .si { color: #A5D6FF } /* Literal.String.Interpol */\n.highlight .sx { color: #A5D6FF } /* Literal.String.Other */\n.highlight .sr { color: #79C0FF } /* Literal.String.Regex */\n.highlight .s1 { color: #A5D6FF } /* Literal.String.Single */\n.highlight .ss { color: #A5D6FF } /* Literal.String.Symbol */\n.highlight .bp { color: #E6EDF3 } /* Name.Builtin.Pseudo */\n.highlight .fm { color: #D2A8FF; font-weight: bold } /* Name.Function.Magic */\n.highlight .vc { color: #79C0FF } /* Name.Variable.Class */\n.highlight .vg { color: #79C0FF } /* Name.Variable.Global */\n.highlight .vi { color: #79C0FF } /* Name.Variable.Instance */\n.highlight .vm { color: #79C0FF } /* Name.Variable.Magic */\n.highlight .il { color: #A5D6FF } /* Literal.Number.Integer.Long */\n","/*! normalize.css v8.0.1 | MIT License | github.com/necolas/normalize.css */\n\n/* Document\n ========================================================================== */\n\n/**\n * 1. Correct the line height in all browsers.\n * 2. Prevent adjustments of font size after orientation changes in iOS.\n */\n\nhtml {\n line-height: 1.15; /* 1 */\n text-size-adjust: 100%; /* 2 */\n}\n\n/* Sections\n ========================================================================== */\n\n/**\n * Remove the margin in all browsers.\n */\n\nbody {\n margin: 0;\n}\n\n/**\n * Render the `main` element consistently in IE.\n */\n\nmain {\n display: block;\n}\n\n/**\n * Correct the font size and margin on `h1` elements within `section` and\n * `article` contexts in Chrome, Firefox, and Safari.\n */\n\nh1 {\n font-size: 2em;\n margin: 0.67em 0;\n}\n\n/* Grouping content\n ========================================================================== */\n\n/**\n * 1. Add the correct box sizing in Firefox.\n * 2. Show the overflow in Edge and IE.\n */\n\nhr {\n box-sizing: content-box; /* 1 */\n height: 0; /* 1 */\n overflow: visible; /* 2 */\n}\n\n/**\n * 1. Correct the inheritance and scaling of font size in all browsers.\n * 2. Correct the odd `em` font sizing in all browsers.\n */\n\npre {\n font-family: monospace; /* 1 */\n font-size: 1em; /* 2 */\n}\n\n/* Text-level semantics\n ========================================================================== */\n\n/**\n * Remove the gray background on active links in IE 10.\n */\n\na {\n background-color: transparent;\n}\n\n/**\n * 1. Remove the bottom border in Chrome 57-\n * 2. Add the correct text decoration in Chrome, Edge, IE, Opera, and Safari.\n */\n\nabbr[title] {\n border-bottom: none; /* 1 */\n text-decoration: underline; /* 2 */\n text-decoration: underline dotted; /* 2 */\n}\n\n/**\n * Add the correct font weight in Chrome, Edge, and Safari.\n */\n\nb,\nstrong {\n font-weight: bolder;\n}\n\n/**\n * 1. Correct the inheritance and scaling of font size in all browsers.\n * 2. Correct the odd `em` font sizing in all browsers.\n */\n\ncode,\nkbd,\nsamp {\n font-family: monospace; /* 1 */\n font-size: 1em; /* 2 */\n}\n\n/**\n * Add the correct font size in all browsers.\n */\n\nsmall {\n font-size: 80%;\n}\n\n/**\n * Prevent `sub` and `sup` elements from affecting the line height in\n * all browsers.\n */\n\nsub,\nsup {\n font-size: 75%;\n line-height: 0;\n position: relative;\n vertical-align: baseline;\n}\n\nsub {\n bottom: -0.25em;\n}\n\nsup {\n top: -0.5em;\n}\n\n/* Embedded content\n ========================================================================== */\n\n/**\n * Remove the border on images inside links in IE 10.\n */\n\nimg {\n border-style: none;\n}\n\n/* Forms\n ========================================================================== */\n\n/**\n * 1. Change the font styles in all browsers.\n * 2. Remove the margin in Firefox and Safari.\n */\n\nbutton,\ninput,\noptgroup,\nselect,\ntextarea {\n font-family: inherit; /* 1 */\n font-size: 100%; /* 1 */\n line-height: 1.15; /* 1 */\n margin: 0; /* 2 */\n}\n\n/**\n * Show the overflow in IE.\n * 1. Show the overflow in Edge.\n */\n\nbutton,\ninput {\n /* 1 */\n overflow: visible;\n}\n\n/**\n * Remove the inheritance of text transform in Edge, Firefox, and IE.\n * 1. Remove the inheritance of text transform in Firefox.\n */\n\nbutton,\nselect {\n /* 1 */\n text-transform: none;\n}\n\n/**\n * Correct the inability to style clickable types in iOS and Safari.\n */\n\nbutton,\n[type=\"button\"],\n[type=\"reset\"],\n[type=\"submit\"] {\n appearance: button;\n}\n\n/**\n * Remove the inner border and padding in Firefox.\n */\n\nbutton::-moz-focus-inner,\n[type=\"button\"]::-moz-focus-inner,\n[type=\"reset\"]::-moz-focus-inner,\n[type=\"submit\"]::-moz-focus-inner {\n border-style: none;\n padding: 0;\n}\n\n/**\n * Restore the focus styles unset by the previous rule.\n */\n\nbutton:-moz-focusring,\n[type=\"button\"]:-moz-focusring,\n[type=\"reset\"]:-moz-focusring,\n[type=\"submit\"]:-moz-focusring {\n outline: 1px dotted ButtonText;\n}\n\n/**\n * Correct the padding in Firefox.\n */\n\nfieldset {\n padding: 0.35em 0.75em 0.625em;\n}\n\n/**\n * 1. Correct the text wrapping in Edge and IE.\n * 2. Correct the color inheritance from `fieldset` elements in IE.\n * 3. Remove the padding so developers are not caught out when they zero out\n * `fieldset` elements in all browsers.\n */\n\nlegend {\n box-sizing: border-box; /* 1 */\n color: inherit; /* 2 */\n display: table; /* 1 */\n max-width: 100%; /* 1 */\n padding: 0; /* 3 */\n white-space: normal; /* 1 */\n}\n\n/**\n * Add the correct vertical alignment in Chrome, Firefox, and Opera.\n */\n\nprogress {\n vertical-align: baseline;\n}\n\n/**\n * Remove the default vertical scrollbar in IE 10+.\n */\n\ntextarea {\n overflow: auto;\n}\n\n/**\n * 1. Add the correct box sizing in IE 10.\n * 2. Remove the padding in IE 10.\n */\n\n[type=\"checkbox\"],\n[type=\"radio\"] {\n box-sizing: border-box; /* 1 */\n padding: 0; /* 2 */\n}\n\n/**\n * Correct the cursor style of increment and decrement buttons in Chrome.\n */\n\n[type=\"number\"]::-webkit-inner-spin-button,\n[type=\"number\"]::-webkit-outer-spin-button {\n height: auto;\n}\n\n/**\n * 1. Correct the odd appearance in Chrome and Safari.\n * 2. Correct the outline style in Safari.\n */\n\n[type=\"search\"] {\n appearance: textfield; /* 1 */\n outline-offset: -2px; /* 2 */\n}\n\n/**\n * Remove the inner padding in Chrome and Safari on macOS.\n */\n\n[type=\"search\"]::-webkit-search-decoration {\n appearance: none;\n}\n\n/**\n * 1. Correct the inability to style clickable types in iOS and Safari.\n * 2. Change font properties to `inherit` in Safari.\n */\n\n::-webkit-file-upload-button {\n appearance: button; /* 1 */\n font: inherit; /* 2 */\n}\n\n/* Interactive\n ========================================================================== */\n\n/*\n * Add the correct display in Edge, IE 10+, and Firefox.\n */\n\ndetails {\n display: block;\n}\n\n/*\n * Add the correct display in all browsers.\n */\n\nsummary {\n display: list-item;\n}\n\n/* Misc\n ========================================================================== */\n\n/**\n * Add the correct display in IE 10+.\n */\n\ntemplate {\n display: none;\n}\n\n/**\n * Add the correct display in IE 10.\n */\n\n[hidden] {\n display: none;\n}\n","// Base element style overrides\n// stylelint-disable selector-no-type, selector-max-type, selector-max-specificity, selector-max-id\n\n:root {\n color-scheme: $color-scheme;\n}\n\n* {\n box-sizing: border-box;\n}\n\nhtml {\n scroll-behavior: smooth;\n\n @include fs-4;\n}\n\nbody {\n font-family: $body-font-family;\n font-size: inherit;\n line-height: $body-line-height;\n color: $body-text-color;\n background-color: $body-background-color;\n overflow-wrap: break-word;\n}\n\nol,\nul,\ndl,\npre,\naddress,\nblockquote,\ntable,\ndiv,\nhr,\nform,\nfieldset,\nnoscript .table-wrapper {\n margin-top: 0;\n}\n\nh1,\nh2,\nh3,\nh4,\nh5,\nh6,\n#toctitle {\n margin-top: 0;\n margin-bottom: 1em;\n font-weight: 500;\n line-height: $body-heading-line-height;\n color: $body-heading-color;\n}\n\np {\n margin-top: 1em;\n margin-bottom: 1em;\n}\n\na {\n color: $link-color;\n text-decoration: none;\n}\n\na:not([class]) {\n text-decoration: underline;\n text-decoration-color: $border-color;\n text-underline-offset: 2px;\n\n &:hover {\n text-decoration-color: rgba($link-color, 0.45);\n }\n}\n\ncode {\n font-family: $mono-font-family;\n font-size: 0.75em;\n line-height: $body-line-height;\n}\n\nfigure,\npre {\n margin: 0;\n}\n\nli {\n margin: 0.25em 0;\n}\n\nimg {\n max-width: 100%;\n height: auto;\n}\n\nhr {\n height: 1px;\n padding: 0;\n margin: $sp-6 0;\n background-color: $border-color;\n border: 0;\n}\n\n// adds a GitHub-style sidebar to blockquotes\nblockquote {\n margin: 10px 0;\n\n // resets user-agent stylesheets for blockquotes\n margin-block-start: 0;\n margin-inline-start: 0;\n padding-left: 1rem;\n border-left: 3px solid $border-color;\n}\n","$color-scheme: dark;\n$body-background-color: $grey-dk-300;\n$body-heading-color: $grey-lt-000;\n$body-text-color: $grey-lt-300;\n$link-color: lighten($blue-000, 10%);\n$nav-child-link-color: $grey-dk-000;\n$sidebar-color: $grey-dk-300;\n$base-button-color: $grey-dk-250;\n$btn-primary-color: $blue-200;\n$code-background-color: #0d1117; // github-dark bg color\n$code-linenumber-color: #e6edf3; // github-dark line number color\n$feedback-color: darken($sidebar-color, 3%);\n$table-background-color: $grey-dk-250;\n$search-background-color: $grey-dk-250;\n$search-result-preview-color: $grey-lt-300;\n$border-color: $grey-dk-200;\n\n@import \"./vendor/accessible-pygments/github-dark\";\n","@mixin fs-1 {\n & {\n font-size: $font-size-1 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-1-sm !important;\n }\n}\n\n@mixin fs-2 {\n & {\n font-size: $font-size-2 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-3 !important;\n }\n}\n\n@mixin fs-3 {\n & {\n font-size: $font-size-3 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-4 !important;\n }\n}\n\n@mixin fs-4 {\n & {\n font-size: $font-size-4 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-5 !important;\n }\n}\n\n@mixin fs-5 {\n & {\n font-size: $font-size-5 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-6 !important;\n }\n}\n\n@mixin fs-6 {\n & {\n font-size: $font-size-6 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-7 !important;\n line-height: $body-heading-line-height;\n }\n}\n\n@mixin fs-7 {\n & {\n font-size: $font-size-7 !important;\n line-height: $body-heading-line-height;\n }\n\n @include mq(sm) {\n font-size: $font-size-8 !important;\n }\n}\n\n@mixin fs-8 {\n & {\n font-size: $font-size-8 !important;\n line-height: $body-heading-line-height;\n }\n\n @include mq(sm) {\n font-size: $font-size-9 !important;\n }\n}\n\n@mixin fs-9 {\n & {\n font-size: $font-size-9 !important;\n line-height: $body-heading-line-height;\n }\n\n @include mq(sm) {\n font-size: $font-size-10 !important;\n }\n}\n\n@mixin fs-10 {\n & {\n font-size: $font-size-10 !important;\n line-height: $body-heading-line-height;\n }\n\n @include mq(sm) {\n font-size: $font-size-10-sm !important;\n }\n}\n","// Media query\n\n// Media query mixin\n// Usage:\n// @include mq(md) {\n// ..medium and up styles\n// }\n@mixin mq($name) {\n // Retrieves the value from the key\n $value: map-get($media-queries, $name);\n\n // If the key exists in the map\n @if $value {\n // Prints a media query based on the value\n @media (min-width: $value) {\n @content;\n }\n } @else {\n @warn \"No value could be retrieved from `#{$media-query}`. Please make sure it is defined in `$media-queries` map.\";\n }\n}\n\n// Responsive container\n\n@mixin container {\n padding-right: $gutter-spacing-sm;\n padding-left: $gutter-spacing-sm;\n\n @include mq(md) {\n padding-right: $gutter-spacing;\n padding-left: $gutter-spacing;\n }\n}\n","// Typography\n\n// prettier-ignore\n$body-font-family: system-ui, -apple-system, blinkmacsystemfont, \"Segoe UI\",\n roboto, \"Helvetica Neue\", arial, sans-serif, \"Segoe UI Emoji\" !default;\n$mono-font-family: \"SFMono-Regular\", menlo, consolas, monospace !default;\n$root-font-size: 16px !default; // DEPRECATED: previously base font-size for rems\n$body-line-height: 1.4 !default;\n$content-line-height: 1.6 !default;\n$body-heading-line-height: 1.25 !default;\n\n// Font size\n// `-sm` suffix is the size at the small (and above) media query\n\n$font-size-1: 0.5625rem !default;\n$font-size-1-sm: 0.625rem !default;\n$font-size-2: 0.6875rem !default; // h4 - uppercased!, h6 not uppercased, text-small\n$font-size-3: 0.75rem !default; // h5\n$font-size-4: 0.875rem !default;\n$font-size-5: 1rem !default; // h3\n$font-size-6: 1.125rem !default; // h2\n$font-size-7: 1.5rem !default;\n$font-size-8: 2rem !default; // h1\n$font-size-9: 2.25rem !default;\n$font-size-10: 2.625rem !default;\n$font-size-10-sm: 3rem !default;\n\n// Colors\n\n$white: #fff !default;\n$grey-dk-000: #959396 !default;\n$grey-dk-100: #5c5962 !default;\n$grey-dk-200: #44434d !default;\n$grey-dk-250: #302d36 !default;\n$grey-dk-300: #27262b !default;\n$grey-lt-000: #f5f6fa !default;\n$grey-lt-100: #eeebee !default;\n$grey-lt-200: #ecebed !default;\n$grey-lt-300: #e6e1e8 !default;\n$purple-000: #7253ed !default;\n$purple-100: #5e41d0 !default;\n$purple-200: #4e26af !default;\n$purple-300: #381885 !default;\n$blue-000: #2c84fa !default;\n$blue-100: #2869e6 !default;\n$blue-200: #264caf !default;\n$blue-300: #183385 !default;\n$green-000: #41d693 !default;\n$green-100: #11b584 !default;\n$green-200: #009c7b !default;\n$green-300: #026e57 !default;\n$yellow-000: #ffeb82 !default;\n$yellow-100: #fadf50 !default;\n$yellow-200: #f7d12e !default;\n$yellow-300: #e7af06 !default;\n$red-000: #f77e7e !default;\n$red-100: #f96e65 !default;\n$red-200: #e94c4c !default;\n$red-300: #dd2e2e !default;\n\n// Spacing\n\n$spacing-unit: 1rem; // 1rem == 16px\n\n$spacers: (\n sp-0: 0,\n sp-1: $spacing-unit * 0.25,\n sp-2: $spacing-unit * 0.5,\n sp-3: $spacing-unit * 0.75,\n sp-4: $spacing-unit,\n sp-5: $spacing-unit * 1.5,\n sp-6: $spacing-unit * 2,\n sp-7: $spacing-unit * 2.5,\n sp-8: $spacing-unit * 3,\n sp-9: $spacing-unit * 3.5,\n sp-10: $spacing-unit * 4,\n) !default;\n$sp-1: map-get($spacers, sp-1) !default; // 0.25 rem == 4px\n$sp-2: map-get($spacers, sp-2) !default; // 0.5 rem == 8px\n$sp-3: map-get($spacers, sp-3) !default; // 0.75 rem == 12px\n$sp-4: map-get($spacers, sp-4) !default; // 1 rem == 16px\n$sp-5: map-get($spacers, sp-5) !default; // 1.5 rem == 24px\n$sp-6: map-get($spacers, sp-6) !default; // 2 rem == 32px\n$sp-7: map-get($spacers, sp-7) !default; // 2.5 rem == 40px\n$sp-8: map-get($spacers, sp-8) !default; // 3 rem == 48px\n$sp-9: map-get($spacers, sp-9) !default; // 3.5 rem == 56px\n$sp-10: map-get($spacers, sp-10) !default; // 4 rem == 64px\n\n// Borders\n\n$border: 1px solid !default;\n$border-radius: 4px !default;\n$border-color: $grey-lt-100 !default;\n\n// Grid system\n\n$gutter-spacing: $sp-6 !default;\n$gutter-spacing-sm: $sp-4 !default;\n$nav-width: 16.5rem !default;\n$nav-width-md: 15.5rem !default;\n$nav-list-item-height: $sp-6 !default;\n$nav-list-item-height-sm: $sp-8 !default;\n$nav-list-expander-right: true;\n$content-width: 50rem !default;\n$header-height: 3.75rem !default;\n$search-results-width: $content-width - $nav-width !default;\n$transition-duration: 400ms;\n\n// Media queries in pixels\n\n$media-queries: (\n xs: 20rem,\n sm: 31.25rem,\n md: $content-width,\n lg: $content-width + $nav-width,\n xl: 87.5rem,\n) !default;\n","// The basic two column layout\n\n.side-bar {\n z-index: 0;\n display: flex;\n flex-wrap: wrap;\n background-color: $sidebar-color;\n\n @include mq(md) {\n flex-flow: column nowrap;\n position: fixed;\n width: $nav-width-md;\n height: 100%;\n border-right: $border $border-color;\n align-items: flex-end;\n }\n\n @include mq(lg) {\n width: calc((100% - #{$nav-width + $content-width}) / 2 + #{$nav-width});\n min-width: $nav-width;\n }\n\n & + .main {\n @include mq(md) {\n margin-left: $nav-width-md;\n }\n\n @include mq(lg) {\n // stylelint-disable function-name-case\n // disable for Max(), we want to use the CSS max() function\n margin-left: Max(\n #{$nav-width},\n calc((100% - #{$nav-width + $content-width}) / 2 + #{$nav-width})\n );\n // stylelint-enable function-name-case\n }\n\n .main-header {\n display: none;\n background-color: $sidebar-color;\n\n @include mq(md) {\n display: flex;\n background-color: $body-background-color;\n }\n\n &.nav-open {\n display: block;\n\n @include mq(md) {\n display: flex;\n }\n }\n }\n }\n}\n\n.main {\n margin: auto;\n\n @include mq(md) {\n position: relative;\n max-width: $content-width;\n }\n}\n\n.main-content-wrap {\n padding-top: $gutter-spacing-sm;\n padding-bottom: $gutter-spacing-sm;\n\n @include container;\n\n @include mq(md) {\n padding-top: $gutter-spacing;\n padding-bottom: $gutter-spacing;\n }\n}\n\n.main-header {\n z-index: 0;\n border-bottom: $border $border-color;\n\n @include mq(md) {\n display: flex;\n justify-content: space-between;\n height: $header-height;\n }\n}\n\n.site-nav,\n.site-header,\n.site-footer {\n width: 100%;\n\n @include mq(lg) {\n width: $nav-width;\n }\n}\n\n.site-nav {\n display: none;\n\n &.nav-open {\n display: block;\n }\n\n @include mq(md) {\n display: block;\n padding-top: $sp-8;\n padding-bottom: $gutter-spacing-sm;\n overflow-y: auto;\n flex: 1 1 auto;\n }\n}\n\n.site-header {\n display: flex;\n min-height: $header-height;\n align-items: center;\n\n @include mq(md) {\n height: $header-height;\n max-height: $header-height;\n border-bottom: $border $border-color;\n }\n}\n\n.site-title {\n flex-grow: 1;\n display: flex;\n height: 100%;\n align-items: center;\n padding-top: $sp-3;\n padding-bottom: $sp-3;\n color: $body-heading-color;\n\n @include container;\n\n @include fs-6;\n\n @include mq(md) {\n padding-top: $sp-2;\n padding-bottom: $sp-2;\n }\n}\n\n@if variable-exists(logo) {\n .site-logo {\n width: 100%;\n height: 100%;\n background-image: url($logo);\n background-repeat: no-repeat;\n background-position: left center;\n background-size: contain;\n }\n}\n\n.site-button {\n display: flex;\n height: 100%;\n padding: $gutter-spacing-sm;\n align-items: center;\n}\n\n@include mq(md) {\n .site-header .site-button {\n display: none;\n }\n}\n\n.site-title:hover {\n background-image: linear-gradient(\n -90deg,\n rgba($feedback-color, 1) 0%,\n rgba($feedback-color, 0.8) 80%,\n rgba($feedback-color, 0) 100%\n );\n}\n\n.site-button:hover {\n background-image: linear-gradient(\n -90deg,\n rgba($feedback-color, 1) 0%,\n rgba($feedback-color, 0.8) 100%\n );\n}\n\n.site-footer {\n position: absolute;\n bottom: 0;\n left: 0;\n padding-top: $sp-4;\n padding-bottom: $sp-4;\n\n @include container;\n\n @include fs-2;\n\n @include mq(md) {\n position: static;\n justify-self: end;\n }\n}\n\n.icon {\n width: $sp-5;\n height: $sp-5;\n color: $link-color;\n}\n","@charset \"UTF-8\";\n\n// Styles for rendered markdown in the .main-content container\n// stylelint-disable selector-no-type, max-nesting-depth, selector-max-compound-selectors, selector-max-type, selector-max-specificity, selector-max-id\n\n.main-content {\n line-height: $content-line-height;\n\n ol,\n ul,\n dl,\n pre,\n address,\n blockquote,\n .table-wrapper {\n margin-top: 0.5em;\n }\n\n a {\n overflow: hidden;\n text-overflow: ellipsis;\n }\n\n ul,\n ol {\n padding-left: 1.5em;\n }\n\n li {\n .highlight {\n margin-top: $sp-1;\n }\n }\n\n ol {\n list-style-type: none;\n counter-reset: step-counter;\n\n > li {\n position: relative;\n\n &::before {\n position: absolute;\n top: 0.2em;\n left: -1.6em;\n color: $grey-dk-000;\n content: counter(step-counter);\n counter-increment: step-counter;\n @include fs-3;\n\n @include mq(sm) {\n top: 0.11em;\n }\n }\n\n ol {\n counter-reset: sub-counter;\n\n > li {\n &::before {\n content: counter(sub-counter, lower-alpha);\n counter-increment: sub-counter;\n }\n }\n }\n }\n }\n\n ul {\n list-style: none;\n\n > li {\n &::before {\n position: absolute;\n margin-left: -1.4em;\n color: $grey-dk-000;\n content: \"•\";\n }\n }\n }\n\n .task-list-item {\n &::before {\n content: \"\";\n }\n }\n\n .task-list-item-checkbox {\n margin-right: 0.6em;\n margin-left: -1.4em;\n\n // The same margin-left is used above for ul > li::before\n }\n\n hr + * {\n margin-top: 0;\n }\n\n h1:first-of-type {\n margin-top: 0.5em;\n }\n\n dl {\n display: grid;\n grid-template: auto / 10em 1fr;\n }\n\n dt,\n dd {\n margin: 0.25em 0;\n }\n\n dt {\n grid-column: 1;\n font-weight: 500;\n text-align: right;\n\n &::after {\n content: \":\";\n }\n }\n\n dd {\n grid-column: 2;\n margin-bottom: 0;\n margin-left: 1em;\n\n blockquote,\n div,\n dl,\n dt,\n h1,\n h2,\n h3,\n h4,\n h5,\n h6,\n li,\n ol,\n p,\n pre,\n table,\n ul,\n .table-wrapper {\n &:first-child {\n margin-top: 0;\n }\n }\n }\n\n dd,\n ol,\n ul {\n dl:first-child {\n dt:first-child,\n dd:nth-child(2) {\n margin-top: 0;\n }\n }\n }\n\n .anchor-heading {\n position: absolute;\n right: -$sp-4;\n width: $sp-5;\n height: 100%;\n padding-right: $sp-1;\n padding-left: $sp-1;\n overflow: visible;\n\n @include mq(md) {\n right: auto;\n left: -$sp-5;\n }\n\n svg {\n display: inline-block;\n width: 100%;\n height: 100%;\n color: $link-color;\n visibility: hidden;\n }\n }\n\n .anchor-heading:hover,\n .anchor-heading:focus,\n h1:hover > .anchor-heading,\n h2:hover > .anchor-heading,\n h3:hover > .anchor-heading,\n h4:hover > .anchor-heading,\n h5:hover > .anchor-heading,\n h6:hover > .anchor-heading {\n svg {\n visibility: visible;\n }\n }\n\n summary {\n cursor: pointer;\n }\n\n h1,\n h2,\n h3,\n h4,\n h5,\n h6,\n #toctitle {\n position: relative;\n margin-top: 1.5em;\n margin-bottom: 0.25em;\n\n + table,\n + .table-wrapper,\n + .code-example,\n + .highlighter-rouge,\n + .sectionbody .listingblock {\n margin-top: 1em;\n }\n\n + p:not(.label) {\n margin-top: 0;\n }\n }\n\n > h1:first-child,\n > h2:first-child,\n > h3:first-child,\n > h4:first-child,\n > h5:first-child,\n > h6:first-child,\n > .sect1:first-child > h2,\n > .sect2:first-child > h3,\n > .sect3:first-child > h4,\n > .sect4:first-child > h5,\n > .sect5:first-child > h6 {\n margin-top: $sp-2;\n }\n}\n","// Main nav, breadcrumb, etc...\n// stylelint-disable selector-no-type, max-nesting-depth, selector-max-compound-selectors, selector-max-type, selector-max-specificity\n\n.nav-list {\n padding: 0;\n margin-top: 0;\n margin-bottom: 0;\n list-style: none;\n\n .nav-list-item {\n position: relative;\n margin: 0;\n\n @include fs-4;\n\n @include mq(md) {\n @include fs-3;\n }\n\n .nav-list-link {\n display: block;\n min-height: $nav-list-item-height-sm;\n padding-top: $sp-1;\n padding-bottom: $sp-1;\n line-height: #{$nav-list-item-height-sm - 2 * $sp-1};\n @if $nav-list-expander-right {\n padding-right: $nav-list-item-height-sm;\n padding-left: $gutter-spacing-sm;\n } @else {\n padding-right: $gutter-spacing-sm;\n padding-left: $nav-list-item-height-sm;\n }\n\n @include mq(md) {\n min-height: $nav-list-item-height;\n line-height: #{$nav-list-item-height - 2 * $sp-1};\n @if $nav-list-expander-right {\n padding-right: $nav-list-item-height;\n padding-left: $gutter-spacing;\n } @else {\n padding-right: $gutter-spacing;\n padding-left: $nav-list-item-height;\n }\n }\n\n &.external > svg {\n width: $sp-4;\n height: $sp-4;\n vertical-align: text-bottom;\n }\n\n &.active {\n font-weight: 600;\n text-decoration: none;\n }\n\n &:hover,\n &.active {\n color: darken($link-color, 5%);\n background-image: linear-gradient(\n -90deg,\n rgba($feedback-color, 1) 0%,\n rgba($feedback-color, 0.8) 80%,\n rgba($feedback-color, 0) 100%\n );\n }\n }\n\n .nav-list-expander {\n position: absolute;\n @if $nav-list-expander-right {\n right: 0;\n }\n\n width: $nav-list-item-height-sm;\n height: $nav-list-item-height-sm;\n padding: #{$nav-list-item-height-sm * 0.25};\n color: $link-color;\n\n @include mq(md) {\n width: $nav-list-item-height;\n height: $nav-list-item-height;\n padding: #{$nav-list-item-height * 0.25};\n }\n\n &:hover {\n background-image: linear-gradient(\n -90deg,\n rgba($feedback-color, 1) 0%,\n rgba($feedback-color, 0.8) 100%\n );\n }\n\n @if $nav-list-expander-right {\n svg {\n transform: rotate(90deg);\n }\n }\n }\n\n > .nav-list {\n display: none;\n padding-left: $sp-3;\n list-style: none;\n\n .nav-list-item {\n position: relative;\n\n .nav-list-link {\n color: $nav-child-link-color;\n }\n\n .nav-list-expander {\n color: $nav-child-link-color;\n }\n }\n }\n\n &.active {\n > .nav-list-expander svg {\n @if $nav-list-expander-right {\n transform: rotate(-90deg);\n } @else {\n transform: rotate(90deg);\n }\n }\n\n > .nav-list {\n display: block;\n }\n }\n }\n}\n\n.nav-category {\n padding: $sp-2 $gutter-spacing-sm;\n font-weight: 600;\n text-align: start;\n text-transform: uppercase;\n border-bottom: $border $border-color;\n @include fs-2;\n\n @include mq(md) {\n padding: $sp-2 $gutter-spacing;\n margin-top: $gutter-spacing-sm;\n text-align: start;\n\n &:first-child {\n margin-top: 0;\n }\n }\n}\n\n.nav-list.nav-category-list {\n > .nav-list-item {\n margin: 0;\n\n > .nav-list {\n padding: 0;\n\n > .nav-list-item {\n > .nav-list-link {\n color: $link-color;\n }\n\n > .nav-list-expander {\n color: $link-color;\n }\n }\n }\n }\n}\n\n// Aux nav\n\n.aux-nav {\n height: 100%;\n overflow-x: auto;\n @include fs-2;\n\n .aux-nav-list {\n display: flex;\n height: 100%;\n padding: 0;\n margin: 0;\n list-style: none;\n }\n\n .aux-nav-list-item {\n display: inline-block;\n height: 100%;\n padding: 0;\n margin: 0;\n }\n\n @include mq(md) {\n padding-right: $gutter-spacing-sm;\n }\n}\n\n// Breadcrumb nav\n\n.breadcrumb-nav {\n @include mq(md) {\n margin-top: -$sp-4;\n }\n}\n\n.breadcrumb-nav-list {\n padding-left: 0;\n margin-bottom: $sp-3;\n list-style: none;\n}\n\n.breadcrumb-nav-list-item {\n display: table-cell;\n @include fs-2;\n\n &::before {\n display: none;\n }\n\n &::after {\n display: inline-block;\n margin-right: $sp-2;\n margin-left: $sp-2;\n color: $grey-dk-000;\n content: \"/\";\n }\n\n &:last-child {\n &::after {\n content: \"\";\n }\n }\n}\n","// Typography\n// stylelint-disable selector-no-type, selector-max-type, selector-max-specificity, selector-max-id\n\nh1,\n.text-alpha {\n font-weight: 300;\n\n @include fs-8;\n}\n\nh2,\n.text-beta,\n#toctitle {\n @include fs-6;\n}\n\nh3,\n.text-gamma {\n @include fs-5;\n}\n\nh4,\n.text-delta {\n font-weight: 400;\n text-transform: uppercase;\n letter-spacing: 0.1em;\n\n @include fs-2;\n}\n\nh4 code {\n text-transform: none;\n}\n\nh5,\n.text-epsilon {\n @include fs-3;\n}\n\nh6,\n.text-zeta {\n @include fs-2;\n}\n\n.text-small {\n @include fs-2;\n}\n\n.text-mono {\n font-family: $mono-font-family !important;\n}\n\n.text-left {\n text-align: left !important;\n}\n\n.text-center {\n text-align: center !important;\n}\n\n.text-right {\n text-align: right !important;\n}\n","// Labels (not the form kind)\n\n// this :not() prevents a style clash with Mermaid.js's\n// diagram labels, which also use .label\n// for more, see https://github.com/just-the-docs/just-the-docs/issues/1272\n// and the accompanying PR\n.label:not(g),\n.label-blue:not(g) {\n display: inline-block;\n padding: 0.16em 0.56em;\n margin-right: $sp-2;\n margin-left: $sp-2;\n color: $white;\n text-transform: uppercase;\n vertical-align: middle;\n background-color: $blue-100;\n border-radius: 12px;\n\n @include fs-2;\n}\n\n.label-green:not(g) {\n background-color: $green-300;\n}\n\n.label-purple:not(g) {\n background-color: $purple-100;\n}\n\n.label-red:not(g) {\n background-color: $red-300;\n}\n\n.label-yellow:not(g) {\n color: $grey-dk-200;\n background-color: $yellow-200;\n}\n","// Buttons and things that look like buttons\n// stylelint-disable color-named\n\n.btn {\n display: inline-block;\n box-sizing: border-box;\n padding: 0.3em 1em;\n margin: 0;\n font-family: inherit;\n font-size: inherit;\n font-weight: 500;\n line-height: 1.5;\n color: $link-color;\n text-decoration: none;\n vertical-align: baseline;\n cursor: pointer;\n background-color: $base-button-color;\n border-width: 0;\n border-radius: $border-radius;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n appearance: none;\n\n &:focus {\n text-decoration: none;\n outline: none;\n box-shadow: 0 0 0 3px rgba(blue, 0.25);\n }\n\n &:focus:hover,\n &.selected:focus {\n box-shadow: 0 0 0 3px rgba(blue, 0.25);\n }\n\n &:hover,\n &.zeroclipboard-is-hover {\n color: darken($link-color, 2%);\n }\n\n &:hover,\n &:active,\n &.zeroclipboard-is-hover,\n &.zeroclipboard-is-active {\n text-decoration: none;\n background-color: darken($base-button-color, 1%);\n }\n\n &:active,\n &.selected,\n &.zeroclipboard-is-active {\n background-color: darken($base-button-color, 3%);\n background-image: none;\n box-shadow: inset 0 2px 4px rgba(0, 0, 0, 0.15);\n }\n\n &.selected:hover {\n background-color: darken(#dcdcdc, 5%);\n }\n\n &:disabled,\n &.disabled {\n &,\n &:hover {\n color: rgba(102, 102, 102, 0.5);\n cursor: default;\n background-color: rgba(229, 229, 229, 0.5);\n background-image: none;\n box-shadow: none;\n }\n }\n}\n\n.btn-outline {\n color: $link-color;\n background: transparent;\n box-shadow: inset 0 0 0 2px $grey-lt-300;\n\n &:hover,\n &:active,\n &.zeroclipboard-is-hover,\n &.zeroclipboard-is-active {\n color: darken($link-color, 4%);\n text-decoration: none;\n background-color: transparent;\n box-shadow: inset 0 0 0 3px $grey-lt-300;\n }\n\n &:focus {\n text-decoration: none;\n outline: none;\n box-shadow:\n inset 0 0 0 2px $grey-dk-100,\n 0 0 0 3px rgba(blue, 0.25);\n }\n\n &:focus:hover,\n &.selected:focus {\n box-shadow: inset 0 0 0 2px $grey-dk-100;\n }\n}\n\n.btn-primary {\n @include btn-color($white, $btn-primary-color);\n}\n\n.btn-purple {\n @include btn-color($white, $purple-100);\n}\n\n.btn-blue {\n @include btn-color($white, $blue-200);\n}\n\n.btn-green {\n @include btn-color($white, $green-300);\n}\n\n.btn-reset {\n background: none;\n border: none;\n margin: 0;\n text-align: inherit;\n font: inherit;\n border-radius: 0;\n appearance: none;\n}\n","// Colored button\n\n@mixin btn-color($fg, $bg) {\n color: $fg;\n background-color: darken($bg, 2%);\n background-image: linear-gradient(lighten($bg, 5%), darken($bg, 2%));\n box-shadow:\n 0 1px 3px rgba(0, 0, 0, 0.25),\n 0 4px 10px rgba(0, 0, 0, 0.12);\n\n &:hover,\n &.zeroclipboard-is-hover {\n color: $fg;\n background-color: darken($bg, 4%);\n background-image: linear-gradient((lighten($bg, 2%), darken($bg, 4%)));\n }\n\n &:active,\n &.selected,\n &.zeroclipboard-is-active {\n background-color: darken($bg, 5%);\n background-image: none;\n box-shadow: inset 0 2px 4px rgba(0, 0, 0, 0.15);\n }\n\n &.selected:hover {\n background-color: darken($bg, 10%);\n }\n}\n","// Search input and autocomplete\n\n.search {\n position: relative;\n z-index: 2;\n flex-grow: 1;\n height: $sp-10;\n padding: $sp-2;\n transition: padding linear #{$transition-duration * 0.5};\n\n @include mq(md) {\n position: relative !important;\n width: auto !important;\n height: 100% !important;\n padding: 0;\n transition: none;\n }\n}\n\n.search-input-wrap {\n position: relative;\n z-index: 1;\n height: $sp-8;\n overflow: hidden;\n border-radius: $border-radius;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n transition: height linear #{$transition-duration * 0.5};\n\n @include mq(md) {\n position: absolute;\n width: 100%;\n max-width: $search-results-width;\n height: 100% !important;\n border-radius: 0;\n box-shadow: none;\n transition: width ease $transition-duration;\n }\n}\n\n.search-input {\n position: absolute;\n width: 100%;\n height: 100%;\n padding: $sp-2 $gutter-spacing-sm $sp-2 #{$gutter-spacing-sm + $sp-5};\n font-size: 1rem;\n color: $body-text-color;\n background-color: $search-background-color;\n border-top: 0;\n border-right: 0;\n border-bottom: 0;\n border-left: 0;\n border-radius: 0;\n\n @include mq(md) {\n padding: $sp-2 $gutter-spacing-sm $sp-2 #{$gutter-spacing + $sp-5};\n font-size: 0.875rem;\n background-color: $body-background-color;\n transition: padding-left linear #{$transition-duration * 0.5};\n }\n\n &:focus {\n outline: 2px solid $link-color;\n outline-offset: -2px;\n\n + .search-label .search-icon {\n color: $link-color;\n }\n }\n}\n\n.search-label {\n position: absolute;\n display: flex;\n height: 100%;\n padding-left: $gutter-spacing-sm;\n\n @include mq(md) {\n padding-left: $gutter-spacing;\n transition: padding-left linear #{$transition-duration * 0.5};\n }\n\n .search-icon {\n width: #{$sp-4 * 1.2};\n height: #{$sp-4 * 1.2};\n align-self: center;\n color: $grey-dk-000;\n }\n}\n\n.search-results {\n position: absolute;\n left: 0;\n display: none;\n width: 100%;\n max-height: calc(100% - #{$sp-10});\n overflow-y: auto;\n background-color: $search-background-color;\n border-bottom-right-radius: $border-radius;\n border-bottom-left-radius: $border-radius;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n\n @include mq(md) {\n top: 100%;\n width: $search-results-width;\n max-height: calc(100vh - 200%) !important;\n }\n}\n\n.search-results-list {\n padding-left: 0;\n margin-bottom: $sp-1;\n list-style: none;\n @include fs-4;\n\n @include mq(md) {\n @include fs-3;\n }\n}\n\n.search-results-list-item {\n padding: 0;\n margin: 0;\n}\n\n.search-result {\n display: block;\n padding: $sp-1 $sp-3;\n\n &:hover,\n &.active {\n background-color: $feedback-color;\n }\n}\n\n.search-result-title {\n display: block;\n padding-top: $sp-2;\n padding-bottom: $sp-2;\n\n @include mq(sm) {\n display: inline-block;\n width: 40%;\n padding-right: $sp-2;\n vertical-align: top;\n }\n}\n\n.search-result-doc {\n display: flex;\n align-items: center;\n word-wrap: break-word;\n\n &.search-result-doc-parent {\n opacity: 0.5;\n @include fs-3;\n\n @include mq(md) {\n @include fs-2;\n }\n }\n\n .search-result-icon {\n width: $sp-4;\n height: $sp-4;\n margin-right: $sp-2;\n color: $link-color;\n flex-shrink: 0;\n }\n\n .search-result-doc-title {\n overflow: auto;\n }\n}\n\n.search-result-section {\n margin-left: #{$sp-4 + $sp-2};\n word-wrap: break-word;\n}\n\n.search-result-rel-url {\n display: block;\n margin-left: #{$sp-4 + $sp-2};\n overflow: hidden;\n color: $search-result-preview-color;\n text-overflow: ellipsis;\n white-space: nowrap;\n @include fs-1;\n}\n\n.search-result-previews {\n display: block;\n padding-top: $sp-2;\n padding-bottom: $sp-2;\n padding-left: $sp-4;\n margin-left: $sp-2;\n color: $search-result-preview-color;\n word-wrap: break-word;\n border-left: $border;\n border-left-color: $border-color;\n @include fs-2;\n\n @include mq(sm) {\n display: inline-block;\n width: 60%;\n padding-left: $sp-2;\n margin-left: 0;\n vertical-align: top;\n }\n}\n\n.search-result-preview + .search-result-preview {\n margin-top: $sp-1;\n}\n\n.search-result-highlight {\n font-weight: bold;\n}\n\n.search-no-result {\n padding: $sp-2 $sp-3;\n @include fs-3;\n}\n\n.search-button {\n position: fixed;\n right: $sp-4;\n bottom: $sp-4;\n display: flex;\n width: $sp-9;\n height: $sp-9;\n background-color: $search-background-color;\n border: 1px solid rgba($link-color, 0.3);\n border-radius: #{$sp-9 * 0.5};\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n align-items: center;\n justify-content: center;\n}\n\n.search-overlay {\n position: fixed;\n top: 0;\n left: 0;\n z-index: 1;\n width: 0;\n height: 0;\n background-color: rgba(0, 0, 0, 0.3);\n opacity: 0;\n transition:\n opacity ease $transition-duration,\n width 0s $transition-duration,\n height 0s $transition-duration;\n}\n\n.search-active {\n .search {\n position: fixed;\n top: 0;\n left: 0;\n width: 100%;\n height: 100%;\n padding: 0;\n }\n\n .search-input-wrap {\n height: $sp-10;\n border-radius: 0;\n\n @include mq(md) {\n width: $search-results-width;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n }\n }\n\n .search-input {\n background-color: $search-background-color;\n\n @include mq(md) {\n padding-left: 2.3rem;\n }\n }\n\n .search-label {\n @include mq(md) {\n padding-left: 0.6rem;\n }\n }\n\n .search-results {\n display: block;\n }\n\n .search-overlay {\n width: 100%;\n height: 100%;\n opacity: 1;\n transition:\n opacity ease $transition-duration,\n width 0s,\n height 0s;\n }\n\n @include mq(md) {\n .main {\n position: fixed;\n right: 0;\n left: 0;\n }\n }\n\n .main-header {\n padding-top: $sp-10;\n\n @include mq(md) {\n padding-top: 0;\n }\n }\n}\n","// Tables\n// stylelint-disable max-nesting-depth, selector-no-type, selector-max-type\n\n.table-wrapper {\n display: block;\n width: 100%;\n max-width: 100%;\n margin-bottom: $sp-5;\n overflow-x: auto;\n border-radius: $border-radius;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n}\n\ntable {\n display: table;\n min-width: 100%;\n border-collapse: separate;\n}\n\nth,\ntd {\n min-width: 7.5rem;\n padding: $sp-2 $sp-3;\n background-color: $table-background-color;\n border-bottom: $border rgba($border-color, 0.5);\n border-left: $border $border-color;\n\n @include fs-3;\n\n &:first-of-type {\n border-left: 0;\n }\n}\n\ntbody {\n tr {\n &:last-of-type {\n th,\n td {\n border-bottom: 0;\n }\n\n td {\n padding-bottom: $sp-3;\n }\n }\n }\n}\n\nthead {\n th {\n border-bottom: $border $border-color;\n }\n}\n","// Code and syntax highlighting\n// stylelint-disable selector-no-qualifying-type, declaration-block-semicolon-newline-after,declaration-block-single-line-max-declarations, selector-no-type, selector-max-type, scss/comment-no-empty\n\n// {% raw %}\n\n// This instruction applies to all queues not within 'pre' or 'figure', avoiding 'code' generated by the highlight.\n:not(pre, figure) {\n & > code {\n padding: 0.2em 0.15em;\n font-weight: 400;\n background-color: $code-background-color;\n border: $border $border-color;\n border-radius: $border-radius;\n }\n}\n\n// Avoid appearance of dark border around visited code links in Safari\na:visited code {\n border-color: $border-color;\n}\n\n// Content structure for highlighted code blocks using fences or Liquid\n//\n// ```[LANG]...```, no kramdown line_numbers:\n// div.[language-LANG.]highlighter-rouge > div.highlight > pre.highlight > code\n//\n// ```[LANG]...```, kramdown line_numbers = true:\n// div.[language-LANG.]highlighter-rouge > div.highlight > pre.highlight > code\n// > div.table-wrapper > table.rouge-table > tbody > tr\n// > td.rouge-gutter.gl > pre.lineno\n// | td.rouge-code > pre\n//\n// {% highlight LANG %}...{% endhighlight %}:\n// figure.highlight > pre > code.language-LANG\n//\n// {% highlight LANG linenos %}...{% endhighlight %}:\n// figure.highlight > pre > code.language-LANG\n// > div.table-wrapper > table.rouge-table > tbody > tr\n// > td.gutter.gl > pre.lineno\n// | td.code > pre\n//\n// ----...---- (AsciiDoc)\n// div.listingblock > div.content > pre.rouge.highlight\n//\n// fix_linenos removes the outermost pre when it encloses table.rouge-table\n//\n// See docs/index-test.md for some tests.\n//\n// No kramdown line_numbers: fences and Liquid highlighting look the same.\n// Kramdown line_numbers = true: fences have a wider gutter than with Liquid?\n\n// ```[LANG]...```\n// or in AsciiDoc:\n//\n// ----\n// ...\n// ----\n\n// the code may appear with 3 different types:\n// container \\ case: default case, code with line number, code with html rendering\n// top level: div.highlighter-rouge, figure.highlight, figure.highlight\n// second level: div.highlight, div.table-wrapper, pre.highlight\n// third level: pre.highlight, td.code, absent\n// last level: code, pre, code (optionality)\n// highlighter level: span, span, span\n// the spacing are only in the second level for case 1, 3 and in the third level for case 2\n// in AsciiDoc, there is a parent container that contains optionally a title and the content.\n\n// select top level container\ndiv.highlighter-rouge,\ndiv.listingblock > div.content,\nfigure.highlight {\n margin-top: 0;\n margin-bottom: $sp-3;\n background-color: $code-background-color;\n border-radius: $border-radius;\n box-shadow: none;\n -webkit-overflow-scrolling: touch;\n position: relative;\n padding: 0;\n\n // copy button (or other button)\n // the button appear only when there is a hover on the code or focus on button\n > button {\n width: $sp-3;\n opacity: 0;\n position: absolute;\n top: 0;\n right: 0;\n padding: $sp-3;\n border: none;\n background: none;\n color: $body-text-color;\n box-sizing: content-box;\n\n svg {\n fill: $body-text-color;\n }\n\n &:active {\n text-decoration: none;\n outline: none;\n opacity: 1;\n }\n\n &:focus {\n opacity: 1;\n outline: 2px solid $link-color;\n }\n }\n\n // the button can be seen by doing a simple hover in the code, there is no need to go over the location of the button\n &:hover {\n > button {\n cursor: copy;\n opacity: 1;\n }\n }\n}\n\n// setting the spacing and scrollbar on the second level for the first case\n// remove all space on the second and third level\n// this is a mixin to accommodate for the slightly different structures generated via Markdown vs AsciiDoc\n@mixin scroll-and-spacing($code-div, $pre-select) {\n #{$code-div} {\n overflow-x: auto;\n padding: $sp-3;\n margin: 0;\n border: 1px solid $body-text-color;\n border-radius: $border-radius;\n }\n\n #{$pre-select},\n code {\n padding: 0;\n margin: 0;\n border: 0;\n }\n}\n\n// for Markdown\ndiv.highlighter-rouge {\n @include scroll-and-spacing(\"div.highlight\", \"pre.highlight\");\n}\n\n// for AsciiDoc. we also need to fix the margins for its parent container.\ndiv.listingblock {\n margin-top: 0;\n margin-bottom: $sp-3;\n\n @include scroll-and-spacing(\"div.content\", \"div.content > pre\");\n}\n\n// {% highlight LANG %}...{% endhighlight %},\n// {% highlight LANG linenos %}...{% endhighlight %}:\n\n// setting the spacing and scrollbar on the second level for the thirt case\n// the css rule are apply only to the last code enviroment\n// setting the scroolbar\nfigure.highlight {\n pre,\n :not(pre) > code {\n overflow-x: auto;\n padding: $sp-3;\n margin: 0;\n border: 1px solid $body-text-color;\n border-radius: $border-radius;\n }\n}\n\n// ```[LANG]...```, kramdown line_numbers = true,\n// {% highlight LANG linenos %}...{% endhighlight %}:\n\n// setting the spacing and scrollbar on the thirt level for the second case\n.highlight .table-wrapper {\n padding: $sp-3 0;\n margin: 0;\n border: 0;\n box-shadow: none;\n\n td,\n pre {\n min-width: 0;\n padding: 0;\n background-color: $code-background-color;\n border: 0;\n\n @include fs-2;\n }\n\n td.gl {\n width: 1em;\n padding-right: $sp-3;\n padding-left: $sp-3;\n }\n\n pre {\n margin: 0;\n line-height: 2;\n }\n}\n\n// Code examples: html render of a code\n.code-example,\n.listingblock > .title {\n padding: $sp-3;\n margin-bottom: $sp-3;\n overflow: auto;\n border: 1px solid $border-color;\n border-radius: $border-radius;\n\n + .highlighter-rouge,\n + .sectionbody .listingblock,\n + .content,\n + figure.highlight {\n position: relative;\n margin-top: -$sp-4;\n border-right: 1px solid $border-color;\n border-bottom: 1px solid $border-color;\n border-left: 1px solid $border-color;\n border-top-left-radius: 0;\n border-top-right-radius: 0;\n }\n}\n\n// Mermaid diagram code blocks should be left unstyled.\ncode.language-mermaid {\n padding: 0;\n background-color: inherit;\n border: 0;\n}\n\n// Override OneDarkJekyll Colors for Code Blocks\n.highlight,\npre.highlight {\n background: $code-background-color; // Code Background\n // For Backwards Compatibility Before $code-linenumber-color was added\n @if variable-exists(code-linenumber-color) {\n color: $code-linenumber-color; // Code Line Numbers\n } @else {\n color: $body-text-color; // Code Line Numbers\n }\n}\n\n// Override OneDarkJekyll Colors for Code Blocks\n.highlight pre {\n background: $code-background-color; // Code Background\n}\n\n// {% endraw %}\n","// Utility classes for colors\n\n// Text colors\n\n.text-grey-dk-000 {\n color: $grey-dk-000 !important;\n}\n\n.text-grey-dk-100 {\n color: $grey-dk-100 !important;\n}\n\n.text-grey-dk-200 {\n color: $grey-dk-200 !important;\n}\n\n.text-grey-dk-250 {\n color: $grey-dk-250 !important;\n}\n\n.text-grey-dk-300 {\n color: $grey-dk-300 !important;\n}\n\n.text-grey-lt-000 {\n color: $grey-lt-000 !important;\n}\n\n.text-grey-lt-100 {\n color: $grey-lt-100 !important;\n}\n\n.text-grey-lt-200 {\n color: $grey-lt-200 !important;\n}\n\n.text-grey-lt-300 {\n color: $grey-lt-300 !important;\n}\n\n.text-blue-000 {\n color: $blue-000 !important;\n}\n\n.text-blue-100 {\n color: $blue-100 !important;\n}\n\n.text-blue-200 {\n color: $blue-200 !important;\n}\n\n.text-blue-300 {\n color: $blue-300 !important;\n}\n\n.text-green-000 {\n color: $green-000 !important;\n}\n\n.text-green-100 {\n color: $green-100 !important;\n}\n\n.text-green-200 {\n color: $green-200 !important;\n}\n\n.text-green-300 {\n color: $green-300 !important;\n}\n\n.text-purple-000 {\n color: $purple-000 !important;\n}\n\n.text-purple-100 {\n color: $purple-100 !important;\n}\n\n.text-purple-200 {\n color: $purple-200 !important;\n}\n\n.text-purple-300 {\n color: $purple-300 !important;\n}\n\n.text-yellow-000 {\n color: $yellow-000 !important;\n}\n\n.text-yellow-100 {\n color: $yellow-100 !important;\n}\n\n.text-yellow-200 {\n color: $yellow-200 !important;\n}\n\n.text-yellow-300 {\n color: $yellow-300 !important;\n}\n\n.text-red-000 {\n color: $red-000 !important;\n}\n\n.text-red-100 {\n color: $red-100 !important;\n}\n\n.text-red-200 {\n color: $red-200 !important;\n}\n\n.text-red-300 {\n color: $red-300 !important;\n}\n\n// Background colors\n\n.bg-grey-dk-000 {\n background-color: $grey-dk-000 !important;\n}\n\n.bg-grey-dk-100 {\n background-color: $grey-dk-100 !important;\n}\n\n.bg-grey-dk-200 {\n background-color: $grey-dk-200 !important;\n}\n\n.bg-grey-dk-250 {\n background-color: $grey-dk-250 !important;\n}\n\n.bg-grey-dk-300 {\n background-color: $grey-dk-300 !important;\n}\n\n.bg-grey-lt-000 {\n background-color: $grey-lt-000 !important;\n}\n\n.bg-grey-lt-100 {\n background-color: $grey-lt-100 !important;\n}\n\n.bg-grey-lt-200 {\n background-color: $grey-lt-200 !important;\n}\n\n.bg-grey-lt-300 {\n background-color: $grey-lt-300 !important;\n}\n\n.bg-blue-000 {\n background-color: $blue-000 !important;\n}\n\n.bg-blue-100 {\n background-color: $blue-100 !important;\n}\n\n.bg-blue-200 {\n background-color: $blue-200 !important;\n}\n\n.bg-blue-300 {\n background-color: $blue-300 !important;\n}\n\n.bg-green-000 {\n background-color: $green-000 !important;\n}\n\n.bg-green-100 {\n background-color: $green-100 !important;\n}\n\n.bg-green-200 {\n background-color: $green-200 !important;\n}\n\n.bg-green-300 {\n background-color: $green-300 !important;\n}\n\n.bg-purple-000 {\n background-color: $purple-000 !important;\n}\n\n.bg-purple-100 {\n background-color: $purple-100 !important;\n}\n\n.bg-purple-200 {\n background-color: $purple-200 !important;\n}\n\n.bg-purple-300 {\n background-color: $purple-300 !important;\n}\n\n.bg-yellow-000 {\n background-color: $yellow-000 !important;\n}\n\n.bg-yellow-100 {\n background-color: $yellow-100 !important;\n}\n\n.bg-yellow-200 {\n background-color: $yellow-200 !important;\n}\n\n.bg-yellow-300 {\n background-color: $yellow-300 !important;\n}\n\n.bg-red-000 {\n background-color: $red-000 !important;\n}\n\n.bg-red-100 {\n background-color: $red-100 !important;\n}\n\n.bg-red-200 {\n background-color: $red-200 !important;\n}\n\n.bg-red-300 {\n background-color: $red-300 !important;\n}\n","// Utility classes for layout\n\n// Display\n\n.d-block {\n display: block !important;\n}\n\n.d-flex {\n display: flex !important;\n}\n\n.d-inline {\n display: inline !important;\n}\n\n.d-inline-block {\n display: inline-block !important;\n}\n\n.d-none {\n display: none !important;\n}\n\n// Screenreader-only\n\n.sr-only {\n position: absolute;\n width: 1px;\n height: 1px;\n padding: 0;\n margin: -1px;\n overflow: hidden;\n clip: rect(0, 0, 0, 0);\n white-space: nowrap;\n border-width: 0;\n}\n\n@each $media-query in map-keys($media-queries) {\n @for $i from 1 through length($spacers) {\n @include mq($media-query) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .d-sm-block, .d-md-none, .d-lg-inline\n .d-#{$media-query}-block {\n display: block !important;\n }\n .d-#{$media-query}-flex {\n display: flex !important;\n }\n .d-#{$media-query}-inline {\n display: inline !important;\n }\n .d-#{$media-query}-inline-block {\n display: inline-block !important;\n }\n .d-#{$media-query}-none {\n display: none !important;\n }\n }\n }\n}\n\n// Horizontal alignment\n\n.float-left {\n float: left !important;\n}\n\n.float-right {\n float: right !important;\n}\n\n.flex-justify-start {\n justify-content: flex-start !important;\n}\n\n.flex-justify-end {\n justify-content: flex-end !important;\n}\n\n.flex-justify-between {\n justify-content: space-between !important;\n}\n\n.flex-justify-around {\n justify-content: space-around !important;\n}\n\n// Vertical alignment\n\n.v-align-baseline {\n vertical-align: baseline !important;\n}\n\n.v-align-bottom {\n vertical-align: bottom !important;\n}\n\n.v-align-middle {\n vertical-align: middle !important;\n}\n\n.v-align-text-bottom {\n vertical-align: text-bottom !important;\n}\n\n.v-align-text-top {\n vertical-align: text-top !important;\n}\n\n.v-align-top {\n vertical-align: top !important;\n}\n","// Utility classes for typography\n\n.fs-1 {\n @include fs-1;\n}\n\n.fs-2 {\n @include fs-2;\n}\n\n.fs-3 {\n @include fs-3;\n}\n\n.fs-4 {\n @include fs-4;\n}\n\n.fs-5 {\n @include fs-5;\n}\n\n.fs-6 {\n @include fs-6;\n}\n\n.fs-7 {\n @include fs-7;\n}\n\n.fs-8 {\n @include fs-8;\n}\n\n.fs-9 {\n @include fs-9;\n}\n\n.fs-10 {\n @include fs-10;\n}\n\n.fw-300 {\n font-weight: 300 !important;\n}\n\n.fw-400 {\n font-weight: 400 !important;\n}\n\n.fw-500 {\n font-weight: 500 !important;\n}\n\n.fw-700 {\n font-weight: 700 !important;\n}\n\n.lh-0 {\n line-height: 0 !important;\n}\n\n.lh-default {\n line-height: $body-line-height;\n}\n\n.lh-tight {\n line-height: $body-heading-line-height;\n}\n\n.ls-5 {\n letter-spacing: 0.05em !important;\n}\n\n.ls-10 {\n letter-spacing: 0.1em !important;\n}\n\n.ls-0 {\n letter-spacing: 0 !important;\n}\n\n.text-uppercase {\n text-transform: uppercase !important;\n}\n","// Utility classes for lists\n\n// stylelint-disable selector-max-type\n\n.list-style-none {\n padding: 0 !important;\n margin: 0 !important;\n list-style: none !important;\n\n li {\n &::before {\n display: none !important;\n }\n }\n}\n","// Utility classes for margins and padding\n\n// stylelint-disable block-opening-brace-space-after, block-opening-brace-space-before\n\n// Margin spacer utilities\n\n.mx-auto {\n margin-right: auto !important;\n margin-left: auto !important;\n}\n\n@for $i from 1 through length($spacers) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .m-0, .m-1, .m-2...\n .m-#{$scale} {\n margin: #{$size} !important;\n }\n .mt-#{$scale} {\n margin-top: #{$size} !important;\n }\n .mr-#{$scale} {\n margin-right: #{$size} !important;\n }\n .mb-#{$scale} {\n margin-bottom: #{$size} !important;\n }\n .ml-#{$scale} {\n margin-left: #{$size} !important;\n }\n\n .mx-#{$scale} {\n margin-right: #{$size} !important;\n margin-left: #{$size} !important;\n }\n\n .my-#{$scale} {\n margin-top: #{$size} !important;\n margin-bottom: #{$size} !important;\n }\n\n .mxn-#{$scale} {\n margin-right: -#{$size} !important;\n margin-left: -#{$size} !important;\n }\n .mx-#{$scale}-auto {\n margin-right: auto !important;\n margin-left: auto !important;\n }\n}\n\n@each $media-query in map-keys($media-queries) {\n @for $i from 1 through length($spacers) {\n @include mq($media-query) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .m-sm-0, .m-md-1, .m-lg-2...\n .m-#{$media-query}-#{$scale} {\n margin: #{$size} !important;\n }\n .mt-#{$media-query}-#{$scale} {\n margin-top: #{$size} !important;\n }\n .mr-#{$media-query}-#{$scale} {\n margin-right: #{$size} !important;\n }\n .mb-#{$media-query}-#{$scale} {\n margin-bottom: #{$size} !important;\n }\n .ml-#{$media-query}-#{$scale} {\n margin-left: #{$size} !important;\n }\n\n .mx-#{$media-query}-#{$scale} {\n margin-right: #{$size} !important;\n margin-left: #{$size} !important;\n }\n\n .my-#{$media-query}-#{$scale} {\n margin-top: #{$size} !important;\n margin-bottom: #{$size} !important;\n }\n\n .mxn-#{$media-query}-#{$scale} {\n margin-right: -#{$size} !important;\n margin-left: -#{$size} !important;\n }\n }\n }\n}\n\n// Padding spacer utilities\n\n@for $i from 1 through length($spacers) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .p-0, .p-1, .p-2...\n .p-#{$scale} {\n padding: #{$size} !important;\n }\n .pt-#{$scale} {\n padding-top: #{$size} !important;\n }\n .pr-#{$scale} {\n padding-right: #{$size} !important;\n }\n .pb-#{$scale} {\n padding-bottom: #{$size} !important;\n }\n .pl-#{$scale} {\n padding-left: #{$size} !important;\n }\n\n .px-#{$scale} {\n padding-right: #{$size} !important;\n padding-left: #{$size} !important;\n }\n\n .py-#{$scale} {\n padding-top: #{$size} !important;\n padding-bottom: #{$size} !important;\n }\n}\n\n@each $media-query in map-keys($media-queries) {\n @include mq($media-query) {\n @for $i from 1 through length($spacers) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .p-sm-0, .p-md-1, .p-lg-2...\n .p-#{$media-query}-#{$scale} {\n padding: #{$size} !important;\n }\n .pt-#{$media-query}-#{$scale} {\n padding-top: #{$size} !important;\n }\n .pr-#{$media-query}-#{$scale} {\n padding-right: #{$size} !important;\n }\n .pb-#{$media-query}-#{$scale} {\n padding-bottom: #{$size} !important;\n }\n .pl-#{$media-query}-#{$scale} {\n padding-left: #{$size} !important;\n }\n\n .px-#{$media-query}-#{$scale} {\n padding-right: #{$size} !important;\n padding-left: #{$size} !important;\n }\n\n .py-#{$media-query}-#{$scale} {\n padding-top: #{$size} !important;\n padding-bottom: #{$size} !important;\n }\n }\n }\n}\n","// stylelint-disable selector-max-specificity, selector-max-id, selector-max-type, selector-no-qualifying-type\n\n@media print {\n .site-footer,\n .site-button,\n #edit-this-page,\n #back-to-top,\n .site-nav,\n .main-header {\n display: none !important;\n }\n\n hr {\n margin-top: 1rem;\n margin-bottom: 1rem;\n }\n\n .side-bar {\n width: 100%;\n height: auto;\n border-right: 0 !important;\n }\n\n .site-header {\n border-bottom: 1px solid $border-color;\n }\n\n .site-title {\n font-size: 1rem !important;\n font-weight: 700 !important;\n }\n\n .text-small {\n font-size: 8pt !important;\n }\n\n pre.highlight {\n border: 1px solid $border-color;\n }\n\n .main {\n max-width: none;\n margin-left: 0;\n }\n}\n","// Skipnav\n// Skip to main content\n\na.skip-to-main {\n left: -999px;\n position: absolute;\n top: auto;\n width: 1px;\n height: 1px;\n overflow: hidden;\n z-index: -999;\n}\n\na.skip-to-main:focus,\na.skip-to-main:active {\n color: $link-color;\n background-color: $body-background-color;\n left: auto;\n top: auto;\n width: 30%;\n height: auto;\n overflow: auto;\n margin: 10px 35%;\n padding: 5px;\n border-radius: 15px;\n border: 4px solid $btn-primary-color;\n text-align: center;\n font-size: 1.2em;\n z-index: 999;\n}\n","\n@import \"./support/support\";\n@import \"./custom/setup\";\n@import \"./color_schemes/light\";\n\n@import \"./color_schemes/dark\";\n\n@import \"./modules\";\ndiv.opaque {\n background-color: $body-background-color;\n}\n\np.tip, blockquote.tip {\n border: 1px $green-300 solid;\n border-left: $border-radius solid $green-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n \n &::before {\n color: $green-300;\n content: \"Tip\";\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n \n > .tip-title {\n color: $green-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\np.tip-title, blockquote.tip-title {\n border: 1px $green-300 solid;\n border-left: $border-radius solid $green-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n > p:first-child {\n margin-top: 0;\n margin-bottom: 0;\n color: $green-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\nblockquote.tip {\n margin-left: 0;\n margin-right: 0;\n\n > p:first-child {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\nblockquote.tip-title {\n margin-left: 0;\n margin-right: 0;\n\n > p:nth-child(2) {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\n\n\np.note, blockquote.note {\n border: 1px $blue-300 solid;\n border-left: $border-radius solid $blue-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n \n &::before {\n color: $blue-300;\n content: \"Note\";\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n \n > .note-title {\n color: $blue-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\np.note-title, blockquote.note-title {\n border: 1px $blue-300 solid;\n border-left: $border-radius solid $blue-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n > p:first-child {\n margin-top: 0;\n margin-bottom: 0;\n color: $blue-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\nblockquote.note {\n margin-left: 0;\n margin-right: 0;\n\n > p:first-child {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\nblockquote.note-title {\n margin-left: 0;\n margin-right: 0;\n\n > p:nth-child(2) {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\n\n\np.warning, blockquote.warning {\n border: 1px $yellow-300 solid;\n border-left: $border-radius solid $yellow-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n \n &::before {\n color: $yellow-300;\n content: \"Warning\";\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n \n > .warning-title {\n color: $yellow-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\np.warning-title, blockquote.warning-title {\n border: 1px $yellow-300 solid;\n border-left: $border-radius solid $yellow-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n > p:first-child {\n margin-top: 0;\n margin-bottom: 0;\n color: $yellow-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\nblockquote.warning {\n margin-left: 0;\n margin-right: 0;\n\n > p:first-child {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\nblockquote.warning-title {\n margin-left: 0;\n margin-right: 0;\n\n > p:nth-child(2) {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\n\n@import \"./custom/custom\";\n\n\n"],"file":"just-the-docs-dark.css"} \ No newline at end of file diff --git a/main/assets/css/just-the-docs-default.css.map b/main/assets/css/just-the-docs-default.css.map index 5a0cb39944..fc009f44d6 100644 --- a/main/assets/css/just-the-docs-default.css.map +++ b/main/assets/css/just-the-docs-default.css.map @@ -1 +1 @@ -{"version":3,"sourceRoot":"","sources":["../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/vendor/accessible-pygments/github-light.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/vendor/normalize.scss/normalize.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/base.scss","../../_sass/color_schemes/meshtastic.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/support/mixins/_typography.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/support/mixins/_layout.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/support/_variables.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/layout.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/content.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/navigation.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/typography.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/labels.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/buttons.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/color_schemes/light.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/support/mixins/_buttons.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/search.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/tables.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/code.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/utilities/_colors.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/utilities/_layout.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/utilities/_typography.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/utilities/_lists.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/utilities/_spacing.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/print.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/skiptomain.scss","just-the-docs-default.scss"],"names":[],"mappings":";AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAUA;EAAkB;;;AAClB;EAAgB;EAAiB;AACjC;EAAkB;EAAiB;AACnC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAkB;EAAiB;AACnC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAqB;AACtC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAoB;AACrC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAgB;EAAiB;AACjC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AChFlC;AAEA;AAAA;AAGA;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAAA;AAKA;EACE;EACA;EACA;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;EACA;;;AAGF;AAAA;AAAA;AAIA;AAAA;EAEE;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;AAAA;EAGE;EACA;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;EAEE;EACA;EACA;EACA;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAAA;AAKA;AAAA;AAAA;AAAA;AAAA;EAKE;EACA;EACA;EACA;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;AAEE;EACA;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;AAEE;EACA;;;AAGF;AAAA;AAAA;AAIA;AAAA;AAAA;AAAA;EAIE;;;AAGF;AAAA;AAAA;AAIA;AAAA;AAAA;AAAA;EAIE;EACA;;;AAGF;AAAA;AAAA;AAIA;AAAA;AAAA;AAAA;EAIE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAOA;EACE;EACA;EACA;EACA;EACA;EACA;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;EAEE;EACA;;;AAGF;AAAA;AAAA;AAIA;AAAA;EAEE;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AC1VF;EACE,cCGa;;;ADAf;EACE;;;AAGF;EACE;;AEmBA;EACE;;AClBA;EHHJ;IEyBI;;;;AFnBJ;EACE,aIfiB;EJgBjB;EACA,aIbiB;EJcjB,OCTgB;EDUhB,kBCZsB;EDatB;;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAYE;;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAOE;EACA;EACA;EACA,aI1CyB;EJ2CzB,OCvCmB;;;AD0CrB;EACE;EACA;;;AAGF;EACE,OC7CW;ED8CX;;;AAGF;EACE;EACA,uBCvCa;EDwCb;;AAEA;EACE;;;AAIJ;EACE,aIvEiB;EJwEjB;EACA,aIvEiB;;;AJ0EnB;AAAA;EAEE;;;AAGF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;EACA;EACA,kBCvEa;EDwEb;;;AAIF;EACE;EAGA;EACA;EACA;EACA;;;AK7GF;EACE;EACA;EACA;EACA,kBJKc;;AEGZ;EEZJ;IAOI;IACA;IACA,ODwFW;ICvFX;IACA;IACA;;;AFAA;EEZJ;IAgBI;IACA,WD+EQ;;;ADpFR;EEQF;IAEI,aD2ES;;;ADrFX;EEQF;IAQI;;;AAOF;EACE;EACA,kBJ5BU;;AEGZ;EEuBA;IAKI;IACA,kBJjCgB;;;AIoClB;EACE;;AFjCJ;EEgCE;IAII;;;;AAOV;EACE;;AF5CE;EE2CJ;IAII;IACA,WDyCY;;;;ACrChB;EACE,aDaK;ECZL,gBDYK;EDvDL,eCuDK;EDtDL,cCsDK;;ADlEH;EEoDJ;IFrCI,eCqDG;IDpDH,cCoDG;;;ADpEH;EEoDJ;IAOI,aDSG;ICRH,gBDQG;;;;ACJP;EACE;EACA;;AFlEE;EEgEJ;IAKI;IACA;IACA,QDmBY;;;;ACfhB;AAAA;AAAA;EAGE;;AF9EE;EE2EJ;AAAA;AAAA;IAMI,ODGQ;;;;ACCZ;EACE;;AAEA;EACE;;AFzFA;EEqFJ;IAQI;IACA,aDxBG;ICyBH,gBD7BG;IC8BH;IACA;;;;AAIJ;EACE;EACA,YDbc;ECcd;;AFxGE;EEqGJ;IAMI,QDjBY;ICkBZ,YDlBY;ICmBZ;;;;AAIJ;EACE;EACA;EACA;EACA;EACA,aDrDK;ECsDL,gBDtDK;ECuDL,OJzHmB;EEYnB,eCuDK;EDtDL,cCsDK;;ADlEH;EEiHJ;IFlGI,eCqDG;IDpDH,cCoDG;;;AF/BL;EACE;;ACtCA;EEiHJ;IHvEI;IACA,aEhDuB;;;ADKvB;EEiHJ;IAcI,aD/DG;ICgEH,gBDhEG;;;;AC+EP;EACE;EACA;EACA,SDhFK;ECiFL;;;AFnJE;EEuJF;IACE;;;AAIJ;EACE;;;AAQF;EACE;;;AAOF;EACE;EACA;EACA;EACA,aD/GK;ECgHL,gBDhHK;EDvDL,eCuDK;EDtDL,cCsDK;;ADlEH;EE6KJ;IF9JI,eCqDG;IDpDH,cCoDG;;;AFvEL;EACE;;ACEA;EE6KJ;IH3KI;;;ACFA;EE6KJ;IAYI;IACA;;;;AAIJ;EACE,OD5HK;EC6HL,QD7HK;EC8HL,OJ/LW;;;AKXb;EACE,aFEoB;;AEApB;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAOE;;AAGF;EACE;EACA;;AAGF;AAAA;EAEE;;AAIA;EACE,YF+CC;;AE3CL;EACE;EACA;;AAEA;EACE;;AAEA;EACE;EACA;EACA;EACA,OFfM;EEgBN;EACA;;AJ1BN;EACE;;ACRA;EG2BE;IJfF;;;ACZA;EG2BE;IAUI;;;AAIJ;EACE;;AAGE;EACE;EACA;;AAOV;EACE;;AAGE;EACE;EACA;EACA,OF7CM;EE8CN;;AAMJ;EACE;;AAIJ;EACE;EACA;;AAKF;EACE;;AAGF;EACE;;AAGF;EACE;EACA;;AAGF;AAAA;EAEE;;AAGF;EACE;EACA;EACA;;AAEA;EACE;;AAIJ;EACE;EACA;EACA;;AAmBE;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EACE;;AASF;AAAA;AAAA;AAAA;AAAA;AAAA;EAEE;;AAKN;EACE;EACA;EACA,OFnFG;EEoFH;EACA,eFzFG;EE0FH,cF1FG;EE2FH;;AH1JA;EGmJF;IAUI;IACA;;;AAGF;EACE;EACA;EACA;EACA,OLnKO;EKoKP;;AAYF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EACE;;AAIJ;EACE;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAOE;EACA;EACA;;AAEA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAKE;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EACE;;AAIJ;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAWE,YF9JG;;;AG3EP;EACE;EACA;EACA;EACA;;AAEA;EACE;EACA;;ALoBF;EACE;;AClBA;EILF;IL2BE;;;ACtBA;EDOF;IACE;;;ACRA;EILF;ILiBE;;;AKPA;EACE;EACA,YH+DC;EG9DD,aHuDC;EGtDD,gBHsDC;EGrDD;EAEE,eH0DD;EGzDC,cHqDD;;ADlEH;EIKA;IAeI,YHgDD;IG/CC;IAEE,eH6CH;IG5CG,cH4CH;;;AGrCD;EACE,OHkCD;EGjCC,QHiCD;EGhCC;;AAGF;EACE;EACA;;AAGF;EAEE;EACA;;AASJ;EACE;EAEE;EAGF,OHUC;EGTD,QHSC;EGRD;EACA,ON7DO;;AEFT;EIsDA;IAYI,OHED;IGDC,QHCD;IGAC;;;AAGF;EACE;;AAQA;EACE;;AAKN;EACE;EACA,cHvBC;EGwBD;;AAEA;EACE;;AAEA;EACE,ONzFa;;AM4Ff;EACE,ON7Fa;;AMmGjB;EAEI;;AAMJ;EACE;;;AAMR;EACE;EACA;EACA;EACA;EACA;;ALhIA;EACE;;ACEA;EIwHJ;ILtHI;;;ACFA;EIwHJ;IASI;IACA,YHhEG;IGiEH;;EAEA;IACE;;;;AAMJ;EACE;;AAEA;EACE;;AAGE;EACE,ONlJG;;AMqJL;EACE,ONtJG;;;AM+Jb;EACE;EACA;;ALtKA;EACE;;ACEA;EIiKJ;IL/JI;;;AKoKF;EACE;EACA;EACA;EACA;EACA;;AAGF;EACE;EACA;EACA;EACA;;AJlLA;EIiKJ;IAqBI,eHpHG;;;;ADlEH;EI4LJ;IAEI;;;;AAIJ;EACE;EACA,eHnIK;EGoIL;;;AAGF;EACE;;AL5MA;EACE;;ACEA;EIwMJ;ILtMI;;;AK0MF;EACE;;AAGF;EACE;EACA,cHlJG;EGmJH,aHnJG;EGoJH,OHpMU;EGqMV;;AAIA;EACE;;;ACrON;AAAA;EAEE;;ANoEA;AAAA;EACE;EACA,aElEuB;;ADKvB;EKXJ;AAAA;IN4EI;;;;AA5BF;AAAA;AAAA;EACE;;ACtCA;EKJJ;AAAA;AAAA;IN8CI;IACA,aEhDuB;;;;AFgCzB;AAAA;EACE;;AC5BA;EKEJ;AAAA;IN8BI;;;;AMzBJ;AAAA;EAEE;EACA;EACA;;ANdA;AAAA;EACE;;ACEA;EKOJ;AAAA;INLI;;;;AMcJ;EACE;;;ANVA;AAAA;EACE;;ACRA;EKoBJ;AAAA;INRI;;;;AAfF;AAAA;EACE;;ACEA;EKyBJ;AAAA;INvBI;;;;AALF;EACE;;ACEA;EK8BJ;IN5BI;;;;AMgCJ;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;ACvDF;AAAA;EAEE;EACA;EACA,cLoEK;EKnEL,aLmEK;EKlEL,OLiBM;EKhBN;EACA;EACA,kBL6BS;EK5BT;;APLA;AAAA;EACE;;ACEA;EMRJ;AAAA;IPUI;;;;AOKJ;EACE,kBL4BU;;;AKzBZ;EACE,kBLcW;;;AKXb;EACE,kBL4BQ;;;AKzBV;EACE,OLFY;EKGZ,kBLkBW;;;AMlDb;EACE;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA,OTIW;ESHX;EACA;EACA;EACA,kBCTkB;EDUlB;EACA,eNyEc;EMxEd,YACE;EAEF;;AAEA;EACE;EACA;EACA;;AAGF;EAEE;;AAGF;EAEE;;AAGF;EAIE;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;AAKA;EAEE;EACA;EACA;EACA;EACA;;;AAKN;EACE,OT1DW;ES2DX;EACA;;AAEA;EAIE;EACA;EACA;EACA;;AAGF;EACE;EACA;EACA,YACE;;AAIJ;EAEE;;;AAIJ;EEnGE,OR0BM;EQzBN;EACA;EACA,YACE;;AAGF;EAEE,ORiBI;EQhBJ;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;;AFgFJ;EEvGE,OR0BM;EQzBN;EACA;EACA,YACE;;AAGF;EAEE,ORiBI;EQhBJ;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;;AFoFJ;EE3GE,OR0BM;EQzBN;EACA;EACA,YACE;;AAGF;EAEE,ORiBI;EQhBJ;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;;AFwFJ;EE/GE,OR0BM;EQzBN;EACA;EACA,YACE;;AAGF;EAEE,ORiBI;EQhBJ;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;;AF4FJ;EACE;EACA;EACA;EACA;EACA;EACA;EACA;;;AG3HF;EACE;EACA;EACA;EACA,QTgFM;ES/EN,STuEK;EStEL;;AVME;EUZJ;IASI;IACA;IACA;IACA;IACA;;;;AAIJ;EACE;EACA;EACA,QT8DK;ES7DL;EACA,eTmEc;ESlEd,YACE;EAEF;;AVdE;EUKJ;IAYI;IACA;IACA,WTwEmB;ISvEnB;IACA;IACA;IACA;;;;AAIJ;EACE;EACA;EACA;EACA;EACA;EACA,OZnCgB;EYoChB,kBZVwB;EYWxB;EACA;EACA;EACA;EACA;;AVvCE;EU2BJ;IAeI;IACA;IACA,kBZhDoB;IYiDpB;;;AAGF;EACE;EACA;;AAEA;EACE,OZnDO;;;AYwDb;EACE;EACA;EACA;EACA,cTIK;;ADlEH;EU0DJ;IAOI,cTGG;ISFH;;;AAGF;EACE;EACA;EACA;EACA,OTzDU;;;AS6Dd;EACE;EACA;EACA;EACA;EACA;EACA;EACA,kBZ5DwB;EY6DxB,4BTRc;ESSd,2BTTc;ESUd,YACE;;AVxFA;EU6EJ;IAeI;IACA,OTFmB;ISGnB;;;;AAIJ;EACE;EACA,eTrCK;ESsCL;;AXpFA;EACE;;AClBA;EUkGJ;IX5EI;;;ACtBA;EDOF;IACE;;;ACRA;EUkGJ;IXtFI;;;;AWiGJ;EACE;EACA;;;AAGF;EACE;EACA;;AAEA;EAEE,kBZnGa;;;AYuGjB;EACE;EACA,aT9DK;ES+DL,gBT/DK;;ADhEH;EU4HJ;IAMI;IACA;IACA,eTpEG;ISqEH;;;;AAIJ;EACE;EACA;EACA;;AAEA;EACE;;AXxIF;EACE;;ACRA;EU8IF;IXlIE;;;ACZA;EDHF;IACE;;;ACEA;EU8IF;IX5IE;;;AWqJF;EACE,OTtFG;ESuFH,QTvFG;ESwFH,cT1FG;ES2FH,OZzJS;EY0JT;;AAGF;EACE;;;AAIJ;EACE;EACA;;;AAGF;EACE;EACA;EACA;EACA,OZtK4B;EYuK5B;EACA;;AX5LA;EACE;;ACYA;EUyKJ;IXjLI;;;;AW2LJ;EACE;EACA,aTrHK;ESsHL,gBTtHK;ESuHL,cTrHK;ESsHL,aTxHK;ESyHL,OZlL4B;EYmL5B;EACA,aT/GO;ESgHP,mBZ9Ka;;ACjBb;EACE;;ACEA;EUmLJ;IXjLI;;;ACFA;EUmLJ;IAaI;IACA;IACA,cTlIG;ISmIH;IACA;;;;AAIJ;EACE,YT1IK;;;AS6IP;EACE;;;AAGF;EACE;;AX1MA;EACE;;ACRA;EUgNJ;IXpMI;;;;AWyMJ;EACE;EACA,OTrJK;ESsJL,QTtJK;ESuJL;EACA,OTnJK;ESoJL,QTpJK;ESqJL,kBZpMwB;EYqMxB;EACA;EACA,YACE;EAEF;EACA;;;AAGF;EACE;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA,YACE;;;AAMF;EACE;EACA;EACA;EACA;EACA;EACA;;AAGF;EACE,QTxLI;ESyLJ;;AVjQA;EU+PF;IAKI,OTzKiB;IS0KjB,YACE;;;AAKN;EACE,kBZpPsB;;AExBtB;EU2QF;IAII;;;AV/QF;EUmRF;IAEI;;;AAIJ;EACE;;AAGF;EACE;EACA;EACA;EACA,YACE;;AVlSF;EUwSA;IACE;IACA;IACA;;;AAIJ;EACE,aTxOI;;ADxEJ;EU+SF;IAII;;;;AC9TN;EACE;EACA;EACA;EACA,eV0EK;EUzEL;EACA,eVkFc;EUjFd,YACE;;;AAIJ;EACE;EACA;EACA;;;AAGF;AAAA;EAEE;EACA;EACA,kBbIuB;EaHvB;EACA;;AZNA;AAAA;EACE;;ACRA;EWOJ;AAAA;IZKI;;;AYKF;AAAA;EACE;;;AAOE;AAAA;EAEE;;AAGF;EACE,gBVkCD;;;AU3BL;EACE;;;AC9CF;EACE;EACA;EACA,kBdcoB;EcbpB;EACA,eX+EY;;;AW1EhB;EACE,cdUa;;;AcyCf;AAAA;AAAA;EAGE;EACA,eXMK;EWLL,kBdlDsB;EcmDtB,eXgBc;EWfd;EACA;EACA;EACA;;AAIA;AAAA;AAAA;EACE,OXLG;EWMH;EACA;EACA;EACA;EACA,SXVG;EWWH;EACA;EACA,OdhFc;EciFd;;AAEA;AAAA;AAAA;EACE,MdpFY;;AcuFd;AAAA;AAAA;EACE;EACA;EACA;;AAGF;AAAA;AAAA;EACE;EACA;;AAMF;AAAA;AAAA;EACE;EACA;;;AASJ;EACE;EACA,SX/CG;EWgDH;EACA;EACA,eXtCY;;AWyCd;AAAA;EAEE;EACA;EACA;;;AAUJ;EACE;EACA,eXrEK;;AW6CL;EACE;EACA,SX/CG;EWgDH;EACA;EACA,eXtCY;;AWyCd;AAAA;EAEE;EACA;EACA;;;AAwBF;AAAA;EAEE;EACA,SXpFG;EWqFH;EACA;EACA,eX3EY;;;AWmFhB;EACE;EACA;EACA;EACA;;AAEA;AAAA;EAEE;EACA;EACA,kBdhKoB;EciKpB;;Ab9KF;AAAA;EACE;;ACEA;EYsKF;AAAA;IbpKE;;;Aa8KF;EACE;EACA,eXjHG;EWkHH,cXlHG;;AWqHL;EACE;EACA;;;AAKJ;AAAA;EAEE,SX9HK;EW+HL,eX/HK;EWgIL;EACA;EACA,eXtHc;;AWwHd;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAIE;EACA;EACA;EACA;EACA;EACA;EACA;;;AAKJ;EACE;EACA;EACA;;;AAIF;AAAA;EAEE,YdnNsB;EcsNpB,OdrNoB;;;Ac4NxB;EACE,Yd9NsB;;;AepBxB;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAKF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;ACvOF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAKF;EACE;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;;;AdrBE;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;AAQR;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAKF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AfhHA;EACE;;ACYA;EeZJ;IhBII;;;;AAKF;EACE;;ACEA;EeRJ;IhBUI;;;;AAKF;EACE;;ACRA;EeJJ;IhBgBI;;;;AAKF;EACE;;AClBA;EeAJ;IhBsBI;;;;AAKF;EACE;;AC5BA;EeIJ;IhB4BI;;;;AAKF;EACE;;ACtCA;EeQJ;IhBkCI;IACA,aEhDuB;;;;AFqDzB;EACE;EACA,aEvDuB;;ADKvB;EeYJ;IhB0CI;;;;AAKF;EACE;EACA,aElEuB;;ADKvB;EegBJ;IhBiDI;;;;AAKF;EACE;EACA,aE7EuB;;ADKvB;EeoBJ;IhBwDI;;;;AAKF;EACE;EACA,aExFuB;;ADKvB;EewBJ;IhB+DI;;;;AgB3DJ;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE,adxDiB;;;Ac2DnB;EACE,ad1DyB;;;Ac6D3B;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AC/EF;EACE;EACA;EACA;;AAGE;EACE;;;ACLN;EACE;EACA;;;AAQA;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AjBlCA;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AAaN;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AjB7GA;EiBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjB/IJ;EiBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjB/IJ;EiBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjB/IJ;EiBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjB/IJ;EiBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AC3JR;EACE;AAAA;AAAA;AAAA;AAAA;AAAA;IAME;;EAGF;IACE;IACA;;EAGF;IACE;IACA;IACA;;EAGF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;;EAGF;IACE;;EAGF;IACE;IACA;;;ACvCJ;EACE;EACA;EACA;EACA;EACA;EACA;EACA;;;AAGF;AAAA;EAEE,OrBCW;EqBAX,kBrBNsB;EqBOtB;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;;;ACnBF;EACE;;;AAGF;EACI;EACA;EACA,enB2EY;EmB1EZ;EACA;;AAEA;EACI,OnB6BI;EmB5BJ;EACA;EACA;EACA;EACA;EACA;;AAGJ;EACE,OnBmBM;EmBlBN;EACA;EACA;EACA;EACA;;;AAIN;EACI;EACA;EACA,enBgDY;EmB/CZ;EACA;;AACA;EACE;EACA;EACA,OnBCM;EmBAN;EACA;EACA;EACA;EACA;;;AAIN;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAIJ;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAMJ;EACI;EACA;EACA,enBEY;EmBDZ;EACA;;AAEA;EACI,OnBhDG;EmBiDH;EACA;EACA;EACA;EACA;EACA;;AAGJ;EACE,OnB1DK;EmB2DL;EACA;EACA;EACA;EACA;;;AAIN;EACI;EACA;EACA,enBzBY;EmB0BZ;EACA;;AACA;EACE;EACA;EACA,OnB5EK;EmB6EL;EACA;EACA;EACA;EACA;;;AAIN;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAIJ;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAMJ;EACI;EACA;EACA,enBvEY;EmBwEZ;EACA;;AAEA;EACI,OnBjHK;EmBkHL;EACA;EACA;EACA;EACA;EACA;;AAGJ;EACE,OnB3HO;EmB4HP;EACA;EACA;EACA;EACA;;;AAIN;EACI;EACA;EACA,enBlGY;EmBmGZ;EACA;;AACA;EACE;EACA;EACA,OnB7IO;EmB8IP;EACA;EACA;EACA;EACA;;;AAIN;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAIJ;EACE;EACA;;AAEA;EACE;;AAGF;EACE","sourcesContent":["/*\ngenerated by accessible-pygments \nCopyright (c) 2022, Quansight Labs\nLicensed under the BSD license, see LICENSE for details.\n--\ngenerated by Pygments \nCopyright 2006-2025 by the Pygments team.\nLicensed under the BSD license, see LICENSE for details.\n*/\n\n.highlight .hll { background-color: #0969da4a }\n.highlight .c { color: #6E7781 } /* Comment */\n.highlight .err { color: #CF222E } /* Error */\n.highlight .k { color: #CF222E } /* Keyword */\n.highlight .l { color: #953800 } /* Literal */\n.highlight .n { color: #8250DF } /* Name */\n.highlight .o { color: #116329 } /* Operator */\n.highlight .p { color: #24292F } /* Punctuation */\n.highlight .ch { color: #6E7781 } /* Comment.Hashbang */\n.highlight .cm { color: #6E7781 } /* Comment.Multiline */\n.highlight .cp { color: #6E7781 } /* Comment.Preproc */\n.highlight .cpf { color: #6E7781 } /* Comment.PreprocFile */\n.highlight .c1 { color: #6E7781 } /* Comment.Single */\n.highlight .cs { color: #6E7781 } /* Comment.Special */\n.highlight .gd { color: #0550AE } /* Generic.Deleted */\n.highlight .ge { font-style: italic } /* Generic.Emph */\n.highlight .gr { color: #CF222E } /* Generic.Error */\n.highlight .gh { color: #0550AE } /* Generic.Heading */\n.highlight .gs { font-weight: bold } /* Generic.Strong */\n.highlight .gu { color: #0550AE } /* Generic.Subheading */\n.highlight .kc { color: #0550AE } /* Keyword.Constant */\n.highlight .kd { color: #CF222E } /* Keyword.Declaration */\n.highlight .kn { color: #CF222E } /* Keyword.Namespace */\n.highlight .kp { color: #CF222E } /* Keyword.Pseudo */\n.highlight .kr { color: #CF222E } /* Keyword.Reserved */\n.highlight .kt { color: #CF222E } /* Keyword.Type */\n.highlight .ld { color: #953800 } /* Literal.Date */\n.highlight .m { color: #953800 } /* Literal.Number */\n.highlight .s { color: #0550AE } /* Literal.String */\n.highlight .na { color: #953800 } /* Name.Attribute */\n.highlight .nb { color: #953800 } /* Name.Builtin */\n.highlight .nc { color: #0550AE } /* Name.Class */\n.highlight .no { color: #0550AE } /* Name.Constant */\n.highlight .nd { color: #953800 } /* Name.Decorator */\n.highlight .ni { color: #116329 } /* Name.Entity */\n.highlight .ne { color: #8250DF } /* Name.Exception */\n.highlight .nf { color: #0550AE } /* Name.Function */\n.highlight .nl { color: #953800 } /* Name.Label */\n.highlight .nn { color: #24292F } /* Name.Namespace */\n.highlight .nx { color: #8250DF } /* Name.Other */\n.highlight .py { color: #0550AE } /* Name.Property */\n.highlight .nt { color: #116329 } /* Name.Tag */\n.highlight .nv { color: #953800 } /* Name.Variable */\n.highlight .ow { color: #8250DF } /* Operator.Word */\n.highlight .pm { color: #24292F } /* Punctuation.Marker */\n.highlight .w { color: #24292F } /* Text.Whitespace */\n.highlight .mb { color: #953800 } /* Literal.Number.Bin */\n.highlight .mf { color: #953800 } /* Literal.Number.Float */\n.highlight .mh { color: #953800 } /* Literal.Number.Hex */\n.highlight .mi { color: #953800 } /* Literal.Number.Integer */\n.highlight .mo { color: #953800 } /* Literal.Number.Oct */\n.highlight .sa { color: #0550AE } /* Literal.String.Affix */\n.highlight .sb { color: #0550AE } /* Literal.String.Backtick */\n.highlight .sc { color: #0550AE } /* Literal.String.Char */\n.highlight .dl { color: #0550AE } /* Literal.String.Delimiter */\n.highlight .sd { color: #0550AE } /* Literal.String.Doc */\n.highlight .s2 { color: #0550AE } /* Literal.String.Double */\n.highlight .se { color: #0550AE } /* Literal.String.Escape */\n.highlight .sh { color: #0550AE } /* Literal.String.Heredoc */\n.highlight .si { color: #0550AE } /* Literal.String.Interpol */\n.highlight .sx { color: #0550AE } /* Literal.String.Other */\n.highlight .sr { color: #0550AE } /* Literal.String.Regex */\n.highlight .s1 { color: #0550AE } /* Literal.String.Single */\n.highlight .ss { color: #0550AE } /* Literal.String.Symbol */\n.highlight .bp { color: #953800 } /* Name.Builtin.Pseudo */\n.highlight .fm { color: #0550AE } /* Name.Function.Magic */\n.highlight .vc { color: #953800 } /* Name.Variable.Class */\n.highlight .vg { color: #953800 } /* Name.Variable.Global */\n.highlight .vi { color: #953800 } /* Name.Variable.Instance */\n.highlight .vm { color: #953800 } /* Name.Variable.Magic */\n.highlight .il { color: #953800 } /* Literal.Number.Integer.Long */\n","/*! normalize.css v8.0.1 | MIT License | github.com/necolas/normalize.css */\n\n/* Document\n ========================================================================== */\n\n/**\n * 1. Correct the line height in all browsers.\n * 2. Prevent adjustments of font size after orientation changes in iOS.\n */\n\nhtml {\n line-height: 1.15; /* 1 */\n text-size-adjust: 100%; /* 2 */\n}\n\n/* Sections\n ========================================================================== */\n\n/**\n * Remove the margin in all browsers.\n */\n\nbody {\n margin: 0;\n}\n\n/**\n * Render the `main` element consistently in IE.\n */\n\nmain {\n display: block;\n}\n\n/**\n * Correct the font size and margin on `h1` elements within `section` and\n * `article` contexts in Chrome, Firefox, and Safari.\n */\n\nh1 {\n font-size: 2em;\n margin: 0.67em 0;\n}\n\n/* Grouping content\n ========================================================================== */\n\n/**\n * 1. Add the correct box sizing in Firefox.\n * 2. Show the overflow in Edge and IE.\n */\n\nhr {\n box-sizing: content-box; /* 1 */\n height: 0; /* 1 */\n overflow: visible; /* 2 */\n}\n\n/**\n * 1. Correct the inheritance and scaling of font size in all browsers.\n * 2. Correct the odd `em` font sizing in all browsers.\n */\n\npre {\n font-family: monospace; /* 1 */\n font-size: 1em; /* 2 */\n}\n\n/* Text-level semantics\n ========================================================================== */\n\n/**\n * Remove the gray background on active links in IE 10.\n */\n\na {\n background-color: transparent;\n}\n\n/**\n * 1. Remove the bottom border in Chrome 57-\n * 2. Add the correct text decoration in Chrome, Edge, IE, Opera, and Safari.\n */\n\nabbr[title] {\n border-bottom: none; /* 1 */\n text-decoration: underline; /* 2 */\n text-decoration: underline dotted; /* 2 */\n}\n\n/**\n * Add the correct font weight in Chrome, Edge, and Safari.\n */\n\nb,\nstrong {\n font-weight: bolder;\n}\n\n/**\n * 1. Correct the inheritance and scaling of font size in all browsers.\n * 2. Correct the odd `em` font sizing in all browsers.\n */\n\ncode,\nkbd,\nsamp {\n font-family: monospace; /* 1 */\n font-size: 1em; /* 2 */\n}\n\n/**\n * Add the correct font size in all browsers.\n */\n\nsmall {\n font-size: 80%;\n}\n\n/**\n * Prevent `sub` and `sup` elements from affecting the line height in\n * all browsers.\n */\n\nsub,\nsup {\n font-size: 75%;\n line-height: 0;\n position: relative;\n vertical-align: baseline;\n}\n\nsub {\n bottom: -0.25em;\n}\n\nsup {\n top: -0.5em;\n}\n\n/* Embedded content\n ========================================================================== */\n\n/**\n * Remove the border on images inside links in IE 10.\n */\n\nimg {\n border-style: none;\n}\n\n/* Forms\n ========================================================================== */\n\n/**\n * 1. Change the font styles in all browsers.\n * 2. Remove the margin in Firefox and Safari.\n */\n\nbutton,\ninput,\noptgroup,\nselect,\ntextarea {\n font-family: inherit; /* 1 */\n font-size: 100%; /* 1 */\n line-height: 1.15; /* 1 */\n margin: 0; /* 2 */\n}\n\n/**\n * Show the overflow in IE.\n * 1. Show the overflow in Edge.\n */\n\nbutton,\ninput {\n /* 1 */\n overflow: visible;\n}\n\n/**\n * Remove the inheritance of text transform in Edge, Firefox, and IE.\n * 1. Remove the inheritance of text transform in Firefox.\n */\n\nbutton,\nselect {\n /* 1 */\n text-transform: none;\n}\n\n/**\n * Correct the inability to style clickable types in iOS and Safari.\n */\n\nbutton,\n[type=\"button\"],\n[type=\"reset\"],\n[type=\"submit\"] {\n appearance: button;\n}\n\n/**\n * Remove the inner border and padding in Firefox.\n */\n\nbutton::-moz-focus-inner,\n[type=\"button\"]::-moz-focus-inner,\n[type=\"reset\"]::-moz-focus-inner,\n[type=\"submit\"]::-moz-focus-inner {\n border-style: none;\n padding: 0;\n}\n\n/**\n * Restore the focus styles unset by the previous rule.\n */\n\nbutton:-moz-focusring,\n[type=\"button\"]:-moz-focusring,\n[type=\"reset\"]:-moz-focusring,\n[type=\"submit\"]:-moz-focusring {\n outline: 1px dotted ButtonText;\n}\n\n/**\n * Correct the padding in Firefox.\n */\n\nfieldset {\n padding: 0.35em 0.75em 0.625em;\n}\n\n/**\n * 1. Correct the text wrapping in Edge and IE.\n * 2. Correct the color inheritance from `fieldset` elements in IE.\n * 3. Remove the padding so developers are not caught out when they zero out\n * `fieldset` elements in all browsers.\n */\n\nlegend {\n box-sizing: border-box; /* 1 */\n color: inherit; /* 2 */\n display: table; /* 1 */\n max-width: 100%; /* 1 */\n padding: 0; /* 3 */\n white-space: normal; /* 1 */\n}\n\n/**\n * Add the correct vertical alignment in Chrome, Firefox, and Opera.\n */\n\nprogress {\n vertical-align: baseline;\n}\n\n/**\n * Remove the default vertical scrollbar in IE 10+.\n */\n\ntextarea {\n overflow: auto;\n}\n\n/**\n * 1. Add the correct box sizing in IE 10.\n * 2. Remove the padding in IE 10.\n */\n\n[type=\"checkbox\"],\n[type=\"radio\"] {\n box-sizing: border-box; /* 1 */\n padding: 0; /* 2 */\n}\n\n/**\n * Correct the cursor style of increment and decrement buttons in Chrome.\n */\n\n[type=\"number\"]::-webkit-inner-spin-button,\n[type=\"number\"]::-webkit-outer-spin-button {\n height: auto;\n}\n\n/**\n * 1. Correct the odd appearance in Chrome and Safari.\n * 2. Correct the outline style in Safari.\n */\n\n[type=\"search\"] {\n appearance: textfield; /* 1 */\n outline-offset: -2px; /* 2 */\n}\n\n/**\n * Remove the inner padding in Chrome and Safari on macOS.\n */\n\n[type=\"search\"]::-webkit-search-decoration {\n appearance: none;\n}\n\n/**\n * 1. Correct the inability to style clickable types in iOS and Safari.\n * 2. Change font properties to `inherit` in Safari.\n */\n\n::-webkit-file-upload-button {\n appearance: button; /* 1 */\n font: inherit; /* 2 */\n}\n\n/* Interactive\n ========================================================================== */\n\n/*\n * Add the correct display in Edge, IE 10+, and Firefox.\n */\n\ndetails {\n display: block;\n}\n\n/*\n * Add the correct display in all browsers.\n */\n\nsummary {\n display: list-item;\n}\n\n/* Misc\n ========================================================================== */\n\n/**\n * Add the correct display in IE 10+.\n */\n\ntemplate {\n display: none;\n}\n\n/**\n * Add the correct display in IE 10.\n */\n\n[hidden] {\n display: none;\n}\n","// Base element style overrides\n// stylelint-disable selector-no-type, selector-max-type, selector-max-specificity, selector-max-id\n\n:root {\n color-scheme: $color-scheme;\n}\n\n* {\n box-sizing: border-box;\n}\n\nhtml {\n scroll-behavior: smooth;\n\n @include fs-4;\n}\n\nbody {\n font-family: $body-font-family;\n font-size: inherit;\n line-height: $body-line-height;\n color: $body-text-color;\n background-color: $body-background-color;\n overflow-wrap: break-word;\n}\n\nol,\nul,\ndl,\npre,\naddress,\nblockquote,\ntable,\ndiv,\nhr,\nform,\nfieldset,\nnoscript .table-wrapper {\n margin-top: 0;\n}\n\nh1,\nh2,\nh3,\nh4,\nh5,\nh6,\n#toctitle {\n margin-top: 0;\n margin-bottom: 1em;\n font-weight: 500;\n line-height: $body-heading-line-height;\n color: $body-heading-color;\n}\n\np {\n margin-top: 1em;\n margin-bottom: 1em;\n}\n\na {\n color: $link-color;\n text-decoration: none;\n}\n\na:not([class]) {\n text-decoration: underline;\n text-decoration-color: $border-color;\n text-underline-offset: 2px;\n\n &:hover {\n text-decoration-color: rgba($link-color, 0.45);\n }\n}\n\ncode {\n font-family: $mono-font-family;\n font-size: 0.75em;\n line-height: $body-line-height;\n}\n\nfigure,\npre {\n margin: 0;\n}\n\nli {\n margin: 0.25em 0;\n}\n\nimg {\n max-width: 100%;\n height: auto;\n}\n\nhr {\n height: 1px;\n padding: 0;\n margin: $sp-6 0;\n background-color: $border-color;\n border: 0;\n}\n\n// adds a GitHub-style sidebar to blockquotes\nblockquote {\n margin: 10px 0;\n\n // resets user-agent stylesheets for blockquotes\n margin-block-start: 0;\n margin-inline-start: 0;\n padding-left: 1rem;\n border-left: 3px solid $border-color;\n}\n","// Meshtastic Material 3 — Light color scheme for just-the-docs\n// Source: core/ui/.../Color.kt §8.2 (Light Scheme)\n//\n// Brand colors:\n// Primary (Light): #2D8F52 (Green 700)\n// Surface (Light): #F5F6FA (Neutral 50)\n\n$color-scheme: light;\n\n// Body / page background\n$body-background-color: #F5F6FA; // Neutral 50 — surfaceLight\n$sidebar-color: #ECEDF3; // Neutral 100 — surfaceContainerLight\n$body-text-color: #2C2D3C; // Neutral 800 — onSurfaceLight\n$body-heading-color: #2C2D3C; // Neutral 800\n\n// Links\n$link-color: #2D8F52; // Green 700 — primaryLight\n$nav-link-color: #2D8F52; // Green 700\n\n// Navigation\n$nav-child-link-color: #555668; // Neutral 600 — secondaryLight\n$search-result-preview-color: #555668;\n\n// Code\n$code-background-color: #ECEDF3; // Neutral 100\n$code-linenumber-color: #9496A6; // Neutral 400\n\n// Borders\n$border-color: #D5D6E0; // Neutral 200 — outlineVariantLight\n$table-background-color: #F5F6FA; // Neutral 50\n\n// Buttons\n$btn-primary-color: #2D8F52; // Green 700\n\n// Feedback / callouts\n$feedback-color: #E0E1EB; // surfaceContainerHighLight\n\n// Search\n$search-background-color: #FFFFFF; // surfaceContainerLowestLight\n","@mixin fs-1 {\n & {\n font-size: $font-size-1 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-1-sm !important;\n }\n}\n\n@mixin fs-2 {\n & {\n font-size: $font-size-2 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-3 !important;\n }\n}\n\n@mixin fs-3 {\n & {\n font-size: $font-size-3 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-4 !important;\n }\n}\n\n@mixin fs-4 {\n & {\n font-size: $font-size-4 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-5 !important;\n }\n}\n\n@mixin fs-5 {\n & {\n font-size: $font-size-5 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-6 !important;\n }\n}\n\n@mixin fs-6 {\n & {\n font-size: $font-size-6 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-7 !important;\n line-height: $body-heading-line-height;\n }\n}\n\n@mixin fs-7 {\n & {\n font-size: $font-size-7 !important;\n line-height: $body-heading-line-height;\n }\n\n @include mq(sm) {\n font-size: $font-size-8 !important;\n }\n}\n\n@mixin fs-8 {\n & {\n font-size: $font-size-8 !important;\n line-height: $body-heading-line-height;\n }\n\n @include mq(sm) {\n font-size: $font-size-9 !important;\n }\n}\n\n@mixin fs-9 {\n & {\n font-size: $font-size-9 !important;\n line-height: $body-heading-line-height;\n }\n\n @include mq(sm) {\n font-size: $font-size-10 !important;\n }\n}\n\n@mixin fs-10 {\n & {\n font-size: $font-size-10 !important;\n line-height: $body-heading-line-height;\n }\n\n @include mq(sm) {\n font-size: $font-size-10-sm !important;\n }\n}\n","// Media query\n\n// Media query mixin\n// Usage:\n// @include mq(md) {\n// ..medium and up styles\n// }\n@mixin mq($name) {\n // Retrieves the value from the key\n $value: map-get($media-queries, $name);\n\n // If the key exists in the map\n @if $value {\n // Prints a media query based on the value\n @media (min-width: $value) {\n @content;\n }\n } @else {\n @warn \"No value could be retrieved from `#{$media-query}`. Please make sure it is defined in `$media-queries` map.\";\n }\n}\n\n// Responsive container\n\n@mixin container {\n padding-right: $gutter-spacing-sm;\n padding-left: $gutter-spacing-sm;\n\n @include mq(md) {\n padding-right: $gutter-spacing;\n padding-left: $gutter-spacing;\n }\n}\n","// Typography\n\n// prettier-ignore\n$body-font-family: system-ui, -apple-system, blinkmacsystemfont, \"Segoe UI\",\n roboto, \"Helvetica Neue\", arial, sans-serif, \"Segoe UI Emoji\" !default;\n$mono-font-family: \"SFMono-Regular\", menlo, consolas, monospace !default;\n$root-font-size: 16px !default; // DEPRECATED: previously base font-size for rems\n$body-line-height: 1.4 !default;\n$content-line-height: 1.6 !default;\n$body-heading-line-height: 1.25 !default;\n\n// Font size\n// `-sm` suffix is the size at the small (and above) media query\n\n$font-size-1: 0.5625rem !default;\n$font-size-1-sm: 0.625rem !default;\n$font-size-2: 0.6875rem !default; // h4 - uppercased!, h6 not uppercased, text-small\n$font-size-3: 0.75rem !default; // h5\n$font-size-4: 0.875rem !default;\n$font-size-5: 1rem !default; // h3\n$font-size-6: 1.125rem !default; // h2\n$font-size-7: 1.5rem !default;\n$font-size-8: 2rem !default; // h1\n$font-size-9: 2.25rem !default;\n$font-size-10: 2.625rem !default;\n$font-size-10-sm: 3rem !default;\n\n// Colors\n\n$white: #fff !default;\n$grey-dk-000: #959396 !default;\n$grey-dk-100: #5c5962 !default;\n$grey-dk-200: #44434d !default;\n$grey-dk-250: #302d36 !default;\n$grey-dk-300: #27262b !default;\n$grey-lt-000: #f5f6fa !default;\n$grey-lt-100: #eeebee !default;\n$grey-lt-200: #ecebed !default;\n$grey-lt-300: #e6e1e8 !default;\n$purple-000: #7253ed !default;\n$purple-100: #5e41d0 !default;\n$purple-200: #4e26af !default;\n$purple-300: #381885 !default;\n$blue-000: #2c84fa !default;\n$blue-100: #2869e6 !default;\n$blue-200: #264caf !default;\n$blue-300: #183385 !default;\n$green-000: #41d693 !default;\n$green-100: #11b584 !default;\n$green-200: #009c7b !default;\n$green-300: #026e57 !default;\n$yellow-000: #ffeb82 !default;\n$yellow-100: #fadf50 !default;\n$yellow-200: #f7d12e !default;\n$yellow-300: #e7af06 !default;\n$red-000: #f77e7e !default;\n$red-100: #f96e65 !default;\n$red-200: #e94c4c !default;\n$red-300: #dd2e2e !default;\n\n// Spacing\n\n$spacing-unit: 1rem; // 1rem == 16px\n\n$spacers: (\n sp-0: 0,\n sp-1: $spacing-unit * 0.25,\n sp-2: $spacing-unit * 0.5,\n sp-3: $spacing-unit * 0.75,\n sp-4: $spacing-unit,\n sp-5: $spacing-unit * 1.5,\n sp-6: $spacing-unit * 2,\n sp-7: $spacing-unit * 2.5,\n sp-8: $spacing-unit * 3,\n sp-9: $spacing-unit * 3.5,\n sp-10: $spacing-unit * 4,\n) !default;\n$sp-1: map-get($spacers, sp-1) !default; // 0.25 rem == 4px\n$sp-2: map-get($spacers, sp-2) !default; // 0.5 rem == 8px\n$sp-3: map-get($spacers, sp-3) !default; // 0.75 rem == 12px\n$sp-4: map-get($spacers, sp-4) !default; // 1 rem == 16px\n$sp-5: map-get($spacers, sp-5) !default; // 1.5 rem == 24px\n$sp-6: map-get($spacers, sp-6) !default; // 2 rem == 32px\n$sp-7: map-get($spacers, sp-7) !default; // 2.5 rem == 40px\n$sp-8: map-get($spacers, sp-8) !default; // 3 rem == 48px\n$sp-9: map-get($spacers, sp-9) !default; // 3.5 rem == 56px\n$sp-10: map-get($spacers, sp-10) !default; // 4 rem == 64px\n\n// Borders\n\n$border: 1px solid !default;\n$border-radius: 4px !default;\n$border-color: $grey-lt-100 !default;\n\n// Grid system\n\n$gutter-spacing: $sp-6 !default;\n$gutter-spacing-sm: $sp-4 !default;\n$nav-width: 16.5rem !default;\n$nav-width-md: 15.5rem !default;\n$nav-list-item-height: $sp-6 !default;\n$nav-list-item-height-sm: $sp-8 !default;\n$nav-list-expander-right: true;\n$content-width: 50rem !default;\n$header-height: 3.75rem !default;\n$search-results-width: $content-width - $nav-width !default;\n$transition-duration: 400ms;\n\n// Media queries in pixels\n\n$media-queries: (\n xs: 20rem,\n sm: 31.25rem,\n md: $content-width,\n lg: $content-width + $nav-width,\n xl: 87.5rem,\n) !default;\n","// The basic two column layout\n\n.side-bar {\n z-index: 0;\n display: flex;\n flex-wrap: wrap;\n background-color: $sidebar-color;\n\n @include mq(md) {\n flex-flow: column nowrap;\n position: fixed;\n width: $nav-width-md;\n height: 100%;\n border-right: $border $border-color;\n align-items: flex-end;\n }\n\n @include mq(lg) {\n width: calc((100% - #{$nav-width + $content-width}) / 2 + #{$nav-width});\n min-width: $nav-width;\n }\n\n & + .main {\n @include mq(md) {\n margin-left: $nav-width-md;\n }\n\n @include mq(lg) {\n // stylelint-disable function-name-case\n // disable for Max(), we want to use the CSS max() function\n margin-left: Max(\n #{$nav-width},\n calc((100% - #{$nav-width + $content-width}) / 2 + #{$nav-width})\n );\n // stylelint-enable function-name-case\n }\n\n .main-header {\n display: none;\n background-color: $sidebar-color;\n\n @include mq(md) {\n display: flex;\n background-color: $body-background-color;\n }\n\n &.nav-open {\n display: block;\n\n @include mq(md) {\n display: flex;\n }\n }\n }\n }\n}\n\n.main {\n margin: auto;\n\n @include mq(md) {\n position: relative;\n max-width: $content-width;\n }\n}\n\n.main-content-wrap {\n padding-top: $gutter-spacing-sm;\n padding-bottom: $gutter-spacing-sm;\n\n @include container;\n\n @include mq(md) {\n padding-top: $gutter-spacing;\n padding-bottom: $gutter-spacing;\n }\n}\n\n.main-header {\n z-index: 0;\n border-bottom: $border $border-color;\n\n @include mq(md) {\n display: flex;\n justify-content: space-between;\n height: $header-height;\n }\n}\n\n.site-nav,\n.site-header,\n.site-footer {\n width: 100%;\n\n @include mq(lg) {\n width: $nav-width;\n }\n}\n\n.site-nav {\n display: none;\n\n &.nav-open {\n display: block;\n }\n\n @include mq(md) {\n display: block;\n padding-top: $sp-8;\n padding-bottom: $gutter-spacing-sm;\n overflow-y: auto;\n flex: 1 1 auto;\n }\n}\n\n.site-header {\n display: flex;\n min-height: $header-height;\n align-items: center;\n\n @include mq(md) {\n height: $header-height;\n max-height: $header-height;\n border-bottom: $border $border-color;\n }\n}\n\n.site-title {\n flex-grow: 1;\n display: flex;\n height: 100%;\n align-items: center;\n padding-top: $sp-3;\n padding-bottom: $sp-3;\n color: $body-heading-color;\n\n @include container;\n\n @include fs-6;\n\n @include mq(md) {\n padding-top: $sp-2;\n padding-bottom: $sp-2;\n }\n}\n\n@if variable-exists(logo) {\n .site-logo {\n width: 100%;\n height: 100%;\n background-image: url($logo);\n background-repeat: no-repeat;\n background-position: left center;\n background-size: contain;\n }\n}\n\n.site-button {\n display: flex;\n height: 100%;\n padding: $gutter-spacing-sm;\n align-items: center;\n}\n\n@include mq(md) {\n .site-header .site-button {\n display: none;\n }\n}\n\n.site-title:hover {\n background-image: linear-gradient(\n -90deg,\n rgba($feedback-color, 1) 0%,\n rgba($feedback-color, 0.8) 80%,\n rgba($feedback-color, 0) 100%\n );\n}\n\n.site-button:hover {\n background-image: linear-gradient(\n -90deg,\n rgba($feedback-color, 1) 0%,\n rgba($feedback-color, 0.8) 100%\n );\n}\n\n.site-footer {\n position: absolute;\n bottom: 0;\n left: 0;\n padding-top: $sp-4;\n padding-bottom: $sp-4;\n\n @include container;\n\n @include fs-2;\n\n @include mq(md) {\n position: static;\n justify-self: end;\n }\n}\n\n.icon {\n width: $sp-5;\n height: $sp-5;\n color: $link-color;\n}\n","@charset \"UTF-8\";\n\n// Styles for rendered markdown in the .main-content container\n// stylelint-disable selector-no-type, max-nesting-depth, selector-max-compound-selectors, selector-max-type, selector-max-specificity, selector-max-id\n\n.main-content {\n line-height: $content-line-height;\n\n ol,\n ul,\n dl,\n pre,\n address,\n blockquote,\n .table-wrapper {\n margin-top: 0.5em;\n }\n\n a {\n overflow: hidden;\n text-overflow: ellipsis;\n }\n\n ul,\n ol {\n padding-left: 1.5em;\n }\n\n li {\n .highlight {\n margin-top: $sp-1;\n }\n }\n\n ol {\n list-style-type: none;\n counter-reset: step-counter;\n\n > li {\n position: relative;\n\n &::before {\n position: absolute;\n top: 0.2em;\n left: -1.6em;\n color: $grey-dk-000;\n content: counter(step-counter);\n counter-increment: step-counter;\n @include fs-3;\n\n @include mq(sm) {\n top: 0.11em;\n }\n }\n\n ol {\n counter-reset: sub-counter;\n\n > li {\n &::before {\n content: counter(sub-counter, lower-alpha);\n counter-increment: sub-counter;\n }\n }\n }\n }\n }\n\n ul {\n list-style: none;\n\n > li {\n &::before {\n position: absolute;\n margin-left: -1.4em;\n color: $grey-dk-000;\n content: \"•\";\n }\n }\n }\n\n .task-list-item {\n &::before {\n content: \"\";\n }\n }\n\n .task-list-item-checkbox {\n margin-right: 0.6em;\n margin-left: -1.4em;\n\n // The same margin-left is used above for ul > li::before\n }\n\n hr + * {\n margin-top: 0;\n }\n\n h1:first-of-type {\n margin-top: 0.5em;\n }\n\n dl {\n display: grid;\n grid-template: auto / 10em 1fr;\n }\n\n dt,\n dd {\n margin: 0.25em 0;\n }\n\n dt {\n grid-column: 1;\n font-weight: 500;\n text-align: right;\n\n &::after {\n content: \":\";\n }\n }\n\n dd {\n grid-column: 2;\n margin-bottom: 0;\n margin-left: 1em;\n\n blockquote,\n div,\n dl,\n dt,\n h1,\n h2,\n h3,\n h4,\n h5,\n h6,\n li,\n ol,\n p,\n pre,\n table,\n ul,\n .table-wrapper {\n &:first-child {\n margin-top: 0;\n }\n }\n }\n\n dd,\n ol,\n ul {\n dl:first-child {\n dt:first-child,\n dd:nth-child(2) {\n margin-top: 0;\n }\n }\n }\n\n .anchor-heading {\n position: absolute;\n right: -$sp-4;\n width: $sp-5;\n height: 100%;\n padding-right: $sp-1;\n padding-left: $sp-1;\n overflow: visible;\n\n @include mq(md) {\n right: auto;\n left: -$sp-5;\n }\n\n svg {\n display: inline-block;\n width: 100%;\n height: 100%;\n color: $link-color;\n visibility: hidden;\n }\n }\n\n .anchor-heading:hover,\n .anchor-heading:focus,\n h1:hover > .anchor-heading,\n h2:hover > .anchor-heading,\n h3:hover > .anchor-heading,\n h4:hover > .anchor-heading,\n h5:hover > .anchor-heading,\n h6:hover > .anchor-heading {\n svg {\n visibility: visible;\n }\n }\n\n summary {\n cursor: pointer;\n }\n\n h1,\n h2,\n h3,\n h4,\n h5,\n h6,\n #toctitle {\n position: relative;\n margin-top: 1.5em;\n margin-bottom: 0.25em;\n\n + table,\n + .table-wrapper,\n + .code-example,\n + .highlighter-rouge,\n + .sectionbody .listingblock {\n margin-top: 1em;\n }\n\n + p:not(.label) {\n margin-top: 0;\n }\n }\n\n > h1:first-child,\n > h2:first-child,\n > h3:first-child,\n > h4:first-child,\n > h5:first-child,\n > h6:first-child,\n > .sect1:first-child > h2,\n > .sect2:first-child > h3,\n > .sect3:first-child > h4,\n > .sect4:first-child > h5,\n > .sect5:first-child > h6 {\n margin-top: $sp-2;\n }\n}\n","// Main nav, breadcrumb, etc...\n// stylelint-disable selector-no-type, max-nesting-depth, selector-max-compound-selectors, selector-max-type, selector-max-specificity\n\n.nav-list {\n padding: 0;\n margin-top: 0;\n margin-bottom: 0;\n list-style: none;\n\n .nav-list-item {\n position: relative;\n margin: 0;\n\n @include fs-4;\n\n @include mq(md) {\n @include fs-3;\n }\n\n .nav-list-link {\n display: block;\n min-height: $nav-list-item-height-sm;\n padding-top: $sp-1;\n padding-bottom: $sp-1;\n line-height: #{$nav-list-item-height-sm - 2 * $sp-1};\n @if $nav-list-expander-right {\n padding-right: $nav-list-item-height-sm;\n padding-left: $gutter-spacing-sm;\n } @else {\n padding-right: $gutter-spacing-sm;\n padding-left: $nav-list-item-height-sm;\n }\n\n @include mq(md) {\n min-height: $nav-list-item-height;\n line-height: #{$nav-list-item-height - 2 * $sp-1};\n @if $nav-list-expander-right {\n padding-right: $nav-list-item-height;\n padding-left: $gutter-spacing;\n } @else {\n padding-right: $gutter-spacing;\n padding-left: $nav-list-item-height;\n }\n }\n\n &.external > svg {\n width: $sp-4;\n height: $sp-4;\n vertical-align: text-bottom;\n }\n\n &.active {\n font-weight: 600;\n text-decoration: none;\n }\n\n &:hover,\n &.active {\n color: darken($link-color, 5%);\n background-image: linear-gradient(\n -90deg,\n rgba($feedback-color, 1) 0%,\n rgba($feedback-color, 0.8) 80%,\n rgba($feedback-color, 0) 100%\n );\n }\n }\n\n .nav-list-expander {\n position: absolute;\n @if $nav-list-expander-right {\n right: 0;\n }\n\n width: $nav-list-item-height-sm;\n height: $nav-list-item-height-sm;\n padding: #{$nav-list-item-height-sm * 0.25};\n color: $link-color;\n\n @include mq(md) {\n width: $nav-list-item-height;\n height: $nav-list-item-height;\n padding: #{$nav-list-item-height * 0.25};\n }\n\n &:hover {\n background-image: linear-gradient(\n -90deg,\n rgba($feedback-color, 1) 0%,\n rgba($feedback-color, 0.8) 100%\n );\n }\n\n @if $nav-list-expander-right {\n svg {\n transform: rotate(90deg);\n }\n }\n }\n\n > .nav-list {\n display: none;\n padding-left: $sp-3;\n list-style: none;\n\n .nav-list-item {\n position: relative;\n\n .nav-list-link {\n color: $nav-child-link-color;\n }\n\n .nav-list-expander {\n color: $nav-child-link-color;\n }\n }\n }\n\n &.active {\n > .nav-list-expander svg {\n @if $nav-list-expander-right {\n transform: rotate(-90deg);\n } @else {\n transform: rotate(90deg);\n }\n }\n\n > .nav-list {\n display: block;\n }\n }\n }\n}\n\n.nav-category {\n padding: $sp-2 $gutter-spacing-sm;\n font-weight: 600;\n text-align: start;\n text-transform: uppercase;\n border-bottom: $border $border-color;\n @include fs-2;\n\n @include mq(md) {\n padding: $sp-2 $gutter-spacing;\n margin-top: $gutter-spacing-sm;\n text-align: start;\n\n &:first-child {\n margin-top: 0;\n }\n }\n}\n\n.nav-list.nav-category-list {\n > .nav-list-item {\n margin: 0;\n\n > .nav-list {\n padding: 0;\n\n > .nav-list-item {\n > .nav-list-link {\n color: $link-color;\n }\n\n > .nav-list-expander {\n color: $link-color;\n }\n }\n }\n }\n}\n\n// Aux nav\n\n.aux-nav {\n height: 100%;\n overflow-x: auto;\n @include fs-2;\n\n .aux-nav-list {\n display: flex;\n height: 100%;\n padding: 0;\n margin: 0;\n list-style: none;\n }\n\n .aux-nav-list-item {\n display: inline-block;\n height: 100%;\n padding: 0;\n margin: 0;\n }\n\n @include mq(md) {\n padding-right: $gutter-spacing-sm;\n }\n}\n\n// Breadcrumb nav\n\n.breadcrumb-nav {\n @include mq(md) {\n margin-top: -$sp-4;\n }\n}\n\n.breadcrumb-nav-list {\n padding-left: 0;\n margin-bottom: $sp-3;\n list-style: none;\n}\n\n.breadcrumb-nav-list-item {\n display: table-cell;\n @include fs-2;\n\n &::before {\n display: none;\n }\n\n &::after {\n display: inline-block;\n margin-right: $sp-2;\n margin-left: $sp-2;\n color: $grey-dk-000;\n content: \"/\";\n }\n\n &:last-child {\n &::after {\n content: \"\";\n }\n }\n}\n","// Typography\n// stylelint-disable selector-no-type, selector-max-type, selector-max-specificity, selector-max-id\n\nh1,\n.text-alpha {\n font-weight: 300;\n\n @include fs-8;\n}\n\nh2,\n.text-beta,\n#toctitle {\n @include fs-6;\n}\n\nh3,\n.text-gamma {\n @include fs-5;\n}\n\nh4,\n.text-delta {\n font-weight: 400;\n text-transform: uppercase;\n letter-spacing: 0.1em;\n\n @include fs-2;\n}\n\nh4 code {\n text-transform: none;\n}\n\nh5,\n.text-epsilon {\n @include fs-3;\n}\n\nh6,\n.text-zeta {\n @include fs-2;\n}\n\n.text-small {\n @include fs-2;\n}\n\n.text-mono {\n font-family: $mono-font-family !important;\n}\n\n.text-left {\n text-align: left !important;\n}\n\n.text-center {\n text-align: center !important;\n}\n\n.text-right {\n text-align: right !important;\n}\n","// Labels (not the form kind)\n\n// this :not() prevents a style clash with Mermaid.js's\n// diagram labels, which also use .label\n// for more, see https://github.com/just-the-docs/just-the-docs/issues/1272\n// and the accompanying PR\n.label:not(g),\n.label-blue:not(g) {\n display: inline-block;\n padding: 0.16em 0.56em;\n margin-right: $sp-2;\n margin-left: $sp-2;\n color: $white;\n text-transform: uppercase;\n vertical-align: middle;\n background-color: $blue-100;\n border-radius: 12px;\n\n @include fs-2;\n}\n\n.label-green:not(g) {\n background-color: $green-300;\n}\n\n.label-purple:not(g) {\n background-color: $purple-100;\n}\n\n.label-red:not(g) {\n background-color: $red-300;\n}\n\n.label-yellow:not(g) {\n color: $grey-dk-200;\n background-color: $yellow-200;\n}\n","// Buttons and things that look like buttons\n// stylelint-disable color-named\n\n.btn {\n display: inline-block;\n box-sizing: border-box;\n padding: 0.3em 1em;\n margin: 0;\n font-family: inherit;\n font-size: inherit;\n font-weight: 500;\n line-height: 1.5;\n color: $link-color;\n text-decoration: none;\n vertical-align: baseline;\n cursor: pointer;\n background-color: $base-button-color;\n border-width: 0;\n border-radius: $border-radius;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n appearance: none;\n\n &:focus {\n text-decoration: none;\n outline: none;\n box-shadow: 0 0 0 3px rgba(blue, 0.25);\n }\n\n &:focus:hover,\n &.selected:focus {\n box-shadow: 0 0 0 3px rgba(blue, 0.25);\n }\n\n &:hover,\n &.zeroclipboard-is-hover {\n color: darken($link-color, 2%);\n }\n\n &:hover,\n &:active,\n &.zeroclipboard-is-hover,\n &.zeroclipboard-is-active {\n text-decoration: none;\n background-color: darken($base-button-color, 1%);\n }\n\n &:active,\n &.selected,\n &.zeroclipboard-is-active {\n background-color: darken($base-button-color, 3%);\n background-image: none;\n box-shadow: inset 0 2px 4px rgba(0, 0, 0, 0.15);\n }\n\n &.selected:hover {\n background-color: darken(#dcdcdc, 5%);\n }\n\n &:disabled,\n &.disabled {\n &,\n &:hover {\n color: rgba(102, 102, 102, 0.5);\n cursor: default;\n background-color: rgba(229, 229, 229, 0.5);\n background-image: none;\n box-shadow: none;\n }\n }\n}\n\n.btn-outline {\n color: $link-color;\n background: transparent;\n box-shadow: inset 0 0 0 2px $grey-lt-300;\n\n &:hover,\n &:active,\n &.zeroclipboard-is-hover,\n &.zeroclipboard-is-active {\n color: darken($link-color, 4%);\n text-decoration: none;\n background-color: transparent;\n box-shadow: inset 0 0 0 3px $grey-lt-300;\n }\n\n &:focus {\n text-decoration: none;\n outline: none;\n box-shadow:\n inset 0 0 0 2px $grey-dk-100,\n 0 0 0 3px rgba(blue, 0.25);\n }\n\n &:focus:hover,\n &.selected:focus {\n box-shadow: inset 0 0 0 2px $grey-dk-100;\n }\n}\n\n.btn-primary {\n @include btn-color($white, $btn-primary-color);\n}\n\n.btn-purple {\n @include btn-color($white, $purple-100);\n}\n\n.btn-blue {\n @include btn-color($white, $blue-200);\n}\n\n.btn-green {\n @include btn-color($white, $green-300);\n}\n\n.btn-reset {\n background: none;\n border: none;\n margin: 0;\n text-align: inherit;\n font: inherit;\n border-radius: 0;\n appearance: none;\n}\n","$color-scheme: light !default;\n$body-background-color: $white !default;\n$body-heading-color: $grey-dk-300 !default;\n$body-text-color: $grey-dk-100 !default;\n$link-color: $purple-000 !default;\n$nav-child-link-color: $grey-dk-100 !default;\n$sidebar-color: $grey-lt-000 !default;\n$base-button-color: #f7f7f7 !default;\n$btn-primary-color: $purple-100 !default;\n$code-background-color: $white !default;\n$feedback-color: darken($sidebar-color, 3%) !default;\n$table-background-color: $white !default;\n$search-background-color: $white !default;\n$search-result-preview-color: $grey-dk-100 !default;\n\n@import \"./vendor/accessible-pygments/github-light\";\n","// Colored button\n\n@mixin btn-color($fg, $bg) {\n color: $fg;\n background-color: darken($bg, 2%);\n background-image: linear-gradient(lighten($bg, 5%), darken($bg, 2%));\n box-shadow:\n 0 1px 3px rgba(0, 0, 0, 0.25),\n 0 4px 10px rgba(0, 0, 0, 0.12);\n\n &:hover,\n &.zeroclipboard-is-hover {\n color: $fg;\n background-color: darken($bg, 4%);\n background-image: linear-gradient((lighten($bg, 2%), darken($bg, 4%)));\n }\n\n &:active,\n &.selected,\n &.zeroclipboard-is-active {\n background-color: darken($bg, 5%);\n background-image: none;\n box-shadow: inset 0 2px 4px rgba(0, 0, 0, 0.15);\n }\n\n &.selected:hover {\n background-color: darken($bg, 10%);\n }\n}\n","// Search input and autocomplete\n\n.search {\n position: relative;\n z-index: 2;\n flex-grow: 1;\n height: $sp-10;\n padding: $sp-2;\n transition: padding linear #{$transition-duration * 0.5};\n\n @include mq(md) {\n position: relative !important;\n width: auto !important;\n height: 100% !important;\n padding: 0;\n transition: none;\n }\n}\n\n.search-input-wrap {\n position: relative;\n z-index: 1;\n height: $sp-8;\n overflow: hidden;\n border-radius: $border-radius;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n transition: height linear #{$transition-duration * 0.5};\n\n @include mq(md) {\n position: absolute;\n width: 100%;\n max-width: $search-results-width;\n height: 100% !important;\n border-radius: 0;\n box-shadow: none;\n transition: width ease $transition-duration;\n }\n}\n\n.search-input {\n position: absolute;\n width: 100%;\n height: 100%;\n padding: $sp-2 $gutter-spacing-sm $sp-2 #{$gutter-spacing-sm + $sp-5};\n font-size: 1rem;\n color: $body-text-color;\n background-color: $search-background-color;\n border-top: 0;\n border-right: 0;\n border-bottom: 0;\n border-left: 0;\n border-radius: 0;\n\n @include mq(md) {\n padding: $sp-2 $gutter-spacing-sm $sp-2 #{$gutter-spacing + $sp-5};\n font-size: 0.875rem;\n background-color: $body-background-color;\n transition: padding-left linear #{$transition-duration * 0.5};\n }\n\n &:focus {\n outline: 2px solid $link-color;\n outline-offset: -2px;\n\n + .search-label .search-icon {\n color: $link-color;\n }\n }\n}\n\n.search-label {\n position: absolute;\n display: flex;\n height: 100%;\n padding-left: $gutter-spacing-sm;\n\n @include mq(md) {\n padding-left: $gutter-spacing;\n transition: padding-left linear #{$transition-duration * 0.5};\n }\n\n .search-icon {\n width: #{$sp-4 * 1.2};\n height: #{$sp-4 * 1.2};\n align-self: center;\n color: $grey-dk-000;\n }\n}\n\n.search-results {\n position: absolute;\n left: 0;\n display: none;\n width: 100%;\n max-height: calc(100% - #{$sp-10});\n overflow-y: auto;\n background-color: $search-background-color;\n border-bottom-right-radius: $border-radius;\n border-bottom-left-radius: $border-radius;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n\n @include mq(md) {\n top: 100%;\n width: $search-results-width;\n max-height: calc(100vh - 200%) !important;\n }\n}\n\n.search-results-list {\n padding-left: 0;\n margin-bottom: $sp-1;\n list-style: none;\n @include fs-4;\n\n @include mq(md) {\n @include fs-3;\n }\n}\n\n.search-results-list-item {\n padding: 0;\n margin: 0;\n}\n\n.search-result {\n display: block;\n padding: $sp-1 $sp-3;\n\n &:hover,\n &.active {\n background-color: $feedback-color;\n }\n}\n\n.search-result-title {\n display: block;\n padding-top: $sp-2;\n padding-bottom: $sp-2;\n\n @include mq(sm) {\n display: inline-block;\n width: 40%;\n padding-right: $sp-2;\n vertical-align: top;\n }\n}\n\n.search-result-doc {\n display: flex;\n align-items: center;\n word-wrap: break-word;\n\n &.search-result-doc-parent {\n opacity: 0.5;\n @include fs-3;\n\n @include mq(md) {\n @include fs-2;\n }\n }\n\n .search-result-icon {\n width: $sp-4;\n height: $sp-4;\n margin-right: $sp-2;\n color: $link-color;\n flex-shrink: 0;\n }\n\n .search-result-doc-title {\n overflow: auto;\n }\n}\n\n.search-result-section {\n margin-left: #{$sp-4 + $sp-2};\n word-wrap: break-word;\n}\n\n.search-result-rel-url {\n display: block;\n margin-left: #{$sp-4 + $sp-2};\n overflow: hidden;\n color: $search-result-preview-color;\n text-overflow: ellipsis;\n white-space: nowrap;\n @include fs-1;\n}\n\n.search-result-previews {\n display: block;\n padding-top: $sp-2;\n padding-bottom: $sp-2;\n padding-left: $sp-4;\n margin-left: $sp-2;\n color: $search-result-preview-color;\n word-wrap: break-word;\n border-left: $border;\n border-left-color: $border-color;\n @include fs-2;\n\n @include mq(sm) {\n display: inline-block;\n width: 60%;\n padding-left: $sp-2;\n margin-left: 0;\n vertical-align: top;\n }\n}\n\n.search-result-preview + .search-result-preview {\n margin-top: $sp-1;\n}\n\n.search-result-highlight {\n font-weight: bold;\n}\n\n.search-no-result {\n padding: $sp-2 $sp-3;\n @include fs-3;\n}\n\n.search-button {\n position: fixed;\n right: $sp-4;\n bottom: $sp-4;\n display: flex;\n width: $sp-9;\n height: $sp-9;\n background-color: $search-background-color;\n border: 1px solid rgba($link-color, 0.3);\n border-radius: #{$sp-9 * 0.5};\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n align-items: center;\n justify-content: center;\n}\n\n.search-overlay {\n position: fixed;\n top: 0;\n left: 0;\n z-index: 1;\n width: 0;\n height: 0;\n background-color: rgba(0, 0, 0, 0.3);\n opacity: 0;\n transition:\n opacity ease $transition-duration,\n width 0s $transition-duration,\n height 0s $transition-duration;\n}\n\n.search-active {\n .search {\n position: fixed;\n top: 0;\n left: 0;\n width: 100%;\n height: 100%;\n padding: 0;\n }\n\n .search-input-wrap {\n height: $sp-10;\n border-radius: 0;\n\n @include mq(md) {\n width: $search-results-width;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n }\n }\n\n .search-input {\n background-color: $search-background-color;\n\n @include mq(md) {\n padding-left: 2.3rem;\n }\n }\n\n .search-label {\n @include mq(md) {\n padding-left: 0.6rem;\n }\n }\n\n .search-results {\n display: block;\n }\n\n .search-overlay {\n width: 100%;\n height: 100%;\n opacity: 1;\n transition:\n opacity ease $transition-duration,\n width 0s,\n height 0s;\n }\n\n @include mq(md) {\n .main {\n position: fixed;\n right: 0;\n left: 0;\n }\n }\n\n .main-header {\n padding-top: $sp-10;\n\n @include mq(md) {\n padding-top: 0;\n }\n }\n}\n","// Tables\n// stylelint-disable max-nesting-depth, selector-no-type, selector-max-type\n\n.table-wrapper {\n display: block;\n width: 100%;\n max-width: 100%;\n margin-bottom: $sp-5;\n overflow-x: auto;\n border-radius: $border-radius;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n}\n\ntable {\n display: table;\n min-width: 100%;\n border-collapse: separate;\n}\n\nth,\ntd {\n min-width: 7.5rem;\n padding: $sp-2 $sp-3;\n background-color: $table-background-color;\n border-bottom: $border rgba($border-color, 0.5);\n border-left: $border $border-color;\n\n @include fs-3;\n\n &:first-of-type {\n border-left: 0;\n }\n}\n\ntbody {\n tr {\n &:last-of-type {\n th,\n td {\n border-bottom: 0;\n }\n\n td {\n padding-bottom: $sp-3;\n }\n }\n }\n}\n\nthead {\n th {\n border-bottom: $border $border-color;\n }\n}\n","// Code and syntax highlighting\n// stylelint-disable selector-no-qualifying-type, declaration-block-semicolon-newline-after,declaration-block-single-line-max-declarations, selector-no-type, selector-max-type, scss/comment-no-empty\n\n// {% raw %}\n\n// This instruction applies to all queues not within 'pre' or 'figure', avoiding 'code' generated by the highlight.\n:not(pre, figure) {\n & > code {\n padding: 0.2em 0.15em;\n font-weight: 400;\n background-color: $code-background-color;\n border: $border $border-color;\n border-radius: $border-radius;\n }\n}\n\n// Avoid appearance of dark border around visited code links in Safari\na:visited code {\n border-color: $border-color;\n}\n\n// Content structure for highlighted code blocks using fences or Liquid\n//\n// ```[LANG]...```, no kramdown line_numbers:\n// div.[language-LANG.]highlighter-rouge > div.highlight > pre.highlight > code\n//\n// ```[LANG]...```, kramdown line_numbers = true:\n// div.[language-LANG.]highlighter-rouge > div.highlight > pre.highlight > code\n// > div.table-wrapper > table.rouge-table > tbody > tr\n// > td.rouge-gutter.gl > pre.lineno\n// | td.rouge-code > pre\n//\n// {% highlight LANG %}...{% endhighlight %}:\n// figure.highlight > pre > code.language-LANG\n//\n// {% highlight LANG linenos %}...{% endhighlight %}:\n// figure.highlight > pre > code.language-LANG\n// > div.table-wrapper > table.rouge-table > tbody > tr\n// > td.gutter.gl > pre.lineno\n// | td.code > pre\n//\n// ----...---- (AsciiDoc)\n// div.listingblock > div.content > pre.rouge.highlight\n//\n// fix_linenos removes the outermost pre when it encloses table.rouge-table\n//\n// See docs/index-test.md for some tests.\n//\n// No kramdown line_numbers: fences and Liquid highlighting look the same.\n// Kramdown line_numbers = true: fences have a wider gutter than with Liquid?\n\n// ```[LANG]...```\n// or in AsciiDoc:\n//\n// ----\n// ...\n// ----\n\n// the code may appear with 3 different types:\n// container \\ case: default case, code with line number, code with html rendering\n// top level: div.highlighter-rouge, figure.highlight, figure.highlight\n// second level: div.highlight, div.table-wrapper, pre.highlight\n// third level: pre.highlight, td.code, absent\n// last level: code, pre, code (optionality)\n// highlighter level: span, span, span\n// the spacing are only in the second level for case 1, 3 and in the third level for case 2\n// in AsciiDoc, there is a parent container that contains optionally a title and the content.\n\n// select top level container\ndiv.highlighter-rouge,\ndiv.listingblock > div.content,\nfigure.highlight {\n margin-top: 0;\n margin-bottom: $sp-3;\n background-color: $code-background-color;\n border-radius: $border-radius;\n box-shadow: none;\n -webkit-overflow-scrolling: touch;\n position: relative;\n padding: 0;\n\n // copy button (or other button)\n // the button appear only when there is a hover on the code or focus on button\n > button {\n width: $sp-3;\n opacity: 0;\n position: absolute;\n top: 0;\n right: 0;\n padding: $sp-3;\n border: none;\n background: none;\n color: $body-text-color;\n box-sizing: content-box;\n\n svg {\n fill: $body-text-color;\n }\n\n &:active {\n text-decoration: none;\n outline: none;\n opacity: 1;\n }\n\n &:focus {\n opacity: 1;\n outline: 2px solid $link-color;\n }\n }\n\n // the button can be seen by doing a simple hover in the code, there is no need to go over the location of the button\n &:hover {\n > button {\n cursor: copy;\n opacity: 1;\n }\n }\n}\n\n// setting the spacing and scrollbar on the second level for the first case\n// remove all space on the second and third level\n// this is a mixin to accommodate for the slightly different structures generated via Markdown vs AsciiDoc\n@mixin scroll-and-spacing($code-div, $pre-select) {\n #{$code-div} {\n overflow-x: auto;\n padding: $sp-3;\n margin: 0;\n border: 1px solid $body-text-color;\n border-radius: $border-radius;\n }\n\n #{$pre-select},\n code {\n padding: 0;\n margin: 0;\n border: 0;\n }\n}\n\n// for Markdown\ndiv.highlighter-rouge {\n @include scroll-and-spacing(\"div.highlight\", \"pre.highlight\");\n}\n\n// for AsciiDoc. we also need to fix the margins for its parent container.\ndiv.listingblock {\n margin-top: 0;\n margin-bottom: $sp-3;\n\n @include scroll-and-spacing(\"div.content\", \"div.content > pre\");\n}\n\n// {% highlight LANG %}...{% endhighlight %},\n// {% highlight LANG linenos %}...{% endhighlight %}:\n\n// setting the spacing and scrollbar on the second level for the thirt case\n// the css rule are apply only to the last code enviroment\n// setting the scroolbar\nfigure.highlight {\n pre,\n :not(pre) > code {\n overflow-x: auto;\n padding: $sp-3;\n margin: 0;\n border: 1px solid $body-text-color;\n border-radius: $border-radius;\n }\n}\n\n// ```[LANG]...```, kramdown line_numbers = true,\n// {% highlight LANG linenos %}...{% endhighlight %}:\n\n// setting the spacing and scrollbar on the thirt level for the second case\n.highlight .table-wrapper {\n padding: $sp-3 0;\n margin: 0;\n border: 0;\n box-shadow: none;\n\n td,\n pre {\n min-width: 0;\n padding: 0;\n background-color: $code-background-color;\n border: 0;\n\n @include fs-2;\n }\n\n td.gl {\n width: 1em;\n padding-right: $sp-3;\n padding-left: $sp-3;\n }\n\n pre {\n margin: 0;\n line-height: 2;\n }\n}\n\n// Code examples: html render of a code\n.code-example,\n.listingblock > .title {\n padding: $sp-3;\n margin-bottom: $sp-3;\n overflow: auto;\n border: 1px solid $border-color;\n border-radius: $border-radius;\n\n + .highlighter-rouge,\n + .sectionbody .listingblock,\n + .content,\n + figure.highlight {\n position: relative;\n margin-top: -$sp-4;\n border-right: 1px solid $border-color;\n border-bottom: 1px solid $border-color;\n border-left: 1px solid $border-color;\n border-top-left-radius: 0;\n border-top-right-radius: 0;\n }\n}\n\n// Mermaid diagram code blocks should be left unstyled.\ncode.language-mermaid {\n padding: 0;\n background-color: inherit;\n border: 0;\n}\n\n// Override OneDarkJekyll Colors for Code Blocks\n.highlight,\npre.highlight {\n background: $code-background-color; // Code Background\n // For Backwards Compatibility Before $code-linenumber-color was added\n @if variable-exists(code-linenumber-color) {\n color: $code-linenumber-color; // Code Line Numbers\n } @else {\n color: $body-text-color; // Code Line Numbers\n }\n}\n\n// Override OneDarkJekyll Colors for Code Blocks\n.highlight pre {\n background: $code-background-color; // Code Background\n}\n\n// {% endraw %}\n","// Utility classes for colors\n\n// Text colors\n\n.text-grey-dk-000 {\n color: $grey-dk-000 !important;\n}\n\n.text-grey-dk-100 {\n color: $grey-dk-100 !important;\n}\n\n.text-grey-dk-200 {\n color: $grey-dk-200 !important;\n}\n\n.text-grey-dk-250 {\n color: $grey-dk-250 !important;\n}\n\n.text-grey-dk-300 {\n color: $grey-dk-300 !important;\n}\n\n.text-grey-lt-000 {\n color: $grey-lt-000 !important;\n}\n\n.text-grey-lt-100 {\n color: $grey-lt-100 !important;\n}\n\n.text-grey-lt-200 {\n color: $grey-lt-200 !important;\n}\n\n.text-grey-lt-300 {\n color: $grey-lt-300 !important;\n}\n\n.text-blue-000 {\n color: $blue-000 !important;\n}\n\n.text-blue-100 {\n color: $blue-100 !important;\n}\n\n.text-blue-200 {\n color: $blue-200 !important;\n}\n\n.text-blue-300 {\n color: $blue-300 !important;\n}\n\n.text-green-000 {\n color: $green-000 !important;\n}\n\n.text-green-100 {\n color: $green-100 !important;\n}\n\n.text-green-200 {\n color: $green-200 !important;\n}\n\n.text-green-300 {\n color: $green-300 !important;\n}\n\n.text-purple-000 {\n color: $purple-000 !important;\n}\n\n.text-purple-100 {\n color: $purple-100 !important;\n}\n\n.text-purple-200 {\n color: $purple-200 !important;\n}\n\n.text-purple-300 {\n color: $purple-300 !important;\n}\n\n.text-yellow-000 {\n color: $yellow-000 !important;\n}\n\n.text-yellow-100 {\n color: $yellow-100 !important;\n}\n\n.text-yellow-200 {\n color: $yellow-200 !important;\n}\n\n.text-yellow-300 {\n color: $yellow-300 !important;\n}\n\n.text-red-000 {\n color: $red-000 !important;\n}\n\n.text-red-100 {\n color: $red-100 !important;\n}\n\n.text-red-200 {\n color: $red-200 !important;\n}\n\n.text-red-300 {\n color: $red-300 !important;\n}\n\n// Background colors\n\n.bg-grey-dk-000 {\n background-color: $grey-dk-000 !important;\n}\n\n.bg-grey-dk-100 {\n background-color: $grey-dk-100 !important;\n}\n\n.bg-grey-dk-200 {\n background-color: $grey-dk-200 !important;\n}\n\n.bg-grey-dk-250 {\n background-color: $grey-dk-250 !important;\n}\n\n.bg-grey-dk-300 {\n background-color: $grey-dk-300 !important;\n}\n\n.bg-grey-lt-000 {\n background-color: $grey-lt-000 !important;\n}\n\n.bg-grey-lt-100 {\n background-color: $grey-lt-100 !important;\n}\n\n.bg-grey-lt-200 {\n background-color: $grey-lt-200 !important;\n}\n\n.bg-grey-lt-300 {\n background-color: $grey-lt-300 !important;\n}\n\n.bg-blue-000 {\n background-color: $blue-000 !important;\n}\n\n.bg-blue-100 {\n background-color: $blue-100 !important;\n}\n\n.bg-blue-200 {\n background-color: $blue-200 !important;\n}\n\n.bg-blue-300 {\n background-color: $blue-300 !important;\n}\n\n.bg-green-000 {\n background-color: $green-000 !important;\n}\n\n.bg-green-100 {\n background-color: $green-100 !important;\n}\n\n.bg-green-200 {\n background-color: $green-200 !important;\n}\n\n.bg-green-300 {\n background-color: $green-300 !important;\n}\n\n.bg-purple-000 {\n background-color: $purple-000 !important;\n}\n\n.bg-purple-100 {\n background-color: $purple-100 !important;\n}\n\n.bg-purple-200 {\n background-color: $purple-200 !important;\n}\n\n.bg-purple-300 {\n background-color: $purple-300 !important;\n}\n\n.bg-yellow-000 {\n background-color: $yellow-000 !important;\n}\n\n.bg-yellow-100 {\n background-color: $yellow-100 !important;\n}\n\n.bg-yellow-200 {\n background-color: $yellow-200 !important;\n}\n\n.bg-yellow-300 {\n background-color: $yellow-300 !important;\n}\n\n.bg-red-000 {\n background-color: $red-000 !important;\n}\n\n.bg-red-100 {\n background-color: $red-100 !important;\n}\n\n.bg-red-200 {\n background-color: $red-200 !important;\n}\n\n.bg-red-300 {\n background-color: $red-300 !important;\n}\n","// Utility classes for layout\n\n// Display\n\n.d-block {\n display: block !important;\n}\n\n.d-flex {\n display: flex !important;\n}\n\n.d-inline {\n display: inline !important;\n}\n\n.d-inline-block {\n display: inline-block !important;\n}\n\n.d-none {\n display: none !important;\n}\n\n// Screenreader-only\n\n.sr-only {\n position: absolute;\n width: 1px;\n height: 1px;\n padding: 0;\n margin: -1px;\n overflow: hidden;\n clip: rect(0, 0, 0, 0);\n white-space: nowrap;\n border-width: 0;\n}\n\n@each $media-query in map-keys($media-queries) {\n @for $i from 1 through length($spacers) {\n @include mq($media-query) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .d-sm-block, .d-md-none, .d-lg-inline\n .d-#{$media-query}-block {\n display: block !important;\n }\n .d-#{$media-query}-flex {\n display: flex !important;\n }\n .d-#{$media-query}-inline {\n display: inline !important;\n }\n .d-#{$media-query}-inline-block {\n display: inline-block !important;\n }\n .d-#{$media-query}-none {\n display: none !important;\n }\n }\n }\n}\n\n// Horizontal alignment\n\n.float-left {\n float: left !important;\n}\n\n.float-right {\n float: right !important;\n}\n\n.flex-justify-start {\n justify-content: flex-start !important;\n}\n\n.flex-justify-end {\n justify-content: flex-end !important;\n}\n\n.flex-justify-between {\n justify-content: space-between !important;\n}\n\n.flex-justify-around {\n justify-content: space-around !important;\n}\n\n// Vertical alignment\n\n.v-align-baseline {\n vertical-align: baseline !important;\n}\n\n.v-align-bottom {\n vertical-align: bottom !important;\n}\n\n.v-align-middle {\n vertical-align: middle !important;\n}\n\n.v-align-text-bottom {\n vertical-align: text-bottom !important;\n}\n\n.v-align-text-top {\n vertical-align: text-top !important;\n}\n\n.v-align-top {\n vertical-align: top !important;\n}\n","// Utility classes for typography\n\n.fs-1 {\n @include fs-1;\n}\n\n.fs-2 {\n @include fs-2;\n}\n\n.fs-3 {\n @include fs-3;\n}\n\n.fs-4 {\n @include fs-4;\n}\n\n.fs-5 {\n @include fs-5;\n}\n\n.fs-6 {\n @include fs-6;\n}\n\n.fs-7 {\n @include fs-7;\n}\n\n.fs-8 {\n @include fs-8;\n}\n\n.fs-9 {\n @include fs-9;\n}\n\n.fs-10 {\n @include fs-10;\n}\n\n.fw-300 {\n font-weight: 300 !important;\n}\n\n.fw-400 {\n font-weight: 400 !important;\n}\n\n.fw-500 {\n font-weight: 500 !important;\n}\n\n.fw-700 {\n font-weight: 700 !important;\n}\n\n.lh-0 {\n line-height: 0 !important;\n}\n\n.lh-default {\n line-height: $body-line-height;\n}\n\n.lh-tight {\n line-height: $body-heading-line-height;\n}\n\n.ls-5 {\n letter-spacing: 0.05em !important;\n}\n\n.ls-10 {\n letter-spacing: 0.1em !important;\n}\n\n.ls-0 {\n letter-spacing: 0 !important;\n}\n\n.text-uppercase {\n text-transform: uppercase !important;\n}\n","// Utility classes for lists\n\n// stylelint-disable selector-max-type\n\n.list-style-none {\n padding: 0 !important;\n margin: 0 !important;\n list-style: none !important;\n\n li {\n &::before {\n display: none !important;\n }\n }\n}\n","// Utility classes for margins and padding\n\n// stylelint-disable block-opening-brace-space-after, block-opening-brace-space-before\n\n// Margin spacer utilities\n\n.mx-auto {\n margin-right: auto !important;\n margin-left: auto !important;\n}\n\n@for $i from 1 through length($spacers) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .m-0, .m-1, .m-2...\n .m-#{$scale} {\n margin: #{$size} !important;\n }\n .mt-#{$scale} {\n margin-top: #{$size} !important;\n }\n .mr-#{$scale} {\n margin-right: #{$size} !important;\n }\n .mb-#{$scale} {\n margin-bottom: #{$size} !important;\n }\n .ml-#{$scale} {\n margin-left: #{$size} !important;\n }\n\n .mx-#{$scale} {\n margin-right: #{$size} !important;\n margin-left: #{$size} !important;\n }\n\n .my-#{$scale} {\n margin-top: #{$size} !important;\n margin-bottom: #{$size} !important;\n }\n\n .mxn-#{$scale} {\n margin-right: -#{$size} !important;\n margin-left: -#{$size} !important;\n }\n .mx-#{$scale}-auto {\n margin-right: auto !important;\n margin-left: auto !important;\n }\n}\n\n@each $media-query in map-keys($media-queries) {\n @for $i from 1 through length($spacers) {\n @include mq($media-query) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .m-sm-0, .m-md-1, .m-lg-2...\n .m-#{$media-query}-#{$scale} {\n margin: #{$size} !important;\n }\n .mt-#{$media-query}-#{$scale} {\n margin-top: #{$size} !important;\n }\n .mr-#{$media-query}-#{$scale} {\n margin-right: #{$size} !important;\n }\n .mb-#{$media-query}-#{$scale} {\n margin-bottom: #{$size} !important;\n }\n .ml-#{$media-query}-#{$scale} {\n margin-left: #{$size} !important;\n }\n\n .mx-#{$media-query}-#{$scale} {\n margin-right: #{$size} !important;\n margin-left: #{$size} !important;\n }\n\n .my-#{$media-query}-#{$scale} {\n margin-top: #{$size} !important;\n margin-bottom: #{$size} !important;\n }\n\n .mxn-#{$media-query}-#{$scale} {\n margin-right: -#{$size} !important;\n margin-left: -#{$size} !important;\n }\n }\n }\n}\n\n// Padding spacer utilities\n\n@for $i from 1 through length($spacers) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .p-0, .p-1, .p-2...\n .p-#{$scale} {\n padding: #{$size} !important;\n }\n .pt-#{$scale} {\n padding-top: #{$size} !important;\n }\n .pr-#{$scale} {\n padding-right: #{$size} !important;\n }\n .pb-#{$scale} {\n padding-bottom: #{$size} !important;\n }\n .pl-#{$scale} {\n padding-left: #{$size} !important;\n }\n\n .px-#{$scale} {\n padding-right: #{$size} !important;\n padding-left: #{$size} !important;\n }\n\n .py-#{$scale} {\n padding-top: #{$size} !important;\n padding-bottom: #{$size} !important;\n }\n}\n\n@each $media-query in map-keys($media-queries) {\n @include mq($media-query) {\n @for $i from 1 through length($spacers) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .p-sm-0, .p-md-1, .p-lg-2...\n .p-#{$media-query}-#{$scale} {\n padding: #{$size} !important;\n }\n .pt-#{$media-query}-#{$scale} {\n padding-top: #{$size} !important;\n }\n .pr-#{$media-query}-#{$scale} {\n padding-right: #{$size} !important;\n }\n .pb-#{$media-query}-#{$scale} {\n padding-bottom: #{$size} !important;\n }\n .pl-#{$media-query}-#{$scale} {\n padding-left: #{$size} !important;\n }\n\n .px-#{$media-query}-#{$scale} {\n padding-right: #{$size} !important;\n padding-left: #{$size} !important;\n }\n\n .py-#{$media-query}-#{$scale} {\n padding-top: #{$size} !important;\n padding-bottom: #{$size} !important;\n }\n }\n }\n}\n","// stylelint-disable selector-max-specificity, selector-max-id, selector-max-type, selector-no-qualifying-type\n\n@media print {\n .site-footer,\n .site-button,\n #edit-this-page,\n #back-to-top,\n .site-nav,\n .main-header {\n display: none !important;\n }\n\n hr {\n margin-top: 1rem;\n margin-bottom: 1rem;\n }\n\n .side-bar {\n width: 100%;\n height: auto;\n border-right: 0 !important;\n }\n\n .site-header {\n border-bottom: 1px solid $border-color;\n }\n\n .site-title {\n font-size: 1rem !important;\n font-weight: 700 !important;\n }\n\n .text-small {\n font-size: 8pt !important;\n }\n\n pre.highlight {\n border: 1px solid $border-color;\n }\n\n .main {\n max-width: none;\n margin-left: 0;\n }\n}\n","// Skipnav\n// Skip to main content\n\na.skip-to-main {\n left: -999px;\n position: absolute;\n top: auto;\n width: 1px;\n height: 1px;\n overflow: hidden;\n z-index: -999;\n}\n\na.skip-to-main:focus,\na.skip-to-main:active {\n color: $link-color;\n background-color: $body-background-color;\n left: auto;\n top: auto;\n width: 30%;\n height: auto;\n overflow: auto;\n margin: 10px 35%;\n padding: 5px;\n border-radius: 15px;\n border: 4px solid $btn-primary-color;\n text-align: center;\n font-size: 1.2em;\n z-index: 999;\n}\n","\n\n@import \"./support/support\";\n@import \"./custom/setup\";\n@import \"./color_schemes/light\";\n\n@import \"./color_schemes/meshtastic\";\n\n@import \"./modules\";\ndiv.opaque {\n background-color: $body-background-color;\n}\n\np.tip, blockquote.tip {\n border: 1px $green-000 solid;\n border-left: $border-radius solid $green-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n \n &::before {\n color: $green-300;\n content: \"Tip\";\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n \n > .tip-title {\n color: $green-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\np.tip-title, blockquote.tip-title {\n border: 1px $green-000 solid;\n border-left: $border-radius solid $green-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n > p:first-child {\n margin-top: 0;\n margin-bottom: 0;\n color: $green-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\nblockquote.tip {\n margin-left: 0;\n margin-right: 0;\n\n > p:first-child {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\nblockquote.tip-title {\n margin-left: 0;\n margin-right: 0;\n\n > p:nth-child(2) {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\n\n\np.note, blockquote.note {\n border: 1px $blue-000 solid;\n border-left: $border-radius solid $blue-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n \n &::before {\n color: $blue-300;\n content: \"Note\";\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n \n > .note-title {\n color: $blue-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\np.note-title, blockquote.note-title {\n border: 1px $blue-000 solid;\n border-left: $border-radius solid $blue-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n > p:first-child {\n margin-top: 0;\n margin-bottom: 0;\n color: $blue-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\nblockquote.note {\n margin-left: 0;\n margin-right: 0;\n\n > p:first-child {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\nblockquote.note-title {\n margin-left: 0;\n margin-right: 0;\n\n > p:nth-child(2) {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\n\n\np.warning, blockquote.warning {\n border: 1px $yellow-000 solid;\n border-left: $border-radius solid $yellow-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n \n &::before {\n color: $yellow-300;\n content: \"Warning\";\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n \n > .warning-title {\n color: $yellow-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\np.warning-title, blockquote.warning-title {\n border: 1px $yellow-000 solid;\n border-left: $border-radius solid $yellow-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n > p:first-child {\n margin-top: 0;\n margin-bottom: 0;\n color: $yellow-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\nblockquote.warning {\n margin-left: 0;\n margin-right: 0;\n\n > p:first-child {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\nblockquote.warning-title {\n margin-left: 0;\n margin-right: 0;\n\n > p:nth-child(2) {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\n\n@import \"./custom/custom\";\n\n\n"],"file":"just-the-docs-default.css"} \ No newline at end of file +{"version":3,"sourceRoot":"","sources":["../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/vendor/accessible-pygments/github-light.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/vendor/normalize.scss/normalize.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/base.scss","../../_sass/color_schemes/meshtastic.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/support/mixins/_typography.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/support/mixins/_layout.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/support/_variables.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/layout.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/content.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/navigation.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/typography.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/labels.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/buttons.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/color_schemes/light.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/support/mixins/_buttons.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/search.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/tables.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/code.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/utilities/_colors.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/utilities/_layout.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/utilities/_typography.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/utilities/_lists.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/utilities/_spacing.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/print.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/skiptomain.scss","just-the-docs-default.scss"],"names":[],"mappings":";AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAUA;EAAkB;;;AAClB;EAAgB;EAAiB;AACjC;EAAkB;EAAiB;AACnC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAkB;EAAiB;AACnC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAqB;AACtC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAoB;AACrC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAgB;EAAiB;AACjC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AChFlC;AAEA;AAAA;AAGA;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAAA;AAKA;EACE;EACA;EACA;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;EACA;;;AAGF;AAAA;AAAA;AAIA;AAAA;EAEE;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;AAAA;EAGE;EACA;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;EAEE;EACA;EACA;EACA;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAAA;AAKA;AAAA;AAAA;AAAA;AAAA;EAKE;EACA;EACA;EACA;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;AAEE;EACA;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;AAEE;EACA;;;AAGF;AAAA;AAAA;AAIA;AAAA;AAAA;AAAA;EAIE;;;AAGF;AAAA;AAAA;AAIA;AAAA;AAAA;AAAA;EAIE;EACA;;;AAGF;AAAA;AAAA;AAIA;AAAA;AAAA;AAAA;EAIE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAOA;EACE;EACA;EACA;EACA;EACA;EACA;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;EAEE;EACA;;;AAGF;AAAA;AAAA;AAIA;AAAA;EAEE;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AC1VF;EACE,cCGa;;;ADAf;EACE;;;AAGF;EACE;;AEmBA;EACE;;AClBA;EHHJ;IEyBI;;;;AFnBJ;EACE,aIfiB;EJgBjB;EACA,aIbiB;EJcjB,OCTgB;EDUhB,kBCZsB;EDatB;;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAYE;;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAOE;EACA;EACA;EACA,aI1CyB;EJ2CzB,OCvCmB;;;AD0CrB;EACE;EACA;;;AAGF;EACE,OC7CW;ED8CX;;;AAGF;EACE;EACA,uBCvCa;EDwCb;;AAEA;EACE;;;AAIJ;EACE,aIvEiB;EJwEjB;EACA,aIvEiB;;;AJ0EnB;AAAA;EAEE;;;AAGF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;EACA;EACA,kBCvEa;EDwEb;;;AAIF;EACE;EAGA;EACA;EACA;EACA;;;AK7GF;EACE;EACA;EACA;EACA,kBJKc;;AEGZ;EEZJ;IAOI;IACA;IACA,ODwFW;ICvFX;IACA;IACA;;;AFAA;EEZJ;IAgBI;IACA,WD+EQ;;;ADpFR;EEQF;IAEI,aD2ES;;;ADrFX;EEQF;IAQI;;;AAOF;EACE;EACA,kBJ5BU;;AEGZ;EEuBA;IAKI;IACA,kBJjCgB;;;AIoClB;EACE;;AFjCJ;EEgCE;IAII;;;;AAOV;EACE;;AF5CE;EE2CJ;IAII;IACA,WDyCY;;;;ACrChB;EACE,aDaK;ECZL,gBDYK;EDvDL,eCuDK;EDtDL,cCsDK;;ADlEH;EEoDJ;IFrCI,eCqDG;IDpDH,cCoDG;;;ADpEH;EEoDJ;IAOI,aDSG;ICRH,gBDQG;;;;ACJP;EACE;EACA;;AFlEE;EEgEJ;IAKI;IACA;IACA,QDmBY;;;;ACfhB;AAAA;AAAA;EAGE;;AF9EE;EE2EJ;AAAA;AAAA;IAMI,ODGQ;;;;ACCZ;EACE;;AAEA;EACE;;AFzFA;EEqFJ;IAQI;IACA,aDxBG;ICyBH,gBD7BG;IC8BH;IACA;;;;AAIJ;EACE;EACA,YDbc;ECcd;;AFxGE;EEqGJ;IAMI,QDjBY;ICkBZ,YDlBY;ICmBZ;;;;AAIJ;EACE;EACA;EACA;EACA;EACA,aDrDK;ECsDL,gBDtDK;ECuDL,OJzHmB;EEYnB,eCuDK;EDtDL,cCsDK;;ADlEH;EEiHJ;IFlGI,eCqDG;IDpDH,cCoDG;;;AF/BL;EACE;;ACtCA;EEiHJ;IHvEI;IACA,aEhDuB;;;ADKvB;EEiHJ;IAcI,aD/DG;ICgEH,gBDhEG;;;;AC+EP;EACE;EACA;EACA,SDhFK;ECiFL;;;AFnJE;EEuJF;IACE;;;AAIJ;EACE;;;AAQF;EACE;;;AAOF;EACE;EACA;EACA;EACA,aD/GK;ECgHL,gBDhHK;EDvDL,eCuDK;EDtDL,cCsDK;;ADlEH;EE6KJ;IF9JI,eCqDG;IDpDH,cCoDG;;;AFvEL;EACE;;ACEA;EE6KJ;IH3KI;;;ACFA;EE6KJ;IAYI;IACA;;;;AAIJ;EACE,OD5HK;EC6HL,QD7HK;EC8HL,OJ/LW;;;AKXb;EACE,aFEoB;;AEApB;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAOE;;AAGF;EACE;EACA;;AAGF;AAAA;EAEE;;AAIA;EACE,YF+CC;;AE3CL;EACE;EACA;;AAEA;EACE;;AAEA;EACE;EACA;EACA;EACA,OFfM;EEgBN;EACA;;AJ1BN;EACE;;ACRA;EG2BE;IJfF;;;ACZA;EG2BE;IAUI;;;AAIJ;EACE;;AAGE;EACE;EACA;;AAOV;EACE;;AAGE;EACE;EACA;EACA,OF7CM;EE8CN;;AAMJ;EACE;;AAIJ;EACE;EACA;;AAKF;EACE;;AAGF;EACE;;AAGF;EACE;EACA;;AAGF;AAAA;EAEE;;AAGF;EACE;EACA;EACA;;AAEA;EACE;;AAIJ;EACE;EACA;EACA;;AAmBE;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EACE;;AASF;AAAA;AAAA;AAAA;AAAA;AAAA;EAEE;;AAKN;EACE;EACA;EACA,OFnFG;EEoFH;EACA,eFzFG;EE0FH,cF1FG;EE2FH;;AH1JA;EGmJF;IAUI;IACA;;;AAGF;EACE;EACA;EACA;EACA,OLnKO;EKoKP;;AAYF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EACE;;AAIJ;EACE;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAOE;EACA;EACA;;AAEA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAKE;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EACE;;AAIJ;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAWE,YF9JG;;;AG3EP;EACE;EACA;EACA;EACA;;AAEA;EACE;EACA;;ALoBF;EACE;;AClBA;EILF;IL2BE;;;ACtBA;EDOF;IACE;;;ACRA;EILF;ILiBE;;;AKPA;EACE;EACA,YH+DC;EG9DD,aHuDC;EGtDD,gBHsDC;EGrDD;EAEE,eH0DD;EGzDC,cHqDD;;ADlEH;EIKA;IAeI,YHgDD;IG/CC;IAEE,eH6CH;IG5CG,cH4CH;;;AGrCD;EACE,OHkCD;EGjCC,QHiCD;EGhCC;;AAGF;EACE;EACA;;AAGF;EAEE;EACA;;AASJ;EACE;EAEE;EAGF,OHUC;EGTD,QHSC;EGRD;EACA,ON7DO;;AEFT;EIsDA;IAYI,OHED;IGDC,QHCD;IGAC;;;AAGF;EACE;;AAQA;EACE;;AAKN;EACE;EACA,cHvBC;EGwBD;;AAEA;EACE;;AAEA;EACE,ONzFa;;AM4Ff;EACE,ON7Fa;;AMmGjB;EAEI;;AAMJ;EACE;;;AAMR;EACE;EACA;EACA;EACA;EACA;;ALhIA;EACE;;ACEA;EIwHJ;ILtHI;;;ACFA;EIwHJ;IASI;IACA,YHhEG;IGiEH;;EAEA;IACE;;;;AAMJ;EACE;;AAEA;EACE;;AAGE;EACE,ONlJG;;AMqJL;EACE,ONtJG;;;AM+Jb;EACE;EACA;;ALtKA;EACE;;ACEA;EIiKJ;IL/JI;;;AKoKF;EACE;EACA;EACA;EACA;EACA;;AAGF;EACE;EACA;EACA;EACA;;AJlLA;EIiKJ;IAqBI,eHpHG;;;;ADlEH;EI4LJ;IAEI;;;;AAIJ;EACE;EACA,eHnIK;EGoIL;;;AAGF;EACE;;AL5MA;EACE;;ACEA;EIwMJ;ILtMI;;;AK0MF;EACE;;AAGF;EACE;EACA,cHlJG;EGmJH,aHnJG;EGoJH,OHpMU;EGqMV;;AAIA;EACE;;;ACrON;AAAA;EAEE;;ANoEA;AAAA;EACE;EACA,aElEuB;;ADKvB;EKXJ;AAAA;IN4EI;;;;AA5BF;AAAA;AAAA;EACE;;ACtCA;EKJJ;AAAA;AAAA;IN8CI;IACA,aEhDuB;;;;AFgCzB;AAAA;EACE;;AC5BA;EKEJ;AAAA;IN8BI;;;;AMzBJ;AAAA;EAEE;EACA;EACA;;ANdA;AAAA;EACE;;ACEA;EKOJ;AAAA;INLI;;;;AMcJ;EACE;;;ANVA;AAAA;EACE;;ACRA;EKoBJ;AAAA;INRI;;;;AAfF;AAAA;EACE;;ACEA;EKyBJ;AAAA;INvBI;;;;AALF;EACE;;ACEA;EK8BJ;IN5BI;;;;AMgCJ;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;ACvDF;AAAA;EAEE;EACA;EACA,cLoEK;EKnEL,aLmEK;EKlEL,OLiBM;EKhBN;EACA;EACA,kBL6BS;EK5BT;;APLA;AAAA;EACE;;ACEA;EMRJ;AAAA;IPUI;;;;AOKJ;EACE,kBL4BU;;;AKzBZ;EACE,kBLcW;;;AKXb;EACE,kBL4BQ;;;AKzBV;EACE,OLFY;EKGZ,kBLkBW;;;AMlDb;EACE;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA,OTIW;ESHX;EACA;EACA;EACA,kBCTkB;EDUlB;EACA,eNyEc;EMxEd,YACE;EAEF;;AAEA;EACE;EACA;EACA;;AAGF;EAEE;;AAGF;EAEE;;AAGF;EAIE;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;AAKA;EAEE;EACA;EACA;EACA;EACA;;;AAKN;EACE,OT1DW;ES2DX;EACA;;AAEA;EAIE;EACA;EACA;EACA;;AAGF;EACE;EACA;EACA,YACE;;AAIJ;EAEE;;;AAIJ;EEnGE,OR0BM;EQzBN;EACA;EACA,YACE;;AAGF;EAEE,ORiBI;EQhBJ;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;;AFgFJ;EEvGE,OR0BM;EQzBN;EACA;EACA,YACE;;AAGF;EAEE,ORiBI;EQhBJ;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;;AFoFJ;EE3GE,OR0BM;EQzBN;EACA;EACA,YACE;;AAGF;EAEE,ORiBI;EQhBJ;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;;AFwFJ;EE/GE,OR0BM;EQzBN;EACA;EACA,YACE;;AAGF;EAEE,ORiBI;EQhBJ;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;;AF4FJ;EACE;EACA;EACA;EACA;EACA;EACA;EACA;;;AG3HF;EACE;EACA;EACA;EACA,QTgFM;ES/EN,STuEK;EStEL;;AVME;EUZJ;IASI;IACA;IACA;IACA;IACA;;;;AAIJ;EACE;EACA;EACA,QT8DK;ES7DL;EACA,eTmEc;ESlEd,YACE;EAEF;;AVdE;EUKJ;IAYI;IACA;IACA,WTwEmB;ISvEnB;IACA;IACA;IACA;;;;AAIJ;EACE;EACA;EACA;EACA;EACA;EACA,OZnCgB;EYoChB,kBZVwB;EYWxB;EACA;EACA;EACA;EACA;;AVvCE;EU2BJ;IAeI;IACA;IACA,kBZhDoB;IYiDpB;;;AAGF;EACE;EACA;;AAEA;EACE,OZnDO;;;AYwDb;EACE;EACA;EACA;EACA,cTIK;;ADlEH;EU0DJ;IAOI,cTGG;ISFH;;;AAGF;EACE;EACA;EACA;EACA,OTzDU;;;AS6Dd;EACE;EACA;EACA;EACA;EACA;EACA;EACA,kBZ5DwB;EY6DxB,4BTRc;ESSd,2BTTc;ESUd,YACE;;AVxFA;EU6EJ;IAeI;IACA,OTFmB;ISGnB;;;;AAIJ;EACE;EACA,eTrCK;ESsCL;;AXpFA;EACE;;AClBA;EUkGJ;IX5EI;;;ACtBA;EDOF;IACE;;;ACRA;EUkGJ;IXtFI;;;;AWiGJ;EACE;EACA;;;AAGF;EACE;EACA;;AAEA;EAEE,kBZnGa;;;AYuGjB;EACE;EACA,aT9DK;ES+DL,gBT/DK;;ADhEH;EU4HJ;IAMI;IACA;IACA,eTpEG;ISqEH;;;;AAIJ;EACE;EACA;EACA;;AAEA;EACE;;AXxIF;EACE;;ACRA;EU8IF;IXlIE;;;ACZA;EDHF;IACE;;;ACEA;EU8IF;IX5IE;;;AWqJF;EACE,OTtFG;ESuFH,QTvFG;ESwFH,cT1FG;ES2FH,OZzJS;EY0JT;;AAGF;EACE;;;AAIJ;EACE;EACA;;;AAGF;EACE;EACA;EACA;EACA,OZtK4B;EYuK5B;EACA;;AX5LA;EACE;;ACYA;EUyKJ;IXjLI;;;;AW2LJ;EACE;EACA,aTrHK;ESsHL,gBTtHK;ESuHL,cTrHK;ESsHL,aTxHK;ESyHL,OZlL4B;EYmL5B;EACA,aT/GO;ESgHP,mBZ9Ka;;ACjBb;EACE;;ACEA;EUmLJ;IXjLI;;;ACFA;EUmLJ;IAaI;IACA;IACA,cTlIG;ISmIH;IACA;;;;AAIJ;EACE,YT1IK;;;AS6IP;EACE;;;AAGF;EACE;;AX1MA;EACE;;ACRA;EUgNJ;IXpMI;;;;AWyMJ;EACE;EACA,OTrJK;ESsJL,QTtJK;ESuJL;EACA,OTnJK;ESoJL,QTpJK;ESqJL,kBZpMwB;EYqMxB;EACA;EACA,YACE;EAEF;EACA;;;AAGF;EACE;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA,YACE;;;AAMF;EACE;EACA;EACA;EACA;EACA;EACA;;AAGF;EACE,QTxLI;ESyLJ;;AVjQA;EU+PF;IAKI,OTzKiB;IS0KjB,YACE;;;AAKN;EACE,kBZpPsB;;AExBtB;EU2QF;IAII;;;AV/QF;EUmRF;IAEI;;;AAIJ;EACE;;AAGF;EACE;EACA;EACA;EACA,YACE;;AVlSF;EUwSA;IACE;IACA;IACA;;;AAIJ;EACE,aTxOI;;ADxEJ;EU+SF;IAII;;;;AC9TN;EACE;EACA;EACA;EACA,eV0EK;EUzEL;EACA,eVkFc;EUjFd,YACE;;;AAIJ;EACE;EACA;EACA;;;AAGF;AAAA;EAEE;EACA;EACA,kBbIuB;EaHvB;EACA;;AZNA;AAAA;EACE;;ACRA;EWOJ;AAAA;IZKI;;;AYKF;AAAA;EACE;;;AAOE;AAAA;EAEE;;AAGF;EACE,gBVkCD;;;AU3BL;EACE;;;AC9CF;EACE;EACA;EACA,kBdcoB;EcbpB;EACA,eX+EY;;;AW1EhB;EACE,cdUa;;;AcyCf;AAAA;AAAA;EAGE;EACA,eXMK;EWLL,kBdlDsB;EcmDtB,eXgBc;EWfd;EACA;EACA;EACA;;AAIA;AAAA;AAAA;EACE,OXLG;EWMH;EACA;EACA;EACA;EACA,SXVG;EWWH;EACA;EACA,OdhFc;EciFd;;AAEA;AAAA;AAAA;EACE,MdpFY;;AcuFd;AAAA;AAAA;EACE;EACA;EACA;;AAGF;AAAA;AAAA;EACE;EACA;;AAMF;AAAA;AAAA;EACE;EACA;;;AASJ;EACE;EACA,SX/CG;EWgDH;EACA;EACA,eXtCY;;AWyCd;AAAA;EAEE;EACA;EACA;;;AAUJ;EACE;EACA,eXrEK;;AW6CL;EACE;EACA,SX/CG;EWgDH;EACA;EACA,eXtCY;;AWyCd;AAAA;EAEE;EACA;EACA;;;AAwBF;AAAA;EAEE;EACA,SXpFG;EWqFH;EACA;EACA,eX3EY;;;AWmFhB;EACE;EACA;EACA;EACA;;AAEA;AAAA;EAEE;EACA;EACA,kBdhKoB;EciKpB;;Ab9KF;AAAA;EACE;;ACEA;EYsKF;AAAA;IbpKE;;;Aa8KF;EACE;EACA,eXjHG;EWkHH,cXlHG;;AWqHL;EACE;EACA;;;AAKJ;AAAA;EAEE,SX9HK;EW+HL,eX/HK;EWgIL;EACA;EACA,eXtHc;;AWwHd;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAIE;EACA;EACA;EACA;EACA;EACA;EACA;;;AAKJ;EACE;EACA;EACA;;;AAIF;AAAA;EAEE,YdnNsB;EcsNpB,OdrNoB;;;Ac4NxB;EACE,Yd9NsB;;;AepBxB;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAKF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;ACvOF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAKF;EACE;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;;;AdrBE;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;AAQR;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAKF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AfhHA;EACE;;ACYA;EeZJ;IhBII;;;;AAKF;EACE;;ACEA;EeRJ;IhBUI;;;;AAKF;EACE;;ACRA;EeJJ;IhBgBI;;;;AAKF;EACE;;AClBA;EeAJ;IhBsBI;;;;AAKF;EACE;;AC5BA;EeIJ;IhB4BI;;;;AAKF;EACE;;ACtCA;EeQJ;IhBkCI;IACA,aEhDuB;;;;AFqDzB;EACE;EACA,aEvDuB;;ADKvB;EeYJ;IhB0CI;;;;AAKF;EACE;EACA,aElEuB;;ADKvB;EegBJ;IhBiDI;;;;AAKF;EACE;EACA,aE7EuB;;ADKvB;EeoBJ;IhBwDI;;;;AAKF;EACE;EACA,aExFuB;;ADKvB;EewBJ;IhB+DI;;;;AgB3DJ;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE,adxDiB;;;Ac2DnB;EACE,ad1DyB;;;Ac6D3B;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AC/EF;EACE;EACA;EACA;;AAGE;EACE;;;ACLN;EACE;EACA;;;AAQA;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AjBlCA;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AAaN;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AjB7GA;EiBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjB/IJ;EiBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjB/IJ;EiBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjB/IJ;EiBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjB/IJ;EiBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AC3JR;EACE;AAAA;AAAA;AAAA;AAAA;AAAA;IAME;;EAGF;IACE;IACA;;EAGF;IACE;IACA;IACA;;EAGF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;;EAGF;IACE;;EAGF;IACE;IACA;;;ACvCJ;EACE;EACA;EACA;EACA;EACA;EACA;EACA;;;AAGF;AAAA;EAEE,OrBCW;EqBAX,kBrBNsB;EqBOtB;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;;;ACnBF;EACE;;;AAGF;EACI;EACA;EACA,enB2EY;EmB1EZ;EACA;;AAEA;EACI,OnB6BI;EmB5BJ;EACA;EACA;EACA;EACA;EACA;;AAGJ;EACE,OnBmBM;EmBlBN;EACA;EACA;EACA;EACA;;;AAIN;EACI;EACA;EACA,enBgDY;EmB/CZ;EACA;;AACA;EACE;EACA;EACA,OnBCM;EmBAN;EACA;EACA;EACA;EACA;;;AAIN;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAIJ;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAMJ;EACI;EACA;EACA,enBEY;EmBDZ;EACA;;AAEA;EACI,OnBhDG;EmBiDH;EACA;EACA;EACA;EACA;EACA;;AAGJ;EACE,OnB1DK;EmB2DL;EACA;EACA;EACA;EACA;;;AAIN;EACI;EACA;EACA,enBzBY;EmB0BZ;EACA;;AACA;EACE;EACA;EACA,OnB5EK;EmB6EL;EACA;EACA;EACA;EACA;;;AAIN;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAIJ;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAMJ;EACI;EACA;EACA,enBvEY;EmBwEZ;EACA;;AAEA;EACI,OnBjHK;EmBkHL;EACA;EACA;EACA;EACA;EACA;;AAGJ;EACE,OnB3HO;EmB4HP;EACA;EACA;EACA;EACA;;;AAIN;EACI;EACA;EACA,enBlGY;EmBmGZ;EACA;;AACA;EACE;EACA;EACA,OnB7IO;EmB8IP;EACA;EACA;EACA;EACA;;;AAIN;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAIJ;EACE;EACA;;AAEA;EACE;;AAGF;EACE","sourcesContent":["/*\ngenerated by accessible-pygments \nCopyright (c) 2022, Quansight Labs\nLicensed under the BSD license, see LICENSE for details.\n--\ngenerated by Pygments \nCopyright 2006-2025 by the Pygments team.\nLicensed under the BSD license, see LICENSE for details.\n*/\n\n.highlight .hll { background-color: #0969da4a }\n.highlight .c { color: #6E7781 } /* Comment */\n.highlight .err { color: #CF222E } /* Error */\n.highlight .k { color: #CF222E } /* Keyword */\n.highlight .l { color: #953800 } /* Literal */\n.highlight .n { color: #8250DF } /* Name */\n.highlight .o { color: #116329 } /* Operator */\n.highlight .p { color: #24292F } /* Punctuation */\n.highlight .ch { color: #6E7781 } /* Comment.Hashbang */\n.highlight .cm { color: #6E7781 } /* Comment.Multiline */\n.highlight .cp { color: #6E7781 } /* Comment.Preproc */\n.highlight .cpf { color: #6E7781 } /* Comment.PreprocFile */\n.highlight .c1 { color: #6E7781 } /* Comment.Single */\n.highlight .cs { color: #6E7781 } /* Comment.Special */\n.highlight .gd { color: #0550AE } /* Generic.Deleted */\n.highlight .ge { font-style: italic } /* Generic.Emph */\n.highlight .gr { color: #CF222E } /* Generic.Error */\n.highlight .gh { color: #0550AE } /* Generic.Heading */\n.highlight .gs { font-weight: bold } /* Generic.Strong */\n.highlight .gu { color: #0550AE } /* Generic.Subheading */\n.highlight .kc { color: #0550AE } /* Keyword.Constant */\n.highlight .kd { color: #CF222E } /* Keyword.Declaration */\n.highlight .kn { color: #CF222E } /* Keyword.Namespace */\n.highlight .kp { color: #CF222E } /* Keyword.Pseudo */\n.highlight .kr { color: #CF222E } /* Keyword.Reserved */\n.highlight .kt { color: #CF222E } /* Keyword.Type */\n.highlight .ld { color: #953800 } /* Literal.Date */\n.highlight .m { color: #953800 } /* Literal.Number */\n.highlight .s { color: #0550AE } /* Literal.String */\n.highlight .na { color: #953800 } /* Name.Attribute */\n.highlight .nb { color: #953800 } /* Name.Builtin */\n.highlight .nc { color: #0550AE } /* Name.Class */\n.highlight .no { color: #0550AE } /* Name.Constant */\n.highlight .nd { color: #953800 } /* Name.Decorator */\n.highlight .ni { color: #116329 } /* Name.Entity */\n.highlight .ne { color: #8250DF } /* Name.Exception */\n.highlight .nf { color: #0550AE } /* Name.Function */\n.highlight .nl { color: #953800 } /* Name.Label */\n.highlight .nn { color: #24292F } /* Name.Namespace */\n.highlight .nx { color: #8250DF } /* Name.Other */\n.highlight .py { color: #0550AE } /* Name.Property */\n.highlight .nt { color: #116329 } /* Name.Tag */\n.highlight .nv { color: #953800 } /* Name.Variable */\n.highlight .ow { color: #8250DF } /* Operator.Word */\n.highlight .pm { color: #24292F } /* Punctuation.Marker */\n.highlight .w { color: #24292F } /* Text.Whitespace */\n.highlight .mb { color: #953800 } /* Literal.Number.Bin */\n.highlight .mf { color: #953800 } /* Literal.Number.Float */\n.highlight .mh { color: #953800 } /* Literal.Number.Hex */\n.highlight .mi { color: #953800 } /* Literal.Number.Integer */\n.highlight .mo { color: #953800 } /* Literal.Number.Oct */\n.highlight .sa { color: #0550AE } /* Literal.String.Affix */\n.highlight .sb { color: #0550AE } /* Literal.String.Backtick */\n.highlight .sc { color: #0550AE } /* Literal.String.Char */\n.highlight .dl { color: #0550AE } /* Literal.String.Delimiter */\n.highlight .sd { color: #0550AE } /* Literal.String.Doc */\n.highlight .s2 { color: #0550AE } /* Literal.String.Double */\n.highlight .se { color: #0550AE } /* Literal.String.Escape */\n.highlight .sh { color: #0550AE } /* Literal.String.Heredoc */\n.highlight .si { color: #0550AE } /* Literal.String.Interpol */\n.highlight .sx { color: #0550AE } /* Literal.String.Other */\n.highlight .sr { color: #0550AE } /* Literal.String.Regex */\n.highlight .s1 { color: #0550AE } /* Literal.String.Single */\n.highlight .ss { color: #0550AE } /* Literal.String.Symbol */\n.highlight .bp { color: #953800 } /* Name.Builtin.Pseudo */\n.highlight .fm { color: #0550AE } /* Name.Function.Magic */\n.highlight .vc { color: #953800 } /* Name.Variable.Class */\n.highlight .vg { color: #953800 } /* Name.Variable.Global */\n.highlight .vi { color: #953800 } /* Name.Variable.Instance */\n.highlight .vm { color: #953800 } /* Name.Variable.Magic */\n.highlight .il { color: #953800 } /* Literal.Number.Integer.Long */\n","/*! normalize.css v8.0.1 | MIT License | github.com/necolas/normalize.css */\n\n/* Document\n ========================================================================== */\n\n/**\n * 1. Correct the line height in all browsers.\n * 2. Prevent adjustments of font size after orientation changes in iOS.\n */\n\nhtml {\n line-height: 1.15; /* 1 */\n text-size-adjust: 100%; /* 2 */\n}\n\n/* Sections\n ========================================================================== */\n\n/**\n * Remove the margin in all browsers.\n */\n\nbody {\n margin: 0;\n}\n\n/**\n * Render the `main` element consistently in IE.\n */\n\nmain {\n display: block;\n}\n\n/**\n * Correct the font size and margin on `h1` elements within `section` and\n * `article` contexts in Chrome, Firefox, and Safari.\n */\n\nh1 {\n font-size: 2em;\n margin: 0.67em 0;\n}\n\n/* Grouping content\n ========================================================================== */\n\n/**\n * 1. Add the correct box sizing in Firefox.\n * 2. Show the overflow in Edge and IE.\n */\n\nhr {\n box-sizing: content-box; /* 1 */\n height: 0; /* 1 */\n overflow: visible; /* 2 */\n}\n\n/**\n * 1. Correct the inheritance and scaling of font size in all browsers.\n * 2. Correct the odd `em` font sizing in all browsers.\n */\n\npre {\n font-family: monospace; /* 1 */\n font-size: 1em; /* 2 */\n}\n\n/* Text-level semantics\n ========================================================================== */\n\n/**\n * Remove the gray background on active links in IE 10.\n */\n\na {\n background-color: transparent;\n}\n\n/**\n * 1. Remove the bottom border in Chrome 57-\n * 2. Add the correct text decoration in Chrome, Edge, IE, Opera, and Safari.\n */\n\nabbr[title] {\n border-bottom: none; /* 1 */\n text-decoration: underline; /* 2 */\n text-decoration: underline dotted; /* 2 */\n}\n\n/**\n * Add the correct font weight in Chrome, Edge, and Safari.\n */\n\nb,\nstrong {\n font-weight: bolder;\n}\n\n/**\n * 1. Correct the inheritance and scaling of font size in all browsers.\n * 2. Correct the odd `em` font sizing in all browsers.\n */\n\ncode,\nkbd,\nsamp {\n font-family: monospace; /* 1 */\n font-size: 1em; /* 2 */\n}\n\n/**\n * Add the correct font size in all browsers.\n */\n\nsmall {\n font-size: 80%;\n}\n\n/**\n * Prevent `sub` and `sup` elements from affecting the line height in\n * all browsers.\n */\n\nsub,\nsup {\n font-size: 75%;\n line-height: 0;\n position: relative;\n vertical-align: baseline;\n}\n\nsub {\n bottom: -0.25em;\n}\n\nsup {\n top: -0.5em;\n}\n\n/* Embedded content\n ========================================================================== */\n\n/**\n * Remove the border on images inside links in IE 10.\n */\n\nimg {\n border-style: none;\n}\n\n/* Forms\n ========================================================================== */\n\n/**\n * 1. Change the font styles in all browsers.\n * 2. Remove the margin in Firefox and Safari.\n */\n\nbutton,\ninput,\noptgroup,\nselect,\ntextarea {\n font-family: inherit; /* 1 */\n font-size: 100%; /* 1 */\n line-height: 1.15; /* 1 */\n margin: 0; /* 2 */\n}\n\n/**\n * Show the overflow in IE.\n * 1. Show the overflow in Edge.\n */\n\nbutton,\ninput {\n /* 1 */\n overflow: visible;\n}\n\n/**\n * Remove the inheritance of text transform in Edge, Firefox, and IE.\n * 1. Remove the inheritance of text transform in Firefox.\n */\n\nbutton,\nselect {\n /* 1 */\n text-transform: none;\n}\n\n/**\n * Correct the inability to style clickable types in iOS and Safari.\n */\n\nbutton,\n[type=\"button\"],\n[type=\"reset\"],\n[type=\"submit\"] {\n appearance: button;\n}\n\n/**\n * Remove the inner border and padding in Firefox.\n */\n\nbutton::-moz-focus-inner,\n[type=\"button\"]::-moz-focus-inner,\n[type=\"reset\"]::-moz-focus-inner,\n[type=\"submit\"]::-moz-focus-inner {\n border-style: none;\n padding: 0;\n}\n\n/**\n * Restore the focus styles unset by the previous rule.\n */\n\nbutton:-moz-focusring,\n[type=\"button\"]:-moz-focusring,\n[type=\"reset\"]:-moz-focusring,\n[type=\"submit\"]:-moz-focusring {\n outline: 1px dotted ButtonText;\n}\n\n/**\n * Correct the padding in Firefox.\n */\n\nfieldset {\n padding: 0.35em 0.75em 0.625em;\n}\n\n/**\n * 1. Correct the text wrapping in Edge and IE.\n * 2. Correct the color inheritance from `fieldset` elements in IE.\n * 3. Remove the padding so developers are not caught out when they zero out\n * `fieldset` elements in all browsers.\n */\n\nlegend {\n box-sizing: border-box; /* 1 */\n color: inherit; /* 2 */\n display: table; /* 1 */\n max-width: 100%; /* 1 */\n padding: 0; /* 3 */\n white-space: normal; /* 1 */\n}\n\n/**\n * Add the correct vertical alignment in Chrome, Firefox, and Opera.\n */\n\nprogress {\n vertical-align: baseline;\n}\n\n/**\n * Remove the default vertical scrollbar in IE 10+.\n */\n\ntextarea {\n overflow: auto;\n}\n\n/**\n * 1. Add the correct box sizing in IE 10.\n * 2. Remove the padding in IE 10.\n */\n\n[type=\"checkbox\"],\n[type=\"radio\"] {\n box-sizing: border-box; /* 1 */\n padding: 0; /* 2 */\n}\n\n/**\n * Correct the cursor style of increment and decrement buttons in Chrome.\n */\n\n[type=\"number\"]::-webkit-inner-spin-button,\n[type=\"number\"]::-webkit-outer-spin-button {\n height: auto;\n}\n\n/**\n * 1. Correct the odd appearance in Chrome and Safari.\n * 2. Correct the outline style in Safari.\n */\n\n[type=\"search\"] {\n appearance: textfield; /* 1 */\n outline-offset: -2px; /* 2 */\n}\n\n/**\n * Remove the inner padding in Chrome and Safari on macOS.\n */\n\n[type=\"search\"]::-webkit-search-decoration {\n appearance: none;\n}\n\n/**\n * 1. Correct the inability to style clickable types in iOS and Safari.\n * 2. Change font properties to `inherit` in Safari.\n */\n\n::-webkit-file-upload-button {\n appearance: button; /* 1 */\n font: inherit; /* 2 */\n}\n\n/* Interactive\n ========================================================================== */\n\n/*\n * Add the correct display in Edge, IE 10+, and Firefox.\n */\n\ndetails {\n display: block;\n}\n\n/*\n * Add the correct display in all browsers.\n */\n\nsummary {\n display: list-item;\n}\n\n/* Misc\n ========================================================================== */\n\n/**\n * Add the correct display in IE 10+.\n */\n\ntemplate {\n display: none;\n}\n\n/**\n * Add the correct display in IE 10.\n */\n\n[hidden] {\n display: none;\n}\n","// Base element style overrides\n// stylelint-disable selector-no-type, selector-max-type, selector-max-specificity, selector-max-id\n\n:root {\n color-scheme: $color-scheme;\n}\n\n* {\n box-sizing: border-box;\n}\n\nhtml {\n scroll-behavior: smooth;\n\n @include fs-4;\n}\n\nbody {\n font-family: $body-font-family;\n font-size: inherit;\n line-height: $body-line-height;\n color: $body-text-color;\n background-color: $body-background-color;\n overflow-wrap: break-word;\n}\n\nol,\nul,\ndl,\npre,\naddress,\nblockquote,\ntable,\ndiv,\nhr,\nform,\nfieldset,\nnoscript .table-wrapper {\n margin-top: 0;\n}\n\nh1,\nh2,\nh3,\nh4,\nh5,\nh6,\n#toctitle {\n margin-top: 0;\n margin-bottom: 1em;\n font-weight: 500;\n line-height: $body-heading-line-height;\n color: $body-heading-color;\n}\n\np {\n margin-top: 1em;\n margin-bottom: 1em;\n}\n\na {\n color: $link-color;\n text-decoration: none;\n}\n\na:not([class]) {\n text-decoration: underline;\n text-decoration-color: $border-color;\n text-underline-offset: 2px;\n\n &:hover {\n text-decoration-color: rgba($link-color, 0.45);\n }\n}\n\ncode {\n font-family: $mono-font-family;\n font-size: 0.75em;\n line-height: $body-line-height;\n}\n\nfigure,\npre {\n margin: 0;\n}\n\nli {\n margin: 0.25em 0;\n}\n\nimg {\n max-width: 100%;\n height: auto;\n}\n\nhr {\n height: 1px;\n padding: 0;\n margin: $sp-6 0;\n background-color: $border-color;\n border: 0;\n}\n\n// adds a GitHub-style sidebar to blockquotes\nblockquote {\n margin: 10px 0;\n\n // resets user-agent stylesheets for blockquotes\n margin-block-start: 0;\n margin-inline-start: 0;\n padding-left: 1rem;\n border-left: 3px solid $border-color;\n}\n","// Meshtastic Material 3 — Light color scheme for just-the-docs\n// Source: core/ui/.../Color.kt §8.2 (Light Scheme)\n//\n// Brand colors:\n// Primary (Light): #2D8F52 (Green 700)\n// Surface (Light): #F5F6FA (Neutral 50)\n\n$color-scheme: light;\n\n// Body / page background\n$body-background-color: #F5F6FA; // Neutral 50 — surfaceLight\n$sidebar-color: #ECEDF3; // Neutral 100 — surfaceContainerLight\n$body-text-color: #2C2D3C; // Neutral 800 — onSurfaceLight\n$body-heading-color: #2C2D3C; // Neutral 800\n\n// Links\n$link-color: #2D8F52; // Green 700 — primaryLight\n$nav-link-color: #2D8F52; // Green 700\n\n// Navigation\n$nav-child-link-color: #555668; // Neutral 600 — secondaryLight\n$search-result-preview-color: #555668;\n\n// Code\n$code-background-color: #ECEDF3; // Neutral 100\n$code-linenumber-color: #9496A6; // Neutral 400\n\n// Borders\n$border-color: #D5D6E0; // Neutral 200 — outlineVariantLight\n$table-background-color: #F5F6FA; // Neutral 50\n\n// Buttons\n$btn-primary-color: #2D8F52; // Green 700\n\n// Feedback / callouts\n$feedback-color: #E0E1EB; // surfaceContainerHighLight\n\n// Search\n$search-background-color: #FFFFFF; // surfaceContainerLowestLight\n","@mixin fs-1 {\n & {\n font-size: $font-size-1 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-1-sm !important;\n }\n}\n\n@mixin fs-2 {\n & {\n font-size: $font-size-2 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-3 !important;\n }\n}\n\n@mixin fs-3 {\n & {\n font-size: $font-size-3 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-4 !important;\n }\n}\n\n@mixin fs-4 {\n & {\n font-size: $font-size-4 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-5 !important;\n }\n}\n\n@mixin fs-5 {\n & {\n font-size: $font-size-5 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-6 !important;\n }\n}\n\n@mixin fs-6 {\n & {\n font-size: $font-size-6 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-7 !important;\n line-height: $body-heading-line-height;\n }\n}\n\n@mixin fs-7 {\n & {\n font-size: $font-size-7 !important;\n line-height: $body-heading-line-height;\n }\n\n @include mq(sm) {\n font-size: $font-size-8 !important;\n }\n}\n\n@mixin fs-8 {\n & {\n font-size: $font-size-8 !important;\n line-height: $body-heading-line-height;\n }\n\n @include mq(sm) {\n font-size: $font-size-9 !important;\n }\n}\n\n@mixin fs-9 {\n & {\n font-size: $font-size-9 !important;\n line-height: $body-heading-line-height;\n }\n\n @include mq(sm) {\n font-size: $font-size-10 !important;\n }\n}\n\n@mixin fs-10 {\n & {\n font-size: $font-size-10 !important;\n line-height: $body-heading-line-height;\n }\n\n @include mq(sm) {\n font-size: $font-size-10-sm !important;\n }\n}\n","// Media query\n\n// Media query mixin\n// Usage:\n// @include mq(md) {\n// ..medium and up styles\n// }\n@mixin mq($name) {\n // Retrieves the value from the key\n $value: map-get($media-queries, $name);\n\n // If the key exists in the map\n @if $value {\n // Prints a media query based on the value\n @media (min-width: $value) {\n @content;\n }\n } @else {\n @warn \"No value could be retrieved from `#{$media-query}`. Please make sure it is defined in `$media-queries` map.\";\n }\n}\n\n// Responsive container\n\n@mixin container {\n padding-right: $gutter-spacing-sm;\n padding-left: $gutter-spacing-sm;\n\n @include mq(md) {\n padding-right: $gutter-spacing;\n padding-left: $gutter-spacing;\n }\n}\n","// Typography\n\n// prettier-ignore\n$body-font-family: system-ui, -apple-system, blinkmacsystemfont, \"Segoe UI\",\n roboto, \"Helvetica Neue\", arial, sans-serif, \"Segoe UI Emoji\" !default;\n$mono-font-family: \"SFMono-Regular\", menlo, consolas, monospace !default;\n$root-font-size: 16px !default; // DEPRECATED: previously base font-size for rems\n$body-line-height: 1.4 !default;\n$content-line-height: 1.6 !default;\n$body-heading-line-height: 1.25 !default;\n\n// Font size\n// `-sm` suffix is the size at the small (and above) media query\n\n$font-size-1: 0.5625rem !default;\n$font-size-1-sm: 0.625rem !default;\n$font-size-2: 0.6875rem !default; // h4 - uppercased!, h6 not uppercased, text-small\n$font-size-3: 0.75rem !default; // h5\n$font-size-4: 0.875rem !default;\n$font-size-5: 1rem !default; // h3\n$font-size-6: 1.125rem !default; // h2\n$font-size-7: 1.5rem !default;\n$font-size-8: 2rem !default; // h1\n$font-size-9: 2.25rem !default;\n$font-size-10: 2.625rem !default;\n$font-size-10-sm: 3rem !default;\n\n// Colors\n\n$white: #fff !default;\n$grey-dk-000: #959396 !default;\n$grey-dk-100: #5c5962 !default;\n$grey-dk-200: #44434d !default;\n$grey-dk-250: #302d36 !default;\n$grey-dk-300: #27262b !default;\n$grey-lt-000: #f5f6fa !default;\n$grey-lt-100: #eeebee !default;\n$grey-lt-200: #ecebed !default;\n$grey-lt-300: #e6e1e8 !default;\n$purple-000: #7253ed !default;\n$purple-100: #5e41d0 !default;\n$purple-200: #4e26af !default;\n$purple-300: #381885 !default;\n$blue-000: #2c84fa !default;\n$blue-100: #2869e6 !default;\n$blue-200: #264caf !default;\n$blue-300: #183385 !default;\n$green-000: #41d693 !default;\n$green-100: #11b584 !default;\n$green-200: #009c7b !default;\n$green-300: #026e57 !default;\n$yellow-000: #ffeb82 !default;\n$yellow-100: #fadf50 !default;\n$yellow-200: #f7d12e !default;\n$yellow-300: #e7af06 !default;\n$red-000: #f77e7e !default;\n$red-100: #f96e65 !default;\n$red-200: #e94c4c !default;\n$red-300: #dd2e2e !default;\n\n// Spacing\n\n$spacing-unit: 1rem; // 1rem == 16px\n\n$spacers: (\n sp-0: 0,\n sp-1: $spacing-unit * 0.25,\n sp-2: $spacing-unit * 0.5,\n sp-3: $spacing-unit * 0.75,\n sp-4: $spacing-unit,\n sp-5: $spacing-unit * 1.5,\n sp-6: $spacing-unit * 2,\n sp-7: $spacing-unit * 2.5,\n sp-8: $spacing-unit * 3,\n sp-9: $spacing-unit * 3.5,\n sp-10: $spacing-unit * 4,\n) !default;\n$sp-1: map-get($spacers, sp-1) !default; // 0.25 rem == 4px\n$sp-2: map-get($spacers, sp-2) !default; // 0.5 rem == 8px\n$sp-3: map-get($spacers, sp-3) !default; // 0.75 rem == 12px\n$sp-4: map-get($spacers, sp-4) !default; // 1 rem == 16px\n$sp-5: map-get($spacers, sp-5) !default; // 1.5 rem == 24px\n$sp-6: map-get($spacers, sp-6) !default; // 2 rem == 32px\n$sp-7: map-get($spacers, sp-7) !default; // 2.5 rem == 40px\n$sp-8: map-get($spacers, sp-8) !default; // 3 rem == 48px\n$sp-9: map-get($spacers, sp-9) !default; // 3.5 rem == 56px\n$sp-10: map-get($spacers, sp-10) !default; // 4 rem == 64px\n\n// Borders\n\n$border: 1px solid !default;\n$border-radius: 4px !default;\n$border-color: $grey-lt-100 !default;\n\n// Grid system\n\n$gutter-spacing: $sp-6 !default;\n$gutter-spacing-sm: $sp-4 !default;\n$nav-width: 16.5rem !default;\n$nav-width-md: 15.5rem !default;\n$nav-list-item-height: $sp-6 !default;\n$nav-list-item-height-sm: $sp-8 !default;\n$nav-list-expander-right: true;\n$content-width: 50rem !default;\n$header-height: 3.75rem !default;\n$search-results-width: $content-width - $nav-width !default;\n$transition-duration: 400ms;\n\n// Media queries in pixels\n\n$media-queries: (\n xs: 20rem,\n sm: 31.25rem,\n md: $content-width,\n lg: $content-width + $nav-width,\n xl: 87.5rem,\n) !default;\n","// The basic two column layout\n\n.side-bar {\n z-index: 0;\n display: flex;\n flex-wrap: wrap;\n background-color: $sidebar-color;\n\n @include mq(md) {\n flex-flow: column nowrap;\n position: fixed;\n width: $nav-width-md;\n height: 100%;\n border-right: $border $border-color;\n align-items: flex-end;\n }\n\n @include mq(lg) {\n width: calc((100% - #{$nav-width + $content-width}) / 2 + #{$nav-width});\n min-width: $nav-width;\n }\n\n & + .main {\n @include mq(md) {\n margin-left: $nav-width-md;\n }\n\n @include mq(lg) {\n // stylelint-disable function-name-case\n // disable for Max(), we want to use the CSS max() function\n margin-left: Max(\n #{$nav-width},\n calc((100% - #{$nav-width + $content-width}) / 2 + #{$nav-width})\n );\n // stylelint-enable function-name-case\n }\n\n .main-header {\n display: none;\n background-color: $sidebar-color;\n\n @include mq(md) {\n display: flex;\n background-color: $body-background-color;\n }\n\n &.nav-open {\n display: block;\n\n @include mq(md) {\n display: flex;\n }\n }\n }\n }\n}\n\n.main {\n margin: auto;\n\n @include mq(md) {\n position: relative;\n max-width: $content-width;\n }\n}\n\n.main-content-wrap {\n padding-top: $gutter-spacing-sm;\n padding-bottom: $gutter-spacing-sm;\n\n @include container;\n\n @include mq(md) {\n padding-top: $gutter-spacing;\n padding-bottom: $gutter-spacing;\n }\n}\n\n.main-header {\n z-index: 0;\n border-bottom: $border $border-color;\n\n @include mq(md) {\n display: flex;\n justify-content: space-between;\n height: $header-height;\n }\n}\n\n.site-nav,\n.site-header,\n.site-footer {\n width: 100%;\n\n @include mq(lg) {\n width: $nav-width;\n }\n}\n\n.site-nav {\n display: none;\n\n &.nav-open {\n display: block;\n }\n\n @include mq(md) {\n display: block;\n padding-top: $sp-8;\n padding-bottom: $gutter-spacing-sm;\n overflow-y: auto;\n flex: 1 1 auto;\n }\n}\n\n.site-header {\n display: flex;\n min-height: $header-height;\n align-items: center;\n\n @include mq(md) {\n height: $header-height;\n max-height: $header-height;\n border-bottom: $border $border-color;\n }\n}\n\n.site-title {\n flex-grow: 1;\n display: flex;\n height: 100%;\n align-items: center;\n padding-top: $sp-3;\n padding-bottom: $sp-3;\n color: $body-heading-color;\n\n @include container;\n\n @include fs-6;\n\n @include mq(md) {\n padding-top: $sp-2;\n padding-bottom: $sp-2;\n }\n}\n\n@if variable-exists(logo) {\n .site-logo {\n width: 100%;\n height: 100%;\n background-image: url($logo);\n background-repeat: no-repeat;\n background-position: left center;\n background-size: contain;\n }\n}\n\n.site-button {\n display: flex;\n height: 100%;\n padding: $gutter-spacing-sm;\n align-items: center;\n}\n\n@include mq(md) {\n .site-header .site-button {\n display: none;\n }\n}\n\n.site-title:hover {\n background-image: linear-gradient(\n -90deg,\n rgba($feedback-color, 1) 0%,\n rgba($feedback-color, 0.8) 80%,\n rgba($feedback-color, 0) 100%\n );\n}\n\n.site-button:hover {\n background-image: linear-gradient(\n -90deg,\n rgba($feedback-color, 1) 0%,\n rgba($feedback-color, 0.8) 100%\n );\n}\n\n.site-footer {\n position: absolute;\n bottom: 0;\n left: 0;\n padding-top: $sp-4;\n padding-bottom: $sp-4;\n\n @include container;\n\n @include fs-2;\n\n @include mq(md) {\n position: static;\n justify-self: end;\n }\n}\n\n.icon {\n width: $sp-5;\n height: $sp-5;\n color: $link-color;\n}\n","@charset \"UTF-8\";\n\n// Styles for rendered markdown in the .main-content container\n// stylelint-disable selector-no-type, max-nesting-depth, selector-max-compound-selectors, selector-max-type, selector-max-specificity, selector-max-id\n\n.main-content {\n line-height: $content-line-height;\n\n ol,\n ul,\n dl,\n pre,\n address,\n blockquote,\n .table-wrapper {\n margin-top: 0.5em;\n }\n\n a {\n overflow: hidden;\n text-overflow: ellipsis;\n }\n\n ul,\n ol {\n padding-left: 1.5em;\n }\n\n li {\n .highlight {\n margin-top: $sp-1;\n }\n }\n\n ol {\n list-style-type: none;\n counter-reset: step-counter;\n\n > li {\n position: relative;\n\n &::before {\n position: absolute;\n top: 0.2em;\n left: -1.6em;\n color: $grey-dk-000;\n content: counter(step-counter);\n counter-increment: step-counter;\n @include fs-3;\n\n @include mq(sm) {\n top: 0.11em;\n }\n }\n\n ol {\n counter-reset: sub-counter;\n\n > li {\n &::before {\n content: counter(sub-counter, lower-alpha);\n counter-increment: sub-counter;\n }\n }\n }\n }\n }\n\n ul {\n list-style: none;\n\n > li {\n &::before {\n position: absolute;\n margin-left: -1.4em;\n color: $grey-dk-000;\n content: \"•\";\n }\n }\n }\n\n .task-list-item {\n &::before {\n content: \"\";\n }\n }\n\n .task-list-item-checkbox {\n margin-right: 0.6em;\n margin-left: -1.4em;\n\n // The same margin-left is used above for ul > li::before\n }\n\n hr + * {\n margin-top: 0;\n }\n\n h1:first-of-type {\n margin-top: 0.5em;\n }\n\n dl {\n display: grid;\n grid-template: auto / 10em 1fr;\n }\n\n dt,\n dd {\n margin: 0.25em 0;\n }\n\n dt {\n grid-column: 1;\n font-weight: 500;\n text-align: right;\n\n &::after {\n content: \":\";\n }\n }\n\n dd {\n grid-column: 2;\n margin-bottom: 0;\n margin-left: 1em;\n\n blockquote,\n div,\n dl,\n dt,\n h1,\n h2,\n h3,\n h4,\n h5,\n h6,\n li,\n ol,\n p,\n pre,\n table,\n ul,\n .table-wrapper {\n &:first-child {\n margin-top: 0;\n }\n }\n }\n\n dd,\n ol,\n ul {\n dl:first-child {\n dt:first-child,\n dd:nth-child(2) {\n margin-top: 0;\n }\n }\n }\n\n .anchor-heading {\n position: absolute;\n right: -$sp-4;\n width: $sp-5;\n height: 100%;\n padding-right: $sp-1;\n padding-left: $sp-1;\n overflow: visible;\n\n @include mq(md) {\n right: auto;\n left: -$sp-5;\n }\n\n svg {\n display: inline-block;\n width: 100%;\n height: 100%;\n color: $link-color;\n visibility: hidden;\n }\n }\n\n .anchor-heading:hover,\n .anchor-heading:focus,\n h1:hover > .anchor-heading,\n h2:hover > .anchor-heading,\n h3:hover > .anchor-heading,\n h4:hover > .anchor-heading,\n h5:hover > .anchor-heading,\n h6:hover > .anchor-heading {\n svg {\n visibility: visible;\n }\n }\n\n summary {\n cursor: pointer;\n }\n\n h1,\n h2,\n h3,\n h4,\n h5,\n h6,\n #toctitle {\n position: relative;\n margin-top: 1.5em;\n margin-bottom: 0.25em;\n\n + table,\n + .table-wrapper,\n + .code-example,\n + .highlighter-rouge,\n + .sectionbody .listingblock {\n margin-top: 1em;\n }\n\n + p:not(.label) {\n margin-top: 0;\n }\n }\n\n > h1:first-child,\n > h2:first-child,\n > h3:first-child,\n > h4:first-child,\n > h5:first-child,\n > h6:first-child,\n > .sect1:first-child > h2,\n > .sect2:first-child > h3,\n > .sect3:first-child > h4,\n > .sect4:first-child > h5,\n > .sect5:first-child > h6 {\n margin-top: $sp-2;\n }\n}\n","// Main nav, breadcrumb, etc...\n// stylelint-disable selector-no-type, max-nesting-depth, selector-max-compound-selectors, selector-max-type, selector-max-specificity\n\n.nav-list {\n padding: 0;\n margin-top: 0;\n margin-bottom: 0;\n list-style: none;\n\n .nav-list-item {\n position: relative;\n margin: 0;\n\n @include fs-4;\n\n @include mq(md) {\n @include fs-3;\n }\n\n .nav-list-link {\n display: block;\n min-height: $nav-list-item-height-sm;\n padding-top: $sp-1;\n padding-bottom: $sp-1;\n line-height: #{$nav-list-item-height-sm - 2 * $sp-1};\n @if $nav-list-expander-right {\n padding-right: $nav-list-item-height-sm;\n padding-left: $gutter-spacing-sm;\n } @else {\n padding-right: $gutter-spacing-sm;\n padding-left: $nav-list-item-height-sm;\n }\n\n @include mq(md) {\n min-height: $nav-list-item-height;\n line-height: #{$nav-list-item-height - 2 * $sp-1};\n @if $nav-list-expander-right {\n padding-right: $nav-list-item-height;\n padding-left: $gutter-spacing;\n } @else {\n padding-right: $gutter-spacing;\n padding-left: $nav-list-item-height;\n }\n }\n\n &.external > svg {\n width: $sp-4;\n height: $sp-4;\n vertical-align: text-bottom;\n }\n\n &.active {\n font-weight: 600;\n text-decoration: none;\n }\n\n &:hover,\n &.active {\n color: darken($link-color, 5%);\n background-image: linear-gradient(\n -90deg,\n rgba($feedback-color, 1) 0%,\n rgba($feedback-color, 0.8) 80%,\n rgba($feedback-color, 0) 100%\n );\n }\n }\n\n .nav-list-expander {\n position: absolute;\n @if $nav-list-expander-right {\n right: 0;\n }\n\n width: $nav-list-item-height-sm;\n height: $nav-list-item-height-sm;\n padding: #{$nav-list-item-height-sm * 0.25};\n color: $link-color;\n\n @include mq(md) {\n width: $nav-list-item-height;\n height: $nav-list-item-height;\n padding: #{$nav-list-item-height * 0.25};\n }\n\n &:hover {\n background-image: linear-gradient(\n -90deg,\n rgba($feedback-color, 1) 0%,\n rgba($feedback-color, 0.8) 100%\n );\n }\n\n @if $nav-list-expander-right {\n svg {\n transform: rotate(90deg);\n }\n }\n }\n\n > .nav-list {\n display: none;\n padding-left: $sp-3;\n list-style: none;\n\n .nav-list-item {\n position: relative;\n\n .nav-list-link {\n color: $nav-child-link-color;\n }\n\n .nav-list-expander {\n color: $nav-child-link-color;\n }\n }\n }\n\n &.active {\n > .nav-list-expander svg {\n @if $nav-list-expander-right {\n transform: rotate(-90deg);\n } @else {\n transform: rotate(90deg);\n }\n }\n\n > .nav-list {\n display: block;\n }\n }\n }\n}\n\n.nav-category {\n padding: $sp-2 $gutter-spacing-sm;\n font-weight: 600;\n text-align: start;\n text-transform: uppercase;\n border-bottom: $border $border-color;\n @include fs-2;\n\n @include mq(md) {\n padding: $sp-2 $gutter-spacing;\n margin-top: $gutter-spacing-sm;\n text-align: start;\n\n &:first-child {\n margin-top: 0;\n }\n }\n}\n\n.nav-list.nav-category-list {\n > .nav-list-item {\n margin: 0;\n\n > .nav-list {\n padding: 0;\n\n > .nav-list-item {\n > .nav-list-link {\n color: $link-color;\n }\n\n > .nav-list-expander {\n color: $link-color;\n }\n }\n }\n }\n}\n\n// Aux nav\n\n.aux-nav {\n height: 100%;\n overflow-x: auto;\n @include fs-2;\n\n .aux-nav-list {\n display: flex;\n height: 100%;\n padding: 0;\n margin: 0;\n list-style: none;\n }\n\n .aux-nav-list-item {\n display: inline-block;\n height: 100%;\n padding: 0;\n margin: 0;\n }\n\n @include mq(md) {\n padding-right: $gutter-spacing-sm;\n }\n}\n\n// Breadcrumb nav\n\n.breadcrumb-nav {\n @include mq(md) {\n margin-top: -$sp-4;\n }\n}\n\n.breadcrumb-nav-list {\n padding-left: 0;\n margin-bottom: $sp-3;\n list-style: none;\n}\n\n.breadcrumb-nav-list-item {\n display: table-cell;\n @include fs-2;\n\n &::before {\n display: none;\n }\n\n &::after {\n display: inline-block;\n margin-right: $sp-2;\n margin-left: $sp-2;\n color: $grey-dk-000;\n content: \"/\";\n }\n\n &:last-child {\n &::after {\n content: \"\";\n }\n }\n}\n","// Typography\n// stylelint-disable selector-no-type, selector-max-type, selector-max-specificity, selector-max-id\n\nh1,\n.text-alpha {\n font-weight: 300;\n\n @include fs-8;\n}\n\nh2,\n.text-beta,\n#toctitle {\n @include fs-6;\n}\n\nh3,\n.text-gamma {\n @include fs-5;\n}\n\nh4,\n.text-delta {\n font-weight: 400;\n text-transform: uppercase;\n letter-spacing: 0.1em;\n\n @include fs-2;\n}\n\nh4 code {\n text-transform: none;\n}\n\nh5,\n.text-epsilon {\n @include fs-3;\n}\n\nh6,\n.text-zeta {\n @include fs-2;\n}\n\n.text-small {\n @include fs-2;\n}\n\n.text-mono {\n font-family: $mono-font-family !important;\n}\n\n.text-left {\n text-align: left !important;\n}\n\n.text-center {\n text-align: center !important;\n}\n\n.text-right {\n text-align: right !important;\n}\n","// Labels (not the form kind)\n\n// this :not() prevents a style clash with Mermaid.js's\n// diagram labels, which also use .label\n// for more, see https://github.com/just-the-docs/just-the-docs/issues/1272\n// and the accompanying PR\n.label:not(g),\n.label-blue:not(g) {\n display: inline-block;\n padding: 0.16em 0.56em;\n margin-right: $sp-2;\n margin-left: $sp-2;\n color: $white;\n text-transform: uppercase;\n vertical-align: middle;\n background-color: $blue-100;\n border-radius: 12px;\n\n @include fs-2;\n}\n\n.label-green:not(g) {\n background-color: $green-300;\n}\n\n.label-purple:not(g) {\n background-color: $purple-100;\n}\n\n.label-red:not(g) {\n background-color: $red-300;\n}\n\n.label-yellow:not(g) {\n color: $grey-dk-200;\n background-color: $yellow-200;\n}\n","// Buttons and things that look like buttons\n// stylelint-disable color-named\n\n.btn {\n display: inline-block;\n box-sizing: border-box;\n padding: 0.3em 1em;\n margin: 0;\n font-family: inherit;\n font-size: inherit;\n font-weight: 500;\n line-height: 1.5;\n color: $link-color;\n text-decoration: none;\n vertical-align: baseline;\n cursor: pointer;\n background-color: $base-button-color;\n border-width: 0;\n border-radius: $border-radius;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n appearance: none;\n\n &:focus {\n text-decoration: none;\n outline: none;\n box-shadow: 0 0 0 3px rgba(blue, 0.25);\n }\n\n &:focus:hover,\n &.selected:focus {\n box-shadow: 0 0 0 3px rgba(blue, 0.25);\n }\n\n &:hover,\n &.zeroclipboard-is-hover {\n color: darken($link-color, 2%);\n }\n\n &:hover,\n &:active,\n &.zeroclipboard-is-hover,\n &.zeroclipboard-is-active {\n text-decoration: none;\n background-color: darken($base-button-color, 1%);\n }\n\n &:active,\n &.selected,\n &.zeroclipboard-is-active {\n background-color: darken($base-button-color, 3%);\n background-image: none;\n box-shadow: inset 0 2px 4px rgba(0, 0, 0, 0.15);\n }\n\n &.selected:hover {\n background-color: darken(#dcdcdc, 5%);\n }\n\n &:disabled,\n &.disabled {\n &,\n &:hover {\n color: rgba(102, 102, 102, 0.5);\n cursor: default;\n background-color: rgba(229, 229, 229, 0.5);\n background-image: none;\n box-shadow: none;\n }\n }\n}\n\n.btn-outline {\n color: $link-color;\n background: transparent;\n box-shadow: inset 0 0 0 2px $grey-lt-300;\n\n &:hover,\n &:active,\n &.zeroclipboard-is-hover,\n &.zeroclipboard-is-active {\n color: darken($link-color, 4%);\n text-decoration: none;\n background-color: transparent;\n box-shadow: inset 0 0 0 3px $grey-lt-300;\n }\n\n &:focus {\n text-decoration: none;\n outline: none;\n box-shadow:\n inset 0 0 0 2px $grey-dk-100,\n 0 0 0 3px rgba(blue, 0.25);\n }\n\n &:focus:hover,\n &.selected:focus {\n box-shadow: inset 0 0 0 2px $grey-dk-100;\n }\n}\n\n.btn-primary {\n @include btn-color($white, $btn-primary-color);\n}\n\n.btn-purple {\n @include btn-color($white, $purple-100);\n}\n\n.btn-blue {\n @include btn-color($white, $blue-200);\n}\n\n.btn-green {\n @include btn-color($white, $green-300);\n}\n\n.btn-reset {\n background: none;\n border: none;\n margin: 0;\n text-align: inherit;\n font: inherit;\n border-radius: 0;\n appearance: none;\n}\n","$color-scheme: light !default;\n$body-background-color: $white !default;\n$body-heading-color: $grey-dk-300 !default;\n$body-text-color: $grey-dk-100 !default;\n$link-color: $purple-000 !default;\n$nav-child-link-color: $grey-dk-100 !default;\n$sidebar-color: $grey-lt-000 !default;\n$base-button-color: #f7f7f7 !default;\n$btn-primary-color: $purple-100 !default;\n$code-background-color: $white !default;\n$feedback-color: darken($sidebar-color, 3%) !default;\n$table-background-color: $white !default;\n$search-background-color: $white !default;\n$search-result-preview-color: $grey-dk-100 !default;\n\n@import \"./vendor/accessible-pygments/github-light\";\n","// Colored button\n\n@mixin btn-color($fg, $bg) {\n color: $fg;\n background-color: darken($bg, 2%);\n background-image: linear-gradient(lighten($bg, 5%), darken($bg, 2%));\n box-shadow:\n 0 1px 3px rgba(0, 0, 0, 0.25),\n 0 4px 10px rgba(0, 0, 0, 0.12);\n\n &:hover,\n &.zeroclipboard-is-hover {\n color: $fg;\n background-color: darken($bg, 4%);\n background-image: linear-gradient((lighten($bg, 2%), darken($bg, 4%)));\n }\n\n &:active,\n &.selected,\n &.zeroclipboard-is-active {\n background-color: darken($bg, 5%);\n background-image: none;\n box-shadow: inset 0 2px 4px rgba(0, 0, 0, 0.15);\n }\n\n &.selected:hover {\n background-color: darken($bg, 10%);\n }\n}\n","// Search input and autocomplete\n\n.search {\n position: relative;\n z-index: 2;\n flex-grow: 1;\n height: $sp-10;\n padding: $sp-2;\n transition: padding linear #{$transition-duration * 0.5};\n\n @include mq(md) {\n position: relative !important;\n width: auto !important;\n height: 100% !important;\n padding: 0;\n transition: none;\n }\n}\n\n.search-input-wrap {\n position: relative;\n z-index: 1;\n height: $sp-8;\n overflow: hidden;\n border-radius: $border-radius;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n transition: height linear #{$transition-duration * 0.5};\n\n @include mq(md) {\n position: absolute;\n width: 100%;\n max-width: $search-results-width;\n height: 100% !important;\n border-radius: 0;\n box-shadow: none;\n transition: width ease $transition-duration;\n }\n}\n\n.search-input {\n position: absolute;\n width: 100%;\n height: 100%;\n padding: $sp-2 $gutter-spacing-sm $sp-2 #{$gutter-spacing-sm + $sp-5};\n font-size: 1rem;\n color: $body-text-color;\n background-color: $search-background-color;\n border-top: 0;\n border-right: 0;\n border-bottom: 0;\n border-left: 0;\n border-radius: 0;\n\n @include mq(md) {\n padding: $sp-2 $gutter-spacing-sm $sp-2 #{$gutter-spacing + $sp-5};\n font-size: 0.875rem;\n background-color: $body-background-color;\n transition: padding-left linear #{$transition-duration * 0.5};\n }\n\n &:focus {\n outline: 2px solid $link-color;\n outline-offset: -2px;\n\n + .search-label .search-icon {\n color: $link-color;\n }\n }\n}\n\n.search-label {\n position: absolute;\n display: flex;\n height: 100%;\n padding-left: $gutter-spacing-sm;\n\n @include mq(md) {\n padding-left: $gutter-spacing;\n transition: padding-left linear #{$transition-duration * 0.5};\n }\n\n .search-icon {\n width: #{$sp-4 * 1.2};\n height: #{$sp-4 * 1.2};\n align-self: center;\n color: $grey-dk-000;\n }\n}\n\n.search-results {\n position: absolute;\n left: 0;\n display: none;\n width: 100%;\n max-height: calc(100% - #{$sp-10});\n overflow-y: auto;\n background-color: $search-background-color;\n border-bottom-right-radius: $border-radius;\n border-bottom-left-radius: $border-radius;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n\n @include mq(md) {\n top: 100%;\n width: $search-results-width;\n max-height: calc(100vh - 200%) !important;\n }\n}\n\n.search-results-list {\n padding-left: 0;\n margin-bottom: $sp-1;\n list-style: none;\n @include fs-4;\n\n @include mq(md) {\n @include fs-3;\n }\n}\n\n.search-results-list-item {\n padding: 0;\n margin: 0;\n}\n\n.search-result {\n display: block;\n padding: $sp-1 $sp-3;\n\n &:hover,\n &.active {\n background-color: $feedback-color;\n }\n}\n\n.search-result-title {\n display: block;\n padding-top: $sp-2;\n padding-bottom: $sp-2;\n\n @include mq(sm) {\n display: inline-block;\n width: 40%;\n padding-right: $sp-2;\n vertical-align: top;\n }\n}\n\n.search-result-doc {\n display: flex;\n align-items: center;\n word-wrap: break-word;\n\n &.search-result-doc-parent {\n opacity: 0.5;\n @include fs-3;\n\n @include mq(md) {\n @include fs-2;\n }\n }\n\n .search-result-icon {\n width: $sp-4;\n height: $sp-4;\n margin-right: $sp-2;\n color: $link-color;\n flex-shrink: 0;\n }\n\n .search-result-doc-title {\n overflow: auto;\n }\n}\n\n.search-result-section {\n margin-left: #{$sp-4 + $sp-2};\n word-wrap: break-word;\n}\n\n.search-result-rel-url {\n display: block;\n margin-left: #{$sp-4 + $sp-2};\n overflow: hidden;\n color: $search-result-preview-color;\n text-overflow: ellipsis;\n white-space: nowrap;\n @include fs-1;\n}\n\n.search-result-previews {\n display: block;\n padding-top: $sp-2;\n padding-bottom: $sp-2;\n padding-left: $sp-4;\n margin-left: $sp-2;\n color: $search-result-preview-color;\n word-wrap: break-word;\n border-left: $border;\n border-left-color: $border-color;\n @include fs-2;\n\n @include mq(sm) {\n display: inline-block;\n width: 60%;\n padding-left: $sp-2;\n margin-left: 0;\n vertical-align: top;\n }\n}\n\n.search-result-preview + .search-result-preview {\n margin-top: $sp-1;\n}\n\n.search-result-highlight {\n font-weight: bold;\n}\n\n.search-no-result {\n padding: $sp-2 $sp-3;\n @include fs-3;\n}\n\n.search-button {\n position: fixed;\n right: $sp-4;\n bottom: $sp-4;\n display: flex;\n width: $sp-9;\n height: $sp-9;\n background-color: $search-background-color;\n border: 1px solid rgba($link-color, 0.3);\n border-radius: #{$sp-9 * 0.5};\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n align-items: center;\n justify-content: center;\n}\n\n.search-overlay {\n position: fixed;\n top: 0;\n left: 0;\n z-index: 1;\n width: 0;\n height: 0;\n background-color: rgba(0, 0, 0, 0.3);\n opacity: 0;\n transition:\n opacity ease $transition-duration,\n width 0s $transition-duration,\n height 0s $transition-duration;\n}\n\n.search-active {\n .search {\n position: fixed;\n top: 0;\n left: 0;\n width: 100%;\n height: 100%;\n padding: 0;\n }\n\n .search-input-wrap {\n height: $sp-10;\n border-radius: 0;\n\n @include mq(md) {\n width: $search-results-width;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n }\n }\n\n .search-input {\n background-color: $search-background-color;\n\n @include mq(md) {\n padding-left: 2.3rem;\n }\n }\n\n .search-label {\n @include mq(md) {\n padding-left: 0.6rem;\n }\n }\n\n .search-results {\n display: block;\n }\n\n .search-overlay {\n width: 100%;\n height: 100%;\n opacity: 1;\n transition:\n opacity ease $transition-duration,\n width 0s,\n height 0s;\n }\n\n @include mq(md) {\n .main {\n position: fixed;\n right: 0;\n left: 0;\n }\n }\n\n .main-header {\n padding-top: $sp-10;\n\n @include mq(md) {\n padding-top: 0;\n }\n }\n}\n","// Tables\n// stylelint-disable max-nesting-depth, selector-no-type, selector-max-type\n\n.table-wrapper {\n display: block;\n width: 100%;\n max-width: 100%;\n margin-bottom: $sp-5;\n overflow-x: auto;\n border-radius: $border-radius;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n}\n\ntable {\n display: table;\n min-width: 100%;\n border-collapse: separate;\n}\n\nth,\ntd {\n min-width: 7.5rem;\n padding: $sp-2 $sp-3;\n background-color: $table-background-color;\n border-bottom: $border rgba($border-color, 0.5);\n border-left: $border $border-color;\n\n @include fs-3;\n\n &:first-of-type {\n border-left: 0;\n }\n}\n\ntbody {\n tr {\n &:last-of-type {\n th,\n td {\n border-bottom: 0;\n }\n\n td {\n padding-bottom: $sp-3;\n }\n }\n }\n}\n\nthead {\n th {\n border-bottom: $border $border-color;\n }\n}\n","// Code and syntax highlighting\n// stylelint-disable selector-no-qualifying-type, declaration-block-semicolon-newline-after,declaration-block-single-line-max-declarations, selector-no-type, selector-max-type, scss/comment-no-empty\n\n// {% raw %}\n\n// This instruction applies to all queues not within 'pre' or 'figure', avoiding 'code' generated by the highlight.\n:not(pre, figure) {\n & > code {\n padding: 0.2em 0.15em;\n font-weight: 400;\n background-color: $code-background-color;\n border: $border $border-color;\n border-radius: $border-radius;\n }\n}\n\n// Avoid appearance of dark border around visited code links in Safari\na:visited code {\n border-color: $border-color;\n}\n\n// Content structure for highlighted code blocks using fences or Liquid\n//\n// ```[LANG]...```, no kramdown line_numbers:\n// div.[language-LANG.]highlighter-rouge > div.highlight > pre.highlight > code\n//\n// ```[LANG]...```, kramdown line_numbers = true:\n// div.[language-LANG.]highlighter-rouge > div.highlight > pre.highlight > code\n// > div.table-wrapper > table.rouge-table > tbody > tr\n// > td.rouge-gutter.gl > pre.lineno\n// | td.rouge-code > pre\n//\n// {% highlight LANG %}...{% endhighlight %}:\n// figure.highlight > pre > code.language-LANG\n//\n// {% highlight LANG linenos %}...{% endhighlight %}:\n// figure.highlight > pre > code.language-LANG\n// > div.table-wrapper > table.rouge-table > tbody > tr\n// > td.gutter.gl > pre.lineno\n// | td.code > pre\n//\n// ----...---- (AsciiDoc)\n// div.listingblock > div.content > pre.rouge.highlight\n//\n// fix_linenos removes the outermost pre when it encloses table.rouge-table\n//\n// See docs/index-test.md for some tests.\n//\n// No kramdown line_numbers: fences and Liquid highlighting look the same.\n// Kramdown line_numbers = true: fences have a wider gutter than with Liquid?\n\n// ```[LANG]...```\n// or in AsciiDoc:\n//\n// ----\n// ...\n// ----\n\n// the code may appear with 3 different types:\n// container \\ case: default case, code with line number, code with html rendering\n// top level: div.highlighter-rouge, figure.highlight, figure.highlight\n// second level: div.highlight, div.table-wrapper, pre.highlight\n// third level: pre.highlight, td.code, absent\n// last level: code, pre, code (optionality)\n// highlighter level: span, span, span\n// the spacing are only in the second level for case 1, 3 and in the third level for case 2\n// in AsciiDoc, there is a parent container that contains optionally a title and the content.\n\n// select top level container\ndiv.highlighter-rouge,\ndiv.listingblock > div.content,\nfigure.highlight {\n margin-top: 0;\n margin-bottom: $sp-3;\n background-color: $code-background-color;\n border-radius: $border-radius;\n box-shadow: none;\n -webkit-overflow-scrolling: touch;\n position: relative;\n padding: 0;\n\n // copy button (or other button)\n // the button appear only when there is a hover on the code or focus on button\n > button {\n width: $sp-3;\n opacity: 0;\n position: absolute;\n top: 0;\n right: 0;\n padding: $sp-3;\n border: none;\n background: none;\n color: $body-text-color;\n box-sizing: content-box;\n\n svg {\n fill: $body-text-color;\n }\n\n &:active {\n text-decoration: none;\n outline: none;\n opacity: 1;\n }\n\n &:focus {\n opacity: 1;\n outline: 2px solid $link-color;\n }\n }\n\n // the button can be seen by doing a simple hover in the code, there is no need to go over the location of the button\n &:hover {\n > button {\n cursor: copy;\n opacity: 1;\n }\n }\n}\n\n// setting the spacing and scrollbar on the second level for the first case\n// remove all space on the second and third level\n// this is a mixin to accommodate for the slightly different structures generated via Markdown vs AsciiDoc\n@mixin scroll-and-spacing($code-div, $pre-select) {\n #{$code-div} {\n overflow-x: auto;\n padding: $sp-3;\n margin: 0;\n border: 1px solid $body-text-color;\n border-radius: $border-radius;\n }\n\n #{$pre-select},\n code {\n padding: 0;\n margin: 0;\n border: 0;\n }\n}\n\n// for Markdown\ndiv.highlighter-rouge {\n @include scroll-and-spacing(\"div.highlight\", \"pre.highlight\");\n}\n\n// for AsciiDoc. we also need to fix the margins for its parent container.\ndiv.listingblock {\n margin-top: 0;\n margin-bottom: $sp-3;\n\n @include scroll-and-spacing(\"div.content\", \"div.content > pre\");\n}\n\n// {% highlight LANG %}...{% endhighlight %},\n// {% highlight LANG linenos %}...{% endhighlight %}:\n\n// setting the spacing and scrollbar on the second level for the thirt case\n// the css rule are apply only to the last code enviroment\n// setting the scroolbar\nfigure.highlight {\n pre,\n :not(pre) > code {\n overflow-x: auto;\n padding: $sp-3;\n margin: 0;\n border: 1px solid $body-text-color;\n border-radius: $border-radius;\n }\n}\n\n// ```[LANG]...```, kramdown line_numbers = true,\n// {% highlight LANG linenos %}...{% endhighlight %}:\n\n// setting the spacing and scrollbar on the thirt level for the second case\n.highlight .table-wrapper {\n padding: $sp-3 0;\n margin: 0;\n border: 0;\n box-shadow: none;\n\n td,\n pre {\n min-width: 0;\n padding: 0;\n background-color: $code-background-color;\n border: 0;\n\n @include fs-2;\n }\n\n td.gl {\n width: 1em;\n padding-right: $sp-3;\n padding-left: $sp-3;\n }\n\n pre {\n margin: 0;\n line-height: 2;\n }\n}\n\n// Code examples: html render of a code\n.code-example,\n.listingblock > .title {\n padding: $sp-3;\n margin-bottom: $sp-3;\n overflow: auto;\n border: 1px solid $border-color;\n border-radius: $border-radius;\n\n + .highlighter-rouge,\n + .sectionbody .listingblock,\n + .content,\n + figure.highlight {\n position: relative;\n margin-top: -$sp-4;\n border-right: 1px solid $border-color;\n border-bottom: 1px solid $border-color;\n border-left: 1px solid $border-color;\n border-top-left-radius: 0;\n border-top-right-radius: 0;\n }\n}\n\n// Mermaid diagram code blocks should be left unstyled.\ncode.language-mermaid {\n padding: 0;\n background-color: inherit;\n border: 0;\n}\n\n// Override OneDarkJekyll Colors for Code Blocks\n.highlight,\npre.highlight {\n background: $code-background-color; // Code Background\n // For Backwards Compatibility Before $code-linenumber-color was added\n @if variable-exists(code-linenumber-color) {\n color: $code-linenumber-color; // Code Line Numbers\n } @else {\n color: $body-text-color; // Code Line Numbers\n }\n}\n\n// Override OneDarkJekyll Colors for Code Blocks\n.highlight pre {\n background: $code-background-color; // Code Background\n}\n\n// {% endraw %}\n","// Utility classes for colors\n\n// Text colors\n\n.text-grey-dk-000 {\n color: $grey-dk-000 !important;\n}\n\n.text-grey-dk-100 {\n color: $grey-dk-100 !important;\n}\n\n.text-grey-dk-200 {\n color: $grey-dk-200 !important;\n}\n\n.text-grey-dk-250 {\n color: $grey-dk-250 !important;\n}\n\n.text-grey-dk-300 {\n color: $grey-dk-300 !important;\n}\n\n.text-grey-lt-000 {\n color: $grey-lt-000 !important;\n}\n\n.text-grey-lt-100 {\n color: $grey-lt-100 !important;\n}\n\n.text-grey-lt-200 {\n color: $grey-lt-200 !important;\n}\n\n.text-grey-lt-300 {\n color: $grey-lt-300 !important;\n}\n\n.text-blue-000 {\n color: $blue-000 !important;\n}\n\n.text-blue-100 {\n color: $blue-100 !important;\n}\n\n.text-blue-200 {\n color: $blue-200 !important;\n}\n\n.text-blue-300 {\n color: $blue-300 !important;\n}\n\n.text-green-000 {\n color: $green-000 !important;\n}\n\n.text-green-100 {\n color: $green-100 !important;\n}\n\n.text-green-200 {\n color: $green-200 !important;\n}\n\n.text-green-300 {\n color: $green-300 !important;\n}\n\n.text-purple-000 {\n color: $purple-000 !important;\n}\n\n.text-purple-100 {\n color: $purple-100 !important;\n}\n\n.text-purple-200 {\n color: $purple-200 !important;\n}\n\n.text-purple-300 {\n color: $purple-300 !important;\n}\n\n.text-yellow-000 {\n color: $yellow-000 !important;\n}\n\n.text-yellow-100 {\n color: $yellow-100 !important;\n}\n\n.text-yellow-200 {\n color: $yellow-200 !important;\n}\n\n.text-yellow-300 {\n color: $yellow-300 !important;\n}\n\n.text-red-000 {\n color: $red-000 !important;\n}\n\n.text-red-100 {\n color: $red-100 !important;\n}\n\n.text-red-200 {\n color: $red-200 !important;\n}\n\n.text-red-300 {\n color: $red-300 !important;\n}\n\n// Background colors\n\n.bg-grey-dk-000 {\n background-color: $grey-dk-000 !important;\n}\n\n.bg-grey-dk-100 {\n background-color: $grey-dk-100 !important;\n}\n\n.bg-grey-dk-200 {\n background-color: $grey-dk-200 !important;\n}\n\n.bg-grey-dk-250 {\n background-color: $grey-dk-250 !important;\n}\n\n.bg-grey-dk-300 {\n background-color: $grey-dk-300 !important;\n}\n\n.bg-grey-lt-000 {\n background-color: $grey-lt-000 !important;\n}\n\n.bg-grey-lt-100 {\n background-color: $grey-lt-100 !important;\n}\n\n.bg-grey-lt-200 {\n background-color: $grey-lt-200 !important;\n}\n\n.bg-grey-lt-300 {\n background-color: $grey-lt-300 !important;\n}\n\n.bg-blue-000 {\n background-color: $blue-000 !important;\n}\n\n.bg-blue-100 {\n background-color: $blue-100 !important;\n}\n\n.bg-blue-200 {\n background-color: $blue-200 !important;\n}\n\n.bg-blue-300 {\n background-color: $blue-300 !important;\n}\n\n.bg-green-000 {\n background-color: $green-000 !important;\n}\n\n.bg-green-100 {\n background-color: $green-100 !important;\n}\n\n.bg-green-200 {\n background-color: $green-200 !important;\n}\n\n.bg-green-300 {\n background-color: $green-300 !important;\n}\n\n.bg-purple-000 {\n background-color: $purple-000 !important;\n}\n\n.bg-purple-100 {\n background-color: $purple-100 !important;\n}\n\n.bg-purple-200 {\n background-color: $purple-200 !important;\n}\n\n.bg-purple-300 {\n background-color: $purple-300 !important;\n}\n\n.bg-yellow-000 {\n background-color: $yellow-000 !important;\n}\n\n.bg-yellow-100 {\n background-color: $yellow-100 !important;\n}\n\n.bg-yellow-200 {\n background-color: $yellow-200 !important;\n}\n\n.bg-yellow-300 {\n background-color: $yellow-300 !important;\n}\n\n.bg-red-000 {\n background-color: $red-000 !important;\n}\n\n.bg-red-100 {\n background-color: $red-100 !important;\n}\n\n.bg-red-200 {\n background-color: $red-200 !important;\n}\n\n.bg-red-300 {\n background-color: $red-300 !important;\n}\n","// Utility classes for layout\n\n// Display\n\n.d-block {\n display: block !important;\n}\n\n.d-flex {\n display: flex !important;\n}\n\n.d-inline {\n display: inline !important;\n}\n\n.d-inline-block {\n display: inline-block !important;\n}\n\n.d-none {\n display: none !important;\n}\n\n// Screenreader-only\n\n.sr-only {\n position: absolute;\n width: 1px;\n height: 1px;\n padding: 0;\n margin: -1px;\n overflow: hidden;\n clip: rect(0, 0, 0, 0);\n white-space: nowrap;\n border-width: 0;\n}\n\n@each $media-query in map-keys($media-queries) {\n @for $i from 1 through length($spacers) {\n @include mq($media-query) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .d-sm-block, .d-md-none, .d-lg-inline\n .d-#{$media-query}-block {\n display: block !important;\n }\n .d-#{$media-query}-flex {\n display: flex !important;\n }\n .d-#{$media-query}-inline {\n display: inline !important;\n }\n .d-#{$media-query}-inline-block {\n display: inline-block !important;\n }\n .d-#{$media-query}-none {\n display: none !important;\n }\n }\n }\n}\n\n// Horizontal alignment\n\n.float-left {\n float: left !important;\n}\n\n.float-right {\n float: right !important;\n}\n\n.flex-justify-start {\n justify-content: flex-start !important;\n}\n\n.flex-justify-end {\n justify-content: flex-end !important;\n}\n\n.flex-justify-between {\n justify-content: space-between !important;\n}\n\n.flex-justify-around {\n justify-content: space-around !important;\n}\n\n// Vertical alignment\n\n.v-align-baseline {\n vertical-align: baseline !important;\n}\n\n.v-align-bottom {\n vertical-align: bottom !important;\n}\n\n.v-align-middle {\n vertical-align: middle !important;\n}\n\n.v-align-text-bottom {\n vertical-align: text-bottom !important;\n}\n\n.v-align-text-top {\n vertical-align: text-top !important;\n}\n\n.v-align-top {\n vertical-align: top !important;\n}\n","// Utility classes for typography\n\n.fs-1 {\n @include fs-1;\n}\n\n.fs-2 {\n @include fs-2;\n}\n\n.fs-3 {\n @include fs-3;\n}\n\n.fs-4 {\n @include fs-4;\n}\n\n.fs-5 {\n @include fs-5;\n}\n\n.fs-6 {\n @include fs-6;\n}\n\n.fs-7 {\n @include fs-7;\n}\n\n.fs-8 {\n @include fs-8;\n}\n\n.fs-9 {\n @include fs-9;\n}\n\n.fs-10 {\n @include fs-10;\n}\n\n.fw-300 {\n font-weight: 300 !important;\n}\n\n.fw-400 {\n font-weight: 400 !important;\n}\n\n.fw-500 {\n font-weight: 500 !important;\n}\n\n.fw-700 {\n font-weight: 700 !important;\n}\n\n.lh-0 {\n line-height: 0 !important;\n}\n\n.lh-default {\n line-height: $body-line-height;\n}\n\n.lh-tight {\n line-height: $body-heading-line-height;\n}\n\n.ls-5 {\n letter-spacing: 0.05em !important;\n}\n\n.ls-10 {\n letter-spacing: 0.1em !important;\n}\n\n.ls-0 {\n letter-spacing: 0 !important;\n}\n\n.text-uppercase {\n text-transform: uppercase !important;\n}\n","// Utility classes for lists\n\n// stylelint-disable selector-max-type\n\n.list-style-none {\n padding: 0 !important;\n margin: 0 !important;\n list-style: none !important;\n\n li {\n &::before {\n display: none !important;\n }\n }\n}\n","// Utility classes for margins and padding\n\n// stylelint-disable block-opening-brace-space-after, block-opening-brace-space-before\n\n// Margin spacer utilities\n\n.mx-auto {\n margin-right: auto !important;\n margin-left: auto !important;\n}\n\n@for $i from 1 through length($spacers) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .m-0, .m-1, .m-2...\n .m-#{$scale} {\n margin: #{$size} !important;\n }\n .mt-#{$scale} {\n margin-top: #{$size} !important;\n }\n .mr-#{$scale} {\n margin-right: #{$size} !important;\n }\n .mb-#{$scale} {\n margin-bottom: #{$size} !important;\n }\n .ml-#{$scale} {\n margin-left: #{$size} !important;\n }\n\n .mx-#{$scale} {\n margin-right: #{$size} !important;\n margin-left: #{$size} !important;\n }\n\n .my-#{$scale} {\n margin-top: #{$size} !important;\n margin-bottom: #{$size} !important;\n }\n\n .mxn-#{$scale} {\n margin-right: -#{$size} !important;\n margin-left: -#{$size} !important;\n }\n .mx-#{$scale}-auto {\n margin-right: auto !important;\n margin-left: auto !important;\n }\n}\n\n@each $media-query in map-keys($media-queries) {\n @for $i from 1 through length($spacers) {\n @include mq($media-query) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .m-sm-0, .m-md-1, .m-lg-2...\n .m-#{$media-query}-#{$scale} {\n margin: #{$size} !important;\n }\n .mt-#{$media-query}-#{$scale} {\n margin-top: #{$size} !important;\n }\n .mr-#{$media-query}-#{$scale} {\n margin-right: #{$size} !important;\n }\n .mb-#{$media-query}-#{$scale} {\n margin-bottom: #{$size} !important;\n }\n .ml-#{$media-query}-#{$scale} {\n margin-left: #{$size} !important;\n }\n\n .mx-#{$media-query}-#{$scale} {\n margin-right: #{$size} !important;\n margin-left: #{$size} !important;\n }\n\n .my-#{$media-query}-#{$scale} {\n margin-top: #{$size} !important;\n margin-bottom: #{$size} !important;\n }\n\n .mxn-#{$media-query}-#{$scale} {\n margin-right: -#{$size} !important;\n margin-left: -#{$size} !important;\n }\n }\n }\n}\n\n// Padding spacer utilities\n\n@for $i from 1 through length($spacers) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .p-0, .p-1, .p-2...\n .p-#{$scale} {\n padding: #{$size} !important;\n }\n .pt-#{$scale} {\n padding-top: #{$size} !important;\n }\n .pr-#{$scale} {\n padding-right: #{$size} !important;\n }\n .pb-#{$scale} {\n padding-bottom: #{$size} !important;\n }\n .pl-#{$scale} {\n padding-left: #{$size} !important;\n }\n\n .px-#{$scale} {\n padding-right: #{$size} !important;\n padding-left: #{$size} !important;\n }\n\n .py-#{$scale} {\n padding-top: #{$size} !important;\n padding-bottom: #{$size} !important;\n }\n}\n\n@each $media-query in map-keys($media-queries) {\n @include mq($media-query) {\n @for $i from 1 through length($spacers) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .p-sm-0, .p-md-1, .p-lg-2...\n .p-#{$media-query}-#{$scale} {\n padding: #{$size} !important;\n }\n .pt-#{$media-query}-#{$scale} {\n padding-top: #{$size} !important;\n }\n .pr-#{$media-query}-#{$scale} {\n padding-right: #{$size} !important;\n }\n .pb-#{$media-query}-#{$scale} {\n padding-bottom: #{$size} !important;\n }\n .pl-#{$media-query}-#{$scale} {\n padding-left: #{$size} !important;\n }\n\n .px-#{$media-query}-#{$scale} {\n padding-right: #{$size} !important;\n padding-left: #{$size} !important;\n }\n\n .py-#{$media-query}-#{$scale} {\n padding-top: #{$size} !important;\n padding-bottom: #{$size} !important;\n }\n }\n }\n}\n","// stylelint-disable selector-max-specificity, selector-max-id, selector-max-type, selector-no-qualifying-type\n\n@media print {\n .site-footer,\n .site-button,\n #edit-this-page,\n #back-to-top,\n .site-nav,\n .main-header {\n display: none !important;\n }\n\n hr {\n margin-top: 1rem;\n margin-bottom: 1rem;\n }\n\n .side-bar {\n width: 100%;\n height: auto;\n border-right: 0 !important;\n }\n\n .site-header {\n border-bottom: 1px solid $border-color;\n }\n\n .site-title {\n font-size: 1rem !important;\n font-weight: 700 !important;\n }\n\n .text-small {\n font-size: 8pt !important;\n }\n\n pre.highlight {\n border: 1px solid $border-color;\n }\n\n .main {\n max-width: none;\n margin-left: 0;\n }\n}\n","// Skipnav\n// Skip to main content\n\na.skip-to-main {\n left: -999px;\n position: absolute;\n top: auto;\n width: 1px;\n height: 1px;\n overflow: hidden;\n z-index: -999;\n}\n\na.skip-to-main:focus,\na.skip-to-main:active {\n color: $link-color;\n background-color: $body-background-color;\n left: auto;\n top: auto;\n width: 30%;\n height: auto;\n overflow: auto;\n margin: 10px 35%;\n padding: 5px;\n border-radius: 15px;\n border: 4px solid $btn-primary-color;\n text-align: center;\n font-size: 1.2em;\n z-index: 999;\n}\n","\n\n@import \"./support/support\";\n@import \"./custom/setup\";\n@import \"./color_schemes/light\";\n\n@import \"./color_schemes/meshtastic\";\n\n@import \"./modules\";\ndiv.opaque {\n background-color: $body-background-color;\n}\n\np.tip, blockquote.tip {\n border: 1px $green-000 solid;\n border-left: $border-radius solid $green-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n \n &::before {\n color: $green-300;\n content: \"Tip\";\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n \n > .tip-title {\n color: $green-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\np.tip-title, blockquote.tip-title {\n border: 1px $green-000 solid;\n border-left: $border-radius solid $green-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n > p:first-child {\n margin-top: 0;\n margin-bottom: 0;\n color: $green-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\nblockquote.tip {\n margin-left: 0;\n margin-right: 0;\n\n > p:first-child {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\nblockquote.tip-title {\n margin-left: 0;\n margin-right: 0;\n\n > p:nth-child(2) {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\n\n\np.note, blockquote.note {\n border: 1px $blue-000 solid;\n border-left: $border-radius solid $blue-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n \n &::before {\n color: $blue-300;\n content: \"Note\";\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n \n > .note-title {\n color: $blue-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\np.note-title, blockquote.note-title {\n border: 1px $blue-000 solid;\n border-left: $border-radius solid $blue-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n > p:first-child {\n margin-top: 0;\n margin-bottom: 0;\n color: $blue-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\nblockquote.note {\n margin-left: 0;\n margin-right: 0;\n\n > p:first-child {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\nblockquote.note-title {\n margin-left: 0;\n margin-right: 0;\n\n > p:nth-child(2) {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\n\n\np.warning, blockquote.warning {\n border: 1px $yellow-000 solid;\n border-left: $border-radius solid $yellow-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n \n &::before {\n color: $yellow-300;\n content: \"Warning\";\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n \n > .warning-title {\n color: $yellow-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\np.warning-title, blockquote.warning-title {\n border: 1px $yellow-000 solid;\n border-left: $border-radius solid $yellow-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n > p:first-child {\n margin-top: 0;\n margin-bottom: 0;\n color: $yellow-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\nblockquote.warning {\n margin-left: 0;\n margin-right: 0;\n\n > p:first-child {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\nblockquote.warning-title {\n margin-left: 0;\n margin-right: 0;\n\n > p:nth-child(2) {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\n\n@import \"./custom/custom\";\n\n\n"],"file":"just-the-docs-default.css"} \ No newline at end of file diff --git a/main/assets/css/just-the-docs-light.css.map b/main/assets/css/just-the-docs-light.css.map index 935503c44b..dc29f2b616 100644 --- a/main/assets/css/just-the-docs-light.css.map +++ b/main/assets/css/just-the-docs-light.css.map @@ -1 +1 @@ -{"version":3,"sourceRoot":"","sources":["../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/vendor/accessible-pygments/github-light.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/vendor/normalize.scss/normalize.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/base.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/color_schemes/light.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/support/mixins/_typography.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/support/mixins/_layout.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/support/_variables.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/layout.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/content.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/navigation.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/typography.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/labels.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/buttons.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/support/mixins/_buttons.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/search.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/tables.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/code.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/utilities/_colors.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/utilities/_layout.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/utilities/_typography.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/utilities/_lists.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/utilities/_spacing.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/print.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/skiptomain.scss","just-the-docs-light.scss"],"names":[],"mappings":";AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAUA;EAAkB;;;AAClB;EAAgB;EAAiB;AACjC;EAAkB;EAAiB;AACnC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAkB;EAAiB;AACnC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAqB;AACtC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAoB;AACrC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAgB;EAAiB;AACjC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AChFlC;AAEA;AAAA;AAGA;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAAA;AAKA;EACE;EACA;EACA;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;EACA;;;AAGF;AAAA;AAAA;AAIA;AAAA;EAEE;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;AAAA;EAGE;EACA;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;EAEE;EACA;EACA;EACA;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAAA;AAKA;AAAA;AAAA;AAAA;AAAA;EAKE;EACA;EACA;EACA;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;AAEE;EACA;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;AAEE;EACA;;;AAGF;AAAA;AAAA;AAIA;AAAA;AAAA;AAAA;EAIE;;;AAGF;AAAA;AAAA;AAIA;AAAA;AAAA;AAAA;EAIE;EACA;;;AAGF;AAAA;AAAA;AAIA;AAAA;AAAA;AAAA;EAIE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAOA;EACE;EACA;EACA;EACA;EACA;EACA;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;EAEE;EACA;;;AAGF;AAAA;AAAA;AAIA;AAAA;EAEE;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AC1VF;EACE,cCJa;;;ADOf;EACE;;;AAGF;EACE;;AEmBA;EACE;;AClBA;EHHJ;IEyBI;;;;AFnBJ;EACE,aIfiB;EJgBjB;EACA,aIbiB;EJcjB,OIUY;EJTZ,kBIOM;EJNN;;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAYE;;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAOE;EACA;EACA;EACA,aI1CyB;EJ2CzB,OIlBY;;;AJqBd;EACE;EACA;;;AAGF;EACE,OItBW;EJuBX;;;AAGF;EACE;EACA,uBI/BY;EJgCZ;;AAEA;EACE;;;AAIJ;EACE,aIvEiB;EJwEjB;EACA,aIvEiB;;;AJ0EnB;AAAA;EAEE;;;AAGF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;EACA;EACA,kBI/DY;EJgEZ;;;AAIF;EACE;EAGA;EACA;EACA;EACA;;;AK7GF;EACE;EACA;EACA;EACA,kBD6BY;;ADrBV;EEZJ;IAOI;IACA;IACA,ODwFW;ICvFX;IACA;IACA;;;AFAA;EEZJ;IAgBI;IACA,WD+EQ;;;ADpFR;EEQF;IAEI,aD2ES;;;ADrFX;EEQF;IAQI;;;AAOF;EACE;EACA,kBDJQ;;ADrBV;EEuBA;IAKI;IACA,kBDdA;;;ACiBF;EACE;;AFjCJ;EEgCE;IAII;;;;AAOV;EACE;;AF5CE;EE2CJ;IAII;IACA,WDyCY;;;;ACrChB;EACE,aDaK;ECZL,gBDYK;EDvDL,eCuDK;EDtDL,cCsDK;;ADlEH;EEoDJ;IFrCI,eCqDG;IDpDH,cCoDG;;;ADpEH;EEoDJ;IAOI,aDSG;ICRH,gBDQG;;;;ACJP;EACE;EACA;;AFlEE;EEgEJ;IAKI;IACA;IACA,QDmBY;;;;ACfhB;AAAA;AAAA;EAGE;;AF9EE;EE2EJ;AAAA;AAAA;IAMI,ODGQ;;;;ACCZ;EACE;;AAEA;EACE;;AFzFA;EEqFJ;IAQI;IACA,aDxBG;ICyBH,gBD7BG;IC8BH;IACA;;;;AAIJ;EACE;EACA,YDbc;ECcd;;AFxGE;EEqGJ;IAMI,QDjBY;ICkBZ,YDlBY;ICmBZ;;;;AAIJ;EACE;EACA;EACA;EACA;EACA,aDrDK;ECsDL,gBDtDK;ECuDL,ODpGY;EDTZ,eCuDK;EDtDL,cCsDK;;ADlEH;EEiHJ;IFlGI,eCqDG;IDpDH,cCoDG;;;AF/BL;EACE;;ACtCA;EEiHJ;IHvEI;IACA,aEhDuB;;;ADKvB;EEiHJ;IAcI,aD/DG;ICgEH,gBDhEG;;;;AC+EP;EACE;EACA;EACA,SDhFK;ECiFL;;;AFnJE;EEuJF;IACE;;;AAIJ;EACE;;;AAQF;EACE;;;AAOF;EACE;EACA;EACA;EACA,aD/GK;ECgHL,gBDhHK;EDvDL,eCuDK;EDtDL,cCsDK;;ADlEH;EE6KJ;IF9JI,eCqDG;IDpDH,cCoDG;;;AFvEL;EACE;;ACEA;EE6KJ;IH3KI;;;ACFA;EE6KJ;IAYI;IACA;;;;AAIJ;EACE,OD5HK;EC6HL,QD7HK;EC8HL,ODxKW;;;AElCb;EACE,aFEoB;;AEApB;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAOE;;AAGF;EACE;EACA;;AAGF;AAAA;EAEE;;AAIA;EACE,YF+CC;;AE3CL;EACE;EACA;;AAEA;EACE;;AAEA;EACE;EACA;EACA;EACA,OFfM;EEgBN;EACA;;AJ1BN;EACE;;ACRA;EG2BE;IJfF;;;ACZA;EG2BE;IAUI;;;AAIJ;EACE;;AAGE;EACE;EACA;;AAOV;EACE;;AAGE;EACE;EACA;EACA,OF7CM;EE8CN;;AAMJ;EACE;;AAIJ;EACE;EACA;;AAKF;EACE;;AAGF;EACE;;AAGF;EACE;EACA;;AAGF;AAAA;EAEE;;AAGF;EACE;EACA;EACA;;AAEA;EACE;;AAIJ;EACE;EACA;EACA;;AAmBE;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EACE;;AASF;AAAA;AAAA;AAAA;AAAA;AAAA;EAEE;;AAKN;EACE;EACA;EACA,OFnFG;EEoFH;EACA,eFzFG;EE0FH,cF1FG;EE2FH;;AH1JA;EGmJF;IAUI;IACA;;;AAGF;EACE;EACA;EACA;EACA,OF5IO;EE6IP;;AAYF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EACE;;AAIJ;EACE;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAOE;EACA;EACA;;AAEA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAKE;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EACE;;AAIJ;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAWE,YF9JG;;;AG3EP;EACE;EACA;EACA;EACA;;AAEA;EACE;EACA;;ALoBF;EACE;;AClBA;EILF;IL2BE;;;ACtBA;EDOF;IACE;;;ACRA;EILF;ILiBE;;;AKPA;EACE;EACA,YH+DC;EG9DD,aHuDC;EGtDD,gBHsDC;EGrDD;EAEE,eH0DD;EGzDC,cHqDD;;ADlEH;EIKA;IAeI,YHgDD;IG/CC;IAEE,eH6CH;IG5CG,cH4CH;;;AGrCD;EACE,OHkCD;EGjCC,QHiCD;EGhCC;;AAGF;EACE;EACA;;AAGF;EAEE;EACA;;AASJ;EACE;EAEE;EAGF,OHUC;EGTD,QHSC;EGRD;EACA,OHtCO;;ADzBT;EIsDA;IAYI,OHED;IGDC,QHCD;IGAC;;;AAGF;EACE;;AAQA;EACE;;AAKN;EACE;EACA,cHvBC;EGwBD;;AAEA;EACE;;AAEA;EACE,OH9EI;;AGiFN;EACE,OHlFI;;AGwFR;EAEI;;AAMJ;EACE;;;AAMR;EACE;EACA;EACA;EACA;EACA;;ALhIA;EACE;;ACEA;EIwHJ;ILtHI;;;ACFA;EIwHJ;IASI;IACA,YHhEG;IGiEH;;EAEA;IACE;;;;AAMJ;EACE;;AAEA;EACE;;AAGE;EACE,OH3HG;;AG8HL;EACE,OH/HG;;;AGwIb;EACE;EACA;;ALtKA;EACE;;ACEA;EIiKJ;IL/JI;;;AKoKF;EACE;EACA;EACA;EACA;EACA;;AAGF;EACE;EACA;EACA;EACA;;AJlLA;EIiKJ;IAqBI,eHpHG;;;;ADlEH;EI4LJ;IAEI;;;;AAIJ;EACE;EACA,eHnIK;EGoIL;;;AAGF;EACE;;AL5MA;EACE;;ACEA;EIwMJ;ILtMI;;;AK0MF;EACE;;AAGF;EACE;EACA,cHlJG;EGmJH,aHnJG;EGoJH,OHpMU;EGqMV;;AAIA;EACE;;;ACrON;AAAA;EAEE;;ANoEA;AAAA;EACE;EACA,aElEuB;;ADKvB;EKXJ;AAAA;IN4EI;;;;AA5BF;AAAA;AAAA;EACE;;ACtCA;EKJJ;AAAA;AAAA;IN8CI;IACA,aEhDuB;;;;AFgCzB;AAAA;EACE;;AC5BA;EKEJ;AAAA;IN8BI;;;;AMzBJ;AAAA;EAEE;EACA;EACA;;ANdA;AAAA;EACE;;ACEA;EKOJ;AAAA;INLI;;;;AMcJ;EACE;;;ANVA;AAAA;EACE;;ACRA;EKoBJ;AAAA;INRI;;;;AAfF;AAAA;EACE;;ACEA;EKyBJ;AAAA;INvBI;;;;AALF;EACE;;ACEA;EK8BJ;IN5BI;;;;AMgCJ;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;ACvDF;AAAA;EAEE;EACA;EACA,cLoEK;EKnEL,aLmEK;EKlEL,OLiBM;EKhBN;EACA;EACA,kBL6BS;EK5BT;;APLA;AAAA;EACE;;ACEA;EMRJ;AAAA;IPUI;;;;AOKJ;EACE,kBL4BU;;;AKzBZ;EACE,kBLcW;;;AKXb;EACE,kBL4BQ;;;AKzBV;EACE,OLFY;EKGZ,kBLkBW;;;AMlDb;EACE;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA,ON2BW;EM1BX;EACA;EACA;EACA,kBTTkB;ESUlB;EACA,eNyEc;EMxEd,YACE;EAEF;;AAEA;EACE;EACA;EACA;;AAGF;EAEE;;AAGF;EAEE;;AAGF;EAIE;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;AAKA;EAEE;EACA;EACA;EACA;EACA;;;AAKN;EACE,ONnCW;EMoCX;EACA;;AAEA;EAIE;EACA;EACA;EACA;;AAGF;EACE;EACA;EACA,YACE;;AAIJ;EAEE;;;AAIJ;ECnGE,OP0BM;EOzBN;EACA;EACA,YACE;;AAGF;EAEE,OPiBI;EOhBJ;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;;ADgFJ;ECvGE,OP0BM;EOzBN;EACA;EACA,YACE;;AAGF;EAEE,OPiBI;EOhBJ;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;;ADoFJ;EC3GE,OP0BM;EOzBN;EACA;EACA,YACE;;AAGF;EAEE,OPiBI;EOhBJ;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;;ADwFJ;EC/GE,OP0BM;EOzBN;EACA;EACA,YACE;;AAGF;EAEE,OPiBI;EOhBJ;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;;AD4FJ;EACE;EACA;EACA;EACA;EACA;EACA;EACA;;;AE3HF;EACE;EACA;EACA;EACA,QRgFM;EQ/EN,SRuEK;EQtEL;;ATME;ESZJ;IASI;IACA;IACA;IACA;IACA;;;;AAIJ;EACE;EACA;EACA,QR8DK;EQ7DL;EACA,eRmEc;EQlEd,YACE;EAEF;;ATdE;ESKJ;IAYI;IACA;IACA,WRwEmB;IQvEnB;IACA;IACA;IACA;;;;AAIJ;EACE;EACA;EACA;EACA;EACA;EACA,ORhBY;EQiBZ,kBRnBM;EQoBN;EACA;EACA;EACA;EACA;;ATvCE;ES2BJ;IAeI;IACA;IACA,kBR7BI;IQ8BJ;;;AAGF;EACE;EACA;;AAEA;EACE,OR5BO;;;AQiCb;EACE;EACA;EACA;EACA,cRIK;;ADlEH;ES0DJ;IAOI,cRGG;IQFH;;;AAGF;EACE;EACA;EACA;EACA,ORzDU;;;AQ6Dd;EACE;EACA;EACA;EACA;EACA;EACA;EACA,kBRrEM;EQsEN,4BRRc;EQSd,2BRTc;EQUd,YACE;;ATxFA;ES6EJ;IAeI;IACA,ORFmB;IQGnB;;;;AAIJ;EACE;EACA,eRrCK;EQsCL;;AVpFA;EACE;;AClBA;ESkGJ;IV5EI;;;ACtBA;EDOF;IACE;;;ACRA;ESkGJ;IVtFI;;;;AUiGJ;EACE;EACA;;;AAGF;EACE;EACA;;AAEA;EAEE,kBX5Ha;;;AWgIjB;EACE;EACA,aR9DK;EQ+DL,gBR/DK;;ADhEH;ES4HJ;IAMI;IACA;IACA,eRpEG;IQqEH;;;;AAIJ;EACE;EACA;EACA;;AAEA;EACE;;AVxIF;EACE;;ACRA;ES8IF;IVlIE;;;ACZA;EDHF;IACE;;;ACEA;ES8IF;IV5IE;;;AUqJF;EACE,ORtFG;EQuFH,QRvFG;EQwFH,cR1FG;EQ2FH,ORlIS;EQmIT;;AAGF;EACE;;;AAIJ;EACE;EACA;;;AAGF;EACE;EACA;EACA;EACA,OR5JY;EQ6JZ;EACA;;AV5LA;EACE;;ACYA;ESyKJ;IVjLI;;;;AU2LJ;EACE;EACA,aRrHK;EQsHL,gBRtHK;EQuHL,cRrHK;EQsHL,aRxHK;EQyHL,ORxKY;EQyKZ;EACA,aR/GO;EQgHP,mBRtKY;;AFzBZ;EACE;;ACEA;ESmLJ;IVjLI;;;ACFA;ESmLJ;IAaI;IACA;IACA,cRlIG;IQmIH;IACA;;;;AAIJ;EACE,YR1IK;;;AQ6IP;EACE;;;AAGF;EACE;;AV1MA;EACE;;ACRA;ESgNJ;IVpMI;;;;AUyMJ;EACE;EACA,ORrJK;EQsJL,QRtJK;EQuJL;EACA,ORnJK;EQoJL,QRpJK;EQqJL,kBR7MM;EQ8MN;EACA;EACA,YACE;EAEF;EACA;;;AAGF;EACE;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA,YACE;;;AAMF;EACE;EACA;EACA;EACA;EACA;EACA;;AAGF;EACE,QRxLI;EQyLJ;;ATjQA;ES+PF;IAKI,ORzKiB;IQ0KjB,YACE;;;AAKN;EACE,kBR7PI;;ADfJ;ES2QF;IAII;;;AT/QF;ESmRF;IAEI;;;AAIJ;EACE;;AAGF;EACE;EACA;EACA;EACA,YACE;;ATlSF;ESwSA;IACE;IACA;IACA;;;AAIJ;EACE,aRxOI;;ADxEJ;ES+SF;IAII;;;;AC9TN;EACE;EACA;EACA;EACA,eT0EK;ESzEL;EACA,eTkFc;ESjFd,YACE;;;AAIJ;EACE;EACA;EACA;;;AAGF;AAAA;EAEE;EACA;EACA,kBTIM;ESHN;EACA;;AXNA;AAAA;EACE;;ACRA;EUOJ;AAAA;IXKI;;;AWKF;AAAA;EACE;;;AAOE;AAAA;EAEE;;AAGF;EACE,gBTkCD;;;AS3BL;EACE;;;AC9CF;EACE;EACA;EACA,kBVmBI;EUlBJ;EACA,eV+EY;;;AU1EhB;EACE,cVkBY;;;AUiCd;AAAA;AAAA;EAGE;EACA,eVMK;EULL,kBV7CM;EU8CN,eVgBc;EUfd;EACA;EACA;EACA;;AAIA;AAAA;AAAA;EACE,OVLG;EUMH;EACA;EACA;EACA;EACA,SVVG;EUWH;EACA;EACA,OV7DU;EU8DV;;AAEA;AAAA;AAAA;EACE,MVjEQ;;AUoEV;AAAA;AAAA;EACE;EACA;EACA;;AAGF;AAAA;AAAA;EACE;EACA;;AAMF;AAAA;AAAA;EACE;EACA;;;AASJ;EACE;EACA,SV/CG;EUgDH;EACA;EACA,eVtCY;;AUyCd;AAAA;EAEE;EACA;EACA;;;AAUJ;EACE;EACA,eVrEK;;AU6CL;EACE;EACA,SV/CG;EUgDH;EACA;EACA,eVtCY;;AUyCd;AAAA;EAEE;EACA;EACA;;;AAwBF;AAAA;EAEE;EACA,SVpFG;EUqFH;EACA;EACA,eV3EY;;;AUmFhB;EACE;EACA;EACA;EACA;;AAEA;AAAA;EAEE;EACA;EACA,kBV3JI;EU4JJ;;AZ9KF;AAAA;EACE;;ACEA;EWsKF;AAAA;IZpKE;;;AY8KF;EACE;EACA,eVjHG;EUkHH,cVlHG;;AUqHL;EACE;EACA;;;AAKJ;AAAA;EAEE,SV9HK;EU+HL,eV/HK;EUgIL;EACA;EACA,eVtHc;;AUwHd;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAIE;EACA;EACA;EACA;EACA;EACA;EACA;;;AAKJ;EACE;EACA;EACA;;;AAIF;AAAA;EAEE,YV9MM;EUmNJ,OVjNU;;;AUsNd;EACE,YVzNM;;;AWzBR;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAKF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;ACvOF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAKF;EACE;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;;;AbrBE;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;AAQR;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAKF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AdhHA;EACE;;ACYA;EcZJ;IfII;;;;AAKF;EACE;;ACEA;EcRJ;IfUI;;;;AAKF;EACE;;ACRA;EcJJ;IfgBI;;;;AAKF;EACE;;AClBA;EcAJ;IfsBI;;;;AAKF;EACE;;AC5BA;EcIJ;If4BI;;;;AAKF;EACE;;ACtCA;EcQJ;IfkCI;IACA,aEhDuB;;;;AFqDzB;EACE;EACA,aEvDuB;;ADKvB;EcYJ;If0CI;;;;AAKF;EACE;EACA,aElEuB;;ADKvB;EcgBJ;IfiDI;;;;AAKF;EACE;EACA,aE7EuB;;ADKvB;EcoBJ;IfwDI;;;;AAKF;EACE;EACA,aExFuB;;ADKvB;EcwBJ;If+DI;;;;Ae3DJ;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE,abxDiB;;;Aa2DnB;EACE,ab1DyB;;;Aa6D3B;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AC/EF;EACE;EACA;EACA;;AAGE;EACE;;;ACLN;EACE;EACA;;;AAQA;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AhBlCA;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AAaN;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AhB7GA;EgBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhB/IJ;EgBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhB/IJ;EgBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhB/IJ;EgBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhB/IJ;EgBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AC3JR;EACE;AAAA;AAAA;AAAA;AAAA;AAAA;IAME;;EAGF;IACE;IACA;;EAGF;IACE;IACA;IACA;;EAGF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;;EAGF;IACE;;EAGF;IACE;IACA;;;ACvCJ;EACE;EACA;EACA;EACA;EACA;EACA;EACA;;;AAGF;AAAA;EAEE,OjBwBW;EiBvBX,kBjBaM;EiBZN;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;;;ACtBF;EACE,kBlBsBM;;;AkBnBR;EACI;EACA;EACA,elB8EY;EkB7EZ;EACA;;AAEA;EACI,OlBgCI;EkB/BJ;EACA;EACA;EACA;EACA;EACA;;AAGJ;EACE,OlBsBM;EkBrBN;EACA;EACA;EACA;EACA;;;AAIN;EACI;EACA;EACA,elBmDY;EkBlDZ;EACA;;AACA;EACE;EACA;EACA,OlBIM;EkBHN;EACA;EACA;EACA;EACA;;;AAIN;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAIJ;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAMJ;EACI;EACA;EACA,elBKY;EkBJZ;EACA;;AAEA;EACI,OlB7CG;EkB8CH;EACA;EACA;EACA;EACA;EACA;;AAGJ;EACE,OlBvDK;EkBwDL;EACA;EACA;EACA;EACA;;;AAIN;EACI;EACA;EACA,elBtBY;EkBuBZ;EACA;;AACA;EACE;EACA;EACA,OlBzEK;EkB0EL;EACA;EACA;EACA;EACA;;;AAIN;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAIJ;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAMJ;EACI;EACA;EACA,elBpEY;EkBqEZ;EACA;;AAEA;EACI,OlB9GK;EkB+GL;EACA;EACA;EACA;EACA;EACA;;AAGJ;EACE,OlBxHO;EkByHP;EACA;EACA;EACA;EACA;;;AAIN;EACI;EACA;EACA,elB/FY;EkBgGZ;EACA;;AACA;EACE;EACA;EACA,OlB1IO;EkB2IP;EACA;EACA;EACA;EACA;;;AAIN;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAIJ;EACE;EACA;;AAEA;EACE;;AAGF;EACE","sourcesContent":["/*\ngenerated by accessible-pygments \nCopyright (c) 2022, Quansight Labs\nLicensed under the BSD license, see LICENSE for details.\n--\ngenerated by Pygments \nCopyright 2006-2025 by the Pygments team.\nLicensed under the BSD license, see LICENSE for details.\n*/\n\n.highlight .hll { background-color: #0969da4a }\n.highlight .c { color: #6E7781 } /* Comment */\n.highlight .err { color: #CF222E } /* Error */\n.highlight .k { color: #CF222E } /* Keyword */\n.highlight .l { color: #953800 } /* Literal */\n.highlight .n { color: #8250DF } /* Name */\n.highlight .o { color: #116329 } /* Operator */\n.highlight .p { color: #24292F } /* Punctuation */\n.highlight .ch { color: #6E7781 } /* Comment.Hashbang */\n.highlight .cm { color: #6E7781 } /* Comment.Multiline */\n.highlight .cp { color: #6E7781 } /* Comment.Preproc */\n.highlight .cpf { color: #6E7781 } /* Comment.PreprocFile */\n.highlight .c1 { color: #6E7781 } /* Comment.Single */\n.highlight .cs { color: #6E7781 } /* Comment.Special */\n.highlight .gd { color: #0550AE } /* Generic.Deleted */\n.highlight .ge { font-style: italic } /* Generic.Emph */\n.highlight .gr { color: #CF222E } /* Generic.Error */\n.highlight .gh { color: #0550AE } /* Generic.Heading */\n.highlight .gs { font-weight: bold } /* Generic.Strong */\n.highlight .gu { color: #0550AE } /* Generic.Subheading */\n.highlight .kc { color: #0550AE } /* Keyword.Constant */\n.highlight .kd { color: #CF222E } /* Keyword.Declaration */\n.highlight .kn { color: #CF222E } /* Keyword.Namespace */\n.highlight .kp { color: #CF222E } /* Keyword.Pseudo */\n.highlight .kr { color: #CF222E } /* Keyword.Reserved */\n.highlight .kt { color: #CF222E } /* Keyword.Type */\n.highlight .ld { color: #953800 } /* Literal.Date */\n.highlight .m { color: #953800 } /* Literal.Number */\n.highlight .s { color: #0550AE } /* Literal.String */\n.highlight .na { color: #953800 } /* Name.Attribute */\n.highlight .nb { color: #953800 } /* Name.Builtin */\n.highlight .nc { color: #0550AE } /* Name.Class */\n.highlight .no { color: #0550AE } /* Name.Constant */\n.highlight .nd { color: #953800 } /* Name.Decorator */\n.highlight .ni { color: #116329 } /* Name.Entity */\n.highlight .ne { color: #8250DF } /* Name.Exception */\n.highlight .nf { color: #0550AE } /* Name.Function */\n.highlight .nl { color: #953800 } /* Name.Label */\n.highlight .nn { color: #24292F } /* Name.Namespace */\n.highlight .nx { color: #8250DF } /* Name.Other */\n.highlight .py { color: #0550AE } /* Name.Property */\n.highlight .nt { color: #116329 } /* Name.Tag */\n.highlight .nv { color: #953800 } /* Name.Variable */\n.highlight .ow { color: #8250DF } /* Operator.Word */\n.highlight .pm { color: #24292F } /* Punctuation.Marker */\n.highlight .w { color: #24292F } /* Text.Whitespace */\n.highlight .mb { color: #953800 } /* Literal.Number.Bin */\n.highlight .mf { color: #953800 } /* Literal.Number.Float */\n.highlight .mh { color: #953800 } /* Literal.Number.Hex */\n.highlight .mi { color: #953800 } /* Literal.Number.Integer */\n.highlight .mo { color: #953800 } /* Literal.Number.Oct */\n.highlight .sa { color: #0550AE } /* Literal.String.Affix */\n.highlight .sb { color: #0550AE } /* Literal.String.Backtick */\n.highlight .sc { color: #0550AE } /* Literal.String.Char */\n.highlight .dl { color: #0550AE } /* Literal.String.Delimiter */\n.highlight .sd { color: #0550AE } /* Literal.String.Doc */\n.highlight .s2 { color: #0550AE } /* Literal.String.Double */\n.highlight .se { color: #0550AE } /* Literal.String.Escape */\n.highlight .sh { color: #0550AE } /* Literal.String.Heredoc */\n.highlight .si { color: #0550AE } /* Literal.String.Interpol */\n.highlight .sx { color: #0550AE } /* Literal.String.Other */\n.highlight .sr { color: #0550AE } /* Literal.String.Regex */\n.highlight .s1 { color: #0550AE } /* Literal.String.Single */\n.highlight .ss { color: #0550AE } /* Literal.String.Symbol */\n.highlight .bp { color: #953800 } /* Name.Builtin.Pseudo */\n.highlight .fm { color: #0550AE } /* Name.Function.Magic */\n.highlight .vc { color: #953800 } /* Name.Variable.Class */\n.highlight .vg { color: #953800 } /* Name.Variable.Global */\n.highlight .vi { color: #953800 } /* Name.Variable.Instance */\n.highlight .vm { color: #953800 } /* Name.Variable.Magic */\n.highlight .il { color: #953800 } /* Literal.Number.Integer.Long */\n","/*! normalize.css v8.0.1 | MIT License | github.com/necolas/normalize.css */\n\n/* Document\n ========================================================================== */\n\n/**\n * 1. Correct the line height in all browsers.\n * 2. Prevent adjustments of font size after orientation changes in iOS.\n */\n\nhtml {\n line-height: 1.15; /* 1 */\n text-size-adjust: 100%; /* 2 */\n}\n\n/* Sections\n ========================================================================== */\n\n/**\n * Remove the margin in all browsers.\n */\n\nbody {\n margin: 0;\n}\n\n/**\n * Render the `main` element consistently in IE.\n */\n\nmain {\n display: block;\n}\n\n/**\n * Correct the font size and margin on `h1` elements within `section` and\n * `article` contexts in Chrome, Firefox, and Safari.\n */\n\nh1 {\n font-size: 2em;\n margin: 0.67em 0;\n}\n\n/* Grouping content\n ========================================================================== */\n\n/**\n * 1. Add the correct box sizing in Firefox.\n * 2. Show the overflow in Edge and IE.\n */\n\nhr {\n box-sizing: content-box; /* 1 */\n height: 0; /* 1 */\n overflow: visible; /* 2 */\n}\n\n/**\n * 1. Correct the inheritance and scaling of font size in all browsers.\n * 2. Correct the odd `em` font sizing in all browsers.\n */\n\npre {\n font-family: monospace; /* 1 */\n font-size: 1em; /* 2 */\n}\n\n/* Text-level semantics\n ========================================================================== */\n\n/**\n * Remove the gray background on active links in IE 10.\n */\n\na {\n background-color: transparent;\n}\n\n/**\n * 1. Remove the bottom border in Chrome 57-\n * 2. Add the correct text decoration in Chrome, Edge, IE, Opera, and Safari.\n */\n\nabbr[title] {\n border-bottom: none; /* 1 */\n text-decoration: underline; /* 2 */\n text-decoration: underline dotted; /* 2 */\n}\n\n/**\n * Add the correct font weight in Chrome, Edge, and Safari.\n */\n\nb,\nstrong {\n font-weight: bolder;\n}\n\n/**\n * 1. Correct the inheritance and scaling of font size in all browsers.\n * 2. Correct the odd `em` font sizing in all browsers.\n */\n\ncode,\nkbd,\nsamp {\n font-family: monospace; /* 1 */\n font-size: 1em; /* 2 */\n}\n\n/**\n * Add the correct font size in all browsers.\n */\n\nsmall {\n font-size: 80%;\n}\n\n/**\n * Prevent `sub` and `sup` elements from affecting the line height in\n * all browsers.\n */\n\nsub,\nsup {\n font-size: 75%;\n line-height: 0;\n position: relative;\n vertical-align: baseline;\n}\n\nsub {\n bottom: -0.25em;\n}\n\nsup {\n top: -0.5em;\n}\n\n/* Embedded content\n ========================================================================== */\n\n/**\n * Remove the border on images inside links in IE 10.\n */\n\nimg {\n border-style: none;\n}\n\n/* Forms\n ========================================================================== */\n\n/**\n * 1. Change the font styles in all browsers.\n * 2. Remove the margin in Firefox and Safari.\n */\n\nbutton,\ninput,\noptgroup,\nselect,\ntextarea {\n font-family: inherit; /* 1 */\n font-size: 100%; /* 1 */\n line-height: 1.15; /* 1 */\n margin: 0; /* 2 */\n}\n\n/**\n * Show the overflow in IE.\n * 1. Show the overflow in Edge.\n */\n\nbutton,\ninput {\n /* 1 */\n overflow: visible;\n}\n\n/**\n * Remove the inheritance of text transform in Edge, Firefox, and IE.\n * 1. Remove the inheritance of text transform in Firefox.\n */\n\nbutton,\nselect {\n /* 1 */\n text-transform: none;\n}\n\n/**\n * Correct the inability to style clickable types in iOS and Safari.\n */\n\nbutton,\n[type=\"button\"],\n[type=\"reset\"],\n[type=\"submit\"] {\n appearance: button;\n}\n\n/**\n * Remove the inner border and padding in Firefox.\n */\n\nbutton::-moz-focus-inner,\n[type=\"button\"]::-moz-focus-inner,\n[type=\"reset\"]::-moz-focus-inner,\n[type=\"submit\"]::-moz-focus-inner {\n border-style: none;\n padding: 0;\n}\n\n/**\n * Restore the focus styles unset by the previous rule.\n */\n\nbutton:-moz-focusring,\n[type=\"button\"]:-moz-focusring,\n[type=\"reset\"]:-moz-focusring,\n[type=\"submit\"]:-moz-focusring {\n outline: 1px dotted ButtonText;\n}\n\n/**\n * Correct the padding in Firefox.\n */\n\nfieldset {\n padding: 0.35em 0.75em 0.625em;\n}\n\n/**\n * 1. Correct the text wrapping in Edge and IE.\n * 2. Correct the color inheritance from `fieldset` elements in IE.\n * 3. Remove the padding so developers are not caught out when they zero out\n * `fieldset` elements in all browsers.\n */\n\nlegend {\n box-sizing: border-box; /* 1 */\n color: inherit; /* 2 */\n display: table; /* 1 */\n max-width: 100%; /* 1 */\n padding: 0; /* 3 */\n white-space: normal; /* 1 */\n}\n\n/**\n * Add the correct vertical alignment in Chrome, Firefox, and Opera.\n */\n\nprogress {\n vertical-align: baseline;\n}\n\n/**\n * Remove the default vertical scrollbar in IE 10+.\n */\n\ntextarea {\n overflow: auto;\n}\n\n/**\n * 1. Add the correct box sizing in IE 10.\n * 2. Remove the padding in IE 10.\n */\n\n[type=\"checkbox\"],\n[type=\"radio\"] {\n box-sizing: border-box; /* 1 */\n padding: 0; /* 2 */\n}\n\n/**\n * Correct the cursor style of increment and decrement buttons in Chrome.\n */\n\n[type=\"number\"]::-webkit-inner-spin-button,\n[type=\"number\"]::-webkit-outer-spin-button {\n height: auto;\n}\n\n/**\n * 1. Correct the odd appearance in Chrome and Safari.\n * 2. Correct the outline style in Safari.\n */\n\n[type=\"search\"] {\n appearance: textfield; /* 1 */\n outline-offset: -2px; /* 2 */\n}\n\n/**\n * Remove the inner padding in Chrome and Safari on macOS.\n */\n\n[type=\"search\"]::-webkit-search-decoration {\n appearance: none;\n}\n\n/**\n * 1. Correct the inability to style clickable types in iOS and Safari.\n * 2. Change font properties to `inherit` in Safari.\n */\n\n::-webkit-file-upload-button {\n appearance: button; /* 1 */\n font: inherit; /* 2 */\n}\n\n/* Interactive\n ========================================================================== */\n\n/*\n * Add the correct display in Edge, IE 10+, and Firefox.\n */\n\ndetails {\n display: block;\n}\n\n/*\n * Add the correct display in all browsers.\n */\n\nsummary {\n display: list-item;\n}\n\n/* Misc\n ========================================================================== */\n\n/**\n * Add the correct display in IE 10+.\n */\n\ntemplate {\n display: none;\n}\n\n/**\n * Add the correct display in IE 10.\n */\n\n[hidden] {\n display: none;\n}\n","// Base element style overrides\n// stylelint-disable selector-no-type, selector-max-type, selector-max-specificity, selector-max-id\n\n:root {\n color-scheme: $color-scheme;\n}\n\n* {\n box-sizing: border-box;\n}\n\nhtml {\n scroll-behavior: smooth;\n\n @include fs-4;\n}\n\nbody {\n font-family: $body-font-family;\n font-size: inherit;\n line-height: $body-line-height;\n color: $body-text-color;\n background-color: $body-background-color;\n overflow-wrap: break-word;\n}\n\nol,\nul,\ndl,\npre,\naddress,\nblockquote,\ntable,\ndiv,\nhr,\nform,\nfieldset,\nnoscript .table-wrapper {\n margin-top: 0;\n}\n\nh1,\nh2,\nh3,\nh4,\nh5,\nh6,\n#toctitle {\n margin-top: 0;\n margin-bottom: 1em;\n font-weight: 500;\n line-height: $body-heading-line-height;\n color: $body-heading-color;\n}\n\np {\n margin-top: 1em;\n margin-bottom: 1em;\n}\n\na {\n color: $link-color;\n text-decoration: none;\n}\n\na:not([class]) {\n text-decoration: underline;\n text-decoration-color: $border-color;\n text-underline-offset: 2px;\n\n &:hover {\n text-decoration-color: rgba($link-color, 0.45);\n }\n}\n\ncode {\n font-family: $mono-font-family;\n font-size: 0.75em;\n line-height: $body-line-height;\n}\n\nfigure,\npre {\n margin: 0;\n}\n\nli {\n margin: 0.25em 0;\n}\n\nimg {\n max-width: 100%;\n height: auto;\n}\n\nhr {\n height: 1px;\n padding: 0;\n margin: $sp-6 0;\n background-color: $border-color;\n border: 0;\n}\n\n// adds a GitHub-style sidebar to blockquotes\nblockquote {\n margin: 10px 0;\n\n // resets user-agent stylesheets for blockquotes\n margin-block-start: 0;\n margin-inline-start: 0;\n padding-left: 1rem;\n border-left: 3px solid $border-color;\n}\n","$color-scheme: light !default;\n$body-background-color: $white !default;\n$body-heading-color: $grey-dk-300 !default;\n$body-text-color: $grey-dk-100 !default;\n$link-color: $purple-000 !default;\n$nav-child-link-color: $grey-dk-100 !default;\n$sidebar-color: $grey-lt-000 !default;\n$base-button-color: #f7f7f7 !default;\n$btn-primary-color: $purple-100 !default;\n$code-background-color: $white !default;\n$feedback-color: darken($sidebar-color, 3%) !default;\n$table-background-color: $white !default;\n$search-background-color: $white !default;\n$search-result-preview-color: $grey-dk-100 !default;\n\n@import \"./vendor/accessible-pygments/github-light\";\n","@mixin fs-1 {\n & {\n font-size: $font-size-1 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-1-sm !important;\n }\n}\n\n@mixin fs-2 {\n & {\n font-size: $font-size-2 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-3 !important;\n }\n}\n\n@mixin fs-3 {\n & {\n font-size: $font-size-3 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-4 !important;\n }\n}\n\n@mixin fs-4 {\n & {\n font-size: $font-size-4 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-5 !important;\n }\n}\n\n@mixin fs-5 {\n & {\n font-size: $font-size-5 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-6 !important;\n }\n}\n\n@mixin fs-6 {\n & {\n font-size: $font-size-6 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-7 !important;\n line-height: $body-heading-line-height;\n }\n}\n\n@mixin fs-7 {\n & {\n font-size: $font-size-7 !important;\n line-height: $body-heading-line-height;\n }\n\n @include mq(sm) {\n font-size: $font-size-8 !important;\n }\n}\n\n@mixin fs-8 {\n & {\n font-size: $font-size-8 !important;\n line-height: $body-heading-line-height;\n }\n\n @include mq(sm) {\n font-size: $font-size-9 !important;\n }\n}\n\n@mixin fs-9 {\n & {\n font-size: $font-size-9 !important;\n line-height: $body-heading-line-height;\n }\n\n @include mq(sm) {\n font-size: $font-size-10 !important;\n }\n}\n\n@mixin fs-10 {\n & {\n font-size: $font-size-10 !important;\n line-height: $body-heading-line-height;\n }\n\n @include mq(sm) {\n font-size: $font-size-10-sm !important;\n }\n}\n","// Media query\n\n// Media query mixin\n// Usage:\n// @include mq(md) {\n// ..medium and up styles\n// }\n@mixin mq($name) {\n // Retrieves the value from the key\n $value: map-get($media-queries, $name);\n\n // If the key exists in the map\n @if $value {\n // Prints a media query based on the value\n @media (min-width: $value) {\n @content;\n }\n } @else {\n @warn \"No value could be retrieved from `#{$media-query}`. Please make sure it is defined in `$media-queries` map.\";\n }\n}\n\n// Responsive container\n\n@mixin container {\n padding-right: $gutter-spacing-sm;\n padding-left: $gutter-spacing-sm;\n\n @include mq(md) {\n padding-right: $gutter-spacing;\n padding-left: $gutter-spacing;\n }\n}\n","// Typography\n\n// prettier-ignore\n$body-font-family: system-ui, -apple-system, blinkmacsystemfont, \"Segoe UI\",\n roboto, \"Helvetica Neue\", arial, sans-serif, \"Segoe UI Emoji\" !default;\n$mono-font-family: \"SFMono-Regular\", menlo, consolas, monospace !default;\n$root-font-size: 16px !default; // DEPRECATED: previously base font-size for rems\n$body-line-height: 1.4 !default;\n$content-line-height: 1.6 !default;\n$body-heading-line-height: 1.25 !default;\n\n// Font size\n// `-sm` suffix is the size at the small (and above) media query\n\n$font-size-1: 0.5625rem !default;\n$font-size-1-sm: 0.625rem !default;\n$font-size-2: 0.6875rem !default; // h4 - uppercased!, h6 not uppercased, text-small\n$font-size-3: 0.75rem !default; // h5\n$font-size-4: 0.875rem !default;\n$font-size-5: 1rem !default; // h3\n$font-size-6: 1.125rem !default; // h2\n$font-size-7: 1.5rem !default;\n$font-size-8: 2rem !default; // h1\n$font-size-9: 2.25rem !default;\n$font-size-10: 2.625rem !default;\n$font-size-10-sm: 3rem !default;\n\n// Colors\n\n$white: #fff !default;\n$grey-dk-000: #959396 !default;\n$grey-dk-100: #5c5962 !default;\n$grey-dk-200: #44434d !default;\n$grey-dk-250: #302d36 !default;\n$grey-dk-300: #27262b !default;\n$grey-lt-000: #f5f6fa !default;\n$grey-lt-100: #eeebee !default;\n$grey-lt-200: #ecebed !default;\n$grey-lt-300: #e6e1e8 !default;\n$purple-000: #7253ed !default;\n$purple-100: #5e41d0 !default;\n$purple-200: #4e26af !default;\n$purple-300: #381885 !default;\n$blue-000: #2c84fa !default;\n$blue-100: #2869e6 !default;\n$blue-200: #264caf !default;\n$blue-300: #183385 !default;\n$green-000: #41d693 !default;\n$green-100: #11b584 !default;\n$green-200: #009c7b !default;\n$green-300: #026e57 !default;\n$yellow-000: #ffeb82 !default;\n$yellow-100: #fadf50 !default;\n$yellow-200: #f7d12e !default;\n$yellow-300: #e7af06 !default;\n$red-000: #f77e7e !default;\n$red-100: #f96e65 !default;\n$red-200: #e94c4c !default;\n$red-300: #dd2e2e !default;\n\n// Spacing\n\n$spacing-unit: 1rem; // 1rem == 16px\n\n$spacers: (\n sp-0: 0,\n sp-1: $spacing-unit * 0.25,\n sp-2: $spacing-unit * 0.5,\n sp-3: $spacing-unit * 0.75,\n sp-4: $spacing-unit,\n sp-5: $spacing-unit * 1.5,\n sp-6: $spacing-unit * 2,\n sp-7: $spacing-unit * 2.5,\n sp-8: $spacing-unit * 3,\n sp-9: $spacing-unit * 3.5,\n sp-10: $spacing-unit * 4,\n) !default;\n$sp-1: map-get($spacers, sp-1) !default; // 0.25 rem == 4px\n$sp-2: map-get($spacers, sp-2) !default; // 0.5 rem == 8px\n$sp-3: map-get($spacers, sp-3) !default; // 0.75 rem == 12px\n$sp-4: map-get($spacers, sp-4) !default; // 1 rem == 16px\n$sp-5: map-get($spacers, sp-5) !default; // 1.5 rem == 24px\n$sp-6: map-get($spacers, sp-6) !default; // 2 rem == 32px\n$sp-7: map-get($spacers, sp-7) !default; // 2.5 rem == 40px\n$sp-8: map-get($spacers, sp-8) !default; // 3 rem == 48px\n$sp-9: map-get($spacers, sp-9) !default; // 3.5 rem == 56px\n$sp-10: map-get($spacers, sp-10) !default; // 4 rem == 64px\n\n// Borders\n\n$border: 1px solid !default;\n$border-radius: 4px !default;\n$border-color: $grey-lt-100 !default;\n\n// Grid system\n\n$gutter-spacing: $sp-6 !default;\n$gutter-spacing-sm: $sp-4 !default;\n$nav-width: 16.5rem !default;\n$nav-width-md: 15.5rem !default;\n$nav-list-item-height: $sp-6 !default;\n$nav-list-item-height-sm: $sp-8 !default;\n$nav-list-expander-right: true;\n$content-width: 50rem !default;\n$header-height: 3.75rem !default;\n$search-results-width: $content-width - $nav-width !default;\n$transition-duration: 400ms;\n\n// Media queries in pixels\n\n$media-queries: (\n xs: 20rem,\n sm: 31.25rem,\n md: $content-width,\n lg: $content-width + $nav-width,\n xl: 87.5rem,\n) !default;\n","// The basic two column layout\n\n.side-bar {\n z-index: 0;\n display: flex;\n flex-wrap: wrap;\n background-color: $sidebar-color;\n\n @include mq(md) {\n flex-flow: column nowrap;\n position: fixed;\n width: $nav-width-md;\n height: 100%;\n border-right: $border $border-color;\n align-items: flex-end;\n }\n\n @include mq(lg) {\n width: calc((100% - #{$nav-width + $content-width}) / 2 + #{$nav-width});\n min-width: $nav-width;\n }\n\n & + .main {\n @include mq(md) {\n margin-left: $nav-width-md;\n }\n\n @include mq(lg) {\n // stylelint-disable function-name-case\n // disable for Max(), we want to use the CSS max() function\n margin-left: Max(\n #{$nav-width},\n calc((100% - #{$nav-width + $content-width}) / 2 + #{$nav-width})\n );\n // stylelint-enable function-name-case\n }\n\n .main-header {\n display: none;\n background-color: $sidebar-color;\n\n @include mq(md) {\n display: flex;\n background-color: $body-background-color;\n }\n\n &.nav-open {\n display: block;\n\n @include mq(md) {\n display: flex;\n }\n }\n }\n }\n}\n\n.main {\n margin: auto;\n\n @include mq(md) {\n position: relative;\n max-width: $content-width;\n }\n}\n\n.main-content-wrap {\n padding-top: $gutter-spacing-sm;\n padding-bottom: $gutter-spacing-sm;\n\n @include container;\n\n @include mq(md) {\n padding-top: $gutter-spacing;\n padding-bottom: $gutter-spacing;\n }\n}\n\n.main-header {\n z-index: 0;\n border-bottom: $border $border-color;\n\n @include mq(md) {\n display: flex;\n justify-content: space-between;\n height: $header-height;\n }\n}\n\n.site-nav,\n.site-header,\n.site-footer {\n width: 100%;\n\n @include mq(lg) {\n width: $nav-width;\n }\n}\n\n.site-nav {\n display: none;\n\n &.nav-open {\n display: block;\n }\n\n @include mq(md) {\n display: block;\n padding-top: $sp-8;\n padding-bottom: $gutter-spacing-sm;\n overflow-y: auto;\n flex: 1 1 auto;\n }\n}\n\n.site-header {\n display: flex;\n min-height: $header-height;\n align-items: center;\n\n @include mq(md) {\n height: $header-height;\n max-height: $header-height;\n border-bottom: $border $border-color;\n }\n}\n\n.site-title {\n flex-grow: 1;\n display: flex;\n height: 100%;\n align-items: center;\n padding-top: $sp-3;\n padding-bottom: $sp-3;\n color: $body-heading-color;\n\n @include container;\n\n @include fs-6;\n\n @include mq(md) {\n padding-top: $sp-2;\n padding-bottom: $sp-2;\n }\n}\n\n@if variable-exists(logo) {\n .site-logo {\n width: 100%;\n height: 100%;\n background-image: url($logo);\n background-repeat: no-repeat;\n background-position: left center;\n background-size: contain;\n }\n}\n\n.site-button {\n display: flex;\n height: 100%;\n padding: $gutter-spacing-sm;\n align-items: center;\n}\n\n@include mq(md) {\n .site-header .site-button {\n display: none;\n }\n}\n\n.site-title:hover {\n background-image: linear-gradient(\n -90deg,\n rgba($feedback-color, 1) 0%,\n rgba($feedback-color, 0.8) 80%,\n rgba($feedback-color, 0) 100%\n );\n}\n\n.site-button:hover {\n background-image: linear-gradient(\n -90deg,\n rgba($feedback-color, 1) 0%,\n rgba($feedback-color, 0.8) 100%\n );\n}\n\n.site-footer {\n position: absolute;\n bottom: 0;\n left: 0;\n padding-top: $sp-4;\n padding-bottom: $sp-4;\n\n @include container;\n\n @include fs-2;\n\n @include mq(md) {\n position: static;\n justify-self: end;\n }\n}\n\n.icon {\n width: $sp-5;\n height: $sp-5;\n color: $link-color;\n}\n","@charset \"UTF-8\";\n\n// Styles for rendered markdown in the .main-content container\n// stylelint-disable selector-no-type, max-nesting-depth, selector-max-compound-selectors, selector-max-type, selector-max-specificity, selector-max-id\n\n.main-content {\n line-height: $content-line-height;\n\n ol,\n ul,\n dl,\n pre,\n address,\n blockquote,\n .table-wrapper {\n margin-top: 0.5em;\n }\n\n a {\n overflow: hidden;\n text-overflow: ellipsis;\n }\n\n ul,\n ol {\n padding-left: 1.5em;\n }\n\n li {\n .highlight {\n margin-top: $sp-1;\n }\n }\n\n ol {\n list-style-type: none;\n counter-reset: step-counter;\n\n > li {\n position: relative;\n\n &::before {\n position: absolute;\n top: 0.2em;\n left: -1.6em;\n color: $grey-dk-000;\n content: counter(step-counter);\n counter-increment: step-counter;\n @include fs-3;\n\n @include mq(sm) {\n top: 0.11em;\n }\n }\n\n ol {\n counter-reset: sub-counter;\n\n > li {\n &::before {\n content: counter(sub-counter, lower-alpha);\n counter-increment: sub-counter;\n }\n }\n }\n }\n }\n\n ul {\n list-style: none;\n\n > li {\n &::before {\n position: absolute;\n margin-left: -1.4em;\n color: $grey-dk-000;\n content: \"•\";\n }\n }\n }\n\n .task-list-item {\n &::before {\n content: \"\";\n }\n }\n\n .task-list-item-checkbox {\n margin-right: 0.6em;\n margin-left: -1.4em;\n\n // The same margin-left is used above for ul > li::before\n }\n\n hr + * {\n margin-top: 0;\n }\n\n h1:first-of-type {\n margin-top: 0.5em;\n }\n\n dl {\n display: grid;\n grid-template: auto / 10em 1fr;\n }\n\n dt,\n dd {\n margin: 0.25em 0;\n }\n\n dt {\n grid-column: 1;\n font-weight: 500;\n text-align: right;\n\n &::after {\n content: \":\";\n }\n }\n\n dd {\n grid-column: 2;\n margin-bottom: 0;\n margin-left: 1em;\n\n blockquote,\n div,\n dl,\n dt,\n h1,\n h2,\n h3,\n h4,\n h5,\n h6,\n li,\n ol,\n p,\n pre,\n table,\n ul,\n .table-wrapper {\n &:first-child {\n margin-top: 0;\n }\n }\n }\n\n dd,\n ol,\n ul {\n dl:first-child {\n dt:first-child,\n dd:nth-child(2) {\n margin-top: 0;\n }\n }\n }\n\n .anchor-heading {\n position: absolute;\n right: -$sp-4;\n width: $sp-5;\n height: 100%;\n padding-right: $sp-1;\n padding-left: $sp-1;\n overflow: visible;\n\n @include mq(md) {\n right: auto;\n left: -$sp-5;\n }\n\n svg {\n display: inline-block;\n width: 100%;\n height: 100%;\n color: $link-color;\n visibility: hidden;\n }\n }\n\n .anchor-heading:hover,\n .anchor-heading:focus,\n h1:hover > .anchor-heading,\n h2:hover > .anchor-heading,\n h3:hover > .anchor-heading,\n h4:hover > .anchor-heading,\n h5:hover > .anchor-heading,\n h6:hover > .anchor-heading {\n svg {\n visibility: visible;\n }\n }\n\n summary {\n cursor: pointer;\n }\n\n h1,\n h2,\n h3,\n h4,\n h5,\n h6,\n #toctitle {\n position: relative;\n margin-top: 1.5em;\n margin-bottom: 0.25em;\n\n + table,\n + .table-wrapper,\n + .code-example,\n + .highlighter-rouge,\n + .sectionbody .listingblock {\n margin-top: 1em;\n }\n\n + p:not(.label) {\n margin-top: 0;\n }\n }\n\n > h1:first-child,\n > h2:first-child,\n > h3:first-child,\n > h4:first-child,\n > h5:first-child,\n > h6:first-child,\n > .sect1:first-child > h2,\n > .sect2:first-child > h3,\n > .sect3:first-child > h4,\n > .sect4:first-child > h5,\n > .sect5:first-child > h6 {\n margin-top: $sp-2;\n }\n}\n","// Main nav, breadcrumb, etc...\n// stylelint-disable selector-no-type, max-nesting-depth, selector-max-compound-selectors, selector-max-type, selector-max-specificity\n\n.nav-list {\n padding: 0;\n margin-top: 0;\n margin-bottom: 0;\n list-style: none;\n\n .nav-list-item {\n position: relative;\n margin: 0;\n\n @include fs-4;\n\n @include mq(md) {\n @include fs-3;\n }\n\n .nav-list-link {\n display: block;\n min-height: $nav-list-item-height-sm;\n padding-top: $sp-1;\n padding-bottom: $sp-1;\n line-height: #{$nav-list-item-height-sm - 2 * $sp-1};\n @if $nav-list-expander-right {\n padding-right: $nav-list-item-height-sm;\n padding-left: $gutter-spacing-sm;\n } @else {\n padding-right: $gutter-spacing-sm;\n padding-left: $nav-list-item-height-sm;\n }\n\n @include mq(md) {\n min-height: $nav-list-item-height;\n line-height: #{$nav-list-item-height - 2 * $sp-1};\n @if $nav-list-expander-right {\n padding-right: $nav-list-item-height;\n padding-left: $gutter-spacing;\n } @else {\n padding-right: $gutter-spacing;\n padding-left: $nav-list-item-height;\n }\n }\n\n &.external > svg {\n width: $sp-4;\n height: $sp-4;\n vertical-align: text-bottom;\n }\n\n &.active {\n font-weight: 600;\n text-decoration: none;\n }\n\n &:hover,\n &.active {\n color: darken($link-color, 5%);\n background-image: linear-gradient(\n -90deg,\n rgba($feedback-color, 1) 0%,\n rgba($feedback-color, 0.8) 80%,\n rgba($feedback-color, 0) 100%\n );\n }\n }\n\n .nav-list-expander {\n position: absolute;\n @if $nav-list-expander-right {\n right: 0;\n }\n\n width: $nav-list-item-height-sm;\n height: $nav-list-item-height-sm;\n padding: #{$nav-list-item-height-sm * 0.25};\n color: $link-color;\n\n @include mq(md) {\n width: $nav-list-item-height;\n height: $nav-list-item-height;\n padding: #{$nav-list-item-height * 0.25};\n }\n\n &:hover {\n background-image: linear-gradient(\n -90deg,\n rgba($feedback-color, 1) 0%,\n rgba($feedback-color, 0.8) 100%\n );\n }\n\n @if $nav-list-expander-right {\n svg {\n transform: rotate(90deg);\n }\n }\n }\n\n > .nav-list {\n display: none;\n padding-left: $sp-3;\n list-style: none;\n\n .nav-list-item {\n position: relative;\n\n .nav-list-link {\n color: $nav-child-link-color;\n }\n\n .nav-list-expander {\n color: $nav-child-link-color;\n }\n }\n }\n\n &.active {\n > .nav-list-expander svg {\n @if $nav-list-expander-right {\n transform: rotate(-90deg);\n } @else {\n transform: rotate(90deg);\n }\n }\n\n > .nav-list {\n display: block;\n }\n }\n }\n}\n\n.nav-category {\n padding: $sp-2 $gutter-spacing-sm;\n font-weight: 600;\n text-align: start;\n text-transform: uppercase;\n border-bottom: $border $border-color;\n @include fs-2;\n\n @include mq(md) {\n padding: $sp-2 $gutter-spacing;\n margin-top: $gutter-spacing-sm;\n text-align: start;\n\n &:first-child {\n margin-top: 0;\n }\n }\n}\n\n.nav-list.nav-category-list {\n > .nav-list-item {\n margin: 0;\n\n > .nav-list {\n padding: 0;\n\n > .nav-list-item {\n > .nav-list-link {\n color: $link-color;\n }\n\n > .nav-list-expander {\n color: $link-color;\n }\n }\n }\n }\n}\n\n// Aux nav\n\n.aux-nav {\n height: 100%;\n overflow-x: auto;\n @include fs-2;\n\n .aux-nav-list {\n display: flex;\n height: 100%;\n padding: 0;\n margin: 0;\n list-style: none;\n }\n\n .aux-nav-list-item {\n display: inline-block;\n height: 100%;\n padding: 0;\n margin: 0;\n }\n\n @include mq(md) {\n padding-right: $gutter-spacing-sm;\n }\n}\n\n// Breadcrumb nav\n\n.breadcrumb-nav {\n @include mq(md) {\n margin-top: -$sp-4;\n }\n}\n\n.breadcrumb-nav-list {\n padding-left: 0;\n margin-bottom: $sp-3;\n list-style: none;\n}\n\n.breadcrumb-nav-list-item {\n display: table-cell;\n @include fs-2;\n\n &::before {\n display: none;\n }\n\n &::after {\n display: inline-block;\n margin-right: $sp-2;\n margin-left: $sp-2;\n color: $grey-dk-000;\n content: \"/\";\n }\n\n &:last-child {\n &::after {\n content: \"\";\n }\n }\n}\n","// Typography\n// stylelint-disable selector-no-type, selector-max-type, selector-max-specificity, selector-max-id\n\nh1,\n.text-alpha {\n font-weight: 300;\n\n @include fs-8;\n}\n\nh2,\n.text-beta,\n#toctitle {\n @include fs-6;\n}\n\nh3,\n.text-gamma {\n @include fs-5;\n}\n\nh4,\n.text-delta {\n font-weight: 400;\n text-transform: uppercase;\n letter-spacing: 0.1em;\n\n @include fs-2;\n}\n\nh4 code {\n text-transform: none;\n}\n\nh5,\n.text-epsilon {\n @include fs-3;\n}\n\nh6,\n.text-zeta {\n @include fs-2;\n}\n\n.text-small {\n @include fs-2;\n}\n\n.text-mono {\n font-family: $mono-font-family !important;\n}\n\n.text-left {\n text-align: left !important;\n}\n\n.text-center {\n text-align: center !important;\n}\n\n.text-right {\n text-align: right !important;\n}\n","// Labels (not the form kind)\n\n// this :not() prevents a style clash with Mermaid.js's\n// diagram labels, which also use .label\n// for more, see https://github.com/just-the-docs/just-the-docs/issues/1272\n// and the accompanying PR\n.label:not(g),\n.label-blue:not(g) {\n display: inline-block;\n padding: 0.16em 0.56em;\n margin-right: $sp-2;\n margin-left: $sp-2;\n color: $white;\n text-transform: uppercase;\n vertical-align: middle;\n background-color: $blue-100;\n border-radius: 12px;\n\n @include fs-2;\n}\n\n.label-green:not(g) {\n background-color: $green-300;\n}\n\n.label-purple:not(g) {\n background-color: $purple-100;\n}\n\n.label-red:not(g) {\n background-color: $red-300;\n}\n\n.label-yellow:not(g) {\n color: $grey-dk-200;\n background-color: $yellow-200;\n}\n","// Buttons and things that look like buttons\n// stylelint-disable color-named\n\n.btn {\n display: inline-block;\n box-sizing: border-box;\n padding: 0.3em 1em;\n margin: 0;\n font-family: inherit;\n font-size: inherit;\n font-weight: 500;\n line-height: 1.5;\n color: $link-color;\n text-decoration: none;\n vertical-align: baseline;\n cursor: pointer;\n background-color: $base-button-color;\n border-width: 0;\n border-radius: $border-radius;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n appearance: none;\n\n &:focus {\n text-decoration: none;\n outline: none;\n box-shadow: 0 0 0 3px rgba(blue, 0.25);\n }\n\n &:focus:hover,\n &.selected:focus {\n box-shadow: 0 0 0 3px rgba(blue, 0.25);\n }\n\n &:hover,\n &.zeroclipboard-is-hover {\n color: darken($link-color, 2%);\n }\n\n &:hover,\n &:active,\n &.zeroclipboard-is-hover,\n &.zeroclipboard-is-active {\n text-decoration: none;\n background-color: darken($base-button-color, 1%);\n }\n\n &:active,\n &.selected,\n &.zeroclipboard-is-active {\n background-color: darken($base-button-color, 3%);\n background-image: none;\n box-shadow: inset 0 2px 4px rgba(0, 0, 0, 0.15);\n }\n\n &.selected:hover {\n background-color: darken(#dcdcdc, 5%);\n }\n\n &:disabled,\n &.disabled {\n &,\n &:hover {\n color: rgba(102, 102, 102, 0.5);\n cursor: default;\n background-color: rgba(229, 229, 229, 0.5);\n background-image: none;\n box-shadow: none;\n }\n }\n}\n\n.btn-outline {\n color: $link-color;\n background: transparent;\n box-shadow: inset 0 0 0 2px $grey-lt-300;\n\n &:hover,\n &:active,\n &.zeroclipboard-is-hover,\n &.zeroclipboard-is-active {\n color: darken($link-color, 4%);\n text-decoration: none;\n background-color: transparent;\n box-shadow: inset 0 0 0 3px $grey-lt-300;\n }\n\n &:focus {\n text-decoration: none;\n outline: none;\n box-shadow:\n inset 0 0 0 2px $grey-dk-100,\n 0 0 0 3px rgba(blue, 0.25);\n }\n\n &:focus:hover,\n &.selected:focus {\n box-shadow: inset 0 0 0 2px $grey-dk-100;\n }\n}\n\n.btn-primary {\n @include btn-color($white, $btn-primary-color);\n}\n\n.btn-purple {\n @include btn-color($white, $purple-100);\n}\n\n.btn-blue {\n @include btn-color($white, $blue-200);\n}\n\n.btn-green {\n @include btn-color($white, $green-300);\n}\n\n.btn-reset {\n background: none;\n border: none;\n margin: 0;\n text-align: inherit;\n font: inherit;\n border-radius: 0;\n appearance: none;\n}\n","// Colored button\n\n@mixin btn-color($fg, $bg) {\n color: $fg;\n background-color: darken($bg, 2%);\n background-image: linear-gradient(lighten($bg, 5%), darken($bg, 2%));\n box-shadow:\n 0 1px 3px rgba(0, 0, 0, 0.25),\n 0 4px 10px rgba(0, 0, 0, 0.12);\n\n &:hover,\n &.zeroclipboard-is-hover {\n color: $fg;\n background-color: darken($bg, 4%);\n background-image: linear-gradient((lighten($bg, 2%), darken($bg, 4%)));\n }\n\n &:active,\n &.selected,\n &.zeroclipboard-is-active {\n background-color: darken($bg, 5%);\n background-image: none;\n box-shadow: inset 0 2px 4px rgba(0, 0, 0, 0.15);\n }\n\n &.selected:hover {\n background-color: darken($bg, 10%);\n }\n}\n","// Search input and autocomplete\n\n.search {\n position: relative;\n z-index: 2;\n flex-grow: 1;\n height: $sp-10;\n padding: $sp-2;\n transition: padding linear #{$transition-duration * 0.5};\n\n @include mq(md) {\n position: relative !important;\n width: auto !important;\n height: 100% !important;\n padding: 0;\n transition: none;\n }\n}\n\n.search-input-wrap {\n position: relative;\n z-index: 1;\n height: $sp-8;\n overflow: hidden;\n border-radius: $border-radius;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n transition: height linear #{$transition-duration * 0.5};\n\n @include mq(md) {\n position: absolute;\n width: 100%;\n max-width: $search-results-width;\n height: 100% !important;\n border-radius: 0;\n box-shadow: none;\n transition: width ease $transition-duration;\n }\n}\n\n.search-input {\n position: absolute;\n width: 100%;\n height: 100%;\n padding: $sp-2 $gutter-spacing-sm $sp-2 #{$gutter-spacing-sm + $sp-5};\n font-size: 1rem;\n color: $body-text-color;\n background-color: $search-background-color;\n border-top: 0;\n border-right: 0;\n border-bottom: 0;\n border-left: 0;\n border-radius: 0;\n\n @include mq(md) {\n padding: $sp-2 $gutter-spacing-sm $sp-2 #{$gutter-spacing + $sp-5};\n font-size: 0.875rem;\n background-color: $body-background-color;\n transition: padding-left linear #{$transition-duration * 0.5};\n }\n\n &:focus {\n outline: 2px solid $link-color;\n outline-offset: -2px;\n\n + .search-label .search-icon {\n color: $link-color;\n }\n }\n}\n\n.search-label {\n position: absolute;\n display: flex;\n height: 100%;\n padding-left: $gutter-spacing-sm;\n\n @include mq(md) {\n padding-left: $gutter-spacing;\n transition: padding-left linear #{$transition-duration * 0.5};\n }\n\n .search-icon {\n width: #{$sp-4 * 1.2};\n height: #{$sp-4 * 1.2};\n align-self: center;\n color: $grey-dk-000;\n }\n}\n\n.search-results {\n position: absolute;\n left: 0;\n display: none;\n width: 100%;\n max-height: calc(100% - #{$sp-10});\n overflow-y: auto;\n background-color: $search-background-color;\n border-bottom-right-radius: $border-radius;\n border-bottom-left-radius: $border-radius;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n\n @include mq(md) {\n top: 100%;\n width: $search-results-width;\n max-height: calc(100vh - 200%) !important;\n }\n}\n\n.search-results-list {\n padding-left: 0;\n margin-bottom: $sp-1;\n list-style: none;\n @include fs-4;\n\n @include mq(md) {\n @include fs-3;\n }\n}\n\n.search-results-list-item {\n padding: 0;\n margin: 0;\n}\n\n.search-result {\n display: block;\n padding: $sp-1 $sp-3;\n\n &:hover,\n &.active {\n background-color: $feedback-color;\n }\n}\n\n.search-result-title {\n display: block;\n padding-top: $sp-2;\n padding-bottom: $sp-2;\n\n @include mq(sm) {\n display: inline-block;\n width: 40%;\n padding-right: $sp-2;\n vertical-align: top;\n }\n}\n\n.search-result-doc {\n display: flex;\n align-items: center;\n word-wrap: break-word;\n\n &.search-result-doc-parent {\n opacity: 0.5;\n @include fs-3;\n\n @include mq(md) {\n @include fs-2;\n }\n }\n\n .search-result-icon {\n width: $sp-4;\n height: $sp-4;\n margin-right: $sp-2;\n color: $link-color;\n flex-shrink: 0;\n }\n\n .search-result-doc-title {\n overflow: auto;\n }\n}\n\n.search-result-section {\n margin-left: #{$sp-4 + $sp-2};\n word-wrap: break-word;\n}\n\n.search-result-rel-url {\n display: block;\n margin-left: #{$sp-4 + $sp-2};\n overflow: hidden;\n color: $search-result-preview-color;\n text-overflow: ellipsis;\n white-space: nowrap;\n @include fs-1;\n}\n\n.search-result-previews {\n display: block;\n padding-top: $sp-2;\n padding-bottom: $sp-2;\n padding-left: $sp-4;\n margin-left: $sp-2;\n color: $search-result-preview-color;\n word-wrap: break-word;\n border-left: $border;\n border-left-color: $border-color;\n @include fs-2;\n\n @include mq(sm) {\n display: inline-block;\n width: 60%;\n padding-left: $sp-2;\n margin-left: 0;\n vertical-align: top;\n }\n}\n\n.search-result-preview + .search-result-preview {\n margin-top: $sp-1;\n}\n\n.search-result-highlight {\n font-weight: bold;\n}\n\n.search-no-result {\n padding: $sp-2 $sp-3;\n @include fs-3;\n}\n\n.search-button {\n position: fixed;\n right: $sp-4;\n bottom: $sp-4;\n display: flex;\n width: $sp-9;\n height: $sp-9;\n background-color: $search-background-color;\n border: 1px solid rgba($link-color, 0.3);\n border-radius: #{$sp-9 * 0.5};\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n align-items: center;\n justify-content: center;\n}\n\n.search-overlay {\n position: fixed;\n top: 0;\n left: 0;\n z-index: 1;\n width: 0;\n height: 0;\n background-color: rgba(0, 0, 0, 0.3);\n opacity: 0;\n transition:\n opacity ease $transition-duration,\n width 0s $transition-duration,\n height 0s $transition-duration;\n}\n\n.search-active {\n .search {\n position: fixed;\n top: 0;\n left: 0;\n width: 100%;\n height: 100%;\n padding: 0;\n }\n\n .search-input-wrap {\n height: $sp-10;\n border-radius: 0;\n\n @include mq(md) {\n width: $search-results-width;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n }\n }\n\n .search-input {\n background-color: $search-background-color;\n\n @include mq(md) {\n padding-left: 2.3rem;\n }\n }\n\n .search-label {\n @include mq(md) {\n padding-left: 0.6rem;\n }\n }\n\n .search-results {\n display: block;\n }\n\n .search-overlay {\n width: 100%;\n height: 100%;\n opacity: 1;\n transition:\n opacity ease $transition-duration,\n width 0s,\n height 0s;\n }\n\n @include mq(md) {\n .main {\n position: fixed;\n right: 0;\n left: 0;\n }\n }\n\n .main-header {\n padding-top: $sp-10;\n\n @include mq(md) {\n padding-top: 0;\n }\n }\n}\n","// Tables\n// stylelint-disable max-nesting-depth, selector-no-type, selector-max-type\n\n.table-wrapper {\n display: block;\n width: 100%;\n max-width: 100%;\n margin-bottom: $sp-5;\n overflow-x: auto;\n border-radius: $border-radius;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n}\n\ntable {\n display: table;\n min-width: 100%;\n border-collapse: separate;\n}\n\nth,\ntd {\n min-width: 7.5rem;\n padding: $sp-2 $sp-3;\n background-color: $table-background-color;\n border-bottom: $border rgba($border-color, 0.5);\n border-left: $border $border-color;\n\n @include fs-3;\n\n &:first-of-type {\n border-left: 0;\n }\n}\n\ntbody {\n tr {\n &:last-of-type {\n th,\n td {\n border-bottom: 0;\n }\n\n td {\n padding-bottom: $sp-3;\n }\n }\n }\n}\n\nthead {\n th {\n border-bottom: $border $border-color;\n }\n}\n","// Code and syntax highlighting\n// stylelint-disable selector-no-qualifying-type, declaration-block-semicolon-newline-after,declaration-block-single-line-max-declarations, selector-no-type, selector-max-type, scss/comment-no-empty\n\n// {% raw %}\n\n// This instruction applies to all queues not within 'pre' or 'figure', avoiding 'code' generated by the highlight.\n:not(pre, figure) {\n & > code {\n padding: 0.2em 0.15em;\n font-weight: 400;\n background-color: $code-background-color;\n border: $border $border-color;\n border-radius: $border-radius;\n }\n}\n\n// Avoid appearance of dark border around visited code links in Safari\na:visited code {\n border-color: $border-color;\n}\n\n// Content structure for highlighted code blocks using fences or Liquid\n//\n// ```[LANG]...```, no kramdown line_numbers:\n// div.[language-LANG.]highlighter-rouge > div.highlight > pre.highlight > code\n//\n// ```[LANG]...```, kramdown line_numbers = true:\n// div.[language-LANG.]highlighter-rouge > div.highlight > pre.highlight > code\n// > div.table-wrapper > table.rouge-table > tbody > tr\n// > td.rouge-gutter.gl > pre.lineno\n// | td.rouge-code > pre\n//\n// {% highlight LANG %}...{% endhighlight %}:\n// figure.highlight > pre > code.language-LANG\n//\n// {% highlight LANG linenos %}...{% endhighlight %}:\n// figure.highlight > pre > code.language-LANG\n// > div.table-wrapper > table.rouge-table > tbody > tr\n// > td.gutter.gl > pre.lineno\n// | td.code > pre\n//\n// ----...---- (AsciiDoc)\n// div.listingblock > div.content > pre.rouge.highlight\n//\n// fix_linenos removes the outermost pre when it encloses table.rouge-table\n//\n// See docs/index-test.md for some tests.\n//\n// No kramdown line_numbers: fences and Liquid highlighting look the same.\n// Kramdown line_numbers = true: fences have a wider gutter than with Liquid?\n\n// ```[LANG]...```\n// or in AsciiDoc:\n//\n// ----\n// ...\n// ----\n\n// the code may appear with 3 different types:\n// container \\ case: default case, code with line number, code with html rendering\n// top level: div.highlighter-rouge, figure.highlight, figure.highlight\n// second level: div.highlight, div.table-wrapper, pre.highlight\n// third level: pre.highlight, td.code, absent\n// last level: code, pre, code (optionality)\n// highlighter level: span, span, span\n// the spacing are only in the second level for case 1, 3 and in the third level for case 2\n// in AsciiDoc, there is a parent container that contains optionally a title and the content.\n\n// select top level container\ndiv.highlighter-rouge,\ndiv.listingblock > div.content,\nfigure.highlight {\n margin-top: 0;\n margin-bottom: $sp-3;\n background-color: $code-background-color;\n border-radius: $border-radius;\n box-shadow: none;\n -webkit-overflow-scrolling: touch;\n position: relative;\n padding: 0;\n\n // copy button (or other button)\n // the button appear only when there is a hover on the code or focus on button\n > button {\n width: $sp-3;\n opacity: 0;\n position: absolute;\n top: 0;\n right: 0;\n padding: $sp-3;\n border: none;\n background: none;\n color: $body-text-color;\n box-sizing: content-box;\n\n svg {\n fill: $body-text-color;\n }\n\n &:active {\n text-decoration: none;\n outline: none;\n opacity: 1;\n }\n\n &:focus {\n opacity: 1;\n outline: 2px solid $link-color;\n }\n }\n\n // the button can be seen by doing a simple hover in the code, there is no need to go over the location of the button\n &:hover {\n > button {\n cursor: copy;\n opacity: 1;\n }\n }\n}\n\n// setting the spacing and scrollbar on the second level for the first case\n// remove all space on the second and third level\n// this is a mixin to accommodate for the slightly different structures generated via Markdown vs AsciiDoc\n@mixin scroll-and-spacing($code-div, $pre-select) {\n #{$code-div} {\n overflow-x: auto;\n padding: $sp-3;\n margin: 0;\n border: 1px solid $body-text-color;\n border-radius: $border-radius;\n }\n\n #{$pre-select},\n code {\n padding: 0;\n margin: 0;\n border: 0;\n }\n}\n\n// for Markdown\ndiv.highlighter-rouge {\n @include scroll-and-spacing(\"div.highlight\", \"pre.highlight\");\n}\n\n// for AsciiDoc. we also need to fix the margins for its parent container.\ndiv.listingblock {\n margin-top: 0;\n margin-bottom: $sp-3;\n\n @include scroll-and-spacing(\"div.content\", \"div.content > pre\");\n}\n\n// {% highlight LANG %}...{% endhighlight %},\n// {% highlight LANG linenos %}...{% endhighlight %}:\n\n// setting the spacing and scrollbar on the second level for the thirt case\n// the css rule are apply only to the last code enviroment\n// setting the scroolbar\nfigure.highlight {\n pre,\n :not(pre) > code {\n overflow-x: auto;\n padding: $sp-3;\n margin: 0;\n border: 1px solid $body-text-color;\n border-radius: $border-radius;\n }\n}\n\n// ```[LANG]...```, kramdown line_numbers = true,\n// {% highlight LANG linenos %}...{% endhighlight %}:\n\n// setting the spacing and scrollbar on the thirt level for the second case\n.highlight .table-wrapper {\n padding: $sp-3 0;\n margin: 0;\n border: 0;\n box-shadow: none;\n\n td,\n pre {\n min-width: 0;\n padding: 0;\n background-color: $code-background-color;\n border: 0;\n\n @include fs-2;\n }\n\n td.gl {\n width: 1em;\n padding-right: $sp-3;\n padding-left: $sp-3;\n }\n\n pre {\n margin: 0;\n line-height: 2;\n }\n}\n\n// Code examples: html render of a code\n.code-example,\n.listingblock > .title {\n padding: $sp-3;\n margin-bottom: $sp-3;\n overflow: auto;\n border: 1px solid $border-color;\n border-radius: $border-radius;\n\n + .highlighter-rouge,\n + .sectionbody .listingblock,\n + .content,\n + figure.highlight {\n position: relative;\n margin-top: -$sp-4;\n border-right: 1px solid $border-color;\n border-bottom: 1px solid $border-color;\n border-left: 1px solid $border-color;\n border-top-left-radius: 0;\n border-top-right-radius: 0;\n }\n}\n\n// Mermaid diagram code blocks should be left unstyled.\ncode.language-mermaid {\n padding: 0;\n background-color: inherit;\n border: 0;\n}\n\n// Override OneDarkJekyll Colors for Code Blocks\n.highlight,\npre.highlight {\n background: $code-background-color; // Code Background\n // For Backwards Compatibility Before $code-linenumber-color was added\n @if variable-exists(code-linenumber-color) {\n color: $code-linenumber-color; // Code Line Numbers\n } @else {\n color: $body-text-color; // Code Line Numbers\n }\n}\n\n// Override OneDarkJekyll Colors for Code Blocks\n.highlight pre {\n background: $code-background-color; // Code Background\n}\n\n// {% endraw %}\n","// Utility classes for colors\n\n// Text colors\n\n.text-grey-dk-000 {\n color: $grey-dk-000 !important;\n}\n\n.text-grey-dk-100 {\n color: $grey-dk-100 !important;\n}\n\n.text-grey-dk-200 {\n color: $grey-dk-200 !important;\n}\n\n.text-grey-dk-250 {\n color: $grey-dk-250 !important;\n}\n\n.text-grey-dk-300 {\n color: $grey-dk-300 !important;\n}\n\n.text-grey-lt-000 {\n color: $grey-lt-000 !important;\n}\n\n.text-grey-lt-100 {\n color: $grey-lt-100 !important;\n}\n\n.text-grey-lt-200 {\n color: $grey-lt-200 !important;\n}\n\n.text-grey-lt-300 {\n color: $grey-lt-300 !important;\n}\n\n.text-blue-000 {\n color: $blue-000 !important;\n}\n\n.text-blue-100 {\n color: $blue-100 !important;\n}\n\n.text-blue-200 {\n color: $blue-200 !important;\n}\n\n.text-blue-300 {\n color: $blue-300 !important;\n}\n\n.text-green-000 {\n color: $green-000 !important;\n}\n\n.text-green-100 {\n color: $green-100 !important;\n}\n\n.text-green-200 {\n color: $green-200 !important;\n}\n\n.text-green-300 {\n color: $green-300 !important;\n}\n\n.text-purple-000 {\n color: $purple-000 !important;\n}\n\n.text-purple-100 {\n color: $purple-100 !important;\n}\n\n.text-purple-200 {\n color: $purple-200 !important;\n}\n\n.text-purple-300 {\n color: $purple-300 !important;\n}\n\n.text-yellow-000 {\n color: $yellow-000 !important;\n}\n\n.text-yellow-100 {\n color: $yellow-100 !important;\n}\n\n.text-yellow-200 {\n color: $yellow-200 !important;\n}\n\n.text-yellow-300 {\n color: $yellow-300 !important;\n}\n\n.text-red-000 {\n color: $red-000 !important;\n}\n\n.text-red-100 {\n color: $red-100 !important;\n}\n\n.text-red-200 {\n color: $red-200 !important;\n}\n\n.text-red-300 {\n color: $red-300 !important;\n}\n\n// Background colors\n\n.bg-grey-dk-000 {\n background-color: $grey-dk-000 !important;\n}\n\n.bg-grey-dk-100 {\n background-color: $grey-dk-100 !important;\n}\n\n.bg-grey-dk-200 {\n background-color: $grey-dk-200 !important;\n}\n\n.bg-grey-dk-250 {\n background-color: $grey-dk-250 !important;\n}\n\n.bg-grey-dk-300 {\n background-color: $grey-dk-300 !important;\n}\n\n.bg-grey-lt-000 {\n background-color: $grey-lt-000 !important;\n}\n\n.bg-grey-lt-100 {\n background-color: $grey-lt-100 !important;\n}\n\n.bg-grey-lt-200 {\n background-color: $grey-lt-200 !important;\n}\n\n.bg-grey-lt-300 {\n background-color: $grey-lt-300 !important;\n}\n\n.bg-blue-000 {\n background-color: $blue-000 !important;\n}\n\n.bg-blue-100 {\n background-color: $blue-100 !important;\n}\n\n.bg-blue-200 {\n background-color: $blue-200 !important;\n}\n\n.bg-blue-300 {\n background-color: $blue-300 !important;\n}\n\n.bg-green-000 {\n background-color: $green-000 !important;\n}\n\n.bg-green-100 {\n background-color: $green-100 !important;\n}\n\n.bg-green-200 {\n background-color: $green-200 !important;\n}\n\n.bg-green-300 {\n background-color: $green-300 !important;\n}\n\n.bg-purple-000 {\n background-color: $purple-000 !important;\n}\n\n.bg-purple-100 {\n background-color: $purple-100 !important;\n}\n\n.bg-purple-200 {\n background-color: $purple-200 !important;\n}\n\n.bg-purple-300 {\n background-color: $purple-300 !important;\n}\n\n.bg-yellow-000 {\n background-color: $yellow-000 !important;\n}\n\n.bg-yellow-100 {\n background-color: $yellow-100 !important;\n}\n\n.bg-yellow-200 {\n background-color: $yellow-200 !important;\n}\n\n.bg-yellow-300 {\n background-color: $yellow-300 !important;\n}\n\n.bg-red-000 {\n background-color: $red-000 !important;\n}\n\n.bg-red-100 {\n background-color: $red-100 !important;\n}\n\n.bg-red-200 {\n background-color: $red-200 !important;\n}\n\n.bg-red-300 {\n background-color: $red-300 !important;\n}\n","// Utility classes for layout\n\n// Display\n\n.d-block {\n display: block !important;\n}\n\n.d-flex {\n display: flex !important;\n}\n\n.d-inline {\n display: inline !important;\n}\n\n.d-inline-block {\n display: inline-block !important;\n}\n\n.d-none {\n display: none !important;\n}\n\n// Screenreader-only\n\n.sr-only {\n position: absolute;\n width: 1px;\n height: 1px;\n padding: 0;\n margin: -1px;\n overflow: hidden;\n clip: rect(0, 0, 0, 0);\n white-space: nowrap;\n border-width: 0;\n}\n\n@each $media-query in map-keys($media-queries) {\n @for $i from 1 through length($spacers) {\n @include mq($media-query) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .d-sm-block, .d-md-none, .d-lg-inline\n .d-#{$media-query}-block {\n display: block !important;\n }\n .d-#{$media-query}-flex {\n display: flex !important;\n }\n .d-#{$media-query}-inline {\n display: inline !important;\n }\n .d-#{$media-query}-inline-block {\n display: inline-block !important;\n }\n .d-#{$media-query}-none {\n display: none !important;\n }\n }\n }\n}\n\n// Horizontal alignment\n\n.float-left {\n float: left !important;\n}\n\n.float-right {\n float: right !important;\n}\n\n.flex-justify-start {\n justify-content: flex-start !important;\n}\n\n.flex-justify-end {\n justify-content: flex-end !important;\n}\n\n.flex-justify-between {\n justify-content: space-between !important;\n}\n\n.flex-justify-around {\n justify-content: space-around !important;\n}\n\n// Vertical alignment\n\n.v-align-baseline {\n vertical-align: baseline !important;\n}\n\n.v-align-bottom {\n vertical-align: bottom !important;\n}\n\n.v-align-middle {\n vertical-align: middle !important;\n}\n\n.v-align-text-bottom {\n vertical-align: text-bottom !important;\n}\n\n.v-align-text-top {\n vertical-align: text-top !important;\n}\n\n.v-align-top {\n vertical-align: top !important;\n}\n","// Utility classes for typography\n\n.fs-1 {\n @include fs-1;\n}\n\n.fs-2 {\n @include fs-2;\n}\n\n.fs-3 {\n @include fs-3;\n}\n\n.fs-4 {\n @include fs-4;\n}\n\n.fs-5 {\n @include fs-5;\n}\n\n.fs-6 {\n @include fs-6;\n}\n\n.fs-7 {\n @include fs-7;\n}\n\n.fs-8 {\n @include fs-8;\n}\n\n.fs-9 {\n @include fs-9;\n}\n\n.fs-10 {\n @include fs-10;\n}\n\n.fw-300 {\n font-weight: 300 !important;\n}\n\n.fw-400 {\n font-weight: 400 !important;\n}\n\n.fw-500 {\n font-weight: 500 !important;\n}\n\n.fw-700 {\n font-weight: 700 !important;\n}\n\n.lh-0 {\n line-height: 0 !important;\n}\n\n.lh-default {\n line-height: $body-line-height;\n}\n\n.lh-tight {\n line-height: $body-heading-line-height;\n}\n\n.ls-5 {\n letter-spacing: 0.05em !important;\n}\n\n.ls-10 {\n letter-spacing: 0.1em !important;\n}\n\n.ls-0 {\n letter-spacing: 0 !important;\n}\n\n.text-uppercase {\n text-transform: uppercase !important;\n}\n","// Utility classes for lists\n\n// stylelint-disable selector-max-type\n\n.list-style-none {\n padding: 0 !important;\n margin: 0 !important;\n list-style: none !important;\n\n li {\n &::before {\n display: none !important;\n }\n }\n}\n","// Utility classes for margins and padding\n\n// stylelint-disable block-opening-brace-space-after, block-opening-brace-space-before\n\n// Margin spacer utilities\n\n.mx-auto {\n margin-right: auto !important;\n margin-left: auto !important;\n}\n\n@for $i from 1 through length($spacers) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .m-0, .m-1, .m-2...\n .m-#{$scale} {\n margin: #{$size} !important;\n }\n .mt-#{$scale} {\n margin-top: #{$size} !important;\n }\n .mr-#{$scale} {\n margin-right: #{$size} !important;\n }\n .mb-#{$scale} {\n margin-bottom: #{$size} !important;\n }\n .ml-#{$scale} {\n margin-left: #{$size} !important;\n }\n\n .mx-#{$scale} {\n margin-right: #{$size} !important;\n margin-left: #{$size} !important;\n }\n\n .my-#{$scale} {\n margin-top: #{$size} !important;\n margin-bottom: #{$size} !important;\n }\n\n .mxn-#{$scale} {\n margin-right: -#{$size} !important;\n margin-left: -#{$size} !important;\n }\n .mx-#{$scale}-auto {\n margin-right: auto !important;\n margin-left: auto !important;\n }\n}\n\n@each $media-query in map-keys($media-queries) {\n @for $i from 1 through length($spacers) {\n @include mq($media-query) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .m-sm-0, .m-md-1, .m-lg-2...\n .m-#{$media-query}-#{$scale} {\n margin: #{$size} !important;\n }\n .mt-#{$media-query}-#{$scale} {\n margin-top: #{$size} !important;\n }\n .mr-#{$media-query}-#{$scale} {\n margin-right: #{$size} !important;\n }\n .mb-#{$media-query}-#{$scale} {\n margin-bottom: #{$size} !important;\n }\n .ml-#{$media-query}-#{$scale} {\n margin-left: #{$size} !important;\n }\n\n .mx-#{$media-query}-#{$scale} {\n margin-right: #{$size} !important;\n margin-left: #{$size} !important;\n }\n\n .my-#{$media-query}-#{$scale} {\n margin-top: #{$size} !important;\n margin-bottom: #{$size} !important;\n }\n\n .mxn-#{$media-query}-#{$scale} {\n margin-right: -#{$size} !important;\n margin-left: -#{$size} !important;\n }\n }\n }\n}\n\n// Padding spacer utilities\n\n@for $i from 1 through length($spacers) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .p-0, .p-1, .p-2...\n .p-#{$scale} {\n padding: #{$size} !important;\n }\n .pt-#{$scale} {\n padding-top: #{$size} !important;\n }\n .pr-#{$scale} {\n padding-right: #{$size} !important;\n }\n .pb-#{$scale} {\n padding-bottom: #{$size} !important;\n }\n .pl-#{$scale} {\n padding-left: #{$size} !important;\n }\n\n .px-#{$scale} {\n padding-right: #{$size} !important;\n padding-left: #{$size} !important;\n }\n\n .py-#{$scale} {\n padding-top: #{$size} !important;\n padding-bottom: #{$size} !important;\n }\n}\n\n@each $media-query in map-keys($media-queries) {\n @include mq($media-query) {\n @for $i from 1 through length($spacers) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .p-sm-0, .p-md-1, .p-lg-2...\n .p-#{$media-query}-#{$scale} {\n padding: #{$size} !important;\n }\n .pt-#{$media-query}-#{$scale} {\n padding-top: #{$size} !important;\n }\n .pr-#{$media-query}-#{$scale} {\n padding-right: #{$size} !important;\n }\n .pb-#{$media-query}-#{$scale} {\n padding-bottom: #{$size} !important;\n }\n .pl-#{$media-query}-#{$scale} {\n padding-left: #{$size} !important;\n }\n\n .px-#{$media-query}-#{$scale} {\n padding-right: #{$size} !important;\n padding-left: #{$size} !important;\n }\n\n .py-#{$media-query}-#{$scale} {\n padding-top: #{$size} !important;\n padding-bottom: #{$size} !important;\n }\n }\n }\n}\n","// stylelint-disable selector-max-specificity, selector-max-id, selector-max-type, selector-no-qualifying-type\n\n@media print {\n .site-footer,\n .site-button,\n #edit-this-page,\n #back-to-top,\n .site-nav,\n .main-header {\n display: none !important;\n }\n\n hr {\n margin-top: 1rem;\n margin-bottom: 1rem;\n }\n\n .side-bar {\n width: 100%;\n height: auto;\n border-right: 0 !important;\n }\n\n .site-header {\n border-bottom: 1px solid $border-color;\n }\n\n .site-title {\n font-size: 1rem !important;\n font-weight: 700 !important;\n }\n\n .text-small {\n font-size: 8pt !important;\n }\n\n pre.highlight {\n border: 1px solid $border-color;\n }\n\n .main {\n max-width: none;\n margin-left: 0;\n }\n}\n","// Skipnav\n// Skip to main content\n\na.skip-to-main {\n left: -999px;\n position: absolute;\n top: auto;\n width: 1px;\n height: 1px;\n overflow: hidden;\n z-index: -999;\n}\n\na.skip-to-main:focus,\na.skip-to-main:active {\n color: $link-color;\n background-color: $body-background-color;\n left: auto;\n top: auto;\n width: 30%;\n height: auto;\n overflow: auto;\n margin: 10px 35%;\n padding: 5px;\n border-radius: 15px;\n border: 4px solid $btn-primary-color;\n text-align: center;\n font-size: 1.2em;\n z-index: 999;\n}\n","\n@import \"./support/support\";\n@import \"./custom/setup\";\n@import \"./color_schemes/light\";\n\n@import \"./modules\";\ndiv.opaque {\n background-color: $body-background-color;\n}\n\np.tip, blockquote.tip {\n border: 1px $green-000 solid;\n border-left: $border-radius solid $green-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n \n &::before {\n color: $green-300;\n content: \"Tip\";\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n \n > .tip-title {\n color: $green-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\np.tip-title, blockquote.tip-title {\n border: 1px $green-000 solid;\n border-left: $border-radius solid $green-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n > p:first-child {\n margin-top: 0;\n margin-bottom: 0;\n color: $green-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\nblockquote.tip {\n margin-left: 0;\n margin-right: 0;\n\n > p:first-child {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\nblockquote.tip-title {\n margin-left: 0;\n margin-right: 0;\n\n > p:nth-child(2) {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\n\n\np.note, blockquote.note {\n border: 1px $blue-000 solid;\n border-left: $border-radius solid $blue-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n \n &::before {\n color: $blue-300;\n content: \"Note\";\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n \n > .note-title {\n color: $blue-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\np.note-title, blockquote.note-title {\n border: 1px $blue-000 solid;\n border-left: $border-radius solid $blue-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n > p:first-child {\n margin-top: 0;\n margin-bottom: 0;\n color: $blue-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\nblockquote.note {\n margin-left: 0;\n margin-right: 0;\n\n > p:first-child {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\nblockquote.note-title {\n margin-left: 0;\n margin-right: 0;\n\n > p:nth-child(2) {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\n\n\np.warning, blockquote.warning {\n border: 1px $yellow-000 solid;\n border-left: $border-radius solid $yellow-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n \n &::before {\n color: $yellow-300;\n content: \"Warning\";\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n \n > .warning-title {\n color: $yellow-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\np.warning-title, blockquote.warning-title {\n border: 1px $yellow-000 solid;\n border-left: $border-radius solid $yellow-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n > p:first-child {\n margin-top: 0;\n margin-bottom: 0;\n color: $yellow-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\nblockquote.warning {\n margin-left: 0;\n margin-right: 0;\n\n > p:first-child {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\nblockquote.warning-title {\n margin-left: 0;\n margin-right: 0;\n\n > p:nth-child(2) {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\n\n@import \"./custom/custom\";\n\n\n"],"file":"just-the-docs-light.css"} \ No newline at end of file +{"version":3,"sourceRoot":"","sources":["../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/vendor/accessible-pygments/github-light.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/vendor/normalize.scss/normalize.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/base.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/color_schemes/light.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/support/mixins/_typography.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/support/mixins/_layout.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/support/_variables.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/layout.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/content.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/navigation.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/typography.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/labels.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/buttons.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/support/mixins/_buttons.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/search.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/tables.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/code.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/utilities/_colors.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/utilities/_layout.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/utilities/_typography.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/utilities/_lists.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/utilities/_spacing.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/print.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/skiptomain.scss","just-the-docs-light.scss"],"names":[],"mappings":";AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAUA;EAAkB;;;AAClB;EAAgB;EAAiB;AACjC;EAAkB;EAAiB;AACnC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAkB;EAAiB;AACnC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAqB;AACtC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAoB;AACrC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAgB;EAAiB;AACjC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AChFlC;AAEA;AAAA;AAGA;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAAA;AAKA;EACE;EACA;EACA;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;EACA;;;AAGF;AAAA;AAAA;AAIA;AAAA;EAEE;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;AAAA;EAGE;EACA;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;EAEE;EACA;EACA;EACA;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAAA;AAKA;AAAA;AAAA;AAAA;AAAA;EAKE;EACA;EACA;EACA;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;AAEE;EACA;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;AAEE;EACA;;;AAGF;AAAA;AAAA;AAIA;AAAA;AAAA;AAAA;EAIE;;;AAGF;AAAA;AAAA;AAIA;AAAA;AAAA;AAAA;EAIE;EACA;;;AAGF;AAAA;AAAA;AAIA;AAAA;AAAA;AAAA;EAIE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAOA;EACE;EACA;EACA;EACA;EACA;EACA;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;EAEE;EACA;;;AAGF;AAAA;AAAA;AAIA;AAAA;EAEE;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AC1VF;EACE,cCJa;;;ADOf;EACE;;;AAGF;EACE;;AEmBA;EACE;;AClBA;EHHJ;IEyBI;;;;AFnBJ;EACE,aIfiB;EJgBjB;EACA,aIbiB;EJcjB,OIUY;EJTZ,kBIOM;EJNN;;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAYE;;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAOE;EACA;EACA;EACA,aI1CyB;EJ2CzB,OIlBY;;;AJqBd;EACE;EACA;;;AAGF;EACE,OItBW;EJuBX;;;AAGF;EACE;EACA,uBI/BY;EJgCZ;;AAEA;EACE;;;AAIJ;EACE,aIvEiB;EJwEjB;EACA,aIvEiB;;;AJ0EnB;AAAA;EAEE;;;AAGF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;EACA;EACA,kBI/DY;EJgEZ;;;AAIF;EACE;EAGA;EACA;EACA;EACA;;;AK7GF;EACE;EACA;EACA;EACA,kBD6BY;;ADrBV;EEZJ;IAOI;IACA;IACA,ODwFW;ICvFX;IACA;IACA;;;AFAA;EEZJ;IAgBI;IACA,WD+EQ;;;ADpFR;EEQF;IAEI,aD2ES;;;ADrFX;EEQF;IAQI;;;AAOF;EACE;EACA,kBDJQ;;ADrBV;EEuBA;IAKI;IACA,kBDdA;;;ACiBF;EACE;;AFjCJ;EEgCE;IAII;;;;AAOV;EACE;;AF5CE;EE2CJ;IAII;IACA,WDyCY;;;;ACrChB;EACE,aDaK;ECZL,gBDYK;EDvDL,eCuDK;EDtDL,cCsDK;;ADlEH;EEoDJ;IFrCI,eCqDG;IDpDH,cCoDG;;;ADpEH;EEoDJ;IAOI,aDSG;ICRH,gBDQG;;;;ACJP;EACE;EACA;;AFlEE;EEgEJ;IAKI;IACA;IACA,QDmBY;;;;ACfhB;AAAA;AAAA;EAGE;;AF9EE;EE2EJ;AAAA;AAAA;IAMI,ODGQ;;;;ACCZ;EACE;;AAEA;EACE;;AFzFA;EEqFJ;IAQI;IACA,aDxBG;ICyBH,gBD7BG;IC8BH;IACA;;;;AAIJ;EACE;EACA,YDbc;ECcd;;AFxGE;EEqGJ;IAMI,QDjBY;ICkBZ,YDlBY;ICmBZ;;;;AAIJ;EACE;EACA;EACA;EACA;EACA,aDrDK;ECsDL,gBDtDK;ECuDL,ODpGY;EDTZ,eCuDK;EDtDL,cCsDK;;ADlEH;EEiHJ;IFlGI,eCqDG;IDpDH,cCoDG;;;AF/BL;EACE;;ACtCA;EEiHJ;IHvEI;IACA,aEhDuB;;;ADKvB;EEiHJ;IAcI,aD/DG;ICgEH,gBDhEG;;;;AC+EP;EACE;EACA;EACA,SDhFK;ECiFL;;;AFnJE;EEuJF;IACE;;;AAIJ;EACE;;;AAQF;EACE;;;AAOF;EACE;EACA;EACA;EACA,aD/GK;ECgHL,gBDhHK;EDvDL,eCuDK;EDtDL,cCsDK;;ADlEH;EE6KJ;IF9JI,eCqDG;IDpDH,cCoDG;;;AFvEL;EACE;;ACEA;EE6KJ;IH3KI;;;ACFA;EE6KJ;IAYI;IACA;;;;AAIJ;EACE,OD5HK;EC6HL,QD7HK;EC8HL,ODxKW;;;AElCb;EACE,aFEoB;;AEApB;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAOE;;AAGF;EACE;EACA;;AAGF;AAAA;EAEE;;AAIA;EACE,YF+CC;;AE3CL;EACE;EACA;;AAEA;EACE;;AAEA;EACE;EACA;EACA;EACA,OFfM;EEgBN;EACA;;AJ1BN;EACE;;ACRA;EG2BE;IJfF;;;ACZA;EG2BE;IAUI;;;AAIJ;EACE;;AAGE;EACE;EACA;;AAOV;EACE;;AAGE;EACE;EACA;EACA,OF7CM;EE8CN;;AAMJ;EACE;;AAIJ;EACE;EACA;;AAKF;EACE;;AAGF;EACE;;AAGF;EACE;EACA;;AAGF;AAAA;EAEE;;AAGF;EACE;EACA;EACA;;AAEA;EACE;;AAIJ;EACE;EACA;EACA;;AAmBE;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EACE;;AASF;AAAA;AAAA;AAAA;AAAA;AAAA;EAEE;;AAKN;EACE;EACA;EACA,OFnFG;EEoFH;EACA,eFzFG;EE0FH,cF1FG;EE2FH;;AH1JA;EGmJF;IAUI;IACA;;;AAGF;EACE;EACA;EACA;EACA,OF5IO;EE6IP;;AAYF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EACE;;AAIJ;EACE;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAOE;EACA;EACA;;AAEA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAKE;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EACE;;AAIJ;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAWE,YF9JG;;;AG3EP;EACE;EACA;EACA;EACA;;AAEA;EACE;EACA;;ALoBF;EACE;;AClBA;EILF;IL2BE;;;ACtBA;EDOF;IACE;;;ACRA;EILF;ILiBE;;;AKPA;EACE;EACA,YH+DC;EG9DD,aHuDC;EGtDD,gBHsDC;EGrDD;EAEE,eH0DD;EGzDC,cHqDD;;ADlEH;EIKA;IAeI,YHgDD;IG/CC;IAEE,eH6CH;IG5CG,cH4CH;;;AGrCD;EACE,OHkCD;EGjCC,QHiCD;EGhCC;;AAGF;EACE;EACA;;AAGF;EAEE;EACA;;AASJ;EACE;EAEE;EAGF,OHUC;EGTD,QHSC;EGRD;EACA,OHtCO;;ADzBT;EIsDA;IAYI,OHED;IGDC,QHCD;IGAC;;;AAGF;EACE;;AAQA;EACE;;AAKN;EACE;EACA,cHvBC;EGwBD;;AAEA;EACE;;AAEA;EACE,OH9EI;;AGiFN;EACE,OHlFI;;AGwFR;EAEI;;AAMJ;EACE;;;AAMR;EACE;EACA;EACA;EACA;EACA;;ALhIA;EACE;;ACEA;EIwHJ;ILtHI;;;ACFA;EIwHJ;IASI;IACA,YHhEG;IGiEH;;EAEA;IACE;;;;AAMJ;EACE;;AAEA;EACE;;AAGE;EACE,OH3HG;;AG8HL;EACE,OH/HG;;;AGwIb;EACE;EACA;;ALtKA;EACE;;ACEA;EIiKJ;IL/JI;;;AKoKF;EACE;EACA;EACA;EACA;EACA;;AAGF;EACE;EACA;EACA;EACA;;AJlLA;EIiKJ;IAqBI,eHpHG;;;;ADlEH;EI4LJ;IAEI;;;;AAIJ;EACE;EACA,eHnIK;EGoIL;;;AAGF;EACE;;AL5MA;EACE;;ACEA;EIwMJ;ILtMI;;;AK0MF;EACE;;AAGF;EACE;EACA,cHlJG;EGmJH,aHnJG;EGoJH,OHpMU;EGqMV;;AAIA;EACE;;;ACrON;AAAA;EAEE;;ANoEA;AAAA;EACE;EACA,aElEuB;;ADKvB;EKXJ;AAAA;IN4EI;;;;AA5BF;AAAA;AAAA;EACE;;ACtCA;EKJJ;AAAA;AAAA;IN8CI;IACA,aEhDuB;;;;AFgCzB;AAAA;EACE;;AC5BA;EKEJ;AAAA;IN8BI;;;;AMzBJ;AAAA;EAEE;EACA;EACA;;ANdA;AAAA;EACE;;ACEA;EKOJ;AAAA;INLI;;;;AMcJ;EACE;;;ANVA;AAAA;EACE;;ACRA;EKoBJ;AAAA;INRI;;;;AAfF;AAAA;EACE;;ACEA;EKyBJ;AAAA;INvBI;;;;AALF;EACE;;ACEA;EK8BJ;IN5BI;;;;AMgCJ;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;ACvDF;AAAA;EAEE;EACA;EACA,cLoEK;EKnEL,aLmEK;EKlEL,OLiBM;EKhBN;EACA;EACA,kBL6BS;EK5BT;;APLA;AAAA;EACE;;ACEA;EMRJ;AAAA;IPUI;;;;AOKJ;EACE,kBL4BU;;;AKzBZ;EACE,kBLcW;;;AKXb;EACE,kBL4BQ;;;AKzBV;EACE,OLFY;EKGZ,kBLkBW;;;AMlDb;EACE;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA,ON2BW;EM1BX;EACA;EACA;EACA,kBTTkB;ESUlB;EACA,eNyEc;EMxEd,YACE;EAEF;;AAEA;EACE;EACA;EACA;;AAGF;EAEE;;AAGF;EAEE;;AAGF;EAIE;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;AAKA;EAEE;EACA;EACA;EACA;EACA;;;AAKN;EACE,ONnCW;EMoCX;EACA;;AAEA;EAIE;EACA;EACA;EACA;;AAGF;EACE;EACA;EACA,YACE;;AAIJ;EAEE;;;AAIJ;ECnGE,OP0BM;EOzBN;EACA;EACA,YACE;;AAGF;EAEE,OPiBI;EOhBJ;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;;ADgFJ;ECvGE,OP0BM;EOzBN;EACA;EACA,YACE;;AAGF;EAEE,OPiBI;EOhBJ;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;;ADoFJ;EC3GE,OP0BM;EOzBN;EACA;EACA,YACE;;AAGF;EAEE,OPiBI;EOhBJ;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;;ADwFJ;EC/GE,OP0BM;EOzBN;EACA;EACA,YACE;;AAGF;EAEE,OPiBI;EOhBJ;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;;AD4FJ;EACE;EACA;EACA;EACA;EACA;EACA;EACA;;;AE3HF;EACE;EACA;EACA;EACA,QRgFM;EQ/EN,SRuEK;EQtEL;;ATME;ESZJ;IASI;IACA;IACA;IACA;IACA;;;;AAIJ;EACE;EACA;EACA,QR8DK;EQ7DL;EACA,eRmEc;EQlEd,YACE;EAEF;;ATdE;ESKJ;IAYI;IACA;IACA,WRwEmB;IQvEnB;IACA;IACA;IACA;;;;AAIJ;EACE;EACA;EACA;EACA;EACA;EACA,ORhBY;EQiBZ,kBRnBM;EQoBN;EACA;EACA;EACA;EACA;;ATvCE;ES2BJ;IAeI;IACA;IACA,kBR7BI;IQ8BJ;;;AAGF;EACE;EACA;;AAEA;EACE,OR5BO;;;AQiCb;EACE;EACA;EACA;EACA,cRIK;;ADlEH;ES0DJ;IAOI,cRGG;IQFH;;;AAGF;EACE;EACA;EACA;EACA,ORzDU;;;AQ6Dd;EACE;EACA;EACA;EACA;EACA;EACA;EACA,kBRrEM;EQsEN,4BRRc;EQSd,2BRTc;EQUd,YACE;;ATxFA;ES6EJ;IAeI;IACA,ORFmB;IQGnB;;;;AAIJ;EACE;EACA,eRrCK;EQsCL;;AVpFA;EACE;;AClBA;ESkGJ;IV5EI;;;ACtBA;EDOF;IACE;;;ACRA;ESkGJ;IVtFI;;;;AUiGJ;EACE;EACA;;;AAGF;EACE;EACA;;AAEA;EAEE,kBX5Ha;;;AWgIjB;EACE;EACA,aR9DK;EQ+DL,gBR/DK;;ADhEH;ES4HJ;IAMI;IACA;IACA,eRpEG;IQqEH;;;;AAIJ;EACE;EACA;EACA;;AAEA;EACE;;AVxIF;EACE;;ACRA;ES8IF;IVlIE;;;ACZA;EDHF;IACE;;;ACEA;ES8IF;IV5IE;;;AUqJF;EACE,ORtFG;EQuFH,QRvFG;EQwFH,cR1FG;EQ2FH,ORlIS;EQmIT;;AAGF;EACE;;;AAIJ;EACE;EACA;;;AAGF;EACE;EACA;EACA;EACA,OR5JY;EQ6JZ;EACA;;AV5LA;EACE;;ACYA;ESyKJ;IVjLI;;;;AU2LJ;EACE;EACA,aRrHK;EQsHL,gBRtHK;EQuHL,cRrHK;EQsHL,aRxHK;EQyHL,ORxKY;EQyKZ;EACA,aR/GO;EQgHP,mBRtKY;;AFzBZ;EACE;;ACEA;ESmLJ;IVjLI;;;ACFA;ESmLJ;IAaI;IACA;IACA,cRlIG;IQmIH;IACA;;;;AAIJ;EACE,YR1IK;;;AQ6IP;EACE;;;AAGF;EACE;;AV1MA;EACE;;ACRA;ESgNJ;IVpMI;;;;AUyMJ;EACE;EACA,ORrJK;EQsJL,QRtJK;EQuJL;EACA,ORnJK;EQoJL,QRpJK;EQqJL,kBR7MM;EQ8MN;EACA;EACA,YACE;EAEF;EACA;;;AAGF;EACE;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA,YACE;;;AAMF;EACE;EACA;EACA;EACA;EACA;EACA;;AAGF;EACE,QRxLI;EQyLJ;;ATjQA;ES+PF;IAKI,ORzKiB;IQ0KjB,YACE;;;AAKN;EACE,kBR7PI;;ADfJ;ES2QF;IAII;;;AT/QF;ESmRF;IAEI;;;AAIJ;EACE;;AAGF;EACE;EACA;EACA;EACA,YACE;;ATlSF;ESwSA;IACE;IACA;IACA;;;AAIJ;EACE,aRxOI;;ADxEJ;ES+SF;IAII;;;;AC9TN;EACE;EACA;EACA;EACA,eT0EK;ESzEL;EACA,eTkFc;ESjFd,YACE;;;AAIJ;EACE;EACA;EACA;;;AAGF;AAAA;EAEE;EACA;EACA,kBTIM;ESHN;EACA;;AXNA;AAAA;EACE;;ACRA;EUOJ;AAAA;IXKI;;;AWKF;AAAA;EACE;;;AAOE;AAAA;EAEE;;AAGF;EACE,gBTkCD;;;AS3BL;EACE;;;AC9CF;EACE;EACA;EACA,kBVmBI;EUlBJ;EACA,eV+EY;;;AU1EhB;EACE,cVkBY;;;AUiCd;AAAA;AAAA;EAGE;EACA,eVMK;EULL,kBV7CM;EU8CN,eVgBc;EUfd;EACA;EACA;EACA;;AAIA;AAAA;AAAA;EACE,OVLG;EUMH;EACA;EACA;EACA;EACA,SVVG;EUWH;EACA;EACA,OV7DU;EU8DV;;AAEA;AAAA;AAAA;EACE,MVjEQ;;AUoEV;AAAA;AAAA;EACE;EACA;EACA;;AAGF;AAAA;AAAA;EACE;EACA;;AAMF;AAAA;AAAA;EACE;EACA;;;AASJ;EACE;EACA,SV/CG;EUgDH;EACA;EACA,eVtCY;;AUyCd;AAAA;EAEE;EACA;EACA;;;AAUJ;EACE;EACA,eVrEK;;AU6CL;EACE;EACA,SV/CG;EUgDH;EACA;EACA,eVtCY;;AUyCd;AAAA;EAEE;EACA;EACA;;;AAwBF;AAAA;EAEE;EACA,SVpFG;EUqFH;EACA;EACA,eV3EY;;;AUmFhB;EACE;EACA;EACA;EACA;;AAEA;AAAA;EAEE;EACA;EACA,kBV3JI;EU4JJ;;AZ9KF;AAAA;EACE;;ACEA;EWsKF;AAAA;IZpKE;;;AY8KF;EACE;EACA,eVjHG;EUkHH,cVlHG;;AUqHL;EACE;EACA;;;AAKJ;AAAA;EAEE,SV9HK;EU+HL,eV/HK;EUgIL;EACA;EACA,eVtHc;;AUwHd;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAIE;EACA;EACA;EACA;EACA;EACA;EACA;;;AAKJ;EACE;EACA;EACA;;;AAIF;AAAA;EAEE,YV9MM;EUmNJ,OVjNU;;;AUsNd;EACE,YVzNM;;;AWzBR;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAKF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;ACvOF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAKF;EACE;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;;;AbrBE;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;AAQR;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAKF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AdhHA;EACE;;ACYA;EcZJ;IfII;;;;AAKF;EACE;;ACEA;EcRJ;IfUI;;;;AAKF;EACE;;ACRA;EcJJ;IfgBI;;;;AAKF;EACE;;AClBA;EcAJ;IfsBI;;;;AAKF;EACE;;AC5BA;EcIJ;If4BI;;;;AAKF;EACE;;ACtCA;EcQJ;IfkCI;IACA,aEhDuB;;;;AFqDzB;EACE;EACA,aEvDuB;;ADKvB;EcYJ;If0CI;;;;AAKF;EACE;EACA,aElEuB;;ADKvB;EcgBJ;IfiDI;;;;AAKF;EACE;EACA,aE7EuB;;ADKvB;EcoBJ;IfwDI;;;;AAKF;EACE;EACA,aExFuB;;ADKvB;EcwBJ;If+DI;;;;Ae3DJ;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE,abxDiB;;;Aa2DnB;EACE,ab1DyB;;;Aa6D3B;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AC/EF;EACE;EACA;EACA;;AAGE;EACE;;;ACLN;EACE;EACA;;;AAQA;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AhBlCA;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AAaN;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AhB7GA;EgBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhB/IJ;EgBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhB/IJ;EgBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhB/IJ;EgBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhB/IJ;EgBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AC3JR;EACE;AAAA;AAAA;AAAA;AAAA;AAAA;IAME;;EAGF;IACE;IACA;;EAGF;IACE;IACA;IACA;;EAGF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;;EAGF;IACE;;EAGF;IACE;IACA;;;ACvCJ;EACE;EACA;EACA;EACA;EACA;EACA;EACA;;;AAGF;AAAA;EAEE,OjBwBW;EiBvBX,kBjBaM;EiBZN;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;;;ACtBF;EACE,kBlBsBM;;;AkBnBR;EACI;EACA;EACA,elB8EY;EkB7EZ;EACA;;AAEA;EACI,OlBgCI;EkB/BJ;EACA;EACA;EACA;EACA;EACA;;AAGJ;EACE,OlBsBM;EkBrBN;EACA;EACA;EACA;EACA;;;AAIN;EACI;EACA;EACA,elBmDY;EkBlDZ;EACA;;AACA;EACE;EACA;EACA,OlBIM;EkBHN;EACA;EACA;EACA;EACA;;;AAIN;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAIJ;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAMJ;EACI;EACA;EACA,elBKY;EkBJZ;EACA;;AAEA;EACI,OlB7CG;EkB8CH;EACA;EACA;EACA;EACA;EACA;;AAGJ;EACE,OlBvDK;EkBwDL;EACA;EACA;EACA;EACA;;;AAIN;EACI;EACA;EACA,elBtBY;EkBuBZ;EACA;;AACA;EACE;EACA;EACA,OlBzEK;EkB0EL;EACA;EACA;EACA;EACA;;;AAIN;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAIJ;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAMJ;EACI;EACA;EACA,elBpEY;EkBqEZ;EACA;;AAEA;EACI,OlB9GK;EkB+GL;EACA;EACA;EACA;EACA;EACA;;AAGJ;EACE,OlBxHO;EkByHP;EACA;EACA;EACA;EACA;;;AAIN;EACI;EACA;EACA,elB/FY;EkBgGZ;EACA;;AACA;EACE;EACA;EACA,OlB1IO;EkB2IP;EACA;EACA;EACA;EACA;;;AAIN;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAIJ;EACE;EACA;;AAEA;EACE;;AAGF;EACE","sourcesContent":["/*\ngenerated by accessible-pygments \nCopyright (c) 2022, Quansight Labs\nLicensed under the BSD license, see LICENSE for details.\n--\ngenerated by Pygments \nCopyright 2006-2025 by the Pygments team.\nLicensed under the BSD license, see LICENSE for details.\n*/\n\n.highlight .hll { background-color: #0969da4a }\n.highlight .c { color: #6E7781 } /* Comment */\n.highlight .err { color: #CF222E } /* Error */\n.highlight .k { color: #CF222E } /* Keyword */\n.highlight .l { color: #953800 } /* Literal */\n.highlight .n { color: #8250DF } /* Name */\n.highlight .o { color: #116329 } /* Operator */\n.highlight .p { color: #24292F } /* Punctuation */\n.highlight .ch { color: #6E7781 } /* Comment.Hashbang */\n.highlight .cm { color: #6E7781 } /* Comment.Multiline */\n.highlight .cp { color: #6E7781 } /* Comment.Preproc */\n.highlight .cpf { color: #6E7781 } /* Comment.PreprocFile */\n.highlight .c1 { color: #6E7781 } /* Comment.Single */\n.highlight .cs { color: #6E7781 } /* Comment.Special */\n.highlight .gd { color: #0550AE } /* Generic.Deleted */\n.highlight .ge { font-style: italic } /* Generic.Emph */\n.highlight .gr { color: #CF222E } /* Generic.Error */\n.highlight .gh { color: #0550AE } /* Generic.Heading */\n.highlight .gs { font-weight: bold } /* Generic.Strong */\n.highlight .gu { color: #0550AE } /* Generic.Subheading */\n.highlight .kc { color: #0550AE } /* Keyword.Constant */\n.highlight .kd { color: #CF222E } /* Keyword.Declaration */\n.highlight .kn { color: #CF222E } /* Keyword.Namespace */\n.highlight .kp { color: #CF222E } /* Keyword.Pseudo */\n.highlight .kr { color: #CF222E } /* Keyword.Reserved */\n.highlight .kt { color: #CF222E } /* Keyword.Type */\n.highlight .ld { color: #953800 } /* Literal.Date */\n.highlight .m { color: #953800 } /* Literal.Number */\n.highlight .s { color: #0550AE } /* Literal.String */\n.highlight .na { color: #953800 } /* Name.Attribute */\n.highlight .nb { color: #953800 } /* Name.Builtin */\n.highlight .nc { color: #0550AE } /* Name.Class */\n.highlight .no { color: #0550AE } /* Name.Constant */\n.highlight .nd { color: #953800 } /* Name.Decorator */\n.highlight .ni { color: #116329 } /* Name.Entity */\n.highlight .ne { color: #8250DF } /* Name.Exception */\n.highlight .nf { color: #0550AE } /* Name.Function */\n.highlight .nl { color: #953800 } /* Name.Label */\n.highlight .nn { color: #24292F } /* Name.Namespace */\n.highlight .nx { color: #8250DF } /* Name.Other */\n.highlight .py { color: #0550AE } /* Name.Property */\n.highlight .nt { color: #116329 } /* Name.Tag */\n.highlight .nv { color: #953800 } /* Name.Variable */\n.highlight .ow { color: #8250DF } /* Operator.Word */\n.highlight .pm { color: #24292F } /* Punctuation.Marker */\n.highlight .w { color: #24292F } /* Text.Whitespace */\n.highlight .mb { color: #953800 } /* Literal.Number.Bin */\n.highlight .mf { color: #953800 } /* Literal.Number.Float */\n.highlight .mh { color: #953800 } /* Literal.Number.Hex */\n.highlight .mi { color: #953800 } /* Literal.Number.Integer */\n.highlight .mo { color: #953800 } /* Literal.Number.Oct */\n.highlight .sa { color: #0550AE } /* Literal.String.Affix */\n.highlight .sb { color: #0550AE } /* Literal.String.Backtick */\n.highlight .sc { color: #0550AE } /* Literal.String.Char */\n.highlight .dl { color: #0550AE } /* Literal.String.Delimiter */\n.highlight .sd { color: #0550AE } /* Literal.String.Doc */\n.highlight .s2 { color: #0550AE } /* Literal.String.Double */\n.highlight .se { color: #0550AE } /* Literal.String.Escape */\n.highlight .sh { color: #0550AE } /* Literal.String.Heredoc */\n.highlight .si { color: #0550AE } /* Literal.String.Interpol */\n.highlight .sx { color: #0550AE } /* Literal.String.Other */\n.highlight .sr { color: #0550AE } /* Literal.String.Regex */\n.highlight .s1 { color: #0550AE } /* Literal.String.Single */\n.highlight .ss { color: #0550AE } /* Literal.String.Symbol */\n.highlight .bp { color: #953800 } /* Name.Builtin.Pseudo */\n.highlight .fm { color: #0550AE } /* Name.Function.Magic */\n.highlight .vc { color: #953800 } /* Name.Variable.Class */\n.highlight .vg { color: #953800 } /* Name.Variable.Global */\n.highlight .vi { color: #953800 } /* Name.Variable.Instance */\n.highlight .vm { color: #953800 } /* Name.Variable.Magic */\n.highlight .il { color: #953800 } /* Literal.Number.Integer.Long */\n","/*! normalize.css v8.0.1 | MIT License | github.com/necolas/normalize.css */\n\n/* Document\n ========================================================================== */\n\n/**\n * 1. Correct the line height in all browsers.\n * 2. Prevent adjustments of font size after orientation changes in iOS.\n */\n\nhtml {\n line-height: 1.15; /* 1 */\n text-size-adjust: 100%; /* 2 */\n}\n\n/* Sections\n ========================================================================== */\n\n/**\n * Remove the margin in all browsers.\n */\n\nbody {\n margin: 0;\n}\n\n/**\n * Render the `main` element consistently in IE.\n */\n\nmain {\n display: block;\n}\n\n/**\n * Correct the font size and margin on `h1` elements within `section` and\n * `article` contexts in Chrome, Firefox, and Safari.\n */\n\nh1 {\n font-size: 2em;\n margin: 0.67em 0;\n}\n\n/* Grouping content\n ========================================================================== */\n\n/**\n * 1. Add the correct box sizing in Firefox.\n * 2. Show the overflow in Edge and IE.\n */\n\nhr {\n box-sizing: content-box; /* 1 */\n height: 0; /* 1 */\n overflow: visible; /* 2 */\n}\n\n/**\n * 1. Correct the inheritance and scaling of font size in all browsers.\n * 2. Correct the odd `em` font sizing in all browsers.\n */\n\npre {\n font-family: monospace; /* 1 */\n font-size: 1em; /* 2 */\n}\n\n/* Text-level semantics\n ========================================================================== */\n\n/**\n * Remove the gray background on active links in IE 10.\n */\n\na {\n background-color: transparent;\n}\n\n/**\n * 1. Remove the bottom border in Chrome 57-\n * 2. Add the correct text decoration in Chrome, Edge, IE, Opera, and Safari.\n */\n\nabbr[title] {\n border-bottom: none; /* 1 */\n text-decoration: underline; /* 2 */\n text-decoration: underline dotted; /* 2 */\n}\n\n/**\n * Add the correct font weight in Chrome, Edge, and Safari.\n */\n\nb,\nstrong {\n font-weight: bolder;\n}\n\n/**\n * 1. Correct the inheritance and scaling of font size in all browsers.\n * 2. Correct the odd `em` font sizing in all browsers.\n */\n\ncode,\nkbd,\nsamp {\n font-family: monospace; /* 1 */\n font-size: 1em; /* 2 */\n}\n\n/**\n * Add the correct font size in all browsers.\n */\n\nsmall {\n font-size: 80%;\n}\n\n/**\n * Prevent `sub` and `sup` elements from affecting the line height in\n * all browsers.\n */\n\nsub,\nsup {\n font-size: 75%;\n line-height: 0;\n position: relative;\n vertical-align: baseline;\n}\n\nsub {\n bottom: -0.25em;\n}\n\nsup {\n top: -0.5em;\n}\n\n/* Embedded content\n ========================================================================== */\n\n/**\n * Remove the border on images inside links in IE 10.\n */\n\nimg {\n border-style: none;\n}\n\n/* Forms\n ========================================================================== */\n\n/**\n * 1. Change the font styles in all browsers.\n * 2. Remove the margin in Firefox and Safari.\n */\n\nbutton,\ninput,\noptgroup,\nselect,\ntextarea {\n font-family: inherit; /* 1 */\n font-size: 100%; /* 1 */\n line-height: 1.15; /* 1 */\n margin: 0; /* 2 */\n}\n\n/**\n * Show the overflow in IE.\n * 1. Show the overflow in Edge.\n */\n\nbutton,\ninput {\n /* 1 */\n overflow: visible;\n}\n\n/**\n * Remove the inheritance of text transform in Edge, Firefox, and IE.\n * 1. Remove the inheritance of text transform in Firefox.\n */\n\nbutton,\nselect {\n /* 1 */\n text-transform: none;\n}\n\n/**\n * Correct the inability to style clickable types in iOS and Safari.\n */\n\nbutton,\n[type=\"button\"],\n[type=\"reset\"],\n[type=\"submit\"] {\n appearance: button;\n}\n\n/**\n * Remove the inner border and padding in Firefox.\n */\n\nbutton::-moz-focus-inner,\n[type=\"button\"]::-moz-focus-inner,\n[type=\"reset\"]::-moz-focus-inner,\n[type=\"submit\"]::-moz-focus-inner {\n border-style: none;\n padding: 0;\n}\n\n/**\n * Restore the focus styles unset by the previous rule.\n */\n\nbutton:-moz-focusring,\n[type=\"button\"]:-moz-focusring,\n[type=\"reset\"]:-moz-focusring,\n[type=\"submit\"]:-moz-focusring {\n outline: 1px dotted ButtonText;\n}\n\n/**\n * Correct the padding in Firefox.\n */\n\nfieldset {\n padding: 0.35em 0.75em 0.625em;\n}\n\n/**\n * 1. Correct the text wrapping in Edge and IE.\n * 2. Correct the color inheritance from `fieldset` elements in IE.\n * 3. Remove the padding so developers are not caught out when they zero out\n * `fieldset` elements in all browsers.\n */\n\nlegend {\n box-sizing: border-box; /* 1 */\n color: inherit; /* 2 */\n display: table; /* 1 */\n max-width: 100%; /* 1 */\n padding: 0; /* 3 */\n white-space: normal; /* 1 */\n}\n\n/**\n * Add the correct vertical alignment in Chrome, Firefox, and Opera.\n */\n\nprogress {\n vertical-align: baseline;\n}\n\n/**\n * Remove the default vertical scrollbar in IE 10+.\n */\n\ntextarea {\n overflow: auto;\n}\n\n/**\n * 1. Add the correct box sizing in IE 10.\n * 2. Remove the padding in IE 10.\n */\n\n[type=\"checkbox\"],\n[type=\"radio\"] {\n box-sizing: border-box; /* 1 */\n padding: 0; /* 2 */\n}\n\n/**\n * Correct the cursor style of increment and decrement buttons in Chrome.\n */\n\n[type=\"number\"]::-webkit-inner-spin-button,\n[type=\"number\"]::-webkit-outer-spin-button {\n height: auto;\n}\n\n/**\n * 1. Correct the odd appearance in Chrome and Safari.\n * 2. Correct the outline style in Safari.\n */\n\n[type=\"search\"] {\n appearance: textfield; /* 1 */\n outline-offset: -2px; /* 2 */\n}\n\n/**\n * Remove the inner padding in Chrome and Safari on macOS.\n */\n\n[type=\"search\"]::-webkit-search-decoration {\n appearance: none;\n}\n\n/**\n * 1. Correct the inability to style clickable types in iOS and Safari.\n * 2. Change font properties to `inherit` in Safari.\n */\n\n::-webkit-file-upload-button {\n appearance: button; /* 1 */\n font: inherit; /* 2 */\n}\n\n/* Interactive\n ========================================================================== */\n\n/*\n * Add the correct display in Edge, IE 10+, and Firefox.\n */\n\ndetails {\n display: block;\n}\n\n/*\n * Add the correct display in all browsers.\n */\n\nsummary {\n display: list-item;\n}\n\n/* Misc\n ========================================================================== */\n\n/**\n * Add the correct display in IE 10+.\n */\n\ntemplate {\n display: none;\n}\n\n/**\n * Add the correct display in IE 10.\n */\n\n[hidden] {\n display: none;\n}\n","// Base element style overrides\n// stylelint-disable selector-no-type, selector-max-type, selector-max-specificity, selector-max-id\n\n:root {\n color-scheme: $color-scheme;\n}\n\n* {\n box-sizing: border-box;\n}\n\nhtml {\n scroll-behavior: smooth;\n\n @include fs-4;\n}\n\nbody {\n font-family: $body-font-family;\n font-size: inherit;\n line-height: $body-line-height;\n color: $body-text-color;\n background-color: $body-background-color;\n overflow-wrap: break-word;\n}\n\nol,\nul,\ndl,\npre,\naddress,\nblockquote,\ntable,\ndiv,\nhr,\nform,\nfieldset,\nnoscript .table-wrapper {\n margin-top: 0;\n}\n\nh1,\nh2,\nh3,\nh4,\nh5,\nh6,\n#toctitle {\n margin-top: 0;\n margin-bottom: 1em;\n font-weight: 500;\n line-height: $body-heading-line-height;\n color: $body-heading-color;\n}\n\np {\n margin-top: 1em;\n margin-bottom: 1em;\n}\n\na {\n color: $link-color;\n text-decoration: none;\n}\n\na:not([class]) {\n text-decoration: underline;\n text-decoration-color: $border-color;\n text-underline-offset: 2px;\n\n &:hover {\n text-decoration-color: rgba($link-color, 0.45);\n }\n}\n\ncode {\n font-family: $mono-font-family;\n font-size: 0.75em;\n line-height: $body-line-height;\n}\n\nfigure,\npre {\n margin: 0;\n}\n\nli {\n margin: 0.25em 0;\n}\n\nimg {\n max-width: 100%;\n height: auto;\n}\n\nhr {\n height: 1px;\n padding: 0;\n margin: $sp-6 0;\n background-color: $border-color;\n border: 0;\n}\n\n// adds a GitHub-style sidebar to blockquotes\nblockquote {\n margin: 10px 0;\n\n // resets user-agent stylesheets for blockquotes\n margin-block-start: 0;\n margin-inline-start: 0;\n padding-left: 1rem;\n border-left: 3px solid $border-color;\n}\n","$color-scheme: light !default;\n$body-background-color: $white !default;\n$body-heading-color: $grey-dk-300 !default;\n$body-text-color: $grey-dk-100 !default;\n$link-color: $purple-000 !default;\n$nav-child-link-color: $grey-dk-100 !default;\n$sidebar-color: $grey-lt-000 !default;\n$base-button-color: #f7f7f7 !default;\n$btn-primary-color: $purple-100 !default;\n$code-background-color: $white !default;\n$feedback-color: darken($sidebar-color, 3%) !default;\n$table-background-color: $white !default;\n$search-background-color: $white !default;\n$search-result-preview-color: $grey-dk-100 !default;\n\n@import \"./vendor/accessible-pygments/github-light\";\n","@mixin fs-1 {\n & {\n font-size: $font-size-1 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-1-sm !important;\n }\n}\n\n@mixin fs-2 {\n & {\n font-size: $font-size-2 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-3 !important;\n }\n}\n\n@mixin fs-3 {\n & {\n font-size: $font-size-3 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-4 !important;\n }\n}\n\n@mixin fs-4 {\n & {\n font-size: $font-size-4 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-5 !important;\n }\n}\n\n@mixin fs-5 {\n & {\n font-size: $font-size-5 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-6 !important;\n }\n}\n\n@mixin fs-6 {\n & {\n font-size: $font-size-6 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-7 !important;\n line-height: $body-heading-line-height;\n }\n}\n\n@mixin fs-7 {\n & {\n font-size: $font-size-7 !important;\n line-height: $body-heading-line-height;\n }\n\n @include mq(sm) {\n font-size: $font-size-8 !important;\n }\n}\n\n@mixin fs-8 {\n & {\n font-size: $font-size-8 !important;\n line-height: $body-heading-line-height;\n }\n\n @include mq(sm) {\n font-size: $font-size-9 !important;\n }\n}\n\n@mixin fs-9 {\n & {\n font-size: $font-size-9 !important;\n line-height: $body-heading-line-height;\n }\n\n @include mq(sm) {\n font-size: $font-size-10 !important;\n }\n}\n\n@mixin fs-10 {\n & {\n font-size: $font-size-10 !important;\n line-height: $body-heading-line-height;\n }\n\n @include mq(sm) {\n font-size: $font-size-10-sm !important;\n }\n}\n","// Media query\n\n// Media query mixin\n// Usage:\n// @include mq(md) {\n// ..medium and up styles\n// }\n@mixin mq($name) {\n // Retrieves the value from the key\n $value: map-get($media-queries, $name);\n\n // If the key exists in the map\n @if $value {\n // Prints a media query based on the value\n @media (min-width: $value) {\n @content;\n }\n } @else {\n @warn \"No value could be retrieved from `#{$media-query}`. Please make sure it is defined in `$media-queries` map.\";\n }\n}\n\n// Responsive container\n\n@mixin container {\n padding-right: $gutter-spacing-sm;\n padding-left: $gutter-spacing-sm;\n\n @include mq(md) {\n padding-right: $gutter-spacing;\n padding-left: $gutter-spacing;\n }\n}\n","// Typography\n\n// prettier-ignore\n$body-font-family: system-ui, -apple-system, blinkmacsystemfont, \"Segoe UI\",\n roboto, \"Helvetica Neue\", arial, sans-serif, \"Segoe UI Emoji\" !default;\n$mono-font-family: \"SFMono-Regular\", menlo, consolas, monospace !default;\n$root-font-size: 16px !default; // DEPRECATED: previously base font-size for rems\n$body-line-height: 1.4 !default;\n$content-line-height: 1.6 !default;\n$body-heading-line-height: 1.25 !default;\n\n// Font size\n// `-sm` suffix is the size at the small (and above) media query\n\n$font-size-1: 0.5625rem !default;\n$font-size-1-sm: 0.625rem !default;\n$font-size-2: 0.6875rem !default; // h4 - uppercased!, h6 not uppercased, text-small\n$font-size-3: 0.75rem !default; // h5\n$font-size-4: 0.875rem !default;\n$font-size-5: 1rem !default; // h3\n$font-size-6: 1.125rem !default; // h2\n$font-size-7: 1.5rem !default;\n$font-size-8: 2rem !default; // h1\n$font-size-9: 2.25rem !default;\n$font-size-10: 2.625rem !default;\n$font-size-10-sm: 3rem !default;\n\n// Colors\n\n$white: #fff !default;\n$grey-dk-000: #959396 !default;\n$grey-dk-100: #5c5962 !default;\n$grey-dk-200: #44434d !default;\n$grey-dk-250: #302d36 !default;\n$grey-dk-300: #27262b !default;\n$grey-lt-000: #f5f6fa !default;\n$grey-lt-100: #eeebee !default;\n$grey-lt-200: #ecebed !default;\n$grey-lt-300: #e6e1e8 !default;\n$purple-000: #7253ed !default;\n$purple-100: #5e41d0 !default;\n$purple-200: #4e26af !default;\n$purple-300: #381885 !default;\n$blue-000: #2c84fa !default;\n$blue-100: #2869e6 !default;\n$blue-200: #264caf !default;\n$blue-300: #183385 !default;\n$green-000: #41d693 !default;\n$green-100: #11b584 !default;\n$green-200: #009c7b !default;\n$green-300: #026e57 !default;\n$yellow-000: #ffeb82 !default;\n$yellow-100: #fadf50 !default;\n$yellow-200: #f7d12e !default;\n$yellow-300: #e7af06 !default;\n$red-000: #f77e7e !default;\n$red-100: #f96e65 !default;\n$red-200: #e94c4c !default;\n$red-300: #dd2e2e !default;\n\n// Spacing\n\n$spacing-unit: 1rem; // 1rem == 16px\n\n$spacers: (\n sp-0: 0,\n sp-1: $spacing-unit * 0.25,\n sp-2: $spacing-unit * 0.5,\n sp-3: $spacing-unit * 0.75,\n sp-4: $spacing-unit,\n sp-5: $spacing-unit * 1.5,\n sp-6: $spacing-unit * 2,\n sp-7: $spacing-unit * 2.5,\n sp-8: $spacing-unit * 3,\n sp-9: $spacing-unit * 3.5,\n sp-10: $spacing-unit * 4,\n) !default;\n$sp-1: map-get($spacers, sp-1) !default; // 0.25 rem == 4px\n$sp-2: map-get($spacers, sp-2) !default; // 0.5 rem == 8px\n$sp-3: map-get($spacers, sp-3) !default; // 0.75 rem == 12px\n$sp-4: map-get($spacers, sp-4) !default; // 1 rem == 16px\n$sp-5: map-get($spacers, sp-5) !default; // 1.5 rem == 24px\n$sp-6: map-get($spacers, sp-6) !default; // 2 rem == 32px\n$sp-7: map-get($spacers, sp-7) !default; // 2.5 rem == 40px\n$sp-8: map-get($spacers, sp-8) !default; // 3 rem == 48px\n$sp-9: map-get($spacers, sp-9) !default; // 3.5 rem == 56px\n$sp-10: map-get($spacers, sp-10) !default; // 4 rem == 64px\n\n// Borders\n\n$border: 1px solid !default;\n$border-radius: 4px !default;\n$border-color: $grey-lt-100 !default;\n\n// Grid system\n\n$gutter-spacing: $sp-6 !default;\n$gutter-spacing-sm: $sp-4 !default;\n$nav-width: 16.5rem !default;\n$nav-width-md: 15.5rem !default;\n$nav-list-item-height: $sp-6 !default;\n$nav-list-item-height-sm: $sp-8 !default;\n$nav-list-expander-right: true;\n$content-width: 50rem !default;\n$header-height: 3.75rem !default;\n$search-results-width: $content-width - $nav-width !default;\n$transition-duration: 400ms;\n\n// Media queries in pixels\n\n$media-queries: (\n xs: 20rem,\n sm: 31.25rem,\n md: $content-width,\n lg: $content-width + $nav-width,\n xl: 87.5rem,\n) !default;\n","// The basic two column layout\n\n.side-bar {\n z-index: 0;\n display: flex;\n flex-wrap: wrap;\n background-color: $sidebar-color;\n\n @include mq(md) {\n flex-flow: column nowrap;\n position: fixed;\n width: $nav-width-md;\n height: 100%;\n border-right: $border $border-color;\n align-items: flex-end;\n }\n\n @include mq(lg) {\n width: calc((100% - #{$nav-width + $content-width}) / 2 + #{$nav-width});\n min-width: $nav-width;\n }\n\n & + .main {\n @include mq(md) {\n margin-left: $nav-width-md;\n }\n\n @include mq(lg) {\n // stylelint-disable function-name-case\n // disable for Max(), we want to use the CSS max() function\n margin-left: Max(\n #{$nav-width},\n calc((100% - #{$nav-width + $content-width}) / 2 + #{$nav-width})\n );\n // stylelint-enable function-name-case\n }\n\n .main-header {\n display: none;\n background-color: $sidebar-color;\n\n @include mq(md) {\n display: flex;\n background-color: $body-background-color;\n }\n\n &.nav-open {\n display: block;\n\n @include mq(md) {\n display: flex;\n }\n }\n }\n }\n}\n\n.main {\n margin: auto;\n\n @include mq(md) {\n position: relative;\n max-width: $content-width;\n }\n}\n\n.main-content-wrap {\n padding-top: $gutter-spacing-sm;\n padding-bottom: $gutter-spacing-sm;\n\n @include container;\n\n @include mq(md) {\n padding-top: $gutter-spacing;\n padding-bottom: $gutter-spacing;\n }\n}\n\n.main-header {\n z-index: 0;\n border-bottom: $border $border-color;\n\n @include mq(md) {\n display: flex;\n justify-content: space-between;\n height: $header-height;\n }\n}\n\n.site-nav,\n.site-header,\n.site-footer {\n width: 100%;\n\n @include mq(lg) {\n width: $nav-width;\n }\n}\n\n.site-nav {\n display: none;\n\n &.nav-open {\n display: block;\n }\n\n @include mq(md) {\n display: block;\n padding-top: $sp-8;\n padding-bottom: $gutter-spacing-sm;\n overflow-y: auto;\n flex: 1 1 auto;\n }\n}\n\n.site-header {\n display: flex;\n min-height: $header-height;\n align-items: center;\n\n @include mq(md) {\n height: $header-height;\n max-height: $header-height;\n border-bottom: $border $border-color;\n }\n}\n\n.site-title {\n flex-grow: 1;\n display: flex;\n height: 100%;\n align-items: center;\n padding-top: $sp-3;\n padding-bottom: $sp-3;\n color: $body-heading-color;\n\n @include container;\n\n @include fs-6;\n\n @include mq(md) {\n padding-top: $sp-2;\n padding-bottom: $sp-2;\n }\n}\n\n@if variable-exists(logo) {\n .site-logo {\n width: 100%;\n height: 100%;\n background-image: url($logo);\n background-repeat: no-repeat;\n background-position: left center;\n background-size: contain;\n }\n}\n\n.site-button {\n display: flex;\n height: 100%;\n padding: $gutter-spacing-sm;\n align-items: center;\n}\n\n@include mq(md) {\n .site-header .site-button {\n display: none;\n }\n}\n\n.site-title:hover {\n background-image: linear-gradient(\n -90deg,\n rgba($feedback-color, 1) 0%,\n rgba($feedback-color, 0.8) 80%,\n rgba($feedback-color, 0) 100%\n );\n}\n\n.site-button:hover {\n background-image: linear-gradient(\n -90deg,\n rgba($feedback-color, 1) 0%,\n rgba($feedback-color, 0.8) 100%\n );\n}\n\n.site-footer {\n position: absolute;\n bottom: 0;\n left: 0;\n padding-top: $sp-4;\n padding-bottom: $sp-4;\n\n @include container;\n\n @include fs-2;\n\n @include mq(md) {\n position: static;\n justify-self: end;\n }\n}\n\n.icon {\n width: $sp-5;\n height: $sp-5;\n color: $link-color;\n}\n","@charset \"UTF-8\";\n\n// Styles for rendered markdown in the .main-content container\n// stylelint-disable selector-no-type, max-nesting-depth, selector-max-compound-selectors, selector-max-type, selector-max-specificity, selector-max-id\n\n.main-content {\n line-height: $content-line-height;\n\n ol,\n ul,\n dl,\n pre,\n address,\n blockquote,\n .table-wrapper {\n margin-top: 0.5em;\n }\n\n a {\n overflow: hidden;\n text-overflow: ellipsis;\n }\n\n ul,\n ol {\n padding-left: 1.5em;\n }\n\n li {\n .highlight {\n margin-top: $sp-1;\n }\n }\n\n ol {\n list-style-type: none;\n counter-reset: step-counter;\n\n > li {\n position: relative;\n\n &::before {\n position: absolute;\n top: 0.2em;\n left: -1.6em;\n color: $grey-dk-000;\n content: counter(step-counter);\n counter-increment: step-counter;\n @include fs-3;\n\n @include mq(sm) {\n top: 0.11em;\n }\n }\n\n ol {\n counter-reset: sub-counter;\n\n > li {\n &::before {\n content: counter(sub-counter, lower-alpha);\n counter-increment: sub-counter;\n }\n }\n }\n }\n }\n\n ul {\n list-style: none;\n\n > li {\n &::before {\n position: absolute;\n margin-left: -1.4em;\n color: $grey-dk-000;\n content: \"•\";\n }\n }\n }\n\n .task-list-item {\n &::before {\n content: \"\";\n }\n }\n\n .task-list-item-checkbox {\n margin-right: 0.6em;\n margin-left: -1.4em;\n\n // The same margin-left is used above for ul > li::before\n }\n\n hr + * {\n margin-top: 0;\n }\n\n h1:first-of-type {\n margin-top: 0.5em;\n }\n\n dl {\n display: grid;\n grid-template: auto / 10em 1fr;\n }\n\n dt,\n dd {\n margin: 0.25em 0;\n }\n\n dt {\n grid-column: 1;\n font-weight: 500;\n text-align: right;\n\n &::after {\n content: \":\";\n }\n }\n\n dd {\n grid-column: 2;\n margin-bottom: 0;\n margin-left: 1em;\n\n blockquote,\n div,\n dl,\n dt,\n h1,\n h2,\n h3,\n h4,\n h5,\n h6,\n li,\n ol,\n p,\n pre,\n table,\n ul,\n .table-wrapper {\n &:first-child {\n margin-top: 0;\n }\n }\n }\n\n dd,\n ol,\n ul {\n dl:first-child {\n dt:first-child,\n dd:nth-child(2) {\n margin-top: 0;\n }\n }\n }\n\n .anchor-heading {\n position: absolute;\n right: -$sp-4;\n width: $sp-5;\n height: 100%;\n padding-right: $sp-1;\n padding-left: $sp-1;\n overflow: visible;\n\n @include mq(md) {\n right: auto;\n left: -$sp-5;\n }\n\n svg {\n display: inline-block;\n width: 100%;\n height: 100%;\n color: $link-color;\n visibility: hidden;\n }\n }\n\n .anchor-heading:hover,\n .anchor-heading:focus,\n h1:hover > .anchor-heading,\n h2:hover > .anchor-heading,\n h3:hover > .anchor-heading,\n h4:hover > .anchor-heading,\n h5:hover > .anchor-heading,\n h6:hover > .anchor-heading {\n svg {\n visibility: visible;\n }\n }\n\n summary {\n cursor: pointer;\n }\n\n h1,\n h2,\n h3,\n h4,\n h5,\n h6,\n #toctitle {\n position: relative;\n margin-top: 1.5em;\n margin-bottom: 0.25em;\n\n + table,\n + .table-wrapper,\n + .code-example,\n + .highlighter-rouge,\n + .sectionbody .listingblock {\n margin-top: 1em;\n }\n\n + p:not(.label) {\n margin-top: 0;\n }\n }\n\n > h1:first-child,\n > h2:first-child,\n > h3:first-child,\n > h4:first-child,\n > h5:first-child,\n > h6:first-child,\n > .sect1:first-child > h2,\n > .sect2:first-child > h3,\n > .sect3:first-child > h4,\n > .sect4:first-child > h5,\n > .sect5:first-child > h6 {\n margin-top: $sp-2;\n }\n}\n","// Main nav, breadcrumb, etc...\n// stylelint-disable selector-no-type, max-nesting-depth, selector-max-compound-selectors, selector-max-type, selector-max-specificity\n\n.nav-list {\n padding: 0;\n margin-top: 0;\n margin-bottom: 0;\n list-style: none;\n\n .nav-list-item {\n position: relative;\n margin: 0;\n\n @include fs-4;\n\n @include mq(md) {\n @include fs-3;\n }\n\n .nav-list-link {\n display: block;\n min-height: $nav-list-item-height-sm;\n padding-top: $sp-1;\n padding-bottom: $sp-1;\n line-height: #{$nav-list-item-height-sm - 2 * $sp-1};\n @if $nav-list-expander-right {\n padding-right: $nav-list-item-height-sm;\n padding-left: $gutter-spacing-sm;\n } @else {\n padding-right: $gutter-spacing-sm;\n padding-left: $nav-list-item-height-sm;\n }\n\n @include mq(md) {\n min-height: $nav-list-item-height;\n line-height: #{$nav-list-item-height - 2 * $sp-1};\n @if $nav-list-expander-right {\n padding-right: $nav-list-item-height;\n padding-left: $gutter-spacing;\n } @else {\n padding-right: $gutter-spacing;\n padding-left: $nav-list-item-height;\n }\n }\n\n &.external > svg {\n width: $sp-4;\n height: $sp-4;\n vertical-align: text-bottom;\n }\n\n &.active {\n font-weight: 600;\n text-decoration: none;\n }\n\n &:hover,\n &.active {\n color: darken($link-color, 5%);\n background-image: linear-gradient(\n -90deg,\n rgba($feedback-color, 1) 0%,\n rgba($feedback-color, 0.8) 80%,\n rgba($feedback-color, 0) 100%\n );\n }\n }\n\n .nav-list-expander {\n position: absolute;\n @if $nav-list-expander-right {\n right: 0;\n }\n\n width: $nav-list-item-height-sm;\n height: $nav-list-item-height-sm;\n padding: #{$nav-list-item-height-sm * 0.25};\n color: $link-color;\n\n @include mq(md) {\n width: $nav-list-item-height;\n height: $nav-list-item-height;\n padding: #{$nav-list-item-height * 0.25};\n }\n\n &:hover {\n background-image: linear-gradient(\n -90deg,\n rgba($feedback-color, 1) 0%,\n rgba($feedback-color, 0.8) 100%\n );\n }\n\n @if $nav-list-expander-right {\n svg {\n transform: rotate(90deg);\n }\n }\n }\n\n > .nav-list {\n display: none;\n padding-left: $sp-3;\n list-style: none;\n\n .nav-list-item {\n position: relative;\n\n .nav-list-link {\n color: $nav-child-link-color;\n }\n\n .nav-list-expander {\n color: $nav-child-link-color;\n }\n }\n }\n\n &.active {\n > .nav-list-expander svg {\n @if $nav-list-expander-right {\n transform: rotate(-90deg);\n } @else {\n transform: rotate(90deg);\n }\n }\n\n > .nav-list {\n display: block;\n }\n }\n }\n}\n\n.nav-category {\n padding: $sp-2 $gutter-spacing-sm;\n font-weight: 600;\n text-align: start;\n text-transform: uppercase;\n border-bottom: $border $border-color;\n @include fs-2;\n\n @include mq(md) {\n padding: $sp-2 $gutter-spacing;\n margin-top: $gutter-spacing-sm;\n text-align: start;\n\n &:first-child {\n margin-top: 0;\n }\n }\n}\n\n.nav-list.nav-category-list {\n > .nav-list-item {\n margin: 0;\n\n > .nav-list {\n padding: 0;\n\n > .nav-list-item {\n > .nav-list-link {\n color: $link-color;\n }\n\n > .nav-list-expander {\n color: $link-color;\n }\n }\n }\n }\n}\n\n// Aux nav\n\n.aux-nav {\n height: 100%;\n overflow-x: auto;\n @include fs-2;\n\n .aux-nav-list {\n display: flex;\n height: 100%;\n padding: 0;\n margin: 0;\n list-style: none;\n }\n\n .aux-nav-list-item {\n display: inline-block;\n height: 100%;\n padding: 0;\n margin: 0;\n }\n\n @include mq(md) {\n padding-right: $gutter-spacing-sm;\n }\n}\n\n// Breadcrumb nav\n\n.breadcrumb-nav {\n @include mq(md) {\n margin-top: -$sp-4;\n }\n}\n\n.breadcrumb-nav-list {\n padding-left: 0;\n margin-bottom: $sp-3;\n list-style: none;\n}\n\n.breadcrumb-nav-list-item {\n display: table-cell;\n @include fs-2;\n\n &::before {\n display: none;\n }\n\n &::after {\n display: inline-block;\n margin-right: $sp-2;\n margin-left: $sp-2;\n color: $grey-dk-000;\n content: \"/\";\n }\n\n &:last-child {\n &::after {\n content: \"\";\n }\n }\n}\n","// Typography\n// stylelint-disable selector-no-type, selector-max-type, selector-max-specificity, selector-max-id\n\nh1,\n.text-alpha {\n font-weight: 300;\n\n @include fs-8;\n}\n\nh2,\n.text-beta,\n#toctitle {\n @include fs-6;\n}\n\nh3,\n.text-gamma {\n @include fs-5;\n}\n\nh4,\n.text-delta {\n font-weight: 400;\n text-transform: uppercase;\n letter-spacing: 0.1em;\n\n @include fs-2;\n}\n\nh4 code {\n text-transform: none;\n}\n\nh5,\n.text-epsilon {\n @include fs-3;\n}\n\nh6,\n.text-zeta {\n @include fs-2;\n}\n\n.text-small {\n @include fs-2;\n}\n\n.text-mono {\n font-family: $mono-font-family !important;\n}\n\n.text-left {\n text-align: left !important;\n}\n\n.text-center {\n text-align: center !important;\n}\n\n.text-right {\n text-align: right !important;\n}\n","// Labels (not the form kind)\n\n// this :not() prevents a style clash with Mermaid.js's\n// diagram labels, which also use .label\n// for more, see https://github.com/just-the-docs/just-the-docs/issues/1272\n// and the accompanying PR\n.label:not(g),\n.label-blue:not(g) {\n display: inline-block;\n padding: 0.16em 0.56em;\n margin-right: $sp-2;\n margin-left: $sp-2;\n color: $white;\n text-transform: uppercase;\n vertical-align: middle;\n background-color: $blue-100;\n border-radius: 12px;\n\n @include fs-2;\n}\n\n.label-green:not(g) {\n background-color: $green-300;\n}\n\n.label-purple:not(g) {\n background-color: $purple-100;\n}\n\n.label-red:not(g) {\n background-color: $red-300;\n}\n\n.label-yellow:not(g) {\n color: $grey-dk-200;\n background-color: $yellow-200;\n}\n","// Buttons and things that look like buttons\n// stylelint-disable color-named\n\n.btn {\n display: inline-block;\n box-sizing: border-box;\n padding: 0.3em 1em;\n margin: 0;\n font-family: inherit;\n font-size: inherit;\n font-weight: 500;\n line-height: 1.5;\n color: $link-color;\n text-decoration: none;\n vertical-align: baseline;\n cursor: pointer;\n background-color: $base-button-color;\n border-width: 0;\n border-radius: $border-radius;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n appearance: none;\n\n &:focus {\n text-decoration: none;\n outline: none;\n box-shadow: 0 0 0 3px rgba(blue, 0.25);\n }\n\n &:focus:hover,\n &.selected:focus {\n box-shadow: 0 0 0 3px rgba(blue, 0.25);\n }\n\n &:hover,\n &.zeroclipboard-is-hover {\n color: darken($link-color, 2%);\n }\n\n &:hover,\n &:active,\n &.zeroclipboard-is-hover,\n &.zeroclipboard-is-active {\n text-decoration: none;\n background-color: darken($base-button-color, 1%);\n }\n\n &:active,\n &.selected,\n &.zeroclipboard-is-active {\n background-color: darken($base-button-color, 3%);\n background-image: none;\n box-shadow: inset 0 2px 4px rgba(0, 0, 0, 0.15);\n }\n\n &.selected:hover {\n background-color: darken(#dcdcdc, 5%);\n }\n\n &:disabled,\n &.disabled {\n &,\n &:hover {\n color: rgba(102, 102, 102, 0.5);\n cursor: default;\n background-color: rgba(229, 229, 229, 0.5);\n background-image: none;\n box-shadow: none;\n }\n }\n}\n\n.btn-outline {\n color: $link-color;\n background: transparent;\n box-shadow: inset 0 0 0 2px $grey-lt-300;\n\n &:hover,\n &:active,\n &.zeroclipboard-is-hover,\n &.zeroclipboard-is-active {\n color: darken($link-color, 4%);\n text-decoration: none;\n background-color: transparent;\n box-shadow: inset 0 0 0 3px $grey-lt-300;\n }\n\n &:focus {\n text-decoration: none;\n outline: none;\n box-shadow:\n inset 0 0 0 2px $grey-dk-100,\n 0 0 0 3px rgba(blue, 0.25);\n }\n\n &:focus:hover,\n &.selected:focus {\n box-shadow: inset 0 0 0 2px $grey-dk-100;\n }\n}\n\n.btn-primary {\n @include btn-color($white, $btn-primary-color);\n}\n\n.btn-purple {\n @include btn-color($white, $purple-100);\n}\n\n.btn-blue {\n @include btn-color($white, $blue-200);\n}\n\n.btn-green {\n @include btn-color($white, $green-300);\n}\n\n.btn-reset {\n background: none;\n border: none;\n margin: 0;\n text-align: inherit;\n font: inherit;\n border-radius: 0;\n appearance: none;\n}\n","// Colored button\n\n@mixin btn-color($fg, $bg) {\n color: $fg;\n background-color: darken($bg, 2%);\n background-image: linear-gradient(lighten($bg, 5%), darken($bg, 2%));\n box-shadow:\n 0 1px 3px rgba(0, 0, 0, 0.25),\n 0 4px 10px rgba(0, 0, 0, 0.12);\n\n &:hover,\n &.zeroclipboard-is-hover {\n color: $fg;\n background-color: darken($bg, 4%);\n background-image: linear-gradient((lighten($bg, 2%), darken($bg, 4%)));\n }\n\n &:active,\n &.selected,\n &.zeroclipboard-is-active {\n background-color: darken($bg, 5%);\n background-image: none;\n box-shadow: inset 0 2px 4px rgba(0, 0, 0, 0.15);\n }\n\n &.selected:hover {\n background-color: darken($bg, 10%);\n }\n}\n","// Search input and autocomplete\n\n.search {\n position: relative;\n z-index: 2;\n flex-grow: 1;\n height: $sp-10;\n padding: $sp-2;\n transition: padding linear #{$transition-duration * 0.5};\n\n @include mq(md) {\n position: relative !important;\n width: auto !important;\n height: 100% !important;\n padding: 0;\n transition: none;\n }\n}\n\n.search-input-wrap {\n position: relative;\n z-index: 1;\n height: $sp-8;\n overflow: hidden;\n border-radius: $border-radius;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n transition: height linear #{$transition-duration * 0.5};\n\n @include mq(md) {\n position: absolute;\n width: 100%;\n max-width: $search-results-width;\n height: 100% !important;\n border-radius: 0;\n box-shadow: none;\n transition: width ease $transition-duration;\n }\n}\n\n.search-input {\n position: absolute;\n width: 100%;\n height: 100%;\n padding: $sp-2 $gutter-spacing-sm $sp-2 #{$gutter-spacing-sm + $sp-5};\n font-size: 1rem;\n color: $body-text-color;\n background-color: $search-background-color;\n border-top: 0;\n border-right: 0;\n border-bottom: 0;\n border-left: 0;\n border-radius: 0;\n\n @include mq(md) {\n padding: $sp-2 $gutter-spacing-sm $sp-2 #{$gutter-spacing + $sp-5};\n font-size: 0.875rem;\n background-color: $body-background-color;\n transition: padding-left linear #{$transition-duration * 0.5};\n }\n\n &:focus {\n outline: 2px solid $link-color;\n outline-offset: -2px;\n\n + .search-label .search-icon {\n color: $link-color;\n }\n }\n}\n\n.search-label {\n position: absolute;\n display: flex;\n height: 100%;\n padding-left: $gutter-spacing-sm;\n\n @include mq(md) {\n padding-left: $gutter-spacing;\n transition: padding-left linear #{$transition-duration * 0.5};\n }\n\n .search-icon {\n width: #{$sp-4 * 1.2};\n height: #{$sp-4 * 1.2};\n align-self: center;\n color: $grey-dk-000;\n }\n}\n\n.search-results {\n position: absolute;\n left: 0;\n display: none;\n width: 100%;\n max-height: calc(100% - #{$sp-10});\n overflow-y: auto;\n background-color: $search-background-color;\n border-bottom-right-radius: $border-radius;\n border-bottom-left-radius: $border-radius;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n\n @include mq(md) {\n top: 100%;\n width: $search-results-width;\n max-height: calc(100vh - 200%) !important;\n }\n}\n\n.search-results-list {\n padding-left: 0;\n margin-bottom: $sp-1;\n list-style: none;\n @include fs-4;\n\n @include mq(md) {\n @include fs-3;\n }\n}\n\n.search-results-list-item {\n padding: 0;\n margin: 0;\n}\n\n.search-result {\n display: block;\n padding: $sp-1 $sp-3;\n\n &:hover,\n &.active {\n background-color: $feedback-color;\n }\n}\n\n.search-result-title {\n display: block;\n padding-top: $sp-2;\n padding-bottom: $sp-2;\n\n @include mq(sm) {\n display: inline-block;\n width: 40%;\n padding-right: $sp-2;\n vertical-align: top;\n }\n}\n\n.search-result-doc {\n display: flex;\n align-items: center;\n word-wrap: break-word;\n\n &.search-result-doc-parent {\n opacity: 0.5;\n @include fs-3;\n\n @include mq(md) {\n @include fs-2;\n }\n }\n\n .search-result-icon {\n width: $sp-4;\n height: $sp-4;\n margin-right: $sp-2;\n color: $link-color;\n flex-shrink: 0;\n }\n\n .search-result-doc-title {\n overflow: auto;\n }\n}\n\n.search-result-section {\n margin-left: #{$sp-4 + $sp-2};\n word-wrap: break-word;\n}\n\n.search-result-rel-url {\n display: block;\n margin-left: #{$sp-4 + $sp-2};\n overflow: hidden;\n color: $search-result-preview-color;\n text-overflow: ellipsis;\n white-space: nowrap;\n @include fs-1;\n}\n\n.search-result-previews {\n display: block;\n padding-top: $sp-2;\n padding-bottom: $sp-2;\n padding-left: $sp-4;\n margin-left: $sp-2;\n color: $search-result-preview-color;\n word-wrap: break-word;\n border-left: $border;\n border-left-color: $border-color;\n @include fs-2;\n\n @include mq(sm) {\n display: inline-block;\n width: 60%;\n padding-left: $sp-2;\n margin-left: 0;\n vertical-align: top;\n }\n}\n\n.search-result-preview + .search-result-preview {\n margin-top: $sp-1;\n}\n\n.search-result-highlight {\n font-weight: bold;\n}\n\n.search-no-result {\n padding: $sp-2 $sp-3;\n @include fs-3;\n}\n\n.search-button {\n position: fixed;\n right: $sp-4;\n bottom: $sp-4;\n display: flex;\n width: $sp-9;\n height: $sp-9;\n background-color: $search-background-color;\n border: 1px solid rgba($link-color, 0.3);\n border-radius: #{$sp-9 * 0.5};\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n align-items: center;\n justify-content: center;\n}\n\n.search-overlay {\n position: fixed;\n top: 0;\n left: 0;\n z-index: 1;\n width: 0;\n height: 0;\n background-color: rgba(0, 0, 0, 0.3);\n opacity: 0;\n transition:\n opacity ease $transition-duration,\n width 0s $transition-duration,\n height 0s $transition-duration;\n}\n\n.search-active {\n .search {\n position: fixed;\n top: 0;\n left: 0;\n width: 100%;\n height: 100%;\n padding: 0;\n }\n\n .search-input-wrap {\n height: $sp-10;\n border-radius: 0;\n\n @include mq(md) {\n width: $search-results-width;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n }\n }\n\n .search-input {\n background-color: $search-background-color;\n\n @include mq(md) {\n padding-left: 2.3rem;\n }\n }\n\n .search-label {\n @include mq(md) {\n padding-left: 0.6rem;\n }\n }\n\n .search-results {\n display: block;\n }\n\n .search-overlay {\n width: 100%;\n height: 100%;\n opacity: 1;\n transition:\n opacity ease $transition-duration,\n width 0s,\n height 0s;\n }\n\n @include mq(md) {\n .main {\n position: fixed;\n right: 0;\n left: 0;\n }\n }\n\n .main-header {\n padding-top: $sp-10;\n\n @include mq(md) {\n padding-top: 0;\n }\n }\n}\n","// Tables\n// stylelint-disable max-nesting-depth, selector-no-type, selector-max-type\n\n.table-wrapper {\n display: block;\n width: 100%;\n max-width: 100%;\n margin-bottom: $sp-5;\n overflow-x: auto;\n border-radius: $border-radius;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n}\n\ntable {\n display: table;\n min-width: 100%;\n border-collapse: separate;\n}\n\nth,\ntd {\n min-width: 7.5rem;\n padding: $sp-2 $sp-3;\n background-color: $table-background-color;\n border-bottom: $border rgba($border-color, 0.5);\n border-left: $border $border-color;\n\n @include fs-3;\n\n &:first-of-type {\n border-left: 0;\n }\n}\n\ntbody {\n tr {\n &:last-of-type {\n th,\n td {\n border-bottom: 0;\n }\n\n td {\n padding-bottom: $sp-3;\n }\n }\n }\n}\n\nthead {\n th {\n border-bottom: $border $border-color;\n }\n}\n","// Code and syntax highlighting\n// stylelint-disable selector-no-qualifying-type, declaration-block-semicolon-newline-after,declaration-block-single-line-max-declarations, selector-no-type, selector-max-type, scss/comment-no-empty\n\n// {% raw %}\n\n// This instruction applies to all queues not within 'pre' or 'figure', avoiding 'code' generated by the highlight.\n:not(pre, figure) {\n & > code {\n padding: 0.2em 0.15em;\n font-weight: 400;\n background-color: $code-background-color;\n border: $border $border-color;\n border-radius: $border-radius;\n }\n}\n\n// Avoid appearance of dark border around visited code links in Safari\na:visited code {\n border-color: $border-color;\n}\n\n// Content structure for highlighted code blocks using fences or Liquid\n//\n// ```[LANG]...```, no kramdown line_numbers:\n// div.[language-LANG.]highlighter-rouge > div.highlight > pre.highlight > code\n//\n// ```[LANG]...```, kramdown line_numbers = true:\n// div.[language-LANG.]highlighter-rouge > div.highlight > pre.highlight > code\n// > div.table-wrapper > table.rouge-table > tbody > tr\n// > td.rouge-gutter.gl > pre.lineno\n// | td.rouge-code > pre\n//\n// {% highlight LANG %}...{% endhighlight %}:\n// figure.highlight > pre > code.language-LANG\n//\n// {% highlight LANG linenos %}...{% endhighlight %}:\n// figure.highlight > pre > code.language-LANG\n// > div.table-wrapper > table.rouge-table > tbody > tr\n// > td.gutter.gl > pre.lineno\n// | td.code > pre\n//\n// ----...---- (AsciiDoc)\n// div.listingblock > div.content > pre.rouge.highlight\n//\n// fix_linenos removes the outermost pre when it encloses table.rouge-table\n//\n// See docs/index-test.md for some tests.\n//\n// No kramdown line_numbers: fences and Liquid highlighting look the same.\n// Kramdown line_numbers = true: fences have a wider gutter than with Liquid?\n\n// ```[LANG]...```\n// or in AsciiDoc:\n//\n// ----\n// ...\n// ----\n\n// the code may appear with 3 different types:\n// container \\ case: default case, code with line number, code with html rendering\n// top level: div.highlighter-rouge, figure.highlight, figure.highlight\n// second level: div.highlight, div.table-wrapper, pre.highlight\n// third level: pre.highlight, td.code, absent\n// last level: code, pre, code (optionality)\n// highlighter level: span, span, span\n// the spacing are only in the second level for case 1, 3 and in the third level for case 2\n// in AsciiDoc, there is a parent container that contains optionally a title and the content.\n\n// select top level container\ndiv.highlighter-rouge,\ndiv.listingblock > div.content,\nfigure.highlight {\n margin-top: 0;\n margin-bottom: $sp-3;\n background-color: $code-background-color;\n border-radius: $border-radius;\n box-shadow: none;\n -webkit-overflow-scrolling: touch;\n position: relative;\n padding: 0;\n\n // copy button (or other button)\n // the button appear only when there is a hover on the code or focus on button\n > button {\n width: $sp-3;\n opacity: 0;\n position: absolute;\n top: 0;\n right: 0;\n padding: $sp-3;\n border: none;\n background: none;\n color: $body-text-color;\n box-sizing: content-box;\n\n svg {\n fill: $body-text-color;\n }\n\n &:active {\n text-decoration: none;\n outline: none;\n opacity: 1;\n }\n\n &:focus {\n opacity: 1;\n outline: 2px solid $link-color;\n }\n }\n\n // the button can be seen by doing a simple hover in the code, there is no need to go over the location of the button\n &:hover {\n > button {\n cursor: copy;\n opacity: 1;\n }\n }\n}\n\n// setting the spacing and scrollbar on the second level for the first case\n// remove all space on the second and third level\n// this is a mixin to accommodate for the slightly different structures generated via Markdown vs AsciiDoc\n@mixin scroll-and-spacing($code-div, $pre-select) {\n #{$code-div} {\n overflow-x: auto;\n padding: $sp-3;\n margin: 0;\n border: 1px solid $body-text-color;\n border-radius: $border-radius;\n }\n\n #{$pre-select},\n code {\n padding: 0;\n margin: 0;\n border: 0;\n }\n}\n\n// for Markdown\ndiv.highlighter-rouge {\n @include scroll-and-spacing(\"div.highlight\", \"pre.highlight\");\n}\n\n// for AsciiDoc. we also need to fix the margins for its parent container.\ndiv.listingblock {\n margin-top: 0;\n margin-bottom: $sp-3;\n\n @include scroll-and-spacing(\"div.content\", \"div.content > pre\");\n}\n\n// {% highlight LANG %}...{% endhighlight %},\n// {% highlight LANG linenos %}...{% endhighlight %}:\n\n// setting the spacing and scrollbar on the second level for the thirt case\n// the css rule are apply only to the last code enviroment\n// setting the scroolbar\nfigure.highlight {\n pre,\n :not(pre) > code {\n overflow-x: auto;\n padding: $sp-3;\n margin: 0;\n border: 1px solid $body-text-color;\n border-radius: $border-radius;\n }\n}\n\n// ```[LANG]...```, kramdown line_numbers = true,\n// {% highlight LANG linenos %}...{% endhighlight %}:\n\n// setting the spacing and scrollbar on the thirt level for the second case\n.highlight .table-wrapper {\n padding: $sp-3 0;\n margin: 0;\n border: 0;\n box-shadow: none;\n\n td,\n pre {\n min-width: 0;\n padding: 0;\n background-color: $code-background-color;\n border: 0;\n\n @include fs-2;\n }\n\n td.gl {\n width: 1em;\n padding-right: $sp-3;\n padding-left: $sp-3;\n }\n\n pre {\n margin: 0;\n line-height: 2;\n }\n}\n\n// Code examples: html render of a code\n.code-example,\n.listingblock > .title {\n padding: $sp-3;\n margin-bottom: $sp-3;\n overflow: auto;\n border: 1px solid $border-color;\n border-radius: $border-radius;\n\n + .highlighter-rouge,\n + .sectionbody .listingblock,\n + .content,\n + figure.highlight {\n position: relative;\n margin-top: -$sp-4;\n border-right: 1px solid $border-color;\n border-bottom: 1px solid $border-color;\n border-left: 1px solid $border-color;\n border-top-left-radius: 0;\n border-top-right-radius: 0;\n }\n}\n\n// Mermaid diagram code blocks should be left unstyled.\ncode.language-mermaid {\n padding: 0;\n background-color: inherit;\n border: 0;\n}\n\n// Override OneDarkJekyll Colors for Code Blocks\n.highlight,\npre.highlight {\n background: $code-background-color; // Code Background\n // For Backwards Compatibility Before $code-linenumber-color was added\n @if variable-exists(code-linenumber-color) {\n color: $code-linenumber-color; // Code Line Numbers\n } @else {\n color: $body-text-color; // Code Line Numbers\n }\n}\n\n// Override OneDarkJekyll Colors for Code Blocks\n.highlight pre {\n background: $code-background-color; // Code Background\n}\n\n// {% endraw %}\n","// Utility classes for colors\n\n// Text colors\n\n.text-grey-dk-000 {\n color: $grey-dk-000 !important;\n}\n\n.text-grey-dk-100 {\n color: $grey-dk-100 !important;\n}\n\n.text-grey-dk-200 {\n color: $grey-dk-200 !important;\n}\n\n.text-grey-dk-250 {\n color: $grey-dk-250 !important;\n}\n\n.text-grey-dk-300 {\n color: $grey-dk-300 !important;\n}\n\n.text-grey-lt-000 {\n color: $grey-lt-000 !important;\n}\n\n.text-grey-lt-100 {\n color: $grey-lt-100 !important;\n}\n\n.text-grey-lt-200 {\n color: $grey-lt-200 !important;\n}\n\n.text-grey-lt-300 {\n color: $grey-lt-300 !important;\n}\n\n.text-blue-000 {\n color: $blue-000 !important;\n}\n\n.text-blue-100 {\n color: $blue-100 !important;\n}\n\n.text-blue-200 {\n color: $blue-200 !important;\n}\n\n.text-blue-300 {\n color: $blue-300 !important;\n}\n\n.text-green-000 {\n color: $green-000 !important;\n}\n\n.text-green-100 {\n color: $green-100 !important;\n}\n\n.text-green-200 {\n color: $green-200 !important;\n}\n\n.text-green-300 {\n color: $green-300 !important;\n}\n\n.text-purple-000 {\n color: $purple-000 !important;\n}\n\n.text-purple-100 {\n color: $purple-100 !important;\n}\n\n.text-purple-200 {\n color: $purple-200 !important;\n}\n\n.text-purple-300 {\n color: $purple-300 !important;\n}\n\n.text-yellow-000 {\n color: $yellow-000 !important;\n}\n\n.text-yellow-100 {\n color: $yellow-100 !important;\n}\n\n.text-yellow-200 {\n color: $yellow-200 !important;\n}\n\n.text-yellow-300 {\n color: $yellow-300 !important;\n}\n\n.text-red-000 {\n color: $red-000 !important;\n}\n\n.text-red-100 {\n color: $red-100 !important;\n}\n\n.text-red-200 {\n color: $red-200 !important;\n}\n\n.text-red-300 {\n color: $red-300 !important;\n}\n\n// Background colors\n\n.bg-grey-dk-000 {\n background-color: $grey-dk-000 !important;\n}\n\n.bg-grey-dk-100 {\n background-color: $grey-dk-100 !important;\n}\n\n.bg-grey-dk-200 {\n background-color: $grey-dk-200 !important;\n}\n\n.bg-grey-dk-250 {\n background-color: $grey-dk-250 !important;\n}\n\n.bg-grey-dk-300 {\n background-color: $grey-dk-300 !important;\n}\n\n.bg-grey-lt-000 {\n background-color: $grey-lt-000 !important;\n}\n\n.bg-grey-lt-100 {\n background-color: $grey-lt-100 !important;\n}\n\n.bg-grey-lt-200 {\n background-color: $grey-lt-200 !important;\n}\n\n.bg-grey-lt-300 {\n background-color: $grey-lt-300 !important;\n}\n\n.bg-blue-000 {\n background-color: $blue-000 !important;\n}\n\n.bg-blue-100 {\n background-color: $blue-100 !important;\n}\n\n.bg-blue-200 {\n background-color: $blue-200 !important;\n}\n\n.bg-blue-300 {\n background-color: $blue-300 !important;\n}\n\n.bg-green-000 {\n background-color: $green-000 !important;\n}\n\n.bg-green-100 {\n background-color: $green-100 !important;\n}\n\n.bg-green-200 {\n background-color: $green-200 !important;\n}\n\n.bg-green-300 {\n background-color: $green-300 !important;\n}\n\n.bg-purple-000 {\n background-color: $purple-000 !important;\n}\n\n.bg-purple-100 {\n background-color: $purple-100 !important;\n}\n\n.bg-purple-200 {\n background-color: $purple-200 !important;\n}\n\n.bg-purple-300 {\n background-color: $purple-300 !important;\n}\n\n.bg-yellow-000 {\n background-color: $yellow-000 !important;\n}\n\n.bg-yellow-100 {\n background-color: $yellow-100 !important;\n}\n\n.bg-yellow-200 {\n background-color: $yellow-200 !important;\n}\n\n.bg-yellow-300 {\n background-color: $yellow-300 !important;\n}\n\n.bg-red-000 {\n background-color: $red-000 !important;\n}\n\n.bg-red-100 {\n background-color: $red-100 !important;\n}\n\n.bg-red-200 {\n background-color: $red-200 !important;\n}\n\n.bg-red-300 {\n background-color: $red-300 !important;\n}\n","// Utility classes for layout\n\n// Display\n\n.d-block {\n display: block !important;\n}\n\n.d-flex {\n display: flex !important;\n}\n\n.d-inline {\n display: inline !important;\n}\n\n.d-inline-block {\n display: inline-block !important;\n}\n\n.d-none {\n display: none !important;\n}\n\n// Screenreader-only\n\n.sr-only {\n position: absolute;\n width: 1px;\n height: 1px;\n padding: 0;\n margin: -1px;\n overflow: hidden;\n clip: rect(0, 0, 0, 0);\n white-space: nowrap;\n border-width: 0;\n}\n\n@each $media-query in map-keys($media-queries) {\n @for $i from 1 through length($spacers) {\n @include mq($media-query) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .d-sm-block, .d-md-none, .d-lg-inline\n .d-#{$media-query}-block {\n display: block !important;\n }\n .d-#{$media-query}-flex {\n display: flex !important;\n }\n .d-#{$media-query}-inline {\n display: inline !important;\n }\n .d-#{$media-query}-inline-block {\n display: inline-block !important;\n }\n .d-#{$media-query}-none {\n display: none !important;\n }\n }\n }\n}\n\n// Horizontal alignment\n\n.float-left {\n float: left !important;\n}\n\n.float-right {\n float: right !important;\n}\n\n.flex-justify-start {\n justify-content: flex-start !important;\n}\n\n.flex-justify-end {\n justify-content: flex-end !important;\n}\n\n.flex-justify-between {\n justify-content: space-between !important;\n}\n\n.flex-justify-around {\n justify-content: space-around !important;\n}\n\n// Vertical alignment\n\n.v-align-baseline {\n vertical-align: baseline !important;\n}\n\n.v-align-bottom {\n vertical-align: bottom !important;\n}\n\n.v-align-middle {\n vertical-align: middle !important;\n}\n\n.v-align-text-bottom {\n vertical-align: text-bottom !important;\n}\n\n.v-align-text-top {\n vertical-align: text-top !important;\n}\n\n.v-align-top {\n vertical-align: top !important;\n}\n","// Utility classes for typography\n\n.fs-1 {\n @include fs-1;\n}\n\n.fs-2 {\n @include fs-2;\n}\n\n.fs-3 {\n @include fs-3;\n}\n\n.fs-4 {\n @include fs-4;\n}\n\n.fs-5 {\n @include fs-5;\n}\n\n.fs-6 {\n @include fs-6;\n}\n\n.fs-7 {\n @include fs-7;\n}\n\n.fs-8 {\n @include fs-8;\n}\n\n.fs-9 {\n @include fs-9;\n}\n\n.fs-10 {\n @include fs-10;\n}\n\n.fw-300 {\n font-weight: 300 !important;\n}\n\n.fw-400 {\n font-weight: 400 !important;\n}\n\n.fw-500 {\n font-weight: 500 !important;\n}\n\n.fw-700 {\n font-weight: 700 !important;\n}\n\n.lh-0 {\n line-height: 0 !important;\n}\n\n.lh-default {\n line-height: $body-line-height;\n}\n\n.lh-tight {\n line-height: $body-heading-line-height;\n}\n\n.ls-5 {\n letter-spacing: 0.05em !important;\n}\n\n.ls-10 {\n letter-spacing: 0.1em !important;\n}\n\n.ls-0 {\n letter-spacing: 0 !important;\n}\n\n.text-uppercase {\n text-transform: uppercase !important;\n}\n","// Utility classes for lists\n\n// stylelint-disable selector-max-type\n\n.list-style-none {\n padding: 0 !important;\n margin: 0 !important;\n list-style: none !important;\n\n li {\n &::before {\n display: none !important;\n }\n }\n}\n","// Utility classes for margins and padding\n\n// stylelint-disable block-opening-brace-space-after, block-opening-brace-space-before\n\n// Margin spacer utilities\n\n.mx-auto {\n margin-right: auto !important;\n margin-left: auto !important;\n}\n\n@for $i from 1 through length($spacers) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .m-0, .m-1, .m-2...\n .m-#{$scale} {\n margin: #{$size} !important;\n }\n .mt-#{$scale} {\n margin-top: #{$size} !important;\n }\n .mr-#{$scale} {\n margin-right: #{$size} !important;\n }\n .mb-#{$scale} {\n margin-bottom: #{$size} !important;\n }\n .ml-#{$scale} {\n margin-left: #{$size} !important;\n }\n\n .mx-#{$scale} {\n margin-right: #{$size} !important;\n margin-left: #{$size} !important;\n }\n\n .my-#{$scale} {\n margin-top: #{$size} !important;\n margin-bottom: #{$size} !important;\n }\n\n .mxn-#{$scale} {\n margin-right: -#{$size} !important;\n margin-left: -#{$size} !important;\n }\n .mx-#{$scale}-auto {\n margin-right: auto !important;\n margin-left: auto !important;\n }\n}\n\n@each $media-query in map-keys($media-queries) {\n @for $i from 1 through length($spacers) {\n @include mq($media-query) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .m-sm-0, .m-md-1, .m-lg-2...\n .m-#{$media-query}-#{$scale} {\n margin: #{$size} !important;\n }\n .mt-#{$media-query}-#{$scale} {\n margin-top: #{$size} !important;\n }\n .mr-#{$media-query}-#{$scale} {\n margin-right: #{$size} !important;\n }\n .mb-#{$media-query}-#{$scale} {\n margin-bottom: #{$size} !important;\n }\n .ml-#{$media-query}-#{$scale} {\n margin-left: #{$size} !important;\n }\n\n .mx-#{$media-query}-#{$scale} {\n margin-right: #{$size} !important;\n margin-left: #{$size} !important;\n }\n\n .my-#{$media-query}-#{$scale} {\n margin-top: #{$size} !important;\n margin-bottom: #{$size} !important;\n }\n\n .mxn-#{$media-query}-#{$scale} {\n margin-right: -#{$size} !important;\n margin-left: -#{$size} !important;\n }\n }\n }\n}\n\n// Padding spacer utilities\n\n@for $i from 1 through length($spacers) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .p-0, .p-1, .p-2...\n .p-#{$scale} {\n padding: #{$size} !important;\n }\n .pt-#{$scale} {\n padding-top: #{$size} !important;\n }\n .pr-#{$scale} {\n padding-right: #{$size} !important;\n }\n .pb-#{$scale} {\n padding-bottom: #{$size} !important;\n }\n .pl-#{$scale} {\n padding-left: #{$size} !important;\n }\n\n .px-#{$scale} {\n padding-right: #{$size} !important;\n padding-left: #{$size} !important;\n }\n\n .py-#{$scale} {\n padding-top: #{$size} !important;\n padding-bottom: #{$size} !important;\n }\n}\n\n@each $media-query in map-keys($media-queries) {\n @include mq($media-query) {\n @for $i from 1 through length($spacers) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .p-sm-0, .p-md-1, .p-lg-2...\n .p-#{$media-query}-#{$scale} {\n padding: #{$size} !important;\n }\n .pt-#{$media-query}-#{$scale} {\n padding-top: #{$size} !important;\n }\n .pr-#{$media-query}-#{$scale} {\n padding-right: #{$size} !important;\n }\n .pb-#{$media-query}-#{$scale} {\n padding-bottom: #{$size} !important;\n }\n .pl-#{$media-query}-#{$scale} {\n padding-left: #{$size} !important;\n }\n\n .px-#{$media-query}-#{$scale} {\n padding-right: #{$size} !important;\n padding-left: #{$size} !important;\n }\n\n .py-#{$media-query}-#{$scale} {\n padding-top: #{$size} !important;\n padding-bottom: #{$size} !important;\n }\n }\n }\n}\n","// stylelint-disable selector-max-specificity, selector-max-id, selector-max-type, selector-no-qualifying-type\n\n@media print {\n .site-footer,\n .site-button,\n #edit-this-page,\n #back-to-top,\n .site-nav,\n .main-header {\n display: none !important;\n }\n\n hr {\n margin-top: 1rem;\n margin-bottom: 1rem;\n }\n\n .side-bar {\n width: 100%;\n height: auto;\n border-right: 0 !important;\n }\n\n .site-header {\n border-bottom: 1px solid $border-color;\n }\n\n .site-title {\n font-size: 1rem !important;\n font-weight: 700 !important;\n }\n\n .text-small {\n font-size: 8pt !important;\n }\n\n pre.highlight {\n border: 1px solid $border-color;\n }\n\n .main {\n max-width: none;\n margin-left: 0;\n }\n}\n","// Skipnav\n// Skip to main content\n\na.skip-to-main {\n left: -999px;\n position: absolute;\n top: auto;\n width: 1px;\n height: 1px;\n overflow: hidden;\n z-index: -999;\n}\n\na.skip-to-main:focus,\na.skip-to-main:active {\n color: $link-color;\n background-color: $body-background-color;\n left: auto;\n top: auto;\n width: 30%;\n height: auto;\n overflow: auto;\n margin: 10px 35%;\n padding: 5px;\n border-radius: 15px;\n border: 4px solid $btn-primary-color;\n text-align: center;\n font-size: 1.2em;\n z-index: 999;\n}\n","\n@import \"./support/support\";\n@import \"./custom/setup\";\n@import \"./color_schemes/light\";\n\n@import \"./modules\";\ndiv.opaque {\n background-color: $body-background-color;\n}\n\np.tip, blockquote.tip {\n border: 1px $green-000 solid;\n border-left: $border-radius solid $green-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n \n &::before {\n color: $green-300;\n content: \"Tip\";\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n \n > .tip-title {\n color: $green-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\np.tip-title, blockquote.tip-title {\n border: 1px $green-000 solid;\n border-left: $border-radius solid $green-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n > p:first-child {\n margin-top: 0;\n margin-bottom: 0;\n color: $green-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\nblockquote.tip {\n margin-left: 0;\n margin-right: 0;\n\n > p:first-child {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\nblockquote.tip-title {\n margin-left: 0;\n margin-right: 0;\n\n > p:nth-child(2) {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\n\n\np.note, blockquote.note {\n border: 1px $blue-000 solid;\n border-left: $border-radius solid $blue-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n \n &::before {\n color: $blue-300;\n content: \"Note\";\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n \n > .note-title {\n color: $blue-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\np.note-title, blockquote.note-title {\n border: 1px $blue-000 solid;\n border-left: $border-radius solid $blue-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n > p:first-child {\n margin-top: 0;\n margin-bottom: 0;\n color: $blue-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\nblockquote.note {\n margin-left: 0;\n margin-right: 0;\n\n > p:first-child {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\nblockquote.note-title {\n margin-left: 0;\n margin-right: 0;\n\n > p:nth-child(2) {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\n\n\np.warning, blockquote.warning {\n border: 1px $yellow-000 solid;\n border-left: $border-radius solid $yellow-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n \n &::before {\n color: $yellow-300;\n content: \"Warning\";\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n \n > .warning-title {\n color: $yellow-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\np.warning-title, blockquote.warning-title {\n border: 1px $yellow-000 solid;\n border-left: $border-radius solid $yellow-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n > p:first-child {\n margin-top: 0;\n margin-bottom: 0;\n color: $yellow-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\nblockquote.warning {\n margin-left: 0;\n margin-right: 0;\n\n > p:first-child {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\nblockquote.warning-title {\n margin-left: 0;\n margin-right: 0;\n\n > p:nth-child(2) {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\n\n@import \"./custom/custom\";\n\n\n"],"file":"just-the-docs-light.css"} \ No newline at end of file diff --git a/main/assets/css/just-the-docs-meshtastic-dark.css.map b/main/assets/css/just-the-docs-meshtastic-dark.css.map index 7f9f2dd50b..874528ebc3 100644 --- a/main/assets/css/just-the-docs-meshtastic-dark.css.map +++ b/main/assets/css/just-the-docs-meshtastic-dark.css.map @@ -1 +1 @@ -{"version":3,"sourceRoot":"","sources":["../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/vendor/accessible-pygments/github-light.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/vendor/normalize.scss/normalize.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/base.scss","../../_sass/color_schemes/meshtastic-dark.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/support/mixins/_typography.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/support/mixins/_layout.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/support/_variables.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/layout.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/content.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/navigation.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/typography.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/labels.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/buttons.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/support/mixins/_buttons.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/search.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/tables.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/code.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/utilities/_colors.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/utilities/_layout.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/utilities/_typography.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/utilities/_lists.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/utilities/_spacing.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/print.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/skiptomain.scss","just-the-docs-meshtastic-dark.scss"],"names":[],"mappings":";AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAUA;EAAkB;;;AAClB;EAAgB;EAAiB;AACjC;EAAkB;EAAiB;AACnC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAkB;EAAiB;AACnC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAqB;AACtC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAoB;AACrC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAgB;EAAiB;AACjC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AChFlC;AAEA;AAAA;AAGA;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAAA;AAKA;EACE;EACA;EACA;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;EACA;;;AAGF;AAAA;AAAA;AAIA;AAAA;EAEE;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;AAAA;EAGE;EACA;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;EAEE;EACA;EACA;EACA;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAAA;AAKA;AAAA;AAAA;AAAA;AAAA;EAKE;EACA;EACA;EACA;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;AAEE;EACA;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;AAEE;EACA;;;AAGF;AAAA;AAAA;AAIA;AAAA;AAAA;AAAA;EAIE;;;AAGF;AAAA;AAAA;AAIA;AAAA;AAAA;AAAA;EAIE;EACA;;;AAGF;AAAA;AAAA;AAIA;AAAA;AAAA;AAAA;EAIE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAOA;EACE;EACA;EACA;EACA;EACA;EACA;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;EAEE;EACA;;;AAGF;AAAA;AAAA;AAIA;AAAA;EAEE;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AC1VF;EACE,cCGa;;;ADAf;EACE;;;AAGF;EACE;;AEmBA;EACE;;AClBA;EHHJ;IEyBI;;;;AFnBJ;EACE,aIfiB;EJgBjB;EACA,aIbiB;EJcjB,OCTgB;EDUhB,kBCZsB;EDatB;;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAYE;;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAOE;EACA;EACA;EACA,aI1CyB;EJ2CzB,OCvCmB;;;AD0CrB;EACE;EACA;;;AAGF;EACE,OC7CW;ED8CX;;;AAGF;EACE;EACA,uBCvCa;EDwCb;;AAEA;EACE;;;AAIJ;EACE,aIvEiB;EJwEjB;EACA,aIvEiB;;;AJ0EnB;AAAA;EAEE;;;AAGF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;EACA;EACA,kBCvEa;EDwEb;;;AAIF;EACE;EAGA;EACA;EACA;EACA;;;AK7GF;EACE;EACA;EACA;EACA,kBJKc;;AEGZ;EEZJ;IAOI;IACA;IACA,ODwFW;ICvFX;IACA;IACA;;;AFAA;EEZJ;IAgBI;IACA,WD+EQ;;;ADpFR;EEQF;IAEI,aD2ES;;;ADrFX;EEQF;IAQI;;;AAOF;EACE;EACA,kBJ5BU;;AEGZ;EEuBA;IAKI;IACA,kBJjCgB;;;AIoClB;EACE;;AFjCJ;EEgCE;IAII;;;;AAOV;EACE;;AF5CE;EE2CJ;IAII;IACA,WDyCY;;;;ACrChB;EACE,aDaK;ECZL,gBDYK;EDvDL,eCuDK;EDtDL,cCsDK;;ADlEH;EEoDJ;IFrCI,eCqDG;IDpDH,cCoDG;;;ADpEH;EEoDJ;IAOI,aDSG;ICRH,gBDQG;;;;ACJP;EACE;EACA;;AFlEE;EEgEJ;IAKI;IACA;IACA,QDmBY;;;;ACfhB;AAAA;AAAA;EAGE;;AF9EE;EE2EJ;AAAA;AAAA;IAMI,ODGQ;;;;ACCZ;EACE;;AAEA;EACE;;AFzFA;EEqFJ;IAQI;IACA,aDxBG;ICyBH,gBD7BG;IC8BH;IACA;;;;AAIJ;EACE;EACA,YDbc;ECcd;;AFxGE;EEqGJ;IAMI,QDjBY;ICkBZ,YDlBY;ICmBZ;;;;AAIJ;EACE;EACA;EACA;EACA;EACA,aDrDK;ECsDL,gBDtDK;ECuDL,OJzHmB;EEYnB,eCuDK;EDtDL,cCsDK;;ADlEH;EEiHJ;IFlGI,eCqDG;IDpDH,cCoDG;;;AF/BL;EACE;;ACtCA;EEiHJ;IHvEI;IACA,aEhDuB;;;ADKvB;EEiHJ;IAcI,aD/DG;ICgEH,gBDhEG;;;;AC+EP;EACE;EACA;EACA,SDhFK;ECiFL;;;AFnJE;EEuJF;IACE;;;AAIJ;EACE;;;AAQF;EACE;;;AAOF;EACE;EACA;EACA;EACA,aD/GK;ECgHL,gBDhHK;EDvDL,eCuDK;EDtDL,cCsDK;;ADlEH;EE6KJ;IF9JI,eCqDG;IDpDH,cCoDG;;;AFvEL;EACE;;ACEA;EE6KJ;IH3KI;;;ACFA;EE6KJ;IAYI;IACA;;;;AAIJ;EACE,OD5HK;EC6HL,QD7HK;EC8HL,OJ/LW;;;AKXb;EACE,aFEoB;;AEApB;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAOE;;AAGF;EACE;EACA;;AAGF;AAAA;EAEE;;AAIA;EACE,YF+CC;;AE3CL;EACE;EACA;;AAEA;EACE;;AAEA;EACE;EACA;EACA;EACA,OFfM;EEgBN;EACA;;AJ1BN;EACE;;ACRA;EG2BE;IJfF;;;ACZA;EG2BE;IAUI;;;AAIJ;EACE;;AAGE;EACE;EACA;;AAOV;EACE;;AAGE;EACE;EACA;EACA,OF7CM;EE8CN;;AAMJ;EACE;;AAIJ;EACE;EACA;;AAKF;EACE;;AAGF;EACE;;AAGF;EACE;EACA;;AAGF;AAAA;EAEE;;AAGF;EACE;EACA;EACA;;AAEA;EACE;;AAIJ;EACE;EACA;EACA;;AAmBE;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EACE;;AASF;AAAA;AAAA;AAAA;AAAA;AAAA;EAEE;;AAKN;EACE;EACA;EACA,OFnFG;EEoFH;EACA,eFzFG;EE0FH,cF1FG;EE2FH;;AH1JA;EGmJF;IAUI;IACA;;;AAGF;EACE;EACA;EACA;EACA,OLnKO;EKoKP;;AAYF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EACE;;AAIJ;EACE;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAOE;EACA;EACA;;AAEA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAKE;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EACE;;AAIJ;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAWE,YF9JG;;;AG3EP;EACE;EACA;EACA;EACA;;AAEA;EACE;EACA;;ALoBF;EACE;;AClBA;EILF;IL2BE;;;ACtBA;EDOF;IACE;;;ACRA;EILF;ILiBE;;;AKPA;EACE;EACA,YH+DC;EG9DD,aHuDC;EGtDD,gBHsDC;EGrDD;EAEE,eH0DD;EGzDC,cHqDD;;ADlEH;EIKA;IAeI,YHgDD;IG/CC;IAEE,eH6CH;IG5CG,cH4CH;;;AGrCD;EACE,OHkCD;EGjCC,QHiCD;EGhCC;;AAGF;EACE;EACA;;AAGF;EAEE;EACA;;AASJ;EACE;EAEE;EAGF,OHUC;EGTD,QHSC;EGRD;EACA,ON7DO;;AEFT;EIsDA;IAYI,OHED;IGDC,QHCD;IGAC;;;AAGF;EACE;;AAQA;EACE;;AAKN;EACE;EACA,cHvBC;EGwBD;;AAEA;EACE;;AAEA;EACE,ONzFa;;AM4Ff;EACE,ON7Fa;;AMmGjB;EAEI;;AAMJ;EACE;;;AAMR;EACE;EACA;EACA;EACA;EACA;;ALhIA;EACE;;ACEA;EIwHJ;ILtHI;;;ACFA;EIwHJ;IASI;IACA,YHhEG;IGiEH;;EAEA;IACE;;;;AAMJ;EACE;;AAEA;EACE;;AAGE;EACE,ONlJG;;AMqJL;EACE,ONtJG;;;AM+Jb;EACE;EACA;;ALtKA;EACE;;ACEA;EIiKJ;IL/JI;;;AKoKF;EACE;EACA;EACA;EACA;EACA;;AAGF;EACE;EACA;EACA;EACA;;AJlLA;EIiKJ;IAqBI,eHpHG;;;;ADlEH;EI4LJ;IAEI;;;;AAIJ;EACE;EACA,eHnIK;EGoIL;;;AAGF;EACE;;AL5MA;EACE;;ACEA;EIwMJ;ILtMI;;;AK0MF;EACE;;AAGF;EACE;EACA,cHlJG;EGmJH,aHnJG;EGoJH,OHpMU;EGqMV;;AAIA;EACE;;;ACrON;AAAA;EAEE;;ANoEA;AAAA;EACE;EACA,aElEuB;;ADKvB;EKXJ;AAAA;IN4EI;;;;AA5BF;AAAA;AAAA;EACE;;ACtCA;EKJJ;AAAA;AAAA;IN8CI;IACA,aEhDuB;;;;AFgCzB;AAAA;EACE;;AC5BA;EKEJ;AAAA;IN8BI;;;;AMzBJ;AAAA;EAEE;EACA;EACA;;ANdA;AAAA;EACE;;ACEA;EKOJ;AAAA;INLI;;;;AMcJ;EACE;;;ANVA;AAAA;EACE;;ACRA;EKoBJ;AAAA;INRI;;;;AAfF;AAAA;EACE;;ACEA;EKyBJ;AAAA;INvBI;;;;AALF;EACE;;ACEA;EK8BJ;IN5BI;;;;AMgCJ;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;ACvDF;AAAA;EAEE;EACA;EACA,cLoEK;EKnEL,aLmEK;EKlEL,OLiBM;EKhBN;EACA;EACA,kBL6BS;EK5BT;;APLA;AAAA;EACE;;ACEA;EMRJ;AAAA;IPUI;;;;AOKJ;EACE,kBL4BU;;;AKzBZ;EACE,kBLcW;;;AKXb;EACE,kBL4BQ;;;AKzBV;EACE,OLFY;EKGZ,kBLkBW;;;AMlDb;EACE;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA,OTIW;ESHX;EACA;EACA;EACA,kBTiBkB;EShBlB;EACA,eNyEc;EMxEd,YACE;EAEF;;AAEA;EACE;EACA;EACA;;AAGF;EAEE;;AAGF;EAEE;;AAGF;EAIE;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;AAKA;EAEE;EACA;EACA;EACA;EACA;;;AAKN;EACE,OT1DW;ES2DX;EACA;;AAEA;EAIE;EACA;EACA;EACA;;AAGF;EACE;EACA;EACA,YACE;;AAIJ;EAEE;;;AAIJ;ECnGE,OP0BM;EOzBN;EACA;EACA,YACE;;AAGF;EAEE,OPiBI;EOhBJ;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;;ADgFJ;ECvGE,OP0BM;EOzBN;EACA;EACA,YACE;;AAGF;EAEE,OPiBI;EOhBJ;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;;ADoFJ;EC3GE,OP0BM;EOzBN;EACA;EACA,YACE;;AAGF;EAEE,OPiBI;EOhBJ;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;;ADwFJ;EC/GE,OP0BM;EOzBN;EACA;EACA,YACE;;AAGF;EAEE,OPiBI;EOhBJ;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;;AD4FJ;EACE;EACA;EACA;EACA;EACA;EACA;EACA;;;AE3HF;EACE;EACA;EACA;EACA,QRgFM;EQ/EN,SRuEK;EQtEL;;ATME;ESZJ;IASI;IACA;IACA;IACA;IACA;;;;AAIJ;EACE;EACA;EACA,QR8DK;EQ7DL;EACA,eRmEc;EQlEd,YACE;EAEF;;ATdE;ESKJ;IAYI;IACA;IACA,WRwEmB;IQvEnB;IACA;IACA;IACA;;;;AAIJ;EACE;EACA;EACA;EACA;EACA;EACA,OXnCgB;EWoChB,kBXTwB;EWUxB;EACA;EACA;EACA;EACA;;ATvCE;ES2BJ;IAeI;IACA;IACA,kBXhDoB;IWiDpB;;;AAGF;EACE;EACA;;AAEA;EACE,OXnDO;;;AWwDb;EACE;EACA;EACA;EACA,cRIK;;ADlEH;ES0DJ;IAOI,cRGG;IQFH;;;AAGF;EACE;EACA;EACA;EACA,ORzDU;;;AQ6Dd;EACE;EACA;EACA;EACA;EACA;EACA;EACA,kBX3DwB;EW4DxB,4BRRc;EQSd,2BRTc;EQUd,YACE;;ATxFA;ES6EJ;IAeI;IACA,ORFmB;IQGnB;;;;AAIJ;EACE;EACA,eRrCK;EQsCL;;AVpFA;EACE;;AClBA;ESkGJ;IV5EI;;;ACtBA;EDOF;IACE;;;ACRA;ESkGJ;IVtFI;;;;AUiGJ;EACE;EACA;;;AAGF;EACE;EACA;;AAEA;EAEE,kBXlGa;;;AWsGjB;EACE;EACA,aR9DK;EQ+DL,gBR/DK;;ADhEH;ES4HJ;IAMI;IACA;IACA,eRpEG;IQqEH;;;;AAIJ;EACE;EACA;EACA;;AAEA;EACE;;AVxIF;EACE;;ACRA;ES8IF;IVlIE;;;ACZA;EDHF;IACE;;;ACEA;ES8IF;IV5IE;;;AUqJF;EACE,ORtFG;EQuFH,QRvFG;EQwFH,cR1FG;EQ2FH,OXzJS;EW0JT;;AAGF;EACE;;;AAIJ;EACE;EACA;;;AAGF;EACE;EACA;EACA;EACA,OXtK4B;EWuK5B;EACA;;AV5LA;EACE;;ACYA;ESyKJ;IVjLI;;;;AU2LJ;EACE;EACA,aRrHK;EQsHL,gBRtHK;EQuHL,cRrHK;EQsHL,aRxHK;EQyHL,OXlL4B;EWmL5B;EACA,aR/GO;EQgHP,mBX9Ka;;ACjBb;EACE;;ACEA;ESmLJ;IVjLI;;;ACFA;ESmLJ;IAaI;IACA;IACA,cRlIG;IQmIH;IACA;;;;AAIJ;EACE,YR1IK;;;AQ6IP;EACE;;;AAGF;EACE;;AV1MA;EACE;;ACRA;ESgNJ;IVpMI;;;;AUyMJ;EACE;EACA,ORrJK;EQsJL,QRtJK;EQuJL;EACA,ORnJK;EQoJL,QRpJK;EQqJL,kBXnMwB;EWoMxB;EACA;EACA,YACE;EAEF;EACA;;;AAGF;EACE;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA,YACE;;;AAMF;EACE;EACA;EACA;EACA;EACA;EACA;;AAGF;EACE,QRxLI;EQyLJ;;ATjQA;ES+PF;IAKI,ORzKiB;IQ0KjB,YACE;;;AAKN;EACE,kBXnPsB;;AEzBtB;ES2QF;IAII;;;AT/QF;ESmRF;IAEI;;;AAIJ;EACE;;AAGF;EACE;EACA;EACA;EACA,YACE;;ATlSF;ESwSA;IACE;IACA;IACA;;;AAIJ;EACE,aRxOI;;ADxEJ;ES+SF;IAII;;;;AC9TN;EACE;EACA;EACA;EACA,eT0EK;ESzEL;EACA,eTkFc;ESjFd,YACE;;;AAIJ;EACE;EACA;EACA;;;AAGF;AAAA;EAEE;EACA;EACA,kBZIuB;EYHvB;EACA;;AXNA;AAAA;EACE;;ACRA;EUOJ;AAAA;IXKI;;;AWKF;AAAA;EACE;;;AAOE;AAAA;EAEE;;AAGF;EACE,gBTkCD;;;AS3BL;EACE;;;AC9CF;EACE;EACA;EACA,kBbcoB;EabpB;EACA,eV+EY;;;AU1EhB;EACE,cbUa;;;AayCf;AAAA;AAAA;EAGE;EACA,eVMK;EULL,kBblDsB;EamDtB,eVgBc;EUfd;EACA;EACA;EACA;;AAIA;AAAA;AAAA;EACE,OVLG;EUMH;EACA;EACA;EACA;EACA,SVVG;EUWH;EACA;EACA,ObhFc;EaiFd;;AAEA;AAAA;AAAA;EACE,MbpFY;;AauFd;AAAA;AAAA;EACE;EACA;EACA;;AAGF;AAAA;AAAA;EACE;EACA;;AAMF;AAAA;AAAA;EACE;EACA;;;AASJ;EACE;EACA,SV/CG;EUgDH;EACA;EACA,eVtCY;;AUyCd;AAAA;EAEE;EACA;EACA;;;AAUJ;EACE;EACA,eVrEK;;AU6CL;EACE;EACA,SV/CG;EUgDH;EACA;EACA,eVtCY;;AUyCd;AAAA;EAEE;EACA;EACA;;;AAwBF;AAAA;EAEE;EACA,SVpFG;EUqFH;EACA;EACA,eV3EY;;;AUmFhB;EACE;EACA;EACA;EACA;;AAEA;AAAA;EAEE;EACA;EACA,kBbhKoB;EaiKpB;;AZ9KF;AAAA;EACE;;ACEA;EWsKF;AAAA;IZpKE;;;AY8KF;EACE;EACA,eVjHG;EUkHH,cVlHG;;AUqHL;EACE;EACA;;;AAKJ;AAAA;EAEE,SV9HK;EU+HL,eV/HK;EUgIL;EACA;EACA,eVtHc;;AUwHd;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAIE;EACA;EACA;EACA;EACA;EACA;EACA;;;AAKJ;EACE;EACA;EACA;;;AAIF;AAAA;EAEE,YbnNsB;EasNpB,ObrNoB;;;Aa4NxB;EACE,Yb9NsB;;;AcpBxB;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAKF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;ACvOF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAKF;EACE;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;;;AbrBE;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;AAQR;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAKF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AdhHA;EACE;;ACYA;EcZJ;IfII;;;;AAKF;EACE;;ACEA;EcRJ;IfUI;;;;AAKF;EACE;;ACRA;EcJJ;IfgBI;;;;AAKF;EACE;;AClBA;EcAJ;IfsBI;;;;AAKF;EACE;;AC5BA;EcIJ;If4BI;;;;AAKF;EACE;;ACtCA;EcQJ;IfkCI;IACA,aEhDuB;;;;AFqDzB;EACE;EACA,aEvDuB;;ADKvB;EcYJ;If0CI;;;;AAKF;EACE;EACA,aElEuB;;ADKvB;EcgBJ;IfiDI;;;;AAKF;EACE;EACA,aE7EuB;;ADKvB;EcoBJ;IfwDI;;;;AAKF;EACE;EACA,aExFuB;;ADKvB;EcwBJ;If+DI;;;;Ae3DJ;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE,abxDiB;;;Aa2DnB;EACE,ab1DyB;;;Aa6D3B;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AC/EF;EACE;EACA;EACA;;AAGE;EACE;;;ACLN;EACE;EACA;;;AAQA;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AhBlCA;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AAaN;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AhB7GA;EgBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhB/IJ;EgBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhB/IJ;EgBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhB/IJ;EgBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhB/IJ;EgBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AC3JR;EACE;AAAA;AAAA;AAAA;AAAA;AAAA;IAME;;EAGF;IACE;IACA;;EAGF;IACE;IACA;IACA;;EAGF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;;EAGF;IACE;;EAGF;IACE;IACA;;;ACvCJ;EACE;EACA;EACA;EACA;EACA;EACA;EACA;;;AAGF;AAAA;EAEE,OpBCW;EoBAX,kBpBNsB;EoBOtB;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;;;ACpBF;EACE,kBrBCsB;;;AqBExB;EACI;EACA;EACA,elB4EY;EkB3EZ;EACA;;AAEA;EACI,OlB8BI;EkB7BJ;EACA;EACA;EACA;EACA;EACA;;AAGJ;EACE,OlBoBM;EkBnBN;EACA;EACA;EACA;EACA;;;AAIN;EACI;EACA;EACA,elBiDY;EkBhDZ;EACA;;AACA;EACE;EACA;EACA,OlBEM;EkBDN;EACA;EACA;EACA;EACA;;;AAIN;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAIJ;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAMJ;EACI;EACA;EACA,elBGY;EkBFZ;EACA;;AAEA;EACI,OlB/CG;EkBgDH;EACA;EACA;EACA;EACA;EACA;;AAGJ;EACE,OlBzDK;EkB0DL;EACA;EACA;EACA;EACA;;;AAIN;EACI;EACA;EACA,elBxBY;EkByBZ;EACA;;AACA;EACE;EACA;EACA,OlB3EK;EkB4EL;EACA;EACA;EACA;EACA;;;AAIN;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAIJ;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAMJ;EACI;EACA;EACA,elBtEY;EkBuEZ;EACA;;AAEA;EACI,OlBhHK;EkBiHL;EACA;EACA;EACA;EACA;EACA;;AAGJ;EACE,OlB1HO;EkB2HP;EACA;EACA;EACA;EACA;;;AAIN;EACI;EACA;EACA,elBjGY;EkBkGZ;EACA;;AACA;EACE;EACA;EACA,OlB5IO;EkB6IP;EACA;EACA;EACA;EACA;;;AAIN;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAIJ;EACE;EACA;;AAEA;EACE;;AAGF;EACE","sourcesContent":["/*\ngenerated by accessible-pygments \nCopyright (c) 2022, Quansight Labs\nLicensed under the BSD license, see LICENSE for details.\n--\ngenerated by Pygments \nCopyright 2006-2025 by the Pygments team.\nLicensed under the BSD license, see LICENSE for details.\n*/\n\n.highlight .hll { background-color: #0969da4a }\n.highlight .c { color: #6E7781 } /* Comment */\n.highlight .err { color: #CF222E } /* Error */\n.highlight .k { color: #CF222E } /* Keyword */\n.highlight .l { color: #953800 } /* Literal */\n.highlight .n { color: #8250DF } /* Name */\n.highlight .o { color: #116329 } /* Operator */\n.highlight .p { color: #24292F } /* Punctuation */\n.highlight .ch { color: #6E7781 } /* Comment.Hashbang */\n.highlight .cm { color: #6E7781 } /* Comment.Multiline */\n.highlight .cp { color: #6E7781 } /* Comment.Preproc */\n.highlight .cpf { color: #6E7781 } /* Comment.PreprocFile */\n.highlight .c1 { color: #6E7781 } /* Comment.Single */\n.highlight .cs { color: #6E7781 } /* Comment.Special */\n.highlight .gd { color: #0550AE } /* Generic.Deleted */\n.highlight .ge { font-style: italic } /* Generic.Emph */\n.highlight .gr { color: #CF222E } /* Generic.Error */\n.highlight .gh { color: #0550AE } /* Generic.Heading */\n.highlight .gs { font-weight: bold } /* Generic.Strong */\n.highlight .gu { color: #0550AE } /* Generic.Subheading */\n.highlight .kc { color: #0550AE } /* Keyword.Constant */\n.highlight .kd { color: #CF222E } /* Keyword.Declaration */\n.highlight .kn { color: #CF222E } /* Keyword.Namespace */\n.highlight .kp { color: #CF222E } /* Keyword.Pseudo */\n.highlight .kr { color: #CF222E } /* Keyword.Reserved */\n.highlight .kt { color: #CF222E } /* Keyword.Type */\n.highlight .ld { color: #953800 } /* Literal.Date */\n.highlight .m { color: #953800 } /* Literal.Number */\n.highlight .s { color: #0550AE } /* Literal.String */\n.highlight .na { color: #953800 } /* Name.Attribute */\n.highlight .nb { color: #953800 } /* Name.Builtin */\n.highlight .nc { color: #0550AE } /* Name.Class */\n.highlight .no { color: #0550AE } /* Name.Constant */\n.highlight .nd { color: #953800 } /* Name.Decorator */\n.highlight .ni { color: #116329 } /* Name.Entity */\n.highlight .ne { color: #8250DF } /* Name.Exception */\n.highlight .nf { color: #0550AE } /* Name.Function */\n.highlight .nl { color: #953800 } /* Name.Label */\n.highlight .nn { color: #24292F } /* Name.Namespace */\n.highlight .nx { color: #8250DF } /* Name.Other */\n.highlight .py { color: #0550AE } /* Name.Property */\n.highlight .nt { color: #116329 } /* Name.Tag */\n.highlight .nv { color: #953800 } /* Name.Variable */\n.highlight .ow { color: #8250DF } /* Operator.Word */\n.highlight .pm { color: #24292F } /* Punctuation.Marker */\n.highlight .w { color: #24292F } /* Text.Whitespace */\n.highlight .mb { color: #953800 } /* Literal.Number.Bin */\n.highlight .mf { color: #953800 } /* Literal.Number.Float */\n.highlight .mh { color: #953800 } /* Literal.Number.Hex */\n.highlight .mi { color: #953800 } /* Literal.Number.Integer */\n.highlight .mo { color: #953800 } /* Literal.Number.Oct */\n.highlight .sa { color: #0550AE } /* Literal.String.Affix */\n.highlight .sb { color: #0550AE } /* Literal.String.Backtick */\n.highlight .sc { color: #0550AE } /* Literal.String.Char */\n.highlight .dl { color: #0550AE } /* Literal.String.Delimiter */\n.highlight .sd { color: #0550AE } /* Literal.String.Doc */\n.highlight .s2 { color: #0550AE } /* Literal.String.Double */\n.highlight .se { color: #0550AE } /* Literal.String.Escape */\n.highlight .sh { color: #0550AE } /* Literal.String.Heredoc */\n.highlight .si { color: #0550AE } /* Literal.String.Interpol */\n.highlight .sx { color: #0550AE } /* Literal.String.Other */\n.highlight .sr { color: #0550AE } /* Literal.String.Regex */\n.highlight .s1 { color: #0550AE } /* Literal.String.Single */\n.highlight .ss { color: #0550AE } /* Literal.String.Symbol */\n.highlight .bp { color: #953800 } /* Name.Builtin.Pseudo */\n.highlight .fm { color: #0550AE } /* Name.Function.Magic */\n.highlight .vc { color: #953800 } /* Name.Variable.Class */\n.highlight .vg { color: #953800 } /* Name.Variable.Global */\n.highlight .vi { color: #953800 } /* Name.Variable.Instance */\n.highlight .vm { color: #953800 } /* Name.Variable.Magic */\n.highlight .il { color: #953800 } /* Literal.Number.Integer.Long */\n","/*! normalize.css v8.0.1 | MIT License | github.com/necolas/normalize.css */\n\n/* Document\n ========================================================================== */\n\n/**\n * 1. Correct the line height in all browsers.\n * 2. Prevent adjustments of font size after orientation changes in iOS.\n */\n\nhtml {\n line-height: 1.15; /* 1 */\n text-size-adjust: 100%; /* 2 */\n}\n\n/* Sections\n ========================================================================== */\n\n/**\n * Remove the margin in all browsers.\n */\n\nbody {\n margin: 0;\n}\n\n/**\n * Render the `main` element consistently in IE.\n */\n\nmain {\n display: block;\n}\n\n/**\n * Correct the font size and margin on `h1` elements within `section` and\n * `article` contexts in Chrome, Firefox, and Safari.\n */\n\nh1 {\n font-size: 2em;\n margin: 0.67em 0;\n}\n\n/* Grouping content\n ========================================================================== */\n\n/**\n * 1. Add the correct box sizing in Firefox.\n * 2. Show the overflow in Edge and IE.\n */\n\nhr {\n box-sizing: content-box; /* 1 */\n height: 0; /* 1 */\n overflow: visible; /* 2 */\n}\n\n/**\n * 1. Correct the inheritance and scaling of font size in all browsers.\n * 2. Correct the odd `em` font sizing in all browsers.\n */\n\npre {\n font-family: monospace; /* 1 */\n font-size: 1em; /* 2 */\n}\n\n/* Text-level semantics\n ========================================================================== */\n\n/**\n * Remove the gray background on active links in IE 10.\n */\n\na {\n background-color: transparent;\n}\n\n/**\n * 1. Remove the bottom border in Chrome 57-\n * 2. Add the correct text decoration in Chrome, Edge, IE, Opera, and Safari.\n */\n\nabbr[title] {\n border-bottom: none; /* 1 */\n text-decoration: underline; /* 2 */\n text-decoration: underline dotted; /* 2 */\n}\n\n/**\n * Add the correct font weight in Chrome, Edge, and Safari.\n */\n\nb,\nstrong {\n font-weight: bolder;\n}\n\n/**\n * 1. Correct the inheritance and scaling of font size in all browsers.\n * 2. Correct the odd `em` font sizing in all browsers.\n */\n\ncode,\nkbd,\nsamp {\n font-family: monospace; /* 1 */\n font-size: 1em; /* 2 */\n}\n\n/**\n * Add the correct font size in all browsers.\n */\n\nsmall {\n font-size: 80%;\n}\n\n/**\n * Prevent `sub` and `sup` elements from affecting the line height in\n * all browsers.\n */\n\nsub,\nsup {\n font-size: 75%;\n line-height: 0;\n position: relative;\n vertical-align: baseline;\n}\n\nsub {\n bottom: -0.25em;\n}\n\nsup {\n top: -0.5em;\n}\n\n/* Embedded content\n ========================================================================== */\n\n/**\n * Remove the border on images inside links in IE 10.\n */\n\nimg {\n border-style: none;\n}\n\n/* Forms\n ========================================================================== */\n\n/**\n * 1. Change the font styles in all browsers.\n * 2. Remove the margin in Firefox and Safari.\n */\n\nbutton,\ninput,\noptgroup,\nselect,\ntextarea {\n font-family: inherit; /* 1 */\n font-size: 100%; /* 1 */\n line-height: 1.15; /* 1 */\n margin: 0; /* 2 */\n}\n\n/**\n * Show the overflow in IE.\n * 1. Show the overflow in Edge.\n */\n\nbutton,\ninput {\n /* 1 */\n overflow: visible;\n}\n\n/**\n * Remove the inheritance of text transform in Edge, Firefox, and IE.\n * 1. Remove the inheritance of text transform in Firefox.\n */\n\nbutton,\nselect {\n /* 1 */\n text-transform: none;\n}\n\n/**\n * Correct the inability to style clickable types in iOS and Safari.\n */\n\nbutton,\n[type=\"button\"],\n[type=\"reset\"],\n[type=\"submit\"] {\n appearance: button;\n}\n\n/**\n * Remove the inner border and padding in Firefox.\n */\n\nbutton::-moz-focus-inner,\n[type=\"button\"]::-moz-focus-inner,\n[type=\"reset\"]::-moz-focus-inner,\n[type=\"submit\"]::-moz-focus-inner {\n border-style: none;\n padding: 0;\n}\n\n/**\n * Restore the focus styles unset by the previous rule.\n */\n\nbutton:-moz-focusring,\n[type=\"button\"]:-moz-focusring,\n[type=\"reset\"]:-moz-focusring,\n[type=\"submit\"]:-moz-focusring {\n outline: 1px dotted ButtonText;\n}\n\n/**\n * Correct the padding in Firefox.\n */\n\nfieldset {\n padding: 0.35em 0.75em 0.625em;\n}\n\n/**\n * 1. Correct the text wrapping in Edge and IE.\n * 2. Correct the color inheritance from `fieldset` elements in IE.\n * 3. Remove the padding so developers are not caught out when they zero out\n * `fieldset` elements in all browsers.\n */\n\nlegend {\n box-sizing: border-box; /* 1 */\n color: inherit; /* 2 */\n display: table; /* 1 */\n max-width: 100%; /* 1 */\n padding: 0; /* 3 */\n white-space: normal; /* 1 */\n}\n\n/**\n * Add the correct vertical alignment in Chrome, Firefox, and Opera.\n */\n\nprogress {\n vertical-align: baseline;\n}\n\n/**\n * Remove the default vertical scrollbar in IE 10+.\n */\n\ntextarea {\n overflow: auto;\n}\n\n/**\n * 1. Add the correct box sizing in IE 10.\n * 2. Remove the padding in IE 10.\n */\n\n[type=\"checkbox\"],\n[type=\"radio\"] {\n box-sizing: border-box; /* 1 */\n padding: 0; /* 2 */\n}\n\n/**\n * Correct the cursor style of increment and decrement buttons in Chrome.\n */\n\n[type=\"number\"]::-webkit-inner-spin-button,\n[type=\"number\"]::-webkit-outer-spin-button {\n height: auto;\n}\n\n/**\n * 1. Correct the odd appearance in Chrome and Safari.\n * 2. Correct the outline style in Safari.\n */\n\n[type=\"search\"] {\n appearance: textfield; /* 1 */\n outline-offset: -2px; /* 2 */\n}\n\n/**\n * Remove the inner padding in Chrome and Safari on macOS.\n */\n\n[type=\"search\"]::-webkit-search-decoration {\n appearance: none;\n}\n\n/**\n * 1. Correct the inability to style clickable types in iOS and Safari.\n * 2. Change font properties to `inherit` in Safari.\n */\n\n::-webkit-file-upload-button {\n appearance: button; /* 1 */\n font: inherit; /* 2 */\n}\n\n/* Interactive\n ========================================================================== */\n\n/*\n * Add the correct display in Edge, IE 10+, and Firefox.\n */\n\ndetails {\n display: block;\n}\n\n/*\n * Add the correct display in all browsers.\n */\n\nsummary {\n display: list-item;\n}\n\n/* Misc\n ========================================================================== */\n\n/**\n * Add the correct display in IE 10+.\n */\n\ntemplate {\n display: none;\n}\n\n/**\n * Add the correct display in IE 10.\n */\n\n[hidden] {\n display: none;\n}\n","// Base element style overrides\n// stylelint-disable selector-no-type, selector-max-type, selector-max-specificity, selector-max-id\n\n:root {\n color-scheme: $color-scheme;\n}\n\n* {\n box-sizing: border-box;\n}\n\nhtml {\n scroll-behavior: smooth;\n\n @include fs-4;\n}\n\nbody {\n font-family: $body-font-family;\n font-size: inherit;\n line-height: $body-line-height;\n color: $body-text-color;\n background-color: $body-background-color;\n overflow-wrap: break-word;\n}\n\nol,\nul,\ndl,\npre,\naddress,\nblockquote,\ntable,\ndiv,\nhr,\nform,\nfieldset,\nnoscript .table-wrapper {\n margin-top: 0;\n}\n\nh1,\nh2,\nh3,\nh4,\nh5,\nh6,\n#toctitle {\n margin-top: 0;\n margin-bottom: 1em;\n font-weight: 500;\n line-height: $body-heading-line-height;\n color: $body-heading-color;\n}\n\np {\n margin-top: 1em;\n margin-bottom: 1em;\n}\n\na {\n color: $link-color;\n text-decoration: none;\n}\n\na:not([class]) {\n text-decoration: underline;\n text-decoration-color: $border-color;\n text-underline-offset: 2px;\n\n &:hover {\n text-decoration-color: rgba($link-color, 0.45);\n }\n}\n\ncode {\n font-family: $mono-font-family;\n font-size: 0.75em;\n line-height: $body-line-height;\n}\n\nfigure,\npre {\n margin: 0;\n}\n\nli {\n margin: 0.25em 0;\n}\n\nimg {\n max-width: 100%;\n height: auto;\n}\n\nhr {\n height: 1px;\n padding: 0;\n margin: $sp-6 0;\n background-color: $border-color;\n border: 0;\n}\n\n// adds a GitHub-style sidebar to blockquotes\nblockquote {\n margin: 10px 0;\n\n // resets user-agent stylesheets for blockquotes\n margin-block-start: 0;\n margin-inline-start: 0;\n padding-left: 1rem;\n border-left: 3px solid $border-color;\n}\n","// Meshtastic Material 3 — Dark color scheme for just-the-docs\n// Source: core/ui/.../Color.kt §8.3 (Dark Scheme)\n//\n// Brand colors:\n// Primary (Dark): #67EA94 (Green 500)\n// Surface (Dark): #1A1B26 (Neutral 900)\n\n$color-scheme: dark;\n\n// Body / page background\n$body-background-color: #1A1B26; // Neutral 900 — surfaceDark\n$sidebar-color: #1A1B26; // Neutral 900\n$body-text-color: #ECEDF3; // Neutral 100 — onSurfaceDark\n$body-heading-color: #ECEDF3; // Neutral 100\n\n// Links\n$link-color: #67EA94; // Green 500 — primaryDark\n$nav-link-color: #67EA94; // Green 500\n\n// Navigation\n$nav-child-link-color: #B8BAC8; // Neutral 300 — secondaryDark\n$search-result-preview-color: #B8BAC8;\n\n// Code\n$code-background-color: #0F1017; // Neutral 950 — surfaceContainerLowestDark\n$code-linenumber-color: #9496A6; // Neutral 400\n\n// Borders\n$border-color: #3D3E50; // Neutral 700 — outlineVariantDark\n$table-background-color: #242533; // Interpolated — surfaceContainerDark\n\n// Buttons\n$btn-primary-color: #67EA94; // Green 500\n$base-button-color: #2C2D3C; // Neutral 800\n\n// Feedback / callouts\n$feedback-color: #242533; // surfaceContainerDark\n\n// Search\n$search-background-color: #242533; // surfaceContainerDark\n","@mixin fs-1 {\n & {\n font-size: $font-size-1 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-1-sm !important;\n }\n}\n\n@mixin fs-2 {\n & {\n font-size: $font-size-2 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-3 !important;\n }\n}\n\n@mixin fs-3 {\n & {\n font-size: $font-size-3 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-4 !important;\n }\n}\n\n@mixin fs-4 {\n & {\n font-size: $font-size-4 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-5 !important;\n }\n}\n\n@mixin fs-5 {\n & {\n font-size: $font-size-5 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-6 !important;\n }\n}\n\n@mixin fs-6 {\n & {\n font-size: $font-size-6 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-7 !important;\n line-height: $body-heading-line-height;\n }\n}\n\n@mixin fs-7 {\n & {\n font-size: $font-size-7 !important;\n line-height: $body-heading-line-height;\n }\n\n @include mq(sm) {\n font-size: $font-size-8 !important;\n }\n}\n\n@mixin fs-8 {\n & {\n font-size: $font-size-8 !important;\n line-height: $body-heading-line-height;\n }\n\n @include mq(sm) {\n font-size: $font-size-9 !important;\n }\n}\n\n@mixin fs-9 {\n & {\n font-size: $font-size-9 !important;\n line-height: $body-heading-line-height;\n }\n\n @include mq(sm) {\n font-size: $font-size-10 !important;\n }\n}\n\n@mixin fs-10 {\n & {\n font-size: $font-size-10 !important;\n line-height: $body-heading-line-height;\n }\n\n @include mq(sm) {\n font-size: $font-size-10-sm !important;\n }\n}\n","// Media query\n\n// Media query mixin\n// Usage:\n// @include mq(md) {\n// ..medium and up styles\n// }\n@mixin mq($name) {\n // Retrieves the value from the key\n $value: map-get($media-queries, $name);\n\n // If the key exists in the map\n @if $value {\n // Prints a media query based on the value\n @media (min-width: $value) {\n @content;\n }\n } @else {\n @warn \"No value could be retrieved from `#{$media-query}`. Please make sure it is defined in `$media-queries` map.\";\n }\n}\n\n// Responsive container\n\n@mixin container {\n padding-right: $gutter-spacing-sm;\n padding-left: $gutter-spacing-sm;\n\n @include mq(md) {\n padding-right: $gutter-spacing;\n padding-left: $gutter-spacing;\n }\n}\n","// Typography\n\n// prettier-ignore\n$body-font-family: system-ui, -apple-system, blinkmacsystemfont, \"Segoe UI\",\n roboto, \"Helvetica Neue\", arial, sans-serif, \"Segoe UI Emoji\" !default;\n$mono-font-family: \"SFMono-Regular\", menlo, consolas, monospace !default;\n$root-font-size: 16px !default; // DEPRECATED: previously base font-size for rems\n$body-line-height: 1.4 !default;\n$content-line-height: 1.6 !default;\n$body-heading-line-height: 1.25 !default;\n\n// Font size\n// `-sm` suffix is the size at the small (and above) media query\n\n$font-size-1: 0.5625rem !default;\n$font-size-1-sm: 0.625rem !default;\n$font-size-2: 0.6875rem !default; // h4 - uppercased!, h6 not uppercased, text-small\n$font-size-3: 0.75rem !default; // h5\n$font-size-4: 0.875rem !default;\n$font-size-5: 1rem !default; // h3\n$font-size-6: 1.125rem !default; // h2\n$font-size-7: 1.5rem !default;\n$font-size-8: 2rem !default; // h1\n$font-size-9: 2.25rem !default;\n$font-size-10: 2.625rem !default;\n$font-size-10-sm: 3rem !default;\n\n// Colors\n\n$white: #fff !default;\n$grey-dk-000: #959396 !default;\n$grey-dk-100: #5c5962 !default;\n$grey-dk-200: #44434d !default;\n$grey-dk-250: #302d36 !default;\n$grey-dk-300: #27262b !default;\n$grey-lt-000: #f5f6fa !default;\n$grey-lt-100: #eeebee !default;\n$grey-lt-200: #ecebed !default;\n$grey-lt-300: #e6e1e8 !default;\n$purple-000: #7253ed !default;\n$purple-100: #5e41d0 !default;\n$purple-200: #4e26af !default;\n$purple-300: #381885 !default;\n$blue-000: #2c84fa !default;\n$blue-100: #2869e6 !default;\n$blue-200: #264caf !default;\n$blue-300: #183385 !default;\n$green-000: #41d693 !default;\n$green-100: #11b584 !default;\n$green-200: #009c7b !default;\n$green-300: #026e57 !default;\n$yellow-000: #ffeb82 !default;\n$yellow-100: #fadf50 !default;\n$yellow-200: #f7d12e !default;\n$yellow-300: #e7af06 !default;\n$red-000: #f77e7e !default;\n$red-100: #f96e65 !default;\n$red-200: #e94c4c !default;\n$red-300: #dd2e2e !default;\n\n// Spacing\n\n$spacing-unit: 1rem; // 1rem == 16px\n\n$spacers: (\n sp-0: 0,\n sp-1: $spacing-unit * 0.25,\n sp-2: $spacing-unit * 0.5,\n sp-3: $spacing-unit * 0.75,\n sp-4: $spacing-unit,\n sp-5: $spacing-unit * 1.5,\n sp-6: $spacing-unit * 2,\n sp-7: $spacing-unit * 2.5,\n sp-8: $spacing-unit * 3,\n sp-9: $spacing-unit * 3.5,\n sp-10: $spacing-unit * 4,\n) !default;\n$sp-1: map-get($spacers, sp-1) !default; // 0.25 rem == 4px\n$sp-2: map-get($spacers, sp-2) !default; // 0.5 rem == 8px\n$sp-3: map-get($spacers, sp-3) !default; // 0.75 rem == 12px\n$sp-4: map-get($spacers, sp-4) !default; // 1 rem == 16px\n$sp-5: map-get($spacers, sp-5) !default; // 1.5 rem == 24px\n$sp-6: map-get($spacers, sp-6) !default; // 2 rem == 32px\n$sp-7: map-get($spacers, sp-7) !default; // 2.5 rem == 40px\n$sp-8: map-get($spacers, sp-8) !default; // 3 rem == 48px\n$sp-9: map-get($spacers, sp-9) !default; // 3.5 rem == 56px\n$sp-10: map-get($spacers, sp-10) !default; // 4 rem == 64px\n\n// Borders\n\n$border: 1px solid !default;\n$border-radius: 4px !default;\n$border-color: $grey-lt-100 !default;\n\n// Grid system\n\n$gutter-spacing: $sp-6 !default;\n$gutter-spacing-sm: $sp-4 !default;\n$nav-width: 16.5rem !default;\n$nav-width-md: 15.5rem !default;\n$nav-list-item-height: $sp-6 !default;\n$nav-list-item-height-sm: $sp-8 !default;\n$nav-list-expander-right: true;\n$content-width: 50rem !default;\n$header-height: 3.75rem !default;\n$search-results-width: $content-width - $nav-width !default;\n$transition-duration: 400ms;\n\n// Media queries in pixels\n\n$media-queries: (\n xs: 20rem,\n sm: 31.25rem,\n md: $content-width,\n lg: $content-width + $nav-width,\n xl: 87.5rem,\n) !default;\n","// The basic two column layout\n\n.side-bar {\n z-index: 0;\n display: flex;\n flex-wrap: wrap;\n background-color: $sidebar-color;\n\n @include mq(md) {\n flex-flow: column nowrap;\n position: fixed;\n width: $nav-width-md;\n height: 100%;\n border-right: $border $border-color;\n align-items: flex-end;\n }\n\n @include mq(lg) {\n width: calc((100% - #{$nav-width + $content-width}) / 2 + #{$nav-width});\n min-width: $nav-width;\n }\n\n & + .main {\n @include mq(md) {\n margin-left: $nav-width-md;\n }\n\n @include mq(lg) {\n // stylelint-disable function-name-case\n // disable for Max(), we want to use the CSS max() function\n margin-left: Max(\n #{$nav-width},\n calc((100% - #{$nav-width + $content-width}) / 2 + #{$nav-width})\n );\n // stylelint-enable function-name-case\n }\n\n .main-header {\n display: none;\n background-color: $sidebar-color;\n\n @include mq(md) {\n display: flex;\n background-color: $body-background-color;\n }\n\n &.nav-open {\n display: block;\n\n @include mq(md) {\n display: flex;\n }\n }\n }\n }\n}\n\n.main {\n margin: auto;\n\n @include mq(md) {\n position: relative;\n max-width: $content-width;\n }\n}\n\n.main-content-wrap {\n padding-top: $gutter-spacing-sm;\n padding-bottom: $gutter-spacing-sm;\n\n @include container;\n\n @include mq(md) {\n padding-top: $gutter-spacing;\n padding-bottom: $gutter-spacing;\n }\n}\n\n.main-header {\n z-index: 0;\n border-bottom: $border $border-color;\n\n @include mq(md) {\n display: flex;\n justify-content: space-between;\n height: $header-height;\n }\n}\n\n.site-nav,\n.site-header,\n.site-footer {\n width: 100%;\n\n @include mq(lg) {\n width: $nav-width;\n }\n}\n\n.site-nav {\n display: none;\n\n &.nav-open {\n display: block;\n }\n\n @include mq(md) {\n display: block;\n padding-top: $sp-8;\n padding-bottom: $gutter-spacing-sm;\n overflow-y: auto;\n flex: 1 1 auto;\n }\n}\n\n.site-header {\n display: flex;\n min-height: $header-height;\n align-items: center;\n\n @include mq(md) {\n height: $header-height;\n max-height: $header-height;\n border-bottom: $border $border-color;\n }\n}\n\n.site-title {\n flex-grow: 1;\n display: flex;\n height: 100%;\n align-items: center;\n padding-top: $sp-3;\n padding-bottom: $sp-3;\n color: $body-heading-color;\n\n @include container;\n\n @include fs-6;\n\n @include mq(md) {\n padding-top: $sp-2;\n padding-bottom: $sp-2;\n }\n}\n\n@if variable-exists(logo) {\n .site-logo {\n width: 100%;\n height: 100%;\n background-image: url($logo);\n background-repeat: no-repeat;\n background-position: left center;\n background-size: contain;\n }\n}\n\n.site-button {\n display: flex;\n height: 100%;\n padding: $gutter-spacing-sm;\n align-items: center;\n}\n\n@include mq(md) {\n .site-header .site-button {\n display: none;\n }\n}\n\n.site-title:hover {\n background-image: linear-gradient(\n -90deg,\n rgba($feedback-color, 1) 0%,\n rgba($feedback-color, 0.8) 80%,\n rgba($feedback-color, 0) 100%\n );\n}\n\n.site-button:hover {\n background-image: linear-gradient(\n -90deg,\n rgba($feedback-color, 1) 0%,\n rgba($feedback-color, 0.8) 100%\n );\n}\n\n.site-footer {\n position: absolute;\n bottom: 0;\n left: 0;\n padding-top: $sp-4;\n padding-bottom: $sp-4;\n\n @include container;\n\n @include fs-2;\n\n @include mq(md) {\n position: static;\n justify-self: end;\n }\n}\n\n.icon {\n width: $sp-5;\n height: $sp-5;\n color: $link-color;\n}\n","@charset \"UTF-8\";\n\n// Styles for rendered markdown in the .main-content container\n// stylelint-disable selector-no-type, max-nesting-depth, selector-max-compound-selectors, selector-max-type, selector-max-specificity, selector-max-id\n\n.main-content {\n line-height: $content-line-height;\n\n ol,\n ul,\n dl,\n pre,\n address,\n blockquote,\n .table-wrapper {\n margin-top: 0.5em;\n }\n\n a {\n overflow: hidden;\n text-overflow: ellipsis;\n }\n\n ul,\n ol {\n padding-left: 1.5em;\n }\n\n li {\n .highlight {\n margin-top: $sp-1;\n }\n }\n\n ol {\n list-style-type: none;\n counter-reset: step-counter;\n\n > li {\n position: relative;\n\n &::before {\n position: absolute;\n top: 0.2em;\n left: -1.6em;\n color: $grey-dk-000;\n content: counter(step-counter);\n counter-increment: step-counter;\n @include fs-3;\n\n @include mq(sm) {\n top: 0.11em;\n }\n }\n\n ol {\n counter-reset: sub-counter;\n\n > li {\n &::before {\n content: counter(sub-counter, lower-alpha);\n counter-increment: sub-counter;\n }\n }\n }\n }\n }\n\n ul {\n list-style: none;\n\n > li {\n &::before {\n position: absolute;\n margin-left: -1.4em;\n color: $grey-dk-000;\n content: \"•\";\n }\n }\n }\n\n .task-list-item {\n &::before {\n content: \"\";\n }\n }\n\n .task-list-item-checkbox {\n margin-right: 0.6em;\n margin-left: -1.4em;\n\n // The same margin-left is used above for ul > li::before\n }\n\n hr + * {\n margin-top: 0;\n }\n\n h1:first-of-type {\n margin-top: 0.5em;\n }\n\n dl {\n display: grid;\n grid-template: auto / 10em 1fr;\n }\n\n dt,\n dd {\n margin: 0.25em 0;\n }\n\n dt {\n grid-column: 1;\n font-weight: 500;\n text-align: right;\n\n &::after {\n content: \":\";\n }\n }\n\n dd {\n grid-column: 2;\n margin-bottom: 0;\n margin-left: 1em;\n\n blockquote,\n div,\n dl,\n dt,\n h1,\n h2,\n h3,\n h4,\n h5,\n h6,\n li,\n ol,\n p,\n pre,\n table,\n ul,\n .table-wrapper {\n &:first-child {\n margin-top: 0;\n }\n }\n }\n\n dd,\n ol,\n ul {\n dl:first-child {\n dt:first-child,\n dd:nth-child(2) {\n margin-top: 0;\n }\n }\n }\n\n .anchor-heading {\n position: absolute;\n right: -$sp-4;\n width: $sp-5;\n height: 100%;\n padding-right: $sp-1;\n padding-left: $sp-1;\n overflow: visible;\n\n @include mq(md) {\n right: auto;\n left: -$sp-5;\n }\n\n svg {\n display: inline-block;\n width: 100%;\n height: 100%;\n color: $link-color;\n visibility: hidden;\n }\n }\n\n .anchor-heading:hover,\n .anchor-heading:focus,\n h1:hover > .anchor-heading,\n h2:hover > .anchor-heading,\n h3:hover > .anchor-heading,\n h4:hover > .anchor-heading,\n h5:hover > .anchor-heading,\n h6:hover > .anchor-heading {\n svg {\n visibility: visible;\n }\n }\n\n summary {\n cursor: pointer;\n }\n\n h1,\n h2,\n h3,\n h4,\n h5,\n h6,\n #toctitle {\n position: relative;\n margin-top: 1.5em;\n margin-bottom: 0.25em;\n\n + table,\n + .table-wrapper,\n + .code-example,\n + .highlighter-rouge,\n + .sectionbody .listingblock {\n margin-top: 1em;\n }\n\n + p:not(.label) {\n margin-top: 0;\n }\n }\n\n > h1:first-child,\n > h2:first-child,\n > h3:first-child,\n > h4:first-child,\n > h5:first-child,\n > h6:first-child,\n > .sect1:first-child > h2,\n > .sect2:first-child > h3,\n > .sect3:first-child > h4,\n > .sect4:first-child > h5,\n > .sect5:first-child > h6 {\n margin-top: $sp-2;\n }\n}\n","// Main nav, breadcrumb, etc...\n// stylelint-disable selector-no-type, max-nesting-depth, selector-max-compound-selectors, selector-max-type, selector-max-specificity\n\n.nav-list {\n padding: 0;\n margin-top: 0;\n margin-bottom: 0;\n list-style: none;\n\n .nav-list-item {\n position: relative;\n margin: 0;\n\n @include fs-4;\n\n @include mq(md) {\n @include fs-3;\n }\n\n .nav-list-link {\n display: block;\n min-height: $nav-list-item-height-sm;\n padding-top: $sp-1;\n padding-bottom: $sp-1;\n line-height: #{$nav-list-item-height-sm - 2 * $sp-1};\n @if $nav-list-expander-right {\n padding-right: $nav-list-item-height-sm;\n padding-left: $gutter-spacing-sm;\n } @else {\n padding-right: $gutter-spacing-sm;\n padding-left: $nav-list-item-height-sm;\n }\n\n @include mq(md) {\n min-height: $nav-list-item-height;\n line-height: #{$nav-list-item-height - 2 * $sp-1};\n @if $nav-list-expander-right {\n padding-right: $nav-list-item-height;\n padding-left: $gutter-spacing;\n } @else {\n padding-right: $gutter-spacing;\n padding-left: $nav-list-item-height;\n }\n }\n\n &.external > svg {\n width: $sp-4;\n height: $sp-4;\n vertical-align: text-bottom;\n }\n\n &.active {\n font-weight: 600;\n text-decoration: none;\n }\n\n &:hover,\n &.active {\n color: darken($link-color, 5%);\n background-image: linear-gradient(\n -90deg,\n rgba($feedback-color, 1) 0%,\n rgba($feedback-color, 0.8) 80%,\n rgba($feedback-color, 0) 100%\n );\n }\n }\n\n .nav-list-expander {\n position: absolute;\n @if $nav-list-expander-right {\n right: 0;\n }\n\n width: $nav-list-item-height-sm;\n height: $nav-list-item-height-sm;\n padding: #{$nav-list-item-height-sm * 0.25};\n color: $link-color;\n\n @include mq(md) {\n width: $nav-list-item-height;\n height: $nav-list-item-height;\n padding: #{$nav-list-item-height * 0.25};\n }\n\n &:hover {\n background-image: linear-gradient(\n -90deg,\n rgba($feedback-color, 1) 0%,\n rgba($feedback-color, 0.8) 100%\n );\n }\n\n @if $nav-list-expander-right {\n svg {\n transform: rotate(90deg);\n }\n }\n }\n\n > .nav-list {\n display: none;\n padding-left: $sp-3;\n list-style: none;\n\n .nav-list-item {\n position: relative;\n\n .nav-list-link {\n color: $nav-child-link-color;\n }\n\n .nav-list-expander {\n color: $nav-child-link-color;\n }\n }\n }\n\n &.active {\n > .nav-list-expander svg {\n @if $nav-list-expander-right {\n transform: rotate(-90deg);\n } @else {\n transform: rotate(90deg);\n }\n }\n\n > .nav-list {\n display: block;\n }\n }\n }\n}\n\n.nav-category {\n padding: $sp-2 $gutter-spacing-sm;\n font-weight: 600;\n text-align: start;\n text-transform: uppercase;\n border-bottom: $border $border-color;\n @include fs-2;\n\n @include mq(md) {\n padding: $sp-2 $gutter-spacing;\n margin-top: $gutter-spacing-sm;\n text-align: start;\n\n &:first-child {\n margin-top: 0;\n }\n }\n}\n\n.nav-list.nav-category-list {\n > .nav-list-item {\n margin: 0;\n\n > .nav-list {\n padding: 0;\n\n > .nav-list-item {\n > .nav-list-link {\n color: $link-color;\n }\n\n > .nav-list-expander {\n color: $link-color;\n }\n }\n }\n }\n}\n\n// Aux nav\n\n.aux-nav {\n height: 100%;\n overflow-x: auto;\n @include fs-2;\n\n .aux-nav-list {\n display: flex;\n height: 100%;\n padding: 0;\n margin: 0;\n list-style: none;\n }\n\n .aux-nav-list-item {\n display: inline-block;\n height: 100%;\n padding: 0;\n margin: 0;\n }\n\n @include mq(md) {\n padding-right: $gutter-spacing-sm;\n }\n}\n\n// Breadcrumb nav\n\n.breadcrumb-nav {\n @include mq(md) {\n margin-top: -$sp-4;\n }\n}\n\n.breadcrumb-nav-list {\n padding-left: 0;\n margin-bottom: $sp-3;\n list-style: none;\n}\n\n.breadcrumb-nav-list-item {\n display: table-cell;\n @include fs-2;\n\n &::before {\n display: none;\n }\n\n &::after {\n display: inline-block;\n margin-right: $sp-2;\n margin-left: $sp-2;\n color: $grey-dk-000;\n content: \"/\";\n }\n\n &:last-child {\n &::after {\n content: \"\";\n }\n }\n}\n","// Typography\n// stylelint-disable selector-no-type, selector-max-type, selector-max-specificity, selector-max-id\n\nh1,\n.text-alpha {\n font-weight: 300;\n\n @include fs-8;\n}\n\nh2,\n.text-beta,\n#toctitle {\n @include fs-6;\n}\n\nh3,\n.text-gamma {\n @include fs-5;\n}\n\nh4,\n.text-delta {\n font-weight: 400;\n text-transform: uppercase;\n letter-spacing: 0.1em;\n\n @include fs-2;\n}\n\nh4 code {\n text-transform: none;\n}\n\nh5,\n.text-epsilon {\n @include fs-3;\n}\n\nh6,\n.text-zeta {\n @include fs-2;\n}\n\n.text-small {\n @include fs-2;\n}\n\n.text-mono {\n font-family: $mono-font-family !important;\n}\n\n.text-left {\n text-align: left !important;\n}\n\n.text-center {\n text-align: center !important;\n}\n\n.text-right {\n text-align: right !important;\n}\n","// Labels (not the form kind)\n\n// this :not() prevents a style clash with Mermaid.js's\n// diagram labels, which also use .label\n// for more, see https://github.com/just-the-docs/just-the-docs/issues/1272\n// and the accompanying PR\n.label:not(g),\n.label-blue:not(g) {\n display: inline-block;\n padding: 0.16em 0.56em;\n margin-right: $sp-2;\n margin-left: $sp-2;\n color: $white;\n text-transform: uppercase;\n vertical-align: middle;\n background-color: $blue-100;\n border-radius: 12px;\n\n @include fs-2;\n}\n\n.label-green:not(g) {\n background-color: $green-300;\n}\n\n.label-purple:not(g) {\n background-color: $purple-100;\n}\n\n.label-red:not(g) {\n background-color: $red-300;\n}\n\n.label-yellow:not(g) {\n color: $grey-dk-200;\n background-color: $yellow-200;\n}\n","// Buttons and things that look like buttons\n// stylelint-disable color-named\n\n.btn {\n display: inline-block;\n box-sizing: border-box;\n padding: 0.3em 1em;\n margin: 0;\n font-family: inherit;\n font-size: inherit;\n font-weight: 500;\n line-height: 1.5;\n color: $link-color;\n text-decoration: none;\n vertical-align: baseline;\n cursor: pointer;\n background-color: $base-button-color;\n border-width: 0;\n border-radius: $border-radius;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n appearance: none;\n\n &:focus {\n text-decoration: none;\n outline: none;\n box-shadow: 0 0 0 3px rgba(blue, 0.25);\n }\n\n &:focus:hover,\n &.selected:focus {\n box-shadow: 0 0 0 3px rgba(blue, 0.25);\n }\n\n &:hover,\n &.zeroclipboard-is-hover {\n color: darken($link-color, 2%);\n }\n\n &:hover,\n &:active,\n &.zeroclipboard-is-hover,\n &.zeroclipboard-is-active {\n text-decoration: none;\n background-color: darken($base-button-color, 1%);\n }\n\n &:active,\n &.selected,\n &.zeroclipboard-is-active {\n background-color: darken($base-button-color, 3%);\n background-image: none;\n box-shadow: inset 0 2px 4px rgba(0, 0, 0, 0.15);\n }\n\n &.selected:hover {\n background-color: darken(#dcdcdc, 5%);\n }\n\n &:disabled,\n &.disabled {\n &,\n &:hover {\n color: rgba(102, 102, 102, 0.5);\n cursor: default;\n background-color: rgba(229, 229, 229, 0.5);\n background-image: none;\n box-shadow: none;\n }\n }\n}\n\n.btn-outline {\n color: $link-color;\n background: transparent;\n box-shadow: inset 0 0 0 2px $grey-lt-300;\n\n &:hover,\n &:active,\n &.zeroclipboard-is-hover,\n &.zeroclipboard-is-active {\n color: darken($link-color, 4%);\n text-decoration: none;\n background-color: transparent;\n box-shadow: inset 0 0 0 3px $grey-lt-300;\n }\n\n &:focus {\n text-decoration: none;\n outline: none;\n box-shadow:\n inset 0 0 0 2px $grey-dk-100,\n 0 0 0 3px rgba(blue, 0.25);\n }\n\n &:focus:hover,\n &.selected:focus {\n box-shadow: inset 0 0 0 2px $grey-dk-100;\n }\n}\n\n.btn-primary {\n @include btn-color($white, $btn-primary-color);\n}\n\n.btn-purple {\n @include btn-color($white, $purple-100);\n}\n\n.btn-blue {\n @include btn-color($white, $blue-200);\n}\n\n.btn-green {\n @include btn-color($white, $green-300);\n}\n\n.btn-reset {\n background: none;\n border: none;\n margin: 0;\n text-align: inherit;\n font: inherit;\n border-radius: 0;\n appearance: none;\n}\n","// Colored button\n\n@mixin btn-color($fg, $bg) {\n color: $fg;\n background-color: darken($bg, 2%);\n background-image: linear-gradient(lighten($bg, 5%), darken($bg, 2%));\n box-shadow:\n 0 1px 3px rgba(0, 0, 0, 0.25),\n 0 4px 10px rgba(0, 0, 0, 0.12);\n\n &:hover,\n &.zeroclipboard-is-hover {\n color: $fg;\n background-color: darken($bg, 4%);\n background-image: linear-gradient((lighten($bg, 2%), darken($bg, 4%)));\n }\n\n &:active,\n &.selected,\n &.zeroclipboard-is-active {\n background-color: darken($bg, 5%);\n background-image: none;\n box-shadow: inset 0 2px 4px rgba(0, 0, 0, 0.15);\n }\n\n &.selected:hover {\n background-color: darken($bg, 10%);\n }\n}\n","// Search input and autocomplete\n\n.search {\n position: relative;\n z-index: 2;\n flex-grow: 1;\n height: $sp-10;\n padding: $sp-2;\n transition: padding linear #{$transition-duration * 0.5};\n\n @include mq(md) {\n position: relative !important;\n width: auto !important;\n height: 100% !important;\n padding: 0;\n transition: none;\n }\n}\n\n.search-input-wrap {\n position: relative;\n z-index: 1;\n height: $sp-8;\n overflow: hidden;\n border-radius: $border-radius;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n transition: height linear #{$transition-duration * 0.5};\n\n @include mq(md) {\n position: absolute;\n width: 100%;\n max-width: $search-results-width;\n height: 100% !important;\n border-radius: 0;\n box-shadow: none;\n transition: width ease $transition-duration;\n }\n}\n\n.search-input {\n position: absolute;\n width: 100%;\n height: 100%;\n padding: $sp-2 $gutter-spacing-sm $sp-2 #{$gutter-spacing-sm + $sp-5};\n font-size: 1rem;\n color: $body-text-color;\n background-color: $search-background-color;\n border-top: 0;\n border-right: 0;\n border-bottom: 0;\n border-left: 0;\n border-radius: 0;\n\n @include mq(md) {\n padding: $sp-2 $gutter-spacing-sm $sp-2 #{$gutter-spacing + $sp-5};\n font-size: 0.875rem;\n background-color: $body-background-color;\n transition: padding-left linear #{$transition-duration * 0.5};\n }\n\n &:focus {\n outline: 2px solid $link-color;\n outline-offset: -2px;\n\n + .search-label .search-icon {\n color: $link-color;\n }\n }\n}\n\n.search-label {\n position: absolute;\n display: flex;\n height: 100%;\n padding-left: $gutter-spacing-sm;\n\n @include mq(md) {\n padding-left: $gutter-spacing;\n transition: padding-left linear #{$transition-duration * 0.5};\n }\n\n .search-icon {\n width: #{$sp-4 * 1.2};\n height: #{$sp-4 * 1.2};\n align-self: center;\n color: $grey-dk-000;\n }\n}\n\n.search-results {\n position: absolute;\n left: 0;\n display: none;\n width: 100%;\n max-height: calc(100% - #{$sp-10});\n overflow-y: auto;\n background-color: $search-background-color;\n border-bottom-right-radius: $border-radius;\n border-bottom-left-radius: $border-radius;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n\n @include mq(md) {\n top: 100%;\n width: $search-results-width;\n max-height: calc(100vh - 200%) !important;\n }\n}\n\n.search-results-list {\n padding-left: 0;\n margin-bottom: $sp-1;\n list-style: none;\n @include fs-4;\n\n @include mq(md) {\n @include fs-3;\n }\n}\n\n.search-results-list-item {\n padding: 0;\n margin: 0;\n}\n\n.search-result {\n display: block;\n padding: $sp-1 $sp-3;\n\n &:hover,\n &.active {\n background-color: $feedback-color;\n }\n}\n\n.search-result-title {\n display: block;\n padding-top: $sp-2;\n padding-bottom: $sp-2;\n\n @include mq(sm) {\n display: inline-block;\n width: 40%;\n padding-right: $sp-2;\n vertical-align: top;\n }\n}\n\n.search-result-doc {\n display: flex;\n align-items: center;\n word-wrap: break-word;\n\n &.search-result-doc-parent {\n opacity: 0.5;\n @include fs-3;\n\n @include mq(md) {\n @include fs-2;\n }\n }\n\n .search-result-icon {\n width: $sp-4;\n height: $sp-4;\n margin-right: $sp-2;\n color: $link-color;\n flex-shrink: 0;\n }\n\n .search-result-doc-title {\n overflow: auto;\n }\n}\n\n.search-result-section {\n margin-left: #{$sp-4 + $sp-2};\n word-wrap: break-word;\n}\n\n.search-result-rel-url {\n display: block;\n margin-left: #{$sp-4 + $sp-2};\n overflow: hidden;\n color: $search-result-preview-color;\n text-overflow: ellipsis;\n white-space: nowrap;\n @include fs-1;\n}\n\n.search-result-previews {\n display: block;\n padding-top: $sp-2;\n padding-bottom: $sp-2;\n padding-left: $sp-4;\n margin-left: $sp-2;\n color: $search-result-preview-color;\n word-wrap: break-word;\n border-left: $border;\n border-left-color: $border-color;\n @include fs-2;\n\n @include mq(sm) {\n display: inline-block;\n width: 60%;\n padding-left: $sp-2;\n margin-left: 0;\n vertical-align: top;\n }\n}\n\n.search-result-preview + .search-result-preview {\n margin-top: $sp-1;\n}\n\n.search-result-highlight {\n font-weight: bold;\n}\n\n.search-no-result {\n padding: $sp-2 $sp-3;\n @include fs-3;\n}\n\n.search-button {\n position: fixed;\n right: $sp-4;\n bottom: $sp-4;\n display: flex;\n width: $sp-9;\n height: $sp-9;\n background-color: $search-background-color;\n border: 1px solid rgba($link-color, 0.3);\n border-radius: #{$sp-9 * 0.5};\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n align-items: center;\n justify-content: center;\n}\n\n.search-overlay {\n position: fixed;\n top: 0;\n left: 0;\n z-index: 1;\n width: 0;\n height: 0;\n background-color: rgba(0, 0, 0, 0.3);\n opacity: 0;\n transition:\n opacity ease $transition-duration,\n width 0s $transition-duration,\n height 0s $transition-duration;\n}\n\n.search-active {\n .search {\n position: fixed;\n top: 0;\n left: 0;\n width: 100%;\n height: 100%;\n padding: 0;\n }\n\n .search-input-wrap {\n height: $sp-10;\n border-radius: 0;\n\n @include mq(md) {\n width: $search-results-width;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n }\n }\n\n .search-input {\n background-color: $search-background-color;\n\n @include mq(md) {\n padding-left: 2.3rem;\n }\n }\n\n .search-label {\n @include mq(md) {\n padding-left: 0.6rem;\n }\n }\n\n .search-results {\n display: block;\n }\n\n .search-overlay {\n width: 100%;\n height: 100%;\n opacity: 1;\n transition:\n opacity ease $transition-duration,\n width 0s,\n height 0s;\n }\n\n @include mq(md) {\n .main {\n position: fixed;\n right: 0;\n left: 0;\n }\n }\n\n .main-header {\n padding-top: $sp-10;\n\n @include mq(md) {\n padding-top: 0;\n }\n }\n}\n","// Tables\n// stylelint-disable max-nesting-depth, selector-no-type, selector-max-type\n\n.table-wrapper {\n display: block;\n width: 100%;\n max-width: 100%;\n margin-bottom: $sp-5;\n overflow-x: auto;\n border-radius: $border-radius;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n}\n\ntable {\n display: table;\n min-width: 100%;\n border-collapse: separate;\n}\n\nth,\ntd {\n min-width: 7.5rem;\n padding: $sp-2 $sp-3;\n background-color: $table-background-color;\n border-bottom: $border rgba($border-color, 0.5);\n border-left: $border $border-color;\n\n @include fs-3;\n\n &:first-of-type {\n border-left: 0;\n }\n}\n\ntbody {\n tr {\n &:last-of-type {\n th,\n td {\n border-bottom: 0;\n }\n\n td {\n padding-bottom: $sp-3;\n }\n }\n }\n}\n\nthead {\n th {\n border-bottom: $border $border-color;\n }\n}\n","// Code and syntax highlighting\n// stylelint-disable selector-no-qualifying-type, declaration-block-semicolon-newline-after,declaration-block-single-line-max-declarations, selector-no-type, selector-max-type, scss/comment-no-empty\n\n// {% raw %}\n\n// This instruction applies to all queues not within 'pre' or 'figure', avoiding 'code' generated by the highlight.\n:not(pre, figure) {\n & > code {\n padding: 0.2em 0.15em;\n font-weight: 400;\n background-color: $code-background-color;\n border: $border $border-color;\n border-radius: $border-radius;\n }\n}\n\n// Avoid appearance of dark border around visited code links in Safari\na:visited code {\n border-color: $border-color;\n}\n\n// Content structure for highlighted code blocks using fences or Liquid\n//\n// ```[LANG]...```, no kramdown line_numbers:\n// div.[language-LANG.]highlighter-rouge > div.highlight > pre.highlight > code\n//\n// ```[LANG]...```, kramdown line_numbers = true:\n// div.[language-LANG.]highlighter-rouge > div.highlight > pre.highlight > code\n// > div.table-wrapper > table.rouge-table > tbody > tr\n// > td.rouge-gutter.gl > pre.lineno\n// | td.rouge-code > pre\n//\n// {% highlight LANG %}...{% endhighlight %}:\n// figure.highlight > pre > code.language-LANG\n//\n// {% highlight LANG linenos %}...{% endhighlight %}:\n// figure.highlight > pre > code.language-LANG\n// > div.table-wrapper > table.rouge-table > tbody > tr\n// > td.gutter.gl > pre.lineno\n// | td.code > pre\n//\n// ----...---- (AsciiDoc)\n// div.listingblock > div.content > pre.rouge.highlight\n//\n// fix_linenos removes the outermost pre when it encloses table.rouge-table\n//\n// See docs/index-test.md for some tests.\n//\n// No kramdown line_numbers: fences and Liquid highlighting look the same.\n// Kramdown line_numbers = true: fences have a wider gutter than with Liquid?\n\n// ```[LANG]...```\n// or in AsciiDoc:\n//\n// ----\n// ...\n// ----\n\n// the code may appear with 3 different types:\n// container \\ case: default case, code with line number, code with html rendering\n// top level: div.highlighter-rouge, figure.highlight, figure.highlight\n// second level: div.highlight, div.table-wrapper, pre.highlight\n// third level: pre.highlight, td.code, absent\n// last level: code, pre, code (optionality)\n// highlighter level: span, span, span\n// the spacing are only in the second level for case 1, 3 and in the third level for case 2\n// in AsciiDoc, there is a parent container that contains optionally a title and the content.\n\n// select top level container\ndiv.highlighter-rouge,\ndiv.listingblock > div.content,\nfigure.highlight {\n margin-top: 0;\n margin-bottom: $sp-3;\n background-color: $code-background-color;\n border-radius: $border-radius;\n box-shadow: none;\n -webkit-overflow-scrolling: touch;\n position: relative;\n padding: 0;\n\n // copy button (or other button)\n // the button appear only when there is a hover on the code or focus on button\n > button {\n width: $sp-3;\n opacity: 0;\n position: absolute;\n top: 0;\n right: 0;\n padding: $sp-3;\n border: none;\n background: none;\n color: $body-text-color;\n box-sizing: content-box;\n\n svg {\n fill: $body-text-color;\n }\n\n &:active {\n text-decoration: none;\n outline: none;\n opacity: 1;\n }\n\n &:focus {\n opacity: 1;\n outline: 2px solid $link-color;\n }\n }\n\n // the button can be seen by doing a simple hover in the code, there is no need to go over the location of the button\n &:hover {\n > button {\n cursor: copy;\n opacity: 1;\n }\n }\n}\n\n// setting the spacing and scrollbar on the second level for the first case\n// remove all space on the second and third level\n// this is a mixin to accommodate for the slightly different structures generated via Markdown vs AsciiDoc\n@mixin scroll-and-spacing($code-div, $pre-select) {\n #{$code-div} {\n overflow-x: auto;\n padding: $sp-3;\n margin: 0;\n border: 1px solid $body-text-color;\n border-radius: $border-radius;\n }\n\n #{$pre-select},\n code {\n padding: 0;\n margin: 0;\n border: 0;\n }\n}\n\n// for Markdown\ndiv.highlighter-rouge {\n @include scroll-and-spacing(\"div.highlight\", \"pre.highlight\");\n}\n\n// for AsciiDoc. we also need to fix the margins for its parent container.\ndiv.listingblock {\n margin-top: 0;\n margin-bottom: $sp-3;\n\n @include scroll-and-spacing(\"div.content\", \"div.content > pre\");\n}\n\n// {% highlight LANG %}...{% endhighlight %},\n// {% highlight LANG linenos %}...{% endhighlight %}:\n\n// setting the spacing and scrollbar on the second level for the thirt case\n// the css rule are apply only to the last code enviroment\n// setting the scroolbar\nfigure.highlight {\n pre,\n :not(pre) > code {\n overflow-x: auto;\n padding: $sp-3;\n margin: 0;\n border: 1px solid $body-text-color;\n border-radius: $border-radius;\n }\n}\n\n// ```[LANG]...```, kramdown line_numbers = true,\n// {% highlight LANG linenos %}...{% endhighlight %}:\n\n// setting the spacing and scrollbar on the thirt level for the second case\n.highlight .table-wrapper {\n padding: $sp-3 0;\n margin: 0;\n border: 0;\n box-shadow: none;\n\n td,\n pre {\n min-width: 0;\n padding: 0;\n background-color: $code-background-color;\n border: 0;\n\n @include fs-2;\n }\n\n td.gl {\n width: 1em;\n padding-right: $sp-3;\n padding-left: $sp-3;\n }\n\n pre {\n margin: 0;\n line-height: 2;\n }\n}\n\n// Code examples: html render of a code\n.code-example,\n.listingblock > .title {\n padding: $sp-3;\n margin-bottom: $sp-3;\n overflow: auto;\n border: 1px solid $border-color;\n border-radius: $border-radius;\n\n + .highlighter-rouge,\n + .sectionbody .listingblock,\n + .content,\n + figure.highlight {\n position: relative;\n margin-top: -$sp-4;\n border-right: 1px solid $border-color;\n border-bottom: 1px solid $border-color;\n border-left: 1px solid $border-color;\n border-top-left-radius: 0;\n border-top-right-radius: 0;\n }\n}\n\n// Mermaid diagram code blocks should be left unstyled.\ncode.language-mermaid {\n padding: 0;\n background-color: inherit;\n border: 0;\n}\n\n// Override OneDarkJekyll Colors for Code Blocks\n.highlight,\npre.highlight {\n background: $code-background-color; // Code Background\n // For Backwards Compatibility Before $code-linenumber-color was added\n @if variable-exists(code-linenumber-color) {\n color: $code-linenumber-color; // Code Line Numbers\n } @else {\n color: $body-text-color; // Code Line Numbers\n }\n}\n\n// Override OneDarkJekyll Colors for Code Blocks\n.highlight pre {\n background: $code-background-color; // Code Background\n}\n\n// {% endraw %}\n","// Utility classes for colors\n\n// Text colors\n\n.text-grey-dk-000 {\n color: $grey-dk-000 !important;\n}\n\n.text-grey-dk-100 {\n color: $grey-dk-100 !important;\n}\n\n.text-grey-dk-200 {\n color: $grey-dk-200 !important;\n}\n\n.text-grey-dk-250 {\n color: $grey-dk-250 !important;\n}\n\n.text-grey-dk-300 {\n color: $grey-dk-300 !important;\n}\n\n.text-grey-lt-000 {\n color: $grey-lt-000 !important;\n}\n\n.text-grey-lt-100 {\n color: $grey-lt-100 !important;\n}\n\n.text-grey-lt-200 {\n color: $grey-lt-200 !important;\n}\n\n.text-grey-lt-300 {\n color: $grey-lt-300 !important;\n}\n\n.text-blue-000 {\n color: $blue-000 !important;\n}\n\n.text-blue-100 {\n color: $blue-100 !important;\n}\n\n.text-blue-200 {\n color: $blue-200 !important;\n}\n\n.text-blue-300 {\n color: $blue-300 !important;\n}\n\n.text-green-000 {\n color: $green-000 !important;\n}\n\n.text-green-100 {\n color: $green-100 !important;\n}\n\n.text-green-200 {\n color: $green-200 !important;\n}\n\n.text-green-300 {\n color: $green-300 !important;\n}\n\n.text-purple-000 {\n color: $purple-000 !important;\n}\n\n.text-purple-100 {\n color: $purple-100 !important;\n}\n\n.text-purple-200 {\n color: $purple-200 !important;\n}\n\n.text-purple-300 {\n color: $purple-300 !important;\n}\n\n.text-yellow-000 {\n color: $yellow-000 !important;\n}\n\n.text-yellow-100 {\n color: $yellow-100 !important;\n}\n\n.text-yellow-200 {\n color: $yellow-200 !important;\n}\n\n.text-yellow-300 {\n color: $yellow-300 !important;\n}\n\n.text-red-000 {\n color: $red-000 !important;\n}\n\n.text-red-100 {\n color: $red-100 !important;\n}\n\n.text-red-200 {\n color: $red-200 !important;\n}\n\n.text-red-300 {\n color: $red-300 !important;\n}\n\n// Background colors\n\n.bg-grey-dk-000 {\n background-color: $grey-dk-000 !important;\n}\n\n.bg-grey-dk-100 {\n background-color: $grey-dk-100 !important;\n}\n\n.bg-grey-dk-200 {\n background-color: $grey-dk-200 !important;\n}\n\n.bg-grey-dk-250 {\n background-color: $grey-dk-250 !important;\n}\n\n.bg-grey-dk-300 {\n background-color: $grey-dk-300 !important;\n}\n\n.bg-grey-lt-000 {\n background-color: $grey-lt-000 !important;\n}\n\n.bg-grey-lt-100 {\n background-color: $grey-lt-100 !important;\n}\n\n.bg-grey-lt-200 {\n background-color: $grey-lt-200 !important;\n}\n\n.bg-grey-lt-300 {\n background-color: $grey-lt-300 !important;\n}\n\n.bg-blue-000 {\n background-color: $blue-000 !important;\n}\n\n.bg-blue-100 {\n background-color: $blue-100 !important;\n}\n\n.bg-blue-200 {\n background-color: $blue-200 !important;\n}\n\n.bg-blue-300 {\n background-color: $blue-300 !important;\n}\n\n.bg-green-000 {\n background-color: $green-000 !important;\n}\n\n.bg-green-100 {\n background-color: $green-100 !important;\n}\n\n.bg-green-200 {\n background-color: $green-200 !important;\n}\n\n.bg-green-300 {\n background-color: $green-300 !important;\n}\n\n.bg-purple-000 {\n background-color: $purple-000 !important;\n}\n\n.bg-purple-100 {\n background-color: $purple-100 !important;\n}\n\n.bg-purple-200 {\n background-color: $purple-200 !important;\n}\n\n.bg-purple-300 {\n background-color: $purple-300 !important;\n}\n\n.bg-yellow-000 {\n background-color: $yellow-000 !important;\n}\n\n.bg-yellow-100 {\n background-color: $yellow-100 !important;\n}\n\n.bg-yellow-200 {\n background-color: $yellow-200 !important;\n}\n\n.bg-yellow-300 {\n background-color: $yellow-300 !important;\n}\n\n.bg-red-000 {\n background-color: $red-000 !important;\n}\n\n.bg-red-100 {\n background-color: $red-100 !important;\n}\n\n.bg-red-200 {\n background-color: $red-200 !important;\n}\n\n.bg-red-300 {\n background-color: $red-300 !important;\n}\n","// Utility classes for layout\n\n// Display\n\n.d-block {\n display: block !important;\n}\n\n.d-flex {\n display: flex !important;\n}\n\n.d-inline {\n display: inline !important;\n}\n\n.d-inline-block {\n display: inline-block !important;\n}\n\n.d-none {\n display: none !important;\n}\n\n// Screenreader-only\n\n.sr-only {\n position: absolute;\n width: 1px;\n height: 1px;\n padding: 0;\n margin: -1px;\n overflow: hidden;\n clip: rect(0, 0, 0, 0);\n white-space: nowrap;\n border-width: 0;\n}\n\n@each $media-query in map-keys($media-queries) {\n @for $i from 1 through length($spacers) {\n @include mq($media-query) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .d-sm-block, .d-md-none, .d-lg-inline\n .d-#{$media-query}-block {\n display: block !important;\n }\n .d-#{$media-query}-flex {\n display: flex !important;\n }\n .d-#{$media-query}-inline {\n display: inline !important;\n }\n .d-#{$media-query}-inline-block {\n display: inline-block !important;\n }\n .d-#{$media-query}-none {\n display: none !important;\n }\n }\n }\n}\n\n// Horizontal alignment\n\n.float-left {\n float: left !important;\n}\n\n.float-right {\n float: right !important;\n}\n\n.flex-justify-start {\n justify-content: flex-start !important;\n}\n\n.flex-justify-end {\n justify-content: flex-end !important;\n}\n\n.flex-justify-between {\n justify-content: space-between !important;\n}\n\n.flex-justify-around {\n justify-content: space-around !important;\n}\n\n// Vertical alignment\n\n.v-align-baseline {\n vertical-align: baseline !important;\n}\n\n.v-align-bottom {\n vertical-align: bottom !important;\n}\n\n.v-align-middle {\n vertical-align: middle !important;\n}\n\n.v-align-text-bottom {\n vertical-align: text-bottom !important;\n}\n\n.v-align-text-top {\n vertical-align: text-top !important;\n}\n\n.v-align-top {\n vertical-align: top !important;\n}\n","// Utility classes for typography\n\n.fs-1 {\n @include fs-1;\n}\n\n.fs-2 {\n @include fs-2;\n}\n\n.fs-3 {\n @include fs-3;\n}\n\n.fs-4 {\n @include fs-4;\n}\n\n.fs-5 {\n @include fs-5;\n}\n\n.fs-6 {\n @include fs-6;\n}\n\n.fs-7 {\n @include fs-7;\n}\n\n.fs-8 {\n @include fs-8;\n}\n\n.fs-9 {\n @include fs-9;\n}\n\n.fs-10 {\n @include fs-10;\n}\n\n.fw-300 {\n font-weight: 300 !important;\n}\n\n.fw-400 {\n font-weight: 400 !important;\n}\n\n.fw-500 {\n font-weight: 500 !important;\n}\n\n.fw-700 {\n font-weight: 700 !important;\n}\n\n.lh-0 {\n line-height: 0 !important;\n}\n\n.lh-default {\n line-height: $body-line-height;\n}\n\n.lh-tight {\n line-height: $body-heading-line-height;\n}\n\n.ls-5 {\n letter-spacing: 0.05em !important;\n}\n\n.ls-10 {\n letter-spacing: 0.1em !important;\n}\n\n.ls-0 {\n letter-spacing: 0 !important;\n}\n\n.text-uppercase {\n text-transform: uppercase !important;\n}\n","// Utility classes for lists\n\n// stylelint-disable selector-max-type\n\n.list-style-none {\n padding: 0 !important;\n margin: 0 !important;\n list-style: none !important;\n\n li {\n &::before {\n display: none !important;\n }\n }\n}\n","// Utility classes for margins and padding\n\n// stylelint-disable block-opening-brace-space-after, block-opening-brace-space-before\n\n// Margin spacer utilities\n\n.mx-auto {\n margin-right: auto !important;\n margin-left: auto !important;\n}\n\n@for $i from 1 through length($spacers) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .m-0, .m-1, .m-2...\n .m-#{$scale} {\n margin: #{$size} !important;\n }\n .mt-#{$scale} {\n margin-top: #{$size} !important;\n }\n .mr-#{$scale} {\n margin-right: #{$size} !important;\n }\n .mb-#{$scale} {\n margin-bottom: #{$size} !important;\n }\n .ml-#{$scale} {\n margin-left: #{$size} !important;\n }\n\n .mx-#{$scale} {\n margin-right: #{$size} !important;\n margin-left: #{$size} !important;\n }\n\n .my-#{$scale} {\n margin-top: #{$size} !important;\n margin-bottom: #{$size} !important;\n }\n\n .mxn-#{$scale} {\n margin-right: -#{$size} !important;\n margin-left: -#{$size} !important;\n }\n .mx-#{$scale}-auto {\n margin-right: auto !important;\n margin-left: auto !important;\n }\n}\n\n@each $media-query in map-keys($media-queries) {\n @for $i from 1 through length($spacers) {\n @include mq($media-query) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .m-sm-0, .m-md-1, .m-lg-2...\n .m-#{$media-query}-#{$scale} {\n margin: #{$size} !important;\n }\n .mt-#{$media-query}-#{$scale} {\n margin-top: #{$size} !important;\n }\n .mr-#{$media-query}-#{$scale} {\n margin-right: #{$size} !important;\n }\n .mb-#{$media-query}-#{$scale} {\n margin-bottom: #{$size} !important;\n }\n .ml-#{$media-query}-#{$scale} {\n margin-left: #{$size} !important;\n }\n\n .mx-#{$media-query}-#{$scale} {\n margin-right: #{$size} !important;\n margin-left: #{$size} !important;\n }\n\n .my-#{$media-query}-#{$scale} {\n margin-top: #{$size} !important;\n margin-bottom: #{$size} !important;\n }\n\n .mxn-#{$media-query}-#{$scale} {\n margin-right: -#{$size} !important;\n margin-left: -#{$size} !important;\n }\n }\n }\n}\n\n// Padding spacer utilities\n\n@for $i from 1 through length($spacers) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .p-0, .p-1, .p-2...\n .p-#{$scale} {\n padding: #{$size} !important;\n }\n .pt-#{$scale} {\n padding-top: #{$size} !important;\n }\n .pr-#{$scale} {\n padding-right: #{$size} !important;\n }\n .pb-#{$scale} {\n padding-bottom: #{$size} !important;\n }\n .pl-#{$scale} {\n padding-left: #{$size} !important;\n }\n\n .px-#{$scale} {\n padding-right: #{$size} !important;\n padding-left: #{$size} !important;\n }\n\n .py-#{$scale} {\n padding-top: #{$size} !important;\n padding-bottom: #{$size} !important;\n }\n}\n\n@each $media-query in map-keys($media-queries) {\n @include mq($media-query) {\n @for $i from 1 through length($spacers) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .p-sm-0, .p-md-1, .p-lg-2...\n .p-#{$media-query}-#{$scale} {\n padding: #{$size} !important;\n }\n .pt-#{$media-query}-#{$scale} {\n padding-top: #{$size} !important;\n }\n .pr-#{$media-query}-#{$scale} {\n padding-right: #{$size} !important;\n }\n .pb-#{$media-query}-#{$scale} {\n padding-bottom: #{$size} !important;\n }\n .pl-#{$media-query}-#{$scale} {\n padding-left: #{$size} !important;\n }\n\n .px-#{$media-query}-#{$scale} {\n padding-right: #{$size} !important;\n padding-left: #{$size} !important;\n }\n\n .py-#{$media-query}-#{$scale} {\n padding-top: #{$size} !important;\n padding-bottom: #{$size} !important;\n }\n }\n }\n}\n","// stylelint-disable selector-max-specificity, selector-max-id, selector-max-type, selector-no-qualifying-type\n\n@media print {\n .site-footer,\n .site-button,\n #edit-this-page,\n #back-to-top,\n .site-nav,\n .main-header {\n display: none !important;\n }\n\n hr {\n margin-top: 1rem;\n margin-bottom: 1rem;\n }\n\n .side-bar {\n width: 100%;\n height: auto;\n border-right: 0 !important;\n }\n\n .site-header {\n border-bottom: 1px solid $border-color;\n }\n\n .site-title {\n font-size: 1rem !important;\n font-weight: 700 !important;\n }\n\n .text-small {\n font-size: 8pt !important;\n }\n\n pre.highlight {\n border: 1px solid $border-color;\n }\n\n .main {\n max-width: none;\n margin-left: 0;\n }\n}\n","// Skipnav\n// Skip to main content\n\na.skip-to-main {\n left: -999px;\n position: absolute;\n top: auto;\n width: 1px;\n height: 1px;\n overflow: hidden;\n z-index: -999;\n}\n\na.skip-to-main:focus,\na.skip-to-main:active {\n color: $link-color;\n background-color: $body-background-color;\n left: auto;\n top: auto;\n width: 30%;\n height: auto;\n overflow: auto;\n margin: 10px 35%;\n padding: 5px;\n border-radius: 15px;\n border: 4px solid $btn-primary-color;\n text-align: center;\n font-size: 1.2em;\n z-index: 999;\n}\n","\n@import \"./support/support\";\n@import \"./custom/setup\";\n@import \"./color_schemes/light\";\n\n@import \"./color_schemes/meshtastic-dark\";\n\n@import \"./modules\";\ndiv.opaque {\n background-color: $body-background-color;\n}\n\np.tip, blockquote.tip {\n border: 1px $green-000 solid;\n border-left: $border-radius solid $green-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n \n &::before {\n color: $green-300;\n content: \"Tip\";\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n \n > .tip-title {\n color: $green-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\np.tip-title, blockquote.tip-title {\n border: 1px $green-000 solid;\n border-left: $border-radius solid $green-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n > p:first-child {\n margin-top: 0;\n margin-bottom: 0;\n color: $green-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\nblockquote.tip {\n margin-left: 0;\n margin-right: 0;\n\n > p:first-child {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\nblockquote.tip-title {\n margin-left: 0;\n margin-right: 0;\n\n > p:nth-child(2) {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\n\n\np.note, blockquote.note {\n border: 1px $blue-000 solid;\n border-left: $border-radius solid $blue-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n \n &::before {\n color: $blue-300;\n content: \"Note\";\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n \n > .note-title {\n color: $blue-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\np.note-title, blockquote.note-title {\n border: 1px $blue-000 solid;\n border-left: $border-radius solid $blue-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n > p:first-child {\n margin-top: 0;\n margin-bottom: 0;\n color: $blue-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\nblockquote.note {\n margin-left: 0;\n margin-right: 0;\n\n > p:first-child {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\nblockquote.note-title {\n margin-left: 0;\n margin-right: 0;\n\n > p:nth-child(2) {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\n\n\np.warning, blockquote.warning {\n border: 1px $yellow-000 solid;\n border-left: $border-radius solid $yellow-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n \n &::before {\n color: $yellow-300;\n content: \"Warning\";\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n \n > .warning-title {\n color: $yellow-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\np.warning-title, blockquote.warning-title {\n border: 1px $yellow-000 solid;\n border-left: $border-radius solid $yellow-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n > p:first-child {\n margin-top: 0;\n margin-bottom: 0;\n color: $yellow-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\nblockquote.warning {\n margin-left: 0;\n margin-right: 0;\n\n > p:first-child {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\nblockquote.warning-title {\n margin-left: 0;\n margin-right: 0;\n\n > p:nth-child(2) {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\n\n@import \"./custom/custom\";\n\n\n"],"file":"just-the-docs-meshtastic-dark.css"} \ No newline at end of file +{"version":3,"sourceRoot":"","sources":["../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/vendor/accessible-pygments/github-light.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/vendor/normalize.scss/normalize.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/base.scss","../../_sass/color_schemes/meshtastic-dark.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/support/mixins/_typography.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/support/mixins/_layout.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/support/_variables.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/layout.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/content.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/navigation.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/typography.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/labels.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/buttons.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/support/mixins/_buttons.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/search.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/tables.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/code.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/utilities/_colors.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/utilities/_layout.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/utilities/_typography.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/utilities/_lists.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/utilities/_spacing.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/print.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/skiptomain.scss","just-the-docs-meshtastic-dark.scss"],"names":[],"mappings":";AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAUA;EAAkB;;;AAClB;EAAgB;EAAiB;AACjC;EAAkB;EAAiB;AACnC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAkB;EAAiB;AACnC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAqB;AACtC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAoB;AACrC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAgB;EAAiB;AACjC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AChFlC;AAEA;AAAA;AAGA;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAAA;AAKA;EACE;EACA;EACA;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;EACA;;;AAGF;AAAA;AAAA;AAIA;AAAA;EAEE;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;AAAA;EAGE;EACA;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;EAEE;EACA;EACA;EACA;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAAA;AAKA;AAAA;AAAA;AAAA;AAAA;EAKE;EACA;EACA;EACA;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;AAEE;EACA;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;AAEE;EACA;;;AAGF;AAAA;AAAA;AAIA;AAAA;AAAA;AAAA;EAIE;;;AAGF;AAAA;AAAA;AAIA;AAAA;AAAA;AAAA;EAIE;EACA;;;AAGF;AAAA;AAAA;AAIA;AAAA;AAAA;AAAA;EAIE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAOA;EACE;EACA;EACA;EACA;EACA;EACA;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;EAEE;EACA;;;AAGF;AAAA;AAAA;AAIA;AAAA;EAEE;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AC1VF;EACE,cCGa;;;ADAf;EACE;;;AAGF;EACE;;AEmBA;EACE;;AClBA;EHHJ;IEyBI;;;;AFnBJ;EACE,aIfiB;EJgBjB;EACA,aIbiB;EJcjB,OCTgB;EDUhB,kBCZsB;EDatB;;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAYE;;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAOE;EACA;EACA;EACA,aI1CyB;EJ2CzB,OCvCmB;;;AD0CrB;EACE;EACA;;;AAGF;EACE,OC7CW;ED8CX;;;AAGF;EACE;EACA,uBCvCa;EDwCb;;AAEA;EACE;;;AAIJ;EACE,aIvEiB;EJwEjB;EACA,aIvEiB;;;AJ0EnB;AAAA;EAEE;;;AAGF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;EACA;EACA,kBCvEa;EDwEb;;;AAIF;EACE;EAGA;EACA;EACA;EACA;;;AK7GF;EACE;EACA;EACA;EACA,kBJKc;;AEGZ;EEZJ;IAOI;IACA;IACA,ODwFW;ICvFX;IACA;IACA;;;AFAA;EEZJ;IAgBI;IACA,WD+EQ;;;ADpFR;EEQF;IAEI,aD2ES;;;ADrFX;EEQF;IAQI;;;AAOF;EACE;EACA,kBJ5BU;;AEGZ;EEuBA;IAKI;IACA,kBJjCgB;;;AIoClB;EACE;;AFjCJ;EEgCE;IAII;;;;AAOV;EACE;;AF5CE;EE2CJ;IAII;IACA,WDyCY;;;;ACrChB;EACE,aDaK;ECZL,gBDYK;EDvDL,eCuDK;EDtDL,cCsDK;;ADlEH;EEoDJ;IFrCI,eCqDG;IDpDH,cCoDG;;;ADpEH;EEoDJ;IAOI,aDSG;ICRH,gBDQG;;;;ACJP;EACE;EACA;;AFlEE;EEgEJ;IAKI;IACA;IACA,QDmBY;;;;ACfhB;AAAA;AAAA;EAGE;;AF9EE;EE2EJ;AAAA;AAAA;IAMI,ODGQ;;;;ACCZ;EACE;;AAEA;EACE;;AFzFA;EEqFJ;IAQI;IACA,aDxBG;ICyBH,gBD7BG;IC8BH;IACA;;;;AAIJ;EACE;EACA,YDbc;ECcd;;AFxGE;EEqGJ;IAMI,QDjBY;ICkBZ,YDlBY;ICmBZ;;;;AAIJ;EACE;EACA;EACA;EACA;EACA,aDrDK;ECsDL,gBDtDK;ECuDL,OJzHmB;EEYnB,eCuDK;EDtDL,cCsDK;;ADlEH;EEiHJ;IFlGI,eCqDG;IDpDH,cCoDG;;;AF/BL;EACE;;ACtCA;EEiHJ;IHvEI;IACA,aEhDuB;;;ADKvB;EEiHJ;IAcI,aD/DG;ICgEH,gBDhEG;;;;AC+EP;EACE;EACA;EACA,SDhFK;ECiFL;;;AFnJE;EEuJF;IACE;;;AAIJ;EACE;;;AAQF;EACE;;;AAOF;EACE;EACA;EACA;EACA,aD/GK;ECgHL,gBDhHK;EDvDL,eCuDK;EDtDL,cCsDK;;ADlEH;EE6KJ;IF9JI,eCqDG;IDpDH,cCoDG;;;AFvEL;EACE;;ACEA;EE6KJ;IH3KI;;;ACFA;EE6KJ;IAYI;IACA;;;;AAIJ;EACE,OD5HK;EC6HL,QD7HK;EC8HL,OJ/LW;;;AKXb;EACE,aFEoB;;AEApB;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAOE;;AAGF;EACE;EACA;;AAGF;AAAA;EAEE;;AAIA;EACE,YF+CC;;AE3CL;EACE;EACA;;AAEA;EACE;;AAEA;EACE;EACA;EACA;EACA,OFfM;EEgBN;EACA;;AJ1BN;EACE;;ACRA;EG2BE;IJfF;;;ACZA;EG2BE;IAUI;;;AAIJ;EACE;;AAGE;EACE;EACA;;AAOV;EACE;;AAGE;EACE;EACA;EACA,OF7CM;EE8CN;;AAMJ;EACE;;AAIJ;EACE;EACA;;AAKF;EACE;;AAGF;EACE;;AAGF;EACE;EACA;;AAGF;AAAA;EAEE;;AAGF;EACE;EACA;EACA;;AAEA;EACE;;AAIJ;EACE;EACA;EACA;;AAmBE;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EACE;;AASF;AAAA;AAAA;AAAA;AAAA;AAAA;EAEE;;AAKN;EACE;EACA;EACA,OFnFG;EEoFH;EACA,eFzFG;EE0FH,cF1FG;EE2FH;;AH1JA;EGmJF;IAUI;IACA;;;AAGF;EACE;EACA;EACA;EACA,OLnKO;EKoKP;;AAYF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EACE;;AAIJ;EACE;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAOE;EACA;EACA;;AAEA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAKE;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EACE;;AAIJ;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAWE,YF9JG;;;AG3EP;EACE;EACA;EACA;EACA;;AAEA;EACE;EACA;;ALoBF;EACE;;AClBA;EILF;IL2BE;;;ACtBA;EDOF;IACE;;;ACRA;EILF;ILiBE;;;AKPA;EACE;EACA,YH+DC;EG9DD,aHuDC;EGtDD,gBHsDC;EGrDD;EAEE,eH0DD;EGzDC,cHqDD;;ADlEH;EIKA;IAeI,YHgDD;IG/CC;IAEE,eH6CH;IG5CG,cH4CH;;;AGrCD;EACE,OHkCD;EGjCC,QHiCD;EGhCC;;AAGF;EACE;EACA;;AAGF;EAEE;EACA;;AASJ;EACE;EAEE;EAGF,OHUC;EGTD,QHSC;EGRD;EACA,ON7DO;;AEFT;EIsDA;IAYI,OHED;IGDC,QHCD;IGAC;;;AAGF;EACE;;AAQA;EACE;;AAKN;EACE;EACA,cHvBC;EGwBD;;AAEA;EACE;;AAEA;EACE,ONzFa;;AM4Ff;EACE,ON7Fa;;AMmGjB;EAEI;;AAMJ;EACE;;;AAMR;EACE;EACA;EACA;EACA;EACA;;ALhIA;EACE;;ACEA;EIwHJ;ILtHI;;;ACFA;EIwHJ;IASI;IACA,YHhEG;IGiEH;;EAEA;IACE;;;;AAMJ;EACE;;AAEA;EACE;;AAGE;EACE,ONlJG;;AMqJL;EACE,ONtJG;;;AM+Jb;EACE;EACA;;ALtKA;EACE;;ACEA;EIiKJ;IL/JI;;;AKoKF;EACE;EACA;EACA;EACA;EACA;;AAGF;EACE;EACA;EACA;EACA;;AJlLA;EIiKJ;IAqBI,eHpHG;;;;ADlEH;EI4LJ;IAEI;;;;AAIJ;EACE;EACA,eHnIK;EGoIL;;;AAGF;EACE;;AL5MA;EACE;;ACEA;EIwMJ;ILtMI;;;AK0MF;EACE;;AAGF;EACE;EACA,cHlJG;EGmJH,aHnJG;EGoJH,OHpMU;EGqMV;;AAIA;EACE;;;ACrON;AAAA;EAEE;;ANoEA;AAAA;EACE;EACA,aElEuB;;ADKvB;EKXJ;AAAA;IN4EI;;;;AA5BF;AAAA;AAAA;EACE;;ACtCA;EKJJ;AAAA;AAAA;IN8CI;IACA,aEhDuB;;;;AFgCzB;AAAA;EACE;;AC5BA;EKEJ;AAAA;IN8BI;;;;AMzBJ;AAAA;EAEE;EACA;EACA;;ANdA;AAAA;EACE;;ACEA;EKOJ;AAAA;INLI;;;;AMcJ;EACE;;;ANVA;AAAA;EACE;;ACRA;EKoBJ;AAAA;INRI;;;;AAfF;AAAA;EACE;;ACEA;EKyBJ;AAAA;INvBI;;;;AALF;EACE;;ACEA;EK8BJ;IN5BI;;;;AMgCJ;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;ACvDF;AAAA;EAEE;EACA;EACA,cLoEK;EKnEL,aLmEK;EKlEL,OLiBM;EKhBN;EACA;EACA,kBL6BS;EK5BT;;APLA;AAAA;EACE;;ACEA;EMRJ;AAAA;IPUI;;;;AOKJ;EACE,kBL4BU;;;AKzBZ;EACE,kBLcW;;;AKXb;EACE,kBL4BQ;;;AKzBV;EACE,OLFY;EKGZ,kBLkBW;;;AMlDb;EACE;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA,OTIW;ESHX;EACA;EACA;EACA,kBTiBkB;EShBlB;EACA,eNyEc;EMxEd,YACE;EAEF;;AAEA;EACE;EACA;EACA;;AAGF;EAEE;;AAGF;EAEE;;AAGF;EAIE;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;AAKA;EAEE;EACA;EACA;EACA;EACA;;;AAKN;EACE,OT1DW;ES2DX;EACA;;AAEA;EAIE;EACA;EACA;EACA;;AAGF;EACE;EACA;EACA,YACE;;AAIJ;EAEE;;;AAIJ;ECnGE,OP0BM;EOzBN;EACA;EACA,YACE;;AAGF;EAEE,OPiBI;EOhBJ;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;;ADgFJ;ECvGE,OP0BM;EOzBN;EACA;EACA,YACE;;AAGF;EAEE,OPiBI;EOhBJ;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;;ADoFJ;EC3GE,OP0BM;EOzBN;EACA;EACA,YACE;;AAGF;EAEE,OPiBI;EOhBJ;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;;ADwFJ;EC/GE,OP0BM;EOzBN;EACA;EACA,YACE;;AAGF;EAEE,OPiBI;EOhBJ;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;;AD4FJ;EACE;EACA;EACA;EACA;EACA;EACA;EACA;;;AE3HF;EACE;EACA;EACA;EACA,QRgFM;EQ/EN,SRuEK;EQtEL;;ATME;ESZJ;IASI;IACA;IACA;IACA;IACA;;;;AAIJ;EACE;EACA;EACA,QR8DK;EQ7DL;EACA,eRmEc;EQlEd,YACE;EAEF;;ATdE;ESKJ;IAYI;IACA;IACA,WRwEmB;IQvEnB;IACA;IACA;IACA;;;;AAIJ;EACE;EACA;EACA;EACA;EACA;EACA,OXnCgB;EWoChB,kBXTwB;EWUxB;EACA;EACA;EACA;EACA;;ATvCE;ES2BJ;IAeI;IACA;IACA,kBXhDoB;IWiDpB;;;AAGF;EACE;EACA;;AAEA;EACE,OXnDO;;;AWwDb;EACE;EACA;EACA;EACA,cRIK;;ADlEH;ES0DJ;IAOI,cRGG;IQFH;;;AAGF;EACE;EACA;EACA;EACA,ORzDU;;;AQ6Dd;EACE;EACA;EACA;EACA;EACA;EACA;EACA,kBX3DwB;EW4DxB,4BRRc;EQSd,2BRTc;EQUd,YACE;;ATxFA;ES6EJ;IAeI;IACA,ORFmB;IQGnB;;;;AAIJ;EACE;EACA,eRrCK;EQsCL;;AVpFA;EACE;;AClBA;ESkGJ;IV5EI;;;ACtBA;EDOF;IACE;;;ACRA;ESkGJ;IVtFI;;;;AUiGJ;EACE;EACA;;;AAGF;EACE;EACA;;AAEA;EAEE,kBXlGa;;;AWsGjB;EACE;EACA,aR9DK;EQ+DL,gBR/DK;;ADhEH;ES4HJ;IAMI;IACA;IACA,eRpEG;IQqEH;;;;AAIJ;EACE;EACA;EACA;;AAEA;EACE;;AVxIF;EACE;;ACRA;ES8IF;IVlIE;;;ACZA;EDHF;IACE;;;ACEA;ES8IF;IV5IE;;;AUqJF;EACE,ORtFG;EQuFH,QRvFG;EQwFH,cR1FG;EQ2FH,OXzJS;EW0JT;;AAGF;EACE;;;AAIJ;EACE;EACA;;;AAGF;EACE;EACA;EACA;EACA,OXtK4B;EWuK5B;EACA;;AV5LA;EACE;;ACYA;ESyKJ;IVjLI;;;;AU2LJ;EACE;EACA,aRrHK;EQsHL,gBRtHK;EQuHL,cRrHK;EQsHL,aRxHK;EQyHL,OXlL4B;EWmL5B;EACA,aR/GO;EQgHP,mBX9Ka;;ACjBb;EACE;;ACEA;ESmLJ;IVjLI;;;ACFA;ESmLJ;IAaI;IACA;IACA,cRlIG;IQmIH;IACA;;;;AAIJ;EACE,YR1IK;;;AQ6IP;EACE;;;AAGF;EACE;;AV1MA;EACE;;ACRA;ESgNJ;IVpMI;;;;AUyMJ;EACE;EACA,ORrJK;EQsJL,QRtJK;EQuJL;EACA,ORnJK;EQoJL,QRpJK;EQqJL,kBXnMwB;EWoMxB;EACA;EACA,YACE;EAEF;EACA;;;AAGF;EACE;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA,YACE;;;AAMF;EACE;EACA;EACA;EACA;EACA;EACA;;AAGF;EACE,QRxLI;EQyLJ;;ATjQA;ES+PF;IAKI,ORzKiB;IQ0KjB,YACE;;;AAKN;EACE,kBXnPsB;;AEzBtB;ES2QF;IAII;;;AT/QF;ESmRF;IAEI;;;AAIJ;EACE;;AAGF;EACE;EACA;EACA;EACA,YACE;;ATlSF;ESwSA;IACE;IACA;IACA;;;AAIJ;EACE,aRxOI;;ADxEJ;ES+SF;IAII;;;;AC9TN;EACE;EACA;EACA;EACA,eT0EK;ESzEL;EACA,eTkFc;ESjFd,YACE;;;AAIJ;EACE;EACA;EACA;;;AAGF;AAAA;EAEE;EACA;EACA,kBZIuB;EYHvB;EACA;;AXNA;AAAA;EACE;;ACRA;EUOJ;AAAA;IXKI;;;AWKF;AAAA;EACE;;;AAOE;AAAA;EAEE;;AAGF;EACE,gBTkCD;;;AS3BL;EACE;;;AC9CF;EACE;EACA;EACA,kBbcoB;EabpB;EACA,eV+EY;;;AU1EhB;EACE,cbUa;;;AayCf;AAAA;AAAA;EAGE;EACA,eVMK;EULL,kBblDsB;EamDtB,eVgBc;EUfd;EACA;EACA;EACA;;AAIA;AAAA;AAAA;EACE,OVLG;EUMH;EACA;EACA;EACA;EACA,SVVG;EUWH;EACA;EACA,ObhFc;EaiFd;;AAEA;AAAA;AAAA;EACE,MbpFY;;AauFd;AAAA;AAAA;EACE;EACA;EACA;;AAGF;AAAA;AAAA;EACE;EACA;;AAMF;AAAA;AAAA;EACE;EACA;;;AASJ;EACE;EACA,SV/CG;EUgDH;EACA;EACA,eVtCY;;AUyCd;AAAA;EAEE;EACA;EACA;;;AAUJ;EACE;EACA,eVrEK;;AU6CL;EACE;EACA,SV/CG;EUgDH;EACA;EACA,eVtCY;;AUyCd;AAAA;EAEE;EACA;EACA;;;AAwBF;AAAA;EAEE;EACA,SVpFG;EUqFH;EACA;EACA,eV3EY;;;AUmFhB;EACE;EACA;EACA;EACA;;AAEA;AAAA;EAEE;EACA;EACA,kBbhKoB;EaiKpB;;AZ9KF;AAAA;EACE;;ACEA;EWsKF;AAAA;IZpKE;;;AY8KF;EACE;EACA,eVjHG;EUkHH,cVlHG;;AUqHL;EACE;EACA;;;AAKJ;AAAA;EAEE,SV9HK;EU+HL,eV/HK;EUgIL;EACA;EACA,eVtHc;;AUwHd;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAIE;EACA;EACA;EACA;EACA;EACA;EACA;;;AAKJ;EACE;EACA;EACA;;;AAIF;AAAA;EAEE,YbnNsB;EasNpB,ObrNoB;;;Aa4NxB;EACE,Yb9NsB;;;AcpBxB;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAKF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;ACvOF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAKF;EACE;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;;;AbrBE;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ab5CJ;Ea+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;AAQR;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAKF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AdhHA;EACE;;ACYA;EcZJ;IfII;;;;AAKF;EACE;;ACEA;EcRJ;IfUI;;;;AAKF;EACE;;ACRA;EcJJ;IfgBI;;;;AAKF;EACE;;AClBA;EcAJ;IfsBI;;;;AAKF;EACE;;AC5BA;EcIJ;If4BI;;;;AAKF;EACE;;ACtCA;EcQJ;IfkCI;IACA,aEhDuB;;;;AFqDzB;EACE;EACA,aEvDuB;;ADKvB;EcYJ;If0CI;;;;AAKF;EACE;EACA,aElEuB;;ADKvB;EcgBJ;IfiDI;;;;AAKF;EACE;EACA,aE7EuB;;ADKvB;EcoBJ;IfwDI;;;;AAKF;EACE;EACA,aExFuB;;ADKvB;EcwBJ;If+DI;;;;Ae3DJ;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE,abxDiB;;;Aa2DnB;EACE,ab1DyB;;;Aa6D3B;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AC/EF;EACE;EACA;EACA;;AAGE;EACE;;;ACLN;EACE;EACA;;;AAQA;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AhBlCA;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhBzEJ;EgB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AAaN;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AhB7GA;EgBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhB/IJ;EgBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhB/IJ;EgBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhB/IJ;EgBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AhB/IJ;EgBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AC3JR;EACE;AAAA;AAAA;AAAA;AAAA;AAAA;IAME;;EAGF;IACE;IACA;;EAGF;IACE;IACA;IACA;;EAGF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;;EAGF;IACE;;EAGF;IACE;IACA;;;ACvCJ;EACE;EACA;EACA;EACA;EACA;EACA;EACA;;;AAGF;AAAA;EAEE,OpBCW;EoBAX,kBpBNsB;EoBOtB;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;;;ACpBF;EACE,kBrBCsB;;;AqBExB;EACI;EACA;EACA,elB4EY;EkB3EZ;EACA;;AAEA;EACI,OlB8BI;EkB7BJ;EACA;EACA;EACA;EACA;EACA;;AAGJ;EACE,OlBoBM;EkBnBN;EACA;EACA;EACA;EACA;;;AAIN;EACI;EACA;EACA,elBiDY;EkBhDZ;EACA;;AACA;EACE;EACA;EACA,OlBEM;EkBDN;EACA;EACA;EACA;EACA;;;AAIN;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAIJ;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAMJ;EACI;EACA;EACA,elBGY;EkBFZ;EACA;;AAEA;EACI,OlB/CG;EkBgDH;EACA;EACA;EACA;EACA;EACA;;AAGJ;EACE,OlBzDK;EkB0DL;EACA;EACA;EACA;EACA;;;AAIN;EACI;EACA;EACA,elBxBY;EkByBZ;EACA;;AACA;EACE;EACA;EACA,OlB3EK;EkB4EL;EACA;EACA;EACA;EACA;;;AAIN;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAIJ;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAMJ;EACI;EACA;EACA,elBtEY;EkBuEZ;EACA;;AAEA;EACI,OlBhHK;EkBiHL;EACA;EACA;EACA;EACA;EACA;;AAGJ;EACE,OlB1HO;EkB2HP;EACA;EACA;EACA;EACA;;;AAIN;EACI;EACA;EACA,elBjGY;EkBkGZ;EACA;;AACA;EACE;EACA;EACA,OlB5IO;EkB6IP;EACA;EACA;EACA;EACA;;;AAIN;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAIJ;EACE;EACA;;AAEA;EACE;;AAGF;EACE","sourcesContent":["/*\ngenerated by accessible-pygments \nCopyright (c) 2022, Quansight Labs\nLicensed under the BSD license, see LICENSE for details.\n--\ngenerated by Pygments \nCopyright 2006-2025 by the Pygments team.\nLicensed under the BSD license, see LICENSE for details.\n*/\n\n.highlight .hll { background-color: #0969da4a }\n.highlight .c { color: #6E7781 } /* Comment */\n.highlight .err { color: #CF222E } /* Error */\n.highlight .k { color: #CF222E } /* Keyword */\n.highlight .l { color: #953800 } /* Literal */\n.highlight .n { color: #8250DF } /* Name */\n.highlight .o { color: #116329 } /* Operator */\n.highlight .p { color: #24292F } /* Punctuation */\n.highlight .ch { color: #6E7781 } /* Comment.Hashbang */\n.highlight .cm { color: #6E7781 } /* Comment.Multiline */\n.highlight .cp { color: #6E7781 } /* Comment.Preproc */\n.highlight .cpf { color: #6E7781 } /* Comment.PreprocFile */\n.highlight .c1 { color: #6E7781 } /* Comment.Single */\n.highlight .cs { color: #6E7781 } /* Comment.Special */\n.highlight .gd { color: #0550AE } /* Generic.Deleted */\n.highlight .ge { font-style: italic } /* Generic.Emph */\n.highlight .gr { color: #CF222E } /* Generic.Error */\n.highlight .gh { color: #0550AE } /* Generic.Heading */\n.highlight .gs { font-weight: bold } /* Generic.Strong */\n.highlight .gu { color: #0550AE } /* Generic.Subheading */\n.highlight .kc { color: #0550AE } /* Keyword.Constant */\n.highlight .kd { color: #CF222E } /* Keyword.Declaration */\n.highlight .kn { color: #CF222E } /* Keyword.Namespace */\n.highlight .kp { color: #CF222E } /* Keyword.Pseudo */\n.highlight .kr { color: #CF222E } /* Keyword.Reserved */\n.highlight .kt { color: #CF222E } /* Keyword.Type */\n.highlight .ld { color: #953800 } /* Literal.Date */\n.highlight .m { color: #953800 } /* Literal.Number */\n.highlight .s { color: #0550AE } /* Literal.String */\n.highlight .na { color: #953800 } /* Name.Attribute */\n.highlight .nb { color: #953800 } /* Name.Builtin */\n.highlight .nc { color: #0550AE } /* Name.Class */\n.highlight .no { color: #0550AE } /* Name.Constant */\n.highlight .nd { color: #953800 } /* Name.Decorator */\n.highlight .ni { color: #116329 } /* Name.Entity */\n.highlight .ne { color: #8250DF } /* Name.Exception */\n.highlight .nf { color: #0550AE } /* Name.Function */\n.highlight .nl { color: #953800 } /* Name.Label */\n.highlight .nn { color: #24292F } /* Name.Namespace */\n.highlight .nx { color: #8250DF } /* Name.Other */\n.highlight .py { color: #0550AE } /* Name.Property */\n.highlight .nt { color: #116329 } /* Name.Tag */\n.highlight .nv { color: #953800 } /* Name.Variable */\n.highlight .ow { color: #8250DF } /* Operator.Word */\n.highlight .pm { color: #24292F } /* Punctuation.Marker */\n.highlight .w { color: #24292F } /* Text.Whitespace */\n.highlight .mb { color: #953800 } /* Literal.Number.Bin */\n.highlight .mf { color: #953800 } /* Literal.Number.Float */\n.highlight .mh { color: #953800 } /* Literal.Number.Hex */\n.highlight .mi { color: #953800 } /* Literal.Number.Integer */\n.highlight .mo { color: #953800 } /* Literal.Number.Oct */\n.highlight .sa { color: #0550AE } /* Literal.String.Affix */\n.highlight .sb { color: #0550AE } /* Literal.String.Backtick */\n.highlight .sc { color: #0550AE } /* Literal.String.Char */\n.highlight .dl { color: #0550AE } /* Literal.String.Delimiter */\n.highlight .sd { color: #0550AE } /* Literal.String.Doc */\n.highlight .s2 { color: #0550AE } /* Literal.String.Double */\n.highlight .se { color: #0550AE } /* Literal.String.Escape */\n.highlight .sh { color: #0550AE } /* Literal.String.Heredoc */\n.highlight .si { color: #0550AE } /* Literal.String.Interpol */\n.highlight .sx { color: #0550AE } /* Literal.String.Other */\n.highlight .sr { color: #0550AE } /* Literal.String.Regex */\n.highlight .s1 { color: #0550AE } /* Literal.String.Single */\n.highlight .ss { color: #0550AE } /* Literal.String.Symbol */\n.highlight .bp { color: #953800 } /* Name.Builtin.Pseudo */\n.highlight .fm { color: #0550AE } /* Name.Function.Magic */\n.highlight .vc { color: #953800 } /* Name.Variable.Class */\n.highlight .vg { color: #953800 } /* Name.Variable.Global */\n.highlight .vi { color: #953800 } /* Name.Variable.Instance */\n.highlight .vm { color: #953800 } /* Name.Variable.Magic */\n.highlight .il { color: #953800 } /* Literal.Number.Integer.Long */\n","/*! normalize.css v8.0.1 | MIT License | github.com/necolas/normalize.css */\n\n/* Document\n ========================================================================== */\n\n/**\n * 1. Correct the line height in all browsers.\n * 2. Prevent adjustments of font size after orientation changes in iOS.\n */\n\nhtml {\n line-height: 1.15; /* 1 */\n text-size-adjust: 100%; /* 2 */\n}\n\n/* Sections\n ========================================================================== */\n\n/**\n * Remove the margin in all browsers.\n */\n\nbody {\n margin: 0;\n}\n\n/**\n * Render the `main` element consistently in IE.\n */\n\nmain {\n display: block;\n}\n\n/**\n * Correct the font size and margin on `h1` elements within `section` and\n * `article` contexts in Chrome, Firefox, and Safari.\n */\n\nh1 {\n font-size: 2em;\n margin: 0.67em 0;\n}\n\n/* Grouping content\n ========================================================================== */\n\n/**\n * 1. Add the correct box sizing in Firefox.\n * 2. Show the overflow in Edge and IE.\n */\n\nhr {\n box-sizing: content-box; /* 1 */\n height: 0; /* 1 */\n overflow: visible; /* 2 */\n}\n\n/**\n * 1. Correct the inheritance and scaling of font size in all browsers.\n * 2. Correct the odd `em` font sizing in all browsers.\n */\n\npre {\n font-family: monospace; /* 1 */\n font-size: 1em; /* 2 */\n}\n\n/* Text-level semantics\n ========================================================================== */\n\n/**\n * Remove the gray background on active links in IE 10.\n */\n\na {\n background-color: transparent;\n}\n\n/**\n * 1. Remove the bottom border in Chrome 57-\n * 2. Add the correct text decoration in Chrome, Edge, IE, Opera, and Safari.\n */\n\nabbr[title] {\n border-bottom: none; /* 1 */\n text-decoration: underline; /* 2 */\n text-decoration: underline dotted; /* 2 */\n}\n\n/**\n * Add the correct font weight in Chrome, Edge, and Safari.\n */\n\nb,\nstrong {\n font-weight: bolder;\n}\n\n/**\n * 1. Correct the inheritance and scaling of font size in all browsers.\n * 2. Correct the odd `em` font sizing in all browsers.\n */\n\ncode,\nkbd,\nsamp {\n font-family: monospace; /* 1 */\n font-size: 1em; /* 2 */\n}\n\n/**\n * Add the correct font size in all browsers.\n */\n\nsmall {\n font-size: 80%;\n}\n\n/**\n * Prevent `sub` and `sup` elements from affecting the line height in\n * all browsers.\n */\n\nsub,\nsup {\n font-size: 75%;\n line-height: 0;\n position: relative;\n vertical-align: baseline;\n}\n\nsub {\n bottom: -0.25em;\n}\n\nsup {\n top: -0.5em;\n}\n\n/* Embedded content\n ========================================================================== */\n\n/**\n * Remove the border on images inside links in IE 10.\n */\n\nimg {\n border-style: none;\n}\n\n/* Forms\n ========================================================================== */\n\n/**\n * 1. Change the font styles in all browsers.\n * 2. Remove the margin in Firefox and Safari.\n */\n\nbutton,\ninput,\noptgroup,\nselect,\ntextarea {\n font-family: inherit; /* 1 */\n font-size: 100%; /* 1 */\n line-height: 1.15; /* 1 */\n margin: 0; /* 2 */\n}\n\n/**\n * Show the overflow in IE.\n * 1. Show the overflow in Edge.\n */\n\nbutton,\ninput {\n /* 1 */\n overflow: visible;\n}\n\n/**\n * Remove the inheritance of text transform in Edge, Firefox, and IE.\n * 1. Remove the inheritance of text transform in Firefox.\n */\n\nbutton,\nselect {\n /* 1 */\n text-transform: none;\n}\n\n/**\n * Correct the inability to style clickable types in iOS and Safari.\n */\n\nbutton,\n[type=\"button\"],\n[type=\"reset\"],\n[type=\"submit\"] {\n appearance: button;\n}\n\n/**\n * Remove the inner border and padding in Firefox.\n */\n\nbutton::-moz-focus-inner,\n[type=\"button\"]::-moz-focus-inner,\n[type=\"reset\"]::-moz-focus-inner,\n[type=\"submit\"]::-moz-focus-inner {\n border-style: none;\n padding: 0;\n}\n\n/**\n * Restore the focus styles unset by the previous rule.\n */\n\nbutton:-moz-focusring,\n[type=\"button\"]:-moz-focusring,\n[type=\"reset\"]:-moz-focusring,\n[type=\"submit\"]:-moz-focusring {\n outline: 1px dotted ButtonText;\n}\n\n/**\n * Correct the padding in Firefox.\n */\n\nfieldset {\n padding: 0.35em 0.75em 0.625em;\n}\n\n/**\n * 1. Correct the text wrapping in Edge and IE.\n * 2. Correct the color inheritance from `fieldset` elements in IE.\n * 3. Remove the padding so developers are not caught out when they zero out\n * `fieldset` elements in all browsers.\n */\n\nlegend {\n box-sizing: border-box; /* 1 */\n color: inherit; /* 2 */\n display: table; /* 1 */\n max-width: 100%; /* 1 */\n padding: 0; /* 3 */\n white-space: normal; /* 1 */\n}\n\n/**\n * Add the correct vertical alignment in Chrome, Firefox, and Opera.\n */\n\nprogress {\n vertical-align: baseline;\n}\n\n/**\n * Remove the default vertical scrollbar in IE 10+.\n */\n\ntextarea {\n overflow: auto;\n}\n\n/**\n * 1. Add the correct box sizing in IE 10.\n * 2. Remove the padding in IE 10.\n */\n\n[type=\"checkbox\"],\n[type=\"radio\"] {\n box-sizing: border-box; /* 1 */\n padding: 0; /* 2 */\n}\n\n/**\n * Correct the cursor style of increment and decrement buttons in Chrome.\n */\n\n[type=\"number\"]::-webkit-inner-spin-button,\n[type=\"number\"]::-webkit-outer-spin-button {\n height: auto;\n}\n\n/**\n * 1. Correct the odd appearance in Chrome and Safari.\n * 2. Correct the outline style in Safari.\n */\n\n[type=\"search\"] {\n appearance: textfield; /* 1 */\n outline-offset: -2px; /* 2 */\n}\n\n/**\n * Remove the inner padding in Chrome and Safari on macOS.\n */\n\n[type=\"search\"]::-webkit-search-decoration {\n appearance: none;\n}\n\n/**\n * 1. Correct the inability to style clickable types in iOS and Safari.\n * 2. Change font properties to `inherit` in Safari.\n */\n\n::-webkit-file-upload-button {\n appearance: button; /* 1 */\n font: inherit; /* 2 */\n}\n\n/* Interactive\n ========================================================================== */\n\n/*\n * Add the correct display in Edge, IE 10+, and Firefox.\n */\n\ndetails {\n display: block;\n}\n\n/*\n * Add the correct display in all browsers.\n */\n\nsummary {\n display: list-item;\n}\n\n/* Misc\n ========================================================================== */\n\n/**\n * Add the correct display in IE 10+.\n */\n\ntemplate {\n display: none;\n}\n\n/**\n * Add the correct display in IE 10.\n */\n\n[hidden] {\n display: none;\n}\n","// Base element style overrides\n// stylelint-disable selector-no-type, selector-max-type, selector-max-specificity, selector-max-id\n\n:root {\n color-scheme: $color-scheme;\n}\n\n* {\n box-sizing: border-box;\n}\n\nhtml {\n scroll-behavior: smooth;\n\n @include fs-4;\n}\n\nbody {\n font-family: $body-font-family;\n font-size: inherit;\n line-height: $body-line-height;\n color: $body-text-color;\n background-color: $body-background-color;\n overflow-wrap: break-word;\n}\n\nol,\nul,\ndl,\npre,\naddress,\nblockquote,\ntable,\ndiv,\nhr,\nform,\nfieldset,\nnoscript .table-wrapper {\n margin-top: 0;\n}\n\nh1,\nh2,\nh3,\nh4,\nh5,\nh6,\n#toctitle {\n margin-top: 0;\n margin-bottom: 1em;\n font-weight: 500;\n line-height: $body-heading-line-height;\n color: $body-heading-color;\n}\n\np {\n margin-top: 1em;\n margin-bottom: 1em;\n}\n\na {\n color: $link-color;\n text-decoration: none;\n}\n\na:not([class]) {\n text-decoration: underline;\n text-decoration-color: $border-color;\n text-underline-offset: 2px;\n\n &:hover {\n text-decoration-color: rgba($link-color, 0.45);\n }\n}\n\ncode {\n font-family: $mono-font-family;\n font-size: 0.75em;\n line-height: $body-line-height;\n}\n\nfigure,\npre {\n margin: 0;\n}\n\nli {\n margin: 0.25em 0;\n}\n\nimg {\n max-width: 100%;\n height: auto;\n}\n\nhr {\n height: 1px;\n padding: 0;\n margin: $sp-6 0;\n background-color: $border-color;\n border: 0;\n}\n\n// adds a GitHub-style sidebar to blockquotes\nblockquote {\n margin: 10px 0;\n\n // resets user-agent stylesheets for blockquotes\n margin-block-start: 0;\n margin-inline-start: 0;\n padding-left: 1rem;\n border-left: 3px solid $border-color;\n}\n","// Meshtastic Material 3 — Dark color scheme for just-the-docs\n// Source: core/ui/.../Color.kt §8.3 (Dark Scheme)\n//\n// Brand colors:\n// Primary (Dark): #67EA94 (Green 500)\n// Surface (Dark): #1A1B26 (Neutral 900)\n\n$color-scheme: dark;\n\n// Body / page background\n$body-background-color: #1A1B26; // Neutral 900 — surfaceDark\n$sidebar-color: #1A1B26; // Neutral 900\n$body-text-color: #ECEDF3; // Neutral 100 — onSurfaceDark\n$body-heading-color: #ECEDF3; // Neutral 100\n\n// Links\n$link-color: #67EA94; // Green 500 — primaryDark\n$nav-link-color: #67EA94; // Green 500\n\n// Navigation\n$nav-child-link-color: #B8BAC8; // Neutral 300 — secondaryDark\n$search-result-preview-color: #B8BAC8;\n\n// Code\n$code-background-color: #0F1017; // Neutral 950 — surfaceContainerLowestDark\n$code-linenumber-color: #9496A6; // Neutral 400\n\n// Borders\n$border-color: #3D3E50; // Neutral 700 — outlineVariantDark\n$table-background-color: #242533; // Interpolated — surfaceContainerDark\n\n// Buttons\n$btn-primary-color: #67EA94; // Green 500\n$base-button-color: #2C2D3C; // Neutral 800\n\n// Feedback / callouts\n$feedback-color: #242533; // surfaceContainerDark\n\n// Search\n$search-background-color: #242533; // surfaceContainerDark\n","@mixin fs-1 {\n & {\n font-size: $font-size-1 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-1-sm !important;\n }\n}\n\n@mixin fs-2 {\n & {\n font-size: $font-size-2 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-3 !important;\n }\n}\n\n@mixin fs-3 {\n & {\n font-size: $font-size-3 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-4 !important;\n }\n}\n\n@mixin fs-4 {\n & {\n font-size: $font-size-4 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-5 !important;\n }\n}\n\n@mixin fs-5 {\n & {\n font-size: $font-size-5 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-6 !important;\n }\n}\n\n@mixin fs-6 {\n & {\n font-size: $font-size-6 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-7 !important;\n line-height: $body-heading-line-height;\n }\n}\n\n@mixin fs-7 {\n & {\n font-size: $font-size-7 !important;\n line-height: $body-heading-line-height;\n }\n\n @include mq(sm) {\n font-size: $font-size-8 !important;\n }\n}\n\n@mixin fs-8 {\n & {\n font-size: $font-size-8 !important;\n line-height: $body-heading-line-height;\n }\n\n @include mq(sm) {\n font-size: $font-size-9 !important;\n }\n}\n\n@mixin fs-9 {\n & {\n font-size: $font-size-9 !important;\n line-height: $body-heading-line-height;\n }\n\n @include mq(sm) {\n font-size: $font-size-10 !important;\n }\n}\n\n@mixin fs-10 {\n & {\n font-size: $font-size-10 !important;\n line-height: $body-heading-line-height;\n }\n\n @include mq(sm) {\n font-size: $font-size-10-sm !important;\n }\n}\n","// Media query\n\n// Media query mixin\n// Usage:\n// @include mq(md) {\n// ..medium and up styles\n// }\n@mixin mq($name) {\n // Retrieves the value from the key\n $value: map-get($media-queries, $name);\n\n // If the key exists in the map\n @if $value {\n // Prints a media query based on the value\n @media (min-width: $value) {\n @content;\n }\n } @else {\n @warn \"No value could be retrieved from `#{$media-query}`. Please make sure it is defined in `$media-queries` map.\";\n }\n}\n\n// Responsive container\n\n@mixin container {\n padding-right: $gutter-spacing-sm;\n padding-left: $gutter-spacing-sm;\n\n @include mq(md) {\n padding-right: $gutter-spacing;\n padding-left: $gutter-spacing;\n }\n}\n","// Typography\n\n// prettier-ignore\n$body-font-family: system-ui, -apple-system, blinkmacsystemfont, \"Segoe UI\",\n roboto, \"Helvetica Neue\", arial, sans-serif, \"Segoe UI Emoji\" !default;\n$mono-font-family: \"SFMono-Regular\", menlo, consolas, monospace !default;\n$root-font-size: 16px !default; // DEPRECATED: previously base font-size for rems\n$body-line-height: 1.4 !default;\n$content-line-height: 1.6 !default;\n$body-heading-line-height: 1.25 !default;\n\n// Font size\n// `-sm` suffix is the size at the small (and above) media query\n\n$font-size-1: 0.5625rem !default;\n$font-size-1-sm: 0.625rem !default;\n$font-size-2: 0.6875rem !default; // h4 - uppercased!, h6 not uppercased, text-small\n$font-size-3: 0.75rem !default; // h5\n$font-size-4: 0.875rem !default;\n$font-size-5: 1rem !default; // h3\n$font-size-6: 1.125rem !default; // h2\n$font-size-7: 1.5rem !default;\n$font-size-8: 2rem !default; // h1\n$font-size-9: 2.25rem !default;\n$font-size-10: 2.625rem !default;\n$font-size-10-sm: 3rem !default;\n\n// Colors\n\n$white: #fff !default;\n$grey-dk-000: #959396 !default;\n$grey-dk-100: #5c5962 !default;\n$grey-dk-200: #44434d !default;\n$grey-dk-250: #302d36 !default;\n$grey-dk-300: #27262b !default;\n$grey-lt-000: #f5f6fa !default;\n$grey-lt-100: #eeebee !default;\n$grey-lt-200: #ecebed !default;\n$grey-lt-300: #e6e1e8 !default;\n$purple-000: #7253ed !default;\n$purple-100: #5e41d0 !default;\n$purple-200: #4e26af !default;\n$purple-300: #381885 !default;\n$blue-000: #2c84fa !default;\n$blue-100: #2869e6 !default;\n$blue-200: #264caf !default;\n$blue-300: #183385 !default;\n$green-000: #41d693 !default;\n$green-100: #11b584 !default;\n$green-200: #009c7b !default;\n$green-300: #026e57 !default;\n$yellow-000: #ffeb82 !default;\n$yellow-100: #fadf50 !default;\n$yellow-200: #f7d12e !default;\n$yellow-300: #e7af06 !default;\n$red-000: #f77e7e !default;\n$red-100: #f96e65 !default;\n$red-200: #e94c4c !default;\n$red-300: #dd2e2e !default;\n\n// Spacing\n\n$spacing-unit: 1rem; // 1rem == 16px\n\n$spacers: (\n sp-0: 0,\n sp-1: $spacing-unit * 0.25,\n sp-2: $spacing-unit * 0.5,\n sp-3: $spacing-unit * 0.75,\n sp-4: $spacing-unit,\n sp-5: $spacing-unit * 1.5,\n sp-6: $spacing-unit * 2,\n sp-7: $spacing-unit * 2.5,\n sp-8: $spacing-unit * 3,\n sp-9: $spacing-unit * 3.5,\n sp-10: $spacing-unit * 4,\n) !default;\n$sp-1: map-get($spacers, sp-1) !default; // 0.25 rem == 4px\n$sp-2: map-get($spacers, sp-2) !default; // 0.5 rem == 8px\n$sp-3: map-get($spacers, sp-3) !default; // 0.75 rem == 12px\n$sp-4: map-get($spacers, sp-4) !default; // 1 rem == 16px\n$sp-5: map-get($spacers, sp-5) !default; // 1.5 rem == 24px\n$sp-6: map-get($spacers, sp-6) !default; // 2 rem == 32px\n$sp-7: map-get($spacers, sp-7) !default; // 2.5 rem == 40px\n$sp-8: map-get($spacers, sp-8) !default; // 3 rem == 48px\n$sp-9: map-get($spacers, sp-9) !default; // 3.5 rem == 56px\n$sp-10: map-get($spacers, sp-10) !default; // 4 rem == 64px\n\n// Borders\n\n$border: 1px solid !default;\n$border-radius: 4px !default;\n$border-color: $grey-lt-100 !default;\n\n// Grid system\n\n$gutter-spacing: $sp-6 !default;\n$gutter-spacing-sm: $sp-4 !default;\n$nav-width: 16.5rem !default;\n$nav-width-md: 15.5rem !default;\n$nav-list-item-height: $sp-6 !default;\n$nav-list-item-height-sm: $sp-8 !default;\n$nav-list-expander-right: true;\n$content-width: 50rem !default;\n$header-height: 3.75rem !default;\n$search-results-width: $content-width - $nav-width !default;\n$transition-duration: 400ms;\n\n// Media queries in pixels\n\n$media-queries: (\n xs: 20rem,\n sm: 31.25rem,\n md: $content-width,\n lg: $content-width + $nav-width,\n xl: 87.5rem,\n) !default;\n","// The basic two column layout\n\n.side-bar {\n z-index: 0;\n display: flex;\n flex-wrap: wrap;\n background-color: $sidebar-color;\n\n @include mq(md) {\n flex-flow: column nowrap;\n position: fixed;\n width: $nav-width-md;\n height: 100%;\n border-right: $border $border-color;\n align-items: flex-end;\n }\n\n @include mq(lg) {\n width: calc((100% - #{$nav-width + $content-width}) / 2 + #{$nav-width});\n min-width: $nav-width;\n }\n\n & + .main {\n @include mq(md) {\n margin-left: $nav-width-md;\n }\n\n @include mq(lg) {\n // stylelint-disable function-name-case\n // disable for Max(), we want to use the CSS max() function\n margin-left: Max(\n #{$nav-width},\n calc((100% - #{$nav-width + $content-width}) / 2 + #{$nav-width})\n );\n // stylelint-enable function-name-case\n }\n\n .main-header {\n display: none;\n background-color: $sidebar-color;\n\n @include mq(md) {\n display: flex;\n background-color: $body-background-color;\n }\n\n &.nav-open {\n display: block;\n\n @include mq(md) {\n display: flex;\n }\n }\n }\n }\n}\n\n.main {\n margin: auto;\n\n @include mq(md) {\n position: relative;\n max-width: $content-width;\n }\n}\n\n.main-content-wrap {\n padding-top: $gutter-spacing-sm;\n padding-bottom: $gutter-spacing-sm;\n\n @include container;\n\n @include mq(md) {\n padding-top: $gutter-spacing;\n padding-bottom: $gutter-spacing;\n }\n}\n\n.main-header {\n z-index: 0;\n border-bottom: $border $border-color;\n\n @include mq(md) {\n display: flex;\n justify-content: space-between;\n height: $header-height;\n }\n}\n\n.site-nav,\n.site-header,\n.site-footer {\n width: 100%;\n\n @include mq(lg) {\n width: $nav-width;\n }\n}\n\n.site-nav {\n display: none;\n\n &.nav-open {\n display: block;\n }\n\n @include mq(md) {\n display: block;\n padding-top: $sp-8;\n padding-bottom: $gutter-spacing-sm;\n overflow-y: auto;\n flex: 1 1 auto;\n }\n}\n\n.site-header {\n display: flex;\n min-height: $header-height;\n align-items: center;\n\n @include mq(md) {\n height: $header-height;\n max-height: $header-height;\n border-bottom: $border $border-color;\n }\n}\n\n.site-title {\n flex-grow: 1;\n display: flex;\n height: 100%;\n align-items: center;\n padding-top: $sp-3;\n padding-bottom: $sp-3;\n color: $body-heading-color;\n\n @include container;\n\n @include fs-6;\n\n @include mq(md) {\n padding-top: $sp-2;\n padding-bottom: $sp-2;\n }\n}\n\n@if variable-exists(logo) {\n .site-logo {\n width: 100%;\n height: 100%;\n background-image: url($logo);\n background-repeat: no-repeat;\n background-position: left center;\n background-size: contain;\n }\n}\n\n.site-button {\n display: flex;\n height: 100%;\n padding: $gutter-spacing-sm;\n align-items: center;\n}\n\n@include mq(md) {\n .site-header .site-button {\n display: none;\n }\n}\n\n.site-title:hover {\n background-image: linear-gradient(\n -90deg,\n rgba($feedback-color, 1) 0%,\n rgba($feedback-color, 0.8) 80%,\n rgba($feedback-color, 0) 100%\n );\n}\n\n.site-button:hover {\n background-image: linear-gradient(\n -90deg,\n rgba($feedback-color, 1) 0%,\n rgba($feedback-color, 0.8) 100%\n );\n}\n\n.site-footer {\n position: absolute;\n bottom: 0;\n left: 0;\n padding-top: $sp-4;\n padding-bottom: $sp-4;\n\n @include container;\n\n @include fs-2;\n\n @include mq(md) {\n position: static;\n justify-self: end;\n }\n}\n\n.icon {\n width: $sp-5;\n height: $sp-5;\n color: $link-color;\n}\n","@charset \"UTF-8\";\n\n// Styles for rendered markdown in the .main-content container\n// stylelint-disable selector-no-type, max-nesting-depth, selector-max-compound-selectors, selector-max-type, selector-max-specificity, selector-max-id\n\n.main-content {\n line-height: $content-line-height;\n\n ol,\n ul,\n dl,\n pre,\n address,\n blockquote,\n .table-wrapper {\n margin-top: 0.5em;\n }\n\n a {\n overflow: hidden;\n text-overflow: ellipsis;\n }\n\n ul,\n ol {\n padding-left: 1.5em;\n }\n\n li {\n .highlight {\n margin-top: $sp-1;\n }\n }\n\n ol {\n list-style-type: none;\n counter-reset: step-counter;\n\n > li {\n position: relative;\n\n &::before {\n position: absolute;\n top: 0.2em;\n left: -1.6em;\n color: $grey-dk-000;\n content: counter(step-counter);\n counter-increment: step-counter;\n @include fs-3;\n\n @include mq(sm) {\n top: 0.11em;\n }\n }\n\n ol {\n counter-reset: sub-counter;\n\n > li {\n &::before {\n content: counter(sub-counter, lower-alpha);\n counter-increment: sub-counter;\n }\n }\n }\n }\n }\n\n ul {\n list-style: none;\n\n > li {\n &::before {\n position: absolute;\n margin-left: -1.4em;\n color: $grey-dk-000;\n content: \"•\";\n }\n }\n }\n\n .task-list-item {\n &::before {\n content: \"\";\n }\n }\n\n .task-list-item-checkbox {\n margin-right: 0.6em;\n margin-left: -1.4em;\n\n // The same margin-left is used above for ul > li::before\n }\n\n hr + * {\n margin-top: 0;\n }\n\n h1:first-of-type {\n margin-top: 0.5em;\n }\n\n dl {\n display: grid;\n grid-template: auto / 10em 1fr;\n }\n\n dt,\n dd {\n margin: 0.25em 0;\n }\n\n dt {\n grid-column: 1;\n font-weight: 500;\n text-align: right;\n\n &::after {\n content: \":\";\n }\n }\n\n dd {\n grid-column: 2;\n margin-bottom: 0;\n margin-left: 1em;\n\n blockquote,\n div,\n dl,\n dt,\n h1,\n h2,\n h3,\n h4,\n h5,\n h6,\n li,\n ol,\n p,\n pre,\n table,\n ul,\n .table-wrapper {\n &:first-child {\n margin-top: 0;\n }\n }\n }\n\n dd,\n ol,\n ul {\n dl:first-child {\n dt:first-child,\n dd:nth-child(2) {\n margin-top: 0;\n }\n }\n }\n\n .anchor-heading {\n position: absolute;\n right: -$sp-4;\n width: $sp-5;\n height: 100%;\n padding-right: $sp-1;\n padding-left: $sp-1;\n overflow: visible;\n\n @include mq(md) {\n right: auto;\n left: -$sp-5;\n }\n\n svg {\n display: inline-block;\n width: 100%;\n height: 100%;\n color: $link-color;\n visibility: hidden;\n }\n }\n\n .anchor-heading:hover,\n .anchor-heading:focus,\n h1:hover > .anchor-heading,\n h2:hover > .anchor-heading,\n h3:hover > .anchor-heading,\n h4:hover > .anchor-heading,\n h5:hover > .anchor-heading,\n h6:hover > .anchor-heading {\n svg {\n visibility: visible;\n }\n }\n\n summary {\n cursor: pointer;\n }\n\n h1,\n h2,\n h3,\n h4,\n h5,\n h6,\n #toctitle {\n position: relative;\n margin-top: 1.5em;\n margin-bottom: 0.25em;\n\n + table,\n + .table-wrapper,\n + .code-example,\n + .highlighter-rouge,\n + .sectionbody .listingblock {\n margin-top: 1em;\n }\n\n + p:not(.label) {\n margin-top: 0;\n }\n }\n\n > h1:first-child,\n > h2:first-child,\n > h3:first-child,\n > h4:first-child,\n > h5:first-child,\n > h6:first-child,\n > .sect1:first-child > h2,\n > .sect2:first-child > h3,\n > .sect3:first-child > h4,\n > .sect4:first-child > h5,\n > .sect5:first-child > h6 {\n margin-top: $sp-2;\n }\n}\n","// Main nav, breadcrumb, etc...\n// stylelint-disable selector-no-type, max-nesting-depth, selector-max-compound-selectors, selector-max-type, selector-max-specificity\n\n.nav-list {\n padding: 0;\n margin-top: 0;\n margin-bottom: 0;\n list-style: none;\n\n .nav-list-item {\n position: relative;\n margin: 0;\n\n @include fs-4;\n\n @include mq(md) {\n @include fs-3;\n }\n\n .nav-list-link {\n display: block;\n min-height: $nav-list-item-height-sm;\n padding-top: $sp-1;\n padding-bottom: $sp-1;\n line-height: #{$nav-list-item-height-sm - 2 * $sp-1};\n @if $nav-list-expander-right {\n padding-right: $nav-list-item-height-sm;\n padding-left: $gutter-spacing-sm;\n } @else {\n padding-right: $gutter-spacing-sm;\n padding-left: $nav-list-item-height-sm;\n }\n\n @include mq(md) {\n min-height: $nav-list-item-height;\n line-height: #{$nav-list-item-height - 2 * $sp-1};\n @if $nav-list-expander-right {\n padding-right: $nav-list-item-height;\n padding-left: $gutter-spacing;\n } @else {\n padding-right: $gutter-spacing;\n padding-left: $nav-list-item-height;\n }\n }\n\n &.external > svg {\n width: $sp-4;\n height: $sp-4;\n vertical-align: text-bottom;\n }\n\n &.active {\n font-weight: 600;\n text-decoration: none;\n }\n\n &:hover,\n &.active {\n color: darken($link-color, 5%);\n background-image: linear-gradient(\n -90deg,\n rgba($feedback-color, 1) 0%,\n rgba($feedback-color, 0.8) 80%,\n rgba($feedback-color, 0) 100%\n );\n }\n }\n\n .nav-list-expander {\n position: absolute;\n @if $nav-list-expander-right {\n right: 0;\n }\n\n width: $nav-list-item-height-sm;\n height: $nav-list-item-height-sm;\n padding: #{$nav-list-item-height-sm * 0.25};\n color: $link-color;\n\n @include mq(md) {\n width: $nav-list-item-height;\n height: $nav-list-item-height;\n padding: #{$nav-list-item-height * 0.25};\n }\n\n &:hover {\n background-image: linear-gradient(\n -90deg,\n rgba($feedback-color, 1) 0%,\n rgba($feedback-color, 0.8) 100%\n );\n }\n\n @if $nav-list-expander-right {\n svg {\n transform: rotate(90deg);\n }\n }\n }\n\n > .nav-list {\n display: none;\n padding-left: $sp-3;\n list-style: none;\n\n .nav-list-item {\n position: relative;\n\n .nav-list-link {\n color: $nav-child-link-color;\n }\n\n .nav-list-expander {\n color: $nav-child-link-color;\n }\n }\n }\n\n &.active {\n > .nav-list-expander svg {\n @if $nav-list-expander-right {\n transform: rotate(-90deg);\n } @else {\n transform: rotate(90deg);\n }\n }\n\n > .nav-list {\n display: block;\n }\n }\n }\n}\n\n.nav-category {\n padding: $sp-2 $gutter-spacing-sm;\n font-weight: 600;\n text-align: start;\n text-transform: uppercase;\n border-bottom: $border $border-color;\n @include fs-2;\n\n @include mq(md) {\n padding: $sp-2 $gutter-spacing;\n margin-top: $gutter-spacing-sm;\n text-align: start;\n\n &:first-child {\n margin-top: 0;\n }\n }\n}\n\n.nav-list.nav-category-list {\n > .nav-list-item {\n margin: 0;\n\n > .nav-list {\n padding: 0;\n\n > .nav-list-item {\n > .nav-list-link {\n color: $link-color;\n }\n\n > .nav-list-expander {\n color: $link-color;\n }\n }\n }\n }\n}\n\n// Aux nav\n\n.aux-nav {\n height: 100%;\n overflow-x: auto;\n @include fs-2;\n\n .aux-nav-list {\n display: flex;\n height: 100%;\n padding: 0;\n margin: 0;\n list-style: none;\n }\n\n .aux-nav-list-item {\n display: inline-block;\n height: 100%;\n padding: 0;\n margin: 0;\n }\n\n @include mq(md) {\n padding-right: $gutter-spacing-sm;\n }\n}\n\n// Breadcrumb nav\n\n.breadcrumb-nav {\n @include mq(md) {\n margin-top: -$sp-4;\n }\n}\n\n.breadcrumb-nav-list {\n padding-left: 0;\n margin-bottom: $sp-3;\n list-style: none;\n}\n\n.breadcrumb-nav-list-item {\n display: table-cell;\n @include fs-2;\n\n &::before {\n display: none;\n }\n\n &::after {\n display: inline-block;\n margin-right: $sp-2;\n margin-left: $sp-2;\n color: $grey-dk-000;\n content: \"/\";\n }\n\n &:last-child {\n &::after {\n content: \"\";\n }\n }\n}\n","// Typography\n// stylelint-disable selector-no-type, selector-max-type, selector-max-specificity, selector-max-id\n\nh1,\n.text-alpha {\n font-weight: 300;\n\n @include fs-8;\n}\n\nh2,\n.text-beta,\n#toctitle {\n @include fs-6;\n}\n\nh3,\n.text-gamma {\n @include fs-5;\n}\n\nh4,\n.text-delta {\n font-weight: 400;\n text-transform: uppercase;\n letter-spacing: 0.1em;\n\n @include fs-2;\n}\n\nh4 code {\n text-transform: none;\n}\n\nh5,\n.text-epsilon {\n @include fs-3;\n}\n\nh6,\n.text-zeta {\n @include fs-2;\n}\n\n.text-small {\n @include fs-2;\n}\n\n.text-mono {\n font-family: $mono-font-family !important;\n}\n\n.text-left {\n text-align: left !important;\n}\n\n.text-center {\n text-align: center !important;\n}\n\n.text-right {\n text-align: right !important;\n}\n","// Labels (not the form kind)\n\n// this :not() prevents a style clash with Mermaid.js's\n// diagram labels, which also use .label\n// for more, see https://github.com/just-the-docs/just-the-docs/issues/1272\n// and the accompanying PR\n.label:not(g),\n.label-blue:not(g) {\n display: inline-block;\n padding: 0.16em 0.56em;\n margin-right: $sp-2;\n margin-left: $sp-2;\n color: $white;\n text-transform: uppercase;\n vertical-align: middle;\n background-color: $blue-100;\n border-radius: 12px;\n\n @include fs-2;\n}\n\n.label-green:not(g) {\n background-color: $green-300;\n}\n\n.label-purple:not(g) {\n background-color: $purple-100;\n}\n\n.label-red:not(g) {\n background-color: $red-300;\n}\n\n.label-yellow:not(g) {\n color: $grey-dk-200;\n background-color: $yellow-200;\n}\n","// Buttons and things that look like buttons\n// stylelint-disable color-named\n\n.btn {\n display: inline-block;\n box-sizing: border-box;\n padding: 0.3em 1em;\n margin: 0;\n font-family: inherit;\n font-size: inherit;\n font-weight: 500;\n line-height: 1.5;\n color: $link-color;\n text-decoration: none;\n vertical-align: baseline;\n cursor: pointer;\n background-color: $base-button-color;\n border-width: 0;\n border-radius: $border-radius;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n appearance: none;\n\n &:focus {\n text-decoration: none;\n outline: none;\n box-shadow: 0 0 0 3px rgba(blue, 0.25);\n }\n\n &:focus:hover,\n &.selected:focus {\n box-shadow: 0 0 0 3px rgba(blue, 0.25);\n }\n\n &:hover,\n &.zeroclipboard-is-hover {\n color: darken($link-color, 2%);\n }\n\n &:hover,\n &:active,\n &.zeroclipboard-is-hover,\n &.zeroclipboard-is-active {\n text-decoration: none;\n background-color: darken($base-button-color, 1%);\n }\n\n &:active,\n &.selected,\n &.zeroclipboard-is-active {\n background-color: darken($base-button-color, 3%);\n background-image: none;\n box-shadow: inset 0 2px 4px rgba(0, 0, 0, 0.15);\n }\n\n &.selected:hover {\n background-color: darken(#dcdcdc, 5%);\n }\n\n &:disabled,\n &.disabled {\n &,\n &:hover {\n color: rgba(102, 102, 102, 0.5);\n cursor: default;\n background-color: rgba(229, 229, 229, 0.5);\n background-image: none;\n box-shadow: none;\n }\n }\n}\n\n.btn-outline {\n color: $link-color;\n background: transparent;\n box-shadow: inset 0 0 0 2px $grey-lt-300;\n\n &:hover,\n &:active,\n &.zeroclipboard-is-hover,\n &.zeroclipboard-is-active {\n color: darken($link-color, 4%);\n text-decoration: none;\n background-color: transparent;\n box-shadow: inset 0 0 0 3px $grey-lt-300;\n }\n\n &:focus {\n text-decoration: none;\n outline: none;\n box-shadow:\n inset 0 0 0 2px $grey-dk-100,\n 0 0 0 3px rgba(blue, 0.25);\n }\n\n &:focus:hover,\n &.selected:focus {\n box-shadow: inset 0 0 0 2px $grey-dk-100;\n }\n}\n\n.btn-primary {\n @include btn-color($white, $btn-primary-color);\n}\n\n.btn-purple {\n @include btn-color($white, $purple-100);\n}\n\n.btn-blue {\n @include btn-color($white, $blue-200);\n}\n\n.btn-green {\n @include btn-color($white, $green-300);\n}\n\n.btn-reset {\n background: none;\n border: none;\n margin: 0;\n text-align: inherit;\n font: inherit;\n border-radius: 0;\n appearance: none;\n}\n","// Colored button\n\n@mixin btn-color($fg, $bg) {\n color: $fg;\n background-color: darken($bg, 2%);\n background-image: linear-gradient(lighten($bg, 5%), darken($bg, 2%));\n box-shadow:\n 0 1px 3px rgba(0, 0, 0, 0.25),\n 0 4px 10px rgba(0, 0, 0, 0.12);\n\n &:hover,\n &.zeroclipboard-is-hover {\n color: $fg;\n background-color: darken($bg, 4%);\n background-image: linear-gradient((lighten($bg, 2%), darken($bg, 4%)));\n }\n\n &:active,\n &.selected,\n &.zeroclipboard-is-active {\n background-color: darken($bg, 5%);\n background-image: none;\n box-shadow: inset 0 2px 4px rgba(0, 0, 0, 0.15);\n }\n\n &.selected:hover {\n background-color: darken($bg, 10%);\n }\n}\n","// Search input and autocomplete\n\n.search {\n position: relative;\n z-index: 2;\n flex-grow: 1;\n height: $sp-10;\n padding: $sp-2;\n transition: padding linear #{$transition-duration * 0.5};\n\n @include mq(md) {\n position: relative !important;\n width: auto !important;\n height: 100% !important;\n padding: 0;\n transition: none;\n }\n}\n\n.search-input-wrap {\n position: relative;\n z-index: 1;\n height: $sp-8;\n overflow: hidden;\n border-radius: $border-radius;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n transition: height linear #{$transition-duration * 0.5};\n\n @include mq(md) {\n position: absolute;\n width: 100%;\n max-width: $search-results-width;\n height: 100% !important;\n border-radius: 0;\n box-shadow: none;\n transition: width ease $transition-duration;\n }\n}\n\n.search-input {\n position: absolute;\n width: 100%;\n height: 100%;\n padding: $sp-2 $gutter-spacing-sm $sp-2 #{$gutter-spacing-sm + $sp-5};\n font-size: 1rem;\n color: $body-text-color;\n background-color: $search-background-color;\n border-top: 0;\n border-right: 0;\n border-bottom: 0;\n border-left: 0;\n border-radius: 0;\n\n @include mq(md) {\n padding: $sp-2 $gutter-spacing-sm $sp-2 #{$gutter-spacing + $sp-5};\n font-size: 0.875rem;\n background-color: $body-background-color;\n transition: padding-left linear #{$transition-duration * 0.5};\n }\n\n &:focus {\n outline: 2px solid $link-color;\n outline-offset: -2px;\n\n + .search-label .search-icon {\n color: $link-color;\n }\n }\n}\n\n.search-label {\n position: absolute;\n display: flex;\n height: 100%;\n padding-left: $gutter-spacing-sm;\n\n @include mq(md) {\n padding-left: $gutter-spacing;\n transition: padding-left linear #{$transition-duration * 0.5};\n }\n\n .search-icon {\n width: #{$sp-4 * 1.2};\n height: #{$sp-4 * 1.2};\n align-self: center;\n color: $grey-dk-000;\n }\n}\n\n.search-results {\n position: absolute;\n left: 0;\n display: none;\n width: 100%;\n max-height: calc(100% - #{$sp-10});\n overflow-y: auto;\n background-color: $search-background-color;\n border-bottom-right-radius: $border-radius;\n border-bottom-left-radius: $border-radius;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n\n @include mq(md) {\n top: 100%;\n width: $search-results-width;\n max-height: calc(100vh - 200%) !important;\n }\n}\n\n.search-results-list {\n padding-left: 0;\n margin-bottom: $sp-1;\n list-style: none;\n @include fs-4;\n\n @include mq(md) {\n @include fs-3;\n }\n}\n\n.search-results-list-item {\n padding: 0;\n margin: 0;\n}\n\n.search-result {\n display: block;\n padding: $sp-1 $sp-3;\n\n &:hover,\n &.active {\n background-color: $feedback-color;\n }\n}\n\n.search-result-title {\n display: block;\n padding-top: $sp-2;\n padding-bottom: $sp-2;\n\n @include mq(sm) {\n display: inline-block;\n width: 40%;\n padding-right: $sp-2;\n vertical-align: top;\n }\n}\n\n.search-result-doc {\n display: flex;\n align-items: center;\n word-wrap: break-word;\n\n &.search-result-doc-parent {\n opacity: 0.5;\n @include fs-3;\n\n @include mq(md) {\n @include fs-2;\n }\n }\n\n .search-result-icon {\n width: $sp-4;\n height: $sp-4;\n margin-right: $sp-2;\n color: $link-color;\n flex-shrink: 0;\n }\n\n .search-result-doc-title {\n overflow: auto;\n }\n}\n\n.search-result-section {\n margin-left: #{$sp-4 + $sp-2};\n word-wrap: break-word;\n}\n\n.search-result-rel-url {\n display: block;\n margin-left: #{$sp-4 + $sp-2};\n overflow: hidden;\n color: $search-result-preview-color;\n text-overflow: ellipsis;\n white-space: nowrap;\n @include fs-1;\n}\n\n.search-result-previews {\n display: block;\n padding-top: $sp-2;\n padding-bottom: $sp-2;\n padding-left: $sp-4;\n margin-left: $sp-2;\n color: $search-result-preview-color;\n word-wrap: break-word;\n border-left: $border;\n border-left-color: $border-color;\n @include fs-2;\n\n @include mq(sm) {\n display: inline-block;\n width: 60%;\n padding-left: $sp-2;\n margin-left: 0;\n vertical-align: top;\n }\n}\n\n.search-result-preview + .search-result-preview {\n margin-top: $sp-1;\n}\n\n.search-result-highlight {\n font-weight: bold;\n}\n\n.search-no-result {\n padding: $sp-2 $sp-3;\n @include fs-3;\n}\n\n.search-button {\n position: fixed;\n right: $sp-4;\n bottom: $sp-4;\n display: flex;\n width: $sp-9;\n height: $sp-9;\n background-color: $search-background-color;\n border: 1px solid rgba($link-color, 0.3);\n border-radius: #{$sp-9 * 0.5};\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n align-items: center;\n justify-content: center;\n}\n\n.search-overlay {\n position: fixed;\n top: 0;\n left: 0;\n z-index: 1;\n width: 0;\n height: 0;\n background-color: rgba(0, 0, 0, 0.3);\n opacity: 0;\n transition:\n opacity ease $transition-duration,\n width 0s $transition-duration,\n height 0s $transition-duration;\n}\n\n.search-active {\n .search {\n position: fixed;\n top: 0;\n left: 0;\n width: 100%;\n height: 100%;\n padding: 0;\n }\n\n .search-input-wrap {\n height: $sp-10;\n border-radius: 0;\n\n @include mq(md) {\n width: $search-results-width;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n }\n }\n\n .search-input {\n background-color: $search-background-color;\n\n @include mq(md) {\n padding-left: 2.3rem;\n }\n }\n\n .search-label {\n @include mq(md) {\n padding-left: 0.6rem;\n }\n }\n\n .search-results {\n display: block;\n }\n\n .search-overlay {\n width: 100%;\n height: 100%;\n opacity: 1;\n transition:\n opacity ease $transition-duration,\n width 0s,\n height 0s;\n }\n\n @include mq(md) {\n .main {\n position: fixed;\n right: 0;\n left: 0;\n }\n }\n\n .main-header {\n padding-top: $sp-10;\n\n @include mq(md) {\n padding-top: 0;\n }\n }\n}\n","// Tables\n// stylelint-disable max-nesting-depth, selector-no-type, selector-max-type\n\n.table-wrapper {\n display: block;\n width: 100%;\n max-width: 100%;\n margin-bottom: $sp-5;\n overflow-x: auto;\n border-radius: $border-radius;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n}\n\ntable {\n display: table;\n min-width: 100%;\n border-collapse: separate;\n}\n\nth,\ntd {\n min-width: 7.5rem;\n padding: $sp-2 $sp-3;\n background-color: $table-background-color;\n border-bottom: $border rgba($border-color, 0.5);\n border-left: $border $border-color;\n\n @include fs-3;\n\n &:first-of-type {\n border-left: 0;\n }\n}\n\ntbody {\n tr {\n &:last-of-type {\n th,\n td {\n border-bottom: 0;\n }\n\n td {\n padding-bottom: $sp-3;\n }\n }\n }\n}\n\nthead {\n th {\n border-bottom: $border $border-color;\n }\n}\n","// Code and syntax highlighting\n// stylelint-disable selector-no-qualifying-type, declaration-block-semicolon-newline-after,declaration-block-single-line-max-declarations, selector-no-type, selector-max-type, scss/comment-no-empty\n\n// {% raw %}\n\n// This instruction applies to all queues not within 'pre' or 'figure', avoiding 'code' generated by the highlight.\n:not(pre, figure) {\n & > code {\n padding: 0.2em 0.15em;\n font-weight: 400;\n background-color: $code-background-color;\n border: $border $border-color;\n border-radius: $border-radius;\n }\n}\n\n// Avoid appearance of dark border around visited code links in Safari\na:visited code {\n border-color: $border-color;\n}\n\n// Content structure for highlighted code blocks using fences or Liquid\n//\n// ```[LANG]...```, no kramdown line_numbers:\n// div.[language-LANG.]highlighter-rouge > div.highlight > pre.highlight > code\n//\n// ```[LANG]...```, kramdown line_numbers = true:\n// div.[language-LANG.]highlighter-rouge > div.highlight > pre.highlight > code\n// > div.table-wrapper > table.rouge-table > tbody > tr\n// > td.rouge-gutter.gl > pre.lineno\n// | td.rouge-code > pre\n//\n// {% highlight LANG %}...{% endhighlight %}:\n// figure.highlight > pre > code.language-LANG\n//\n// {% highlight LANG linenos %}...{% endhighlight %}:\n// figure.highlight > pre > code.language-LANG\n// > div.table-wrapper > table.rouge-table > tbody > tr\n// > td.gutter.gl > pre.lineno\n// | td.code > pre\n//\n// ----...---- (AsciiDoc)\n// div.listingblock > div.content > pre.rouge.highlight\n//\n// fix_linenos removes the outermost pre when it encloses table.rouge-table\n//\n// See docs/index-test.md for some tests.\n//\n// No kramdown line_numbers: fences and Liquid highlighting look the same.\n// Kramdown line_numbers = true: fences have a wider gutter than with Liquid?\n\n// ```[LANG]...```\n// or in AsciiDoc:\n//\n// ----\n// ...\n// ----\n\n// the code may appear with 3 different types:\n// container \\ case: default case, code with line number, code with html rendering\n// top level: div.highlighter-rouge, figure.highlight, figure.highlight\n// second level: div.highlight, div.table-wrapper, pre.highlight\n// third level: pre.highlight, td.code, absent\n// last level: code, pre, code (optionality)\n// highlighter level: span, span, span\n// the spacing are only in the second level for case 1, 3 and in the third level for case 2\n// in AsciiDoc, there is a parent container that contains optionally a title and the content.\n\n// select top level container\ndiv.highlighter-rouge,\ndiv.listingblock > div.content,\nfigure.highlight {\n margin-top: 0;\n margin-bottom: $sp-3;\n background-color: $code-background-color;\n border-radius: $border-radius;\n box-shadow: none;\n -webkit-overflow-scrolling: touch;\n position: relative;\n padding: 0;\n\n // copy button (or other button)\n // the button appear only when there is a hover on the code or focus on button\n > button {\n width: $sp-3;\n opacity: 0;\n position: absolute;\n top: 0;\n right: 0;\n padding: $sp-3;\n border: none;\n background: none;\n color: $body-text-color;\n box-sizing: content-box;\n\n svg {\n fill: $body-text-color;\n }\n\n &:active {\n text-decoration: none;\n outline: none;\n opacity: 1;\n }\n\n &:focus {\n opacity: 1;\n outline: 2px solid $link-color;\n }\n }\n\n // the button can be seen by doing a simple hover in the code, there is no need to go over the location of the button\n &:hover {\n > button {\n cursor: copy;\n opacity: 1;\n }\n }\n}\n\n// setting the spacing and scrollbar on the second level for the first case\n// remove all space on the second and third level\n// this is a mixin to accommodate for the slightly different structures generated via Markdown vs AsciiDoc\n@mixin scroll-and-spacing($code-div, $pre-select) {\n #{$code-div} {\n overflow-x: auto;\n padding: $sp-3;\n margin: 0;\n border: 1px solid $body-text-color;\n border-radius: $border-radius;\n }\n\n #{$pre-select},\n code {\n padding: 0;\n margin: 0;\n border: 0;\n }\n}\n\n// for Markdown\ndiv.highlighter-rouge {\n @include scroll-and-spacing(\"div.highlight\", \"pre.highlight\");\n}\n\n// for AsciiDoc. we also need to fix the margins for its parent container.\ndiv.listingblock {\n margin-top: 0;\n margin-bottom: $sp-3;\n\n @include scroll-and-spacing(\"div.content\", \"div.content > pre\");\n}\n\n// {% highlight LANG %}...{% endhighlight %},\n// {% highlight LANG linenos %}...{% endhighlight %}:\n\n// setting the spacing and scrollbar on the second level for the thirt case\n// the css rule are apply only to the last code enviroment\n// setting the scroolbar\nfigure.highlight {\n pre,\n :not(pre) > code {\n overflow-x: auto;\n padding: $sp-3;\n margin: 0;\n border: 1px solid $body-text-color;\n border-radius: $border-radius;\n }\n}\n\n// ```[LANG]...```, kramdown line_numbers = true,\n// {% highlight LANG linenos %}...{% endhighlight %}:\n\n// setting the spacing and scrollbar on the thirt level for the second case\n.highlight .table-wrapper {\n padding: $sp-3 0;\n margin: 0;\n border: 0;\n box-shadow: none;\n\n td,\n pre {\n min-width: 0;\n padding: 0;\n background-color: $code-background-color;\n border: 0;\n\n @include fs-2;\n }\n\n td.gl {\n width: 1em;\n padding-right: $sp-3;\n padding-left: $sp-3;\n }\n\n pre {\n margin: 0;\n line-height: 2;\n }\n}\n\n// Code examples: html render of a code\n.code-example,\n.listingblock > .title {\n padding: $sp-3;\n margin-bottom: $sp-3;\n overflow: auto;\n border: 1px solid $border-color;\n border-radius: $border-radius;\n\n + .highlighter-rouge,\n + .sectionbody .listingblock,\n + .content,\n + figure.highlight {\n position: relative;\n margin-top: -$sp-4;\n border-right: 1px solid $border-color;\n border-bottom: 1px solid $border-color;\n border-left: 1px solid $border-color;\n border-top-left-radius: 0;\n border-top-right-radius: 0;\n }\n}\n\n// Mermaid diagram code blocks should be left unstyled.\ncode.language-mermaid {\n padding: 0;\n background-color: inherit;\n border: 0;\n}\n\n// Override OneDarkJekyll Colors for Code Blocks\n.highlight,\npre.highlight {\n background: $code-background-color; // Code Background\n // For Backwards Compatibility Before $code-linenumber-color was added\n @if variable-exists(code-linenumber-color) {\n color: $code-linenumber-color; // Code Line Numbers\n } @else {\n color: $body-text-color; // Code Line Numbers\n }\n}\n\n// Override OneDarkJekyll Colors for Code Blocks\n.highlight pre {\n background: $code-background-color; // Code Background\n}\n\n// {% endraw %}\n","// Utility classes for colors\n\n// Text colors\n\n.text-grey-dk-000 {\n color: $grey-dk-000 !important;\n}\n\n.text-grey-dk-100 {\n color: $grey-dk-100 !important;\n}\n\n.text-grey-dk-200 {\n color: $grey-dk-200 !important;\n}\n\n.text-grey-dk-250 {\n color: $grey-dk-250 !important;\n}\n\n.text-grey-dk-300 {\n color: $grey-dk-300 !important;\n}\n\n.text-grey-lt-000 {\n color: $grey-lt-000 !important;\n}\n\n.text-grey-lt-100 {\n color: $grey-lt-100 !important;\n}\n\n.text-grey-lt-200 {\n color: $grey-lt-200 !important;\n}\n\n.text-grey-lt-300 {\n color: $grey-lt-300 !important;\n}\n\n.text-blue-000 {\n color: $blue-000 !important;\n}\n\n.text-blue-100 {\n color: $blue-100 !important;\n}\n\n.text-blue-200 {\n color: $blue-200 !important;\n}\n\n.text-blue-300 {\n color: $blue-300 !important;\n}\n\n.text-green-000 {\n color: $green-000 !important;\n}\n\n.text-green-100 {\n color: $green-100 !important;\n}\n\n.text-green-200 {\n color: $green-200 !important;\n}\n\n.text-green-300 {\n color: $green-300 !important;\n}\n\n.text-purple-000 {\n color: $purple-000 !important;\n}\n\n.text-purple-100 {\n color: $purple-100 !important;\n}\n\n.text-purple-200 {\n color: $purple-200 !important;\n}\n\n.text-purple-300 {\n color: $purple-300 !important;\n}\n\n.text-yellow-000 {\n color: $yellow-000 !important;\n}\n\n.text-yellow-100 {\n color: $yellow-100 !important;\n}\n\n.text-yellow-200 {\n color: $yellow-200 !important;\n}\n\n.text-yellow-300 {\n color: $yellow-300 !important;\n}\n\n.text-red-000 {\n color: $red-000 !important;\n}\n\n.text-red-100 {\n color: $red-100 !important;\n}\n\n.text-red-200 {\n color: $red-200 !important;\n}\n\n.text-red-300 {\n color: $red-300 !important;\n}\n\n// Background colors\n\n.bg-grey-dk-000 {\n background-color: $grey-dk-000 !important;\n}\n\n.bg-grey-dk-100 {\n background-color: $grey-dk-100 !important;\n}\n\n.bg-grey-dk-200 {\n background-color: $grey-dk-200 !important;\n}\n\n.bg-grey-dk-250 {\n background-color: $grey-dk-250 !important;\n}\n\n.bg-grey-dk-300 {\n background-color: $grey-dk-300 !important;\n}\n\n.bg-grey-lt-000 {\n background-color: $grey-lt-000 !important;\n}\n\n.bg-grey-lt-100 {\n background-color: $grey-lt-100 !important;\n}\n\n.bg-grey-lt-200 {\n background-color: $grey-lt-200 !important;\n}\n\n.bg-grey-lt-300 {\n background-color: $grey-lt-300 !important;\n}\n\n.bg-blue-000 {\n background-color: $blue-000 !important;\n}\n\n.bg-blue-100 {\n background-color: $blue-100 !important;\n}\n\n.bg-blue-200 {\n background-color: $blue-200 !important;\n}\n\n.bg-blue-300 {\n background-color: $blue-300 !important;\n}\n\n.bg-green-000 {\n background-color: $green-000 !important;\n}\n\n.bg-green-100 {\n background-color: $green-100 !important;\n}\n\n.bg-green-200 {\n background-color: $green-200 !important;\n}\n\n.bg-green-300 {\n background-color: $green-300 !important;\n}\n\n.bg-purple-000 {\n background-color: $purple-000 !important;\n}\n\n.bg-purple-100 {\n background-color: $purple-100 !important;\n}\n\n.bg-purple-200 {\n background-color: $purple-200 !important;\n}\n\n.bg-purple-300 {\n background-color: $purple-300 !important;\n}\n\n.bg-yellow-000 {\n background-color: $yellow-000 !important;\n}\n\n.bg-yellow-100 {\n background-color: $yellow-100 !important;\n}\n\n.bg-yellow-200 {\n background-color: $yellow-200 !important;\n}\n\n.bg-yellow-300 {\n background-color: $yellow-300 !important;\n}\n\n.bg-red-000 {\n background-color: $red-000 !important;\n}\n\n.bg-red-100 {\n background-color: $red-100 !important;\n}\n\n.bg-red-200 {\n background-color: $red-200 !important;\n}\n\n.bg-red-300 {\n background-color: $red-300 !important;\n}\n","// Utility classes for layout\n\n// Display\n\n.d-block {\n display: block !important;\n}\n\n.d-flex {\n display: flex !important;\n}\n\n.d-inline {\n display: inline !important;\n}\n\n.d-inline-block {\n display: inline-block !important;\n}\n\n.d-none {\n display: none !important;\n}\n\n// Screenreader-only\n\n.sr-only {\n position: absolute;\n width: 1px;\n height: 1px;\n padding: 0;\n margin: -1px;\n overflow: hidden;\n clip: rect(0, 0, 0, 0);\n white-space: nowrap;\n border-width: 0;\n}\n\n@each $media-query in map-keys($media-queries) {\n @for $i from 1 through length($spacers) {\n @include mq($media-query) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .d-sm-block, .d-md-none, .d-lg-inline\n .d-#{$media-query}-block {\n display: block !important;\n }\n .d-#{$media-query}-flex {\n display: flex !important;\n }\n .d-#{$media-query}-inline {\n display: inline !important;\n }\n .d-#{$media-query}-inline-block {\n display: inline-block !important;\n }\n .d-#{$media-query}-none {\n display: none !important;\n }\n }\n }\n}\n\n// Horizontal alignment\n\n.float-left {\n float: left !important;\n}\n\n.float-right {\n float: right !important;\n}\n\n.flex-justify-start {\n justify-content: flex-start !important;\n}\n\n.flex-justify-end {\n justify-content: flex-end !important;\n}\n\n.flex-justify-between {\n justify-content: space-between !important;\n}\n\n.flex-justify-around {\n justify-content: space-around !important;\n}\n\n// Vertical alignment\n\n.v-align-baseline {\n vertical-align: baseline !important;\n}\n\n.v-align-bottom {\n vertical-align: bottom !important;\n}\n\n.v-align-middle {\n vertical-align: middle !important;\n}\n\n.v-align-text-bottom {\n vertical-align: text-bottom !important;\n}\n\n.v-align-text-top {\n vertical-align: text-top !important;\n}\n\n.v-align-top {\n vertical-align: top !important;\n}\n","// Utility classes for typography\n\n.fs-1 {\n @include fs-1;\n}\n\n.fs-2 {\n @include fs-2;\n}\n\n.fs-3 {\n @include fs-3;\n}\n\n.fs-4 {\n @include fs-4;\n}\n\n.fs-5 {\n @include fs-5;\n}\n\n.fs-6 {\n @include fs-6;\n}\n\n.fs-7 {\n @include fs-7;\n}\n\n.fs-8 {\n @include fs-8;\n}\n\n.fs-9 {\n @include fs-9;\n}\n\n.fs-10 {\n @include fs-10;\n}\n\n.fw-300 {\n font-weight: 300 !important;\n}\n\n.fw-400 {\n font-weight: 400 !important;\n}\n\n.fw-500 {\n font-weight: 500 !important;\n}\n\n.fw-700 {\n font-weight: 700 !important;\n}\n\n.lh-0 {\n line-height: 0 !important;\n}\n\n.lh-default {\n line-height: $body-line-height;\n}\n\n.lh-tight {\n line-height: $body-heading-line-height;\n}\n\n.ls-5 {\n letter-spacing: 0.05em !important;\n}\n\n.ls-10 {\n letter-spacing: 0.1em !important;\n}\n\n.ls-0 {\n letter-spacing: 0 !important;\n}\n\n.text-uppercase {\n text-transform: uppercase !important;\n}\n","// Utility classes for lists\n\n// stylelint-disable selector-max-type\n\n.list-style-none {\n padding: 0 !important;\n margin: 0 !important;\n list-style: none !important;\n\n li {\n &::before {\n display: none !important;\n }\n }\n}\n","// Utility classes for margins and padding\n\n// stylelint-disable block-opening-brace-space-after, block-opening-brace-space-before\n\n// Margin spacer utilities\n\n.mx-auto {\n margin-right: auto !important;\n margin-left: auto !important;\n}\n\n@for $i from 1 through length($spacers) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .m-0, .m-1, .m-2...\n .m-#{$scale} {\n margin: #{$size} !important;\n }\n .mt-#{$scale} {\n margin-top: #{$size} !important;\n }\n .mr-#{$scale} {\n margin-right: #{$size} !important;\n }\n .mb-#{$scale} {\n margin-bottom: #{$size} !important;\n }\n .ml-#{$scale} {\n margin-left: #{$size} !important;\n }\n\n .mx-#{$scale} {\n margin-right: #{$size} !important;\n margin-left: #{$size} !important;\n }\n\n .my-#{$scale} {\n margin-top: #{$size} !important;\n margin-bottom: #{$size} !important;\n }\n\n .mxn-#{$scale} {\n margin-right: -#{$size} !important;\n margin-left: -#{$size} !important;\n }\n .mx-#{$scale}-auto {\n margin-right: auto !important;\n margin-left: auto !important;\n }\n}\n\n@each $media-query in map-keys($media-queries) {\n @for $i from 1 through length($spacers) {\n @include mq($media-query) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .m-sm-0, .m-md-1, .m-lg-2...\n .m-#{$media-query}-#{$scale} {\n margin: #{$size} !important;\n }\n .mt-#{$media-query}-#{$scale} {\n margin-top: #{$size} !important;\n }\n .mr-#{$media-query}-#{$scale} {\n margin-right: #{$size} !important;\n }\n .mb-#{$media-query}-#{$scale} {\n margin-bottom: #{$size} !important;\n }\n .ml-#{$media-query}-#{$scale} {\n margin-left: #{$size} !important;\n }\n\n .mx-#{$media-query}-#{$scale} {\n margin-right: #{$size} !important;\n margin-left: #{$size} !important;\n }\n\n .my-#{$media-query}-#{$scale} {\n margin-top: #{$size} !important;\n margin-bottom: #{$size} !important;\n }\n\n .mxn-#{$media-query}-#{$scale} {\n margin-right: -#{$size} !important;\n margin-left: -#{$size} !important;\n }\n }\n }\n}\n\n// Padding spacer utilities\n\n@for $i from 1 through length($spacers) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .p-0, .p-1, .p-2...\n .p-#{$scale} {\n padding: #{$size} !important;\n }\n .pt-#{$scale} {\n padding-top: #{$size} !important;\n }\n .pr-#{$scale} {\n padding-right: #{$size} !important;\n }\n .pb-#{$scale} {\n padding-bottom: #{$size} !important;\n }\n .pl-#{$scale} {\n padding-left: #{$size} !important;\n }\n\n .px-#{$scale} {\n padding-right: #{$size} !important;\n padding-left: #{$size} !important;\n }\n\n .py-#{$scale} {\n padding-top: #{$size} !important;\n padding-bottom: #{$size} !important;\n }\n}\n\n@each $media-query in map-keys($media-queries) {\n @include mq($media-query) {\n @for $i from 1 through length($spacers) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .p-sm-0, .p-md-1, .p-lg-2...\n .p-#{$media-query}-#{$scale} {\n padding: #{$size} !important;\n }\n .pt-#{$media-query}-#{$scale} {\n padding-top: #{$size} !important;\n }\n .pr-#{$media-query}-#{$scale} {\n padding-right: #{$size} !important;\n }\n .pb-#{$media-query}-#{$scale} {\n padding-bottom: #{$size} !important;\n }\n .pl-#{$media-query}-#{$scale} {\n padding-left: #{$size} !important;\n }\n\n .px-#{$media-query}-#{$scale} {\n padding-right: #{$size} !important;\n padding-left: #{$size} !important;\n }\n\n .py-#{$media-query}-#{$scale} {\n padding-top: #{$size} !important;\n padding-bottom: #{$size} !important;\n }\n }\n }\n}\n","// stylelint-disable selector-max-specificity, selector-max-id, selector-max-type, selector-no-qualifying-type\n\n@media print {\n .site-footer,\n .site-button,\n #edit-this-page,\n #back-to-top,\n .site-nav,\n .main-header {\n display: none !important;\n }\n\n hr {\n margin-top: 1rem;\n margin-bottom: 1rem;\n }\n\n .side-bar {\n width: 100%;\n height: auto;\n border-right: 0 !important;\n }\n\n .site-header {\n border-bottom: 1px solid $border-color;\n }\n\n .site-title {\n font-size: 1rem !important;\n font-weight: 700 !important;\n }\n\n .text-small {\n font-size: 8pt !important;\n }\n\n pre.highlight {\n border: 1px solid $border-color;\n }\n\n .main {\n max-width: none;\n margin-left: 0;\n }\n}\n","// Skipnav\n// Skip to main content\n\na.skip-to-main {\n left: -999px;\n position: absolute;\n top: auto;\n width: 1px;\n height: 1px;\n overflow: hidden;\n z-index: -999;\n}\n\na.skip-to-main:focus,\na.skip-to-main:active {\n color: $link-color;\n background-color: $body-background-color;\n left: auto;\n top: auto;\n width: 30%;\n height: auto;\n overflow: auto;\n margin: 10px 35%;\n padding: 5px;\n border-radius: 15px;\n border: 4px solid $btn-primary-color;\n text-align: center;\n font-size: 1.2em;\n z-index: 999;\n}\n","\n@import \"./support/support\";\n@import \"./custom/setup\";\n@import \"./color_schemes/light\";\n\n@import \"./color_schemes/meshtastic-dark\";\n\n@import \"./modules\";\ndiv.opaque {\n background-color: $body-background-color;\n}\n\np.tip, blockquote.tip {\n border: 1px $green-000 solid;\n border-left: $border-radius solid $green-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n \n &::before {\n color: $green-300;\n content: \"Tip\";\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n \n > .tip-title {\n color: $green-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\np.tip-title, blockquote.tip-title {\n border: 1px $green-000 solid;\n border-left: $border-radius solid $green-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n > p:first-child {\n margin-top: 0;\n margin-bottom: 0;\n color: $green-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\nblockquote.tip {\n margin-left: 0;\n margin-right: 0;\n\n > p:first-child {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\nblockquote.tip-title {\n margin-left: 0;\n margin-right: 0;\n\n > p:nth-child(2) {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\n\n\np.note, blockquote.note {\n border: 1px $blue-000 solid;\n border-left: $border-radius solid $blue-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n \n &::before {\n color: $blue-300;\n content: \"Note\";\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n \n > .note-title {\n color: $blue-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\np.note-title, blockquote.note-title {\n border: 1px $blue-000 solid;\n border-left: $border-radius solid $blue-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n > p:first-child {\n margin-top: 0;\n margin-bottom: 0;\n color: $blue-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\nblockquote.note {\n margin-left: 0;\n margin-right: 0;\n\n > p:first-child {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\nblockquote.note-title {\n margin-left: 0;\n margin-right: 0;\n\n > p:nth-child(2) {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\n\n\np.warning, blockquote.warning {\n border: 1px $yellow-000 solid;\n border-left: $border-radius solid $yellow-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n \n &::before {\n color: $yellow-300;\n content: \"Warning\";\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n \n > .warning-title {\n color: $yellow-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\np.warning-title, blockquote.warning-title {\n border: 1px $yellow-000 solid;\n border-left: $border-radius solid $yellow-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n > p:first-child {\n margin-top: 0;\n margin-bottom: 0;\n color: $yellow-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\nblockquote.warning {\n margin-left: 0;\n margin-right: 0;\n\n > p:first-child {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\nblockquote.warning-title {\n margin-left: 0;\n margin-right: 0;\n\n > p:nth-child(2) {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\n\n@import \"./custom/custom\";\n\n\n"],"file":"just-the-docs-meshtastic-dark.css"} \ No newline at end of file diff --git a/main/assets/css/just-the-docs-meshtastic.css.map b/main/assets/css/just-the-docs-meshtastic.css.map index fb2b4ca0e7..069a5a2fdf 100644 --- a/main/assets/css/just-the-docs-meshtastic.css.map +++ b/main/assets/css/just-the-docs-meshtastic.css.map @@ -1 +1 @@ -{"version":3,"sourceRoot":"","sources":["../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/vendor/accessible-pygments/github-light.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/vendor/normalize.scss/normalize.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/base.scss","../../_sass/color_schemes/meshtastic.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/support/mixins/_typography.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/support/mixins/_layout.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/support/_variables.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/layout.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/content.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/navigation.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/typography.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/labels.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/buttons.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/color_schemes/light.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/support/mixins/_buttons.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/search.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/tables.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/code.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/utilities/_colors.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/utilities/_layout.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/utilities/_typography.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/utilities/_lists.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/utilities/_spacing.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/print.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3176-vkvacr/_sass/skiptomain.scss","just-the-docs-meshtastic.scss"],"names":[],"mappings":";AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAUA;EAAkB;;;AAClB;EAAgB;EAAiB;AACjC;EAAkB;EAAiB;AACnC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAkB;EAAiB;AACnC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAqB;AACtC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAoB;AACrC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAgB;EAAiB;AACjC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AChFlC;AAEA;AAAA;AAGA;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAAA;AAKA;EACE;EACA;EACA;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;EACA;;;AAGF;AAAA;AAAA;AAIA;AAAA;EAEE;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;AAAA;EAGE;EACA;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;EAEE;EACA;EACA;EACA;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAAA;AAKA;AAAA;AAAA;AAAA;AAAA;EAKE;EACA;EACA;EACA;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;AAEE;EACA;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;AAEE;EACA;;;AAGF;AAAA;AAAA;AAIA;AAAA;AAAA;AAAA;EAIE;;;AAGF;AAAA;AAAA;AAIA;AAAA;AAAA;AAAA;EAIE;EACA;;;AAGF;AAAA;AAAA;AAIA;AAAA;AAAA;AAAA;EAIE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAOA;EACE;EACA;EACA;EACA;EACA;EACA;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;EAEE;EACA;;;AAGF;AAAA;AAAA;AAIA;AAAA;EAEE;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AC1VF;EACE,cCGa;;;ADAf;EACE;;;AAGF;EACE;;AEmBA;EACE;;AClBA;EHHJ;IEyBI;;;;AFnBJ;EACE,aIfiB;EJgBjB;EACA,aIbiB;EJcjB,OCTgB;EDUhB,kBCZsB;EDatB;;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAYE;;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAOE;EACA;EACA;EACA,aI1CyB;EJ2CzB,OCvCmB;;;AD0CrB;EACE;EACA;;;AAGF;EACE,OC7CW;ED8CX;;;AAGF;EACE;EACA,uBCvCa;EDwCb;;AAEA;EACE;;;AAIJ;EACE,aIvEiB;EJwEjB;EACA,aIvEiB;;;AJ0EnB;AAAA;EAEE;;;AAGF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;EACA;EACA,kBCvEa;EDwEb;;;AAIF;EACE;EAGA;EACA;EACA;EACA;;;AK7GF;EACE;EACA;EACA;EACA,kBJKc;;AEGZ;EEZJ;IAOI;IACA;IACA,ODwFW;ICvFX;IACA;IACA;;;AFAA;EEZJ;IAgBI;IACA,WD+EQ;;;ADpFR;EEQF;IAEI,aD2ES;;;ADrFX;EEQF;IAQI;;;AAOF;EACE;EACA,kBJ5BU;;AEGZ;EEuBA;IAKI;IACA,kBJjCgB;;;AIoClB;EACE;;AFjCJ;EEgCE;IAII;;;;AAOV;EACE;;AF5CE;EE2CJ;IAII;IACA,WDyCY;;;;ACrChB;EACE,aDaK;ECZL,gBDYK;EDvDL,eCuDK;EDtDL,cCsDK;;ADlEH;EEoDJ;IFrCI,eCqDG;IDpDH,cCoDG;;;ADpEH;EEoDJ;IAOI,aDSG;ICRH,gBDQG;;;;ACJP;EACE;EACA;;AFlEE;EEgEJ;IAKI;IACA;IACA,QDmBY;;;;ACfhB;AAAA;AAAA;EAGE;;AF9EE;EE2EJ;AAAA;AAAA;IAMI,ODGQ;;;;ACCZ;EACE;;AAEA;EACE;;AFzFA;EEqFJ;IAQI;IACA,aDxBG;ICyBH,gBD7BG;IC8BH;IACA;;;;AAIJ;EACE;EACA,YDbc;ECcd;;AFxGE;EEqGJ;IAMI,QDjBY;ICkBZ,YDlBY;ICmBZ;;;;AAIJ;EACE;EACA;EACA;EACA;EACA,aDrDK;ECsDL,gBDtDK;ECuDL,OJzHmB;EEYnB,eCuDK;EDtDL,cCsDK;;ADlEH;EEiHJ;IFlGI,eCqDG;IDpDH,cCoDG;;;AF/BL;EACE;;ACtCA;EEiHJ;IHvEI;IACA,aEhDuB;;;ADKvB;EEiHJ;IAcI,aD/DG;ICgEH,gBDhEG;;;;AC+EP;EACE;EACA;EACA,SDhFK;ECiFL;;;AFnJE;EEuJF;IACE;;;AAIJ;EACE;;;AAQF;EACE;;;AAOF;EACE;EACA;EACA;EACA,aD/GK;ECgHL,gBDhHK;EDvDL,eCuDK;EDtDL,cCsDK;;ADlEH;EE6KJ;IF9JI,eCqDG;IDpDH,cCoDG;;;AFvEL;EACE;;ACEA;EE6KJ;IH3KI;;;ACFA;EE6KJ;IAYI;IACA;;;;AAIJ;EACE,OD5HK;EC6HL,QD7HK;EC8HL,OJ/LW;;;AKXb;EACE,aFEoB;;AEApB;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAOE;;AAGF;EACE;EACA;;AAGF;AAAA;EAEE;;AAIA;EACE,YF+CC;;AE3CL;EACE;EACA;;AAEA;EACE;;AAEA;EACE;EACA;EACA;EACA,OFfM;EEgBN;EACA;;AJ1BN;EACE;;ACRA;EG2BE;IJfF;;;ACZA;EG2BE;IAUI;;;AAIJ;EACE;;AAGE;EACE;EACA;;AAOV;EACE;;AAGE;EACE;EACA;EACA,OF7CM;EE8CN;;AAMJ;EACE;;AAIJ;EACE;EACA;;AAKF;EACE;;AAGF;EACE;;AAGF;EACE;EACA;;AAGF;AAAA;EAEE;;AAGF;EACE;EACA;EACA;;AAEA;EACE;;AAIJ;EACE;EACA;EACA;;AAmBE;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EACE;;AASF;AAAA;AAAA;AAAA;AAAA;AAAA;EAEE;;AAKN;EACE;EACA;EACA,OFnFG;EEoFH;EACA,eFzFG;EE0FH,cF1FG;EE2FH;;AH1JA;EGmJF;IAUI;IACA;;;AAGF;EACE;EACA;EACA;EACA,OLnKO;EKoKP;;AAYF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EACE;;AAIJ;EACE;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAOE;EACA;EACA;;AAEA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAKE;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EACE;;AAIJ;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAWE,YF9JG;;;AG3EP;EACE;EACA;EACA;EACA;;AAEA;EACE;EACA;;ALoBF;EACE;;AClBA;EILF;IL2BE;;;ACtBA;EDOF;IACE;;;ACRA;EILF;ILiBE;;;AKPA;EACE;EACA,YH+DC;EG9DD,aHuDC;EGtDD,gBHsDC;EGrDD;EAEE,eH0DD;EGzDC,cHqDD;;ADlEH;EIKA;IAeI,YHgDD;IG/CC;IAEE,eH6CH;IG5CG,cH4CH;;;AGrCD;EACE,OHkCD;EGjCC,QHiCD;EGhCC;;AAGF;EACE;EACA;;AAGF;EAEE;EACA;;AASJ;EACE;EAEE;EAGF,OHUC;EGTD,QHSC;EGRD;EACA,ON7DO;;AEFT;EIsDA;IAYI,OHED;IGDC,QHCD;IGAC;;;AAGF;EACE;;AAQA;EACE;;AAKN;EACE;EACA,cHvBC;EGwBD;;AAEA;EACE;;AAEA;EACE,ONzFa;;AM4Ff;EACE,ON7Fa;;AMmGjB;EAEI;;AAMJ;EACE;;;AAMR;EACE;EACA;EACA;EACA;EACA;;ALhIA;EACE;;ACEA;EIwHJ;ILtHI;;;ACFA;EIwHJ;IASI;IACA,YHhEG;IGiEH;;EAEA;IACE;;;;AAMJ;EACE;;AAEA;EACE;;AAGE;EACE,ONlJG;;AMqJL;EACE,ONtJG;;;AM+Jb;EACE;EACA;;ALtKA;EACE;;ACEA;EIiKJ;IL/JI;;;AKoKF;EACE;EACA;EACA;EACA;EACA;;AAGF;EACE;EACA;EACA;EACA;;AJlLA;EIiKJ;IAqBI,eHpHG;;;;ADlEH;EI4LJ;IAEI;;;;AAIJ;EACE;EACA,eHnIK;EGoIL;;;AAGF;EACE;;AL5MA;EACE;;ACEA;EIwMJ;ILtMI;;;AK0MF;EACE;;AAGF;EACE;EACA,cHlJG;EGmJH,aHnJG;EGoJH,OHpMU;EGqMV;;AAIA;EACE;;;ACrON;AAAA;EAEE;;ANoEA;AAAA;EACE;EACA,aElEuB;;ADKvB;EKXJ;AAAA;IN4EI;;;;AA5BF;AAAA;AAAA;EACE;;ACtCA;EKJJ;AAAA;AAAA;IN8CI;IACA,aEhDuB;;;;AFgCzB;AAAA;EACE;;AC5BA;EKEJ;AAAA;IN8BI;;;;AMzBJ;AAAA;EAEE;EACA;EACA;;ANdA;AAAA;EACE;;ACEA;EKOJ;AAAA;INLI;;;;AMcJ;EACE;;;ANVA;AAAA;EACE;;ACRA;EKoBJ;AAAA;INRI;;;;AAfF;AAAA;EACE;;ACEA;EKyBJ;AAAA;INvBI;;;;AALF;EACE;;ACEA;EK8BJ;IN5BI;;;;AMgCJ;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;ACvDF;AAAA;EAEE;EACA;EACA,cLoEK;EKnEL,aLmEK;EKlEL,OLiBM;EKhBN;EACA;EACA,kBL6BS;EK5BT;;APLA;AAAA;EACE;;ACEA;EMRJ;AAAA;IPUI;;;;AOKJ;EACE,kBL4BU;;;AKzBZ;EACE,kBLcW;;;AKXb;EACE,kBL4BQ;;;AKzBV;EACE,OLFY;EKGZ,kBLkBW;;;AMlDb;EACE;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA,OTIW;ESHX;EACA;EACA;EACA,kBCTkB;EDUlB;EACA,eNyEc;EMxEd,YACE;EAEF;;AAEA;EACE;EACA;EACA;;AAGF;EAEE;;AAGF;EAEE;;AAGF;EAIE;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;AAKA;EAEE;EACA;EACA;EACA;EACA;;;AAKN;EACE,OT1DW;ES2DX;EACA;;AAEA;EAIE;EACA;EACA;EACA;;AAGF;EACE;EACA;EACA,YACE;;AAIJ;EAEE;;;AAIJ;EEnGE,OR0BM;EQzBN;EACA;EACA,YACE;;AAGF;EAEE,ORiBI;EQhBJ;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;;AFgFJ;EEvGE,OR0BM;EQzBN;EACA;EACA,YACE;;AAGF;EAEE,ORiBI;EQhBJ;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;;AFoFJ;EE3GE,OR0BM;EQzBN;EACA;EACA,YACE;;AAGF;EAEE,ORiBI;EQhBJ;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;;AFwFJ;EE/GE,OR0BM;EQzBN;EACA;EACA,YACE;;AAGF;EAEE,ORiBI;EQhBJ;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;;AF4FJ;EACE;EACA;EACA;EACA;EACA;EACA;EACA;;;AG3HF;EACE;EACA;EACA;EACA,QTgFM;ES/EN,STuEK;EStEL;;AVME;EUZJ;IASI;IACA;IACA;IACA;IACA;;;;AAIJ;EACE;EACA;EACA,QT8DK;ES7DL;EACA,eTmEc;ESlEd,YACE;EAEF;;AVdE;EUKJ;IAYI;IACA;IACA,WTwEmB;ISvEnB;IACA;IACA;IACA;;;;AAIJ;EACE;EACA;EACA;EACA;EACA;EACA,OZnCgB;EYoChB,kBZVwB;EYWxB;EACA;EACA;EACA;EACA;;AVvCE;EU2BJ;IAeI;IACA;IACA,kBZhDoB;IYiDpB;;;AAGF;EACE;EACA;;AAEA;EACE,OZnDO;;;AYwDb;EACE;EACA;EACA;EACA,cTIK;;ADlEH;EU0DJ;IAOI,cTGG;ISFH;;;AAGF;EACE;EACA;EACA;EACA,OTzDU;;;AS6Dd;EACE;EACA;EACA;EACA;EACA;EACA;EACA,kBZ5DwB;EY6DxB,4BTRc;ESSd,2BTTc;ESUd,YACE;;AVxFA;EU6EJ;IAeI;IACA,OTFmB;ISGnB;;;;AAIJ;EACE;EACA,eTrCK;ESsCL;;AXpFA;EACE;;AClBA;EUkGJ;IX5EI;;;ACtBA;EDOF;IACE;;;ACRA;EUkGJ;IXtFI;;;;AWiGJ;EACE;EACA;;;AAGF;EACE;EACA;;AAEA;EAEE,kBZnGa;;;AYuGjB;EACE;EACA,aT9DK;ES+DL,gBT/DK;;ADhEH;EU4HJ;IAMI;IACA;IACA,eTpEG;ISqEH;;;;AAIJ;EACE;EACA;EACA;;AAEA;EACE;;AXxIF;EACE;;ACRA;EU8IF;IXlIE;;;ACZA;EDHF;IACE;;;ACEA;EU8IF;IX5IE;;;AWqJF;EACE,OTtFG;ESuFH,QTvFG;ESwFH,cT1FG;ES2FH,OZzJS;EY0JT;;AAGF;EACE;;;AAIJ;EACE;EACA;;;AAGF;EACE;EACA;EACA;EACA,OZtK4B;EYuK5B;EACA;;AX5LA;EACE;;ACYA;EUyKJ;IXjLI;;;;AW2LJ;EACE;EACA,aTrHK;ESsHL,gBTtHK;ESuHL,cTrHK;ESsHL,aTxHK;ESyHL,OZlL4B;EYmL5B;EACA,aT/GO;ESgHP,mBZ9Ka;;ACjBb;EACE;;ACEA;EUmLJ;IXjLI;;;ACFA;EUmLJ;IAaI;IACA;IACA,cTlIG;ISmIH;IACA;;;;AAIJ;EACE,YT1IK;;;AS6IP;EACE;;;AAGF;EACE;;AX1MA;EACE;;ACRA;EUgNJ;IXpMI;;;;AWyMJ;EACE;EACA,OTrJK;ESsJL,QTtJK;ESuJL;EACA,OTnJK;ESoJL,QTpJK;ESqJL,kBZpMwB;EYqMxB;EACA;EACA,YACE;EAEF;EACA;;;AAGF;EACE;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA,YACE;;;AAMF;EACE;EACA;EACA;EACA;EACA;EACA;;AAGF;EACE,QTxLI;ESyLJ;;AVjQA;EU+PF;IAKI,OTzKiB;IS0KjB,YACE;;;AAKN;EACE,kBZpPsB;;AExBtB;EU2QF;IAII;;;AV/QF;EUmRF;IAEI;;;AAIJ;EACE;;AAGF;EACE;EACA;EACA;EACA,YACE;;AVlSF;EUwSA;IACE;IACA;IACA;;;AAIJ;EACE,aTxOI;;ADxEJ;EU+SF;IAII;;;;AC9TN;EACE;EACA;EACA;EACA,eV0EK;EUzEL;EACA,eVkFc;EUjFd,YACE;;;AAIJ;EACE;EACA;EACA;;;AAGF;AAAA;EAEE;EACA;EACA,kBbIuB;EaHvB;EACA;;AZNA;AAAA;EACE;;ACRA;EWOJ;AAAA;IZKI;;;AYKF;AAAA;EACE;;;AAOE;AAAA;EAEE;;AAGF;EACE,gBVkCD;;;AU3BL;EACE;;;AC9CF;EACE;EACA;EACA,kBdcoB;EcbpB;EACA,eX+EY;;;AW1EhB;EACE,cdUa;;;AcyCf;AAAA;AAAA;EAGE;EACA,eXMK;EWLL,kBdlDsB;EcmDtB,eXgBc;EWfd;EACA;EACA;EACA;;AAIA;AAAA;AAAA;EACE,OXLG;EWMH;EACA;EACA;EACA;EACA,SXVG;EWWH;EACA;EACA,OdhFc;EciFd;;AAEA;AAAA;AAAA;EACE,MdpFY;;AcuFd;AAAA;AAAA;EACE;EACA;EACA;;AAGF;AAAA;AAAA;EACE;EACA;;AAMF;AAAA;AAAA;EACE;EACA;;;AASJ;EACE;EACA,SX/CG;EWgDH;EACA;EACA,eXtCY;;AWyCd;AAAA;EAEE;EACA;EACA;;;AAUJ;EACE;EACA,eXrEK;;AW6CL;EACE;EACA,SX/CG;EWgDH;EACA;EACA,eXtCY;;AWyCd;AAAA;EAEE;EACA;EACA;;;AAwBF;AAAA;EAEE;EACA,SXpFG;EWqFH;EACA;EACA,eX3EY;;;AWmFhB;EACE;EACA;EACA;EACA;;AAEA;AAAA;EAEE;EACA;EACA,kBdhKoB;EciKpB;;Ab9KF;AAAA;EACE;;ACEA;EYsKF;AAAA;IbpKE;;;Aa8KF;EACE;EACA,eXjHG;EWkHH,cXlHG;;AWqHL;EACE;EACA;;;AAKJ;AAAA;EAEE,SX9HK;EW+HL,eX/HK;EWgIL;EACA;EACA,eXtHc;;AWwHd;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAIE;EACA;EACA;EACA;EACA;EACA;EACA;;;AAKJ;EACE;EACA;EACA;;;AAIF;AAAA;EAEE,YdnNsB;EcsNpB,OdrNoB;;;Ac4NxB;EACE,Yd9NsB;;;AepBxB;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAKF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;ACvOF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAKF;EACE;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;;;AdrBE;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;AAQR;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAKF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AfhHA;EACE;;ACYA;EeZJ;IhBII;;;;AAKF;EACE;;ACEA;EeRJ;IhBUI;;;;AAKF;EACE;;ACRA;EeJJ;IhBgBI;;;;AAKF;EACE;;AClBA;EeAJ;IhBsBI;;;;AAKF;EACE;;AC5BA;EeIJ;IhB4BI;;;;AAKF;EACE;;ACtCA;EeQJ;IhBkCI;IACA,aEhDuB;;;;AFqDzB;EACE;EACA,aEvDuB;;ADKvB;EeYJ;IhB0CI;;;;AAKF;EACE;EACA,aElEuB;;ADKvB;EegBJ;IhBiDI;;;;AAKF;EACE;EACA,aE7EuB;;ADKvB;EeoBJ;IhBwDI;;;;AAKF;EACE;EACA,aExFuB;;ADKvB;EewBJ;IhB+DI;;;;AgB3DJ;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE,adxDiB;;;Ac2DnB;EACE,ad1DyB;;;Ac6D3B;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AC/EF;EACE;EACA;EACA;;AAGE;EACE;;;ACLN;EACE;EACA;;;AAQA;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AjBlCA;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AAaN;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AjB7GA;EiBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjB/IJ;EiBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjB/IJ;EiBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjB/IJ;EiBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjB/IJ;EiBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AC3JR;EACE;AAAA;AAAA;AAAA;AAAA;AAAA;IAME;;EAGF;IACE;IACA;;EAGF;IACE;IACA;IACA;;EAGF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;;EAGF;IACE;;EAGF;IACE;IACA;;;ACvCJ;EACE;EACA;EACA;EACA;EACA;EACA;EACA;;;AAGF;AAAA;EAEE,OrBCW;EqBAX,kBrBNsB;EqBOtB;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;;;ACpBF;EACE,kBtBCsB;;;AsBExB;EACI;EACA;EACA,enB4EY;EmB3EZ;EACA;;AAEA;EACI,OnB8BI;EmB7BJ;EACA;EACA;EACA;EACA;EACA;;AAGJ;EACE,OnBoBM;EmBnBN;EACA;EACA;EACA;EACA;;;AAIN;EACI;EACA;EACA,enBiDY;EmBhDZ;EACA;;AACA;EACE;EACA;EACA,OnBEM;EmBDN;EACA;EACA;EACA;EACA;;;AAIN;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAIJ;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAMJ;EACI;EACA;EACA,enBGY;EmBFZ;EACA;;AAEA;EACI,OnB/CG;EmBgDH;EACA;EACA;EACA;EACA;EACA;;AAGJ;EACE,OnBzDK;EmB0DL;EACA;EACA;EACA;EACA;;;AAIN;EACI;EACA;EACA,enBxBY;EmByBZ;EACA;;AACA;EACE;EACA;EACA,OnB3EK;EmB4EL;EACA;EACA;EACA;EACA;;;AAIN;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAIJ;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAMJ;EACI;EACA;EACA,enBtEY;EmBuEZ;EACA;;AAEA;EACI,OnBhHK;EmBiHL;EACA;EACA;EACA;EACA;EACA;;AAGJ;EACE,OnB1HO;EmB2HP;EACA;EACA;EACA;EACA;;;AAIN;EACI;EACA;EACA,enBjGY;EmBkGZ;EACA;;AACA;EACE;EACA;EACA,OnB5IO;EmB6IP;EACA;EACA;EACA;EACA;;;AAIN;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAIJ;EACE;EACA;;AAEA;EACE;;AAGF;EACE","sourcesContent":["/*\ngenerated by accessible-pygments \nCopyright (c) 2022, Quansight Labs\nLicensed under the BSD license, see LICENSE for details.\n--\ngenerated by Pygments \nCopyright 2006-2025 by the Pygments team.\nLicensed under the BSD license, see LICENSE for details.\n*/\n\n.highlight .hll { background-color: #0969da4a }\n.highlight .c { color: #6E7781 } /* Comment */\n.highlight .err { color: #CF222E } /* Error */\n.highlight .k { color: #CF222E } /* Keyword */\n.highlight .l { color: #953800 } /* Literal */\n.highlight .n { color: #8250DF } /* Name */\n.highlight .o { color: #116329 } /* Operator */\n.highlight .p { color: #24292F } /* Punctuation */\n.highlight .ch { color: #6E7781 } /* Comment.Hashbang */\n.highlight .cm { color: #6E7781 } /* Comment.Multiline */\n.highlight .cp { color: #6E7781 } /* Comment.Preproc */\n.highlight .cpf { color: #6E7781 } /* Comment.PreprocFile */\n.highlight .c1 { color: #6E7781 } /* Comment.Single */\n.highlight .cs { color: #6E7781 } /* Comment.Special */\n.highlight .gd { color: #0550AE } /* Generic.Deleted */\n.highlight .ge { font-style: italic } /* Generic.Emph */\n.highlight .gr { color: #CF222E } /* Generic.Error */\n.highlight .gh { color: #0550AE } /* Generic.Heading */\n.highlight .gs { font-weight: bold } /* Generic.Strong */\n.highlight .gu { color: #0550AE } /* Generic.Subheading */\n.highlight .kc { color: #0550AE } /* Keyword.Constant */\n.highlight .kd { color: #CF222E } /* Keyword.Declaration */\n.highlight .kn { color: #CF222E } /* Keyword.Namespace */\n.highlight .kp { color: #CF222E } /* Keyword.Pseudo */\n.highlight .kr { color: #CF222E } /* Keyword.Reserved */\n.highlight .kt { color: #CF222E } /* Keyword.Type */\n.highlight .ld { color: #953800 } /* Literal.Date */\n.highlight .m { color: #953800 } /* Literal.Number */\n.highlight .s { color: #0550AE } /* Literal.String */\n.highlight .na { color: #953800 } /* Name.Attribute */\n.highlight .nb { color: #953800 } /* Name.Builtin */\n.highlight .nc { color: #0550AE } /* Name.Class */\n.highlight .no { color: #0550AE } /* Name.Constant */\n.highlight .nd { color: #953800 } /* Name.Decorator */\n.highlight .ni { color: #116329 } /* Name.Entity */\n.highlight .ne { color: #8250DF } /* Name.Exception */\n.highlight .nf { color: #0550AE } /* Name.Function */\n.highlight .nl { color: #953800 } /* Name.Label */\n.highlight .nn { color: #24292F } /* Name.Namespace */\n.highlight .nx { color: #8250DF } /* Name.Other */\n.highlight .py { color: #0550AE } /* Name.Property */\n.highlight .nt { color: #116329 } /* Name.Tag */\n.highlight .nv { color: #953800 } /* Name.Variable */\n.highlight .ow { color: #8250DF } /* Operator.Word */\n.highlight .pm { color: #24292F } /* Punctuation.Marker */\n.highlight .w { color: #24292F } /* Text.Whitespace */\n.highlight .mb { color: #953800 } /* Literal.Number.Bin */\n.highlight .mf { color: #953800 } /* Literal.Number.Float */\n.highlight .mh { color: #953800 } /* Literal.Number.Hex */\n.highlight .mi { color: #953800 } /* Literal.Number.Integer */\n.highlight .mo { color: #953800 } /* Literal.Number.Oct */\n.highlight .sa { color: #0550AE } /* Literal.String.Affix */\n.highlight .sb { color: #0550AE } /* Literal.String.Backtick */\n.highlight .sc { color: #0550AE } /* Literal.String.Char */\n.highlight .dl { color: #0550AE } /* Literal.String.Delimiter */\n.highlight .sd { color: #0550AE } /* Literal.String.Doc */\n.highlight .s2 { color: #0550AE } /* Literal.String.Double */\n.highlight .se { color: #0550AE } /* Literal.String.Escape */\n.highlight .sh { color: #0550AE } /* Literal.String.Heredoc */\n.highlight .si { color: #0550AE } /* Literal.String.Interpol */\n.highlight .sx { color: #0550AE } /* Literal.String.Other */\n.highlight .sr { color: #0550AE } /* Literal.String.Regex */\n.highlight .s1 { color: #0550AE } /* Literal.String.Single */\n.highlight .ss { color: #0550AE } /* Literal.String.Symbol */\n.highlight .bp { color: #953800 } /* Name.Builtin.Pseudo */\n.highlight .fm { color: #0550AE } /* Name.Function.Magic */\n.highlight .vc { color: #953800 } /* Name.Variable.Class */\n.highlight .vg { color: #953800 } /* Name.Variable.Global */\n.highlight .vi { color: #953800 } /* Name.Variable.Instance */\n.highlight .vm { color: #953800 } /* Name.Variable.Magic */\n.highlight .il { color: #953800 } /* Literal.Number.Integer.Long */\n","/*! normalize.css v8.0.1 | MIT License | github.com/necolas/normalize.css */\n\n/* Document\n ========================================================================== */\n\n/**\n * 1. Correct the line height in all browsers.\n * 2. Prevent adjustments of font size after orientation changes in iOS.\n */\n\nhtml {\n line-height: 1.15; /* 1 */\n text-size-adjust: 100%; /* 2 */\n}\n\n/* Sections\n ========================================================================== */\n\n/**\n * Remove the margin in all browsers.\n */\n\nbody {\n margin: 0;\n}\n\n/**\n * Render the `main` element consistently in IE.\n */\n\nmain {\n display: block;\n}\n\n/**\n * Correct the font size and margin on `h1` elements within `section` and\n * `article` contexts in Chrome, Firefox, and Safari.\n */\n\nh1 {\n font-size: 2em;\n margin: 0.67em 0;\n}\n\n/* Grouping content\n ========================================================================== */\n\n/**\n * 1. Add the correct box sizing in Firefox.\n * 2. Show the overflow in Edge and IE.\n */\n\nhr {\n box-sizing: content-box; /* 1 */\n height: 0; /* 1 */\n overflow: visible; /* 2 */\n}\n\n/**\n * 1. Correct the inheritance and scaling of font size in all browsers.\n * 2. Correct the odd `em` font sizing in all browsers.\n */\n\npre {\n font-family: monospace; /* 1 */\n font-size: 1em; /* 2 */\n}\n\n/* Text-level semantics\n ========================================================================== */\n\n/**\n * Remove the gray background on active links in IE 10.\n */\n\na {\n background-color: transparent;\n}\n\n/**\n * 1. Remove the bottom border in Chrome 57-\n * 2. Add the correct text decoration in Chrome, Edge, IE, Opera, and Safari.\n */\n\nabbr[title] {\n border-bottom: none; /* 1 */\n text-decoration: underline; /* 2 */\n text-decoration: underline dotted; /* 2 */\n}\n\n/**\n * Add the correct font weight in Chrome, Edge, and Safari.\n */\n\nb,\nstrong {\n font-weight: bolder;\n}\n\n/**\n * 1. Correct the inheritance and scaling of font size in all browsers.\n * 2. Correct the odd `em` font sizing in all browsers.\n */\n\ncode,\nkbd,\nsamp {\n font-family: monospace; /* 1 */\n font-size: 1em; /* 2 */\n}\n\n/**\n * Add the correct font size in all browsers.\n */\n\nsmall {\n font-size: 80%;\n}\n\n/**\n * Prevent `sub` and `sup` elements from affecting the line height in\n * all browsers.\n */\n\nsub,\nsup {\n font-size: 75%;\n line-height: 0;\n position: relative;\n vertical-align: baseline;\n}\n\nsub {\n bottom: -0.25em;\n}\n\nsup {\n top: -0.5em;\n}\n\n/* Embedded content\n ========================================================================== */\n\n/**\n * Remove the border on images inside links in IE 10.\n */\n\nimg {\n border-style: none;\n}\n\n/* Forms\n ========================================================================== */\n\n/**\n * 1. Change the font styles in all browsers.\n * 2. Remove the margin in Firefox and Safari.\n */\n\nbutton,\ninput,\noptgroup,\nselect,\ntextarea {\n font-family: inherit; /* 1 */\n font-size: 100%; /* 1 */\n line-height: 1.15; /* 1 */\n margin: 0; /* 2 */\n}\n\n/**\n * Show the overflow in IE.\n * 1. Show the overflow in Edge.\n */\n\nbutton,\ninput {\n /* 1 */\n overflow: visible;\n}\n\n/**\n * Remove the inheritance of text transform in Edge, Firefox, and IE.\n * 1. Remove the inheritance of text transform in Firefox.\n */\n\nbutton,\nselect {\n /* 1 */\n text-transform: none;\n}\n\n/**\n * Correct the inability to style clickable types in iOS and Safari.\n */\n\nbutton,\n[type=\"button\"],\n[type=\"reset\"],\n[type=\"submit\"] {\n appearance: button;\n}\n\n/**\n * Remove the inner border and padding in Firefox.\n */\n\nbutton::-moz-focus-inner,\n[type=\"button\"]::-moz-focus-inner,\n[type=\"reset\"]::-moz-focus-inner,\n[type=\"submit\"]::-moz-focus-inner {\n border-style: none;\n padding: 0;\n}\n\n/**\n * Restore the focus styles unset by the previous rule.\n */\n\nbutton:-moz-focusring,\n[type=\"button\"]:-moz-focusring,\n[type=\"reset\"]:-moz-focusring,\n[type=\"submit\"]:-moz-focusring {\n outline: 1px dotted ButtonText;\n}\n\n/**\n * Correct the padding in Firefox.\n */\n\nfieldset {\n padding: 0.35em 0.75em 0.625em;\n}\n\n/**\n * 1. Correct the text wrapping in Edge and IE.\n * 2. Correct the color inheritance from `fieldset` elements in IE.\n * 3. Remove the padding so developers are not caught out when they zero out\n * `fieldset` elements in all browsers.\n */\n\nlegend {\n box-sizing: border-box; /* 1 */\n color: inherit; /* 2 */\n display: table; /* 1 */\n max-width: 100%; /* 1 */\n padding: 0; /* 3 */\n white-space: normal; /* 1 */\n}\n\n/**\n * Add the correct vertical alignment in Chrome, Firefox, and Opera.\n */\n\nprogress {\n vertical-align: baseline;\n}\n\n/**\n * Remove the default vertical scrollbar in IE 10+.\n */\n\ntextarea {\n overflow: auto;\n}\n\n/**\n * 1. Add the correct box sizing in IE 10.\n * 2. Remove the padding in IE 10.\n */\n\n[type=\"checkbox\"],\n[type=\"radio\"] {\n box-sizing: border-box; /* 1 */\n padding: 0; /* 2 */\n}\n\n/**\n * Correct the cursor style of increment and decrement buttons in Chrome.\n */\n\n[type=\"number\"]::-webkit-inner-spin-button,\n[type=\"number\"]::-webkit-outer-spin-button {\n height: auto;\n}\n\n/**\n * 1. Correct the odd appearance in Chrome and Safari.\n * 2. Correct the outline style in Safari.\n */\n\n[type=\"search\"] {\n appearance: textfield; /* 1 */\n outline-offset: -2px; /* 2 */\n}\n\n/**\n * Remove the inner padding in Chrome and Safari on macOS.\n */\n\n[type=\"search\"]::-webkit-search-decoration {\n appearance: none;\n}\n\n/**\n * 1. Correct the inability to style clickable types in iOS and Safari.\n * 2. Change font properties to `inherit` in Safari.\n */\n\n::-webkit-file-upload-button {\n appearance: button; /* 1 */\n font: inherit; /* 2 */\n}\n\n/* Interactive\n ========================================================================== */\n\n/*\n * Add the correct display in Edge, IE 10+, and Firefox.\n */\n\ndetails {\n display: block;\n}\n\n/*\n * Add the correct display in all browsers.\n */\n\nsummary {\n display: list-item;\n}\n\n/* Misc\n ========================================================================== */\n\n/**\n * Add the correct display in IE 10+.\n */\n\ntemplate {\n display: none;\n}\n\n/**\n * Add the correct display in IE 10.\n */\n\n[hidden] {\n display: none;\n}\n","// Base element style overrides\n// stylelint-disable selector-no-type, selector-max-type, selector-max-specificity, selector-max-id\n\n:root {\n color-scheme: $color-scheme;\n}\n\n* {\n box-sizing: border-box;\n}\n\nhtml {\n scroll-behavior: smooth;\n\n @include fs-4;\n}\n\nbody {\n font-family: $body-font-family;\n font-size: inherit;\n line-height: $body-line-height;\n color: $body-text-color;\n background-color: $body-background-color;\n overflow-wrap: break-word;\n}\n\nol,\nul,\ndl,\npre,\naddress,\nblockquote,\ntable,\ndiv,\nhr,\nform,\nfieldset,\nnoscript .table-wrapper {\n margin-top: 0;\n}\n\nh1,\nh2,\nh3,\nh4,\nh5,\nh6,\n#toctitle {\n margin-top: 0;\n margin-bottom: 1em;\n font-weight: 500;\n line-height: $body-heading-line-height;\n color: $body-heading-color;\n}\n\np {\n margin-top: 1em;\n margin-bottom: 1em;\n}\n\na {\n color: $link-color;\n text-decoration: none;\n}\n\na:not([class]) {\n text-decoration: underline;\n text-decoration-color: $border-color;\n text-underline-offset: 2px;\n\n &:hover {\n text-decoration-color: rgba($link-color, 0.45);\n }\n}\n\ncode {\n font-family: $mono-font-family;\n font-size: 0.75em;\n line-height: $body-line-height;\n}\n\nfigure,\npre {\n margin: 0;\n}\n\nli {\n margin: 0.25em 0;\n}\n\nimg {\n max-width: 100%;\n height: auto;\n}\n\nhr {\n height: 1px;\n padding: 0;\n margin: $sp-6 0;\n background-color: $border-color;\n border: 0;\n}\n\n// adds a GitHub-style sidebar to blockquotes\nblockquote {\n margin: 10px 0;\n\n // resets user-agent stylesheets for blockquotes\n margin-block-start: 0;\n margin-inline-start: 0;\n padding-left: 1rem;\n border-left: 3px solid $border-color;\n}\n","// Meshtastic Material 3 — Light color scheme for just-the-docs\n// Source: core/ui/.../Color.kt §8.2 (Light Scheme)\n//\n// Brand colors:\n// Primary (Light): #2D8F52 (Green 700)\n// Surface (Light): #F5F6FA (Neutral 50)\n\n$color-scheme: light;\n\n// Body / page background\n$body-background-color: #F5F6FA; // Neutral 50 — surfaceLight\n$sidebar-color: #ECEDF3; // Neutral 100 — surfaceContainerLight\n$body-text-color: #2C2D3C; // Neutral 800 — onSurfaceLight\n$body-heading-color: #2C2D3C; // Neutral 800\n\n// Links\n$link-color: #2D8F52; // Green 700 — primaryLight\n$nav-link-color: #2D8F52; // Green 700\n\n// Navigation\n$nav-child-link-color: #555668; // Neutral 600 — secondaryLight\n$search-result-preview-color: #555668;\n\n// Code\n$code-background-color: #ECEDF3; // Neutral 100\n$code-linenumber-color: #9496A6; // Neutral 400\n\n// Borders\n$border-color: #D5D6E0; // Neutral 200 — outlineVariantLight\n$table-background-color: #F5F6FA; // Neutral 50\n\n// Buttons\n$btn-primary-color: #2D8F52; // Green 700\n\n// Feedback / callouts\n$feedback-color: #E0E1EB; // surfaceContainerHighLight\n\n// Search\n$search-background-color: #FFFFFF; // surfaceContainerLowestLight\n","@mixin fs-1 {\n & {\n font-size: $font-size-1 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-1-sm !important;\n }\n}\n\n@mixin fs-2 {\n & {\n font-size: $font-size-2 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-3 !important;\n }\n}\n\n@mixin fs-3 {\n & {\n font-size: $font-size-3 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-4 !important;\n }\n}\n\n@mixin fs-4 {\n & {\n font-size: $font-size-4 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-5 !important;\n }\n}\n\n@mixin fs-5 {\n & {\n font-size: $font-size-5 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-6 !important;\n }\n}\n\n@mixin fs-6 {\n & {\n font-size: $font-size-6 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-7 !important;\n line-height: $body-heading-line-height;\n }\n}\n\n@mixin fs-7 {\n & {\n font-size: $font-size-7 !important;\n line-height: $body-heading-line-height;\n }\n\n @include mq(sm) {\n font-size: $font-size-8 !important;\n }\n}\n\n@mixin fs-8 {\n & {\n font-size: $font-size-8 !important;\n line-height: $body-heading-line-height;\n }\n\n @include mq(sm) {\n font-size: $font-size-9 !important;\n }\n}\n\n@mixin fs-9 {\n & {\n font-size: $font-size-9 !important;\n line-height: $body-heading-line-height;\n }\n\n @include mq(sm) {\n font-size: $font-size-10 !important;\n }\n}\n\n@mixin fs-10 {\n & {\n font-size: $font-size-10 !important;\n line-height: $body-heading-line-height;\n }\n\n @include mq(sm) {\n font-size: $font-size-10-sm !important;\n }\n}\n","// Media query\n\n// Media query mixin\n// Usage:\n// @include mq(md) {\n// ..medium and up styles\n// }\n@mixin mq($name) {\n // Retrieves the value from the key\n $value: map-get($media-queries, $name);\n\n // If the key exists in the map\n @if $value {\n // Prints a media query based on the value\n @media (min-width: $value) {\n @content;\n }\n } @else {\n @warn \"No value could be retrieved from `#{$media-query}`. Please make sure it is defined in `$media-queries` map.\";\n }\n}\n\n// Responsive container\n\n@mixin container {\n padding-right: $gutter-spacing-sm;\n padding-left: $gutter-spacing-sm;\n\n @include mq(md) {\n padding-right: $gutter-spacing;\n padding-left: $gutter-spacing;\n }\n}\n","// Typography\n\n// prettier-ignore\n$body-font-family: system-ui, -apple-system, blinkmacsystemfont, \"Segoe UI\",\n roboto, \"Helvetica Neue\", arial, sans-serif, \"Segoe UI Emoji\" !default;\n$mono-font-family: \"SFMono-Regular\", menlo, consolas, monospace !default;\n$root-font-size: 16px !default; // DEPRECATED: previously base font-size for rems\n$body-line-height: 1.4 !default;\n$content-line-height: 1.6 !default;\n$body-heading-line-height: 1.25 !default;\n\n// Font size\n// `-sm` suffix is the size at the small (and above) media query\n\n$font-size-1: 0.5625rem !default;\n$font-size-1-sm: 0.625rem !default;\n$font-size-2: 0.6875rem !default; // h4 - uppercased!, h6 not uppercased, text-small\n$font-size-3: 0.75rem !default; // h5\n$font-size-4: 0.875rem !default;\n$font-size-5: 1rem !default; // h3\n$font-size-6: 1.125rem !default; // h2\n$font-size-7: 1.5rem !default;\n$font-size-8: 2rem !default; // h1\n$font-size-9: 2.25rem !default;\n$font-size-10: 2.625rem !default;\n$font-size-10-sm: 3rem !default;\n\n// Colors\n\n$white: #fff !default;\n$grey-dk-000: #959396 !default;\n$grey-dk-100: #5c5962 !default;\n$grey-dk-200: #44434d !default;\n$grey-dk-250: #302d36 !default;\n$grey-dk-300: #27262b !default;\n$grey-lt-000: #f5f6fa !default;\n$grey-lt-100: #eeebee !default;\n$grey-lt-200: #ecebed !default;\n$grey-lt-300: #e6e1e8 !default;\n$purple-000: #7253ed !default;\n$purple-100: #5e41d0 !default;\n$purple-200: #4e26af !default;\n$purple-300: #381885 !default;\n$blue-000: #2c84fa !default;\n$blue-100: #2869e6 !default;\n$blue-200: #264caf !default;\n$blue-300: #183385 !default;\n$green-000: #41d693 !default;\n$green-100: #11b584 !default;\n$green-200: #009c7b !default;\n$green-300: #026e57 !default;\n$yellow-000: #ffeb82 !default;\n$yellow-100: #fadf50 !default;\n$yellow-200: #f7d12e !default;\n$yellow-300: #e7af06 !default;\n$red-000: #f77e7e !default;\n$red-100: #f96e65 !default;\n$red-200: #e94c4c !default;\n$red-300: #dd2e2e !default;\n\n// Spacing\n\n$spacing-unit: 1rem; // 1rem == 16px\n\n$spacers: (\n sp-0: 0,\n sp-1: $spacing-unit * 0.25,\n sp-2: $spacing-unit * 0.5,\n sp-3: $spacing-unit * 0.75,\n sp-4: $spacing-unit,\n sp-5: $spacing-unit * 1.5,\n sp-6: $spacing-unit * 2,\n sp-7: $spacing-unit * 2.5,\n sp-8: $spacing-unit * 3,\n sp-9: $spacing-unit * 3.5,\n sp-10: $spacing-unit * 4,\n) !default;\n$sp-1: map-get($spacers, sp-1) !default; // 0.25 rem == 4px\n$sp-2: map-get($spacers, sp-2) !default; // 0.5 rem == 8px\n$sp-3: map-get($spacers, sp-3) !default; // 0.75 rem == 12px\n$sp-4: map-get($spacers, sp-4) !default; // 1 rem == 16px\n$sp-5: map-get($spacers, sp-5) !default; // 1.5 rem == 24px\n$sp-6: map-get($spacers, sp-6) !default; // 2 rem == 32px\n$sp-7: map-get($spacers, sp-7) !default; // 2.5 rem == 40px\n$sp-8: map-get($spacers, sp-8) !default; // 3 rem == 48px\n$sp-9: map-get($spacers, sp-9) !default; // 3.5 rem == 56px\n$sp-10: map-get($spacers, sp-10) !default; // 4 rem == 64px\n\n// Borders\n\n$border: 1px solid !default;\n$border-radius: 4px !default;\n$border-color: $grey-lt-100 !default;\n\n// Grid system\n\n$gutter-spacing: $sp-6 !default;\n$gutter-spacing-sm: $sp-4 !default;\n$nav-width: 16.5rem !default;\n$nav-width-md: 15.5rem !default;\n$nav-list-item-height: $sp-6 !default;\n$nav-list-item-height-sm: $sp-8 !default;\n$nav-list-expander-right: true;\n$content-width: 50rem !default;\n$header-height: 3.75rem !default;\n$search-results-width: $content-width - $nav-width !default;\n$transition-duration: 400ms;\n\n// Media queries in pixels\n\n$media-queries: (\n xs: 20rem,\n sm: 31.25rem,\n md: $content-width,\n lg: $content-width + $nav-width,\n xl: 87.5rem,\n) !default;\n","// The basic two column layout\n\n.side-bar {\n z-index: 0;\n display: flex;\n flex-wrap: wrap;\n background-color: $sidebar-color;\n\n @include mq(md) {\n flex-flow: column nowrap;\n position: fixed;\n width: $nav-width-md;\n height: 100%;\n border-right: $border $border-color;\n align-items: flex-end;\n }\n\n @include mq(lg) {\n width: calc((100% - #{$nav-width + $content-width}) / 2 + #{$nav-width});\n min-width: $nav-width;\n }\n\n & + .main {\n @include mq(md) {\n margin-left: $nav-width-md;\n }\n\n @include mq(lg) {\n // stylelint-disable function-name-case\n // disable for Max(), we want to use the CSS max() function\n margin-left: Max(\n #{$nav-width},\n calc((100% - #{$nav-width + $content-width}) / 2 + #{$nav-width})\n );\n // stylelint-enable function-name-case\n }\n\n .main-header {\n display: none;\n background-color: $sidebar-color;\n\n @include mq(md) {\n display: flex;\n background-color: $body-background-color;\n }\n\n &.nav-open {\n display: block;\n\n @include mq(md) {\n display: flex;\n }\n }\n }\n }\n}\n\n.main {\n margin: auto;\n\n @include mq(md) {\n position: relative;\n max-width: $content-width;\n }\n}\n\n.main-content-wrap {\n padding-top: $gutter-spacing-sm;\n padding-bottom: $gutter-spacing-sm;\n\n @include container;\n\n @include mq(md) {\n padding-top: $gutter-spacing;\n padding-bottom: $gutter-spacing;\n }\n}\n\n.main-header {\n z-index: 0;\n border-bottom: $border $border-color;\n\n @include mq(md) {\n display: flex;\n justify-content: space-between;\n height: $header-height;\n }\n}\n\n.site-nav,\n.site-header,\n.site-footer {\n width: 100%;\n\n @include mq(lg) {\n width: $nav-width;\n }\n}\n\n.site-nav {\n display: none;\n\n &.nav-open {\n display: block;\n }\n\n @include mq(md) {\n display: block;\n padding-top: $sp-8;\n padding-bottom: $gutter-spacing-sm;\n overflow-y: auto;\n flex: 1 1 auto;\n }\n}\n\n.site-header {\n display: flex;\n min-height: $header-height;\n align-items: center;\n\n @include mq(md) {\n height: $header-height;\n max-height: $header-height;\n border-bottom: $border $border-color;\n }\n}\n\n.site-title {\n flex-grow: 1;\n display: flex;\n height: 100%;\n align-items: center;\n padding-top: $sp-3;\n padding-bottom: $sp-3;\n color: $body-heading-color;\n\n @include container;\n\n @include fs-6;\n\n @include mq(md) {\n padding-top: $sp-2;\n padding-bottom: $sp-2;\n }\n}\n\n@if variable-exists(logo) {\n .site-logo {\n width: 100%;\n height: 100%;\n background-image: url($logo);\n background-repeat: no-repeat;\n background-position: left center;\n background-size: contain;\n }\n}\n\n.site-button {\n display: flex;\n height: 100%;\n padding: $gutter-spacing-sm;\n align-items: center;\n}\n\n@include mq(md) {\n .site-header .site-button {\n display: none;\n }\n}\n\n.site-title:hover {\n background-image: linear-gradient(\n -90deg,\n rgba($feedback-color, 1) 0%,\n rgba($feedback-color, 0.8) 80%,\n rgba($feedback-color, 0) 100%\n );\n}\n\n.site-button:hover {\n background-image: linear-gradient(\n -90deg,\n rgba($feedback-color, 1) 0%,\n rgba($feedback-color, 0.8) 100%\n );\n}\n\n.site-footer {\n position: absolute;\n bottom: 0;\n left: 0;\n padding-top: $sp-4;\n padding-bottom: $sp-4;\n\n @include container;\n\n @include fs-2;\n\n @include mq(md) {\n position: static;\n justify-self: end;\n }\n}\n\n.icon {\n width: $sp-5;\n height: $sp-5;\n color: $link-color;\n}\n","@charset \"UTF-8\";\n\n// Styles for rendered markdown in the .main-content container\n// stylelint-disable selector-no-type, max-nesting-depth, selector-max-compound-selectors, selector-max-type, selector-max-specificity, selector-max-id\n\n.main-content {\n line-height: $content-line-height;\n\n ol,\n ul,\n dl,\n pre,\n address,\n blockquote,\n .table-wrapper {\n margin-top: 0.5em;\n }\n\n a {\n overflow: hidden;\n text-overflow: ellipsis;\n }\n\n ul,\n ol {\n padding-left: 1.5em;\n }\n\n li {\n .highlight {\n margin-top: $sp-1;\n }\n }\n\n ol {\n list-style-type: none;\n counter-reset: step-counter;\n\n > li {\n position: relative;\n\n &::before {\n position: absolute;\n top: 0.2em;\n left: -1.6em;\n color: $grey-dk-000;\n content: counter(step-counter);\n counter-increment: step-counter;\n @include fs-3;\n\n @include mq(sm) {\n top: 0.11em;\n }\n }\n\n ol {\n counter-reset: sub-counter;\n\n > li {\n &::before {\n content: counter(sub-counter, lower-alpha);\n counter-increment: sub-counter;\n }\n }\n }\n }\n }\n\n ul {\n list-style: none;\n\n > li {\n &::before {\n position: absolute;\n margin-left: -1.4em;\n color: $grey-dk-000;\n content: \"•\";\n }\n }\n }\n\n .task-list-item {\n &::before {\n content: \"\";\n }\n }\n\n .task-list-item-checkbox {\n margin-right: 0.6em;\n margin-left: -1.4em;\n\n // The same margin-left is used above for ul > li::before\n }\n\n hr + * {\n margin-top: 0;\n }\n\n h1:first-of-type {\n margin-top: 0.5em;\n }\n\n dl {\n display: grid;\n grid-template: auto / 10em 1fr;\n }\n\n dt,\n dd {\n margin: 0.25em 0;\n }\n\n dt {\n grid-column: 1;\n font-weight: 500;\n text-align: right;\n\n &::after {\n content: \":\";\n }\n }\n\n dd {\n grid-column: 2;\n margin-bottom: 0;\n margin-left: 1em;\n\n blockquote,\n div,\n dl,\n dt,\n h1,\n h2,\n h3,\n h4,\n h5,\n h6,\n li,\n ol,\n p,\n pre,\n table,\n ul,\n .table-wrapper {\n &:first-child {\n margin-top: 0;\n }\n }\n }\n\n dd,\n ol,\n ul {\n dl:first-child {\n dt:first-child,\n dd:nth-child(2) {\n margin-top: 0;\n }\n }\n }\n\n .anchor-heading {\n position: absolute;\n right: -$sp-4;\n width: $sp-5;\n height: 100%;\n padding-right: $sp-1;\n padding-left: $sp-1;\n overflow: visible;\n\n @include mq(md) {\n right: auto;\n left: -$sp-5;\n }\n\n svg {\n display: inline-block;\n width: 100%;\n height: 100%;\n color: $link-color;\n visibility: hidden;\n }\n }\n\n .anchor-heading:hover,\n .anchor-heading:focus,\n h1:hover > .anchor-heading,\n h2:hover > .anchor-heading,\n h3:hover > .anchor-heading,\n h4:hover > .anchor-heading,\n h5:hover > .anchor-heading,\n h6:hover > .anchor-heading {\n svg {\n visibility: visible;\n }\n }\n\n summary {\n cursor: pointer;\n }\n\n h1,\n h2,\n h3,\n h4,\n h5,\n h6,\n #toctitle {\n position: relative;\n margin-top: 1.5em;\n margin-bottom: 0.25em;\n\n + table,\n + .table-wrapper,\n + .code-example,\n + .highlighter-rouge,\n + .sectionbody .listingblock {\n margin-top: 1em;\n }\n\n + p:not(.label) {\n margin-top: 0;\n }\n }\n\n > h1:first-child,\n > h2:first-child,\n > h3:first-child,\n > h4:first-child,\n > h5:first-child,\n > h6:first-child,\n > .sect1:first-child > h2,\n > .sect2:first-child > h3,\n > .sect3:first-child > h4,\n > .sect4:first-child > h5,\n > .sect5:first-child > h6 {\n margin-top: $sp-2;\n }\n}\n","// Main nav, breadcrumb, etc...\n// stylelint-disable selector-no-type, max-nesting-depth, selector-max-compound-selectors, selector-max-type, selector-max-specificity\n\n.nav-list {\n padding: 0;\n margin-top: 0;\n margin-bottom: 0;\n list-style: none;\n\n .nav-list-item {\n position: relative;\n margin: 0;\n\n @include fs-4;\n\n @include mq(md) {\n @include fs-3;\n }\n\n .nav-list-link {\n display: block;\n min-height: $nav-list-item-height-sm;\n padding-top: $sp-1;\n padding-bottom: $sp-1;\n line-height: #{$nav-list-item-height-sm - 2 * $sp-1};\n @if $nav-list-expander-right {\n padding-right: $nav-list-item-height-sm;\n padding-left: $gutter-spacing-sm;\n } @else {\n padding-right: $gutter-spacing-sm;\n padding-left: $nav-list-item-height-sm;\n }\n\n @include mq(md) {\n min-height: $nav-list-item-height;\n line-height: #{$nav-list-item-height - 2 * $sp-1};\n @if $nav-list-expander-right {\n padding-right: $nav-list-item-height;\n padding-left: $gutter-spacing;\n } @else {\n padding-right: $gutter-spacing;\n padding-left: $nav-list-item-height;\n }\n }\n\n &.external > svg {\n width: $sp-4;\n height: $sp-4;\n vertical-align: text-bottom;\n }\n\n &.active {\n font-weight: 600;\n text-decoration: none;\n }\n\n &:hover,\n &.active {\n color: darken($link-color, 5%);\n background-image: linear-gradient(\n -90deg,\n rgba($feedback-color, 1) 0%,\n rgba($feedback-color, 0.8) 80%,\n rgba($feedback-color, 0) 100%\n );\n }\n }\n\n .nav-list-expander {\n position: absolute;\n @if $nav-list-expander-right {\n right: 0;\n }\n\n width: $nav-list-item-height-sm;\n height: $nav-list-item-height-sm;\n padding: #{$nav-list-item-height-sm * 0.25};\n color: $link-color;\n\n @include mq(md) {\n width: $nav-list-item-height;\n height: $nav-list-item-height;\n padding: #{$nav-list-item-height * 0.25};\n }\n\n &:hover {\n background-image: linear-gradient(\n -90deg,\n rgba($feedback-color, 1) 0%,\n rgba($feedback-color, 0.8) 100%\n );\n }\n\n @if $nav-list-expander-right {\n svg {\n transform: rotate(90deg);\n }\n }\n }\n\n > .nav-list {\n display: none;\n padding-left: $sp-3;\n list-style: none;\n\n .nav-list-item {\n position: relative;\n\n .nav-list-link {\n color: $nav-child-link-color;\n }\n\n .nav-list-expander {\n color: $nav-child-link-color;\n }\n }\n }\n\n &.active {\n > .nav-list-expander svg {\n @if $nav-list-expander-right {\n transform: rotate(-90deg);\n } @else {\n transform: rotate(90deg);\n }\n }\n\n > .nav-list {\n display: block;\n }\n }\n }\n}\n\n.nav-category {\n padding: $sp-2 $gutter-spacing-sm;\n font-weight: 600;\n text-align: start;\n text-transform: uppercase;\n border-bottom: $border $border-color;\n @include fs-2;\n\n @include mq(md) {\n padding: $sp-2 $gutter-spacing;\n margin-top: $gutter-spacing-sm;\n text-align: start;\n\n &:first-child {\n margin-top: 0;\n }\n }\n}\n\n.nav-list.nav-category-list {\n > .nav-list-item {\n margin: 0;\n\n > .nav-list {\n padding: 0;\n\n > .nav-list-item {\n > .nav-list-link {\n color: $link-color;\n }\n\n > .nav-list-expander {\n color: $link-color;\n }\n }\n }\n }\n}\n\n// Aux nav\n\n.aux-nav {\n height: 100%;\n overflow-x: auto;\n @include fs-2;\n\n .aux-nav-list {\n display: flex;\n height: 100%;\n padding: 0;\n margin: 0;\n list-style: none;\n }\n\n .aux-nav-list-item {\n display: inline-block;\n height: 100%;\n padding: 0;\n margin: 0;\n }\n\n @include mq(md) {\n padding-right: $gutter-spacing-sm;\n }\n}\n\n// Breadcrumb nav\n\n.breadcrumb-nav {\n @include mq(md) {\n margin-top: -$sp-4;\n }\n}\n\n.breadcrumb-nav-list {\n padding-left: 0;\n margin-bottom: $sp-3;\n list-style: none;\n}\n\n.breadcrumb-nav-list-item {\n display: table-cell;\n @include fs-2;\n\n &::before {\n display: none;\n }\n\n &::after {\n display: inline-block;\n margin-right: $sp-2;\n margin-left: $sp-2;\n color: $grey-dk-000;\n content: \"/\";\n }\n\n &:last-child {\n &::after {\n content: \"\";\n }\n }\n}\n","// Typography\n// stylelint-disable selector-no-type, selector-max-type, selector-max-specificity, selector-max-id\n\nh1,\n.text-alpha {\n font-weight: 300;\n\n @include fs-8;\n}\n\nh2,\n.text-beta,\n#toctitle {\n @include fs-6;\n}\n\nh3,\n.text-gamma {\n @include fs-5;\n}\n\nh4,\n.text-delta {\n font-weight: 400;\n text-transform: uppercase;\n letter-spacing: 0.1em;\n\n @include fs-2;\n}\n\nh4 code {\n text-transform: none;\n}\n\nh5,\n.text-epsilon {\n @include fs-3;\n}\n\nh6,\n.text-zeta {\n @include fs-2;\n}\n\n.text-small {\n @include fs-2;\n}\n\n.text-mono {\n font-family: $mono-font-family !important;\n}\n\n.text-left {\n text-align: left !important;\n}\n\n.text-center {\n text-align: center !important;\n}\n\n.text-right {\n text-align: right !important;\n}\n","// Labels (not the form kind)\n\n// this :not() prevents a style clash with Mermaid.js's\n// diagram labels, which also use .label\n// for more, see https://github.com/just-the-docs/just-the-docs/issues/1272\n// and the accompanying PR\n.label:not(g),\n.label-blue:not(g) {\n display: inline-block;\n padding: 0.16em 0.56em;\n margin-right: $sp-2;\n margin-left: $sp-2;\n color: $white;\n text-transform: uppercase;\n vertical-align: middle;\n background-color: $blue-100;\n border-radius: 12px;\n\n @include fs-2;\n}\n\n.label-green:not(g) {\n background-color: $green-300;\n}\n\n.label-purple:not(g) {\n background-color: $purple-100;\n}\n\n.label-red:not(g) {\n background-color: $red-300;\n}\n\n.label-yellow:not(g) {\n color: $grey-dk-200;\n background-color: $yellow-200;\n}\n","// Buttons and things that look like buttons\n// stylelint-disable color-named\n\n.btn {\n display: inline-block;\n box-sizing: border-box;\n padding: 0.3em 1em;\n margin: 0;\n font-family: inherit;\n font-size: inherit;\n font-weight: 500;\n line-height: 1.5;\n color: $link-color;\n text-decoration: none;\n vertical-align: baseline;\n cursor: pointer;\n background-color: $base-button-color;\n border-width: 0;\n border-radius: $border-radius;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n appearance: none;\n\n &:focus {\n text-decoration: none;\n outline: none;\n box-shadow: 0 0 0 3px rgba(blue, 0.25);\n }\n\n &:focus:hover,\n &.selected:focus {\n box-shadow: 0 0 0 3px rgba(blue, 0.25);\n }\n\n &:hover,\n &.zeroclipboard-is-hover {\n color: darken($link-color, 2%);\n }\n\n &:hover,\n &:active,\n &.zeroclipboard-is-hover,\n &.zeroclipboard-is-active {\n text-decoration: none;\n background-color: darken($base-button-color, 1%);\n }\n\n &:active,\n &.selected,\n &.zeroclipboard-is-active {\n background-color: darken($base-button-color, 3%);\n background-image: none;\n box-shadow: inset 0 2px 4px rgba(0, 0, 0, 0.15);\n }\n\n &.selected:hover {\n background-color: darken(#dcdcdc, 5%);\n }\n\n &:disabled,\n &.disabled {\n &,\n &:hover {\n color: rgba(102, 102, 102, 0.5);\n cursor: default;\n background-color: rgba(229, 229, 229, 0.5);\n background-image: none;\n box-shadow: none;\n }\n }\n}\n\n.btn-outline {\n color: $link-color;\n background: transparent;\n box-shadow: inset 0 0 0 2px $grey-lt-300;\n\n &:hover,\n &:active,\n &.zeroclipboard-is-hover,\n &.zeroclipboard-is-active {\n color: darken($link-color, 4%);\n text-decoration: none;\n background-color: transparent;\n box-shadow: inset 0 0 0 3px $grey-lt-300;\n }\n\n &:focus {\n text-decoration: none;\n outline: none;\n box-shadow:\n inset 0 0 0 2px $grey-dk-100,\n 0 0 0 3px rgba(blue, 0.25);\n }\n\n &:focus:hover,\n &.selected:focus {\n box-shadow: inset 0 0 0 2px $grey-dk-100;\n }\n}\n\n.btn-primary {\n @include btn-color($white, $btn-primary-color);\n}\n\n.btn-purple {\n @include btn-color($white, $purple-100);\n}\n\n.btn-blue {\n @include btn-color($white, $blue-200);\n}\n\n.btn-green {\n @include btn-color($white, $green-300);\n}\n\n.btn-reset {\n background: none;\n border: none;\n margin: 0;\n text-align: inherit;\n font: inherit;\n border-radius: 0;\n appearance: none;\n}\n","$color-scheme: light !default;\n$body-background-color: $white !default;\n$body-heading-color: $grey-dk-300 !default;\n$body-text-color: $grey-dk-100 !default;\n$link-color: $purple-000 !default;\n$nav-child-link-color: $grey-dk-100 !default;\n$sidebar-color: $grey-lt-000 !default;\n$base-button-color: #f7f7f7 !default;\n$btn-primary-color: $purple-100 !default;\n$code-background-color: $white !default;\n$feedback-color: darken($sidebar-color, 3%) !default;\n$table-background-color: $white !default;\n$search-background-color: $white !default;\n$search-result-preview-color: $grey-dk-100 !default;\n\n@import \"./vendor/accessible-pygments/github-light\";\n","// Colored button\n\n@mixin btn-color($fg, $bg) {\n color: $fg;\n background-color: darken($bg, 2%);\n background-image: linear-gradient(lighten($bg, 5%), darken($bg, 2%));\n box-shadow:\n 0 1px 3px rgba(0, 0, 0, 0.25),\n 0 4px 10px rgba(0, 0, 0, 0.12);\n\n &:hover,\n &.zeroclipboard-is-hover {\n color: $fg;\n background-color: darken($bg, 4%);\n background-image: linear-gradient((lighten($bg, 2%), darken($bg, 4%)));\n }\n\n &:active,\n &.selected,\n &.zeroclipboard-is-active {\n background-color: darken($bg, 5%);\n background-image: none;\n box-shadow: inset 0 2px 4px rgba(0, 0, 0, 0.15);\n }\n\n &.selected:hover {\n background-color: darken($bg, 10%);\n }\n}\n","// Search input and autocomplete\n\n.search {\n position: relative;\n z-index: 2;\n flex-grow: 1;\n height: $sp-10;\n padding: $sp-2;\n transition: padding linear #{$transition-duration * 0.5};\n\n @include mq(md) {\n position: relative !important;\n width: auto !important;\n height: 100% !important;\n padding: 0;\n transition: none;\n }\n}\n\n.search-input-wrap {\n position: relative;\n z-index: 1;\n height: $sp-8;\n overflow: hidden;\n border-radius: $border-radius;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n transition: height linear #{$transition-duration * 0.5};\n\n @include mq(md) {\n position: absolute;\n width: 100%;\n max-width: $search-results-width;\n height: 100% !important;\n border-radius: 0;\n box-shadow: none;\n transition: width ease $transition-duration;\n }\n}\n\n.search-input {\n position: absolute;\n width: 100%;\n height: 100%;\n padding: $sp-2 $gutter-spacing-sm $sp-2 #{$gutter-spacing-sm + $sp-5};\n font-size: 1rem;\n color: $body-text-color;\n background-color: $search-background-color;\n border-top: 0;\n border-right: 0;\n border-bottom: 0;\n border-left: 0;\n border-radius: 0;\n\n @include mq(md) {\n padding: $sp-2 $gutter-spacing-sm $sp-2 #{$gutter-spacing + $sp-5};\n font-size: 0.875rem;\n background-color: $body-background-color;\n transition: padding-left linear #{$transition-duration * 0.5};\n }\n\n &:focus {\n outline: 2px solid $link-color;\n outline-offset: -2px;\n\n + .search-label .search-icon {\n color: $link-color;\n }\n }\n}\n\n.search-label {\n position: absolute;\n display: flex;\n height: 100%;\n padding-left: $gutter-spacing-sm;\n\n @include mq(md) {\n padding-left: $gutter-spacing;\n transition: padding-left linear #{$transition-duration * 0.5};\n }\n\n .search-icon {\n width: #{$sp-4 * 1.2};\n height: #{$sp-4 * 1.2};\n align-self: center;\n color: $grey-dk-000;\n }\n}\n\n.search-results {\n position: absolute;\n left: 0;\n display: none;\n width: 100%;\n max-height: calc(100% - #{$sp-10});\n overflow-y: auto;\n background-color: $search-background-color;\n border-bottom-right-radius: $border-radius;\n border-bottom-left-radius: $border-radius;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n\n @include mq(md) {\n top: 100%;\n width: $search-results-width;\n max-height: calc(100vh - 200%) !important;\n }\n}\n\n.search-results-list {\n padding-left: 0;\n margin-bottom: $sp-1;\n list-style: none;\n @include fs-4;\n\n @include mq(md) {\n @include fs-3;\n }\n}\n\n.search-results-list-item {\n padding: 0;\n margin: 0;\n}\n\n.search-result {\n display: block;\n padding: $sp-1 $sp-3;\n\n &:hover,\n &.active {\n background-color: $feedback-color;\n }\n}\n\n.search-result-title {\n display: block;\n padding-top: $sp-2;\n padding-bottom: $sp-2;\n\n @include mq(sm) {\n display: inline-block;\n width: 40%;\n padding-right: $sp-2;\n vertical-align: top;\n }\n}\n\n.search-result-doc {\n display: flex;\n align-items: center;\n word-wrap: break-word;\n\n &.search-result-doc-parent {\n opacity: 0.5;\n @include fs-3;\n\n @include mq(md) {\n @include fs-2;\n }\n }\n\n .search-result-icon {\n width: $sp-4;\n height: $sp-4;\n margin-right: $sp-2;\n color: $link-color;\n flex-shrink: 0;\n }\n\n .search-result-doc-title {\n overflow: auto;\n }\n}\n\n.search-result-section {\n margin-left: #{$sp-4 + $sp-2};\n word-wrap: break-word;\n}\n\n.search-result-rel-url {\n display: block;\n margin-left: #{$sp-4 + $sp-2};\n overflow: hidden;\n color: $search-result-preview-color;\n text-overflow: ellipsis;\n white-space: nowrap;\n @include fs-1;\n}\n\n.search-result-previews {\n display: block;\n padding-top: $sp-2;\n padding-bottom: $sp-2;\n padding-left: $sp-4;\n margin-left: $sp-2;\n color: $search-result-preview-color;\n word-wrap: break-word;\n border-left: $border;\n border-left-color: $border-color;\n @include fs-2;\n\n @include mq(sm) {\n display: inline-block;\n width: 60%;\n padding-left: $sp-2;\n margin-left: 0;\n vertical-align: top;\n }\n}\n\n.search-result-preview + .search-result-preview {\n margin-top: $sp-1;\n}\n\n.search-result-highlight {\n font-weight: bold;\n}\n\n.search-no-result {\n padding: $sp-2 $sp-3;\n @include fs-3;\n}\n\n.search-button {\n position: fixed;\n right: $sp-4;\n bottom: $sp-4;\n display: flex;\n width: $sp-9;\n height: $sp-9;\n background-color: $search-background-color;\n border: 1px solid rgba($link-color, 0.3);\n border-radius: #{$sp-9 * 0.5};\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n align-items: center;\n justify-content: center;\n}\n\n.search-overlay {\n position: fixed;\n top: 0;\n left: 0;\n z-index: 1;\n width: 0;\n height: 0;\n background-color: rgba(0, 0, 0, 0.3);\n opacity: 0;\n transition:\n opacity ease $transition-duration,\n width 0s $transition-duration,\n height 0s $transition-duration;\n}\n\n.search-active {\n .search {\n position: fixed;\n top: 0;\n left: 0;\n width: 100%;\n height: 100%;\n padding: 0;\n }\n\n .search-input-wrap {\n height: $sp-10;\n border-radius: 0;\n\n @include mq(md) {\n width: $search-results-width;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n }\n }\n\n .search-input {\n background-color: $search-background-color;\n\n @include mq(md) {\n padding-left: 2.3rem;\n }\n }\n\n .search-label {\n @include mq(md) {\n padding-left: 0.6rem;\n }\n }\n\n .search-results {\n display: block;\n }\n\n .search-overlay {\n width: 100%;\n height: 100%;\n opacity: 1;\n transition:\n opacity ease $transition-duration,\n width 0s,\n height 0s;\n }\n\n @include mq(md) {\n .main {\n position: fixed;\n right: 0;\n left: 0;\n }\n }\n\n .main-header {\n padding-top: $sp-10;\n\n @include mq(md) {\n padding-top: 0;\n }\n }\n}\n","// Tables\n// stylelint-disable max-nesting-depth, selector-no-type, selector-max-type\n\n.table-wrapper {\n display: block;\n width: 100%;\n max-width: 100%;\n margin-bottom: $sp-5;\n overflow-x: auto;\n border-radius: $border-radius;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n}\n\ntable {\n display: table;\n min-width: 100%;\n border-collapse: separate;\n}\n\nth,\ntd {\n min-width: 7.5rem;\n padding: $sp-2 $sp-3;\n background-color: $table-background-color;\n border-bottom: $border rgba($border-color, 0.5);\n border-left: $border $border-color;\n\n @include fs-3;\n\n &:first-of-type {\n border-left: 0;\n }\n}\n\ntbody {\n tr {\n &:last-of-type {\n th,\n td {\n border-bottom: 0;\n }\n\n td {\n padding-bottom: $sp-3;\n }\n }\n }\n}\n\nthead {\n th {\n border-bottom: $border $border-color;\n }\n}\n","// Code and syntax highlighting\n// stylelint-disable selector-no-qualifying-type, declaration-block-semicolon-newline-after,declaration-block-single-line-max-declarations, selector-no-type, selector-max-type, scss/comment-no-empty\n\n// {% raw %}\n\n// This instruction applies to all queues not within 'pre' or 'figure', avoiding 'code' generated by the highlight.\n:not(pre, figure) {\n & > code {\n padding: 0.2em 0.15em;\n font-weight: 400;\n background-color: $code-background-color;\n border: $border $border-color;\n border-radius: $border-radius;\n }\n}\n\n// Avoid appearance of dark border around visited code links in Safari\na:visited code {\n border-color: $border-color;\n}\n\n// Content structure for highlighted code blocks using fences or Liquid\n//\n// ```[LANG]...```, no kramdown line_numbers:\n// div.[language-LANG.]highlighter-rouge > div.highlight > pre.highlight > code\n//\n// ```[LANG]...```, kramdown line_numbers = true:\n// div.[language-LANG.]highlighter-rouge > div.highlight > pre.highlight > code\n// > div.table-wrapper > table.rouge-table > tbody > tr\n// > td.rouge-gutter.gl > pre.lineno\n// | td.rouge-code > pre\n//\n// {% highlight LANG %}...{% endhighlight %}:\n// figure.highlight > pre > code.language-LANG\n//\n// {% highlight LANG linenos %}...{% endhighlight %}:\n// figure.highlight > pre > code.language-LANG\n// > div.table-wrapper > table.rouge-table > tbody > tr\n// > td.gutter.gl > pre.lineno\n// | td.code > pre\n//\n// ----...---- (AsciiDoc)\n// div.listingblock > div.content > pre.rouge.highlight\n//\n// fix_linenos removes the outermost pre when it encloses table.rouge-table\n//\n// See docs/index-test.md for some tests.\n//\n// No kramdown line_numbers: fences and Liquid highlighting look the same.\n// Kramdown line_numbers = true: fences have a wider gutter than with Liquid?\n\n// ```[LANG]...```\n// or in AsciiDoc:\n//\n// ----\n// ...\n// ----\n\n// the code may appear with 3 different types:\n// container \\ case: default case, code with line number, code with html rendering\n// top level: div.highlighter-rouge, figure.highlight, figure.highlight\n// second level: div.highlight, div.table-wrapper, pre.highlight\n// third level: pre.highlight, td.code, absent\n// last level: code, pre, code (optionality)\n// highlighter level: span, span, span\n// the spacing are only in the second level for case 1, 3 and in the third level for case 2\n// in AsciiDoc, there is a parent container that contains optionally a title and the content.\n\n// select top level container\ndiv.highlighter-rouge,\ndiv.listingblock > div.content,\nfigure.highlight {\n margin-top: 0;\n margin-bottom: $sp-3;\n background-color: $code-background-color;\n border-radius: $border-radius;\n box-shadow: none;\n -webkit-overflow-scrolling: touch;\n position: relative;\n padding: 0;\n\n // copy button (or other button)\n // the button appear only when there is a hover on the code or focus on button\n > button {\n width: $sp-3;\n opacity: 0;\n position: absolute;\n top: 0;\n right: 0;\n padding: $sp-3;\n border: none;\n background: none;\n color: $body-text-color;\n box-sizing: content-box;\n\n svg {\n fill: $body-text-color;\n }\n\n &:active {\n text-decoration: none;\n outline: none;\n opacity: 1;\n }\n\n &:focus {\n opacity: 1;\n outline: 2px solid $link-color;\n }\n }\n\n // the button can be seen by doing a simple hover in the code, there is no need to go over the location of the button\n &:hover {\n > button {\n cursor: copy;\n opacity: 1;\n }\n }\n}\n\n// setting the spacing and scrollbar on the second level for the first case\n// remove all space on the second and third level\n// this is a mixin to accommodate for the slightly different structures generated via Markdown vs AsciiDoc\n@mixin scroll-and-spacing($code-div, $pre-select) {\n #{$code-div} {\n overflow-x: auto;\n padding: $sp-3;\n margin: 0;\n border: 1px solid $body-text-color;\n border-radius: $border-radius;\n }\n\n #{$pre-select},\n code {\n padding: 0;\n margin: 0;\n border: 0;\n }\n}\n\n// for Markdown\ndiv.highlighter-rouge {\n @include scroll-and-spacing(\"div.highlight\", \"pre.highlight\");\n}\n\n// for AsciiDoc. we also need to fix the margins for its parent container.\ndiv.listingblock {\n margin-top: 0;\n margin-bottom: $sp-3;\n\n @include scroll-and-spacing(\"div.content\", \"div.content > pre\");\n}\n\n// {% highlight LANG %}...{% endhighlight %},\n// {% highlight LANG linenos %}...{% endhighlight %}:\n\n// setting the spacing and scrollbar on the second level for the thirt case\n// the css rule are apply only to the last code enviroment\n// setting the scroolbar\nfigure.highlight {\n pre,\n :not(pre) > code {\n overflow-x: auto;\n padding: $sp-3;\n margin: 0;\n border: 1px solid $body-text-color;\n border-radius: $border-radius;\n }\n}\n\n// ```[LANG]...```, kramdown line_numbers = true,\n// {% highlight LANG linenos %}...{% endhighlight %}:\n\n// setting the spacing and scrollbar on the thirt level for the second case\n.highlight .table-wrapper {\n padding: $sp-3 0;\n margin: 0;\n border: 0;\n box-shadow: none;\n\n td,\n pre {\n min-width: 0;\n padding: 0;\n background-color: $code-background-color;\n border: 0;\n\n @include fs-2;\n }\n\n td.gl {\n width: 1em;\n padding-right: $sp-3;\n padding-left: $sp-3;\n }\n\n pre {\n margin: 0;\n line-height: 2;\n }\n}\n\n// Code examples: html render of a code\n.code-example,\n.listingblock > .title {\n padding: $sp-3;\n margin-bottom: $sp-3;\n overflow: auto;\n border: 1px solid $border-color;\n border-radius: $border-radius;\n\n + .highlighter-rouge,\n + .sectionbody .listingblock,\n + .content,\n + figure.highlight {\n position: relative;\n margin-top: -$sp-4;\n border-right: 1px solid $border-color;\n border-bottom: 1px solid $border-color;\n border-left: 1px solid $border-color;\n border-top-left-radius: 0;\n border-top-right-radius: 0;\n }\n}\n\n// Mermaid diagram code blocks should be left unstyled.\ncode.language-mermaid {\n padding: 0;\n background-color: inherit;\n border: 0;\n}\n\n// Override OneDarkJekyll Colors for Code Blocks\n.highlight,\npre.highlight {\n background: $code-background-color; // Code Background\n // For Backwards Compatibility Before $code-linenumber-color was added\n @if variable-exists(code-linenumber-color) {\n color: $code-linenumber-color; // Code Line Numbers\n } @else {\n color: $body-text-color; // Code Line Numbers\n }\n}\n\n// Override OneDarkJekyll Colors for Code Blocks\n.highlight pre {\n background: $code-background-color; // Code Background\n}\n\n// {% endraw %}\n","// Utility classes for colors\n\n// Text colors\n\n.text-grey-dk-000 {\n color: $grey-dk-000 !important;\n}\n\n.text-grey-dk-100 {\n color: $grey-dk-100 !important;\n}\n\n.text-grey-dk-200 {\n color: $grey-dk-200 !important;\n}\n\n.text-grey-dk-250 {\n color: $grey-dk-250 !important;\n}\n\n.text-grey-dk-300 {\n color: $grey-dk-300 !important;\n}\n\n.text-grey-lt-000 {\n color: $grey-lt-000 !important;\n}\n\n.text-grey-lt-100 {\n color: $grey-lt-100 !important;\n}\n\n.text-grey-lt-200 {\n color: $grey-lt-200 !important;\n}\n\n.text-grey-lt-300 {\n color: $grey-lt-300 !important;\n}\n\n.text-blue-000 {\n color: $blue-000 !important;\n}\n\n.text-blue-100 {\n color: $blue-100 !important;\n}\n\n.text-blue-200 {\n color: $blue-200 !important;\n}\n\n.text-blue-300 {\n color: $blue-300 !important;\n}\n\n.text-green-000 {\n color: $green-000 !important;\n}\n\n.text-green-100 {\n color: $green-100 !important;\n}\n\n.text-green-200 {\n color: $green-200 !important;\n}\n\n.text-green-300 {\n color: $green-300 !important;\n}\n\n.text-purple-000 {\n color: $purple-000 !important;\n}\n\n.text-purple-100 {\n color: $purple-100 !important;\n}\n\n.text-purple-200 {\n color: $purple-200 !important;\n}\n\n.text-purple-300 {\n color: $purple-300 !important;\n}\n\n.text-yellow-000 {\n color: $yellow-000 !important;\n}\n\n.text-yellow-100 {\n color: $yellow-100 !important;\n}\n\n.text-yellow-200 {\n color: $yellow-200 !important;\n}\n\n.text-yellow-300 {\n color: $yellow-300 !important;\n}\n\n.text-red-000 {\n color: $red-000 !important;\n}\n\n.text-red-100 {\n color: $red-100 !important;\n}\n\n.text-red-200 {\n color: $red-200 !important;\n}\n\n.text-red-300 {\n color: $red-300 !important;\n}\n\n// Background colors\n\n.bg-grey-dk-000 {\n background-color: $grey-dk-000 !important;\n}\n\n.bg-grey-dk-100 {\n background-color: $grey-dk-100 !important;\n}\n\n.bg-grey-dk-200 {\n background-color: $grey-dk-200 !important;\n}\n\n.bg-grey-dk-250 {\n background-color: $grey-dk-250 !important;\n}\n\n.bg-grey-dk-300 {\n background-color: $grey-dk-300 !important;\n}\n\n.bg-grey-lt-000 {\n background-color: $grey-lt-000 !important;\n}\n\n.bg-grey-lt-100 {\n background-color: $grey-lt-100 !important;\n}\n\n.bg-grey-lt-200 {\n background-color: $grey-lt-200 !important;\n}\n\n.bg-grey-lt-300 {\n background-color: $grey-lt-300 !important;\n}\n\n.bg-blue-000 {\n background-color: $blue-000 !important;\n}\n\n.bg-blue-100 {\n background-color: $blue-100 !important;\n}\n\n.bg-blue-200 {\n background-color: $blue-200 !important;\n}\n\n.bg-blue-300 {\n background-color: $blue-300 !important;\n}\n\n.bg-green-000 {\n background-color: $green-000 !important;\n}\n\n.bg-green-100 {\n background-color: $green-100 !important;\n}\n\n.bg-green-200 {\n background-color: $green-200 !important;\n}\n\n.bg-green-300 {\n background-color: $green-300 !important;\n}\n\n.bg-purple-000 {\n background-color: $purple-000 !important;\n}\n\n.bg-purple-100 {\n background-color: $purple-100 !important;\n}\n\n.bg-purple-200 {\n background-color: $purple-200 !important;\n}\n\n.bg-purple-300 {\n background-color: $purple-300 !important;\n}\n\n.bg-yellow-000 {\n background-color: $yellow-000 !important;\n}\n\n.bg-yellow-100 {\n background-color: $yellow-100 !important;\n}\n\n.bg-yellow-200 {\n background-color: $yellow-200 !important;\n}\n\n.bg-yellow-300 {\n background-color: $yellow-300 !important;\n}\n\n.bg-red-000 {\n background-color: $red-000 !important;\n}\n\n.bg-red-100 {\n background-color: $red-100 !important;\n}\n\n.bg-red-200 {\n background-color: $red-200 !important;\n}\n\n.bg-red-300 {\n background-color: $red-300 !important;\n}\n","// Utility classes for layout\n\n// Display\n\n.d-block {\n display: block !important;\n}\n\n.d-flex {\n display: flex !important;\n}\n\n.d-inline {\n display: inline !important;\n}\n\n.d-inline-block {\n display: inline-block !important;\n}\n\n.d-none {\n display: none !important;\n}\n\n// Screenreader-only\n\n.sr-only {\n position: absolute;\n width: 1px;\n height: 1px;\n padding: 0;\n margin: -1px;\n overflow: hidden;\n clip: rect(0, 0, 0, 0);\n white-space: nowrap;\n border-width: 0;\n}\n\n@each $media-query in map-keys($media-queries) {\n @for $i from 1 through length($spacers) {\n @include mq($media-query) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .d-sm-block, .d-md-none, .d-lg-inline\n .d-#{$media-query}-block {\n display: block !important;\n }\n .d-#{$media-query}-flex {\n display: flex !important;\n }\n .d-#{$media-query}-inline {\n display: inline !important;\n }\n .d-#{$media-query}-inline-block {\n display: inline-block !important;\n }\n .d-#{$media-query}-none {\n display: none !important;\n }\n }\n }\n}\n\n// Horizontal alignment\n\n.float-left {\n float: left !important;\n}\n\n.float-right {\n float: right !important;\n}\n\n.flex-justify-start {\n justify-content: flex-start !important;\n}\n\n.flex-justify-end {\n justify-content: flex-end !important;\n}\n\n.flex-justify-between {\n justify-content: space-between !important;\n}\n\n.flex-justify-around {\n justify-content: space-around !important;\n}\n\n// Vertical alignment\n\n.v-align-baseline {\n vertical-align: baseline !important;\n}\n\n.v-align-bottom {\n vertical-align: bottom !important;\n}\n\n.v-align-middle {\n vertical-align: middle !important;\n}\n\n.v-align-text-bottom {\n vertical-align: text-bottom !important;\n}\n\n.v-align-text-top {\n vertical-align: text-top !important;\n}\n\n.v-align-top {\n vertical-align: top !important;\n}\n","// Utility classes for typography\n\n.fs-1 {\n @include fs-1;\n}\n\n.fs-2 {\n @include fs-2;\n}\n\n.fs-3 {\n @include fs-3;\n}\n\n.fs-4 {\n @include fs-4;\n}\n\n.fs-5 {\n @include fs-5;\n}\n\n.fs-6 {\n @include fs-6;\n}\n\n.fs-7 {\n @include fs-7;\n}\n\n.fs-8 {\n @include fs-8;\n}\n\n.fs-9 {\n @include fs-9;\n}\n\n.fs-10 {\n @include fs-10;\n}\n\n.fw-300 {\n font-weight: 300 !important;\n}\n\n.fw-400 {\n font-weight: 400 !important;\n}\n\n.fw-500 {\n font-weight: 500 !important;\n}\n\n.fw-700 {\n font-weight: 700 !important;\n}\n\n.lh-0 {\n line-height: 0 !important;\n}\n\n.lh-default {\n line-height: $body-line-height;\n}\n\n.lh-tight {\n line-height: $body-heading-line-height;\n}\n\n.ls-5 {\n letter-spacing: 0.05em !important;\n}\n\n.ls-10 {\n letter-spacing: 0.1em !important;\n}\n\n.ls-0 {\n letter-spacing: 0 !important;\n}\n\n.text-uppercase {\n text-transform: uppercase !important;\n}\n","// Utility classes for lists\n\n// stylelint-disable selector-max-type\n\n.list-style-none {\n padding: 0 !important;\n margin: 0 !important;\n list-style: none !important;\n\n li {\n &::before {\n display: none !important;\n }\n }\n}\n","// Utility classes for margins and padding\n\n// stylelint-disable block-opening-brace-space-after, block-opening-brace-space-before\n\n// Margin spacer utilities\n\n.mx-auto {\n margin-right: auto !important;\n margin-left: auto !important;\n}\n\n@for $i from 1 through length($spacers) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .m-0, .m-1, .m-2...\n .m-#{$scale} {\n margin: #{$size} !important;\n }\n .mt-#{$scale} {\n margin-top: #{$size} !important;\n }\n .mr-#{$scale} {\n margin-right: #{$size} !important;\n }\n .mb-#{$scale} {\n margin-bottom: #{$size} !important;\n }\n .ml-#{$scale} {\n margin-left: #{$size} !important;\n }\n\n .mx-#{$scale} {\n margin-right: #{$size} !important;\n margin-left: #{$size} !important;\n }\n\n .my-#{$scale} {\n margin-top: #{$size} !important;\n margin-bottom: #{$size} !important;\n }\n\n .mxn-#{$scale} {\n margin-right: -#{$size} !important;\n margin-left: -#{$size} !important;\n }\n .mx-#{$scale}-auto {\n margin-right: auto !important;\n margin-left: auto !important;\n }\n}\n\n@each $media-query in map-keys($media-queries) {\n @for $i from 1 through length($spacers) {\n @include mq($media-query) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .m-sm-0, .m-md-1, .m-lg-2...\n .m-#{$media-query}-#{$scale} {\n margin: #{$size} !important;\n }\n .mt-#{$media-query}-#{$scale} {\n margin-top: #{$size} !important;\n }\n .mr-#{$media-query}-#{$scale} {\n margin-right: #{$size} !important;\n }\n .mb-#{$media-query}-#{$scale} {\n margin-bottom: #{$size} !important;\n }\n .ml-#{$media-query}-#{$scale} {\n margin-left: #{$size} !important;\n }\n\n .mx-#{$media-query}-#{$scale} {\n margin-right: #{$size} !important;\n margin-left: #{$size} !important;\n }\n\n .my-#{$media-query}-#{$scale} {\n margin-top: #{$size} !important;\n margin-bottom: #{$size} !important;\n }\n\n .mxn-#{$media-query}-#{$scale} {\n margin-right: -#{$size} !important;\n margin-left: -#{$size} !important;\n }\n }\n }\n}\n\n// Padding spacer utilities\n\n@for $i from 1 through length($spacers) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .p-0, .p-1, .p-2...\n .p-#{$scale} {\n padding: #{$size} !important;\n }\n .pt-#{$scale} {\n padding-top: #{$size} !important;\n }\n .pr-#{$scale} {\n padding-right: #{$size} !important;\n }\n .pb-#{$scale} {\n padding-bottom: #{$size} !important;\n }\n .pl-#{$scale} {\n padding-left: #{$size} !important;\n }\n\n .px-#{$scale} {\n padding-right: #{$size} !important;\n padding-left: #{$size} !important;\n }\n\n .py-#{$scale} {\n padding-top: #{$size} !important;\n padding-bottom: #{$size} !important;\n }\n}\n\n@each $media-query in map-keys($media-queries) {\n @include mq($media-query) {\n @for $i from 1 through length($spacers) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .p-sm-0, .p-md-1, .p-lg-2...\n .p-#{$media-query}-#{$scale} {\n padding: #{$size} !important;\n }\n .pt-#{$media-query}-#{$scale} {\n padding-top: #{$size} !important;\n }\n .pr-#{$media-query}-#{$scale} {\n padding-right: #{$size} !important;\n }\n .pb-#{$media-query}-#{$scale} {\n padding-bottom: #{$size} !important;\n }\n .pl-#{$media-query}-#{$scale} {\n padding-left: #{$size} !important;\n }\n\n .px-#{$media-query}-#{$scale} {\n padding-right: #{$size} !important;\n padding-left: #{$size} !important;\n }\n\n .py-#{$media-query}-#{$scale} {\n padding-top: #{$size} !important;\n padding-bottom: #{$size} !important;\n }\n }\n }\n}\n","// stylelint-disable selector-max-specificity, selector-max-id, selector-max-type, selector-no-qualifying-type\n\n@media print {\n .site-footer,\n .site-button,\n #edit-this-page,\n #back-to-top,\n .site-nav,\n .main-header {\n display: none !important;\n }\n\n hr {\n margin-top: 1rem;\n margin-bottom: 1rem;\n }\n\n .side-bar {\n width: 100%;\n height: auto;\n border-right: 0 !important;\n }\n\n .site-header {\n border-bottom: 1px solid $border-color;\n }\n\n .site-title {\n font-size: 1rem !important;\n font-weight: 700 !important;\n }\n\n .text-small {\n font-size: 8pt !important;\n }\n\n pre.highlight {\n border: 1px solid $border-color;\n }\n\n .main {\n max-width: none;\n margin-left: 0;\n }\n}\n","// Skipnav\n// Skip to main content\n\na.skip-to-main {\n left: -999px;\n position: absolute;\n top: auto;\n width: 1px;\n height: 1px;\n overflow: hidden;\n z-index: -999;\n}\n\na.skip-to-main:focus,\na.skip-to-main:active {\n color: $link-color;\n background-color: $body-background-color;\n left: auto;\n top: auto;\n width: 30%;\n height: auto;\n overflow: auto;\n margin: 10px 35%;\n padding: 5px;\n border-radius: 15px;\n border: 4px solid $btn-primary-color;\n text-align: center;\n font-size: 1.2em;\n z-index: 999;\n}\n","\n@import \"./support/support\";\n@import \"./custom/setup\";\n@import \"./color_schemes/light\";\n\n@import \"./color_schemes/meshtastic\";\n\n@import \"./modules\";\ndiv.opaque {\n background-color: $body-background-color;\n}\n\np.tip, blockquote.tip {\n border: 1px $green-000 solid;\n border-left: $border-radius solid $green-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n \n &::before {\n color: $green-300;\n content: \"Tip\";\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n \n > .tip-title {\n color: $green-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\np.tip-title, blockquote.tip-title {\n border: 1px $green-000 solid;\n border-left: $border-radius solid $green-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n > p:first-child {\n margin-top: 0;\n margin-bottom: 0;\n color: $green-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\nblockquote.tip {\n margin-left: 0;\n margin-right: 0;\n\n > p:first-child {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\nblockquote.tip-title {\n margin-left: 0;\n margin-right: 0;\n\n > p:nth-child(2) {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\n\n\np.note, blockquote.note {\n border: 1px $blue-000 solid;\n border-left: $border-radius solid $blue-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n \n &::before {\n color: $blue-300;\n content: \"Note\";\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n \n > .note-title {\n color: $blue-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\np.note-title, blockquote.note-title {\n border: 1px $blue-000 solid;\n border-left: $border-radius solid $blue-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n > p:first-child {\n margin-top: 0;\n margin-bottom: 0;\n color: $blue-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\nblockquote.note {\n margin-left: 0;\n margin-right: 0;\n\n > p:first-child {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\nblockquote.note-title {\n margin-left: 0;\n margin-right: 0;\n\n > p:nth-child(2) {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\n\n\np.warning, blockquote.warning {\n border: 1px $yellow-000 solid;\n border-left: $border-radius solid $yellow-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n \n &::before {\n color: $yellow-300;\n content: \"Warning\";\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n \n > .warning-title {\n color: $yellow-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\np.warning-title, blockquote.warning-title {\n border: 1px $yellow-000 solid;\n border-left: $border-radius solid $yellow-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n > p:first-child {\n margin-top: 0;\n margin-bottom: 0;\n color: $yellow-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\nblockquote.warning {\n margin-left: 0;\n margin-right: 0;\n\n > p:first-child {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\nblockquote.warning-title {\n margin-left: 0;\n margin-right: 0;\n\n > p:nth-child(2) {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\n\n@import \"./custom/custom\";\n\n\n"],"file":"just-the-docs-meshtastic.css"} \ No newline at end of file +{"version":3,"sourceRoot":"","sources":["../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/vendor/accessible-pygments/github-light.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/vendor/normalize.scss/normalize.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/base.scss","../../_sass/color_schemes/meshtastic.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/support/mixins/_typography.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/support/mixins/_layout.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/support/_variables.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/layout.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/content.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/navigation.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/typography.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/labels.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/buttons.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/color_schemes/light.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/support/mixins/_buttons.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/search.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/tables.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/code.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/utilities/_colors.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/utilities/_layout.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/utilities/_typography.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/utilities/_lists.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/utilities/_spacing.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/print.scss","../../../../../../../../../../tmp/jekyll-remote-theme-20260922-3154-78bjla/_sass/skiptomain.scss","just-the-docs-meshtastic.scss"],"names":[],"mappings":";AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAUA;EAAkB;;;AAClB;EAAgB;EAAiB;AACjC;EAAkB;EAAiB;AACnC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAkB;EAAiB;AACnC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAqB;AACtC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAoB;AACrC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAgB;EAAiB;AACjC;EAAgB;EAAiB;AACjC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAgB;EAAiB;AACjC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AAClC;EAAiB;EAAiB;AChFlC;AAEA;AAAA;AAGA;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAAA;AAKA;EACE;EACA;EACA;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;EACA;;;AAGF;AAAA;AAAA;AAIA;AAAA;EAEE;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;AAAA;EAGE;EACA;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;EAEE;EACA;EACA;EACA;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAAA;AAKA;AAAA;AAAA;AAAA;AAAA;EAKE;EACA;EACA;EACA;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;AAEE;EACA;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;AAEE;EACA;;;AAGF;AAAA;AAAA;AAIA;AAAA;AAAA;AAAA;EAIE;;;AAGF;AAAA;AAAA;AAIA;AAAA;AAAA;AAAA;EAIE;EACA;;;AAGF;AAAA;AAAA;AAIA;AAAA;AAAA;AAAA;EAIE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAOA;EACE;EACA;EACA;EACA;EACA;EACA;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;AAAA;EAEE;EACA;;;AAGF;AAAA;AAAA;AAIA;AAAA;EAEE;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAAA;AAKA;EACE;EACA;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAGA;AAAA;AAAA;AAIA;EACE;;;AAGF;AAAA;AAAA;AAIA;EACE;;;AC1VF;EACE,cCGa;;;ADAf;EACE;;;AAGF;EACE;;AEmBA;EACE;;AClBA;EHHJ;IEyBI;;;;AFnBJ;EACE,aIfiB;EJgBjB;EACA,aIbiB;EJcjB,OCTgB;EDUhB,kBCZsB;EDatB;;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAYE;;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAOE;EACA;EACA;EACA,aI1CyB;EJ2CzB,OCvCmB;;;AD0CrB;EACE;EACA;;;AAGF;EACE,OC7CW;ED8CX;;;AAGF;EACE;EACA,uBCvCa;EDwCb;;AAEA;EACE;;;AAIJ;EACE,aIvEiB;EJwEjB;EACA,aIvEiB;;;AJ0EnB;AAAA;EAEE;;;AAGF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;EACA;EACA,kBCvEa;EDwEb;;;AAIF;EACE;EAGA;EACA;EACA;EACA;;;AK7GF;EACE;EACA;EACA;EACA,kBJKc;;AEGZ;EEZJ;IAOI;IACA;IACA,ODwFW;ICvFX;IACA;IACA;;;AFAA;EEZJ;IAgBI;IACA,WD+EQ;;;ADpFR;EEQF;IAEI,aD2ES;;;ADrFX;EEQF;IAQI;;;AAOF;EACE;EACA,kBJ5BU;;AEGZ;EEuBA;IAKI;IACA,kBJjCgB;;;AIoClB;EACE;;AFjCJ;EEgCE;IAII;;;;AAOV;EACE;;AF5CE;EE2CJ;IAII;IACA,WDyCY;;;;ACrChB;EACE,aDaK;ECZL,gBDYK;EDvDL,eCuDK;EDtDL,cCsDK;;ADlEH;EEoDJ;IFrCI,eCqDG;IDpDH,cCoDG;;;ADpEH;EEoDJ;IAOI,aDSG;ICRH,gBDQG;;;;ACJP;EACE;EACA;;AFlEE;EEgEJ;IAKI;IACA;IACA,QDmBY;;;;ACfhB;AAAA;AAAA;EAGE;;AF9EE;EE2EJ;AAAA;AAAA;IAMI,ODGQ;;;;ACCZ;EACE;;AAEA;EACE;;AFzFA;EEqFJ;IAQI;IACA,aDxBG;ICyBH,gBD7BG;IC8BH;IACA;;;;AAIJ;EACE;EACA,YDbc;ECcd;;AFxGE;EEqGJ;IAMI,QDjBY;ICkBZ,YDlBY;ICmBZ;;;;AAIJ;EACE;EACA;EACA;EACA;EACA,aDrDK;ECsDL,gBDtDK;ECuDL,OJzHmB;EEYnB,eCuDK;EDtDL,cCsDK;;ADlEH;EEiHJ;IFlGI,eCqDG;IDpDH,cCoDG;;;AF/BL;EACE;;ACtCA;EEiHJ;IHvEI;IACA,aEhDuB;;;ADKvB;EEiHJ;IAcI,aD/DG;ICgEH,gBDhEG;;;;AC+EP;EACE;EACA;EACA,SDhFK;ECiFL;;;AFnJE;EEuJF;IACE;;;AAIJ;EACE;;;AAQF;EACE;;;AAOF;EACE;EACA;EACA;EACA,aD/GK;ECgHL,gBDhHK;EDvDL,eCuDK;EDtDL,cCsDK;;ADlEH;EE6KJ;IF9JI,eCqDG;IDpDH,cCoDG;;;AFvEL;EACE;;ACEA;EE6KJ;IH3KI;;;ACFA;EE6KJ;IAYI;IACA;;;;AAIJ;EACE,OD5HK;EC6HL,QD7HK;EC8HL,OJ/LW;;;AKXb;EACE,aFEoB;;AEApB;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAOE;;AAGF;EACE;EACA;;AAGF;AAAA;EAEE;;AAIA;EACE,YF+CC;;AE3CL;EACE;EACA;;AAEA;EACE;;AAEA;EACE;EACA;EACA;EACA,OFfM;EEgBN;EACA;;AJ1BN;EACE;;ACRA;EG2BE;IJfF;;;ACZA;EG2BE;IAUI;;;AAIJ;EACE;;AAGE;EACE;EACA;;AAOV;EACE;;AAGE;EACE;EACA;EACA,OF7CM;EE8CN;;AAMJ;EACE;;AAIJ;EACE;EACA;;AAKF;EACE;;AAGF;EACE;;AAGF;EACE;EACA;;AAGF;AAAA;EAEE;;AAGF;EACE;EACA;EACA;;AAEA;EACE;;AAIJ;EACE;EACA;EACA;;AAmBE;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EACE;;AASF;AAAA;AAAA;AAAA;AAAA;AAAA;EAEE;;AAKN;EACE;EACA;EACA,OFnFG;EEoFH;EACA,eFzFG;EE0FH,cF1FG;EE2FH;;AH1JA;EGmJF;IAUI;IACA;;;AAGF;EACE;EACA;EACA;EACA,OLnKO;EKoKP;;AAYF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EACE;;AAIJ;EACE;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAOE;EACA;EACA;;AAEA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAKE;;AAGF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EACE;;AAIJ;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAWE,YF9JG;;;AG3EP;EACE;EACA;EACA;EACA;;AAEA;EACE;EACA;;ALoBF;EACE;;AClBA;EILF;IL2BE;;;ACtBA;EDOF;IACE;;;ACRA;EILF;ILiBE;;;AKPA;EACE;EACA,YH+DC;EG9DD,aHuDC;EGtDD,gBHsDC;EGrDD;EAEE,eH0DD;EGzDC,cHqDD;;ADlEH;EIKA;IAeI,YHgDD;IG/CC;IAEE,eH6CH;IG5CG,cH4CH;;;AGrCD;EACE,OHkCD;EGjCC,QHiCD;EGhCC;;AAGF;EACE;EACA;;AAGF;EAEE;EACA;;AASJ;EACE;EAEE;EAGF,OHUC;EGTD,QHSC;EGRD;EACA,ON7DO;;AEFT;EIsDA;IAYI,OHED;IGDC,QHCD;IGAC;;;AAGF;EACE;;AAQA;EACE;;AAKN;EACE;EACA,cHvBC;EGwBD;;AAEA;EACE;;AAEA;EACE,ONzFa;;AM4Ff;EACE,ON7Fa;;AMmGjB;EAEI;;AAMJ;EACE;;;AAMR;EACE;EACA;EACA;EACA;EACA;;ALhIA;EACE;;ACEA;EIwHJ;ILtHI;;;ACFA;EIwHJ;IASI;IACA,YHhEG;IGiEH;;EAEA;IACE;;;;AAMJ;EACE;;AAEA;EACE;;AAGE;EACE,ONlJG;;AMqJL;EACE,ONtJG;;;AM+Jb;EACE;EACA;;ALtKA;EACE;;ACEA;EIiKJ;IL/JI;;;AKoKF;EACE;EACA;EACA;EACA;EACA;;AAGF;EACE;EACA;EACA;EACA;;AJlLA;EIiKJ;IAqBI,eHpHG;;;;ADlEH;EI4LJ;IAEI;;;;AAIJ;EACE;EACA,eHnIK;EGoIL;;;AAGF;EACE;;AL5MA;EACE;;ACEA;EIwMJ;ILtMI;;;AK0MF;EACE;;AAGF;EACE;EACA,cHlJG;EGmJH,aHnJG;EGoJH,OHpMU;EGqMV;;AAIA;EACE;;;ACrON;AAAA;EAEE;;ANoEA;AAAA;EACE;EACA,aElEuB;;ADKvB;EKXJ;AAAA;IN4EI;;;;AA5BF;AAAA;AAAA;EACE;;ACtCA;EKJJ;AAAA;AAAA;IN8CI;IACA,aEhDuB;;;;AFgCzB;AAAA;EACE;;AC5BA;EKEJ;AAAA;IN8BI;;;;AMzBJ;AAAA;EAEE;EACA;EACA;;ANdA;AAAA;EACE;;ACEA;EKOJ;AAAA;INLI;;;;AMcJ;EACE;;;ANVA;AAAA;EACE;;ACRA;EKoBJ;AAAA;INRI;;;;AAfF;AAAA;EACE;;ACEA;EKyBJ;AAAA;INvBI;;;;AALF;EACE;;ACEA;EK8BJ;IN5BI;;;;AMgCJ;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;ACvDF;AAAA;EAEE;EACA;EACA,cLoEK;EKnEL,aLmEK;EKlEL,OLiBM;EKhBN;EACA;EACA,kBL6BS;EK5BT;;APLA;AAAA;EACE;;ACEA;EMRJ;AAAA;IPUI;;;;AOKJ;EACE,kBL4BU;;;AKzBZ;EACE,kBLcW;;;AKXb;EACE,kBL4BQ;;;AKzBV;EACE,OLFY;EKGZ,kBLkBW;;;AMlDb;EACE;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA,OTIW;ESHX;EACA;EACA;EACA,kBCTkB;EDUlB;EACA,eNyEc;EMxEd,YACE;EAEF;;AAEA;EACE;EACA;EACA;;AAGF;EAEE;;AAGF;EAEE;;AAGF;EAIE;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;AAKA;EAEE;EACA;EACA;EACA;EACA;;;AAKN;EACE,OT1DW;ES2DX;EACA;;AAEA;EAIE;EACA;EACA;EACA;;AAGF;EACE;EACA;EACA,YACE;;AAIJ;EAEE;;;AAIJ;EEnGE,OR0BM;EQzBN;EACA;EACA,YACE;;AAGF;EAEE,ORiBI;EQhBJ;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;;AFgFJ;EEvGE,OR0BM;EQzBN;EACA;EACA,YACE;;AAGF;EAEE,ORiBI;EQhBJ;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;;AFoFJ;EE3GE,OR0BM;EQzBN;EACA;EACA,YACE;;AAGF;EAEE,ORiBI;EQhBJ;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;;AFwFJ;EE/GE,OR0BM;EQzBN;EACA;EACA,YACE;;AAGF;EAEE,ORiBI;EQhBJ;EACA;;AAGF;EAGE;EACA;EACA;;AAGF;EACE;;;AF4FJ;EACE;EACA;EACA;EACA;EACA;EACA;EACA;;;AG3HF;EACE;EACA;EACA;EACA,QTgFM;ES/EN,STuEK;EStEL;;AVME;EUZJ;IASI;IACA;IACA;IACA;IACA;;;;AAIJ;EACE;EACA;EACA,QT8DK;ES7DL;EACA,eTmEc;ESlEd,YACE;EAEF;;AVdE;EUKJ;IAYI;IACA;IACA,WTwEmB;ISvEnB;IACA;IACA;IACA;;;;AAIJ;EACE;EACA;EACA;EACA;EACA;EACA,OZnCgB;EYoChB,kBZVwB;EYWxB;EACA;EACA;EACA;EACA;;AVvCE;EU2BJ;IAeI;IACA;IACA,kBZhDoB;IYiDpB;;;AAGF;EACE;EACA;;AAEA;EACE,OZnDO;;;AYwDb;EACE;EACA;EACA;EACA,cTIK;;ADlEH;EU0DJ;IAOI,cTGG;ISFH;;;AAGF;EACE;EACA;EACA;EACA,OTzDU;;;AS6Dd;EACE;EACA;EACA;EACA;EACA;EACA;EACA,kBZ5DwB;EY6DxB,4BTRc;ESSd,2BTTc;ESUd,YACE;;AVxFA;EU6EJ;IAeI;IACA,OTFmB;ISGnB;;;;AAIJ;EACE;EACA,eTrCK;ESsCL;;AXpFA;EACE;;AClBA;EUkGJ;IX5EI;;;ACtBA;EDOF;IACE;;;ACRA;EUkGJ;IXtFI;;;;AWiGJ;EACE;EACA;;;AAGF;EACE;EACA;;AAEA;EAEE,kBZnGa;;;AYuGjB;EACE;EACA,aT9DK;ES+DL,gBT/DK;;ADhEH;EU4HJ;IAMI;IACA;IACA,eTpEG;ISqEH;;;;AAIJ;EACE;EACA;EACA;;AAEA;EACE;;AXxIF;EACE;;ACRA;EU8IF;IXlIE;;;ACZA;EDHF;IACE;;;ACEA;EU8IF;IX5IE;;;AWqJF;EACE,OTtFG;ESuFH,QTvFG;ESwFH,cT1FG;ES2FH,OZzJS;EY0JT;;AAGF;EACE;;;AAIJ;EACE;EACA;;;AAGF;EACE;EACA;EACA;EACA,OZtK4B;EYuK5B;EACA;;AX5LA;EACE;;ACYA;EUyKJ;IXjLI;;;;AW2LJ;EACE;EACA,aTrHK;ESsHL,gBTtHK;ESuHL,cTrHK;ESsHL,aTxHK;ESyHL,OZlL4B;EYmL5B;EACA,aT/GO;ESgHP,mBZ9Ka;;ACjBb;EACE;;ACEA;EUmLJ;IXjLI;;;ACFA;EUmLJ;IAaI;IACA;IACA,cTlIG;ISmIH;IACA;;;;AAIJ;EACE,YT1IK;;;AS6IP;EACE;;;AAGF;EACE;;AX1MA;EACE;;ACRA;EUgNJ;IXpMI;;;;AWyMJ;EACE;EACA,OTrJK;ESsJL,QTtJK;ESuJL;EACA,OTnJK;ESoJL,QTpJK;ESqJL,kBZpMwB;EYqMxB;EACA;EACA,YACE;EAEF;EACA;;;AAGF;EACE;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA,YACE;;;AAMF;EACE;EACA;EACA;EACA;EACA;EACA;;AAGF;EACE,QTxLI;ESyLJ;;AVjQA;EU+PF;IAKI,OTzKiB;IS0KjB,YACE;;;AAKN;EACE,kBZpPsB;;AExBtB;EU2QF;IAII;;;AV/QF;EUmRF;IAEI;;;AAIJ;EACE;;AAGF;EACE;EACA;EACA;EACA,YACE;;AVlSF;EUwSA;IACE;IACA;IACA;;;AAIJ;EACE,aTxOI;;ADxEJ;EU+SF;IAII;;;;AC9TN;EACE;EACA;EACA;EACA,eV0EK;EUzEL;EACA,eVkFc;EUjFd,YACE;;;AAIJ;EACE;EACA;EACA;;;AAGF;AAAA;EAEE;EACA;EACA,kBbIuB;EaHvB;EACA;;AZNA;AAAA;EACE;;ACRA;EWOJ;AAAA;IZKI;;;AYKF;AAAA;EACE;;;AAOE;AAAA;EAEE;;AAGF;EACE,gBVkCD;;;AU3BL;EACE;;;AC9CF;EACE;EACA;EACA,kBdcoB;EcbpB;EACA,eX+EY;;;AW1EhB;EACE,cdUa;;;AcyCf;AAAA;AAAA;EAGE;EACA,eXMK;EWLL,kBdlDsB;EcmDtB,eXgBc;EWfd;EACA;EACA;EACA;;AAIA;AAAA;AAAA;EACE,OXLG;EWMH;EACA;EACA;EACA;EACA,SXVG;EWWH;EACA;EACA,OdhFc;EciFd;;AAEA;AAAA;AAAA;EACE,MdpFY;;AcuFd;AAAA;AAAA;EACE;EACA;EACA;;AAGF;AAAA;AAAA;EACE;EACA;;AAMF;AAAA;AAAA;EACE;EACA;;;AASJ;EACE;EACA,SX/CG;EWgDH;EACA;EACA,eXtCY;;AWyCd;AAAA;EAEE;EACA;EACA;;;AAUJ;EACE;EACA,eXrEK;;AW6CL;EACE;EACA,SX/CG;EWgDH;EACA;EACA,eXtCY;;AWyCd;AAAA;EAEE;EACA;EACA;;;AAwBF;AAAA;EAEE;EACA,SXpFG;EWqFH;EACA;EACA,eX3EY;;;AWmFhB;EACE;EACA;EACA;EACA;;AAEA;AAAA;EAEE;EACA;EACA,kBdhKoB;EciKpB;;Ab9KF;AAAA;EACE;;ACEA;EYsKF;AAAA;IbpKE;;;Aa8KF;EACE;EACA,eXjHG;EWkHH,cXlHG;;AWqHL;EACE;EACA;;;AAKJ;AAAA;EAEE,SX9HK;EW+HL,eX/HK;EWgIL;EACA;EACA,eXtHc;;AWwHd;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;EAIE;EACA;EACA;EACA;EACA;EACA;EACA;;;AAKJ;EACE;EACA;EACA;;;AAIF;AAAA;EAEE,YdnNsB;EcsNpB,OdrNoB;;;Ac4NxB;EACE,Yd9NsB;;;AepBxB;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAKF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;ACvOF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAKF;EACE;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;;;AdrBE;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;Ad5CJ;Ec+BE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;;AAQR;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAKF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AfhHA;EACE;;ACYA;EeZJ;IhBII;;;;AAKF;EACE;;ACEA;EeRJ;IhBUI;;;;AAKF;EACE;;ACRA;EeJJ;IhBgBI;;;;AAKF;EACE;;AClBA;EeAJ;IhBsBI;;;;AAKF;EACE;;AC5BA;EeIJ;IhB4BI;;;;AAKF;EACE;;ACtCA;EeQJ;IhBkCI;IACA,aEhDuB;;;;AFqDzB;EACE;EACA,aEvDuB;;ADKvB;EeYJ;IhB0CI;;;;AAKF;EACE;EACA,aElEuB;;ADKvB;EegBJ;IhBiDI;;;;AAKF;EACE;EACA,aE7EuB;;ADKvB;EeoBJ;IhBwDI;;;;AAKF;EACE;EACA,aExFuB;;ADKvB;EewBJ;IhB+DI;;;;AgB3DJ;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE,adxDiB;;;Ac2DnB;EACE,ad1DyB;;;Ac6D3B;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AAGF;EACE;;;AC/EF;EACE;EACA;EACA;;AAGE;EACE;;;ACLN;EACE;EACA;;;AAQA;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AAhCF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAEF;EACE;EACA;;;AjBlCA;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjBzEJ;EiB6CE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AAaN;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AAvBF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAEF;EACE;;;AAGF;EACE;EACA;;;AAGF;EACE;EACA;;;AjB7GA;EiBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjB/IJ;EiBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjB/IJ;EiBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjB/IJ;EiBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AjB/IJ;EiBwHE;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;EAvBF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAEF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;IACA;;;AC3JR;EACE;AAAA;AAAA;AAAA;AAAA;AAAA;IAME;;EAGF;IACE;IACA;;EAGF;IACE;IACA;IACA;;EAGF;IACE;;EAGF;IACE;IACA;;EAGF;IACE;;EAGF;IACE;;EAGF;IACE;IACA;;;ACvCJ;EACE;EACA;EACA;EACA;EACA;EACA;EACA;;;AAGF;AAAA;EAEE,OrBCW;EqBAX,kBrBNsB;EqBOtB;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;;;ACpBF;EACE,kBtBCsB;;;AsBExB;EACI;EACA;EACA,enB4EY;EmB3EZ;EACA;;AAEA;EACI,OnB8BI;EmB7BJ;EACA;EACA;EACA;EACA;EACA;;AAGJ;EACE,OnBoBM;EmBnBN;EACA;EACA;EACA;EACA;;;AAIN;EACI;EACA;EACA,enBiDY;EmBhDZ;EACA;;AACA;EACE;EACA;EACA,OnBEM;EmBDN;EACA;EACA;EACA;EACA;;;AAIN;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAIJ;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAMJ;EACI;EACA;EACA,enBGY;EmBFZ;EACA;;AAEA;EACI,OnB/CG;EmBgDH;EACA;EACA;EACA;EACA;EACA;;AAGJ;EACE,OnBzDK;EmB0DL;EACA;EACA;EACA;EACA;;;AAIN;EACI;EACA;EACA,enBxBY;EmByBZ;EACA;;AACA;EACE;EACA;EACA,OnB3EK;EmB4EL;EACA;EACA;EACA;EACA;;;AAIN;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAIJ;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAMJ;EACI;EACA;EACA,enBtEY;EmBuEZ;EACA;;AAEA;EACI,OnBhHK;EmBiHL;EACA;EACA;EACA;EACA;EACA;;AAGJ;EACE,OnB1HO;EmB2HP;EACA;EACA;EACA;EACA;;;AAIN;EACI;EACA;EACA,enBjGY;EmBkGZ;EACA;;AACA;EACE;EACA;EACA,OnB5IO;EmB6IP;EACA;EACA;EACA;EACA;;;AAIN;EACE;EACA;;AAEA;EACE;;AAGF;EACE;;;AAIJ;EACE;EACA;;AAEA;EACE;;AAGF;EACE","sourcesContent":["/*\ngenerated by accessible-pygments \nCopyright (c) 2022, Quansight Labs\nLicensed under the BSD license, see LICENSE for details.\n--\ngenerated by Pygments \nCopyright 2006-2025 by the Pygments team.\nLicensed under the BSD license, see LICENSE for details.\n*/\n\n.highlight .hll { background-color: #0969da4a }\n.highlight .c { color: #6E7781 } /* Comment */\n.highlight .err { color: #CF222E } /* Error */\n.highlight .k { color: #CF222E } /* Keyword */\n.highlight .l { color: #953800 } /* Literal */\n.highlight .n { color: #8250DF } /* Name */\n.highlight .o { color: #116329 } /* Operator */\n.highlight .p { color: #24292F } /* Punctuation */\n.highlight .ch { color: #6E7781 } /* Comment.Hashbang */\n.highlight .cm { color: #6E7781 } /* Comment.Multiline */\n.highlight .cp { color: #6E7781 } /* Comment.Preproc */\n.highlight .cpf { color: #6E7781 } /* Comment.PreprocFile */\n.highlight .c1 { color: #6E7781 } /* Comment.Single */\n.highlight .cs { color: #6E7781 } /* Comment.Special */\n.highlight .gd { color: #0550AE } /* Generic.Deleted */\n.highlight .ge { font-style: italic } /* Generic.Emph */\n.highlight .gr { color: #CF222E } /* Generic.Error */\n.highlight .gh { color: #0550AE } /* Generic.Heading */\n.highlight .gs { font-weight: bold } /* Generic.Strong */\n.highlight .gu { color: #0550AE } /* Generic.Subheading */\n.highlight .kc { color: #0550AE } /* Keyword.Constant */\n.highlight .kd { color: #CF222E } /* Keyword.Declaration */\n.highlight .kn { color: #CF222E } /* Keyword.Namespace */\n.highlight .kp { color: #CF222E } /* Keyword.Pseudo */\n.highlight .kr { color: #CF222E } /* Keyword.Reserved */\n.highlight .kt { color: #CF222E } /* Keyword.Type */\n.highlight .ld { color: #953800 } /* Literal.Date */\n.highlight .m { color: #953800 } /* Literal.Number */\n.highlight .s { color: #0550AE } /* Literal.String */\n.highlight .na { color: #953800 } /* Name.Attribute */\n.highlight .nb { color: #953800 } /* Name.Builtin */\n.highlight .nc { color: #0550AE } /* Name.Class */\n.highlight .no { color: #0550AE } /* Name.Constant */\n.highlight .nd { color: #953800 } /* Name.Decorator */\n.highlight .ni { color: #116329 } /* Name.Entity */\n.highlight .ne { color: #8250DF } /* Name.Exception */\n.highlight .nf { color: #0550AE } /* Name.Function */\n.highlight .nl { color: #953800 } /* Name.Label */\n.highlight .nn { color: #24292F } /* Name.Namespace */\n.highlight .nx { color: #8250DF } /* Name.Other */\n.highlight .py { color: #0550AE } /* Name.Property */\n.highlight .nt { color: #116329 } /* Name.Tag */\n.highlight .nv { color: #953800 } /* Name.Variable */\n.highlight .ow { color: #8250DF } /* Operator.Word */\n.highlight .pm { color: #24292F } /* Punctuation.Marker */\n.highlight .w { color: #24292F } /* Text.Whitespace */\n.highlight .mb { color: #953800 } /* Literal.Number.Bin */\n.highlight .mf { color: #953800 } /* Literal.Number.Float */\n.highlight .mh { color: #953800 } /* Literal.Number.Hex */\n.highlight .mi { color: #953800 } /* Literal.Number.Integer */\n.highlight .mo { color: #953800 } /* Literal.Number.Oct */\n.highlight .sa { color: #0550AE } /* Literal.String.Affix */\n.highlight .sb { color: #0550AE } /* Literal.String.Backtick */\n.highlight .sc { color: #0550AE } /* Literal.String.Char */\n.highlight .dl { color: #0550AE } /* Literal.String.Delimiter */\n.highlight .sd { color: #0550AE } /* Literal.String.Doc */\n.highlight .s2 { color: #0550AE } /* Literal.String.Double */\n.highlight .se { color: #0550AE } /* Literal.String.Escape */\n.highlight .sh { color: #0550AE } /* Literal.String.Heredoc */\n.highlight .si { color: #0550AE } /* Literal.String.Interpol */\n.highlight .sx { color: #0550AE } /* Literal.String.Other */\n.highlight .sr { color: #0550AE } /* Literal.String.Regex */\n.highlight .s1 { color: #0550AE } /* Literal.String.Single */\n.highlight .ss { color: #0550AE } /* Literal.String.Symbol */\n.highlight .bp { color: #953800 } /* Name.Builtin.Pseudo */\n.highlight .fm { color: #0550AE } /* Name.Function.Magic */\n.highlight .vc { color: #953800 } /* Name.Variable.Class */\n.highlight .vg { color: #953800 } /* Name.Variable.Global */\n.highlight .vi { color: #953800 } /* Name.Variable.Instance */\n.highlight .vm { color: #953800 } /* Name.Variable.Magic */\n.highlight .il { color: #953800 } /* Literal.Number.Integer.Long */\n","/*! normalize.css v8.0.1 | MIT License | github.com/necolas/normalize.css */\n\n/* Document\n ========================================================================== */\n\n/**\n * 1. Correct the line height in all browsers.\n * 2. Prevent adjustments of font size after orientation changes in iOS.\n */\n\nhtml {\n line-height: 1.15; /* 1 */\n text-size-adjust: 100%; /* 2 */\n}\n\n/* Sections\n ========================================================================== */\n\n/**\n * Remove the margin in all browsers.\n */\n\nbody {\n margin: 0;\n}\n\n/**\n * Render the `main` element consistently in IE.\n */\n\nmain {\n display: block;\n}\n\n/**\n * Correct the font size and margin on `h1` elements within `section` and\n * `article` contexts in Chrome, Firefox, and Safari.\n */\n\nh1 {\n font-size: 2em;\n margin: 0.67em 0;\n}\n\n/* Grouping content\n ========================================================================== */\n\n/**\n * 1. Add the correct box sizing in Firefox.\n * 2. Show the overflow in Edge and IE.\n */\n\nhr {\n box-sizing: content-box; /* 1 */\n height: 0; /* 1 */\n overflow: visible; /* 2 */\n}\n\n/**\n * 1. Correct the inheritance and scaling of font size in all browsers.\n * 2. Correct the odd `em` font sizing in all browsers.\n */\n\npre {\n font-family: monospace; /* 1 */\n font-size: 1em; /* 2 */\n}\n\n/* Text-level semantics\n ========================================================================== */\n\n/**\n * Remove the gray background on active links in IE 10.\n */\n\na {\n background-color: transparent;\n}\n\n/**\n * 1. Remove the bottom border in Chrome 57-\n * 2. Add the correct text decoration in Chrome, Edge, IE, Opera, and Safari.\n */\n\nabbr[title] {\n border-bottom: none; /* 1 */\n text-decoration: underline; /* 2 */\n text-decoration: underline dotted; /* 2 */\n}\n\n/**\n * Add the correct font weight in Chrome, Edge, and Safari.\n */\n\nb,\nstrong {\n font-weight: bolder;\n}\n\n/**\n * 1. Correct the inheritance and scaling of font size in all browsers.\n * 2. Correct the odd `em` font sizing in all browsers.\n */\n\ncode,\nkbd,\nsamp {\n font-family: monospace; /* 1 */\n font-size: 1em; /* 2 */\n}\n\n/**\n * Add the correct font size in all browsers.\n */\n\nsmall {\n font-size: 80%;\n}\n\n/**\n * Prevent `sub` and `sup` elements from affecting the line height in\n * all browsers.\n */\n\nsub,\nsup {\n font-size: 75%;\n line-height: 0;\n position: relative;\n vertical-align: baseline;\n}\n\nsub {\n bottom: -0.25em;\n}\n\nsup {\n top: -0.5em;\n}\n\n/* Embedded content\n ========================================================================== */\n\n/**\n * Remove the border on images inside links in IE 10.\n */\n\nimg {\n border-style: none;\n}\n\n/* Forms\n ========================================================================== */\n\n/**\n * 1. Change the font styles in all browsers.\n * 2. Remove the margin in Firefox and Safari.\n */\n\nbutton,\ninput,\noptgroup,\nselect,\ntextarea {\n font-family: inherit; /* 1 */\n font-size: 100%; /* 1 */\n line-height: 1.15; /* 1 */\n margin: 0; /* 2 */\n}\n\n/**\n * Show the overflow in IE.\n * 1. Show the overflow in Edge.\n */\n\nbutton,\ninput {\n /* 1 */\n overflow: visible;\n}\n\n/**\n * Remove the inheritance of text transform in Edge, Firefox, and IE.\n * 1. Remove the inheritance of text transform in Firefox.\n */\n\nbutton,\nselect {\n /* 1 */\n text-transform: none;\n}\n\n/**\n * Correct the inability to style clickable types in iOS and Safari.\n */\n\nbutton,\n[type=\"button\"],\n[type=\"reset\"],\n[type=\"submit\"] {\n appearance: button;\n}\n\n/**\n * Remove the inner border and padding in Firefox.\n */\n\nbutton::-moz-focus-inner,\n[type=\"button\"]::-moz-focus-inner,\n[type=\"reset\"]::-moz-focus-inner,\n[type=\"submit\"]::-moz-focus-inner {\n border-style: none;\n padding: 0;\n}\n\n/**\n * Restore the focus styles unset by the previous rule.\n */\n\nbutton:-moz-focusring,\n[type=\"button\"]:-moz-focusring,\n[type=\"reset\"]:-moz-focusring,\n[type=\"submit\"]:-moz-focusring {\n outline: 1px dotted ButtonText;\n}\n\n/**\n * Correct the padding in Firefox.\n */\n\nfieldset {\n padding: 0.35em 0.75em 0.625em;\n}\n\n/**\n * 1. Correct the text wrapping in Edge and IE.\n * 2. Correct the color inheritance from `fieldset` elements in IE.\n * 3. Remove the padding so developers are not caught out when they zero out\n * `fieldset` elements in all browsers.\n */\n\nlegend {\n box-sizing: border-box; /* 1 */\n color: inherit; /* 2 */\n display: table; /* 1 */\n max-width: 100%; /* 1 */\n padding: 0; /* 3 */\n white-space: normal; /* 1 */\n}\n\n/**\n * Add the correct vertical alignment in Chrome, Firefox, and Opera.\n */\n\nprogress {\n vertical-align: baseline;\n}\n\n/**\n * Remove the default vertical scrollbar in IE 10+.\n */\n\ntextarea {\n overflow: auto;\n}\n\n/**\n * 1. Add the correct box sizing in IE 10.\n * 2. Remove the padding in IE 10.\n */\n\n[type=\"checkbox\"],\n[type=\"radio\"] {\n box-sizing: border-box; /* 1 */\n padding: 0; /* 2 */\n}\n\n/**\n * Correct the cursor style of increment and decrement buttons in Chrome.\n */\n\n[type=\"number\"]::-webkit-inner-spin-button,\n[type=\"number\"]::-webkit-outer-spin-button {\n height: auto;\n}\n\n/**\n * 1. Correct the odd appearance in Chrome and Safari.\n * 2. Correct the outline style in Safari.\n */\n\n[type=\"search\"] {\n appearance: textfield; /* 1 */\n outline-offset: -2px; /* 2 */\n}\n\n/**\n * Remove the inner padding in Chrome and Safari on macOS.\n */\n\n[type=\"search\"]::-webkit-search-decoration {\n appearance: none;\n}\n\n/**\n * 1. Correct the inability to style clickable types in iOS and Safari.\n * 2. Change font properties to `inherit` in Safari.\n */\n\n::-webkit-file-upload-button {\n appearance: button; /* 1 */\n font: inherit; /* 2 */\n}\n\n/* Interactive\n ========================================================================== */\n\n/*\n * Add the correct display in Edge, IE 10+, and Firefox.\n */\n\ndetails {\n display: block;\n}\n\n/*\n * Add the correct display in all browsers.\n */\n\nsummary {\n display: list-item;\n}\n\n/* Misc\n ========================================================================== */\n\n/**\n * Add the correct display in IE 10+.\n */\n\ntemplate {\n display: none;\n}\n\n/**\n * Add the correct display in IE 10.\n */\n\n[hidden] {\n display: none;\n}\n","// Base element style overrides\n// stylelint-disable selector-no-type, selector-max-type, selector-max-specificity, selector-max-id\n\n:root {\n color-scheme: $color-scheme;\n}\n\n* {\n box-sizing: border-box;\n}\n\nhtml {\n scroll-behavior: smooth;\n\n @include fs-4;\n}\n\nbody {\n font-family: $body-font-family;\n font-size: inherit;\n line-height: $body-line-height;\n color: $body-text-color;\n background-color: $body-background-color;\n overflow-wrap: break-word;\n}\n\nol,\nul,\ndl,\npre,\naddress,\nblockquote,\ntable,\ndiv,\nhr,\nform,\nfieldset,\nnoscript .table-wrapper {\n margin-top: 0;\n}\n\nh1,\nh2,\nh3,\nh4,\nh5,\nh6,\n#toctitle {\n margin-top: 0;\n margin-bottom: 1em;\n font-weight: 500;\n line-height: $body-heading-line-height;\n color: $body-heading-color;\n}\n\np {\n margin-top: 1em;\n margin-bottom: 1em;\n}\n\na {\n color: $link-color;\n text-decoration: none;\n}\n\na:not([class]) {\n text-decoration: underline;\n text-decoration-color: $border-color;\n text-underline-offset: 2px;\n\n &:hover {\n text-decoration-color: rgba($link-color, 0.45);\n }\n}\n\ncode {\n font-family: $mono-font-family;\n font-size: 0.75em;\n line-height: $body-line-height;\n}\n\nfigure,\npre {\n margin: 0;\n}\n\nli {\n margin: 0.25em 0;\n}\n\nimg {\n max-width: 100%;\n height: auto;\n}\n\nhr {\n height: 1px;\n padding: 0;\n margin: $sp-6 0;\n background-color: $border-color;\n border: 0;\n}\n\n// adds a GitHub-style sidebar to blockquotes\nblockquote {\n margin: 10px 0;\n\n // resets user-agent stylesheets for blockquotes\n margin-block-start: 0;\n margin-inline-start: 0;\n padding-left: 1rem;\n border-left: 3px solid $border-color;\n}\n","// Meshtastic Material 3 — Light color scheme for just-the-docs\n// Source: core/ui/.../Color.kt §8.2 (Light Scheme)\n//\n// Brand colors:\n// Primary (Light): #2D8F52 (Green 700)\n// Surface (Light): #F5F6FA (Neutral 50)\n\n$color-scheme: light;\n\n// Body / page background\n$body-background-color: #F5F6FA; // Neutral 50 — surfaceLight\n$sidebar-color: #ECEDF3; // Neutral 100 — surfaceContainerLight\n$body-text-color: #2C2D3C; // Neutral 800 — onSurfaceLight\n$body-heading-color: #2C2D3C; // Neutral 800\n\n// Links\n$link-color: #2D8F52; // Green 700 — primaryLight\n$nav-link-color: #2D8F52; // Green 700\n\n// Navigation\n$nav-child-link-color: #555668; // Neutral 600 — secondaryLight\n$search-result-preview-color: #555668;\n\n// Code\n$code-background-color: #ECEDF3; // Neutral 100\n$code-linenumber-color: #9496A6; // Neutral 400\n\n// Borders\n$border-color: #D5D6E0; // Neutral 200 — outlineVariantLight\n$table-background-color: #F5F6FA; // Neutral 50\n\n// Buttons\n$btn-primary-color: #2D8F52; // Green 700\n\n// Feedback / callouts\n$feedback-color: #E0E1EB; // surfaceContainerHighLight\n\n// Search\n$search-background-color: #FFFFFF; // surfaceContainerLowestLight\n","@mixin fs-1 {\n & {\n font-size: $font-size-1 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-1-sm !important;\n }\n}\n\n@mixin fs-2 {\n & {\n font-size: $font-size-2 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-3 !important;\n }\n}\n\n@mixin fs-3 {\n & {\n font-size: $font-size-3 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-4 !important;\n }\n}\n\n@mixin fs-4 {\n & {\n font-size: $font-size-4 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-5 !important;\n }\n}\n\n@mixin fs-5 {\n & {\n font-size: $font-size-5 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-6 !important;\n }\n}\n\n@mixin fs-6 {\n & {\n font-size: $font-size-6 !important;\n }\n\n @include mq(sm) {\n font-size: $font-size-7 !important;\n line-height: $body-heading-line-height;\n }\n}\n\n@mixin fs-7 {\n & {\n font-size: $font-size-7 !important;\n line-height: $body-heading-line-height;\n }\n\n @include mq(sm) {\n font-size: $font-size-8 !important;\n }\n}\n\n@mixin fs-8 {\n & {\n font-size: $font-size-8 !important;\n line-height: $body-heading-line-height;\n }\n\n @include mq(sm) {\n font-size: $font-size-9 !important;\n }\n}\n\n@mixin fs-9 {\n & {\n font-size: $font-size-9 !important;\n line-height: $body-heading-line-height;\n }\n\n @include mq(sm) {\n font-size: $font-size-10 !important;\n }\n}\n\n@mixin fs-10 {\n & {\n font-size: $font-size-10 !important;\n line-height: $body-heading-line-height;\n }\n\n @include mq(sm) {\n font-size: $font-size-10-sm !important;\n }\n}\n","// Media query\n\n// Media query mixin\n// Usage:\n// @include mq(md) {\n// ..medium and up styles\n// }\n@mixin mq($name) {\n // Retrieves the value from the key\n $value: map-get($media-queries, $name);\n\n // If the key exists in the map\n @if $value {\n // Prints a media query based on the value\n @media (min-width: $value) {\n @content;\n }\n } @else {\n @warn \"No value could be retrieved from `#{$media-query}`. Please make sure it is defined in `$media-queries` map.\";\n }\n}\n\n// Responsive container\n\n@mixin container {\n padding-right: $gutter-spacing-sm;\n padding-left: $gutter-spacing-sm;\n\n @include mq(md) {\n padding-right: $gutter-spacing;\n padding-left: $gutter-spacing;\n }\n}\n","// Typography\n\n// prettier-ignore\n$body-font-family: system-ui, -apple-system, blinkmacsystemfont, \"Segoe UI\",\n roboto, \"Helvetica Neue\", arial, sans-serif, \"Segoe UI Emoji\" !default;\n$mono-font-family: \"SFMono-Regular\", menlo, consolas, monospace !default;\n$root-font-size: 16px !default; // DEPRECATED: previously base font-size for rems\n$body-line-height: 1.4 !default;\n$content-line-height: 1.6 !default;\n$body-heading-line-height: 1.25 !default;\n\n// Font size\n// `-sm` suffix is the size at the small (and above) media query\n\n$font-size-1: 0.5625rem !default;\n$font-size-1-sm: 0.625rem !default;\n$font-size-2: 0.6875rem !default; // h4 - uppercased!, h6 not uppercased, text-small\n$font-size-3: 0.75rem !default; // h5\n$font-size-4: 0.875rem !default;\n$font-size-5: 1rem !default; // h3\n$font-size-6: 1.125rem !default; // h2\n$font-size-7: 1.5rem !default;\n$font-size-8: 2rem !default; // h1\n$font-size-9: 2.25rem !default;\n$font-size-10: 2.625rem !default;\n$font-size-10-sm: 3rem !default;\n\n// Colors\n\n$white: #fff !default;\n$grey-dk-000: #959396 !default;\n$grey-dk-100: #5c5962 !default;\n$grey-dk-200: #44434d !default;\n$grey-dk-250: #302d36 !default;\n$grey-dk-300: #27262b !default;\n$grey-lt-000: #f5f6fa !default;\n$grey-lt-100: #eeebee !default;\n$grey-lt-200: #ecebed !default;\n$grey-lt-300: #e6e1e8 !default;\n$purple-000: #7253ed !default;\n$purple-100: #5e41d0 !default;\n$purple-200: #4e26af !default;\n$purple-300: #381885 !default;\n$blue-000: #2c84fa !default;\n$blue-100: #2869e6 !default;\n$blue-200: #264caf !default;\n$blue-300: #183385 !default;\n$green-000: #41d693 !default;\n$green-100: #11b584 !default;\n$green-200: #009c7b !default;\n$green-300: #026e57 !default;\n$yellow-000: #ffeb82 !default;\n$yellow-100: #fadf50 !default;\n$yellow-200: #f7d12e !default;\n$yellow-300: #e7af06 !default;\n$red-000: #f77e7e !default;\n$red-100: #f96e65 !default;\n$red-200: #e94c4c !default;\n$red-300: #dd2e2e !default;\n\n// Spacing\n\n$spacing-unit: 1rem; // 1rem == 16px\n\n$spacers: (\n sp-0: 0,\n sp-1: $spacing-unit * 0.25,\n sp-2: $spacing-unit * 0.5,\n sp-3: $spacing-unit * 0.75,\n sp-4: $spacing-unit,\n sp-5: $spacing-unit * 1.5,\n sp-6: $spacing-unit * 2,\n sp-7: $spacing-unit * 2.5,\n sp-8: $spacing-unit * 3,\n sp-9: $spacing-unit * 3.5,\n sp-10: $spacing-unit * 4,\n) !default;\n$sp-1: map-get($spacers, sp-1) !default; // 0.25 rem == 4px\n$sp-2: map-get($spacers, sp-2) !default; // 0.5 rem == 8px\n$sp-3: map-get($spacers, sp-3) !default; // 0.75 rem == 12px\n$sp-4: map-get($spacers, sp-4) !default; // 1 rem == 16px\n$sp-5: map-get($spacers, sp-5) !default; // 1.5 rem == 24px\n$sp-6: map-get($spacers, sp-6) !default; // 2 rem == 32px\n$sp-7: map-get($spacers, sp-7) !default; // 2.5 rem == 40px\n$sp-8: map-get($spacers, sp-8) !default; // 3 rem == 48px\n$sp-9: map-get($spacers, sp-9) !default; // 3.5 rem == 56px\n$sp-10: map-get($spacers, sp-10) !default; // 4 rem == 64px\n\n// Borders\n\n$border: 1px solid !default;\n$border-radius: 4px !default;\n$border-color: $grey-lt-100 !default;\n\n// Grid system\n\n$gutter-spacing: $sp-6 !default;\n$gutter-spacing-sm: $sp-4 !default;\n$nav-width: 16.5rem !default;\n$nav-width-md: 15.5rem !default;\n$nav-list-item-height: $sp-6 !default;\n$nav-list-item-height-sm: $sp-8 !default;\n$nav-list-expander-right: true;\n$content-width: 50rem !default;\n$header-height: 3.75rem !default;\n$search-results-width: $content-width - $nav-width !default;\n$transition-duration: 400ms;\n\n// Media queries in pixels\n\n$media-queries: (\n xs: 20rem,\n sm: 31.25rem,\n md: $content-width,\n lg: $content-width + $nav-width,\n xl: 87.5rem,\n) !default;\n","// The basic two column layout\n\n.side-bar {\n z-index: 0;\n display: flex;\n flex-wrap: wrap;\n background-color: $sidebar-color;\n\n @include mq(md) {\n flex-flow: column nowrap;\n position: fixed;\n width: $nav-width-md;\n height: 100%;\n border-right: $border $border-color;\n align-items: flex-end;\n }\n\n @include mq(lg) {\n width: calc((100% - #{$nav-width + $content-width}) / 2 + #{$nav-width});\n min-width: $nav-width;\n }\n\n & + .main {\n @include mq(md) {\n margin-left: $nav-width-md;\n }\n\n @include mq(lg) {\n // stylelint-disable function-name-case\n // disable for Max(), we want to use the CSS max() function\n margin-left: Max(\n #{$nav-width},\n calc((100% - #{$nav-width + $content-width}) / 2 + #{$nav-width})\n );\n // stylelint-enable function-name-case\n }\n\n .main-header {\n display: none;\n background-color: $sidebar-color;\n\n @include mq(md) {\n display: flex;\n background-color: $body-background-color;\n }\n\n &.nav-open {\n display: block;\n\n @include mq(md) {\n display: flex;\n }\n }\n }\n }\n}\n\n.main {\n margin: auto;\n\n @include mq(md) {\n position: relative;\n max-width: $content-width;\n }\n}\n\n.main-content-wrap {\n padding-top: $gutter-spacing-sm;\n padding-bottom: $gutter-spacing-sm;\n\n @include container;\n\n @include mq(md) {\n padding-top: $gutter-spacing;\n padding-bottom: $gutter-spacing;\n }\n}\n\n.main-header {\n z-index: 0;\n border-bottom: $border $border-color;\n\n @include mq(md) {\n display: flex;\n justify-content: space-between;\n height: $header-height;\n }\n}\n\n.site-nav,\n.site-header,\n.site-footer {\n width: 100%;\n\n @include mq(lg) {\n width: $nav-width;\n }\n}\n\n.site-nav {\n display: none;\n\n &.nav-open {\n display: block;\n }\n\n @include mq(md) {\n display: block;\n padding-top: $sp-8;\n padding-bottom: $gutter-spacing-sm;\n overflow-y: auto;\n flex: 1 1 auto;\n }\n}\n\n.site-header {\n display: flex;\n min-height: $header-height;\n align-items: center;\n\n @include mq(md) {\n height: $header-height;\n max-height: $header-height;\n border-bottom: $border $border-color;\n }\n}\n\n.site-title {\n flex-grow: 1;\n display: flex;\n height: 100%;\n align-items: center;\n padding-top: $sp-3;\n padding-bottom: $sp-3;\n color: $body-heading-color;\n\n @include container;\n\n @include fs-6;\n\n @include mq(md) {\n padding-top: $sp-2;\n padding-bottom: $sp-2;\n }\n}\n\n@if variable-exists(logo) {\n .site-logo {\n width: 100%;\n height: 100%;\n background-image: url($logo);\n background-repeat: no-repeat;\n background-position: left center;\n background-size: contain;\n }\n}\n\n.site-button {\n display: flex;\n height: 100%;\n padding: $gutter-spacing-sm;\n align-items: center;\n}\n\n@include mq(md) {\n .site-header .site-button {\n display: none;\n }\n}\n\n.site-title:hover {\n background-image: linear-gradient(\n -90deg,\n rgba($feedback-color, 1) 0%,\n rgba($feedback-color, 0.8) 80%,\n rgba($feedback-color, 0) 100%\n );\n}\n\n.site-button:hover {\n background-image: linear-gradient(\n -90deg,\n rgba($feedback-color, 1) 0%,\n rgba($feedback-color, 0.8) 100%\n );\n}\n\n.site-footer {\n position: absolute;\n bottom: 0;\n left: 0;\n padding-top: $sp-4;\n padding-bottom: $sp-4;\n\n @include container;\n\n @include fs-2;\n\n @include mq(md) {\n position: static;\n justify-self: end;\n }\n}\n\n.icon {\n width: $sp-5;\n height: $sp-5;\n color: $link-color;\n}\n","@charset \"UTF-8\";\n\n// Styles for rendered markdown in the .main-content container\n// stylelint-disable selector-no-type, max-nesting-depth, selector-max-compound-selectors, selector-max-type, selector-max-specificity, selector-max-id\n\n.main-content {\n line-height: $content-line-height;\n\n ol,\n ul,\n dl,\n pre,\n address,\n blockquote,\n .table-wrapper {\n margin-top: 0.5em;\n }\n\n a {\n overflow: hidden;\n text-overflow: ellipsis;\n }\n\n ul,\n ol {\n padding-left: 1.5em;\n }\n\n li {\n .highlight {\n margin-top: $sp-1;\n }\n }\n\n ol {\n list-style-type: none;\n counter-reset: step-counter;\n\n > li {\n position: relative;\n\n &::before {\n position: absolute;\n top: 0.2em;\n left: -1.6em;\n color: $grey-dk-000;\n content: counter(step-counter);\n counter-increment: step-counter;\n @include fs-3;\n\n @include mq(sm) {\n top: 0.11em;\n }\n }\n\n ol {\n counter-reset: sub-counter;\n\n > li {\n &::before {\n content: counter(sub-counter, lower-alpha);\n counter-increment: sub-counter;\n }\n }\n }\n }\n }\n\n ul {\n list-style: none;\n\n > li {\n &::before {\n position: absolute;\n margin-left: -1.4em;\n color: $grey-dk-000;\n content: \"•\";\n }\n }\n }\n\n .task-list-item {\n &::before {\n content: \"\";\n }\n }\n\n .task-list-item-checkbox {\n margin-right: 0.6em;\n margin-left: -1.4em;\n\n // The same margin-left is used above for ul > li::before\n }\n\n hr + * {\n margin-top: 0;\n }\n\n h1:first-of-type {\n margin-top: 0.5em;\n }\n\n dl {\n display: grid;\n grid-template: auto / 10em 1fr;\n }\n\n dt,\n dd {\n margin: 0.25em 0;\n }\n\n dt {\n grid-column: 1;\n font-weight: 500;\n text-align: right;\n\n &::after {\n content: \":\";\n }\n }\n\n dd {\n grid-column: 2;\n margin-bottom: 0;\n margin-left: 1em;\n\n blockquote,\n div,\n dl,\n dt,\n h1,\n h2,\n h3,\n h4,\n h5,\n h6,\n li,\n ol,\n p,\n pre,\n table,\n ul,\n .table-wrapper {\n &:first-child {\n margin-top: 0;\n }\n }\n }\n\n dd,\n ol,\n ul {\n dl:first-child {\n dt:first-child,\n dd:nth-child(2) {\n margin-top: 0;\n }\n }\n }\n\n .anchor-heading {\n position: absolute;\n right: -$sp-4;\n width: $sp-5;\n height: 100%;\n padding-right: $sp-1;\n padding-left: $sp-1;\n overflow: visible;\n\n @include mq(md) {\n right: auto;\n left: -$sp-5;\n }\n\n svg {\n display: inline-block;\n width: 100%;\n height: 100%;\n color: $link-color;\n visibility: hidden;\n }\n }\n\n .anchor-heading:hover,\n .anchor-heading:focus,\n h1:hover > .anchor-heading,\n h2:hover > .anchor-heading,\n h3:hover > .anchor-heading,\n h4:hover > .anchor-heading,\n h5:hover > .anchor-heading,\n h6:hover > .anchor-heading {\n svg {\n visibility: visible;\n }\n }\n\n summary {\n cursor: pointer;\n }\n\n h1,\n h2,\n h3,\n h4,\n h5,\n h6,\n #toctitle {\n position: relative;\n margin-top: 1.5em;\n margin-bottom: 0.25em;\n\n + table,\n + .table-wrapper,\n + .code-example,\n + .highlighter-rouge,\n + .sectionbody .listingblock {\n margin-top: 1em;\n }\n\n + p:not(.label) {\n margin-top: 0;\n }\n }\n\n > h1:first-child,\n > h2:first-child,\n > h3:first-child,\n > h4:first-child,\n > h5:first-child,\n > h6:first-child,\n > .sect1:first-child > h2,\n > .sect2:first-child > h3,\n > .sect3:first-child > h4,\n > .sect4:first-child > h5,\n > .sect5:first-child > h6 {\n margin-top: $sp-2;\n }\n}\n","// Main nav, breadcrumb, etc...\n// stylelint-disable selector-no-type, max-nesting-depth, selector-max-compound-selectors, selector-max-type, selector-max-specificity\n\n.nav-list {\n padding: 0;\n margin-top: 0;\n margin-bottom: 0;\n list-style: none;\n\n .nav-list-item {\n position: relative;\n margin: 0;\n\n @include fs-4;\n\n @include mq(md) {\n @include fs-3;\n }\n\n .nav-list-link {\n display: block;\n min-height: $nav-list-item-height-sm;\n padding-top: $sp-1;\n padding-bottom: $sp-1;\n line-height: #{$nav-list-item-height-sm - 2 * $sp-1};\n @if $nav-list-expander-right {\n padding-right: $nav-list-item-height-sm;\n padding-left: $gutter-spacing-sm;\n } @else {\n padding-right: $gutter-spacing-sm;\n padding-left: $nav-list-item-height-sm;\n }\n\n @include mq(md) {\n min-height: $nav-list-item-height;\n line-height: #{$nav-list-item-height - 2 * $sp-1};\n @if $nav-list-expander-right {\n padding-right: $nav-list-item-height;\n padding-left: $gutter-spacing;\n } @else {\n padding-right: $gutter-spacing;\n padding-left: $nav-list-item-height;\n }\n }\n\n &.external > svg {\n width: $sp-4;\n height: $sp-4;\n vertical-align: text-bottom;\n }\n\n &.active {\n font-weight: 600;\n text-decoration: none;\n }\n\n &:hover,\n &.active {\n color: darken($link-color, 5%);\n background-image: linear-gradient(\n -90deg,\n rgba($feedback-color, 1) 0%,\n rgba($feedback-color, 0.8) 80%,\n rgba($feedback-color, 0) 100%\n );\n }\n }\n\n .nav-list-expander {\n position: absolute;\n @if $nav-list-expander-right {\n right: 0;\n }\n\n width: $nav-list-item-height-sm;\n height: $nav-list-item-height-sm;\n padding: #{$nav-list-item-height-sm * 0.25};\n color: $link-color;\n\n @include mq(md) {\n width: $nav-list-item-height;\n height: $nav-list-item-height;\n padding: #{$nav-list-item-height * 0.25};\n }\n\n &:hover {\n background-image: linear-gradient(\n -90deg,\n rgba($feedback-color, 1) 0%,\n rgba($feedback-color, 0.8) 100%\n );\n }\n\n @if $nav-list-expander-right {\n svg {\n transform: rotate(90deg);\n }\n }\n }\n\n > .nav-list {\n display: none;\n padding-left: $sp-3;\n list-style: none;\n\n .nav-list-item {\n position: relative;\n\n .nav-list-link {\n color: $nav-child-link-color;\n }\n\n .nav-list-expander {\n color: $nav-child-link-color;\n }\n }\n }\n\n &.active {\n > .nav-list-expander svg {\n @if $nav-list-expander-right {\n transform: rotate(-90deg);\n } @else {\n transform: rotate(90deg);\n }\n }\n\n > .nav-list {\n display: block;\n }\n }\n }\n}\n\n.nav-category {\n padding: $sp-2 $gutter-spacing-sm;\n font-weight: 600;\n text-align: start;\n text-transform: uppercase;\n border-bottom: $border $border-color;\n @include fs-2;\n\n @include mq(md) {\n padding: $sp-2 $gutter-spacing;\n margin-top: $gutter-spacing-sm;\n text-align: start;\n\n &:first-child {\n margin-top: 0;\n }\n }\n}\n\n.nav-list.nav-category-list {\n > .nav-list-item {\n margin: 0;\n\n > .nav-list {\n padding: 0;\n\n > .nav-list-item {\n > .nav-list-link {\n color: $link-color;\n }\n\n > .nav-list-expander {\n color: $link-color;\n }\n }\n }\n }\n}\n\n// Aux nav\n\n.aux-nav {\n height: 100%;\n overflow-x: auto;\n @include fs-2;\n\n .aux-nav-list {\n display: flex;\n height: 100%;\n padding: 0;\n margin: 0;\n list-style: none;\n }\n\n .aux-nav-list-item {\n display: inline-block;\n height: 100%;\n padding: 0;\n margin: 0;\n }\n\n @include mq(md) {\n padding-right: $gutter-spacing-sm;\n }\n}\n\n// Breadcrumb nav\n\n.breadcrumb-nav {\n @include mq(md) {\n margin-top: -$sp-4;\n }\n}\n\n.breadcrumb-nav-list {\n padding-left: 0;\n margin-bottom: $sp-3;\n list-style: none;\n}\n\n.breadcrumb-nav-list-item {\n display: table-cell;\n @include fs-2;\n\n &::before {\n display: none;\n }\n\n &::after {\n display: inline-block;\n margin-right: $sp-2;\n margin-left: $sp-2;\n color: $grey-dk-000;\n content: \"/\";\n }\n\n &:last-child {\n &::after {\n content: \"\";\n }\n }\n}\n","// Typography\n// stylelint-disable selector-no-type, selector-max-type, selector-max-specificity, selector-max-id\n\nh1,\n.text-alpha {\n font-weight: 300;\n\n @include fs-8;\n}\n\nh2,\n.text-beta,\n#toctitle {\n @include fs-6;\n}\n\nh3,\n.text-gamma {\n @include fs-5;\n}\n\nh4,\n.text-delta {\n font-weight: 400;\n text-transform: uppercase;\n letter-spacing: 0.1em;\n\n @include fs-2;\n}\n\nh4 code {\n text-transform: none;\n}\n\nh5,\n.text-epsilon {\n @include fs-3;\n}\n\nh6,\n.text-zeta {\n @include fs-2;\n}\n\n.text-small {\n @include fs-2;\n}\n\n.text-mono {\n font-family: $mono-font-family !important;\n}\n\n.text-left {\n text-align: left !important;\n}\n\n.text-center {\n text-align: center !important;\n}\n\n.text-right {\n text-align: right !important;\n}\n","// Labels (not the form kind)\n\n// this :not() prevents a style clash with Mermaid.js's\n// diagram labels, which also use .label\n// for more, see https://github.com/just-the-docs/just-the-docs/issues/1272\n// and the accompanying PR\n.label:not(g),\n.label-blue:not(g) {\n display: inline-block;\n padding: 0.16em 0.56em;\n margin-right: $sp-2;\n margin-left: $sp-2;\n color: $white;\n text-transform: uppercase;\n vertical-align: middle;\n background-color: $blue-100;\n border-radius: 12px;\n\n @include fs-2;\n}\n\n.label-green:not(g) {\n background-color: $green-300;\n}\n\n.label-purple:not(g) {\n background-color: $purple-100;\n}\n\n.label-red:not(g) {\n background-color: $red-300;\n}\n\n.label-yellow:not(g) {\n color: $grey-dk-200;\n background-color: $yellow-200;\n}\n","// Buttons and things that look like buttons\n// stylelint-disable color-named\n\n.btn {\n display: inline-block;\n box-sizing: border-box;\n padding: 0.3em 1em;\n margin: 0;\n font-family: inherit;\n font-size: inherit;\n font-weight: 500;\n line-height: 1.5;\n color: $link-color;\n text-decoration: none;\n vertical-align: baseline;\n cursor: pointer;\n background-color: $base-button-color;\n border-width: 0;\n border-radius: $border-radius;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n appearance: none;\n\n &:focus {\n text-decoration: none;\n outline: none;\n box-shadow: 0 0 0 3px rgba(blue, 0.25);\n }\n\n &:focus:hover,\n &.selected:focus {\n box-shadow: 0 0 0 3px rgba(blue, 0.25);\n }\n\n &:hover,\n &.zeroclipboard-is-hover {\n color: darken($link-color, 2%);\n }\n\n &:hover,\n &:active,\n &.zeroclipboard-is-hover,\n &.zeroclipboard-is-active {\n text-decoration: none;\n background-color: darken($base-button-color, 1%);\n }\n\n &:active,\n &.selected,\n &.zeroclipboard-is-active {\n background-color: darken($base-button-color, 3%);\n background-image: none;\n box-shadow: inset 0 2px 4px rgba(0, 0, 0, 0.15);\n }\n\n &.selected:hover {\n background-color: darken(#dcdcdc, 5%);\n }\n\n &:disabled,\n &.disabled {\n &,\n &:hover {\n color: rgba(102, 102, 102, 0.5);\n cursor: default;\n background-color: rgba(229, 229, 229, 0.5);\n background-image: none;\n box-shadow: none;\n }\n }\n}\n\n.btn-outline {\n color: $link-color;\n background: transparent;\n box-shadow: inset 0 0 0 2px $grey-lt-300;\n\n &:hover,\n &:active,\n &.zeroclipboard-is-hover,\n &.zeroclipboard-is-active {\n color: darken($link-color, 4%);\n text-decoration: none;\n background-color: transparent;\n box-shadow: inset 0 0 0 3px $grey-lt-300;\n }\n\n &:focus {\n text-decoration: none;\n outline: none;\n box-shadow:\n inset 0 0 0 2px $grey-dk-100,\n 0 0 0 3px rgba(blue, 0.25);\n }\n\n &:focus:hover,\n &.selected:focus {\n box-shadow: inset 0 0 0 2px $grey-dk-100;\n }\n}\n\n.btn-primary {\n @include btn-color($white, $btn-primary-color);\n}\n\n.btn-purple {\n @include btn-color($white, $purple-100);\n}\n\n.btn-blue {\n @include btn-color($white, $blue-200);\n}\n\n.btn-green {\n @include btn-color($white, $green-300);\n}\n\n.btn-reset {\n background: none;\n border: none;\n margin: 0;\n text-align: inherit;\n font: inherit;\n border-radius: 0;\n appearance: none;\n}\n","$color-scheme: light !default;\n$body-background-color: $white !default;\n$body-heading-color: $grey-dk-300 !default;\n$body-text-color: $grey-dk-100 !default;\n$link-color: $purple-000 !default;\n$nav-child-link-color: $grey-dk-100 !default;\n$sidebar-color: $grey-lt-000 !default;\n$base-button-color: #f7f7f7 !default;\n$btn-primary-color: $purple-100 !default;\n$code-background-color: $white !default;\n$feedback-color: darken($sidebar-color, 3%) !default;\n$table-background-color: $white !default;\n$search-background-color: $white !default;\n$search-result-preview-color: $grey-dk-100 !default;\n\n@import \"./vendor/accessible-pygments/github-light\";\n","// Colored button\n\n@mixin btn-color($fg, $bg) {\n color: $fg;\n background-color: darken($bg, 2%);\n background-image: linear-gradient(lighten($bg, 5%), darken($bg, 2%));\n box-shadow:\n 0 1px 3px rgba(0, 0, 0, 0.25),\n 0 4px 10px rgba(0, 0, 0, 0.12);\n\n &:hover,\n &.zeroclipboard-is-hover {\n color: $fg;\n background-color: darken($bg, 4%);\n background-image: linear-gradient((lighten($bg, 2%), darken($bg, 4%)));\n }\n\n &:active,\n &.selected,\n &.zeroclipboard-is-active {\n background-color: darken($bg, 5%);\n background-image: none;\n box-shadow: inset 0 2px 4px rgba(0, 0, 0, 0.15);\n }\n\n &.selected:hover {\n background-color: darken($bg, 10%);\n }\n}\n","// Search input and autocomplete\n\n.search {\n position: relative;\n z-index: 2;\n flex-grow: 1;\n height: $sp-10;\n padding: $sp-2;\n transition: padding linear #{$transition-duration * 0.5};\n\n @include mq(md) {\n position: relative !important;\n width: auto !important;\n height: 100% !important;\n padding: 0;\n transition: none;\n }\n}\n\n.search-input-wrap {\n position: relative;\n z-index: 1;\n height: $sp-8;\n overflow: hidden;\n border-radius: $border-radius;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n transition: height linear #{$transition-duration * 0.5};\n\n @include mq(md) {\n position: absolute;\n width: 100%;\n max-width: $search-results-width;\n height: 100% !important;\n border-radius: 0;\n box-shadow: none;\n transition: width ease $transition-duration;\n }\n}\n\n.search-input {\n position: absolute;\n width: 100%;\n height: 100%;\n padding: $sp-2 $gutter-spacing-sm $sp-2 #{$gutter-spacing-sm + $sp-5};\n font-size: 1rem;\n color: $body-text-color;\n background-color: $search-background-color;\n border-top: 0;\n border-right: 0;\n border-bottom: 0;\n border-left: 0;\n border-radius: 0;\n\n @include mq(md) {\n padding: $sp-2 $gutter-spacing-sm $sp-2 #{$gutter-spacing + $sp-5};\n font-size: 0.875rem;\n background-color: $body-background-color;\n transition: padding-left linear #{$transition-duration * 0.5};\n }\n\n &:focus {\n outline: 2px solid $link-color;\n outline-offset: -2px;\n\n + .search-label .search-icon {\n color: $link-color;\n }\n }\n}\n\n.search-label {\n position: absolute;\n display: flex;\n height: 100%;\n padding-left: $gutter-spacing-sm;\n\n @include mq(md) {\n padding-left: $gutter-spacing;\n transition: padding-left linear #{$transition-duration * 0.5};\n }\n\n .search-icon {\n width: #{$sp-4 * 1.2};\n height: #{$sp-4 * 1.2};\n align-self: center;\n color: $grey-dk-000;\n }\n}\n\n.search-results {\n position: absolute;\n left: 0;\n display: none;\n width: 100%;\n max-height: calc(100% - #{$sp-10});\n overflow-y: auto;\n background-color: $search-background-color;\n border-bottom-right-radius: $border-radius;\n border-bottom-left-radius: $border-radius;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n\n @include mq(md) {\n top: 100%;\n width: $search-results-width;\n max-height: calc(100vh - 200%) !important;\n }\n}\n\n.search-results-list {\n padding-left: 0;\n margin-bottom: $sp-1;\n list-style: none;\n @include fs-4;\n\n @include mq(md) {\n @include fs-3;\n }\n}\n\n.search-results-list-item {\n padding: 0;\n margin: 0;\n}\n\n.search-result {\n display: block;\n padding: $sp-1 $sp-3;\n\n &:hover,\n &.active {\n background-color: $feedback-color;\n }\n}\n\n.search-result-title {\n display: block;\n padding-top: $sp-2;\n padding-bottom: $sp-2;\n\n @include mq(sm) {\n display: inline-block;\n width: 40%;\n padding-right: $sp-2;\n vertical-align: top;\n }\n}\n\n.search-result-doc {\n display: flex;\n align-items: center;\n word-wrap: break-word;\n\n &.search-result-doc-parent {\n opacity: 0.5;\n @include fs-3;\n\n @include mq(md) {\n @include fs-2;\n }\n }\n\n .search-result-icon {\n width: $sp-4;\n height: $sp-4;\n margin-right: $sp-2;\n color: $link-color;\n flex-shrink: 0;\n }\n\n .search-result-doc-title {\n overflow: auto;\n }\n}\n\n.search-result-section {\n margin-left: #{$sp-4 + $sp-2};\n word-wrap: break-word;\n}\n\n.search-result-rel-url {\n display: block;\n margin-left: #{$sp-4 + $sp-2};\n overflow: hidden;\n color: $search-result-preview-color;\n text-overflow: ellipsis;\n white-space: nowrap;\n @include fs-1;\n}\n\n.search-result-previews {\n display: block;\n padding-top: $sp-2;\n padding-bottom: $sp-2;\n padding-left: $sp-4;\n margin-left: $sp-2;\n color: $search-result-preview-color;\n word-wrap: break-word;\n border-left: $border;\n border-left-color: $border-color;\n @include fs-2;\n\n @include mq(sm) {\n display: inline-block;\n width: 60%;\n padding-left: $sp-2;\n margin-left: 0;\n vertical-align: top;\n }\n}\n\n.search-result-preview + .search-result-preview {\n margin-top: $sp-1;\n}\n\n.search-result-highlight {\n font-weight: bold;\n}\n\n.search-no-result {\n padding: $sp-2 $sp-3;\n @include fs-3;\n}\n\n.search-button {\n position: fixed;\n right: $sp-4;\n bottom: $sp-4;\n display: flex;\n width: $sp-9;\n height: $sp-9;\n background-color: $search-background-color;\n border: 1px solid rgba($link-color, 0.3);\n border-radius: #{$sp-9 * 0.5};\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n align-items: center;\n justify-content: center;\n}\n\n.search-overlay {\n position: fixed;\n top: 0;\n left: 0;\n z-index: 1;\n width: 0;\n height: 0;\n background-color: rgba(0, 0, 0, 0.3);\n opacity: 0;\n transition:\n opacity ease $transition-duration,\n width 0s $transition-duration,\n height 0s $transition-duration;\n}\n\n.search-active {\n .search {\n position: fixed;\n top: 0;\n left: 0;\n width: 100%;\n height: 100%;\n padding: 0;\n }\n\n .search-input-wrap {\n height: $sp-10;\n border-radius: 0;\n\n @include mq(md) {\n width: $search-results-width;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n }\n }\n\n .search-input {\n background-color: $search-background-color;\n\n @include mq(md) {\n padding-left: 2.3rem;\n }\n }\n\n .search-label {\n @include mq(md) {\n padding-left: 0.6rem;\n }\n }\n\n .search-results {\n display: block;\n }\n\n .search-overlay {\n width: 100%;\n height: 100%;\n opacity: 1;\n transition:\n opacity ease $transition-duration,\n width 0s,\n height 0s;\n }\n\n @include mq(md) {\n .main {\n position: fixed;\n right: 0;\n left: 0;\n }\n }\n\n .main-header {\n padding-top: $sp-10;\n\n @include mq(md) {\n padding-top: 0;\n }\n }\n}\n","// Tables\n// stylelint-disable max-nesting-depth, selector-no-type, selector-max-type\n\n.table-wrapper {\n display: block;\n width: 100%;\n max-width: 100%;\n margin-bottom: $sp-5;\n overflow-x: auto;\n border-radius: $border-radius;\n box-shadow:\n 0 1px 2px rgba(0, 0, 0, 0.12),\n 0 3px 10px rgba(0, 0, 0, 0.08);\n}\n\ntable {\n display: table;\n min-width: 100%;\n border-collapse: separate;\n}\n\nth,\ntd {\n min-width: 7.5rem;\n padding: $sp-2 $sp-3;\n background-color: $table-background-color;\n border-bottom: $border rgba($border-color, 0.5);\n border-left: $border $border-color;\n\n @include fs-3;\n\n &:first-of-type {\n border-left: 0;\n }\n}\n\ntbody {\n tr {\n &:last-of-type {\n th,\n td {\n border-bottom: 0;\n }\n\n td {\n padding-bottom: $sp-3;\n }\n }\n }\n}\n\nthead {\n th {\n border-bottom: $border $border-color;\n }\n}\n","// Code and syntax highlighting\n// stylelint-disable selector-no-qualifying-type, declaration-block-semicolon-newline-after,declaration-block-single-line-max-declarations, selector-no-type, selector-max-type, scss/comment-no-empty\n\n// {% raw %}\n\n// This instruction applies to all queues not within 'pre' or 'figure', avoiding 'code' generated by the highlight.\n:not(pre, figure) {\n & > code {\n padding: 0.2em 0.15em;\n font-weight: 400;\n background-color: $code-background-color;\n border: $border $border-color;\n border-radius: $border-radius;\n }\n}\n\n// Avoid appearance of dark border around visited code links in Safari\na:visited code {\n border-color: $border-color;\n}\n\n// Content structure for highlighted code blocks using fences or Liquid\n//\n// ```[LANG]...```, no kramdown line_numbers:\n// div.[language-LANG.]highlighter-rouge > div.highlight > pre.highlight > code\n//\n// ```[LANG]...```, kramdown line_numbers = true:\n// div.[language-LANG.]highlighter-rouge > div.highlight > pre.highlight > code\n// > div.table-wrapper > table.rouge-table > tbody > tr\n// > td.rouge-gutter.gl > pre.lineno\n// | td.rouge-code > pre\n//\n// {% highlight LANG %}...{% endhighlight %}:\n// figure.highlight > pre > code.language-LANG\n//\n// {% highlight LANG linenos %}...{% endhighlight %}:\n// figure.highlight > pre > code.language-LANG\n// > div.table-wrapper > table.rouge-table > tbody > tr\n// > td.gutter.gl > pre.lineno\n// | td.code > pre\n//\n// ----...---- (AsciiDoc)\n// div.listingblock > div.content > pre.rouge.highlight\n//\n// fix_linenos removes the outermost pre when it encloses table.rouge-table\n//\n// See docs/index-test.md for some tests.\n//\n// No kramdown line_numbers: fences and Liquid highlighting look the same.\n// Kramdown line_numbers = true: fences have a wider gutter than with Liquid?\n\n// ```[LANG]...```\n// or in AsciiDoc:\n//\n// ----\n// ...\n// ----\n\n// the code may appear with 3 different types:\n// container \\ case: default case, code with line number, code with html rendering\n// top level: div.highlighter-rouge, figure.highlight, figure.highlight\n// second level: div.highlight, div.table-wrapper, pre.highlight\n// third level: pre.highlight, td.code, absent\n// last level: code, pre, code (optionality)\n// highlighter level: span, span, span\n// the spacing are only in the second level for case 1, 3 and in the third level for case 2\n// in AsciiDoc, there is a parent container that contains optionally a title and the content.\n\n// select top level container\ndiv.highlighter-rouge,\ndiv.listingblock > div.content,\nfigure.highlight {\n margin-top: 0;\n margin-bottom: $sp-3;\n background-color: $code-background-color;\n border-radius: $border-radius;\n box-shadow: none;\n -webkit-overflow-scrolling: touch;\n position: relative;\n padding: 0;\n\n // copy button (or other button)\n // the button appear only when there is a hover on the code or focus on button\n > button {\n width: $sp-3;\n opacity: 0;\n position: absolute;\n top: 0;\n right: 0;\n padding: $sp-3;\n border: none;\n background: none;\n color: $body-text-color;\n box-sizing: content-box;\n\n svg {\n fill: $body-text-color;\n }\n\n &:active {\n text-decoration: none;\n outline: none;\n opacity: 1;\n }\n\n &:focus {\n opacity: 1;\n outline: 2px solid $link-color;\n }\n }\n\n // the button can be seen by doing a simple hover in the code, there is no need to go over the location of the button\n &:hover {\n > button {\n cursor: copy;\n opacity: 1;\n }\n }\n}\n\n// setting the spacing and scrollbar on the second level for the first case\n// remove all space on the second and third level\n// this is a mixin to accommodate for the slightly different structures generated via Markdown vs AsciiDoc\n@mixin scroll-and-spacing($code-div, $pre-select) {\n #{$code-div} {\n overflow-x: auto;\n padding: $sp-3;\n margin: 0;\n border: 1px solid $body-text-color;\n border-radius: $border-radius;\n }\n\n #{$pre-select},\n code {\n padding: 0;\n margin: 0;\n border: 0;\n }\n}\n\n// for Markdown\ndiv.highlighter-rouge {\n @include scroll-and-spacing(\"div.highlight\", \"pre.highlight\");\n}\n\n// for AsciiDoc. we also need to fix the margins for its parent container.\ndiv.listingblock {\n margin-top: 0;\n margin-bottom: $sp-3;\n\n @include scroll-and-spacing(\"div.content\", \"div.content > pre\");\n}\n\n// {% highlight LANG %}...{% endhighlight %},\n// {% highlight LANG linenos %}...{% endhighlight %}:\n\n// setting the spacing and scrollbar on the second level for the thirt case\n// the css rule are apply only to the last code enviroment\n// setting the scroolbar\nfigure.highlight {\n pre,\n :not(pre) > code {\n overflow-x: auto;\n padding: $sp-3;\n margin: 0;\n border: 1px solid $body-text-color;\n border-radius: $border-radius;\n }\n}\n\n// ```[LANG]...```, kramdown line_numbers = true,\n// {% highlight LANG linenos %}...{% endhighlight %}:\n\n// setting the spacing and scrollbar on the thirt level for the second case\n.highlight .table-wrapper {\n padding: $sp-3 0;\n margin: 0;\n border: 0;\n box-shadow: none;\n\n td,\n pre {\n min-width: 0;\n padding: 0;\n background-color: $code-background-color;\n border: 0;\n\n @include fs-2;\n }\n\n td.gl {\n width: 1em;\n padding-right: $sp-3;\n padding-left: $sp-3;\n }\n\n pre {\n margin: 0;\n line-height: 2;\n }\n}\n\n// Code examples: html render of a code\n.code-example,\n.listingblock > .title {\n padding: $sp-3;\n margin-bottom: $sp-3;\n overflow: auto;\n border: 1px solid $border-color;\n border-radius: $border-radius;\n\n + .highlighter-rouge,\n + .sectionbody .listingblock,\n + .content,\n + figure.highlight {\n position: relative;\n margin-top: -$sp-4;\n border-right: 1px solid $border-color;\n border-bottom: 1px solid $border-color;\n border-left: 1px solid $border-color;\n border-top-left-radius: 0;\n border-top-right-radius: 0;\n }\n}\n\n// Mermaid diagram code blocks should be left unstyled.\ncode.language-mermaid {\n padding: 0;\n background-color: inherit;\n border: 0;\n}\n\n// Override OneDarkJekyll Colors for Code Blocks\n.highlight,\npre.highlight {\n background: $code-background-color; // Code Background\n // For Backwards Compatibility Before $code-linenumber-color was added\n @if variable-exists(code-linenumber-color) {\n color: $code-linenumber-color; // Code Line Numbers\n } @else {\n color: $body-text-color; // Code Line Numbers\n }\n}\n\n// Override OneDarkJekyll Colors for Code Blocks\n.highlight pre {\n background: $code-background-color; // Code Background\n}\n\n// {% endraw %}\n","// Utility classes for colors\n\n// Text colors\n\n.text-grey-dk-000 {\n color: $grey-dk-000 !important;\n}\n\n.text-grey-dk-100 {\n color: $grey-dk-100 !important;\n}\n\n.text-grey-dk-200 {\n color: $grey-dk-200 !important;\n}\n\n.text-grey-dk-250 {\n color: $grey-dk-250 !important;\n}\n\n.text-grey-dk-300 {\n color: $grey-dk-300 !important;\n}\n\n.text-grey-lt-000 {\n color: $grey-lt-000 !important;\n}\n\n.text-grey-lt-100 {\n color: $grey-lt-100 !important;\n}\n\n.text-grey-lt-200 {\n color: $grey-lt-200 !important;\n}\n\n.text-grey-lt-300 {\n color: $grey-lt-300 !important;\n}\n\n.text-blue-000 {\n color: $blue-000 !important;\n}\n\n.text-blue-100 {\n color: $blue-100 !important;\n}\n\n.text-blue-200 {\n color: $blue-200 !important;\n}\n\n.text-blue-300 {\n color: $blue-300 !important;\n}\n\n.text-green-000 {\n color: $green-000 !important;\n}\n\n.text-green-100 {\n color: $green-100 !important;\n}\n\n.text-green-200 {\n color: $green-200 !important;\n}\n\n.text-green-300 {\n color: $green-300 !important;\n}\n\n.text-purple-000 {\n color: $purple-000 !important;\n}\n\n.text-purple-100 {\n color: $purple-100 !important;\n}\n\n.text-purple-200 {\n color: $purple-200 !important;\n}\n\n.text-purple-300 {\n color: $purple-300 !important;\n}\n\n.text-yellow-000 {\n color: $yellow-000 !important;\n}\n\n.text-yellow-100 {\n color: $yellow-100 !important;\n}\n\n.text-yellow-200 {\n color: $yellow-200 !important;\n}\n\n.text-yellow-300 {\n color: $yellow-300 !important;\n}\n\n.text-red-000 {\n color: $red-000 !important;\n}\n\n.text-red-100 {\n color: $red-100 !important;\n}\n\n.text-red-200 {\n color: $red-200 !important;\n}\n\n.text-red-300 {\n color: $red-300 !important;\n}\n\n// Background colors\n\n.bg-grey-dk-000 {\n background-color: $grey-dk-000 !important;\n}\n\n.bg-grey-dk-100 {\n background-color: $grey-dk-100 !important;\n}\n\n.bg-grey-dk-200 {\n background-color: $grey-dk-200 !important;\n}\n\n.bg-grey-dk-250 {\n background-color: $grey-dk-250 !important;\n}\n\n.bg-grey-dk-300 {\n background-color: $grey-dk-300 !important;\n}\n\n.bg-grey-lt-000 {\n background-color: $grey-lt-000 !important;\n}\n\n.bg-grey-lt-100 {\n background-color: $grey-lt-100 !important;\n}\n\n.bg-grey-lt-200 {\n background-color: $grey-lt-200 !important;\n}\n\n.bg-grey-lt-300 {\n background-color: $grey-lt-300 !important;\n}\n\n.bg-blue-000 {\n background-color: $blue-000 !important;\n}\n\n.bg-blue-100 {\n background-color: $blue-100 !important;\n}\n\n.bg-blue-200 {\n background-color: $blue-200 !important;\n}\n\n.bg-blue-300 {\n background-color: $blue-300 !important;\n}\n\n.bg-green-000 {\n background-color: $green-000 !important;\n}\n\n.bg-green-100 {\n background-color: $green-100 !important;\n}\n\n.bg-green-200 {\n background-color: $green-200 !important;\n}\n\n.bg-green-300 {\n background-color: $green-300 !important;\n}\n\n.bg-purple-000 {\n background-color: $purple-000 !important;\n}\n\n.bg-purple-100 {\n background-color: $purple-100 !important;\n}\n\n.bg-purple-200 {\n background-color: $purple-200 !important;\n}\n\n.bg-purple-300 {\n background-color: $purple-300 !important;\n}\n\n.bg-yellow-000 {\n background-color: $yellow-000 !important;\n}\n\n.bg-yellow-100 {\n background-color: $yellow-100 !important;\n}\n\n.bg-yellow-200 {\n background-color: $yellow-200 !important;\n}\n\n.bg-yellow-300 {\n background-color: $yellow-300 !important;\n}\n\n.bg-red-000 {\n background-color: $red-000 !important;\n}\n\n.bg-red-100 {\n background-color: $red-100 !important;\n}\n\n.bg-red-200 {\n background-color: $red-200 !important;\n}\n\n.bg-red-300 {\n background-color: $red-300 !important;\n}\n","// Utility classes for layout\n\n// Display\n\n.d-block {\n display: block !important;\n}\n\n.d-flex {\n display: flex !important;\n}\n\n.d-inline {\n display: inline !important;\n}\n\n.d-inline-block {\n display: inline-block !important;\n}\n\n.d-none {\n display: none !important;\n}\n\n// Screenreader-only\n\n.sr-only {\n position: absolute;\n width: 1px;\n height: 1px;\n padding: 0;\n margin: -1px;\n overflow: hidden;\n clip: rect(0, 0, 0, 0);\n white-space: nowrap;\n border-width: 0;\n}\n\n@each $media-query in map-keys($media-queries) {\n @for $i from 1 through length($spacers) {\n @include mq($media-query) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .d-sm-block, .d-md-none, .d-lg-inline\n .d-#{$media-query}-block {\n display: block !important;\n }\n .d-#{$media-query}-flex {\n display: flex !important;\n }\n .d-#{$media-query}-inline {\n display: inline !important;\n }\n .d-#{$media-query}-inline-block {\n display: inline-block !important;\n }\n .d-#{$media-query}-none {\n display: none !important;\n }\n }\n }\n}\n\n// Horizontal alignment\n\n.float-left {\n float: left !important;\n}\n\n.float-right {\n float: right !important;\n}\n\n.flex-justify-start {\n justify-content: flex-start !important;\n}\n\n.flex-justify-end {\n justify-content: flex-end !important;\n}\n\n.flex-justify-between {\n justify-content: space-between !important;\n}\n\n.flex-justify-around {\n justify-content: space-around !important;\n}\n\n// Vertical alignment\n\n.v-align-baseline {\n vertical-align: baseline !important;\n}\n\n.v-align-bottom {\n vertical-align: bottom !important;\n}\n\n.v-align-middle {\n vertical-align: middle !important;\n}\n\n.v-align-text-bottom {\n vertical-align: text-bottom !important;\n}\n\n.v-align-text-top {\n vertical-align: text-top !important;\n}\n\n.v-align-top {\n vertical-align: top !important;\n}\n","// Utility classes for typography\n\n.fs-1 {\n @include fs-1;\n}\n\n.fs-2 {\n @include fs-2;\n}\n\n.fs-3 {\n @include fs-3;\n}\n\n.fs-4 {\n @include fs-4;\n}\n\n.fs-5 {\n @include fs-5;\n}\n\n.fs-6 {\n @include fs-6;\n}\n\n.fs-7 {\n @include fs-7;\n}\n\n.fs-8 {\n @include fs-8;\n}\n\n.fs-9 {\n @include fs-9;\n}\n\n.fs-10 {\n @include fs-10;\n}\n\n.fw-300 {\n font-weight: 300 !important;\n}\n\n.fw-400 {\n font-weight: 400 !important;\n}\n\n.fw-500 {\n font-weight: 500 !important;\n}\n\n.fw-700 {\n font-weight: 700 !important;\n}\n\n.lh-0 {\n line-height: 0 !important;\n}\n\n.lh-default {\n line-height: $body-line-height;\n}\n\n.lh-tight {\n line-height: $body-heading-line-height;\n}\n\n.ls-5 {\n letter-spacing: 0.05em !important;\n}\n\n.ls-10 {\n letter-spacing: 0.1em !important;\n}\n\n.ls-0 {\n letter-spacing: 0 !important;\n}\n\n.text-uppercase {\n text-transform: uppercase !important;\n}\n","// Utility classes for lists\n\n// stylelint-disable selector-max-type\n\n.list-style-none {\n padding: 0 !important;\n margin: 0 !important;\n list-style: none !important;\n\n li {\n &::before {\n display: none !important;\n }\n }\n}\n","// Utility classes for margins and padding\n\n// stylelint-disable block-opening-brace-space-after, block-opening-brace-space-before\n\n// Margin spacer utilities\n\n.mx-auto {\n margin-right: auto !important;\n margin-left: auto !important;\n}\n\n@for $i from 1 through length($spacers) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .m-0, .m-1, .m-2...\n .m-#{$scale} {\n margin: #{$size} !important;\n }\n .mt-#{$scale} {\n margin-top: #{$size} !important;\n }\n .mr-#{$scale} {\n margin-right: #{$size} !important;\n }\n .mb-#{$scale} {\n margin-bottom: #{$size} !important;\n }\n .ml-#{$scale} {\n margin-left: #{$size} !important;\n }\n\n .mx-#{$scale} {\n margin-right: #{$size} !important;\n margin-left: #{$size} !important;\n }\n\n .my-#{$scale} {\n margin-top: #{$size} !important;\n margin-bottom: #{$size} !important;\n }\n\n .mxn-#{$scale} {\n margin-right: -#{$size} !important;\n margin-left: -#{$size} !important;\n }\n .mx-#{$scale}-auto {\n margin-right: auto !important;\n margin-left: auto !important;\n }\n}\n\n@each $media-query in map-keys($media-queries) {\n @for $i from 1 through length($spacers) {\n @include mq($media-query) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .m-sm-0, .m-md-1, .m-lg-2...\n .m-#{$media-query}-#{$scale} {\n margin: #{$size} !important;\n }\n .mt-#{$media-query}-#{$scale} {\n margin-top: #{$size} !important;\n }\n .mr-#{$media-query}-#{$scale} {\n margin-right: #{$size} !important;\n }\n .mb-#{$media-query}-#{$scale} {\n margin-bottom: #{$size} !important;\n }\n .ml-#{$media-query}-#{$scale} {\n margin-left: #{$size} !important;\n }\n\n .mx-#{$media-query}-#{$scale} {\n margin-right: #{$size} !important;\n margin-left: #{$size} !important;\n }\n\n .my-#{$media-query}-#{$scale} {\n margin-top: #{$size} !important;\n margin-bottom: #{$size} !important;\n }\n\n .mxn-#{$media-query}-#{$scale} {\n margin-right: -#{$size} !important;\n margin-left: -#{$size} !important;\n }\n }\n }\n}\n\n// Padding spacer utilities\n\n@for $i from 1 through length($spacers) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .p-0, .p-1, .p-2...\n .p-#{$scale} {\n padding: #{$size} !important;\n }\n .pt-#{$scale} {\n padding-top: #{$size} !important;\n }\n .pr-#{$scale} {\n padding-right: #{$size} !important;\n }\n .pb-#{$scale} {\n padding-bottom: #{$size} !important;\n }\n .pl-#{$scale} {\n padding-left: #{$size} !important;\n }\n\n .px-#{$scale} {\n padding-right: #{$size} !important;\n padding-left: #{$size} !important;\n }\n\n .py-#{$scale} {\n padding-top: #{$size} !important;\n padding-bottom: #{$size} !important;\n }\n}\n\n@each $media-query in map-keys($media-queries) {\n @include mq($media-query) {\n @for $i from 1 through length($spacers) {\n $size: #{map-get($spacers, sp-#{$i - 1})};\n $scale: #{$i - 1};\n\n // .p-sm-0, .p-md-1, .p-lg-2...\n .p-#{$media-query}-#{$scale} {\n padding: #{$size} !important;\n }\n .pt-#{$media-query}-#{$scale} {\n padding-top: #{$size} !important;\n }\n .pr-#{$media-query}-#{$scale} {\n padding-right: #{$size} !important;\n }\n .pb-#{$media-query}-#{$scale} {\n padding-bottom: #{$size} !important;\n }\n .pl-#{$media-query}-#{$scale} {\n padding-left: #{$size} !important;\n }\n\n .px-#{$media-query}-#{$scale} {\n padding-right: #{$size} !important;\n padding-left: #{$size} !important;\n }\n\n .py-#{$media-query}-#{$scale} {\n padding-top: #{$size} !important;\n padding-bottom: #{$size} !important;\n }\n }\n }\n}\n","// stylelint-disable selector-max-specificity, selector-max-id, selector-max-type, selector-no-qualifying-type\n\n@media print {\n .site-footer,\n .site-button,\n #edit-this-page,\n #back-to-top,\n .site-nav,\n .main-header {\n display: none !important;\n }\n\n hr {\n margin-top: 1rem;\n margin-bottom: 1rem;\n }\n\n .side-bar {\n width: 100%;\n height: auto;\n border-right: 0 !important;\n }\n\n .site-header {\n border-bottom: 1px solid $border-color;\n }\n\n .site-title {\n font-size: 1rem !important;\n font-weight: 700 !important;\n }\n\n .text-small {\n font-size: 8pt !important;\n }\n\n pre.highlight {\n border: 1px solid $border-color;\n }\n\n .main {\n max-width: none;\n margin-left: 0;\n }\n}\n","// Skipnav\n// Skip to main content\n\na.skip-to-main {\n left: -999px;\n position: absolute;\n top: auto;\n width: 1px;\n height: 1px;\n overflow: hidden;\n z-index: -999;\n}\n\na.skip-to-main:focus,\na.skip-to-main:active {\n color: $link-color;\n background-color: $body-background-color;\n left: auto;\n top: auto;\n width: 30%;\n height: auto;\n overflow: auto;\n margin: 10px 35%;\n padding: 5px;\n border-radius: 15px;\n border: 4px solid $btn-primary-color;\n text-align: center;\n font-size: 1.2em;\n z-index: 999;\n}\n","\n@import \"./support/support\";\n@import \"./custom/setup\";\n@import \"./color_schemes/light\";\n\n@import \"./color_schemes/meshtastic\";\n\n@import \"./modules\";\ndiv.opaque {\n background-color: $body-background-color;\n}\n\np.tip, blockquote.tip {\n border: 1px $green-000 solid;\n border-left: $border-radius solid $green-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n \n &::before {\n color: $green-300;\n content: \"Tip\";\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n \n > .tip-title {\n color: $green-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\np.tip-title, blockquote.tip-title {\n border: 1px $green-000 solid;\n border-left: $border-radius solid $green-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n > p:first-child {\n margin-top: 0;\n margin-bottom: 0;\n color: $green-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\nblockquote.tip {\n margin-left: 0;\n margin-right: 0;\n\n > p:first-child {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\nblockquote.tip-title {\n margin-left: 0;\n margin-right: 0;\n\n > p:nth-child(2) {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\n\n\np.note, blockquote.note {\n border: 1px $blue-000 solid;\n border-left: $border-radius solid $blue-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n \n &::before {\n color: $blue-300;\n content: \"Note\";\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n \n > .note-title {\n color: $blue-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\np.note-title, blockquote.note-title {\n border: 1px $blue-000 solid;\n border-left: $border-radius solid $blue-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n > p:first-child {\n margin-top: 0;\n margin-bottom: 0;\n color: $blue-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\nblockquote.note {\n margin-left: 0;\n margin-right: 0;\n\n > p:first-child {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\nblockquote.note-title {\n margin-left: 0;\n margin-right: 0;\n\n > p:nth-child(2) {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\n\n\np.warning, blockquote.warning {\n border: 1px $yellow-000 solid;\n border-left: $border-radius solid $yellow-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n \n &::before {\n color: $yellow-300;\n content: \"Warning\";\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n \n > .warning-title {\n color: $yellow-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\np.warning-title, blockquote.warning-title {\n border: 1px $yellow-000 solid;\n border-left: $border-radius solid $yellow-300;\n border-radius: $border-radius;\n box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);\n padding: .8rem;\n > p:first-child {\n margin-top: 0;\n margin-bottom: 0;\n color: $yellow-300;\n display: block;\n font-weight: bold;\n text-transform: uppercase;\n font-size: .75em;\n padding-bottom: .125rem;\n }\n}\n\nblockquote.warning {\n margin-left: 0;\n margin-right: 0;\n\n > p:first-child {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\nblockquote.warning-title {\n margin-left: 0;\n margin-right: 0;\n\n > p:nth-child(2) {\n margin-top: 0;\n }\n\n > p:last-child {\n margin-bottom: 0;\n }\n}\n\n\n@import \"./custom/custom\";\n\n\n"],"file":"just-the-docs-meshtastic.css"} \ No newline at end of file diff --git a/main/assets/js/search-data.json b/main/assets/js/search-data.json index 3bb9504a9a..1dc9e70c2a 100644 --- a/main/assets/js/search-data.json +++ b/main/assets/js/search-data.json @@ -8023,7 +8023,7 @@ },"1146": { "doc": "Local Mesh Discovery", "title": "Manual exploration", - "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Trasovanie . Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It’s the single most useful tool for debugging connectivity problems. Running a Traceroute . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | Weak link — this relay segment is fragile | . | Many hops (4+) | Long path — consider repositioning a node to shorten it | . | Different path on retry | Mesh is adapting — multiple routes exist (this is good!) | . 💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network. Troubleshooting with Traceroute . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Informácia o susedoch . The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh. Enabling Neighbor Info . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding new nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes. | . Assessing connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ", + "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Trasovanie . Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It’s the single most useful tool for debugging connectivity problems. Running a Traceroute . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | Weak link — this relay segment is fragile | . | Many hops (4+) | Long path — consider repositioning a node to shorten it | . | Different path on retry | Mesh is adapting — multiple routes exist (this is good!) | . 💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network. Troubleshooting with Traceroute . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Informácia o susedoch . The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh. Enabling Neighbor Info . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update Interval. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding new nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes. | . Assessing connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ", "url": "/Meshtastic-Android/main/sk-rSK/user/discovery.html#manual-exploration", "relUrl": "/sk-rSK/user/discovery.html#manual-exploration" @@ -8065,7 +8065,7 @@ },"1152": { "doc": "Local Mesh Discovery", "title": "Manual exploration", - "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Traceroute . Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It’s the single most useful tool for debugging connectivity problems. Running a Traceroute . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | Weak link — this relay segment is fragile | . | Many hops (4+) | Long path — consider repositioning a node to shorten it | . | Different path on retry | Mesh is adapting — multiple routes exist (this is good!) | . 💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network. Troubleshooting with Traceroute . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Neighbor Info . The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh. Enabling Neighbor Info . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding new nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes. | . Assessing connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ", + "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Traceroute . Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It’s the single most useful tool for debugging connectivity problems. Running a Traceroute . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | Weak link — this relay segment is fragile | . | Many hops (4+) | Long path — consider repositioning a node to shorten it | . | Different path on retry | Mesh is adapting — multiple routes exist (this is good!) | . 💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network. Troubleshooting with Traceroute . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Neighbor Info . The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh. Enabling Neighbor Info . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update Interval. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding new nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes. | . Assessing connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ", "url": "/Meshtastic-Android/main/be-rBY/user/discovery.html#manual-exploration", "relUrl": "/be-rBY/user/discovery.html#manual-exploration" @@ -8107,7 +8107,7 @@ },"1158": { "doc": "Discovery della mesh locale", "title": "Manual exploration", - "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Traceroute . Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It’s the single most useful tool for debugging connectivity problems. Running a Traceroute . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | Weak link — this relay segment is fragile | . | Many hops (4+) | Long path — consider repositioning a node to shorten it | . | Different path on retry | Mesh is adapting — multiple routes exist (this is good!) | . 💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network. Troubleshooting with Traceroute . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Informazioni Vicinato . The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh. Enabling Neighbor Info . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding new nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes. | . Assessing connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ", + "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Traceroute . Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It’s the single most useful tool for debugging connectivity problems. Running a Traceroute . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | Weak link — this relay segment is fragile | . | Many hops (4+) | Long path — consider repositioning a node to shorten it | . | Different path on retry | Mesh is adapting — multiple routes exist (this is good!) | . 💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network. Troubleshooting with Traceroute . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Informazioni Vicinato . The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh. Enabling Neighbor Info . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update Interval. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding new nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes. | . Assessing connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ", "url": "/Meshtastic-Android/main/it-rIT/user/discovery.html#manual-exploration", "relUrl": "/it-rIT/user/discovery.html#manual-exploration" @@ -8149,7 +8149,7 @@ },"1164": { "doc": "Local Mesh Discovery", "title": "Manual exploration", - "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Traceroute . Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It’s the single most useful tool for debugging connectivity problems. Running a Traceroute . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | Weak link — this relay segment is fragile | . | Many hops (4+) | Long path — consider repositioning a node to shorten it | . | Different path on retry | Mesh is adapting — multiple routes exist (this is good!) | . 💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network. Troubleshooting with Traceroute . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Información de Vecinos . The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh. Enabling Neighbor Info . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding new nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes. | . Assessing connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ", + "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Traceroute . Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It’s the single most useful tool for debugging connectivity problems. Running a Traceroute . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | Weak link — this relay segment is fragile | . | Many hops (4+) | Long path — consider repositioning a node to shorten it | . | Different path on retry | Mesh is adapting — multiple routes exist (this is good!) | . 💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network. Troubleshooting with Traceroute . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Información de Vecinos . The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh. Enabling Neighbor Info . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update Interval. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding new nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes. | . Assessing connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ", "url": "/Meshtastic-Android/main/es-rES/user/discovery.html#manual-exploration", "relUrl": "/es-rES/user/discovery.html#manual-exploration" @@ -8191,7 +8191,7 @@ },"1170": { "doc": "Local Mesh Discovery", "title": "Manual exploration", - "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Pot . Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It’s the single most useful tool for debugging connectivity problems. Running a Traceroute . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | Weak link — this relay segment is fragile | . | Many hops (4+) | Long path — consider repositioning a node to shorten it | . | Different path on retry | Mesh is adapting — multiple routes exist (this is good!) | . 💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network. Troubleshooting with Traceroute . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Neighbor Info . The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh. Enabling Neighbor Info . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding new nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes. | . Assessing connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ", + "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Pot . Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It’s the single most useful tool for debugging connectivity problems. Running a Traceroute . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | Weak link — this relay segment is fragile | . | Many hops (4+) | Long path — consider repositioning a node to shorten it | . | Different path on retry | Mesh is adapting — multiple routes exist (this is good!) | . 💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network. Troubleshooting with Traceroute . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Neighbor Info . The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh. Enabling Neighbor Info . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update Interval. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding new nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes. | . Assessing connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ", "url": "/Meshtastic-Android/main/sl-rSI/user/discovery.html#manual-exploration", "relUrl": "/sl-rSI/user/discovery.html#manual-exploration" @@ -8233,7 +8233,7 @@ },"1176": { "doc": "Local Mesh Discovery", "title": "Manual exploration", - "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Traceroute . Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It’s the single most useful tool for debugging connectivity problems. Running a Traceroute . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | Weak link — this relay segment is fragile | . | Many hops (4+) | Long path — consider repositioning a node to shorten it | . | Different path on retry | Mesh is adapting — multiple routes exist (this is good!) | . 💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network. Troubleshooting with Traceroute . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Neighbor Info . The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh. Enabling Neighbor Info . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding new nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes. | . Assessing connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ", + "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Traceroute . Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It’s the single most useful tool for debugging connectivity problems. Running a Traceroute . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | Weak link — this relay segment is fragile | . | Many hops (4+) | Long path — consider repositioning a node to shorten it | . | Different path on retry | Mesh is adapting — multiple routes exist (this is good!) | . 💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network. Troubleshooting with Traceroute . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Neighbor Info . The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh. Enabling Neighbor Info . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update Interval. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding new nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes. | . Assessing connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ", "url": "/Meshtastic-Android/main/no-rNO/user/discovery.html#manual-exploration", "relUrl": "/no-rNO/user/discovery.html#manual-exploration" @@ -8275,7 +8275,7 @@ },"1182": { "doc": "Local Mesh Discovery", "title": "Manual exploration", - "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Traceroute . Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It’s the single most useful tool for debugging connectivity problems. Running a Traceroute . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | Weak link — this relay segment is fragile | . | Many hops (4+) | Long path — consider repositioning a node to shorten it | . | Different path on retry | Mesh is adapting — multiple routes exist (this is good!) | . 💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network. Troubleshooting with Traceroute . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Szomszéd-információ . The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh. Enabling Neighbor Info . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding new nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes. | . Assessing connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ", + "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Traceroute . Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It’s the single most useful tool for debugging connectivity problems. Running a Traceroute . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | Weak link — this relay segment is fragile | . | Many hops (4+) | Long path — consider repositioning a node to shorten it | . | Different path on retry | Mesh is adapting — multiple routes exist (this is good!) | . 💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network. Troubleshooting with Traceroute . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Szomszéd-információ . The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh. Enabling Neighbor Info . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update Interval. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding new nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes. | . Assessing connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ", "url": "/Meshtastic-Android/main/hu-rHU/user/discovery.html#manual-exploration", "relUrl": "/hu-rHU/user/discovery.html#manual-exploration" @@ -8317,7 +8317,7 @@ },"1188": { "doc": "Локальное обнаружение сети", "title": "Manual exploration", - "content": "The following tools are available at any time from the node list and node detail screens. Используйте их для исследования конкретных путей и построения картины топологии — вместе с полным сканированием или вместо него. Трассировка маршрута . Трассировка показывает точный путь, который сообщение проходит от твоей ноды до любой другой ноды в сети. Это самый полезный инструмент для отладки проблем с подключением. Выполнение трассировки . | Перейди в Ноды и коснись ноды, которую ты хочешь отследить. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . Результат трассировки выглядит так: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | На что обращать внимание | Что это значит | . | All hops show Good SNR (green) | Здоровый путь — сообщения идут без сбоев | . | One hop shows a poor SNR (orange or red) | Слабое звено — этот сегмент ретрансляции хрупкий | . | Много хопов (4+) | Длинный путь — подумай о перемещении ноды для его сокращения | . | Другой путь при повторе | Сеть адаптируется — существуют несколько маршрутов (это хорошо!) | . 💡 Совет: Запусти трассировку несколько раз в течение нескольких минут. Если путь изменяется, у твоей сети есть лишние маршруты — признак хорошо связанной сети. Устранение неполадок с трассировкой . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Проверь, что обе ноды имеют хотя бы один канал с одинаковым ключом шифрования. | Время ожидания трассировки истекло — путь может быть слишком длинным (превышен лимит хопов) или нода ретрансляции перегружена. Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Асимметричные маршруты — трассировка от A→B может проходить по другому пути, чем B→A. This is normal — radio propagation isn’t always symmetric. | . Информация об окружении . Модуль информации о соседях позволяет каждой ноде передавать список нод, которые она может слышать напрямую (на расстоянии одного хопа). Когда несколько нод делятся своими списками соседей, ты можешь составить карту топологии всей mesh-сети. Включение информации о соседях . | Navigate to Settings → Module configuration → Neighbor Info. | Включение модуля | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Другие ноды с включённым модулем информации о соседях делают то же самое. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | Каждая запись о соседе показывает ноду, которая была услышана напрямую, и качество её сигнала. | Объединяйте данные о соседях от нескольких нод, чтобы понять полную топологию mesh-сети. | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . Сам по себе список нод — мощный инструмент обнаружения, если ты эффективно будешь использовать его возможности фильтрации и сортировки. Finding new nodes . | Сортируйте по “Последнему приёму”, чтобы увидеть вверху списка ноды, активные в последнее время. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes. | . Assessing connectivity . | Сортируйте по «Хопам», чтобы видеть, какие ноды доступны напрямую (0 хопов), а какие — через ретрансляцию. | Сортируйте по “Расстоянию”, чтобы найти близлежащие ноды и убедиться, что они доступны. | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Отключите “Исключить инфраструктуру”, чтобы увидеть ноды Router, Router Late и Client Base. | Проверьте качество их сигнала и время последнего приёма, чтобы убедиться, что твои ноды инфраструктуры работают исправно. | . См. раздел Ноды для получения полной информации о параметрах фильтрации и сортировки. ", + "content": "The following tools are available at any time from the node list and node detail screens. Используйте их для исследования конкретных путей и построения картины топологии — вместе с полным сканированием или вместо него. Трассировка маршрута . Трассировка показывает точный путь, который сообщение проходит от твоей ноды до любой другой ноды в сети. Это самый полезный инструмент для отладки проблем с подключением. Выполнение трассировки . | Перейди в Ноды и коснись ноды, которую ты хочешь отследить. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . Результат трассировки выглядит так: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | На что обращать внимание | Что это значит | . | All hops show Good SNR (green) | Здоровый путь — сообщения идут без сбоев | . | One hop shows a poor SNR (orange or red) | Слабое звено — этот сегмент ретрансляции хрупкий | . | Много хопов (4+) | Длинный путь — подумай о перемещении ноды для его сокращения | . | Другой путь при повторе | Сеть адаптируется — существуют несколько маршрутов (это хорошо!) | . 💡 Совет: Запусти трассировку несколько раз в течение нескольких минут. Если путь изменяется, у твоей сети есть лишние маршруты — признак хорошо связанной сети. Устранение неполадок с трассировкой . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Проверь, что обе ноды имеют хотя бы один канал с одинаковым ключом шифрования. | Время ожидания трассировки истекло — путь может быть слишком длинным (превышен лимит хопов) или нода ретрансляции перегружена. Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Асимметричные маршруты — трассировка от A→B может проходить по другому пути, чем B→A. This is normal — radio propagation isn’t always symmetric. | . Информация об окружении . Модуль информации о соседях позволяет каждой ноде передавать список нод, которые она может слышать напрямую (на расстоянии одного хопа). Когда несколько нод делятся своими списками соседей, ты можешь составить карту топологии всей mesh-сети. Включение информации о соседях . | Navigate to Settings → Module configuration → Neighbor Info. | Включение модуля | Set Update Interval. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Другие ноды с включённым модулем информации о соседях делают то же самое. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | Каждая запись о соседе показывает ноду, которая была услышана напрямую, и качество её сигнала. | Объединяйте данные о соседях от нескольких нод, чтобы понять полную топологию mesh-сети. | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . Сам по себе список нод — мощный инструмент обнаружения, если ты эффективно будешь использовать его возможности фильтрации и сортировки. Finding new nodes . | Сортируйте по “Последнему приёму”, чтобы увидеть вверху списка ноды, активные в последнее время. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes. | . Assessing connectivity . | Сортируйте по «Хопам», чтобы видеть, какие ноды доступны напрямую (0 хопов), а какие — через ретрансляцию. | Сортируйте по “Расстоянию”, чтобы найти близлежащие ноды и убедиться, что они доступны. | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Отключите “Исключить инфраструктуру”, чтобы увидеть ноды Router, Router Late и Client Base. | Проверьте качество их сигнала и время последнего приёма, чтобы убедиться, что твои ноды инфраструктуры работают исправно. | . См. раздел Ноды для получения полной информации о параметрах фильтрации и сортировки. ", "url": "/Meshtastic-Android/main/ru-rRU/user/discovery.html#manual-exploration", "relUrl": "/ru-rRU/user/discovery.html#manual-exploration" @@ -8359,7 +8359,7 @@ },"1194": { "doc": "Vyhledávání zařízení v místní mesh síti", "title": "Manual exploration", - "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Traceroute . Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It’s the single most useful tool for debugging connectivity problems. Running a Traceroute . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | Weak link — this relay segment is fragile | . | Many hops (4+) | Long path — consider repositioning a node to shorten it | . | Different path on retry | Mesh is adapting — multiple routes exist (this is good!) | . 💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network. Troubleshooting with Traceroute . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Informace o sousedech . The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh. Enabling Neighbor Info . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding new nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes. | . Assessing connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ", + "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Traceroute . Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It’s the single most useful tool for debugging connectivity problems. Running a Traceroute . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | Weak link — this relay segment is fragile | . | Many hops (4+) | Long path — consider repositioning a node to shorten it | . | Different path on retry | Mesh is adapting — multiple routes exist (this is good!) | . 💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network. Troubleshooting with Traceroute . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Informace o sousedech . The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh. Enabling Neighbor Info . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update Interval. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding new nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes. | . Assessing connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ", "url": "/Meshtastic-Android/main/cs-rCZ/user/discovery.html#manual-exploration", "relUrl": "/cs-rCZ/user/discovery.html#manual-exploration" @@ -8401,7 +8401,7 @@ },"1200": { "doc": "Local Mesh Discovery", "title": "Manual exploration", - "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Трасиране на маршрут . Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It’s the single most useful tool for debugging connectivity problems. Running a Traceroute . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | Weak link — this relay segment is fragile | . | Many hops (4+) | Long path — consider repositioning a node to shorten it | . | Different path on retry | Mesh is adapting — multiple routes exist (this is good!) | . 💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network. Troubleshooting with Traceroute . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Neighbor Info . The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh. Enabling Neighbor Info . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding new nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes. | . Assessing connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ", + "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Трасиране на маршрут . Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It’s the single most useful tool for debugging connectivity problems. Running a Traceroute . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | Weak link — this relay segment is fragile | . | Many hops (4+) | Long path — consider repositioning a node to shorten it | . | Different path on retry | Mesh is adapting — multiple routes exist (this is good!) | . 💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network. Troubleshooting with Traceroute . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Neighbor Info . The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh. Enabling Neighbor Info . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update Interval. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding new nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes. | . Assessing connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ", "url": "/Meshtastic-Android/main/bg-rBG/user/discovery.html#manual-exploration", "relUrl": "/bg-rBG/user/discovery.html#manual-exploration" @@ -8443,7 +8443,7 @@ },"1206": { "doc": "Local Mesh Discovery", "title": "Manual exploration", - "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Céim rianadóireachta . Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It’s the single most useful tool for debugging connectivity problems. Running a Traceroute . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | Weak link — this relay segment is fragile | . | Many hops (4+) | Long path — consider repositioning a node to shorten it | . | Different path on retry | Mesh is adapting — multiple routes exist (this is good!) | . 💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network. Troubleshooting with Traceroute . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Neighbor Info . The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh. Enabling Neighbor Info . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding new nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes. | . Assessing connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ", + "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Céim rianadóireachta . Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It’s the single most useful tool for debugging connectivity problems. Running a Traceroute . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | Weak link — this relay segment is fragile | . | Many hops (4+) | Long path — consider repositioning a node to shorten it | . | Different path on retry | Mesh is adapting — multiple routes exist (this is good!) | . 💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network. Troubleshooting with Traceroute . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Neighbor Info . The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh. Enabling Neighbor Info . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update Interval. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding new nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes. | . Assessing connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ", "url": "/Meshtastic-Android/main/ga-rIE/user/discovery.html#manual-exploration", "relUrl": "/ga-rIE/user/discovery.html#manual-exploration" @@ -8485,7 +8485,7 @@ },"1212": { "doc": "Découverte de maille locale", "title": "Manual exploration", - "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Traceroute . Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It’s the single most useful tool for debugging connectivity problems. Running a Traceroute . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | Weak link — this relay segment is fragile | . | Many hops (4+) | Long path — consider repositioning a node to shorten it | . | Different path on retry | Mesh is adapting — multiple routes exist (this is good!) | . 💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network. Troubleshooting with Traceroute . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Informations sur les voisins . The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh. Enabling Neighbor Info . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding new nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes. | . Assessing connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ", + "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Traceroute . Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It’s the single most useful tool for debugging connectivity problems. Running a Traceroute . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | Weak link — this relay segment is fragile | . | Many hops (4+) | Long path — consider repositioning a node to shorten it | . | Different path on retry | Mesh is adapting — multiple routes exist (this is good!) | . 💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network. Troubleshooting with Traceroute . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Informations sur les voisins . The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh. Enabling Neighbor Info . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update Interval. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding new nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes. | . Assessing connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ", "url": "/Meshtastic-Android/main/fr-rCA/user/discovery.html#manual-exploration", "relUrl": "/fr-rCA/user/discovery.html#manual-exploration" @@ -8527,7 +8527,7 @@ },"1218": { "doc": "Local Mesh Discovery", "title": "Manual exploration", - "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Праћење руте . Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It’s the single most useful tool for debugging connectivity problems. Running a Traceroute . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | Weak link — this relay segment is fragile | . | Many hops (4+) | Long path — consider repositioning a node to shorten it | . | Different path on retry | Mesh is adapting — multiple routes exist (this is good!) | . 💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network. Troubleshooting with Traceroute . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Neighbor Info . The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh. Enabling Neighbor Info . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding new nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes. | . Assessing connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ", + "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Праћење руте . Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It’s the single most useful tool for debugging connectivity problems. Running a Traceroute . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | Weak link — this relay segment is fragile | . | Many hops (4+) | Long path — consider repositioning a node to shorten it | . | Different path on retry | Mesh is adapting — multiple routes exist (this is good!) | . 💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network. Troubleshooting with Traceroute . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Neighbor Info . The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh. Enabling Neighbor Info . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update Interval. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding new nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes. | . Assessing connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ", "url": "/Meshtastic-Android/main/srp/user/discovery.html#manual-exploration", "relUrl": "/srp/user/discovery.html#manual-exploration" @@ -8569,7 +8569,7 @@ },"1224": { "doc": "Local Mesh Discovery", "title": "Manual exploration", - "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Traçar ruta . Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It’s the single most useful tool for debugging connectivity problems. Running a Traceroute . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | Weak link — this relay segment is fragile | . | Many hops (4+) | Long path — consider repositioning a node to shorten it | . | Different path on retry | Mesh is adapting — multiple routes exist (this is good!) | . 💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network. Troubleshooting with Traceroute . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Neighbor Info . The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh. Enabling Neighbor Info . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding new nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes. | . Assessing connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ", + "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Traçar ruta . Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It’s the single most useful tool for debugging connectivity problems. Running a Traceroute . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | Weak link — this relay segment is fragile | . | Many hops (4+) | Long path — consider repositioning a node to shorten it | . | Different path on retry | Mesh is adapting — multiple routes exist (this is good!) | . 💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network. Troubleshooting with Traceroute . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Neighbor Info . The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh. Enabling Neighbor Info . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update Interval. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding new nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes. | . Assessing connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ", "url": "/Meshtastic-Android/main/ca-rES/user/discovery.html#manual-exploration", "relUrl": "/ca-rES/user/discovery.html#manual-exploration" @@ -8611,7 +8611,7 @@ },"1230": { "doc": "Local Mesh Discovery", "title": "Manual exploration", - "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. 추적 루트 . Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It’s the single most useful tool for debugging connectivity problems. Running a Traceroute . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | Weak link — this relay segment is fragile | . | Many hops (4+) | Long path — consider repositioning a node to shorten it | . | Different path on retry | Mesh is adapting — multiple routes exist (this is good!) | . 💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network. Troubleshooting with Traceroute . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . 이웃 정보 . The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh. Enabling Neighbor Info . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding new nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes. | . Assessing connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ", + "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. 추적 루트 . Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It’s the single most useful tool for debugging connectivity problems. Running a Traceroute . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | Weak link — this relay segment is fragile | . | Many hops (4+) | Long path — consider repositioning a node to shorten it | . | Different path on retry | Mesh is adapting — multiple routes exist (this is good!) | . 💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network. Troubleshooting with Traceroute . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . 이웃 정보 . The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh. Enabling Neighbor Info . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update Interval. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding new nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes. | . Assessing connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ", "url": "/Meshtastic-Android/main/ko-rKR/user/discovery.html#manual-exploration", "relUrl": "/ko-rKR/user/discovery.html#manual-exploration" @@ -8653,7 +8653,7 @@ },"1236": { "doc": "Local Mesh Discovery", "title": "Manual exploration", - "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Traceroute (spåra rutt) . Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It’s the single most useful tool for debugging connectivity problems. Running a Traceroute . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | Weak link — this relay segment is fragile | . | Many hops (4+) | Long path — consider repositioning a node to shorten it | . | Different path on retry | Mesh is adapting — multiple routes exist (this is good!) | . 💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network. Troubleshooting with Traceroute . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Granninformation . The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh. Enabling Neighbor Info . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding new nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes. | . Assessing connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ", + "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Traceroute (spåra rutt) . Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It’s the single most useful tool for debugging connectivity problems. Running a Traceroute . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | Weak link — this relay segment is fragile | . | Many hops (4+) | Long path — consider repositioning a node to shorten it | . | Different path on retry | Mesh is adapting — multiple routes exist (this is good!) | . 💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network. Troubleshooting with Traceroute . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Granninformation . The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh. Enabling Neighbor Info . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update Interval. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding new nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes. | . Assessing connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ", "url": "/Meshtastic-Android/main/sv-rSE/user/discovery.html#manual-exploration", "relUrl": "/sv-rSE/user/discovery.html#manual-exploration" @@ -8695,7 +8695,7 @@ },"1242": { "doc": "Local Mesh Discovery", "title": "Manual exploration", - "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Traceroute . Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It’s the single most useful tool for debugging connectivity problems. Running a Traceroute . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | Weak link — this relay segment is fragile | . | Many hops (4+) | Long path — consider repositioning a node to shorten it | . | Different path on retry | Mesh is adapting — multiple routes exist (this is good!) | . 💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network. Troubleshooting with Traceroute . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Neighbor Info . The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh. Enabling Neighbor Info . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding new nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes. | . Assessing connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ", + "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Traceroute . Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It’s the single most useful tool for debugging connectivity problems. Running a Traceroute . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | Weak link — this relay segment is fragile | . | Many hops (4+) | Long path — consider repositioning a node to shorten it | . | Different path on retry | Mesh is adapting — multiple routes exist (this is good!) | . 💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network. Troubleshooting with Traceroute . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Neighbor Info . The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh. Enabling Neighbor Info . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update Interval. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding new nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes. | . Assessing connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ", "url": "/Meshtastic-Android/main/ht-rHT/user/discovery.html#manual-exploration", "relUrl": "/ht-rHT/user/discovery.html#manual-exploration" @@ -8737,7 +8737,7 @@ },"1248": { "doc": "Local Mesh Discovery", "title": "Manual exploration", - "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Праћење руте . Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It’s the single most useful tool for debugging connectivity problems. Running a Traceroute . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | Weak link — this relay segment is fragile | . | Many hops (4+) | Long path — consider repositioning a node to shorten it | . | Different path on retry | Mesh is adapting — multiple routes exist (this is good!) | . 💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network. Troubleshooting with Traceroute . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Neighbor Info . The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh. Enabling Neighbor Info . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding new nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes. | . Assessing connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ", + "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Праћење руте . Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It’s the single most useful tool for debugging connectivity problems. Running a Traceroute . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | Weak link — this relay segment is fragile | . | Many hops (4+) | Long path — consider repositioning a node to shorten it | . | Different path on retry | Mesh is adapting — multiple routes exist (this is good!) | . 💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network. Troubleshooting with Traceroute . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Neighbor Info . The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh. Enabling Neighbor Info . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update Interval. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding new nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes. | . Assessing connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ", "url": "/Meshtastic-Android/main/sr-rLatn/user/discovery.html#manual-exploration", "relUrl": "/sr-rLatn/user/discovery.html#manual-exploration" @@ -8779,7 +8779,7 @@ },"1254": { "doc": "Local Mesh Discovery", "title": "Manual exploration", - "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Traceroute . Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It’s the single most useful tool for debugging connectivity problems. Running a Traceroute . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | Weak link — this relay segment is fragile | . | Many hops (4+) | Long path — consider repositioning a node to shorten it | . | Different path on retry | Mesh is adapting — multiple routes exist (this is good!) | . 💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network. Troubleshooting with Traceroute . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Neighbor Info . The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh. Enabling Neighbor Info . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding new nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes. | . Assessing connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ", + "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Traceroute . Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It’s the single most useful tool for debugging connectivity problems. Running a Traceroute . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | Weak link — this relay segment is fragile | . | Many hops (4+) | Long path — consider repositioning a node to shorten it | . | Different path on retry | Mesh is adapting — multiple routes exist (this is good!) | . 💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network. Troubleshooting with Traceroute . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Neighbor Info . The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh. Enabling Neighbor Info . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update Interval. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding new nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes. | . Assessing connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ", "url": "/Meshtastic-Android/main/nl-rNL/user/discovery.html#manual-exploration", "relUrl": "/nl-rNL/user/discovery.html#manual-exploration" @@ -8821,7 +8821,7 @@ },"1260": { "doc": "Local Mesh Discovery", "title": "Manual exploration", - "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Маршрут . Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It’s the single most useful tool for debugging connectivity problems. Running a Traceroute . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | Weak link — this relay segment is fragile | . | Many hops (4+) | Long path — consider repositioning a node to shorten it | . | Different path on retry | Mesh is adapting — multiple routes exist (this is good!) | . 💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network. Troubleshooting with Traceroute . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Інформація про сусідів . The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh. Enabling Neighbor Info . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding new nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes. | . Assessing connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ", + "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Маршрут . Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It’s the single most useful tool for debugging connectivity problems. Running a Traceroute . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | Weak link — this relay segment is fragile | . | Many hops (4+) | Long path — consider repositioning a node to shorten it | . | Different path on retry | Mesh is adapting — multiple routes exist (this is good!) | . 💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network. Troubleshooting with Traceroute . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Інформація про сусідів . The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh. Enabling Neighbor Info . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update Interval. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding new nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes. | . Assessing connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ", "url": "/Meshtastic-Android/main/uk-rUA/user/discovery.html#manual-exploration", "relUrl": "/uk-rUA/user/discovery.html#manual-exploration" @@ -8863,7 +8863,7 @@ },"1266": { "doc": "Paikallisen mesh-verkon skannaus", "title": "Manual exploration", - "content": "Seuraavat työkalut ovat aina käytettävissä Radiot- ja Radion tiedot -näkymissä. Käytä niitä yksittäisten reittien tutkimiseen ja topologian muodostamiseen, joko osana skannausta tai sen sijaan. Reitinselvitys . Reitinselvitys näyttää tarkan polun, jota kautta viesti kulkee omalta radioltasi mihin tahansa toiseen verkon radioon. Se on yksittäisistä työkaluista hyödyllisin yhteysongelmien vianmääritykseen. Reitinselvityksen suorittaminen . | Siirry kohtaan Radiot ja napauta radiota, jota haluat jäljittää. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . Reitinselvityksen tulos näyttää tältä: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | Mitä kannattaa tarkkailla | Mitä se tarkoittaa | . | All hops show Good SNR (green) | Hyvä reitti — viestit kulkevat luotettavasti | . | One hop shows a poor SNR (orange or red) | Heikko yhteys — tämä välityssegmentti on haavoittuva | . | Useita hyppyjä (4+) | Pitkä reitti — harkitse radion siirtämistä sen lyhentämiseksi | . | Eri reitti uudelleenyrityksellä | Verkko mukautuu — useita reittejä on olemassa (tämä on hyvä!) | . Vinkki: Aja reitinselvitys useita kertoja muutaman minuutin aikana. Jos reitti muuttuu, verkossasi on varareittejä — merkki hyvin kytketystä verkosta. Reitinselvityksen vianmääritys . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Varmista, että molemmat radiot jakavat vähintään yhden kanavan samalla salausavaimella. | Reitinselvitys aikakatkaistu — reitti voi olla liian pitkä (ylittää hyppymäärärajan) tai välittäjä-radio on ruuhkautunut. Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Epäsymmetriset reitit — reitinselvitys A→B voi kulkea eri reittiä kuin B→A. This is normal — radio propagation isn’t always symmetric. | . Naapuritieto . Naapuritieto-moduuli antaa jokaisen radion lähettää listan radioista, jotka se voi kuulla suoraan (yhden hypyn päässä). Kun useat radiot jakavat naapurilistansa, voit muodostaa koko verkon topologian kartan. Naapuritiedon käyttöönotto . | Navigate to Settings → Module configuration → Neighbor Info. | Ota moduuli käyttöön. | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Myös muut radiot, joissa naapuritieto on käytössä, toimivat samalla tavalla. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | Jokainen naapurimerkintä näyttää radion, joka on kuultu suoraan, sekä sen signaalilaadun. | Yhdistä naapuritiedot useista radioista ymmärtääksesi koko mesh-verkon topologian. | . ℹ️ Huomautus: Naapuritieto lisää lähetysaikaa, koska jokainen toiminnon ottanut radio lähettää säännöllisesti naapuriluettelonsa. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . Radiolista on itsessään tehokas hakutyökalu, kun käytät sen suodatus- ja lajitteluominaisuuksia oikein. Finding new nodes . | Lajittele Viimeksi kuultu nähdäksesi viimeksi aktiiviset radiot ylimpänä. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes. | . Assessing connectivity . | Lajittele Hyppyjen määrä nähdäksesi mitkä radiot ovat suoraan tavoitettavissa (0 hyppyä) ja mitkä välitettyinä. | Lajittele Etäisyys löytääksesi lähellä olevat radiot ja varmistaaksesi niiden tavoitettavuuden. | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Poista Jätä infrastruktuuri pois käytöstä, jos haluat nähdä Router-, Router Late- ja Client Base -radiot. | Tarkista niiden signaalin laatu ja viimeksi kuultu -ajat varmistaaksesi, että infrastruktuuriradiot ovat kunnossa. | . Katso Radiot saadaksesi lisätietoa suodatus- ja lajitteluasetuksista. ", + "content": "Seuraavat työkalut ovat aina käytettävissä Radiot- ja Radion tiedot -näkymissä. Käytä niitä yksittäisten reittien tutkimiseen ja topologian muodostamiseen, joko osana skannausta tai sen sijaan. Reitinselvitys . Reitinselvitys näyttää tarkan polun, jota kautta viesti kulkee omalta radioltasi mihin tahansa toiseen verkon radioon. Se on yksittäisistä työkaluista hyödyllisin yhteysongelmien vianmääritykseen. Reitinselvityksen suorittaminen . | Siirry kohtaan Radiot ja napauta radiota, jota haluat jäljittää. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . Reitinselvityksen tulos näyttää tältä: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | Mitä kannattaa tarkkailla | Mitä se tarkoittaa | . | All hops show Good SNR (green) | Hyvä reitti — viestit kulkevat luotettavasti | . | One hop shows a poor SNR (orange or red) | Heikko yhteys — tämä välityssegmentti on haavoittuva | . | Useita hyppyjä (4+) | Pitkä reitti — harkitse radion siirtämistä sen lyhentämiseksi | . | Eri reitti uudelleenyrityksellä | Verkko mukautuu — useita reittejä on olemassa (tämä on hyvä!) | . Vinkki: Aja reitinselvitys useita kertoja muutaman minuutin aikana. Jos reitti muuttuu, verkossasi on varareittejä — merkki hyvin kytketystä verkosta. Reitinselvityksen vianmääritys . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Varmista, että molemmat radiot jakavat vähintään yhden kanavan samalla salausavaimella. | Reitinselvitys aikakatkaistu — reitti voi olla liian pitkä (ylittää hyppymäärärajan) tai välittäjä-radio on ruuhkautunut. Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Epäsymmetriset reitit — reitinselvitys A→B voi kulkea eri reittiä kuin B→A. This is normal — radio propagation isn’t always symmetric. | . Naapuritieto . Naapuritieto-moduuli antaa jokaisen radion lähettää listan radioista, jotka se voi kuulla suoraan (yhden hypyn päässä). Kun useat radiot jakavat naapurilistansa, voit muodostaa koko verkon topologian kartan. Naapuritiedon käyttöönotto . | Navigate to Settings → Module configuration → Neighbor Info. | Ota moduuli käyttöön. | Set Update Interval. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Myös muut radiot, joissa naapuritieto on käytössä, toimivat samalla tavalla. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | Jokainen naapurimerkintä näyttää radion, joka on kuultu suoraan, sekä sen signaalilaadun. | Yhdistä naapuritiedot useista radioista ymmärtääksesi koko mesh-verkon topologian. | . ℹ️ Huomautus: Naapuritieto lisää lähetysaikaa, koska jokainen toiminnon ottanut radio lähettää säännöllisesti naapuriluettelonsa. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . Radiolista on itsessään tehokas hakutyökalu, kun käytät sen suodatus- ja lajitteluominaisuuksia oikein. Finding new nodes . | Lajittele Viimeksi kuultu nähdäksesi viimeksi aktiiviset radiot ylimpänä. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes. | . Assessing connectivity . | Lajittele Hyppyjen määrä nähdäksesi mitkä radiot ovat suoraan tavoitettavissa (0 hyppyä) ja mitkä välitettyinä. | Lajittele Etäisyys löytääksesi lähellä olevat radiot ja varmistaaksesi niiden tavoitettavuuden. | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Poista Jätä infrastruktuuri pois käytöstä, jos haluat nähdä Router-, Router Late- ja Client Base -radiot. | Tarkista niiden signaalin laatu ja viimeksi kuultu -ajat varmistaaksesi, että infrastruktuuriradiot ovat kunnossa. | . Katso Radiot saadaksesi lisätietoa suodatus- ja lajitteluasetuksista. ", "url": "/Meshtastic-Android/main/fi-rFI/user/discovery.html#manual-exploration", "relUrl": "/fi-rFI/user/discovery.html#manual-exploration" @@ -8905,7 +8905,7 @@ },"1272": { "doc": "Local Mesh Discovery", "title": "Manual exploration", - "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Ferilkönnun . Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It’s the single most useful tool for debugging connectivity problems. Running a Traceroute . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | Weak link — this relay segment is fragile | . | Many hops (4+) | Long path — consider repositioning a node to shorten it | . | Different path on retry | Mesh is adapting — multiple routes exist (this is good!) | . 💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network. Troubleshooting with Traceroute . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Neighbor Info . The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh. Enabling Neighbor Info . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding new nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes. | . Assessing connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ", + "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Ferilkönnun . Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It’s the single most useful tool for debugging connectivity problems. Running a Traceroute . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | Weak link — this relay segment is fragile | . | Many hops (4+) | Long path — consider repositioning a node to shorten it | . | Different path on retry | Mesh is adapting — multiple routes exist (this is good!) | . 💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network. Troubleshooting with Traceroute . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Neighbor Info . The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh. Enabling Neighbor Info . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update Interval. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding new nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes. | . Assessing connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ", "url": "/Meshtastic-Android/main/is-rIS/user/discovery.html#manual-exploration", "relUrl": "/is-rIS/user/discovery.html#manual-exploration" @@ -8947,7 +8947,7 @@ },"1278": { "doc": "Local Mesh Discovery", "title": "Manual exploration", - "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Žinutės kelias . Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It’s the single most useful tool for debugging connectivity problems. Running a Traceroute . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | Weak link — this relay segment is fragile | . | Many hops (4+) | Long path — consider repositioning a node to shorten it | . | Different path on retry | Mesh is adapting — multiple routes exist (this is good!) | . 💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network. Troubleshooting with Traceroute . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Neighbor Info . The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh. Enabling Neighbor Info . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding new nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes. | . Assessing connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ", + "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Žinutės kelias . Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It’s the single most useful tool for debugging connectivity problems. Running a Traceroute . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | Weak link — this relay segment is fragile | . | Many hops (4+) | Long path — consider repositioning a node to shorten it | . | Different path on retry | Mesh is adapting — multiple routes exist (this is good!) | . 💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network. Troubleshooting with Traceroute . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Neighbor Info . The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh. Enabling Neighbor Info . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update Interval. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding new nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes. | . Assessing connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ", "url": "/Meshtastic-Android/main/lt-rLT/user/discovery.html#manual-exploration", "relUrl": "/lt-rLT/user/discovery.html#manual-exploration" @@ -8989,7 +8989,7 @@ },"1284": { "doc": "Local Mesh Discovery", "title": "Manual exploration", - "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Traza-ruta . Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It’s the single most useful tool for debugging connectivity problems. Running a Traceroute . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | Weak link — this relay segment is fragile | . | Many hops (4+) | Long path — consider repositioning a node to shorten it | . | Different path on retry | Mesh is adapting — multiple routes exist (this is good!) | . 💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network. Troubleshooting with Traceroute . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Neighbor Info . The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh. Enabling Neighbor Info . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding new nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes. | . Assessing connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ", + "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Traza-ruta . Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It’s the single most useful tool for debugging connectivity problems. Running a Traceroute . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | Weak link — this relay segment is fragile | . | Many hops (4+) | Long path — consider repositioning a node to shorten it | . | Different path on retry | Mesh is adapting — multiple routes exist (this is good!) | . 💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network. Troubleshooting with Traceroute . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Neighbor Info . The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh. Enabling Neighbor Info . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update Interval. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding new nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes. | . Assessing connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ", "url": "/Meshtastic-Android/main/gl-rES/user/discovery.html#manual-exploration", "relUrl": "/gl-rES/user/discovery.html#manual-exploration" @@ -9031,7 +9031,7 @@ },"1290": { "doc": "ローカルメッシュ探索", "title": "Manual exploration", - "content": "The following tools are available at any time from the node list and node detail screens. 完全なスキャンと併用して、またはその代わりに、特定の経路を調べてトポロジーの全体像を組み立てるのに使えます。 . ルート追跡 . ルート追跡は、メッセージが自分のノードから、メッシュ上の他の任意のノードへ通る正確な経路を明らかにします。接続の問題をデバッグするのに、最も役立つツールです。 . ルート追跡を実行する . | 「ノード」に移動し、追跡したいノードをタップします。 | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . ルート追跡の結果は次のように表示されます： . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | 確認すべき点 | 意味 | . | All hops show Good SNR (green) | 健全な経路。メッセージが確実に流れます | . | One hop shows a poor SNR (orange or red) | 弱いリンク。この中継区間は脆弱です | . | ホップ数が多い（4 以上） | 長い経路。短くするためにノードの再配置を検討してください | . | 再試行で経路が変わる | メッシュが適応しています。複数の経路が存在します（これは良いことです！） | . 💡 ヒント： ルート追跡を数分間かけて何度か実行してください。経路が変わる場合、メッシュには冗長な経路があり、よくつながったネットワークの兆候です。 . ルート追跡によるトラブルシューティング . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. 両方のノードが、同じ暗号化鍵を持つチャンネルを少なくとも 1 つ共有しているか確認してください。 | ルート追跡がタイムアウトする：経路が長すぎる（ホップ数上限を超える）か、中継ノードが混雑している可能性があります。 Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | 非対称な経路：A→B のルート追跡は、B→A とは異なる経路を通ることがあります。 This is normal — radio propagation isn’t always symmetric. | . 隣接ノード情報 . 隣接ノード情報モジュールを使うと、各ノードが直接受信できる（シングルホップの）ノードのリストをブロードキャストできます。複数のノードが隣接ノードのリストを共有すると、メッシュ全体のトポロジーマップを組み立てられます。 . 隣接ノード情報を有効にする . | Navigate to Settings → Module configuration → Neighbor Info. | モジュールを有効にします。 | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. 隣接ノード情報を有効にしている他のノードも、同じことを行います。 . Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | 各隣接ノードの項目には、直接受信したノードとその信号品質が表示されます。 | 複数のノードの隣接ノードデータを組み合わせて、メッシュ全体のトポロジーを把握します。 | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . ノードリスト自体も、絞り込みと並べ替えの機能を効果的に使えば、強力な探索ツールになります。 . Finding new nodes . | 「最後の通信」で並べ替えると、最近アクティブだったノードが先頭に表示されます。 | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes. | . Assessing connectivity . | 「ホップ数」で並べ替えると、直接到達できるノード（0 ホップ）と中継されるノードが分かります。 | 「距離」で並べ替えると、近くのノードを見つけて、到達できるか確認できます。 | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | 「インフラを除外」を無効にすると、ルーター、ルーター・レイト、クライアント・ベースのノードが表示されます。 | 信号品質と最後の通信時刻を確認して、インフラのノードが健全であることを確かめます。 | . 絞り込みと並べ替えのオプションの詳細については、ノード を参照してください。 . ", + "content": "The following tools are available at any time from the node list and node detail screens. 完全なスキャンと併用して、またはその代わりに、特定の経路を調べてトポロジーの全体像を組み立てるのに使えます。 . ルート追跡 . ルート追跡は、メッセージが自分のノードから、メッシュ上の他の任意のノードへ通る正確な経路を明らかにします。接続の問題をデバッグするのに、最も役立つツールです。 . ルート追跡を実行する . | 「ノード」に移動し、追跡したいノードをタップします。 | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . ルート追跡の結果は次のように表示されます： . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | 確認すべき点 | 意味 | . | All hops show Good SNR (green) | 健全な経路。メッセージが確実に流れます | . | One hop shows a poor SNR (orange or red) | 弱いリンク。この中継区間は脆弱です | . | ホップ数が多い（4 以上） | 長い経路。短くするためにノードの再配置を検討してください | . | 再試行で経路が変わる | メッシュが適応しています。複数の経路が存在します（これは良いことです！） | . 💡 ヒント： ルート追跡を数分間かけて何度か実行してください。経路が変わる場合、メッシュには冗長な経路があり、よくつながったネットワークの兆候です。 . ルート追跡によるトラブルシューティング . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. 両方のノードが、同じ暗号化鍵を持つチャンネルを少なくとも 1 つ共有しているか確認してください。 | ルート追跡がタイムアウトする：経路が長すぎる（ホップ数上限を超える）か、中継ノードが混雑している可能性があります。 Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | 非対称な経路：A→B のルート追跡は、B→A とは異なる経路を通ることがあります。 This is normal — radio propagation isn’t always symmetric. | . 隣接ノード情報 . 隣接ノード情報モジュールを使うと、各ノードが直接受信できる（シングルホップの）ノードのリストをブロードキャストできます。複数のノードが隣接ノードのリストを共有すると、メッシュ全体のトポロジーマップを組み立てられます。 . 隣接ノード情報を有効にする . | Navigate to Settings → Module configuration → Neighbor Info. | モジュールを有効にします。 | Set Update Interval. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. 隣接ノード情報を有効にしている他のノードも、同じことを行います。 . Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | 各隣接ノードの項目には、直接受信したノードとその信号品質が表示されます。 | 複数のノードの隣接ノードデータを組み合わせて、メッシュ全体のトポロジーを把握します。 | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . ノードリスト自体も、絞り込みと並べ替えの機能を効果的に使えば、強力な探索ツールになります。 . Finding new nodes . | 「最後の通信」で並べ替えると、最近アクティブだったノードが先頭に表示されます。 | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes. | . Assessing connectivity . | 「ホップ数」で並べ替えると、直接到達できるノード（0 ホップ）と中継されるノードが分かります。 | 「距離」で並べ替えると、近くのノードを見つけて、到達できるか確認できます。 | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | 「インフラを除外」を無効にすると、ルーター、ルーター・レイト、クライアント・ベースのノードが表示されます。 | 信号品質と最後の通信時刻を確認して、インフラのノードが健全であることを確かめます。 | . 絞り込みと並べ替えのオプションの詳細については、ノード を参照してください。 . ", "url": "/Meshtastic-Android/main/ja-rJP/user/discovery.html#manual-exploration", "relUrl": "/ja-rJP/user/discovery.html#manual-exploration" @@ -9073,7 +9073,7 @@ },"1296": { "doc": "Local Mesh Discovery", "title": "Manual exploration", - "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Traceroute . Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It’s the single most useful tool for debugging connectivity problems. Running a Traceroute . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | Weak link — this relay segment is fragile | . | Many hops (4+) | Long path — consider repositioning a node to shorten it | . | Different path on retry | Mesh is adapting — multiple routes exist (this is good!) | . 💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network. Troubleshooting with Traceroute . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Nachbarinformation . The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh. Enabling Neighbor Info . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding new nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes. | . Assessing connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ", + "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Traceroute . Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It’s the single most useful tool for debugging connectivity problems. Running a Traceroute . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | Weak link — this relay segment is fragile | . | Many hops (4+) | Long path — consider repositioning a node to shorten it | . | Different path on retry | Mesh is adapting — multiple routes exist (this is good!) | . 💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network. Troubleshooting with Traceroute . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Nachbarinformation . The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh. Enabling Neighbor Info . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update Interval. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding new nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes. | . Assessing connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ", "url": "/Meshtastic-Android/main/de-rDE/user/discovery.html#manual-exploration", "relUrl": "/de-rDE/user/discovery.html#manual-exploration" @@ -9115,7 +9115,7 @@ },"1302": { "doc": "Local Mesh Discovery", "title": "Manual exploration", - "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Traceroute . Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It’s the single most useful tool for debugging connectivity problems. Running a Traceroute . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | Weak link — this relay segment is fragile | . | Many hops (4+) | Long path — consider repositioning a node to shorten it | . | Different path on retry | Mesh is adapting — multiple routes exist (this is good!) | . 💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network. Troubleshooting with Traceroute . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Neighbor Info . The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh. Enabling Neighbor Info . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding new nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes. | . Assessing connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ", + "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Traceroute . Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It’s the single most useful tool for debugging connectivity problems. Running a Traceroute . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | Weak link — this relay segment is fragile | . | Many hops (4+) | Long path — consider repositioning a node to shorten it | . | Different path on retry | Mesh is adapting — multiple routes exist (this is good!) | . 💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network. Troubleshooting with Traceroute . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Neighbor Info . The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh. Enabling Neighbor Info . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update Interval. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding new nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes. | . Assessing connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ", "url": "/Meshtastic-Android/main/ar-rSA/user/discovery.html#manual-exploration", "relUrl": "/ar-rSA/user/discovery.html#manual-exploration" @@ -9157,7 +9157,7 @@ },"1308": { "doc": "Local Mesh Discovery", "title": "Manual exploration", - "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Traceroute . Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It’s the single most useful tool for debugging connectivity problems. Running a Traceroute . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | Weak link — this relay segment is fragile | . | Many hops (4+) | Long path — consider repositioning a node to shorten it | . | Different path on retry | Mesh is adapting — multiple routes exist (this is good!) | . 💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network. Troubleshooting with Traceroute . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Neighbor Info . The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh. Enabling Neighbor Info . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding new nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes. | . Assessing connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ", + "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Traceroute . Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It’s the single most useful tool for debugging connectivity problems. Running a Traceroute . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | Weak link — this relay segment is fragile | . | Many hops (4+) | Long path — consider repositioning a node to shorten it | . | Different path on retry | Mesh is adapting — multiple routes exist (this is good!) | . 💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network. Troubleshooting with Traceroute . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Neighbor Info . The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh. Enabling Neighbor Info . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update Interval. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding new nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes. | . Assessing connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ", "url": "/Meshtastic-Android/main/hr-rHR/user/discovery.html#manual-exploration", "relUrl": "/hr-rHR/user/discovery.html#manual-exploration" @@ -9199,7 +9199,7 @@ },"1314": { "doc": "Local Mesh Discovery", "title": "Manual exploration", - "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Traçar rota . Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It’s the single most useful tool for debugging connectivity problems. Running a Traceroute . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | Weak link — this relay segment is fragile | . | Many hops (4+) | Long path — consider repositioning a node to shorten it | . | Different path on retry | Mesh is adapting — multiple routes exist (this is good!) | . 💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network. Troubleshooting with Traceroute . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Informações da vizinhança . The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh. Enabling Neighbor Info . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding new nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes. | . Assessing connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ", + "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Traçar rota . Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It’s the single most useful tool for debugging connectivity problems. Running a Traceroute . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | Weak link — this relay segment is fragile | . | Many hops (4+) | Long path — consider repositioning a node to shorten it | . | Different path on retry | Mesh is adapting — multiple routes exist (this is good!) | . 💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network. Troubleshooting with Traceroute . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Informações da vizinhança . The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh. Enabling Neighbor Info . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update Interval. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding new nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes. | . Assessing connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ", "url": "/Meshtastic-Android/main/pt-rPT/user/discovery.html#manual-exploration", "relUrl": "/pt-rPT/user/discovery.html#manual-exploration" @@ -9241,7 +9241,7 @@ },"1320": { "doc": "Local Mesh Discovery", "title": "Manual exploration", - "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Pokaż trasę . Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It’s the single most useful tool for debugging connectivity problems. Running a Traceroute . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | Weak link — this relay segment is fragile | . | Many hops (4+) | Long path — consider repositioning a node to shorten it | . | Different path on retry | Mesh is adapting — multiple routes exist (this is good!) | . 💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network. Troubleshooting with Traceroute . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Informacje o sąsiadze . The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh. Enabling Neighbor Info . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding new nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes. | . Assessing connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ", + "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Pokaż trasę . Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It’s the single most useful tool for debugging connectivity problems. Running a Traceroute . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | Weak link — this relay segment is fragile | . | Many hops (4+) | Long path — consider repositioning a node to shorten it | . | Different path on retry | Mesh is adapting — multiple routes exist (this is good!) | . 💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network. Troubleshooting with Traceroute . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Informacje o sąsiadze . The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh. Enabling Neighbor Info . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update Interval. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding new nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes. | . Assessing connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ", "url": "/Meshtastic-Android/main/pl-rPL/user/discovery.html#manual-exploration", "relUrl": "/pl-rPL/user/discovery.html#manual-exploration" @@ -9283,7 +9283,7 @@ },"1326": { "doc": "本地网状网络发现", "title": "Manual exploration", - "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. 追踪器 . Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It’s the single most useful tool for debugging connectivity problems. Running a Traceroute . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | Weak link — this relay segment is fragile | . | Many hops (4+) | Long path — consider repositioning a node to shorten it | . | Different path on retry | Mesh is adapting — multiple routes exist (this is good!) | . 💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network. Troubleshooting with Traceroute . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . 邻居信息 . The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh. Enabling Neighbor Info . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding new nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes. | . Assessing connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ", + "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. 追踪器 . Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It’s the single most useful tool for debugging connectivity problems. Running a Traceroute . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | Weak link — this relay segment is fragile | . | Many hops (4+) | Long path — consider repositioning a node to shorten it | . | Different path on retry | Mesh is adapting — multiple routes exist (this is good!) | . 💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network. Troubleshooting with Traceroute . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . 邻居信息 . The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh. Enabling Neighbor Info . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update Interval. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding new nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes. | . Assessing connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ", "url": "/Meshtastic-Android/main/zh-rCN/user/discovery.html#manual-exploration", "relUrl": "/zh-rCN/user/discovery.html#manual-exploration" @@ -9325,7 +9325,7 @@ },"1332": { "doc": "Local Mesh Discovery", "title": "Manual exploration", - "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Traceroute . Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It’s the single most useful tool for debugging connectivity problems. Running a Traceroute . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | Weak link — this relay segment is fragile | . | Many hops (4+) | Long path — consider repositioning a node to shorten it | . | Different path on retry | Mesh is adapting — multiple routes exist (this is good!) | . 💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network. Troubleshooting with Traceroute . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Neighbor Info . The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh. Enabling Neighbor Info . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding new nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes. | . Assessing connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ", + "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Traceroute . Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It’s the single most useful tool for debugging connectivity problems. Running a Traceroute . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | Weak link — this relay segment is fragile | . | Many hops (4+) | Long path — consider repositioning a node to shorten it | . | Different path on retry | Mesh is adapting — multiple routes exist (this is good!) | . 💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network. Troubleshooting with Traceroute . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Neighbor Info . The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh. Enabling Neighbor Info . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update Interval. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding new nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes. | . Assessing connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ", "url": "/Meshtastic-Android/main/sq-rAL/user/discovery.html#manual-exploration", "relUrl": "/sq-rAL/user/discovery.html#manual-exploration" @@ -9367,7 +9367,7 @@ },"1338": { "doc": "Local Mesh Discovery", "title": "Manual exploration", - "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. 路由追蹤 . 路由追蹤可顯示訊息從您的節點到 mesh 網路上任一節點所經過的確切路徑。這是診斷連線問題最有效的工具。 . 執行路由追蹤 . | 前往「節點」，並點選您要追蹤的節點。 | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . 路由追蹤結果的顯示方式如下： . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | 判讀重點 | 代表意義 | . | All hops show Good SNR (green) | 路徑狀況良好 — 訊息可穩定傳送 | . | One hop shows a poor SNR (orange or red) | 訊號薄弱 — 此中繼路段不穩定 | . | 跳躍點過多（4 個以上） | 路徑過長 — 建議調整節點位置以縮短路徑 | . | 重試時走不同路徑 | Mesh 網路正在自動調整 — 存在多條路由（這是好現象！） | . 💡 提示：請在幾分鐘內多次執行路由追蹤。若路徑發生變化，代表您的 mesh 網路具備備援路由 — 這是網路連線良好的象徵。 . 使用路由追蹤進行疑難排解 . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. 請確認兩個節點至少共用一個使用相同加密金鑰的頻道。 | 「路由追蹤逾時」— 路徑可能過長（超過跳躍限制），或某中繼節點發生壅塞。 Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | 非對稱路徑 — 從 A → B 的路由追蹤路徑，可能與 B → A 不同。 This is normal — radio propagation isn’t always symmetric. | . 鄰近節點資訊 . 鄰近節點資訊模組可讓每個節點廣播其可直接收到訊號的節點清單（單跳躍）。當多個節點共享各自的鄰近節點清單時，您便可拼湊出整個 mesh 網路的拓撲圖。 . 啟用鄰近節點資訊 . | Navigate to Settings → Module configuration → Neighbor Info. | 啟用此模組。 | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. 其他已啟用鄰近節點資訊的節點也會執行相同動作。 . Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | 每筆鄰近節點記錄會顯示可直接收到訊號的節點及其訊號品質。 | 結合多個節點的鄰近節點資料，以了解完整的 mesh 網路拓撲。 | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . 善用節點清單的篩選與排序功能，即可將其作為強大的探索工具。 . Finding new nodes . | 依「最後收到訊號」排序，可將最近有活動的節點顯示於頂部。 | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes. | . Assessing connectivity . | 依「跳躍距離」排序，可區分可直接到達的節點（0 個跳躍點）與需中繼轉送的節點。 | 依「距離」排序，可找出附近的節點並確認是否可到達。 | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | 檢查其訊號品質與最後收到訊號的時間，以確認基礎架構節點運作正常。 | . 請參閱〔節點〕(nodes) 以了解完整的篩選與排序選項說明。 . ", + "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. 路由追蹤 . 路由追蹤可顯示訊息從您的節點到 mesh 網路上任一節點所經過的確切路徑。這是診斷連線問題最有效的工具。 . 執行路由追蹤 . | 前往「節點」，並點選您要追蹤的節點。 | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . 路由追蹤結果的顯示方式如下： . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | 判讀重點 | 代表意義 | . | All hops show Good SNR (green) | 路徑狀況良好 — 訊息可穩定傳送 | . | One hop shows a poor SNR (orange or red) | 訊號薄弱 — 此中繼路段不穩定 | . | 跳躍點過多（4 個以上） | 路徑過長 — 建議調整節點位置以縮短路徑 | . | 重試時走不同路徑 | Mesh 網路正在自動調整 — 存在多條路由（這是好現象！） | . 💡 提示：請在幾分鐘內多次執行路由追蹤。若路徑發生變化，代表您的 mesh 網路具備備援路由 — 這是網路連線良好的象徵。 . 使用路由追蹤進行疑難排解 . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. 請確認兩個節點至少共用一個使用相同加密金鑰的頻道。 | 「路由追蹤逾時」— 路徑可能過長（超過跳躍限制），或某中繼節點發生壅塞。 Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | 非對稱路徑 — 從 A → B 的路由追蹤路徑，可能與 B → A 不同。 This is normal — radio propagation isn’t always symmetric. | . 鄰近節點資訊 . 鄰近節點資訊模組可讓每個節點廣播其可直接收到訊號的節點清單（單跳躍）。當多個節點共享各自的鄰近節點清單時，您便可拼湊出整個 mesh 網路的拓撲圖。 . 啟用鄰近節點資訊 . | Navigate to Settings → Module configuration → Neighbor Info. | 啟用此模組。 | Set Update Interval. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. 其他已啟用鄰近節點資訊的節點也會執行相同動作。 . Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | 每筆鄰近節點記錄會顯示可直接收到訊號的節點及其訊號品質。 | 結合多個節點的鄰近節點資料，以了解完整的 mesh 網路拓撲。 | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . 善用節點清單的篩選與排序功能，即可將其作為強大的探索工具。 . Finding new nodes . | 依「最後收到訊號」排序，可將最近有活動的節點顯示於頂部。 | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes. | . Assessing connectivity . | 依「跳躍距離」排序，可區分可直接到達的節點（0 個跳躍點）與需中繼轉送的節點。 | 依「距離」排序，可找出附近的節點並確認是否可到達。 | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | 檢查其訊號品質與最後收到訊號的時間，以確認基礎架構節點運作正常。 | . 請參閱〔節點〕(nodes) 以了解完整的篩選與排序選項說明。 . ", "url": "/Meshtastic-Android/main/zh-rTW/user/discovery.html#manual-exploration", "relUrl": "/zh-rTW/user/discovery.html#manual-exploration" @@ -9409,7 +9409,7 @@ },"1344": { "doc": "Kohalik kärgvõrgu avastaja", "title": "Manual exploration", - "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Marsruudi . Traceroute näitab täpset teed, mida sõnum sõlmest mis tahes teise kärgvõrgu sõlme kulgeb. See on kõige kasulikum tööriist ühenduvusprobleemide tõrkeotsinguks. Traceroute’i käivitamine . | Mine valikuni Sõlmed ja puuduta sõlme, mida soovid jälgida. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . Traceroute’i tulemus näeb välja selline: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | Kehv ühendus – see releesegment on habras | . | Mitu hüppet (4+) | Pikk tee – kaalu sõlme ümberpaigutamist selle lühendamiseks | . | Different path on retry | Mesh is adapting — multiple routes exist (this is good!) | . 💡 Vihje: Käivita traceroute’i mitu korda mõne minuti tagant. If the path changes, your mesh has redundant routes — a sign of a well-connected network. Veaotsing koos Traceroute . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Kontrolli, et mõlemad sõlmed jagaksid vähemalt ühte kanalit sama krüpteerimisvõtmega. | Traceroute aegus — Tee võib olla liiga pikk (ületab hüppete limiidi) või on vahendussõlm ülekoormatud. Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asümmeetrilised teed – Jälgimismarsruut teelt A→B võib minna teist teed kui teelt B→A. This is normal — radio propagation isn’t always symmetric. | . Naabruse teave . Naabriinfo moodul võimaldab igal sõlmel levitada nimekirja sõlmedest, mida see otse kuuleb (üksik-hüpe). Kui mitu sõlme jagavad oma naaberloendeid, saate kokku panna kogu võrgu topoloogiakaardi. Naabriinfo lubamine . | Navigate to Settings → Module configuration → Neighbor Info. | Luba moodul. | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Teised sõlmed, millel on naabriinfo lubatud, teevad sama. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | Iga naabri-kirje näitab otse kuuldud sõlme ja selle signaali kvaliteeti. | Kogu kärgvõrgu topoloogia mõistmiseks kombineerige mitme sõlme naaberandmeid. | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . Sõlmede loend ise on võimas avastusvahend, kui kasutada selle filtreerimis- ja sortimisfunktsioone tõhusalt. Finding new nodes . | Sorteeri Viimati kuuldud järgi, et näha kõige hiljutisemaid aktiivseid sõlmi ülaosas. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes. | . Assessing connectivity . | Sorteeri Hüpete arvu järgi, et näha, millised sõlmed on otse kättesaadavad (0 hüpet) ja millised vahendatavate sõlmedega. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Kontrolli nende signaali kvaliteeti ja viimase kuulmise aegu, et veenduda oma infrastruktuuri sõlmede töökorras olekus. | . Filtreerimis- ja sortimisvalikute kohta leiate lisateavet jaotisest Nodes. ", + "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Marsruudi . Traceroute näitab täpset teed, mida sõnum sõlmest mis tahes teise kärgvõrgu sõlme kulgeb. See on kõige kasulikum tööriist ühenduvusprobleemide tõrkeotsinguks. Traceroute’i käivitamine . | Mine valikuni Sõlmed ja puuduta sõlme, mida soovid jälgida. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . Traceroute’i tulemus näeb välja selline: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | Kehv ühendus – see releesegment on habras | . | Mitu hüppet (4+) | Pikk tee – kaalu sõlme ümberpaigutamist selle lühendamiseks | . | Different path on retry | Mesh is adapting — multiple routes exist (this is good!) | . 💡 Vihje: Käivita traceroute’i mitu korda mõne minuti tagant. If the path changes, your mesh has redundant routes — a sign of a well-connected network. Veaotsing koos Traceroute . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Kontrolli, et mõlemad sõlmed jagaksid vähemalt ühte kanalit sama krüpteerimisvõtmega. | Traceroute aegus — Tee võib olla liiga pikk (ületab hüppete limiidi) või on vahendussõlm ülekoormatud. Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asümmeetrilised teed – Jälgimismarsruut teelt A→B võib minna teist teed kui teelt B→A. This is normal — radio propagation isn’t always symmetric. | . Naabruse teave . Naabriinfo moodul võimaldab igal sõlmel levitada nimekirja sõlmedest, mida see otse kuuleb (üksik-hüpe). Kui mitu sõlme jagavad oma naaberloendeid, saate kokku panna kogu võrgu topoloogiakaardi. Naabriinfo lubamine . | Navigate to Settings → Module configuration → Neighbor Info. | Luba moodul. | Set Update Interval. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Teised sõlmed, millel on naabriinfo lubatud, teevad sama. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | Iga naabri-kirje näitab otse kuuldud sõlme ja selle signaali kvaliteeti. | Kogu kärgvõrgu topoloogia mõistmiseks kombineerige mitme sõlme naaberandmeid. | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . Sõlmede loend ise on võimas avastusvahend, kui kasutada selle filtreerimis- ja sortimisfunktsioone tõhusalt. Finding new nodes . | Sorteeri Viimati kuuldud järgi, et näha kõige hiljutisemaid aktiivseid sõlmi ülaosas. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes. | . Assessing connectivity . | Sorteeri Hüpete arvu järgi, et näha, millised sõlmed on otse kättesaadavad (0 hüpet) ja millised vahendatavate sõlmedega. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Kontrolli nende signaali kvaliteeti ja viimase kuulmise aegu, et veenduda oma infrastruktuuri sõlmede töökorras olekus. | . Filtreerimis- ja sortimisvalikute kohta leiate lisateavet jaotisest Nodes. ", "url": "/Meshtastic-Android/main/et-rEE/user/discovery.html#manual-exploration", "relUrl": "/et-rEE/user/discovery.html#manual-exploration" @@ -9451,7 +9451,7 @@ },"1350": { "doc": "Découverte de maille locale", "title": "Manual exploration", - "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Traceroute . Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It’s the single most useful tool for debugging connectivity problems. Running a Traceroute . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | Weak link — this relay segment is fragile | . | Many hops (4+) | Long path — consider repositioning a node to shorten it | . | Different path on retry | Mesh is adapting — multiple routes exist (this is good!) | . 💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network. Troubleshooting with Traceroute . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Informations sur les voisins . The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh. Enabling Neighbor Info . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding new nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes. | . Assessing connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ", + "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Traceroute . Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It’s the single most useful tool for debugging connectivity problems. Running a Traceroute . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | Weak link — this relay segment is fragile | . | Many hops (4+) | Long path — consider repositioning a node to shorten it | . | Different path on retry | Mesh is adapting — multiple routes exist (this is good!) | . 💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network. Troubleshooting with Traceroute . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Informations sur les voisins . The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh. Enabling Neighbor Info . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update Interval. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding new nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes. | . Assessing connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ", "url": "/Meshtastic-Android/main/fr-rFR/user/discovery.html#manual-exploration", "relUrl": "/fr-rFR/user/discovery.html#manual-exploration" @@ -9493,7 +9493,7 @@ },"1356": { "doc": "Local Mesh Discovery", "title": "Manual exploration", - "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Yol izle . Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It’s the single most useful tool for debugging connectivity problems. Running a Traceroute . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | Weak link — this relay segment is fragile | . | Many hops (4+) | Long path — consider repositioning a node to shorten it | . | Different path on retry | Mesh is adapting — multiple routes exist (this is good!) | . 💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network. Troubleshooting with Traceroute . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Komşu Bilgisi . The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh. Enabling Neighbor Info . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding new nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes. | . Assessing connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ", + "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Yol izle . Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It’s the single most useful tool for debugging connectivity problems. Running a Traceroute . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | Weak link — this relay segment is fragile | . | Many hops (4+) | Long path — consider repositioning a node to shorten it | . | Different path on retry | Mesh is adapting — multiple routes exist (this is good!) | . 💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network. Troubleshooting with Traceroute . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Komşu Bilgisi . The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh. Enabling Neighbor Info . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update Interval. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding new nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes. | . Assessing connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ", "url": "/Meshtastic-Android/main/tr-rTR/user/discovery.html#manual-exploration", "relUrl": "/tr-rTR/user/discovery.html#manual-exploration" @@ -9535,7 +9535,7 @@ },"1362": { "doc": "Local Mesh Discovery", "title": "Manual exploration", - "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Traceroute . Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It’s the single most useful tool for debugging connectivity problems. Running a Traceroute . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | Weak link — this relay segment is fragile | . | Many hops (4+) | Long path — consider repositioning a node to shorten it | . | Different path on retry | Mesh is adapting — multiple routes exist (this is good!) | . 💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network. Troubleshooting with Traceroute . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Neighbor Info . The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh. Enabling Neighbor Info . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding new nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes. | . Assessing connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ", + "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Traceroute . Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It’s the single most useful tool for debugging connectivity problems. Running a Traceroute . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | Weak link — this relay segment is fragile | . | Many hops (4+) | Long path — consider repositioning a node to shorten it | . | Different path on retry | Mesh is adapting — multiple routes exist (this is good!) | . 💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network. Troubleshooting with Traceroute . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Neighbor Info . The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh. Enabling Neighbor Info . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update Interval. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding new nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes. | . Assessing connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ", "url": "/Meshtastic-Android/main/el-rGR/user/discovery.html#manual-exploration", "relUrl": "/el-rGR/user/discovery.html#manual-exploration" @@ -9577,7 +9577,7 @@ },"1368": { "doc": "Local Mesh Discovery", "title": "Manual exploration", - "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Trasare traseu . Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It’s the single most useful tool for debugging connectivity problems. Running a Traceroute . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | Weak link — this relay segment is fragile | . | Many hops (4+) | Long path — consider repositioning a node to shorten it | . | Different path on retry | Mesh is adapting — multiple routes exist (this is good!) | . 💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network. Troubleshooting with Traceroute . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Informații vecin . The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh. Enabling Neighbor Info . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding new nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes. | . Assessing connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ", + "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Trasare traseu . Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It’s the single most useful tool for debugging connectivity problems. Running a Traceroute . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | Weak link — this relay segment is fragile | . | Many hops (4+) | Long path — consider repositioning a node to shorten it | . | Different path on retry | Mesh is adapting — multiple routes exist (this is good!) | . 💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network. Troubleshooting with Traceroute . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Informații vecin . The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh. Enabling Neighbor Info . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update Interval. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding new nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes. | . Assessing connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ", "url": "/Meshtastic-Android/main/ro-rRO/user/discovery.html#manual-exploration", "relUrl": "/ro-rRO/user/discovery.html#manual-exploration" @@ -9619,7 +9619,7 @@ },"1374": { "doc": "Local Mesh Discovery", "title": "Manual exploration", - "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. בדיקת מסלול . Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It’s the single most useful tool for debugging connectivity problems. Running a Traceroute . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | Weak link — this relay segment is fragile | . | Many hops (4+) | Long path — consider repositioning a node to shorten it | . | Different path on retry | Mesh is adapting — multiple routes exist (this is good!) | . 💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network. Troubleshooting with Traceroute . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Neighbor Info . The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh. Enabling Neighbor Info . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding new nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes. | . Assessing connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ", + "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. בדיקת מסלול . Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It’s the single most useful tool for debugging connectivity problems. Running a Traceroute . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | Weak link — this relay segment is fragile | . | Many hops (4+) | Long path — consider repositioning a node to shorten it | . | Different path on retry | Mesh is adapting — multiple routes exist (this is good!) | . 💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network. Troubleshooting with Traceroute . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Neighbor Info . The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh. Enabling Neighbor Info . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update Interval. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding new nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes. | . Assessing connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ", "url": "/Meshtastic-Android/main/iw-rIL/user/discovery.html#manual-exploration", "relUrl": "/iw-rIL/user/discovery.html#manual-exploration" @@ -9661,7 +9661,7 @@ },"1380": { "doc": "Local Mesh Discovery", "title": "Manual exploration", - "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Traçar rota . Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It’s the single most useful tool for debugging connectivity problems. Running a Traceroute . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | Weak link — this relay segment is fragile | . | Many hops (4+) | Long path — consider repositioning a node to shorten it | . | Different path on retry | Mesh is adapting — multiple routes exist (this is good!) | . 💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network. Troubleshooting with Traceroute . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Informações do Vizinho . The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh. Enabling Neighbor Info . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding new nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes. | . Assessing connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ", + "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Traçar rota . Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It’s the single most useful tool for debugging connectivity problems. Running a Traceroute . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | Weak link — this relay segment is fragile | . | Many hops (4+) | Long path — consider repositioning a node to shorten it | . | Different path on retry | Mesh is adapting — multiple routes exist (this is good!) | . 💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network. Troubleshooting with Traceroute . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key. | Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Informações do Vizinho . The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh. Enabling Neighbor Info . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update Interval. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | Each neighbor entry shows the node that was directly heard and its signal quality. | Combine neighbor data from multiple nodes to understand the full mesh topology. | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively. Finding new nodes . | Sort by Last heard to see the most recently active nodes at the top. | Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes. | . Assessing connectivity . | Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ", "url": "/Meshtastic-Android/main/pt-rBR/user/discovery.html#manual-exploration", "relUrl": "/pt-rBR/user/discovery.html#manual-exploration" @@ -18691,7 +18691,7 @@ },"2670": { "doc": "MQTT", "title": "Map Reporting", - "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ", + "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map Publish Interval of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ", "url": "/Meshtastic-Android/main/sk-rSK/user/mqtt.html#map-reporting", "relUrl": "/sk-rSK/user/mqtt.html#map-reporting" @@ -18768,7 +18768,7 @@ },"2681": { "doc": "MQTT", "title": "Map Reporting", - "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ", + "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map Publish Interval of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ", "url": "/Meshtastic-Android/main/be-rBY/user/mqtt.html#map-reporting", "relUrl": "/be-rBY/user/mqtt.html#map-reporting" @@ -18845,7 +18845,7 @@ },"2692": { "doc": "MQTT", "title": "Map Reporting", - "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ", + "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map Publish Interval of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ", "url": "/Meshtastic-Android/main/it-rIT/user/mqtt.html#map-reporting", "relUrl": "/it-rIT/user/mqtt.html#map-reporting" @@ -18922,7 +18922,7 @@ },"2703": { "doc": "MQTT", "title": "Map Reporting", - "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ", + "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map Publish Interval of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ", "url": "/Meshtastic-Android/main/es-rES/user/mqtt.html#map-reporting", "relUrl": "/es-rES/user/mqtt.html#map-reporting" @@ -18999,7 +18999,7 @@ },"2714": { "doc": "MQTT", "title": "Map Reporting", - "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ", + "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map Publish Interval of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ", "url": "/Meshtastic-Android/main/sl-rSI/user/mqtt.html#map-reporting", "relUrl": "/sl-rSI/user/mqtt.html#map-reporting" @@ -19076,7 +19076,7 @@ },"2725": { "doc": "MQTT", "title": "Map Reporting", - "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ", + "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map Publish Interval of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ", "url": "/Meshtastic-Android/main/no-rNO/user/mqtt.html#map-reporting", "relUrl": "/no-rNO/user/mqtt.html#map-reporting" @@ -19153,7 +19153,7 @@ },"2736": { "doc": "MQTT", "title": "Map Reporting", - "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ", + "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map Publish Interval of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ", "url": "/Meshtastic-Android/main/hu-rHU/user/mqtt.html#map-reporting", "relUrl": "/hu-rHU/user/mqtt.html#map-reporting" @@ -19230,7 +19230,7 @@ },"2747": { "doc": "MQTT", "title": "Публикация на карте", - "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ", + "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map Publish Interval of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ", "url": "/Meshtastic-Android/main/ru-rRU/user/mqtt.html#%D0%BF%D1%83%D0%B1%D0%BB%D0%B8%D0%BA%D0%B0%D1%86%D0%B8%D1%8F-%D0%BD%D0%B0-%D0%BA%D0%B0%D1%80%D1%82%D0%B5", "relUrl": "/ru-rRU/user/mqtt.html#публикация-на-карте" @@ -19307,7 +19307,7 @@ },"2758": { "doc": "MQTT", "title": "Map Reporting", - "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ", + "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map Publish Interval of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ", "url": "/Meshtastic-Android/main/cs-rCZ/user/mqtt.html#map-reporting", "relUrl": "/cs-rCZ/user/mqtt.html#map-reporting" @@ -19384,7 +19384,7 @@ },"2769": { "doc": "MQTT", "title": "Map Reporting", - "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ", + "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map Publish Interval of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ", "url": "/Meshtastic-Android/main/bg-rBG/user/mqtt.html#map-reporting", "relUrl": "/bg-rBG/user/mqtt.html#map-reporting" @@ -19461,7 +19461,7 @@ },"2780": { "doc": "MQTT", "title": "Map Reporting", - "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ", + "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map Publish Interval of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ", "url": "/Meshtastic-Android/main/ga-rIE/user/mqtt.html#map-reporting", "relUrl": "/ga-rIE/user/mqtt.html#map-reporting" @@ -19538,7 +19538,7 @@ },"2791": { "doc": "MQTT", "title": "Map Reporting", - "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ", + "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map Publish Interval of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ", "url": "/Meshtastic-Android/main/fr-rCA/user/mqtt.html#map-reporting", "relUrl": "/fr-rCA/user/mqtt.html#map-reporting" @@ -19615,7 +19615,7 @@ },"2802": { "doc": "MQTT", "title": "Map Reporting", - "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ", + "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map Publish Interval of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ", "url": "/Meshtastic-Android/main/srp/user/mqtt.html#map-reporting", "relUrl": "/srp/user/mqtt.html#map-reporting" @@ -19692,7 +19692,7 @@ },"2813": { "doc": "MQTT", "title": "Map Reporting", - "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ", + "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map Publish Interval of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ", "url": "/Meshtastic-Android/main/ca-rES/user/mqtt.html#map-reporting", "relUrl": "/ca-rES/user/mqtt.html#map-reporting" @@ -19769,7 +19769,7 @@ },"2824": { "doc": "MQTT", "title": "Map Reporting", - "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ", + "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map Publish Interval of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ", "url": "/Meshtastic-Android/main/ko-rKR/user/mqtt.html#map-reporting", "relUrl": "/ko-rKR/user/mqtt.html#map-reporting" @@ -19846,7 +19846,7 @@ },"2835": { "doc": "MQTT", "title": "Map Reporting", - "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ", + "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map Publish Interval of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ", "url": "/Meshtastic-Android/main/sv-rSE/user/mqtt.html#map-reporting", "relUrl": "/sv-rSE/user/mqtt.html#map-reporting" @@ -19923,7 +19923,7 @@ },"2846": { "doc": "MQTT", "title": "Map Reporting", - "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ", + "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map Publish Interval of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ", "url": "/Meshtastic-Android/main/ht-rHT/user/mqtt.html#map-reporting", "relUrl": "/ht-rHT/user/mqtt.html#map-reporting" @@ -20000,7 +20000,7 @@ },"2857": { "doc": "MQTT", "title": "Map Reporting", - "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ", + "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map Publish Interval of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ", "url": "/Meshtastic-Android/main/sr-rLatn/user/mqtt.html#map-reporting", "relUrl": "/sr-rLatn/user/mqtt.html#map-reporting" @@ -20077,7 +20077,7 @@ },"2868": { "doc": "MQTT", "title": "Map Reporting", - "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ", + "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map Publish Interval of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ", "url": "/Meshtastic-Android/main/nl-rNL/user/mqtt.html#map-reporting", "relUrl": "/nl-rNL/user/mqtt.html#map-reporting" @@ -20154,7 +20154,7 @@ },"2879": { "doc": "MQTT", "title": "Map Reporting", - "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ", + "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map Publish Interval of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ", "url": "/Meshtastic-Android/main/uk-rUA/user/mqtt.html#map-reporting", "relUrl": "/uk-rUA/user/mqtt.html#map-reporting" @@ -20231,7 +20231,7 @@ },"2890": { "doc": "MQTT", "title": "Karttaraportointi", - "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ", + "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map Publish Interval of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ", "url": "/Meshtastic-Android/main/fi-rFI/user/mqtt.html#karttaraportointi", "relUrl": "/fi-rFI/user/mqtt.html#karttaraportointi" @@ -20308,7 +20308,7 @@ },"2901": { "doc": "MQTT", "title": "Map Reporting", - "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ", + "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map Publish Interval of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ", "url": "/Meshtastic-Android/main/is-rIS/user/mqtt.html#map-reporting", "relUrl": "/is-rIS/user/mqtt.html#map-reporting" @@ -20385,7 +20385,7 @@ },"2912": { "doc": "MQTT", "title": "Map Reporting", - "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ", + "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map Publish Interval of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ", "url": "/Meshtastic-Android/main/lt-rLT/user/mqtt.html#map-reporting", "relUrl": "/lt-rLT/user/mqtt.html#map-reporting" @@ -20462,7 +20462,7 @@ },"2923": { "doc": "MQTT", "title": "Map Reporting", - "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ", + "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map Publish Interval of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ", "url": "/Meshtastic-Android/main/gl-rES/user/mqtt.html#map-reporting", "relUrl": "/gl-rES/user/mqtt.html#map-reporting" @@ -20539,7 +20539,7 @@ },"2934": { "doc": "MQTT", "title": "マップ報告", - "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ", + "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map Publish Interval of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ", "url": "/Meshtastic-Android/main/ja-rJP/user/mqtt.html#%E3%83%9E%E3%83%83%E3%83%97%E5%A0%B1%E5%91%8A", "relUrl": "/ja-rJP/user/mqtt.html#マップ報告" @@ -20616,7 +20616,7 @@ },"2945": { "doc": "MQTT", "title": "Map Reporting", - "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ", + "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map Publish Interval of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ", "url": "/Meshtastic-Android/main/de-rDE/user/mqtt.html#map-reporting", "relUrl": "/de-rDE/user/mqtt.html#map-reporting" @@ -20693,7 +20693,7 @@ },"2956": { "doc": "MQTT", "title": "Map Reporting", - "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ", + "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map Publish Interval of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ", "url": "/Meshtastic-Android/main/ar-rSA/user/mqtt.html#map-reporting", "relUrl": "/ar-rSA/user/mqtt.html#map-reporting" @@ -20770,7 +20770,7 @@ },"2967": { "doc": "MQTT", "title": "Map Reporting", - "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ", + "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map Publish Interval of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ", "url": "/Meshtastic-Android/main/hr-rHR/user/mqtt.html#map-reporting", "relUrl": "/hr-rHR/user/mqtt.html#map-reporting" @@ -20847,7 +20847,7 @@ },"2978": { "doc": "MQTT", "title": "Map Reporting", - "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ", + "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map Publish Interval of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ", "url": "/Meshtastic-Android/main/pt-rPT/user/mqtt.html#map-reporting", "relUrl": "/pt-rPT/user/mqtt.html#map-reporting" @@ -20924,7 +20924,7 @@ },"2989": { "doc": "MQTT", "title": "Map Reporting", - "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ", + "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map Publish Interval of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ", "url": "/Meshtastic-Android/main/pl-rPL/user/mqtt.html#map-reporting", "relUrl": "/pl-rPL/user/mqtt.html#map-reporting" @@ -21001,7 +21001,7 @@ },"3000": { "doc": "MQTT", "title": "Map Reporting", - "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ", + "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map Publish Interval of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ", "url": "/Meshtastic-Android/main/zh-rCN/user/mqtt.html#map-reporting", "relUrl": "/zh-rCN/user/mqtt.html#map-reporting" @@ -21078,7 +21078,7 @@ },"3011": { "doc": "MQTT", "title": "Map Reporting", - "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ", + "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map Publish Interval of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ", "url": "/Meshtastic-Android/main/sq-rAL/user/mqtt.html#map-reporting", "relUrl": "/sq-rAL/user/mqtt.html#map-reporting" @@ -21155,7 +21155,7 @@ },"3022": { "doc": "MQTT", "title": "地圖回報", - "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ", + "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map Publish Interval of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ", "url": "/Meshtastic-Android/main/zh-rTW/user/mqtt.html#%E5%9C%B0%E5%9C%96%E5%9B%9E%E5%A0%B1", "relUrl": "/zh-rTW/user/mqtt.html#地圖回報" @@ -21232,7 +21232,7 @@ },"3033": { "doc": "MQTT", "title": "Kaardiaruannete koostamine", - "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ", + "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map Publish Interval of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ", "url": "/Meshtastic-Android/main/et-rEE/user/mqtt.html#kaardiaruannete-koostamine", "relUrl": "/et-rEE/user/mqtt.html#kaardiaruannete-koostamine" @@ -21309,7 +21309,7 @@ },"3044": { "doc": "MQTT", "title": "Map Reporting", - "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ", + "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map Publish Interval of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ", "url": "/Meshtastic-Android/main/fr-rFR/user/mqtt.html#map-reporting", "relUrl": "/fr-rFR/user/mqtt.html#map-reporting" @@ -21386,7 +21386,7 @@ },"3055": { "doc": "MQTT", "title": "Map Reporting", - "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ", + "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map Publish Interval of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ", "url": "/Meshtastic-Android/main/tr-rTR/user/mqtt.html#map-reporting", "relUrl": "/tr-rTR/user/mqtt.html#map-reporting" @@ -21463,7 +21463,7 @@ },"3066": { "doc": "MQTT", "title": "Map Reporting", - "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ", + "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map Publish Interval of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ", "url": "/Meshtastic-Android/main/el-rGR/user/mqtt.html#map-reporting", "relUrl": "/el-rGR/user/mqtt.html#map-reporting" @@ -21540,7 +21540,7 @@ },"3077": { "doc": "MQTT", "title": "Map Reporting", - "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ", + "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map Publish Interval of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ", "url": "/Meshtastic-Android/main/ro-rRO/user/mqtt.html#map-reporting", "relUrl": "/ro-rRO/user/mqtt.html#map-reporting" @@ -21617,7 +21617,7 @@ },"3088": { "doc": "MQTT", "title": "Map Reporting", - "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ", + "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map Publish Interval of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ", "url": "/Meshtastic-Android/main/iw-rIL/user/mqtt.html#map-reporting", "relUrl": "/iw-rIL/user/mqtt.html#map-reporting" @@ -21694,7 +21694,7 @@ },"3099": { "doc": "MQTT", "title": "Map Reporting", - "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ", + "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map Publish Interval of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ", "url": "/Meshtastic-Android/main/pt-rBR/user/mqtt.html#map-reporting", "relUrl": "/pt-rBR/user/mqtt.html#map-reporting" @@ -29674,7 +29674,7 @@ },"4239": { "doc": "Settings — Modules & Admin", "title": "Konfigurácia modulu", - "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Popis | . | MQTT enabled | Toggle MQTT bridge | . | Adresa | MQTT broker address | . | Používateľské meno | Authentication username | . | Heslo | Authentication password | . | Encryption enabled | Encrypt MQTT payloads | . | JSON output enabled | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS enabled | Use secure connection | . | Root topic | Base MQTT topic path | . | Proxy to client enabled | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Map reporting | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Popis | . | I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Map reporting interval (seconds) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Popis | . | Serial enabled | Activate serial communication | . | Echo enabled | Echo received serial data back | . | Serial mode | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Serial baud rate | Port speed | . | Časový limit | How long to wait before considering an incoming message complete | . | Override console serial port | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Popis | . | External notification enabled | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Output LED (GPIO) | Pin the LED is wired to | . | Output LED active high | Whether the LED pin is active high or low | . | Output buzzer (GPIO) | Pin the buzzer is wired to | . | Output vibra (GPIO) | Pin the vibration motor is wired to | . | Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Use I2S as buzzer | Send the alert through an I2S audio output instead | . | Output duration (milliseconds) | How long a single alert lasts | . | Nag timeout (seconds) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Zvonenie | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Popis | . | Store & Forward enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | Number of records | Maximum stored messages | . | History return max | Max messages to replay | . | History return window | Time window for replay | . | Server | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Popis | . | Range test enabled | Activate range testing | . | Sender message interval (seconds) | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Save .CSV in storage (ESP32 only) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Popis | . | Send Device Telemetry | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Device metrics update interval | How often to report battery, uptime and channel utilization | . | Environment metrics module enabled | Report the attached environment sensors | . | Environment metrics update interval | How often to report them | . | Environment metrics on-screen enabled | Also show these readings on the device’s own display | . | Environment metrics use Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Air quality metrics module enabled | Report particulate and CO₂ sensor data | . | Air quality metrics update interval | How often to report them | . | Power metrics module enabled | Report the per-channel voltage and current readings | . | Power metrics update interval | How often to report them | . | Power metrics on-screen enabled | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Popis | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Správy | Newline-separated list of messages | . | Send bell | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Enkóder #1 aktivovaný | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Up/Down/Select input enabled | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Popis | . | CODEC 2 zapnutý | Activate audio module | . | CODEC2 vzorkovacia frekvencia | Audio quality/bandwidth tradeoff | . | PTT pin | GPIO pin for the push-to-talk button | . | I2C výber slova | GPIO pin for I2S WS | . | I2S vstup dát | GPIO pin for I2S DIN | . | I2S výstup dát | GPIO pin for I2S DOUT | . | I2S čas | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Popis | . | Remote Hardware enabled | Activate remote GPIO access | . | Allow undefined pin access | Allow access to any GPIO pin (security risk) | . | Available pins | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Popis | . | Neighbor Info enabled | Activate neighbor broadcasting | . | Update interval (seconds) | How often to broadcast neighbor list | . | Vysielať cez sieť LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Popis | . | Stav LED | Turn the LED on or off | . | Prúd | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Popis | . | Detection Sensor enabled | Activate detection sensor | . | GPIO pin to monitor | GPIO pin connected to sensor | . | Detection trigger type | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Use INPUT_PULLUP mode | Enable the pin’s internal pull-up resistor | . | Minimum broadcast (seconds) | Minimum time between alert broadcasts | . | State broadcast (seconds) | Periodic state broadcast interval | . | Send bell with alert message | Include bell character in alerts | . | Friendly name | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Popis | . | Paxcounter enabled | Activate people counting | . | Update interval (seconds) | How often to report counts | . | Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ", + "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Popis | . | MQTT enabled | Toggle MQTT bridge | . | Adresa | MQTT broker address | . | Používateľské meno | Authentication username | . | Heslo | Authentication password | . | Encryption enabled | Encrypt MQTT payloads | . | JSON output enabled | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS enabled | Use secure connection | . | Root topic | Base MQTT topic path | . | Proxy to client enabled | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Map reporting | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Popis | . | I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Popis | . | Serial enabled | Activate serial communication | . | Echo enabled | Echo received serial data back | . | Serial mode | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Serial baud rate | Port speed | . | Časový limit | How long to wait before considering an incoming message complete | . | Override console serial port | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Popis | . | External notification enabled | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Output LED (GPIO) | Pin the LED is wired to | . | Output LED active high | Whether the LED pin is active high or low | . | Output buzzer (GPIO) | Pin the buzzer is wired to | . | Output vibra (GPIO) | Pin the vibration motor is wired to | . | Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Use I2S as buzzer | Send the alert through an I2S audio output instead | . | GPIO Output Duration | How long a single alert lasts | . | Nag Timeout | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Zvonenie | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Popis | . | Store & Forward enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | Number of records | Maximum stored messages | . | History return max | Max messages to replay | . | History return window | Time window for replay | . | Server | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Popis | . | Range test enabled | Activate range testing | . | Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Save .CSV in storage (ESP32 only) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Popis | . | Send Device Telemetry | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Device metrics update interval | How often to report battery, uptime and channel utilization | . | Environment metrics module enabled | Report the attached environment sensors | . | Environment metrics update interval | How often to report them | . | Environment metrics on-screen enabled | Also show these readings on the device’s own display | . | Environment metrics use Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Air quality metrics module enabled | Report particulate and CO₂ sensor data | . | Air quality metrics update interval | How often to report them | . | Power metrics module enabled | Report the per-channel voltage and current readings | . | Power metrics update interval | How often to report them | . | Power metrics on-screen enabled | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Popis | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Správy | Newline-separated list of messages | . | Send bell | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Enkóder #1 aktivovaný | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Up/Down/Select input enabled | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Popis | . | CODEC 2 zapnutý | Activate audio module | . | CODEC2 vzorkovacia frekvencia | Audio quality/bandwidth tradeoff | . | PTT pin | GPIO pin for the push-to-talk button | . | I2C výber slova | GPIO pin for I2S WS | . | I2S vstup dát | GPIO pin for I2S DIN | . | I2S výstup dát | GPIO pin for I2S DOUT | . | I2S čas | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Popis | . | Remote Hardware enabled | Activate remote GPIO access | . | Allow undefined pin access | Allow access to any GPIO pin (security risk) | . | Available pins | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Popis | . | Neighbor Info enabled | Activate neighbor broadcasting | . | Aktualizačný interval | How often to broadcast neighbor list | . | Vysielať cez sieť LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Popis | . | Stav LED | Turn the LED on or off | . | Prúd | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Popis | . | Detection Sensor enabled | Activate detection sensor | . | GPIO pin to monitor | GPIO pin connected to sensor | . | Detection trigger type | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Use INPUT_PULLUP mode | Enable the pin’s internal pull-up resistor | . | Minimum time between detection broadcasts | Minimum time between alert broadcasts | . | State Broadcast Interval | Periodic state broadcast interval | . | Send bell with alert message | Include bell character in alerts | . | Friendly name | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Popis | . | Paxcounter enabled | Activate people counting | . | Aktualizačný interval | How often to report counts | . | WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ", "url": "/Meshtastic-Android/main/sk-rSK/user/settings-module-admin.html#konfigur%C3%A1cia-modulu", "relUrl": "/sk-rSK/user/settings-module-admin.html#konfigurácia-modulu" @@ -29709,7 +29709,7 @@ },"4244": { "doc": "Settings — Modules & Admin", "title": "Module configuration", - "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Апісанне | . | MQTT enabled | Toggle MQTT bridge | . | Address | MQTT broker address | . | Імя карыстальніка | Authentication username | . | Пароль | Authentication password | . | Encryption enabled | Encrypt MQTT payloads | . | JSON output enabled | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS enabled | Use secure connection | . | Root topic | Base MQTT topic path | . | Proxy to client enabled | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Map reporting | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Апісанне | . | I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Map reporting interval (seconds) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Апісанне | . | Serial enabled | Activate serial communication | . | Echo enabled | Echo received serial data back | . | Serial mode | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Serial baud rate | Port speed | . | Скончыўся час чакання | How long to wait before considering an incoming message complete | . | Override console serial port | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Апісанне | . | External notification enabled | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Output LED (GPIO) | Pin the LED is wired to | . | Output LED active high | Whether the LED pin is active high or low | . | Output buzzer (GPIO) | Pin the buzzer is wired to | . | Output vibra (GPIO) | Pin the vibration motor is wired to | . | Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Use I2S as buzzer | Send the alert through an I2S audio output instead | . | Output duration (milliseconds) | How long a single alert lasts | . | Nag timeout (seconds) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Апісанне | . | Store & Forward enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | Number of records | Maximum stored messages | . | History return max | Max messages to replay | . | History return window | Time window for replay | . | Сервер | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Апісанне | . | Range test enabled | Activate range testing | . | Sender message interval (seconds) | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Save .CSV in storage (ESP32 only) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Апісанне | . | Send Device Telemetry | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Device metrics update interval | How often to report battery, uptime and channel utilization | . | Environment metrics module enabled | Report the attached environment sensors | . | Environment metrics update interval | How often to report them | . | Environment metrics on-screen enabled | Also show these readings on the device’s own display | . | Environment metrics use Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Air quality metrics module enabled | Report particulate and CO₂ sensor data | . | Air quality metrics update interval | How often to report them | . | Power metrics module enabled | Report the per-channel voltage and current readings | . | Power metrics update interval | How often to report them | . | Power metrics on-screen enabled | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Апісанне | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Паведамленні | Newline-separated list of messages | . | Send bell | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Rotary encoder #1 enabled | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Up/Down/Select input enabled | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Апісанне | . | CODEC 2 enabled | Activate audio module | . | CODEC2 sample rate | Audio quality/bandwidth tradeoff | . | PTT pin | GPIO pin for the push-to-talk button | . | I2S word select | GPIO pin for I2S WS | . | I2S data in | GPIO pin for I2S DIN | . | I2S data out | GPIO pin for I2S DOUT | . | I2S clock | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Апісанне | . | Remote Hardware enabled | Activate remote GPIO access | . | Allow undefined pin access | Allow access to any GPIO pin (security risk) | . | Available pins | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Апісанне | . | Neighbor Info enabled | Activate neighbor broadcasting | . | Update interval (seconds) | How often to broadcast neighbor list | . | Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Апісанне | . | LED state | Turn the LED on or off | . | 3 | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Апісанне | . | Detection Sensor enabled | Activate detection sensor | . | GPIO pin to monitor | GPIO pin connected to sensor | . | Detection trigger type | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Use INPUT_PULLUP mode | Enable the pin’s internal pull-up resistor | . | Minimum broadcast (seconds) | Minimum time between alert broadcasts | . | State broadcast (seconds) | Periodic state broadcast interval | . | Send bell with alert message | Include bell character in alerts | . | Friendly name | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Апісанне | . | Paxcounter enabled | Activate people counting | . | Update interval (seconds) | How often to report counts | . | Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ", + "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Апісанне | . | MQTT enabled | Toggle MQTT bridge | . | Address | MQTT broker address | . | Імя карыстальніка | Authentication username | . | Пароль | Authentication password | . | Encryption enabled | Encrypt MQTT payloads | . | JSON output enabled | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS enabled | Use secure connection | . | Root topic | Base MQTT topic path | . | Proxy to client enabled | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Map reporting | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Апісанне | . | I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Апісанне | . | Serial enabled | Activate serial communication | . | Echo enabled | Echo received serial data back | . | Serial mode | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Serial baud rate | Port speed | . | Скончыўся час чакання | How long to wait before considering an incoming message complete | . | Override console serial port | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Апісанне | . | External notification enabled | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Output LED (GPIO) | Pin the LED is wired to | . | Output LED active high | Whether the LED pin is active high or low | . | Output buzzer (GPIO) | Pin the buzzer is wired to | . | Output vibra (GPIO) | Pin the vibration motor is wired to | . | Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Use I2S as buzzer | Send the alert through an I2S audio output instead | . | GPIO Output Duration | How long a single alert lasts | . | Nag Timeout | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Апісанне | . | Store & Forward enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | Number of records | Maximum stored messages | . | History return max | Max messages to replay | . | History return window | Time window for replay | . | Сервер | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Апісанне | . | Range test enabled | Activate range testing | . | Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Save .CSV in storage (ESP32 only) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Апісанне | . | Send Device Telemetry | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Device metrics update interval | How often to report battery, uptime and channel utilization | . | Environment metrics module enabled | Report the attached environment sensors | . | Environment metrics update interval | How often to report them | . | Environment metrics on-screen enabled | Also show these readings on the device’s own display | . | Environment metrics use Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Air quality metrics module enabled | Report particulate and CO₂ sensor data | . | Air quality metrics update interval | How often to report them | . | Power metrics module enabled | Report the per-channel voltage and current readings | . | Power metrics update interval | How often to report them | . | Power metrics on-screen enabled | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Апісанне | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Паведамленні | Newline-separated list of messages | . | Send bell | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Rotary encoder #1 enabled | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Up/Down/Select input enabled | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Апісанне | . | CODEC 2 enabled | Activate audio module | . | CODEC2 sample rate | Audio quality/bandwidth tradeoff | . | PTT pin | GPIO pin for the push-to-talk button | . | I2S word select | GPIO pin for I2S WS | . | I2S data in | GPIO pin for I2S DIN | . | I2S data out | GPIO pin for I2S DOUT | . | I2S clock | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Апісанне | . | Remote Hardware enabled | Activate remote GPIO access | . | Allow undefined pin access | Allow access to any GPIO pin (security risk) | . | Available pins | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Апісанне | . | Neighbor Info enabled | Activate neighbor broadcasting | . | Update Interval | How often to broadcast neighbor list | . | Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Апісанне | . | LED state | Turn the LED on or off | . | 3 | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Апісанне | . | Detection Sensor enabled | Activate detection sensor | . | GPIO pin to monitor | GPIO pin connected to sensor | . | Detection trigger type | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Use INPUT_PULLUP mode | Enable the pin’s internal pull-up resistor | . | Minimum time between detection broadcasts | Minimum time between alert broadcasts | . | State Broadcast Interval | Periodic state broadcast interval | . | Send bell with alert message | Include bell character in alerts | . | Friendly name | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Апісанне | . | Paxcounter enabled | Activate people counting | . | Update Interval | How often to report counts | . | WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ", "url": "/Meshtastic-Android/main/be-rBY/user/settings-module-admin.html#module-configuration", "relUrl": "/be-rBY/user/settings-module-admin.html#module-configuration" @@ -29744,7 +29744,7 @@ },"4249": { "doc": "Settings — Modules & Admin", "title": "Impostazioni moduli", - "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Impostazione | Descrizione | . | MQTT abilitato | Toggle MQTT bridge | . | Indirizzo | MQTT broker address | . | Username | Authentication username | . | Password | Authentication password | . | Crittografia abilitata | Encrypt MQTT payloads | . | Output JSON abilitato | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS abilitato | Use secure connection | . | Root topic | Base MQTT topic path | . | Proxy to client attivato | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | Proxy MQTT su questo telefono | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Segnalazione su mappa | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Impostazione | Descrizione | . | Sono d’accordo. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Intervallo di segnalazione su mappa (secondi) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Impostazione | Descrizione | . | Seriale abilitata | Activate serial communication | . | Echo abilitato | Echo received serial data back | . | Modalità seriale | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Velocità della seriale | Port speed | . | Timeout | How long to wait before considering an incoming message complete | . | Sovrascrivi porta seriale della console | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Impostazione | Descrizione | . | Notifica esterna attivata | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | LED Output (GPIO) | Pin the LED is wired to | . | Output per LED active high | Whether the LED pin is active high or low | . | Output buzzer (GPIO) | Pin the buzzer is wired to | . | Output vibrazione (GPIO) | Pin the vibration motor is wired to | . | Usa buzzer PWM | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Usa I2S come buzzer | Send the alert through an I2S audio output instead | . | Durata output (millisecondi) | How long a single alert lasts | . | Timeout chiusura popup (secondi) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Suoneria | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Impostazione | Descrizione | . | Store & Forward abilitato | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | Numero di record | Maximum stored messages | . | Cronologia ritorno max | Max messages to replay | . | Finestra di ritorno cronologia | Time window for replay | . | Server | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Impostazione | Descrizione | . | Test distanza massima abilitato | Activate range testing | . | Intervallo messaggio mittente (secondi) | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Salva .CSV nella memoria (solo ESP32) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Impostazione | Descrizione | . | Invia Telemetria Dispositivo | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Intervallo aggiornamento metriche dispositivo | How often to report battery, uptime and channel utilization | . | Modulo metriche ambientali abilitato | Report the attached environment sensors | . | Intervallo aggiornamento metriche ambientali | How often to report them | . | Metriche ambientali visualizzate su schermo | Also show these readings on the device’s own display | . | Usa i gradi Fahrenheit nelle metriche ambientali | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Modulo metriche della qualità dell’aria abilitato | Report particulate and CO₂ sensor data | . | Intervallo aggiornamento metriche qualità aria | How often to report them | . | Modulo metriche di alimentazione abilitato | Report the per-channel voltage and current readings | . | Intervallo aggiornamento metriche alimentazione | How often to report them | . | Metriche di alimentazione visualizzate su schermo | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Impostazione | Descrizione | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Messaggi | Newline-separated list of messages | . | Invia campanella | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Encoder rotativo #1 abilitato | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Input Su/Giu/Selezione abilitato | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Impostazione | Descrizione | . | CODEC 2 attivato | Activate audio module | . | Frequenza di campionamento CODEC2 | Audio quality/bandwidth tradeoff | . | Pin PTT | GPIO pin for the push-to-talk button | . | I2S word select | GPIO pin for I2S WS | . | I2S data in | GPIO pin for I2S DIN | . | I2S data out | GPIO pin for I2S DOUT | . | I2S clock | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Impostazione | Descrizione | . | Hardware Remoto abilitato | Activate remote GPIO access | . | Consenti accesso a pin non definiti | Allow access to any GPIO pin (security risk) | . | Pin disponibili | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Impostazione | Descrizione | . | Info Nodi Vicini abilitato | Activate neighbor broadcasting | . | Intervallo di aggiornamento (secondi) | How often to broadcast neighbor list | . | Trasmettere su LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Impostazione | Descrizione | . | LED di stato | Turn the LED on or off | . | Attuale | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Impostazione | Descrizione | . | Sensore Rilevamento attivo | Activate detection sensor | . | Pin GPIO da monitorare | GPIO pin connected to sensor | . | Tipo di trigger di rilevamento | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Usa modalità INPUT_PULLUP | Enable the pin’s internal pull-up resistor | . | Trasmissione minima (secondi) | Minimum time between alert broadcasts | . | Trasmissione stato (secondi) | Periodic state broadcast interval | . | Invia campanella con messaggio di avviso | Include bell character in alerts | . | Nome semplificato | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Impostazione | Descrizione | . | Paxcounter abilitato | Activate people counting | . | Intervallo di aggiornamento (secondi) | How often to report counts | . | Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ", + "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Impostazione | Descrizione | . | MQTT abilitato | Toggle MQTT bridge | . | Indirizzo | MQTT broker address | . | Username | Authentication username | . | Password | Authentication password | . | Crittografia abilitata | Encrypt MQTT payloads | . | Output JSON abilitato | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS abilitato | Use secure connection | . | Root topic | Base MQTT topic path | . | Proxy to client attivato | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | Proxy MQTT su questo telefono | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Segnalazione su mappa | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Impostazione | Descrizione | . | Sono d’accordo. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Impostazione | Descrizione | . | Seriale abilitata | Activate serial communication | . | Echo abilitato | Echo received serial data back | . | Modalità seriale | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Velocità della seriale | Port speed | . | Timeout | How long to wait before considering an incoming message complete | . | Sovrascrivi porta seriale della console | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Impostazione | Descrizione | . | Notifica esterna attivata | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | LED Output (GPIO) | Pin the LED is wired to | . | Output per LED active high | Whether the LED pin is active high or low | . | Output buzzer (GPIO) | Pin the buzzer is wired to | . | Output vibrazione (GPIO) | Pin the vibration motor is wired to | . | Usa buzzer PWM | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Usa I2S come buzzer | Send the alert through an I2S audio output instead | . | GPIO Output Duration | How long a single alert lasts | . | Nag Timeout | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Suoneria | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Impostazione | Descrizione | . | Store & Forward abilitato | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | Numero di record | Maximum stored messages | . | Cronologia ritorno max | Max messages to replay | . | Finestra di ritorno cronologia | Time window for replay | . | Server | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Impostazione | Descrizione | . | Test distanza massima abilitato | Activate range testing | . | Intervallo Del Mittente | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Salva .CSV nella memoria (solo ESP32) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Impostazione | Descrizione | . | Invia Telemetria Dispositivo | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Intervallo aggiornamento metriche dispositivo | How often to report battery, uptime and channel utilization | . | Modulo metriche ambientali abilitato | Report the attached environment sensors | . | Intervallo aggiornamento metriche ambientali | How often to report them | . | Metriche ambientali visualizzate su schermo | Also show these readings on the device’s own display | . | Usa i gradi Fahrenheit nelle metriche ambientali | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Modulo metriche della qualità dell’aria abilitato | Report particulate and CO₂ sensor data | . | Intervallo aggiornamento metriche qualità aria | How often to report them | . | Modulo metriche di alimentazione abilitato | Report the per-channel voltage and current readings | . | Intervallo aggiornamento metriche alimentazione | How often to report them | . | Metriche di alimentazione visualizzate su schermo | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Impostazione | Descrizione | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Messaggi | Newline-separated list of messages | . | Invia campanella | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Encoder rotativo #1 abilitato | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Input Su/Giu/Selezione abilitato | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Impostazione | Descrizione | . | CODEC 2 attivato | Activate audio module | . | Frequenza di campionamento CODEC2 | Audio quality/bandwidth tradeoff | . | Pin PTT | GPIO pin for the push-to-talk button | . | I2S word select | GPIO pin for I2S WS | . | I2S data in | GPIO pin for I2S DIN | . | I2S data out | GPIO pin for I2S DOUT | . | I2S clock | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Impostazione | Descrizione | . | Hardware Remoto abilitato | Activate remote GPIO access | . | Consenti accesso a pin non definiti | Allow access to any GPIO pin (security risk) | . | Pin disponibili | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Impostazione | Descrizione | . | Info Nodi Vicini abilitato | Activate neighbor broadcasting | . | Intervallo Interrogazione GPS | How often to broadcast neighbor list | . | Trasmettere su LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Impostazione | Descrizione | . | LED di stato | Turn the LED on or off | . | Attuale | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Impostazione | Descrizione | . | Sensore Rilevamento attivo | Activate detection sensor | . | Pin GPIO da monitorare | GPIO pin connected to sensor | . | Tipo di trigger di rilevamento | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Usa modalità INPUT_PULLUP | Enable the pin’s internal pull-up resistor | . | Minimum time between detection broadcasts | Minimum time between alert broadcasts | . | Intervallo Di Trasmissione | Periodic state broadcast interval | . | Invia campanella con messaggio di avviso | Include bell character in alerts | . | Nome semplificato | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Impostazione | Descrizione | . | Paxcounter abilitato | Activate people counting | . | Intervallo Interrogazione GPS | How often to report counts | . | WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ", "url": "/Meshtastic-Android/main/it-rIT/user/settings-module-admin.html#impostazioni-moduli", "relUrl": "/it-rIT/user/settings-module-admin.html#impostazioni-moduli" @@ -29779,7 +29779,7 @@ },"4254": { "doc": "Settings — Modules & Admin", "title": "Configuración de módulo", - "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Descripción | . | Activar el MQTT | Toggle MQTT bridge | . | Dirección del Servidor MQTT | MQTT broker address | . | Usuario | Authentication username | . | Contraseña | Authentication password | . | Permitir Encripción | Encrypt MQTT payloads | . | Salida JSON activada | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS activado | Use secure connection | . | Tema raíz | Base MQTT topic path | . | Compartir Internet a la Radio | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Reportar Posición | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Descripción | . | Estoy de acuerdo. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Tiempo entre Reportes de Posición (en Segundos) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Descripción | . | Comunicación serial activada | Activate serial communication | . | Eco activado | Echo received serial data back | . | Modo serial | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Tasa de baudios por segundo | Port speed | . | Tiempo agotado | How long to wait before considering an incoming message complete | . | Sobreescribir el puerto serie de la consola | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Descripción | . | Notificaciones externas activadas | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Salida LED (pin GPIO) | Pin the LED is wired to | . | LED de salida activo en alto | Whether the LED pin is active high or low | . | Salida buzzer (pin GPIO) | Pin the buzzer is wired to | . | Salida vibratoria (pin GPIO) | Pin the vibration motor is wired to | . | Utilizar buzzer PWM | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Utilizar el Buzzer como uno I2S | Send the alert through an I2S audio output instead | . | Duración en las salidas (milisegundos) | How long a single alert lasts | . |   | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Tono de notificación | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Descripción | . | Descargar y reenviar activado | Activate store and forward | . | Pulso de vida | Periodically announce this node’s store-and-forward capability | . | Número de registros | Maximum stored messages | . | Historial máximo devuelto | Max messages to replay | . | History return window | Time window for replay | . | Servidor | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Descripción | . | Test de alcance activado | Activate range testing | . | Periodo entre los mensajes del transmisor (segundos) | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Guardar el .CSV en el almacenamiento (Esp32) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Descripción | . | Enviar telemetría del dispositivo | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Intervalo actualización de métricas del dispositivo | How often to report battery, uptime and channel utilization | . | Módulo para las medidas del entorno activado | Report the attached environment sensors | . | Intervalo actualización de métricas del entorno | How often to report them | . | Mostrar las medidas del entorno en la | Also show these readings on the device’s own display | . | Grados Fahrenheit para la temperatura ambiente | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Módulo para la medición de la calidad del aire activado | Report particulate and CO₂ sensor data | . | Intervalo actualización de métricas calidad del aire | How often to report them | . | Módulo de medidas eléctricas activado | Report the per-channel voltage and current readings | . | Intervalo de actualización de métricas de energía | How often to report them | . | Medidas eléctricas en pantalla | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Descripción | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Mensajes | Newline-separated list of messages | . | Mandar campana 🔔 | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Encoder Número 1 Activado | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Arriba/Abajo/Seleccionar Activado | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Descripción | . | CODEC 2 activado | Activate audio module | . | Frecuencia de Muestreo CODEC2 | Audio quality/bandwidth tradeoff | . | Pin PTT | GPIO pin for the push-to-talk button | . | Selecionar palabras I2S | GPIO pin for I2S WS | . | Entrada de datos I2S | GPIO pin for I2S DIN | . | Salida de datos I2S | GPIO pin for I2S DOUT | . | Reloj del I2S | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Descripción | . | Hardware remoto activado | Activate remote GPIO access | . | Permitir el acceso sin un pin definido | Allow access to any GPIO pin (security risk) | . | Pines disponibles | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Descripción | . | Información de Vecinos | Activate neighbor broadcasting | . | Intervalo de refresco (segundos) | How often to broadcast neighbor list | . | Transmitir en LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Descripción | . | Estado de led | Turn the LED on or off | . | Intensidad | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Descripción | . | Sensor detector activado | Activate detection sensor | . | Pin GPIO para monitorizar | GPIO pin connected to sensor | . | Tipo de detección para activar | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Utilizar el modo de entrada PULL_UP | Enable the pin’s internal pull-up resistor | . | Tiempo mínimo de transmisión (segundos) | Minimum time between alert broadcasts | . | Periodo entre transmisión de estado (segundos) | Periodic state broadcast interval | . | Mandar la campana con el mensaje de alerta | Include bell character in alerts | . | Mote | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Descripción | . | Activar el Contador de Paquetes | Activate people counting | . | Intervalo de refresco (segundos) | How often to report counts | . | Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ", + "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Descripción | . | Activar el MQTT | Toggle MQTT bridge | . | Dirección del Servidor MQTT | MQTT broker address | . | Usuario | Authentication username | . | Contraseña | Authentication password | . | Permitir Encripción | Encrypt MQTT payloads | . | Salida JSON activada | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS activado | Use secure connection | . | Tema raíz | Base MQTT topic path | . | Compartir Internet a la Radio | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Reportar Posición | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Descripción | . | Estoy de acuerdo. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Descripción | . | Comunicación serial activada | Activate serial communication | . | Eco activado | Echo received serial data back | . | Modo serial | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Tasa de baudios por segundo | Port speed | . | Tiempo agotado | How long to wait before considering an incoming message complete | . | Sobreescribir el puerto serie de la consola | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Descripción | . | Notificaciones externas activadas | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Salida LED (pin GPIO) | Pin the LED is wired to | . | LED de salida activo en alto | Whether the LED pin is active high or low | . | Salida buzzer (pin GPIO) | Pin the buzzer is wired to | . | Salida vibratoria (pin GPIO) | Pin the vibration motor is wired to | . | Utilizar buzzer PWM | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Utilizar el Buzzer como uno I2S | Send the alert through an I2S audio output instead | . | GPIO Output Duration | How long a single alert lasts | . | Nag Timeout | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Tono de notificación | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Descripción | . | Descargar y reenviar activado | Activate store and forward | . | Pulso de vida | Periodically announce this node’s store-and-forward capability | . | Número de registros | Maximum stored messages | . | Historial máximo devuelto | Max messages to replay | . | History return window | Time window for replay | . | Servidor | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Descripción | . | Test de alcance activado | Activate range testing | . | Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Guardar el .CSV en el almacenamiento (Esp32) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Descripción | . | Enviar telemetría del dispositivo | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Intervalo actualización de métricas del dispositivo | How often to report battery, uptime and channel utilization | . | Módulo para las medidas del entorno activado | Report the attached environment sensors | . | Intervalo actualización de métricas del entorno | How often to report them | . | Mostrar las medidas del entorno en la | Also show these readings on the device’s own display | . | Grados Fahrenheit para la temperatura ambiente | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Módulo para la medición de la calidad del aire activado | Report particulate and CO₂ sensor data | . | Intervalo actualización de métricas calidad del aire | How often to report them | . | Módulo de medidas eléctricas activado | Report the per-channel voltage and current readings | . | Intervalo de actualización de métricas de energía | How often to report them | . | Medidas eléctricas en pantalla | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Descripción | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Mensajes | Newline-separated list of messages | . | Mandar campana 🔔 | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Encoder Número 1 Activado | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Arriba/Abajo/Seleccionar Activado | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Descripción | . | CODEC 2 activado | Activate audio module | . | Frecuencia de Muestreo CODEC2 | Audio quality/bandwidth tradeoff | . | Pin PTT | GPIO pin for the push-to-talk button | . | Selecionar palabras I2S | GPIO pin for I2S WS | . | Entrada de datos I2S | GPIO pin for I2S DIN | . | Salida de datos I2S | GPIO pin for I2S DOUT | . | Reloj del I2S | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Descripción | . | Hardware remoto activado | Activate remote GPIO access | . | Permitir el acceso sin un pin definido | Allow access to any GPIO pin (security risk) | . | Pines disponibles | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Descripción | . | Información de Vecinos | Activate neighbor broadcasting | . | Intervalo de actualización | How often to broadcast neighbor list | . | Transmitir en LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Descripción | . | Estado de led | Turn the LED on or off | . | Intensidad | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Descripción | . | Sensor detector activado | Activate detection sensor | . | Pin GPIO para monitorizar | GPIO pin connected to sensor | . | Tipo de detección para activar | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Utilizar el modo de entrada PULL_UP | Enable the pin’s internal pull-up resistor | . | Minimum time between detection broadcasts | Minimum time between alert broadcasts | . | State Broadcast Interval | Periodic state broadcast interval | . | Mandar la campana con el mensaje de alerta | Include bell character in alerts | . | Mote | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Descripción | . | Activar el Contador de Paquetes | Activate people counting | . | Intervalo de actualización | How often to report counts | . | WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ", "url": "/Meshtastic-Android/main/es-rES/user/settings-module-admin.html#configuraci%C3%B3n-de-m%C3%B3dulo", "relUrl": "/es-rES/user/settings-module-admin.html#configuración-de-módulo" @@ -29814,7 +29814,7 @@ },"4259": { "doc": "Settings — Modules & Admin", "title": "Nastavitev modula", - "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Opis | . | MQTT enabled | Toggle MQTT bridge | . | Address | MQTT broker address | . | Username | Authentication username | . | Password | Authentication password | . | Encryption enabled | Encrypt MQTT payloads | . | JSON output enabled | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS enabled | Use secure connection | . | Root topic | Base MQTT topic path | . | Proxy to client enabled | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Map reporting | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Opis | . | I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Map reporting interval (seconds) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Opis | . | Serial enabled | Activate serial communication | . | Echo enabled | Echo received serial data back | . | Serial mode | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Serial baud rate | Port speed | . | Časovna omejitev | How long to wait before considering an incoming message complete | . | Override console serial port | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Opis | . | External notification enabled | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Output LED (GPIO) | Pin the LED is wired to | . | Output LED active high | Whether the LED pin is active high or low | . | Output buzzer (GPIO) | Pin the buzzer is wired to | . | Output vibra (GPIO) | Pin the vibration motor is wired to | . | Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Use I2S as buzzer | Send the alert through an I2S audio output instead | . | Output duration (milliseconds) | How long a single alert lasts | . | Nag timeout (seconds) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Opis | . | Store & Forward enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | Number of records | Maximum stored messages | . | History return max | Max messages to replay | . | History return window | Time window for replay | . | Server | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Opis | . | Range test enabled | Activate range testing | . | Sender message interval (seconds) | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Save .CSV in storage (ESP32 only) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Opis | . | Send Device Telemetry | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Device metrics update interval | How often to report battery, uptime and channel utilization | . | Environment metrics module enabled | Report the attached environment sensors | . | Environment metrics update interval | How often to report them | . | Environment metrics on-screen enabled | Also show these readings on the device’s own display | . | Environment metrics use Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Air quality metrics module enabled | Report particulate and CO₂ sensor data | . | Air quality metrics update interval | How often to report them | . | Power metrics module enabled | Report the per-channel voltage and current readings | . | Power metrics update interval | How often to report them | . | Power metrics on-screen enabled | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Opis | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Messages | Newline-separated list of messages | . | Send bell | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Rotary encoder #1 enabled | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Up/Down/Select input enabled | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Opis | . | CODEC 2 enabled | Activate audio module | . | CODEC2 sample rate | Audio quality/bandwidth tradeoff | . | PTT pin | GPIO pin for the push-to-talk button | . | I2S word select | GPIO pin for I2S WS | . | I2S data in | GPIO pin for I2S DIN | . | I2S data out | GPIO pin for I2S DOUT | . | I2S clock | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Opis | . | Remote Hardware enabled | Activate remote GPIO access | . | Allow undefined pin access | Allow access to any GPIO pin (security risk) | . | Available pins | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Opis | . | Neighbor Info enabled | Activate neighbor broadcasting | . | Update interval (seconds) | How often to broadcast neighbor list | . | Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Opis | . | LED state | Turn the LED on or off | . | Current | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Opis | . | Detection Sensor enabled | Activate detection sensor | . | GPIO pin to monitor | GPIO pin connected to sensor | . | Detection trigger type | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Use INPUT_PULLUP mode | Enable the pin’s internal pull-up resistor | . | Minimum broadcast (seconds) | Minimum time between alert broadcasts | . | State broadcast (seconds) | Periodic state broadcast interval | . | Send bell with alert message | Include bell character in alerts | . | Friendly name | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Opis | . | Paxcounter enabled | Activate people counting | . | Update interval (seconds) | How often to report counts | . | Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ", + "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Opis | . | MQTT enabled | Toggle MQTT bridge | . | Address | MQTT broker address | . | Username | Authentication username | . | Password | Authentication password | . | Encryption enabled | Encrypt MQTT payloads | . | JSON output enabled | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS enabled | Use secure connection | . | Root topic | Base MQTT topic path | . | Proxy to client enabled | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Map reporting | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Opis | . | I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Opis | . | Serial enabled | Activate serial communication | . | Echo enabled | Echo received serial data back | . | Serial mode | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Serial baud rate | Port speed | . | Časovna omejitev | How long to wait before considering an incoming message complete | . | Override console serial port | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Opis | . | External notification enabled | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Output LED (GPIO) | Pin the LED is wired to | . | Output LED active high | Whether the LED pin is active high or low | . | Output buzzer (GPIO) | Pin the buzzer is wired to | . | Output vibra (GPIO) | Pin the vibration motor is wired to | . | Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Use I2S as buzzer | Send the alert through an I2S audio output instead | . | GPIO Output Duration | How long a single alert lasts | . | Nag Timeout | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Opis | . | Store & Forward enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | Number of records | Maximum stored messages | . | History return max | Max messages to replay | . | History return window | Time window for replay | . | Server | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Opis | . | Range test enabled | Activate range testing | . | Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Save .CSV in storage (ESP32 only) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Opis | . | Send Device Telemetry | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Device metrics update interval | How often to report battery, uptime and channel utilization | . | Environment metrics module enabled | Report the attached environment sensors | . | Environment metrics update interval | How often to report them | . | Environment metrics on-screen enabled | Also show these readings on the device’s own display | . | Environment metrics use Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Air quality metrics module enabled | Report particulate and CO₂ sensor data | . | Air quality metrics update interval | How often to report them | . | Power metrics module enabled | Report the per-channel voltage and current readings | . | Power metrics update interval | How often to report them | . | Power metrics on-screen enabled | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Opis | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Messages | Newline-separated list of messages | . | Send bell | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Rotary encoder #1 enabled | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Up/Down/Select input enabled | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Opis | . | CODEC 2 enabled | Activate audio module | . | CODEC2 sample rate | Audio quality/bandwidth tradeoff | . | PTT pin | GPIO pin for the push-to-talk button | . | I2S word select | GPIO pin for I2S WS | . | I2S data in | GPIO pin for I2S DIN | . | I2S data out | GPIO pin for I2S DOUT | . | I2S clock | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Opis | . | Remote Hardware enabled | Activate remote GPIO access | . | Allow undefined pin access | Allow access to any GPIO pin (security risk) | . | Available pins | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Opis | . | Neighbor Info enabled | Activate neighbor broadcasting | . | Update Interval | How often to broadcast neighbor list | . | Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Opis | . | LED state | Turn the LED on or off | . | Current | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Opis | . | Detection Sensor enabled | Activate detection sensor | . | GPIO pin to monitor | GPIO pin connected to sensor | . | Detection trigger type | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Use INPUT_PULLUP mode | Enable the pin’s internal pull-up resistor | . | Minimum time between detection broadcasts | Minimum time between alert broadcasts | . | State Broadcast Interval | Periodic state broadcast interval | . | Send bell with alert message | Include bell character in alerts | . | Friendly name | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Opis | . | Paxcounter enabled | Activate people counting | . | Update Interval | How often to report counts | . | WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ", "url": "/Meshtastic-Android/main/sl-rSI/user/settings-module-admin.html#nastavitev-modula", "relUrl": "/sl-rSI/user/settings-module-admin.html#nastavitev-modula" @@ -29849,7 +29849,7 @@ },"4264": { "doc": "Settings — Modules & Admin", "title": "Modul konfigurasjon", - "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Beskrivelse | . | MQTT enabled | Toggle MQTT bridge | . | Address | MQTT broker address | . | Username | Authentication username | . | Password | Authentication password | . | Encryption enabled | Encrypt MQTT payloads | . | JSON output enabled | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS enabled | Use secure connection | . | Root topic | Base MQTT topic path | . | Proxy to client enabled | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Map reporting | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Beskrivelse | . | I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Map reporting interval (seconds) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Beskrivelse | . | Serial enabled | Activate serial communication | . | Echo enabled | Echo received serial data back | . | Serial mode | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Serial baud rate | Port speed | . | Tidsavbrudd | How long to wait before considering an incoming message complete | . | Override console serial port | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Beskrivelse | . | External notification enabled | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Output LED (GPIO) | Pin the LED is wired to | . | Output LED active high | Whether the LED pin is active high or low | . | Output buzzer (GPIO) | Pin the buzzer is wired to | . | Output vibra (GPIO) | Pin the vibration motor is wired to | . | Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Use I2S as buzzer | Send the alert through an I2S audio output instead | . | Output duration (milliseconds) | How long a single alert lasts | . | Nag timeout (seconds) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Beskrivelse | . | Store & Forward enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | Number of records | Maximum stored messages | . | History return max | Max messages to replay | . | History return window | Time window for replay | . | Server | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Beskrivelse | . | Range test enabled | Activate range testing | . | Sender message interval (seconds) | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Save .CSV in storage (ESP32 only) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Beskrivelse | . | Send Device Telemetry | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Device metrics update interval | How often to report battery, uptime and channel utilization | . | Environment metrics module enabled | Report the attached environment sensors | . | Environment metrics update interval | How often to report them | . | Environment metrics on-screen enabled | Also show these readings on the device’s own display | . | Environment metrics use Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Air quality metrics module enabled | Report particulate and CO₂ sensor data | . | Air quality metrics update interval | How often to report them | . | Power metrics module enabled | Report the per-channel voltage and current readings | . | Power metrics update interval | How often to report them | . | Power metrics on-screen enabled | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Beskrivelse | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Messages | Newline-separated list of messages | . | Send bell | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Rotary encoder #1 enabled | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Up/Down/Select input enabled | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Beskrivelse | . | CODEC 2 enabled | Activate audio module | . | CODEC2 sample rate | Audio quality/bandwidth tradeoff | . | PTT pin | GPIO pin for the push-to-talk button | . | I2S word select | GPIO pin for I2S WS | . | I2S data in | GPIO pin for I2S DIN | . | I2S data out | GPIO pin for I2S DOUT | . | I2S clock | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Beskrivelse | . | Remote Hardware enabled | Activate remote GPIO access | . | Allow undefined pin access | Allow access to any GPIO pin (security risk) | . | Available pins | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Beskrivelse | . | Neighbor Info enabled | Activate neighbor broadcasting | . | Update interval (seconds) | How often to broadcast neighbor list | . | Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Beskrivelse | . | LED state | Turn the LED on or off | . | Current | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Beskrivelse | . | Detection Sensor enabled | Activate detection sensor | . | GPIO pin to monitor | GPIO pin connected to sensor | . | Detection trigger type | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Use INPUT_PULLUP mode | Enable the pin’s internal pull-up resistor | . | Minimum broadcast (seconds) | Minimum time between alert broadcasts | . | State broadcast (seconds) | Periodic state broadcast interval | . | Send bell with alert message | Include bell character in alerts | . | Friendly name | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Beskrivelse | . | Paxcounter enabled | Activate people counting | . | Update interval (seconds) | How often to report counts | . | Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ", + "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Beskrivelse | . | MQTT enabled | Toggle MQTT bridge | . | Address | MQTT broker address | . | Username | Authentication username | . | Password | Authentication password | . | Encryption enabled | Encrypt MQTT payloads | . | JSON output enabled | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS enabled | Use secure connection | . | Root topic | Base MQTT topic path | . | Proxy to client enabled | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Map reporting | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Beskrivelse | . | I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Beskrivelse | . | Serial enabled | Activate serial communication | . | Echo enabled | Echo received serial data back | . | Serial mode | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Serial baud rate | Port speed | . | Tidsavbrudd | How long to wait before considering an incoming message complete | . | Override console serial port | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Beskrivelse | . | External notification enabled | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Output LED (GPIO) | Pin the LED is wired to | . | Output LED active high | Whether the LED pin is active high or low | . | Output buzzer (GPIO) | Pin the buzzer is wired to | . | Output vibra (GPIO) | Pin the vibration motor is wired to | . | Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Use I2S as buzzer | Send the alert through an I2S audio output instead | . | GPIO Output Duration | How long a single alert lasts | . | Nag Timeout | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Beskrivelse | . | Store & Forward enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | Number of records | Maximum stored messages | . | History return max | Max messages to replay | . | History return window | Time window for replay | . | Server | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Beskrivelse | . | Range test enabled | Activate range testing | . | Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Save .CSV in storage (ESP32 only) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Beskrivelse | . | Send Device Telemetry | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Device metrics update interval | How often to report battery, uptime and channel utilization | . | Environment metrics module enabled | Report the attached environment sensors | . | Environment metrics update interval | How often to report them | . | Environment metrics on-screen enabled | Also show these readings on the device’s own display | . | Environment metrics use Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Air quality metrics module enabled | Report particulate and CO₂ sensor data | . | Air quality metrics update interval | How often to report them | . | Power metrics module enabled | Report the per-channel voltage and current readings | . | Power metrics update interval | How often to report them | . | Power metrics on-screen enabled | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Beskrivelse | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Messages | Newline-separated list of messages | . | Send bell | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Rotary encoder #1 enabled | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Up/Down/Select input enabled | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Beskrivelse | . | CODEC 2 enabled | Activate audio module | . | CODEC2 sample rate | Audio quality/bandwidth tradeoff | . | PTT pin | GPIO pin for the push-to-talk button | . | I2S word select | GPIO pin for I2S WS | . | I2S data in | GPIO pin for I2S DIN | . | I2S data out | GPIO pin for I2S DOUT | . | I2S clock | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Beskrivelse | . | Remote Hardware enabled | Activate remote GPIO access | . | Allow undefined pin access | Allow access to any GPIO pin (security risk) | . | Available pins | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Beskrivelse | . | Neighbor Info enabled | Activate neighbor broadcasting | . | Update Interval | How often to broadcast neighbor list | . | Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Beskrivelse | . | LED state | Turn the LED on or off | . | Current | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Beskrivelse | . | Detection Sensor enabled | Activate detection sensor | . | GPIO pin to monitor | GPIO pin connected to sensor | . | Detection trigger type | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Use INPUT_PULLUP mode | Enable the pin’s internal pull-up resistor | . | Minimum time between detection broadcasts | Minimum time between alert broadcasts | . | State Broadcast Interval | Periodic state broadcast interval | . | Send bell with alert message | Include bell character in alerts | . | Friendly name | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Beskrivelse | . | Paxcounter enabled | Activate people counting | . | Update Interval | How often to report counts | . | WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ", "url": "/Meshtastic-Android/main/no-rNO/user/settings-module-admin.html#modul-konfigurasjon", "relUrl": "/no-rNO/user/settings-module-admin.html#modul-konfigurasjon" @@ -29884,7 +29884,7 @@ },"4269": { "doc": "Settings — Modules & Admin", "title": "Modul beállítások", - "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Leírás | . | MQTT engedélyezve | Toggle MQTT bridge | . | Cím | MQTT broker address | . | Felhasználónév | Authentication username | . | Jelszó | Authentication password | . | Titkosítás engedélyezve | Encrypt MQTT payloads | . | JSON kimenet engedélyezve | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS engedélyezve | Use secure connection | . | Gyökér téma | Base MQTT topic path | . | Proxy kliens felé engedélyezve | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Térképadat-jelentés | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Leírás | . | Elfogadom. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Térképadat-jelentés intervalluma (másodperc) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Leírás | . | Soros engedélyezve | Activate serial communication | . | Echo engedélyezve | Echo received serial data back | . | Soros mód | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Soros baud ráta | Port speed | . | Időtúllépés | How long to wait before considering an incoming message complete | . | Konzol soros port felülbírálása | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Leírás | . | Külső értesítés engedélyezve | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Kimeneti LED (GPIO) | Pin the LED is wired to | . | Kimeneti LED aktív magas szint | Whether the LED pin is active high or low | . | Kimeneti csipogó (GPIO) | Pin the buzzer is wired to | . | Kimeneti rezgő (GPIO) | Pin the vibration motor is wired to | . | PWM csipogó használata | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | I2S használata csipogóként | Send the alert through an I2S audio output instead | . | Kimeneti időtartam (ezredmásodperc) | How long a single alert lasts | . | Ismétlő riasztás időkorlát (másodperc) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Csengőhang | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Leírás | . | Tárolás és továbbítás engedélyezve | Activate store and forward | . | Heartbeat jel | Periodically announce this node’s store-and-forward capability | . | Rekordok száma | Maximum stored messages | . | Előzmény-visszaadás maximum | Max messages to replay | . | Előzmény-visszaadás időablak | Time window for replay | . | Szerver | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Leírás | . | Hatótáv-teszt engedélyezve | Activate range testing | . | Küldési üzenetintervallum (másodperc) | Time between test transmissions, chosen from a dropdown of fixed intervals | . | .CSV mentése a tárhelyre (csak ESP32) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Leírás | . | Eszköztelemetria küldése | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Eszközmetrikák frissítési időköze | How often to report battery, uptime and channel utilization | . | Környezeti metrika modul engedélyezve | Report the attached environment sensors | . | Környezeti metrikák frissítési időköze | How often to report them | . | Környezeti metrikák megjelenítése képernyőn | Also show these readings on the device’s own display | . | Környezeti metrikák Fahrenheit-ben | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Levegőminőség-metrika modul engedélyezve | Report particulate and CO₂ sensor data | . | Levegőminőségi metrikák frissítési időköze | How often to report them | . | Energia-metrika modul engedélyezve | Report the per-channel voltage and current readings | . | Tápellátási metrikák frissítési időköze | How often to report them | . | Energia-metrikák megjelenítése képernyőn engedélyezve | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Leírás | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Üzenetek | Newline-separated list of messages | . | Harangjel küldése | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | 1. forgóenkóder engedélyezve | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Fel/Le/Kiválaszt gomb engedélyezve | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Leírás | . | CODEC 2 engedélyezve | Activate audio module | . | CODEC2 mintavételi ráta | Audio quality/bandwidth tradeoff | . | PTT pin | GPIO pin for the push-to-talk button | . | I2S szóválasztás | GPIO pin for I2S WS | . | I2S adat be | GPIO pin for I2S DIN | . | I2S adat ki | GPIO pin for I2S DOUT | . | I2S órajel | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Leírás | . | Távoli hardver engedélyezve | Activate remote GPIO access | . | Nem definiált pinek elérésének engedélyezése | Allow access to any GPIO pin (security risk) | . | Elérhető pinek | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Leírás | . | Szomszéd-információ engedélyezve | Activate neighbor broadcasting | . | Frissítési intervallum (másodperc) | How often to broadcast neighbor list | . | Továbbítás LoRa-n keresztül | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Leírás | . | LED állapot | Turn the LED on or off | . | Áramerősség | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Leírás | . | Érzékelő szenzor engedélyezve | Activate detection sensor | . | Figyelt GPIO láb | GPIO pin connected to sensor | . | Érzékelési ravasztípus | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | INPUT_PULLUP mód használata | Enable the pin’s internal pull-up resistor | . | Minimális sugárzási idő (másodperc) | Minimum time between alert broadcasts | . | Állapot-sugárzás (másodperc) | Periodic state broadcast interval | . | Harangjel küldése riasztási üzenettel | Include bell character in alerts | . | Barátságos név | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Leírás | . | Paxcounter engedélyezve | Activate people counting | . | Frissítési intervallum (másodperc) | How often to report counts | . | Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ", + "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Leírás | . | MQTT engedélyezve | Toggle MQTT bridge | . | Cím | MQTT broker address | . | Felhasználónév | Authentication username | . | Jelszó | Authentication password | . | Titkosítás engedélyezve | Encrypt MQTT payloads | . | JSON kimenet engedélyezve | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS engedélyezve | Use secure connection | . | Gyökér téma | Base MQTT topic path | . | Proxy kliens felé engedélyezve | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Térképadat-jelentés | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Leírás | . | Elfogadom. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Leírás | . | Soros engedélyezve | Activate serial communication | . | Echo engedélyezve | Echo received serial data back | . | Soros mód | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Soros baud ráta | Port speed | . | Időtúllépés | How long to wait before considering an incoming message complete | . | Konzol soros port felülbírálása | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Leírás | . | Külső értesítés engedélyezve | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Kimeneti LED (GPIO) | Pin the LED is wired to | . | Kimeneti LED aktív magas szint | Whether the LED pin is active high or low | . | Kimeneti csipogó (GPIO) | Pin the buzzer is wired to | . | Kimeneti rezgő (GPIO) | Pin the vibration motor is wired to | . | PWM csipogó használata | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | I2S használata csipogóként | Send the alert through an I2S audio output instead | . | GPIO Output Duration | How long a single alert lasts | . | Nag Timeout | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Csengőhang | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Leírás | . | Tárolás és továbbítás engedélyezve | Activate store and forward | . | Heartbeat jel | Periodically announce this node’s store-and-forward capability | . | Rekordok száma | Maximum stored messages | . | Előzmény-visszaadás maximum | Max messages to replay | . | Előzmény-visszaadás időablak | Time window for replay | . | Szerver | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Leírás | . | Hatótáv-teszt engedélyezve | Activate range testing | . | Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals | . | .CSV mentése a tárhelyre (csak ESP32) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Leírás | . | Eszköztelemetria küldése | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Eszközmetrikák frissítési időköze | How often to report battery, uptime and channel utilization | . | Környezeti metrika modul engedélyezve | Report the attached environment sensors | . | Környezeti metrikák frissítési időköze | How often to report them | . | Környezeti metrikák megjelenítése képernyőn | Also show these readings on the device’s own display | . | Környezeti metrikák Fahrenheit-ben | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Levegőminőség-metrika modul engedélyezve | Report particulate and CO₂ sensor data | . | Levegőminőségi metrikák frissítési időköze | How often to report them | . | Energia-metrika modul engedélyezve | Report the per-channel voltage and current readings | . | Tápellátási metrikák frissítési időköze | How often to report them | . | Energia-metrikák megjelenítése képernyőn engedélyezve | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Leírás | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Üzenetek | Newline-separated list of messages | . | Harangjel küldése | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | 1. forgóenkóder engedélyezve | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Fel/Le/Kiválaszt gomb engedélyezve | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Leírás | . | CODEC 2 engedélyezve | Activate audio module | . | CODEC2 mintavételi ráta | Audio quality/bandwidth tradeoff | . | PTT pin | GPIO pin for the push-to-talk button | . | I2S szóválasztás | GPIO pin for I2S WS | . | I2S adat be | GPIO pin for I2S DIN | . | I2S adat ki | GPIO pin for I2S DOUT | . | I2S órajel | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Leírás | . | Távoli hardver engedélyezve | Activate remote GPIO access | . | Nem definiált pinek elérésének engedélyezése | Allow access to any GPIO pin (security risk) | . | Elérhető pinek | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Leírás | . | Szomszéd-információ engedélyezve | Activate neighbor broadcasting | . | Frissítési időköz | How often to broadcast neighbor list | . | Továbbítás LoRa-n keresztül | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Leírás | . | LED állapot | Turn the LED on or off | . | Áramerősség | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Leírás | . | Érzékelő szenzor engedélyezve | Activate detection sensor | . | Figyelt GPIO láb | GPIO pin connected to sensor | . | Érzékelési ravasztípus | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | INPUT_PULLUP mód használata | Enable the pin’s internal pull-up resistor | . | Minimum time between detection broadcasts | Minimum time between alert broadcasts | . | State Broadcast Interval | Periodic state broadcast interval | . | Harangjel küldése riasztási üzenettel | Include bell character in alerts | . | Barátságos név | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Leírás | . | Paxcounter engedélyezve | Activate people counting | . | Frissítési időköz | How often to report counts | . | WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ", "url": "/Meshtastic-Android/main/hu-rHU/user/settings-module-admin.html#modul-be%C3%A1ll%C3%ADt%C3%A1sok", "relUrl": "/hu-rHU/user/settings-module-admin.html#modul-beállítások" @@ -29919,7 +29919,7 @@ },"4274": { "doc": "Настройки — Модули и администрирование", "title": "Настройки модуля", - "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Мосты передают сообщения туда и обратно от брокера MQTT для подключения к интернету. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Настройка | Описание | . | MQTT включен | Переключить MQTT мост | . | Адрес | Адрес MQTT брокера | . | Имя пользователя | Имя пользователя для аутентификации | . | Пароль | Пароль аутентификации | . | Шифрование включено | Зашифровать MQTT-пейлоады | . | Вывод JSON включен | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS включен | Использовать защищённое соединение | . | Корневая тема | Базовый путь темы MQTT | . | Прокси клиенту включен | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT-прокси на этом телефоне | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Отчёты по карте | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Настройка | Описание | . | Я согласен. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Интервал отчета карты (в секундах) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . См. MQTT для подробного руководства по использованию, включая шифрование, конфиденциальность и настройку брокера. Serial module . Позволяет общаться через последовательный порт с внешними устройствами (GPS-модулями, датчиками или собственной техникой). Когда включено, последовательный порт ноды может отправлять и получать данные в формате protobuf или текст, что позволяет внешним микроконтроллерам или компьютерам взаимодействовать с сетью. | Настройка | Описание | . | COM-порт включен | Включить последовательное соединение | . | Echo включен | Echo получил обратно последовательные данные | . | Режим COM-порта | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Скорость COM-порта | Port speed | . | Время ожидания истекло | How long to wait before considering an incoming message complete | . | Переопределить COM-порт консоли | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Полезно для устройств, которым нужно физически сигнализировать о приходе сообщения — особенно удобно для неоснащенных персоналом или уличных установок. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Настройка | Описание | . | Внешние уведомления включены | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Выход LED (GPIO) | Pin the LED is wired to | . | Вывод светодиода активный высокий | Whether the LED pin is active high or low | . | Выход Буззера (GPIO) | Pin the buzzer is wired to | . | Вибросигнал (GPIO) | Pin the vibration motor is wired to | . | Использовать PWM-звукоизлучатель | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Использовать I2S как буззер | Send the alert through an I2S audio output instead | . | Продолжительность вывода (миллисекунды) | How long a single alert lasts | . | Таймаут Nag (в секундах) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Рингтон | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Буферизирует сообщения для узлов, которые временно были недоступны, а затем ретранслирует их, когда эти узлы переподключаются. Важное значение для сеток, где узлы входят и выходят вне диапазона регулярно - обеспечивает отсутствие потери сообщений при коротких разъединениях. | Настройка | Описание | . | Store & Forward включен | Активировать режим хранения и пересылки | . | Heartbeat | Периодически объявлять о наличии функции хранения и пересылки у этого узла | . | Количество записей | Максимальное количество сохраненных сообщений | . | Макс возврат истории | Максимум сообщений для повтора | . | Окно возврата истории | Окно времени для повтора | . | Сервер | Действовать как сервер хранения и пересылки для mesh-сети (требуется большой объем памяти, например, ESP32 с PSRAM) | . 💡 Совет: Хранение и пересылка лучше всего работает на узлах с достаточной памятью (ESP32 с PSRAM). Узлы маршрутизатора являются идеальными кандидатами, так как они обычно всегда включены. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Автоматизированный инструмент для проверки дальности и оценки качества связи между нодами. Когда включено, нода периодически отправляет сообщения с увеличивающимся счетчиком. Приёмная нода записывает эти сообщения, что позволяет тебе уйти пешком или уехать на машине, а потом проанализировать, на каком расстоянии сообщения перестали приходить. | Настройка | Описание | . | Проверка дальности включена | Активировать проверку дальности | . | Интервал сообщений отправителя (в секундах) | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Сохранить .CSV в хранилище (только ESP32) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Контролирует какими телеметрическими данными ваш узел делится с сеткой. Телеметрия включает данные о состоянии устройства (заряд батареи, время работы) и данные с датчиков окружающей среды (температура, влажность, давление). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Настройка | Описание | . | Отправлять телеметрию устройства | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Интервал обновления метрик устройства | How often to report battery, uptime and channel utilization | . | Модуль метрик окружения включен | Report the attached environment sensors | . | Интервал обновления метрик среды | How often to report them | . | Показатели окружения на экране включены | Also show these readings on the device’s own display | . | Использовать метрику окружения в Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Модуль измерения качества воздуха включен | Report particulate and CO₂ sensor data | . | Интервал обновления данных качества воздуха | How often to report them | . | Модуль метрик питания включен | Report the per-channel voltage and current readings | . | Интервал обновления метрик электропитания | How often to report them | . | Включить метрики питания на экране | Also show power readings on the device’s display | . Посмотрите Телеметрия и датчики — для получения информации о поддерживаемых датчиках и рекомендациях по настройке. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Определите список быстрых сообщений, которые могут быть переданы без подключённого телефона — идеально подходит для использования в поле. | Настройка | Описание | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Сообщения | Список сообщений, разделённых новой строкой | . | Отправить колокольчик | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Поворотный энкодер #1 включен | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Вверх/Вниз/Выбирать включён | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Поддержка аудио Codec2 для низкополосной голосовой связи через сетку. Это экспериментальная функция, которая кодирует голос в очень маленькие пакеты данных с помощью кодека Codec2. | Настройка | Описание | . | CODEC 2 включен | Активировать модуль аудио | . | Частота дискретизации CODEC2 | Компромисс между качеством звука и полосой пропускания | . | Контакт PTT | GPIO pin for the push-to-talk button | . | I2S Word Select | GPIO контакт для I2S WS | . | I2S Data In | Пин GPIO для I2S DIN | . | I2S Data Out | Пин GPIO для I2S DOUT | . | I2S Clock | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Качество голоса очень низкополосное — представьте себе «разборчивую радиосвязь», а не качество телефонного звонка. Remote Hardware module . Управление GPIO через mesh-сеть. Позволяет удалённому узлу читать и записывать состояния выводов GPIO на другом узле — полезно для активации реле, опроса переключателей или удалённого управления внешним оборудованием. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Настройка | Описание | . | Удаленное оборудование включено | Активировать удаленный GPIO доступ | . | Разрешить неопределённый контакт | Разрешить доступ к любому GPIO-пину (риск для безопасности) | . | Доступные контакты | До 4 пинов GPIO, которые этот узел предоставляет для удалённого чтения и записи | . Neighbor Info module . Транслирует информацию о доступных услышанных соседей, включив ячейку сеточной топологии. Каждый включенный узел периодически делится списком других узлов которые он может слышать и их качество сигнала. | Настройка | Описание | . | Информация о соседях включена | Включить трансляцию соседей | . | Интервал обновления (в секундах) | Как часто транслировать список соседей | . | Передать через LoRa | Также транслировать информацию соседей по LoRa, а не только MQTT/телефон. Недоступно на канале используя ключ по умолчанию и имя | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Управляет встроенными светодиодами NeoPixel или другими адресуемыми RGB-светодиодами на поддерживаемом оборудовании. Может использоваться для визуальных статусовых индикаторов, световых уведомлений, или декоративных эффектов. | Настройка | Описание | . | Состояние LED | Включить или выключить светодиод | . | Ток | Текущий лимит светодиодов (0–31) | . | Красный / Зеленый / Синий | Индивидуальные значения цветов канала (0–255) | . Detection Sensor module . Превращает ваш узел в систему сигнализации на основе датчика движения или открытия двери. При обнаружении изменения состояния на выводе GPIO (например, сработал датчик движения или открылась дверь) узел отправляет по меш-сети оповещение. | Настройка | Описание | . | Датчик определения включен | Активировать датчик обнаружения | . | GPIO контакт для мониторинга | Пин GPIO, подключенный к датчику | . | Тип триггера обнаружения | Как состояние пина интерпретируется как событие обнаружения (например, активный высокий/низкий уровень, срабатывание по фронту) | . | Использовать режим INPUT_PULLUP | Включить внутренний подтягивающий резистор пина | . | Минимальная трансляция (в секундах) | Минимальный интервал между оповещениями | . | Трансляция состояния (в секундах) | Интервал периодической отправки состояния | . | Отправить колокол с уведомлением | Включать символ колокола в оповещения | . | Понятное имя | Пользовательское имя для этого датчика | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Засчитывает ближайшие устройства, пассивно прослушивая зондирующие запросы, чтобы телефоны и ноутбуки излучали при сканировании сетей. Доступно только на устройствах ESP32. | Настройка | Описание | . | Paxcounter включен | Активировать подсчет людей | . | Интервал обновления (в секундах) | Как часто сообщать подсчитывания | . | Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Совет: Paxcounter полезен для приблизительной оценки пешеходного потока в местах начала маршрутов, на мероприятийных площадках или в других локациях. Счетчики приблизительны — один человек может иметь несколько устройств. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Интеграция Team Awareness Kit для совместимости с ATAK и WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. См. TAK Integration для детальной настройки и использования. ", + "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Мосты передают сообщения туда и обратно от брокера MQTT для подключения к интернету. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Настройка | Описание | . | MQTT включен | Переключить MQTT мост | . | Адрес | Адрес MQTT брокера | . | Имя пользователя | Имя пользователя для аутентификации | . | Пароль | Пароль аутентификации | . | Шифрование включено | Зашифровать MQTT-пейлоады | . | Вывод JSON включен | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS включен | Использовать защищённое соединение | . | Корневая тема | Базовый путь темы MQTT | . | Прокси клиенту включен | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT-прокси на этом телефоне | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Отчёты по карте | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Настройка | Описание | . | Я согласен. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . См. MQTT для подробного руководства по использованию, включая шифрование, конфиденциальность и настройку брокера. Serial module . Позволяет общаться через последовательный порт с внешними устройствами (GPS-модулями, датчиками или собственной техникой). Когда включено, последовательный порт ноды может отправлять и получать данные в формате protobuf или текст, что позволяет внешним микроконтроллерам или компьютерам взаимодействовать с сетью. | Настройка | Описание | . | COM-порт включен | Включить последовательное соединение | . | Echo включен | Echo получил обратно последовательные данные | . | Режим COM-порта | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Скорость COM-порта | Port speed | . | Время ожидания истекло | How long to wait before considering an incoming message complete | . | Переопределить COM-порт консоли | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Полезно для устройств, которым нужно физически сигнализировать о приходе сообщения — особенно удобно для неоснащенных персоналом или уличных установок. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Настройка | Описание | . | Внешние уведомления включены | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Выход LED (GPIO) | Pin the LED is wired to | . | Вывод светодиода активный высокий | Whether the LED pin is active high or low | . | Выход Буззера (GPIO) | Pin the buzzer is wired to | . | Вибросигнал (GPIO) | Pin the vibration motor is wired to | . | Использовать PWM-звукоизлучатель | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Использовать I2S как буззер | Send the alert through an I2S audio output instead | . | GPIO Output Duration | How long a single alert lasts | . | Интервал повтора | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Рингтон | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Буферизирует сообщения для узлов, которые временно были недоступны, а затем ретранслирует их, когда эти узлы переподключаются. Важное значение для сеток, где узлы входят и выходят вне диапазона регулярно - обеспечивает отсутствие потери сообщений при коротких разъединениях. | Настройка | Описание | . | Store & Forward включен | Активировать режим хранения и пересылки | . | Heartbeat | Периодически объявлять о наличии функции хранения и пересылки у этого узла | . | Количество записей | Максимальное количество сохраненных сообщений | . | Макс возврат истории | Максимум сообщений для повтора | . | Окно возврата истории | Окно времени для повтора | . | Сервер | Действовать как сервер хранения и пересылки для mesh-сети (требуется большой объем памяти, например, ESP32 с PSRAM) | . 💡 Совет: Хранение и пересылка лучше всего работает на узлах с достаточной памятью (ESP32 с PSRAM). Узлы маршрутизатора являются идеальными кандидатами, так как они обычно всегда включены. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Автоматизированный инструмент для проверки дальности и оценки качества связи между нодами. Когда включено, нода периодически отправляет сообщения с увеличивающимся счетчиком. Приёмная нода записывает эти сообщения, что позволяет тебе уйти пешком или уехать на машине, а потом проанализировать, на каком расстоянии сообщения перестали приходить. | Настройка | Описание | . | Проверка дальности включена | Активировать проверку дальности | . | Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Сохранить .CSV в хранилище (только ESP32) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Контролирует какими телеметрическими данными ваш узел делится с сеткой. Телеметрия включает данные о состоянии устройства (заряд батареи, время работы) и данные с датчиков окружающей среды (температура, влажность, давление). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Настройка | Описание | . | Отправлять телеметрию устройства | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Интервал обновления метрик устройства | How often to report battery, uptime and channel utilization | . | Модуль метрик окружения включен | Report the attached environment sensors | . | Интервал обновления метрик среды | How often to report them | . | Показатели окружения на экране включены | Also show these readings on the device’s own display | . | Использовать метрику окружения в Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Модуль измерения качества воздуха включен | Report particulate and CO₂ sensor data | . | Интервал обновления данных качества воздуха | How often to report them | . | Модуль метрик питания включен | Report the per-channel voltage and current readings | . | Интервал обновления метрик электропитания | How often to report them | . | Включить метрики питания на экране | Also show power readings on the device’s display | . Посмотрите Телеметрия и датчики — для получения информации о поддерживаемых датчиках и рекомендациях по настройке. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Определите список быстрых сообщений, которые могут быть переданы без подключённого телефона — идеально подходит для использования в поле. | Настройка | Описание | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Сообщения | Список сообщений, разделённых новой строкой | . | Отправить колокольчик | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Поворотный энкодер #1 включен | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Вверх/Вниз/Выбирать включён | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Поддержка аудио Codec2 для низкополосной голосовой связи через сетку. Это экспериментальная функция, которая кодирует голос в очень маленькие пакеты данных с помощью кодека Codec2. | Настройка | Описание | . | CODEC 2 включен | Активировать модуль аудио | . | Частота дискретизации CODEC2 | Компромисс между качеством звука и полосой пропускания | . | Контакт PTT | GPIO pin for the push-to-talk button | . | I2S Word Select | GPIO контакт для I2S WS | . | I2S Data In | Пин GPIO для I2S DIN | . | I2S Data Out | Пин GPIO для I2S DOUT | . | I2S Clock | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Качество голоса очень низкополосное — представьте себе «разборчивую радиосвязь», а не качество телефонного звонка. Remote Hardware module . Управление GPIO через mesh-сеть. Позволяет удалённому узлу читать и записывать состояния выводов GPIO на другом узле — полезно для активации реле, опроса переключателей или удалённого управления внешним оборудованием. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Настройка | Описание | . | Удаленное оборудование включено | Активировать удаленный GPIO доступ | . | Разрешить неопределённый контакт | Разрешить доступ к любому GPIO-пину (риск для безопасности) | . | Доступные контакты | До 4 пинов GPIO, которые этот узел предоставляет для удалённого чтения и записи | . Neighbor Info module . Транслирует информацию о доступных услышанных соседей, включив ячейку сеточной топологии. Каждый включенный узел периодически делится списком других узлов которые он может слышать и их качество сигнала. | Настройка | Описание | . | Информация о соседях включена | Включить трансляцию соседей | . | Интервал опроса GPS | Как часто транслировать список соседей | . | Передать через LoRa | Также транслировать информацию соседей по LoRa, а не только MQTT/телефон. Недоступно на канале используя ключ по умолчанию и имя | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Управляет встроенными светодиодами NeoPixel или другими адресуемыми RGB-светодиодами на поддерживаемом оборудовании. Может использоваться для визуальных статусовых индикаторов, световых уведомлений, или декоративных эффектов. | Настройка | Описание | . | Состояние LED | Включить или выключить светодиод | . | Ток | Текущий лимит светодиодов (0–31) | . | Красный / Зеленый / Синий | Индивидуальные значения цветов канала (0–255) | . Detection Sensor module . Превращает ваш узел в систему сигнализации на основе датчика движения или открытия двери. При обнаружении изменения состояния на выводе GPIO (например, сработал датчик движения или открылась дверь) узел отправляет по меш-сети оповещение. | Настройка | Описание | . | Датчик определения включен | Активировать датчик обнаружения | . | GPIO контакт для мониторинга | Пин GPIO, подключенный к датчику | . | Тип триггера обнаружения | Как состояние пина интерпретируется как событие обнаружения (например, активный высокий/низкий уровень, срабатывание по фронту) | . | Использовать режим INPUT_PULLUP | Включить внутренний подтягивающий резистор пина | . | Minimum time between detection broadcasts | Минимальный интервал между оповещениями | . | State Broadcast Interval | Интервал периодической отправки состояния | . | Отправить колокол с уведомлением | Включать символ колокола в оповещения | . | Понятное имя | Пользовательское имя для этого датчика | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Засчитывает ближайшие устройства, пассивно прослушивая зондирующие запросы, чтобы телефоны и ноутбуки излучали при сканировании сетей. Доступно только на устройствах ESP32. | Настройка | Описание | . | Paxcounter включен | Активировать подсчет людей | . | Интервал опроса GPS | Как часто сообщать подсчитывания | . | WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Совет: Paxcounter полезен для приблизительной оценки пешеходного потока в местах начала маршрутов, на мероприятийных площадках или в других локациях. Счетчики приблизительны — один человек может иметь несколько устройств. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Интеграция Team Awareness Kit для совместимости с ATAK и WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. См. TAK Integration для детальной настройки и использования. ", "url": "/Meshtastic-Android/main/ru-rRU/user/settings-module-admin.html#%D0%BD%D0%B0%D1%81%D1%82%D1%80%D0%BE%D0%B9%D0%BA%D0%B8-%D0%BC%D0%BE%D0%B4%D1%83%D0%BB%D1%8F", "relUrl": "/ru-rRU/user/settings-module-admin.html#настройки-модуля" @@ -29947,7 +29947,7 @@ },"4278": { "doc": "Settings — Modules & Admin", "title": "Nastavení modulů", - "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Nastavení | Popis | . | MQTT povoleno | Toggle MQTT bridge | . | Adresa | MQTT broker address | . | Uživatelské jméno | Authentication username | . | Heslo | Authentication password | . | Šifrování povoleno | Encrypt MQTT payloads | . | JSON výstup povolen | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS povoleno | Use secure connection | . | Kořenové téma | Base MQTT topic path | . | Proxy na klienta povoleno | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy na tomto telefonu | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Hlášení mapy | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Nastavení | Popis | . | Souhlasím. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Interval hlášení mapy | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Nastavení | Popis | . | Sériová komunikace povolena | Activate serial communication | . | Povolit echo | Echo received serial data back | . | Sériový režim | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Rychlost sériového přenosu | Port speed | . | Vypršel čas spojení | How long to wait before considering an incoming message complete | . | Přepsat sériový port komunikace | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Nastavení | Popis | . | Externí oznámení povoleno | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Výstupní LED (GPIO) | Pin the LED is wired to | . | Výstupní LED aktivní při HIGH | Whether the LED pin is active high or low | . | Výstupní pin bzučáku (GPIO) | Pin the buzzer is wired to | . | Výstupní pin vybračního motorku (GPIO) | Pin the vibration motor is wired to | . | Použít PWM bzučák | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Použít I2S jako bzučák | Send the alert through an I2S audio output instead | . | Doba trvání výstupu (v milisekundách) | How long a single alert lasts | . | Interval opakovaného zvonění | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Vyzváněcí tón | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Nastavení | Popis | . | Uložit a přeposlat povoleno | Activate store and forward | . | Pulzující LED | Periodically announce this node’s store-and-forward capability | . | Počet záznamů | Maximum stored messages | . | Max. počet záznamů historie | Max messages to replay | . | Časové okno historie | Time window for replay | . | Server | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Nastavení | Popis | . | Test pokrytí povolen | Activate range testing | . | Interval odesílání zpráv | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Uložit .CSV do úložiště (pouze ESP32) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Nastavení | Popis | . | Odesílat telemetrii zařízení | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Interval aktualizace metrik zařízení | How often to report battery, uptime and channel utilization | . | Modul měření životního prostředí povolen | Report the attached environment sensors | . | Interval aktualizace měření životního prostředí | How often to report them | . | Zobrazení měření životního prostředí povoleno | Also show these readings on the device’s own display | . | Měření životního prostředí používá Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Modul měření kvality ovzduší povolen | Report particulate and CO₂ sensor data | . | Interval aktualizace měření kvality ovzduší | How often to report them | . | Modul měření spotřeby povolen | Report the per-channel voltage and current readings | . | Interval aktualizace měření napájení | How often to report them | . | Měření spotřeby na obrazovce povoleno | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Nastavení | Popis | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Zprávy | Newline-separated list of messages | . | Odeslat zvonek | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Rotační enkodér #1 povolen | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Vstup Nahoru/Dolů/Výběr povolen | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Nastavení | Popis | . | CODEC 2 enabled | Activate audio module | . | CODEC2 sample rate | Audio quality/bandwidth tradeoff | . | PTT pin | GPIO pin for the push-to-talk button | . | I2S výběr slov | GPIO pin for I2S WS | . | I2S vstupní data | GPIO pin for I2S DIN | . | I2S výstupní data | GPIO pin for I2S DOUT | . | I2S clock | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Nastavení | Popis | . | Vzdálený modul povolen | Activate remote GPIO access | . | Povolit přiřazení nedefinovaného pinu | Allow access to any GPIO pin (security risk) | . | Dostupné piny | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Nastavení | Popis | . | Informace o sousedech povoleny | Activate neighbor broadcasting | . | Interval aktualizace (v sekundách) | How often to broadcast neighbor list | . | Přenos přes LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Nastavení | Popis | . | Stav LED | Turn the LED on or off | . | Proud | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Nastavení | Popis | . | Detekční senzor povolen | Activate detection sensor | . | GPIO pin ke sledování | GPIO pin connected to sensor | . | Typ spouštění detekce | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Použít INPUT_PULLUP režim | Enable the pin’s internal pull-up resistor | . | Minimální vysílání (sekundy) | Minimum time between alert broadcasts | . | Vysílání stavu (v sekundách) | Periodic state broadcast interval | . | Poslat zvonek s výstražnou zprávou | Include bell character in alerts | . | Přezdívka | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Nastavení | Popis | . | Paxcounter povolen | Activate people counting | . | Interval aktualizace (v sekundách) | How often to report counts | . | Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ", + "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Nastavení | Popis | . | MQTT povoleno | Toggle MQTT bridge | . | Adresa | MQTT broker address | . | Uživatelské jméno | Authentication username | . | Heslo | Authentication password | . | Šifrování povoleno | Encrypt MQTT payloads | . | JSON výstup povolen | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS povoleno | Use secure connection | . | Kořenové téma | Base MQTT topic path | . | Proxy na klienta povoleno | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy na tomto telefonu | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Hlášení mapy | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Nastavení | Popis | . | Souhlasím. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Nastavení | Popis | . | Sériová komunikace povolena | Activate serial communication | . | Povolit echo | Echo received serial data back | . | Sériový režim | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Rychlost sériového přenosu | Port speed | . | Vypršel čas spojení | How long to wait before considering an incoming message complete | . | Přepsat sériový port komunikace | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Nastavení | Popis | . | Externí oznámení povoleno | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Výstupní LED (GPIO) | Pin the LED is wired to | . | Výstupní LED aktivní při HIGH | Whether the LED pin is active high or low | . | Výstupní pin bzučáku (GPIO) | Pin the buzzer is wired to | . | Výstupní pin vybračního motorku (GPIO) | Pin the vibration motor is wired to | . | Použít PWM bzučák | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Použít I2S jako bzučák | Send the alert through an I2S audio output instead | . | GPIO Output Duration | How long a single alert lasts | . | Nag Timeout | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Vyzváněcí tón | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Nastavení | Popis | . | Uložit a přeposlat povoleno | Activate store and forward | . | Pulzující LED | Periodically announce this node’s store-and-forward capability | . | Počet záznamů | Maximum stored messages | . | Max. počet záznamů historie | Max messages to replay | . | Časové okno historie | Time window for replay | . | Server | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Nastavení | Popis | . | Test pokrytí povolen | Activate range testing | . | Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Uložit .CSV do úložiště (pouze ESP32) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Nastavení | Popis | . | Odesílat telemetrii zařízení | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Interval aktualizace metrik zařízení | How often to report battery, uptime and channel utilization | . | Modul měření životního prostředí povolen | Report the attached environment sensors | . | Interval aktualizace měření životního prostředí | How often to report them | . | Zobrazení měření životního prostředí povoleno | Also show these readings on the device’s own display | . | Měření životního prostředí používá Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Modul měření kvality ovzduší povolen | Report particulate and CO₂ sensor data | . | Interval aktualizace měření kvality ovzduší | How often to report them | . | Modul měření spotřeby povolen | Report the per-channel voltage and current readings | . | Interval aktualizace měření napájení | How often to report them | . | Měření spotřeby na obrazovce povoleno | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Nastavení | Popis | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Zprávy | Newline-separated list of messages | . | Odeslat zvonek | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Rotační enkodér #1 povolen | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Vstup Nahoru/Dolů/Výběr povolen | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Nastavení | Popis | . | CODEC 2 enabled | Activate audio module | . | CODEC2 sample rate | Audio quality/bandwidth tradeoff | . | PTT pin | GPIO pin for the push-to-talk button | . | I2S výběr slov | GPIO pin for I2S WS | . | I2S vstupní data | GPIO pin for I2S DIN | . | I2S výstupní data | GPIO pin for I2S DOUT | . | I2S clock | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Nastavení | Popis | . | Vzdálený modul povolen | Activate remote GPIO access | . | Povolit přiřazení nedefinovaného pinu | Allow access to any GPIO pin (security risk) | . | Dostupné piny | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Nastavení | Popis | . | Informace o sousedech povoleny | Activate neighbor broadcasting | . | Interval aktualizace GPS | How often to broadcast neighbor list | . | Přenos přes LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Nastavení | Popis | . | Stav LED | Turn the LED on or off | . | Proud | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Nastavení | Popis | . | Detekční senzor povolen | Activate detection sensor | . | GPIO pin ke sledování | GPIO pin connected to sensor | . | Typ spouštění detekce | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Použít INPUT_PULLUP režim | Enable the pin’s internal pull-up resistor | . | Minimum time between detection broadcasts | Minimum time between alert broadcasts | . | State Broadcast Interval | Periodic state broadcast interval | . | Poslat zvonek s výstražnou zprávou | Include bell character in alerts | . | Přezdívka | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Nastavení | Popis | . | Paxcounter povolen | Activate people counting | . | Interval aktualizace GPS | How often to report counts | . | WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ", "url": "/Meshtastic-Android/main/cs-rCZ/user/settings-module-admin.html#nastaven%C3%AD-modul%C5%AF", "relUrl": "/cs-rCZ/user/settings-module-admin.html#nastavení-modulů" @@ -29982,7 +29982,7 @@ },"4283": { "doc": "Settings — Modules & Admin", "title": "Конфигуриране на модулите", - "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Настройка | Описание | . | MQTT е активиран | Toggle MQTT bridge | . | Адрес | MQTT broker address | . | Потребителско име | Authentication username | . | Парола | Authentication password | . | Криптирането е активирано | Encrypt MQTT payloads | . | JSON output enabled | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS е активиран | Use secure connection | . | Root topic | Base MQTT topic path | . | Прокси към клиент е активиран | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT прокси на този телефон | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Map reporting | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Настройка | Описание | . | Съгласен съм. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Map reporting interval (seconds) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Настройка | Описание | . | Серийната връзка е активирана | Activate serial communication | . | Echo е активирано | Echo received serial data back | . | Сериен режим | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Серийна скорост на предаване | Port speed | . | Timeout | How long to wait before considering an incoming message complete | . | Override console serial port | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Настройка | Описание | . | Външните известия са активирани | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Output LED (GPIO) | Pin the LED is wired to | . | Output LED active high | Whether the LED pin is active high or low | . | Output buzzer (GPIO) | Pin the buzzer is wired to | . | Output vibra (GPIO) | Pin the vibration motor is wired to | . | Използване на PWM зумер | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Use I2S as buzzer | Send the alert through an I2S audio output instead | . | Output duration (milliseconds) | How long a single alert lasts | . | Nag timeout (seconds) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Тон на звънене | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Настройка | Описание | . | Съхраняване & препращане е активиран | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | Брой записи | Maximum stored messages | . | History return max | Max messages to replay | . | History return window | Time window for replay | . | Сървър | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Настройка | Описание | . | Тест на обхвата е активиран | Activate range testing | . | Sender message interval (seconds) | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Запазване на .CSV в хранилище (само за ESP32) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Настройка | Описание | . | Изпращане на телеметрия на устройството | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Интервал на актуализиране на показателите на устройството | How often to report battery, uptime and channel utilization | . | Модулът за измерване на околната среда е активиран | Report the attached environment sensors | . | Интервал на актуализиране на показателите за средата | How often to report them | . | Показателите на околната среда на екрана са активирани | Also show these readings on the device’s own display | . | Показателите на околната среда използват Фаренхайт | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Модулът за показатели за качеството на въздуха е активиран | Report particulate and CO₂ sensor data | . | Интервал на актуализиране на показателите за качеството на въздуха | How often to report them | . | Power metrics module enabled | Report the per-channel voltage and current readings | . | Power metrics update interval | How often to report them | . | Power metrics on-screen enabled | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Настройка | Описание | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Съобщения | Newline-separated list of messages | . | Send bell | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Ротационен енкодер #1 е активиран | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Up/Down/Select input enabled | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Настройка | Описание | . | CODEC 2 е активиран | Activate audio module | . | CODEC2 sample rate | Audio quality/bandwidth tradeoff | . | Пин за РТТ | GPIO pin for the push-to-talk button | . | I2S word select | GPIO pin for I2S WS | . | I2S data in | GPIO pin for I2S DIN | . | I2S data out | GPIO pin for I2S DOUT | . | I2S clock | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Настройка | Описание | . | Отдалечен хардуер е активиран | Activate remote GPIO access | . | Allow undefined pin access | Allow access to any GPIO pin (security risk) | . | Налични пинове | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Настройка | Описание | . | Neighbor Info enabled | Activate neighbor broadcasting | . | Интервал на актуализиране (секунди) | How often to broadcast neighbor list | . | Предаване през LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Настройка | Описание | . | LED за състояние | Turn the LED on or off | . | Текущ | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Настройка | Описание | . | Detection Sensor enabled | Activate detection sensor | . | GPIO pin to monitor | GPIO pin connected to sensor | . | Detection trigger type | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Използване на режим INPUT_PULLUP | Enable the pin’s internal pull-up resistor | . | Minimum broadcast (seconds) | Minimum time between alert broadcasts | . | State broadcast (seconds) | Periodic state broadcast interval | . | Send bell with alert message | Include bell character in alerts | . | Приятелско име | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Настройка | Описание | . | Paxcounter е активиран | Activate people counting | . | Интервал на актуализиране (секунди) | How often to report counts | . | Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ", + "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Настройка | Описание | . | MQTT е активиран | Toggle MQTT bridge | . | Адрес | MQTT broker address | . | Потребителско име | Authentication username | . | Парола | Authentication password | . | Криптирането е активирано | Encrypt MQTT payloads | . | JSON output enabled | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS е активиран | Use secure connection | . | Root topic | Base MQTT topic path | . | Прокси към клиент е активиран | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT прокси на този телефон | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Map reporting | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Настройка | Описание | . | Съгласен съм. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Настройка | Описание | . | Серийната връзка е активирана | Activate serial communication | . | Echo е активирано | Echo received serial data back | . | Сериен режим | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Серийна скорост на предаване | Port speed | . | Timeout | How long to wait before considering an incoming message complete | . | Override console serial port | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Настройка | Описание | . | Външните известия са активирани | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Output LED (GPIO) | Pin the LED is wired to | . | Output LED active high | Whether the LED pin is active high or low | . | Output buzzer (GPIO) | Pin the buzzer is wired to | . | Output vibra (GPIO) | Pin the vibration motor is wired to | . | Използване на PWM зумер | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Use I2S as buzzer | Send the alert through an I2S audio output instead | . | GPIO Output Duration | How long a single alert lasts | . | Nag Timeout | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Тон на звънене | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Настройка | Описание | . | Съхраняване & препращане е активиран | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | Брой записи | Maximum stored messages | . | History return max | Max messages to replay | . | History return window | Time window for replay | . | Сървър | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Настройка | Описание | . | Тест на обхвата е активиран | Activate range testing | . | Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Запазване на .CSV в хранилище (само за ESP32) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Настройка | Описание | . | Изпращане на телеметрия на устройството | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Интервал на актуализиране на показателите на устройството | How often to report battery, uptime and channel utilization | . | Модулът за измерване на околната среда е активиран | Report the attached environment sensors | . | Интервал на актуализиране на показателите за средата | How often to report them | . | Показателите на околната среда на екрана са активирани | Also show these readings on the device’s own display | . | Показателите на околната среда използват Фаренхайт | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Модулът за показатели за качеството на въздуха е активиран | Report particulate and CO₂ sensor data | . | Интервал на актуализиране на показателите за качеството на въздуха | How often to report them | . | Power metrics module enabled | Report the per-channel voltage and current readings | . | Power metrics update interval | How often to report them | . | Power metrics on-screen enabled | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Настройка | Описание | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Съобщения | Newline-separated list of messages | . | Send bell | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Ротационен енкодер #1 е активиран | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Up/Down/Select input enabled | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Настройка | Описание | . | CODEC 2 е активиран | Activate audio module | . | CODEC2 sample rate | Audio quality/bandwidth tradeoff | . | Пин за РТТ | GPIO pin for the push-to-talk button | . | I2S word select | GPIO pin for I2S WS | . | I2S data in | GPIO pin for I2S DIN | . | I2S data out | GPIO pin for I2S DOUT | . | I2S clock | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Настройка | Описание | . | Отдалечен хардуер е активиран | Activate remote GPIO access | . | Allow undefined pin access | Allow access to any GPIO pin (security risk) | . | Налични пинове | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Настройка | Описание | . | Neighbor Info enabled | Activate neighbor broadcasting | . | Интервал на актуализиране | How often to broadcast neighbor list | . | Предаване през LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Настройка | Описание | . | LED за състояние | Turn the LED on or off | . | Текущ | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Настройка | Описание | . | Detection Sensor enabled | Activate detection sensor | . | GPIO pin to monitor | GPIO pin connected to sensor | . | Detection trigger type | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Използване на режим INPUT_PULLUP | Enable the pin’s internal pull-up resistor | . | Minimum time between detection broadcasts | Minimum time between alert broadcasts | . | State Broadcast Interval | Periodic state broadcast interval | . | Send bell with alert message | Include bell character in alerts | . | Приятелско име | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Настройка | Описание | . | Paxcounter е активиран | Activate people counting | . | Интервал на актуализиране | How often to report counts | . | WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ", "url": "/Meshtastic-Android/main/bg-rBG/user/settings-module-admin.html#%D0%BA%D0%BE%D0%BD%D1%84%D0%B8%D0%B3%D1%83%D1%80%D0%B8%D1%80%D0%B0%D0%BD%D0%B5-%D0%BD%D0%B0-%D0%BC%D0%BE%D0%B4%D1%83%D0%BB%D0%B8%D1%82%D0%B5", "relUrl": "/bg-rBG/user/settings-module-admin.html#конфигуриране-на-модулите" @@ -30017,7 +30017,7 @@ },"4288": { "doc": "Settings — Modules & Admin", "title": "Cumraíocht an mhódule", - "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Cur síos | . | MQTT enabled | Toggle MQTT bridge | . | Address | MQTT broker address | . | Username | Authentication username | . | Password | Authentication password | . | Encryption enabled | Encrypt MQTT payloads | . | JSON output enabled | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS enabled | Use secure connection | . | Root topic | Base MQTT topic path | . | Proxy to client enabled | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Map reporting | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Cur síos | . | I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Map reporting interval (seconds) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Cur síos | . | Serial enabled | Activate serial communication | . | Echo enabled | Echo received serial data back | . | Serial mode | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Serial baud rate | Port speed | . | Am tráth | How long to wait before considering an incoming message complete | . | Override console serial port | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Cur síos | . | External notification enabled | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Output LED (GPIO) | Pin the LED is wired to | . | Output LED active high | Whether the LED pin is active high or low | . | Output buzzer (GPIO) | Pin the buzzer is wired to | . | Output vibra (GPIO) | Pin the vibration motor is wired to | . | Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Use I2S as buzzer | Send the alert through an I2S audio output instead | . | Output duration (milliseconds) | How long a single alert lasts | . | Nag timeout (seconds) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Cur síos | . | Store & Forward enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | Number of records | Maximum stored messages | . | History return max | Max messages to replay | . | History return window | Time window for replay | . | Server | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Cur síos | . | Range test enabled | Activate range testing | . | Sender message interval (seconds) | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Save .CSV in storage (ESP32 only) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Cur síos | . | Send Device Telemetry | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Device metrics update interval | How often to report battery, uptime and channel utilization | . | Environment metrics module enabled | Report the attached environment sensors | . | Environment metrics update interval | How often to report them | . | Environment metrics on-screen enabled | Also show these readings on the device’s own display | . | Environment metrics use Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Air quality metrics module enabled | Report particulate and CO₂ sensor data | . | Air quality metrics update interval | How often to report them | . | Power metrics module enabled | Report the per-channel voltage and current readings | . | Power metrics update interval | How often to report them | . | Power metrics on-screen enabled | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Cur síos | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Messages | Newline-separated list of messages | . | Send bell | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Rotary encoder #1 enabled | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Up/Down/Select input enabled | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Cur síos | . | CODEC 2 enabled | Activate audio module | . | CODEC2 sample rate | Audio quality/bandwidth tradeoff | . | PTT pin | GPIO pin for the push-to-talk button | . | I2S word select | GPIO pin for I2S WS | . | I2S data in | GPIO pin for I2S DIN | . | I2S data out | GPIO pin for I2S DOUT | . | I2S clock | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Cur síos | . | Remote Hardware enabled | Activate remote GPIO access | . | Allow undefined pin access | Allow access to any GPIO pin (security risk) | . | Available pins | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Cur síos | . | Neighbor Info enabled | Activate neighbor broadcasting | . | Update interval (seconds) | How often to broadcast neighbor list | . | Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Cur síos | . | LED state | Turn the LED on or off | . | Current | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Cur síos | . | Detection Sensor enabled | Activate detection sensor | . | GPIO pin to monitor | GPIO pin connected to sensor | . | Detection trigger type | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Use INPUT_PULLUP mode | Enable the pin’s internal pull-up resistor | . | Minimum broadcast (seconds) | Minimum time between alert broadcasts | . | State broadcast (seconds) | Periodic state broadcast interval | . | Send bell with alert message | Include bell character in alerts | . | Friendly name | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Cur síos | . | Paxcounter enabled | Activate people counting | . | Update interval (seconds) | How often to report counts | . | Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ", + "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Cur síos | . | MQTT enabled | Toggle MQTT bridge | . | Address | MQTT broker address | . | Username | Authentication username | . | Password | Authentication password | . | Encryption enabled | Encrypt MQTT payloads | . | JSON output enabled | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS enabled | Use secure connection | . | Root topic | Base MQTT topic path | . | Proxy to client enabled | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Map reporting | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Cur síos | . | I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Cur síos | . | Serial enabled | Activate serial communication | . | Echo enabled | Echo received serial data back | . | Serial mode | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Serial baud rate | Port speed | . | Am tráth | How long to wait before considering an incoming message complete | . | Override console serial port | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Cur síos | . | External notification enabled | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Output LED (GPIO) | Pin the LED is wired to | . | Output LED active high | Whether the LED pin is active high or low | . | Output buzzer (GPIO) | Pin the buzzer is wired to | . | Output vibra (GPIO) | Pin the vibration motor is wired to | . | Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Use I2S as buzzer | Send the alert through an I2S audio output instead | . | GPIO Output Duration | How long a single alert lasts | . | Nag Timeout | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Cur síos | . | Store & Forward enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | Number of records | Maximum stored messages | . | History return max | Max messages to replay | . | History return window | Time window for replay | . | Server | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Cur síos | . | Range test enabled | Activate range testing | . | Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Save .CSV in storage (ESP32 only) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Cur síos | . | Send Device Telemetry | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Device metrics update interval | How often to report battery, uptime and channel utilization | . | Environment metrics module enabled | Report the attached environment sensors | . | Environment metrics update interval | How often to report them | . | Environment metrics on-screen enabled | Also show these readings on the device’s own display | . | Environment metrics use Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Air quality metrics module enabled | Report particulate and CO₂ sensor data | . | Air quality metrics update interval | How often to report them | . | Power metrics module enabled | Report the per-channel voltage and current readings | . | Power metrics update interval | How often to report them | . | Power metrics on-screen enabled | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Cur síos | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Messages | Newline-separated list of messages | . | Send bell | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Rotary encoder #1 enabled | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Up/Down/Select input enabled | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Cur síos | . | CODEC 2 enabled | Activate audio module | . | CODEC2 sample rate | Audio quality/bandwidth tradeoff | . | PTT pin | GPIO pin for the push-to-talk button | . | I2S word select | GPIO pin for I2S WS | . | I2S data in | GPIO pin for I2S DIN | . | I2S data out | GPIO pin for I2S DOUT | . | I2S clock | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Cur síos | . | Remote Hardware enabled | Activate remote GPIO access | . | Allow undefined pin access | Allow access to any GPIO pin (security risk) | . | Available pins | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Cur síos | . | Neighbor Info enabled | Activate neighbor broadcasting | . | Update Interval | How often to broadcast neighbor list | . | Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Cur síos | . | LED state | Turn the LED on or off | . | Current | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Cur síos | . | Detection Sensor enabled | Activate detection sensor | . | GPIO pin to monitor | GPIO pin connected to sensor | . | Detection trigger type | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Use INPUT_PULLUP mode | Enable the pin’s internal pull-up resistor | . | Minimum time between detection broadcasts | Minimum time between alert broadcasts | . | State Broadcast Interval | Periodic state broadcast interval | . | Send bell with alert message | Include bell character in alerts | . | Friendly name | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Cur síos | . | Paxcounter enabled | Activate people counting | . | Update Interval | How often to report counts | . | WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ", "url": "/Meshtastic-Android/main/ga-rIE/user/settings-module-admin.html#cumra%C3%ADocht-an-mh%C3%B3dule", "relUrl": "/ga-rIE/user/settings-module-admin.html#cumraíocht-an-mhódule" @@ -30052,7 +30052,7 @@ },"4293": { "doc": "Settings — Modules & Admin", "title": "Réglages du module", - "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Description | . | MQTT activé | Toggle MQTT bridge | . | Adresse | MQTT broker address | . | Nom d’utilisateur | Authentication username | . | Mot de passe | Authentication password | . | Chiffrement activé | Encrypt MQTT payloads | . | Sortie JSON activée | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS activé | Use secure connection | . | Sujet principal | Base MQTT topic path | . | Proxy pour le client activé | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Rapport cartographique | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Description | . | J’accepte. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Intervalle de rapport cartographique (secondes) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Description | . | Série activée | Activate serial communication | . | Écho activé | Echo received serial data back | . | Mode série | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Vitesse de transmission série | Port speed | . | Délai d’expiration | How long to wait before considering an incoming message complete | . | Outrepasser le port série de la console | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Description | . | Notifications externes activées | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | LED extérieure (GPIO) | Pin the LED is wired to | . | Sortie LED active à l’état haut | Whether the LED pin is active high or low | . | Buzzer extérieur (GPIO) | Pin the buzzer is wired to | . | Sortie vibreur (GPIO) | Pin the vibration motor is wired to | . | Utiliser le buzzer PWM | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Utiliser l’I2S comme buzzer | Send the alert through an I2S audio output instead | . | Durée de sortie (en millisecondes) | How long a single alert lasts | . | Durée de répétition de la sortie (secondes) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Sonnerie | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Description | . | Stocker & Transférer activé | Activate store and forward | . | Battement de cœur (heartbeat) | Periodically announce this node’s store-and-forward capability | . | Nombre d’enregistrements | Maximum stored messages | . | Limite d’historique renvoyé | Max messages to replay | . | Fenêtre de retour d’historique | Time window for replay | . | Serveur | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Description | . | Test de portée activé | Activate range testing | . | Intervalle de message de l’expéditeur (secondes) | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Enregistrer .CSV dans le stockage (ESP32 seulement) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Description | . | Envoyer la télémétrie de l’appareil | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Intervalle de mise à jour des mesures | How often to report battery, uptime and channel utilization | . | Module de métriques de l’environnement activé | Report the attached environment sensors | . | Intervalle de mise à jour des mesures d’environnement | How often to report them | . | Mesures d’environnement à l’écran activées | Also show these readings on the device’s own display | . | Les mesures environnementales utilisent Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Module de mesure de la qualité de l’air activé | Report particulate and CO₂ sensor data | . | Intervalle de mise à jour des mesures de qualité d’air | How often to report them | . | Module de mesure de puissance activé | Report the per-channel voltage and current readings | . | Intervalle de mise à jour des mesures d’alimentation | How often to report them | . | Indicateurs d’alimentation à l’écran activés | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Description | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Messages | Newline-separated list of messages | . | Envoyer une sonnerie | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Encodeur rotatif #1 activé | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Entrée Haut/Bas/Select activée | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Description | . | CODEC 2 activé | Activate audio module | . | Taux d’échantillonnage CODEC2 | Audio quality/bandwidth tradeoff | . | Broche PTT | GPIO pin for the push-to-talk button | . | Selection de mot I2S | GPIO pin for I2S WS | . | Données d’entrée I2S | GPIO pin for I2S DIN | . | Données de sortie I2S | GPIO pin for I2S DOUT | . | Horloge I2C | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Description | . | Matériel distant activé | Activate remote GPIO access | . | Autoriser l’accès non défini aux broches | Allow access to any GPIO pin (security risk) | . | Broches disponibles | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Description | . | Infos de voisinage activées | Activate neighbor broadcasting | . | Intervalle de mise à jour (secondes) | How often to broadcast neighbor list | . | Transmettre par LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Description | . | État de la LED | Turn the LED on or off | . | Actif | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Description | . | Capteur de détection activé | Activate detection sensor | . | Broche GPIO à surveiller | GPIO pin connected to sensor | . | Type du déclencheur de détection | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Utiliser le mode INPUT_PULLUP | Enable the pin’s internal pull-up resistor | . | Diffusion minimale (secondes) | Minimum time between alert broadcasts | . | Diffusion de l’État (secondes) | Periodic state broadcast interval | . | Envoyer une sonnerie avec un message d’alerte | Include bell character in alerts | . | Nom convivial | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Paramètre | Description | . | Paxcounter activé | Activate people counting | . | Intervalle de mise à jour (secondes) | How often to report counts | . | Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ", + "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Description | . | MQTT activé | Toggle MQTT bridge | . | Adresse | MQTT broker address | . | Nom d’utilisateur | Authentication username | . | Mot de passe | Authentication password | . | Chiffrement activé | Encrypt MQTT payloads | . | Sortie JSON activée | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS activé | Use secure connection | . | Sujet principal | Base MQTT topic path | . | Proxy pour le client activé | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Rapport cartographique | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Description | . | J’accepte. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Description | . | Série activée | Activate serial communication | . | Écho activé | Echo received serial data back | . | Mode série | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Vitesse de transmission série | Port speed | . | Délai d’expiration | How long to wait before considering an incoming message complete | . | Outrepasser le port série de la console | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Description | . | Notifications externes activées | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | LED extérieure (GPIO) | Pin the LED is wired to | . | Sortie LED active à l’état haut | Whether the LED pin is active high or low | . | Buzzer extérieur (GPIO) | Pin the buzzer is wired to | . | Sortie vibreur (GPIO) | Pin the vibration motor is wired to | . | Utiliser le buzzer PWM | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Utiliser l’I2S comme buzzer | Send the alert through an I2S audio output instead | . | GPIO Output Duration | How long a single alert lasts | . | Délai d’expiration du message | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Sonnerie | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Description | . | Stocker & Transférer activé | Activate store and forward | . | Battement de cœur (heartbeat) | Periodically announce this node’s store-and-forward capability | . | Nombre d’enregistrements | Maximum stored messages | . | Limite d’historique renvoyé | Max messages to replay | . | Fenêtre de retour d’historique | Time window for replay | . | Serveur | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Description | . | Test de portée activé | Activate range testing | . | Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Enregistrer .CSV dans le stockage (ESP32 seulement) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Description | . | Envoyer la télémétrie de l’appareil | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Intervalle de mise à jour des mesures | How often to report battery, uptime and channel utilization | . | Module de métriques de l’environnement activé | Report the attached environment sensors | . | Intervalle de mise à jour des mesures d’environnement | How often to report them | . | Mesures d’environnement à l’écran activées | Also show these readings on the device’s own display | . | Les mesures environnementales utilisent Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Module de mesure de la qualité de l’air activé | Report particulate and CO₂ sensor data | . | Intervalle de mise à jour des mesures de qualité d’air | How often to report them | . | Module de mesure de puissance activé | Report the per-channel voltage and current readings | . | Intervalle de mise à jour des mesures d’alimentation | How often to report them | . | Indicateurs d’alimentation à l’écran activés | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Description | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Messages | Newline-separated list of messages | . | Envoyer une sonnerie | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Encodeur rotatif #1 activé | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Entrée Haut/Bas/Select activée | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Description | . | CODEC 2 activé | Activate audio module | . | Taux d’échantillonnage CODEC2 | Audio quality/bandwidth tradeoff | . | Broche PTT | GPIO pin for the push-to-talk button | . | Selection de mot I2S | GPIO pin for I2S WS | . | Données d’entrée I2S | GPIO pin for I2S DIN | . | Données de sortie I2S | GPIO pin for I2S DOUT | . | Horloge I2C | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Description | . | Matériel distant activé | Activate remote GPIO access | . | Autoriser l’accès non défini aux broches | Allow access to any GPIO pin (security risk) | . | Broches disponibles | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Description | . | Infos de voisinage activées | Activate neighbor broadcasting | . | Fréquence de récupération GPS | How often to broadcast neighbor list | . | Transmettre par LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Description | . | État de la LED | Turn the LED on or off | . | Actif | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Description | . | Capteur de détection activé | Activate detection sensor | . | Broche GPIO à surveiller | GPIO pin connected to sensor | . | Type du déclencheur de détection | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Utiliser le mode INPUT_PULLUP | Enable the pin’s internal pull-up resistor | . | Minimum time between detection broadcasts | Minimum time between alert broadcasts | . | State Broadcast Interval | Periodic state broadcast interval | . | Envoyer une sonnerie avec un message d’alerte | Include bell character in alerts | . | Nom convivial | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Paramètre | Description | . | Paxcounter activé | Activate people counting | . | Fréquence de récupération GPS | How often to report counts | . | WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ", "url": "/Meshtastic-Android/main/fr-rCA/user/settings-module-admin.html#r%C3%A9glages-du-module", "relUrl": "/fr-rCA/user/settings-module-admin.html#réglages-du-module" @@ -30087,7 +30087,7 @@ },"4298": { "doc": "Settings — Modules & Admin", "title": "Конфигурација модула", - "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Опис | . | MQTT enabled | Toggle MQTT bridge | . | Адреса | MQTT broker address | . | Корисничко име | Authentication username | . | Лозинка | Authentication password | . | Encryption enabled | Encrypt MQTT payloads | . | JSON output enabled | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS enabled | Use secure connection | . | Root topic | Base MQTT topic path | . | Proxy to client enabled | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Map reporting | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Опис | . | I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Map reporting interval (seconds) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Опис | . | Serial enabled | Activate serial communication | . | Echo enabled | Echo received serial data back | . | Serial mode | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Serial baud rate | Port speed | . | Временско ограничење | How long to wait before considering an incoming message complete | . | Override console serial port | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Опис | . | External notification enabled | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Output LED (GPIO) | Pin the LED is wired to | . | Output LED active high | Whether the LED pin is active high or low | . | Output buzzer (GPIO) | Pin the buzzer is wired to | . | Output vibra (GPIO) | Pin the vibration motor is wired to | . | Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Use I2S as buzzer | Send the alert through an I2S audio output instead | . | Output duration (milliseconds) | How long a single alert lasts | . | Nag timeout (seconds) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Мелодија звона | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Опис | . | Store & Forward enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | Број записа | Maximum stored messages | . | History return max | Max messages to replay | . | History return window | Time window for replay | . | Сервер | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Опис | . | Range test enabled | Activate range testing | . | Sender message interval (seconds) | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Save .CSV in storage (ESP32 only) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Опис | . | Send Device Telemetry | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Device metrics update interval | How often to report battery, uptime and channel utilization | . | Environment metrics module enabled | Report the attached environment sensors | . | Environment metrics update interval | How often to report them | . | Environment metrics on-screen enabled | Also show these readings on the device’s own display | . | Environment metrics use Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Air quality metrics module enabled | Report particulate and CO₂ sensor data | . | Air quality metrics update interval | How often to report them | . | Power metrics module enabled | Report the per-channel voltage and current readings | . | Power metrics update interval | How often to report them | . | Power metrics on-screen enabled | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Опис | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Поруке | Newline-separated list of messages | . | Send bell | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Rotary encoder #1 enabled | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Up/Down/Select input enabled | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Опис | . | CODEC 2 enabled | Activate audio module | . | CODEC2 sample rate | Audio quality/bandwidth tradeoff | . | PTT pin | GPIO pin for the push-to-talk button | . | I2S word select | GPIO pin for I2S WS | . | I2S data in | GPIO pin for I2S DIN | . | I2S data out | GPIO pin for I2S DOUT | . | I2S clock | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Опис | . | Remote Hardware enabled | Activate remote GPIO access | . | Allow undefined pin access | Allow access to any GPIO pin (security risk) | . | Available pins | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Опис | . | Neighbor Info enabled | Activate neighbor broadcasting | . | Update interval (seconds) | How often to broadcast neighbor list | . | Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Опис | . | LED state | Turn the LED on or off | . | Струја | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Опис | . | Detection Sensor enabled | Activate detection sensor | . | GPIO pin to monitor | GPIO pin connected to sensor | . | Detection trigger type | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Use INPUT_PULLUP mode | Enable the pin’s internal pull-up resistor | . | Minimum broadcast (seconds) | Minimum time between alert broadcasts | . | State broadcast (seconds) | Periodic state broadcast interval | . | Send bell with alert message | Include bell character in alerts | . | Пријатељски назив | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Опис | . | Paxcounter enabled | Activate people counting | . | Update interval (seconds) | How often to report counts | . | Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ", + "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Опис | . | MQTT enabled | Toggle MQTT bridge | . | Адреса | MQTT broker address | . | Корисничко име | Authentication username | . | Лозинка | Authentication password | . | Encryption enabled | Encrypt MQTT payloads | . | JSON output enabled | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS enabled | Use secure connection | . | Root topic | Base MQTT topic path | . | Proxy to client enabled | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Map reporting | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Опис | . | I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Интервал објављивања мапе | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Опис | . | Serial enabled | Activate serial communication | . | Echo enabled | Echo received serial data back | . | Serial mode | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Serial baud rate | Port speed | . | Временско ограничење | How long to wait before considering an incoming message complete | . | Override console serial port | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Опис | . | External notification enabled | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Output LED (GPIO) | Pin the LED is wired to | . | Output LED active high | Whether the LED pin is active high or low | . | Output buzzer (GPIO) | Pin the buzzer is wired to | . | Output vibra (GPIO) | Pin the vibration motor is wired to | . | Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Use I2S as buzzer | Send the alert through an I2S audio output instead | . | Трајање GPIO излаза | How long a single alert lasts | . | Nag Timeout | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Мелодија звона | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Опис | . | Store & Forward enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | Број записа | Maximum stored messages | . | History return max | Max messages to replay | . | History return window | Time window for replay | . | Сервер | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Опис | . | Range test enabled | Activate range testing | . | Инерварл пошиљаоца | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Save .CSV in storage (ESP32 only) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Опис | . | Send Device Telemetry | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Device metrics update interval | How often to report battery, uptime and channel utilization | . | Environment metrics module enabled | Report the attached environment sensors | . | Environment metrics update interval | How often to report them | . | Environment metrics on-screen enabled | Also show these readings on the device’s own display | . | Environment metrics use Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Air quality metrics module enabled | Report particulate and CO₂ sensor data | . | Air quality metrics update interval | How often to report them | . | Power metrics module enabled | Report the per-channel voltage and current readings | . | Power metrics update interval | How often to report them | . | Power metrics on-screen enabled | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Опис | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Поруке | Newline-separated list of messages | . | Send bell | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Rotary encoder #1 enabled | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Up/Down/Select input enabled | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Опис | . | CODEC 2 enabled | Activate audio module | . | CODEC2 sample rate | Audio quality/bandwidth tradeoff | . | PTT pin | GPIO pin for the push-to-talk button | . | I2S word select | GPIO pin for I2S WS | . | I2S data in | GPIO pin for I2S DIN | . | I2S data out | GPIO pin for I2S DOUT | . | I2S clock | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Опис | . | Remote Hardware enabled | Activate remote GPIO access | . | Allow undefined pin access | Allow access to any GPIO pin (security risk) | . | Available pins | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Опис | . | Neighbor Info enabled | Activate neighbor broadcasting | . | Интервал ажурирања | How often to broadcast neighbor list | . | Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Опис | . | LED state | Turn the LED on or off | . | Струја | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Опис | . | Detection Sensor enabled | Activate detection sensor | . | GPIO pin to monitor | GPIO pin connected to sensor | . | Detection trigger type | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Use INPUT_PULLUP mode | Enable the pin’s internal pull-up resistor | . | Минимално време између емитовања детекције | Minimum time between alert broadcasts | . | Интервал емитовања стања | Periodic state broadcast interval | . | Send bell with alert message | Include bell character in alerts | . | Пријатељски назив | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Опис | . | Paxcounter enabled | Activate people counting | . | Интервал ажурирања | How often to report counts | . | WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ", "url": "/Meshtastic-Android/main/srp/user/settings-module-admin.html#%D0%BA%D0%BE%D0%BD%D1%84%D0%B8%D0%B3%D1%83%D1%80%D0%B0%D1%86%D0%B8%D1%98%D0%B0-%D0%BC%D0%BE%D0%B4%D1%83%D0%BB%D0%B0", "relUrl": "/srp/user/settings-module-admin.html#конфигурација-модула" @@ -30122,7 +30122,7 @@ },"4303": { "doc": "Settings — Modules & Admin", "title": "Configuració de mòdul", - "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Descripció | . | MQTT enabled | Toggle MQTT bridge | . | Address | MQTT broker address | . | Username | Authentication username | . | Password | Authentication password | . | Encryption enabled | Encrypt MQTT payloads | . | JSON output enabled | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS enabled | Use secure connection | . | Root topic | Base MQTT topic path | . | Proxy to client enabled | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Map reporting | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Descripció | . | I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Map reporting interval (seconds) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Descripció | . | Serial enabled | Activate serial communication | . | Echo enabled | Echo received serial data back | . | Serial mode | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Serial baud rate | Port speed | . | Temps esgotat | How long to wait before considering an incoming message complete | . | Override console serial port | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Descripció | . | External notification enabled | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Output LED (GPIO) | Pin the LED is wired to | . | Output LED active high | Whether the LED pin is active high or low | . | Output buzzer (GPIO) | Pin the buzzer is wired to | . | Output vibra (GPIO) | Pin the vibration motor is wired to | . | Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Use I2S as buzzer | Send the alert through an I2S audio output instead | . | Output duration (milliseconds) | How long a single alert lasts | . | Nag timeout (seconds) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Descripció | . | Store & Forward enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | Number of records | Maximum stored messages | . | History return max | Max messages to replay | . | History return window | Time window for replay | . | Server | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Descripció | . | Range test enabled | Activate range testing | . | Sender message interval (seconds) | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Save .CSV in storage (ESP32 only) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Descripció | . | Send Device Telemetry | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Device metrics update interval | How often to report battery, uptime and channel utilization | . | Environment metrics module enabled | Report the attached environment sensors | . | Environment metrics update interval | How often to report them | . | Environment metrics on-screen enabled | Also show these readings on the device’s own display | . | Environment metrics use Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Air quality metrics module enabled | Report particulate and CO₂ sensor data | . | Air quality metrics update interval | How often to report them | . | Power metrics module enabled | Report the per-channel voltage and current readings | . | Power metrics update interval | How often to report them | . | Power metrics on-screen enabled | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Descripció | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Messages | Newline-separated list of messages | . | Send bell | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Rotary encoder #1 enabled | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Up/Down/Select input enabled | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Descripció | . | CODEC 2 enabled | Activate audio module | . | CODEC2 sample rate | Audio quality/bandwidth tradeoff | . | PTT pin | GPIO pin for the push-to-talk button | . | I2S word select | GPIO pin for I2S WS | . | I2S data in | GPIO pin for I2S DIN | . | I2S data out | GPIO pin for I2S DOUT | . | I2S clock | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Descripció | . | Remote Hardware enabled | Activate remote GPIO access | . | Allow undefined pin access | Allow access to any GPIO pin (security risk) | . | Available pins | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Descripció | . | Neighbor Info enabled | Activate neighbor broadcasting | . | Update interval (seconds) | How often to broadcast neighbor list | . | Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Descripció | . | LED state | Turn the LED on or off | . | Current | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Descripció | . | Detection Sensor enabled | Activate detection sensor | . | GPIO pin to monitor | GPIO pin connected to sensor | . | Detection trigger type | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Use INPUT_PULLUP mode | Enable the pin’s internal pull-up resistor | . | Minimum broadcast (seconds) | Minimum time between alert broadcasts | . | State broadcast (seconds) | Periodic state broadcast interval | . | Send bell with alert message | Include bell character in alerts | . | Friendly name | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Descripció | . | Paxcounter enabled | Activate people counting | . | Update interval (seconds) | How often to report counts | . | Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ", + "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Descripció | . | MQTT enabled | Toggle MQTT bridge | . | Address | MQTT broker address | . | Username | Authentication username | . | Password | Authentication password | . | Encryption enabled | Encrypt MQTT payloads | . | JSON output enabled | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS enabled | Use secure connection | . | Root topic | Base MQTT topic path | . | Proxy to client enabled | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Map reporting | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Descripció | . | I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Descripció | . | Serial enabled | Activate serial communication | . | Echo enabled | Echo received serial data back | . | Serial mode | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Serial baud rate | Port speed | . | Temps esgotat | How long to wait before considering an incoming message complete | . | Override console serial port | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Descripció | . | External notification enabled | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Output LED (GPIO) | Pin the LED is wired to | . | Output LED active high | Whether the LED pin is active high or low | . | Output buzzer (GPIO) | Pin the buzzer is wired to | . | Output vibra (GPIO) | Pin the vibration motor is wired to | . | Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Use I2S as buzzer | Send the alert through an I2S audio output instead | . | GPIO Output Duration | How long a single alert lasts | . | Nag Timeout | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Descripció | . | Store & Forward enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | Number of records | Maximum stored messages | . | History return max | Max messages to replay | . | History return window | Time window for replay | . | Server | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Descripció | . | Range test enabled | Activate range testing | . | Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Save .CSV in storage (ESP32 only) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Descripció | . | Send Device Telemetry | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Device metrics update interval | How often to report battery, uptime and channel utilization | . | Environment metrics module enabled | Report the attached environment sensors | . | Environment metrics update interval | How often to report them | . | Environment metrics on-screen enabled | Also show these readings on the device’s own display | . | Environment metrics use Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Air quality metrics module enabled | Report particulate and CO₂ sensor data | . | Air quality metrics update interval | How often to report them | . | Power metrics module enabled | Report the per-channel voltage and current readings | . | Power metrics update interval | How often to report them | . | Power metrics on-screen enabled | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Descripció | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Messages | Newline-separated list of messages | . | Send bell | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Rotary encoder #1 enabled | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Up/Down/Select input enabled | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Descripció | . | CODEC 2 enabled | Activate audio module | . | CODEC2 sample rate | Audio quality/bandwidth tradeoff | . | PTT pin | GPIO pin for the push-to-talk button | . | I2S word select | GPIO pin for I2S WS | . | I2S data in | GPIO pin for I2S DIN | . | I2S data out | GPIO pin for I2S DOUT | . | I2S clock | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Descripció | . | Remote Hardware enabled | Activate remote GPIO access | . | Allow undefined pin access | Allow access to any GPIO pin (security risk) | . | Available pins | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Descripció | . | Neighbor Info enabled | Activate neighbor broadcasting | . | Update Interval | How often to broadcast neighbor list | . | Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Descripció | . | LED state | Turn the LED on or off | . | Current | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Descripció | . | Detection Sensor enabled | Activate detection sensor | . | GPIO pin to monitor | GPIO pin connected to sensor | . | Detection trigger type | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Use INPUT_PULLUP mode | Enable the pin’s internal pull-up resistor | . | Minimum time between detection broadcasts | Minimum time between alert broadcasts | . | State Broadcast Interval | Periodic state broadcast interval | . | Send bell with alert message | Include bell character in alerts | . | Friendly name | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Descripció | . | Paxcounter enabled | Activate people counting | . | Update Interval | How often to report counts | . | WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ", "url": "/Meshtastic-Android/main/ca-rES/user/settings-module-admin.html#configuraci%C3%B3-de-m%C3%B2dul", "relUrl": "/ca-rES/user/settings-module-admin.html#configuració-de-mòdul" @@ -30157,7 +30157,7 @@ },"4308": { "doc": "Settings — Modules & Admin", "title": "모듈 설정", - "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | 설명 | . | MQTT 활성화 | Toggle MQTT bridge | . | 서버 주소 | MQTT broker address | . | 사용자명 | Authentication username | . | 비밀번호 | Authentication password | . | 암호화 사용 | Encrypt MQTT payloads | . | JSON 사용 | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS 사용 | Use secure connection | . | Root topic | Base MQTT topic path | . | Proxy to client 사용 | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | 맵 보고 | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | 설명 | . | 동의합니다. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | 맵 보고 간격 (초) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | 설명 | . | 시리얼 활성화 | Activate serial communication | . | 에코 활성화 | Echo received serial data back | . | 시리얼 모드 | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | 시리얼 baud rate | Port speed | . | 시간 초과 | How long to wait before considering an incoming message complete | . | Override console serial port | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | 설명 | . | 외부 알림 활성화 | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | LED 출력 (GPIO) | Pin the LED is wired to | . | LED 출력 active high | Whether the LED pin is active high or low | . | 부저 출력 (GPIO) | Pin the buzzer is wired to | . | 진동 출력 (GPIO) | Pin the vibration motor is wired to | . | PWM 부저 사용 | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | I2S 부저 사용 | Send the alert through an I2S audio output instead | . | 출력 지속시간 (밀리초) | How long a single alert lasts | . | 반복 종료 시간 (초) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | 벨소리 | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | 설명 | . | 저장 및 전달 활성화 | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | Number of records | Maximum stored messages | . | History return max | Max messages to replay | . | History return window | Time window for replay | . | 서버 | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | 설명 | . | 거리 테스트 활성화 | Activate range testing | . | 송신 장치 메시지 간격 (초) | Time between test transmissions, chosen from a dropdown of fixed intervals | . | .CSV 파일 저장 (EPS32만 동작) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | 설명 | . | Send Device Telemetry | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Device metrics update interval | How often to report battery, uptime and channel utilization | . | 환경 메트릭 모듈 사용 | Report the attached environment sensors | . | Environment metrics update interval | How often to report them | . | 환경 메트릭 화면 사용 | Also show these readings on the device’s own display | . | 환경 메트릭에서 화씨 사용 | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | 대기질 메트릭 모듈 사용 | Report particulate and CO₂ sensor data | . | Air quality metrics update interval | How often to report them | . | 전력 메트릭 모듈 사용 | Report the per-channel voltage and current readings | . | Power metrics update interval | How often to report them | . | 전력 메트릭 화면 사용 | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | 설명 | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | 메시지기기 | Newline-separated list of messages | . | 벨 전송 | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | 로터리 엔코더 #1 활성화 | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | 업/다운/선택 입력 활성화 | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | 설명 | . | CODEC2 활성화 | Activate audio module | . | CODEC2 샘플 레이트 | Audio quality/bandwidth tradeoff | . | PTT 핀 | GPIO pin for the push-to-talk button | . | I2S 단어 선택 | GPIO pin for I2S WS | . | I2S 데이터 in | GPIO pin for I2S DIN | . | I2S 데이터 out | GPIO pin for I2S DOUT | . | I2S 시간 | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | 설명 | . | 원격 하드웨어 활성화 | Activate remote GPIO access | . | Allow undefined pin access | Allow access to any GPIO pin (security risk) | . | Available pins | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | 설명 | . | 이웃 정보 활성화 | Activate neighbor broadcasting | . | 업데이트 간격 (초) | How often to broadcast neighbor list | . | LoRa로 전송 | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | 설명 | . | LED 상태 | Turn the LED on or off | . | 전류 | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | 설명 | . | 감지 센서 활성화 | Activate detection sensor | . | 상태 모니터링 GPIO 핀 | GPIO pin connected to sensor | . | 디텍션 트리거 타입 | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | INPUT_PULLUP 모드 사용 | Enable the pin’s internal pull-up resistor | . | 최소 전송 간격 (초) | Minimum time between alert broadcasts | . | 상태 전송 간격 (초) | Periodic state broadcast interval | . | 알람 메시지와 벨 전송 | Include bell character in alerts | . | 식별 이름 | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | 설명 | . | 팍스카운터 활성화 | Activate people counting | . | 업데이트 간격 (초) | How often to report counts | . | Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ", + "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | 설명 | . | MQTT 활성화 | Toggle MQTT bridge | . | 서버 주소 | MQTT broker address | . | 사용자명 | Authentication username | . | 비밀번호 | Authentication password | . | 암호화 사용 | Encrypt MQTT payloads | . | JSON 사용 | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS 사용 | Use secure connection | . | Root topic | Base MQTT topic path | . | Proxy to client 사용 | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | 맵 보고 | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | 설명 | . | 동의합니다. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | 설명 | . | 시리얼 활성화 | Activate serial communication | . | 에코 활성화 | Echo received serial data back | . | 시리얼 모드 | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | 시리얼 baud rate | Port speed | . | 시간 초과 | How long to wait before considering an incoming message complete | . | Override console serial port | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | 설명 | . | 외부 알림 활성화 | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | LED 출력 (GPIO) | Pin the LED is wired to | . | LED 출력 active high | Whether the LED pin is active high or low | . | 부저 출력 (GPIO) | Pin the buzzer is wired to | . | 진동 출력 (GPIO) | Pin the vibration motor is wired to | . | PWM 부저 사용 | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | I2S 부저 사용 | Send the alert through an I2S audio output instead | . | GPIO Output Duration | How long a single alert lasts | . | Nag Timeout | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | 벨소리 | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | 설명 | . | 저장 및 전달 활성화 | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | Number of records | Maximum stored messages | . | History return max | Max messages to replay | . | History return window | Time window for replay | . | 서버 | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | 설명 | . | 거리 테스트 활성화 | Activate range testing | . | Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals | . | .CSV 파일 저장 (EPS32만 동작) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | 설명 | . | Send Device Telemetry | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Device metrics update interval | How often to report battery, uptime and channel utilization | . | 환경 메트릭 모듈 사용 | Report the attached environment sensors | . | Environment metrics update interval | How often to report them | . | 환경 메트릭 화면 사용 | Also show these readings on the device’s own display | . | 환경 메트릭에서 화씨 사용 | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | 대기질 메트릭 모듈 사용 | Report particulate and CO₂ sensor data | . | Air quality metrics update interval | How often to report them | . | 전력 메트릭 모듈 사용 | Report the per-channel voltage and current readings | . | Power metrics update interval | How often to report them | . | 전력 메트릭 화면 사용 | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | 설명 | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | 메시지기기 | Newline-separated list of messages | . | 벨 전송 | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | 로터리 엔코더 #1 활성화 | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | 업/다운/선택 입력 활성화 | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | 설명 | . | CODEC2 활성화 | Activate audio module | . | CODEC2 샘플 레이트 | Audio quality/bandwidth tradeoff | . | PTT 핀 | GPIO pin for the push-to-talk button | . | I2S 단어 선택 | GPIO pin for I2S WS | . | I2S 데이터 in | GPIO pin for I2S DIN | . | I2S 데이터 out | GPIO pin for I2S DOUT | . | I2S 시간 | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | 설명 | . | 원격 하드웨어 활성화 | Activate remote GPIO access | . | Allow undefined pin access | Allow access to any GPIO pin (security risk) | . | Available pins | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | 설명 | . | 이웃 정보 활성화 | Activate neighbor broadcasting | . | Update Interval | How often to broadcast neighbor list | . | LoRa로 전송 | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | 설명 | . | LED 상태 | Turn the LED on or off | . | 전류 | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | 설명 | . | 감지 센서 활성화 | Activate detection sensor | . | 상태 모니터링 GPIO 핀 | GPIO pin connected to sensor | . | 디텍션 트리거 타입 | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | INPUT_PULLUP 모드 사용 | Enable the pin’s internal pull-up resistor | . | Minimum time between detection broadcasts | Minimum time between alert broadcasts | . | State Broadcast Interval | Periodic state broadcast interval | . | 알람 메시지와 벨 전송 | Include bell character in alerts | . | 식별 이름 | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | 설명 | . | 팍스카운터 활성화 | Activate people counting | . | Update Interval | How often to report counts | . | WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ", "url": "/Meshtastic-Android/main/ko-rKR/user/settings-module-admin.html#%EB%AA%A8%EB%93%88-%EC%84%A4%EC%A0%95", "relUrl": "/ko-rKR/user/settings-module-admin.html#모듈-설정" @@ -30192,7 +30192,7 @@ },"4313": { "doc": "Settings — Modules & Admin", "title": "Modul konfiguration", - "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Beskrivning | . | MQTT är aktiverat | Toggle MQTT bridge | . | Adress | MQTT broker address | . | Användarnamn | Authentication username | . | Lösenord | Authentication password | . | Kryptering aktiverad | Encrypt MQTT payloads | . | JSON-utdata aktiverad | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS är aktiverat | Use secure connection | . | Rotämne (root topic) | Base MQTT topic path | . | Proxy till klient aktiverad | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Map reporting | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Beskrivning | . | Jag godkänner. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Map reporting interval (seconds) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Beskrivning | . | Seriell aktiverad | Activate serial communication | . | Eko aktiverad | Echo received serial data back | . | Seriellt läge | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Den seriella kommunikationens hastighet | Port speed | . | Timeout | How long to wait before considering an incoming message complete | . | Override console serial port | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Beskrivning | . | Externa aviseringar aktiverad | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Utmatning LED (GPIO) | Pin the LED is wired to | . | Utmatnings-LED aktiv hög | Whether the LED pin is active high or low | . | Utmatning summer (GPIO) | Pin the buzzer is wired to | . | Utmatning vibration (GPIO) | Pin the vibration motor is wired to | . | Använd PWM-summern | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Använd I2S som summer | Send the alert through an I2S audio output instead | . | Utmatningstid (millisekunder) | How long a single alert lasts | . | Sluta tjata efter (sekunder) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Ringsignal | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Beskrivning | . | Lagra & vidarebefordra är aktiverad | Activate store and forward | . | Pulsera | Periodically announce this node’s store-and-forward capability | . | Antal poster | Maximum stored messages | . | Maxstorlek för historik | Max messages to replay | . | Returfönstrets storlek för historik | Time window for replay | . | Server | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Beskrivning | . | Räckvidstest aktiverat | Activate range testing | . | Avsändarens meddelandeintervall (sekunder) | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Spara .CSV i enheten (endast ESP32) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Beskrivning | . | Skicka enhetstelemetri | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Uppdateringsintervall för enhetsdata | How often to report battery, uptime and channel utilization | . | Mätmodul för miljö aktiverad | Report the attached environment sensors | . | Uppdateringsintervall för miljödata | How often to report them | . | Visning av miljödata på skärm är aktiverad | Also show these readings on the device’s own display | . | Miljömätvärden använder Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Luftkvalitetsmätarmodul aktiverad | Report particulate and CO₂ sensor data | . | Uppdateringsintervall för luftkvalitet | How often to report them | . | Strömmätarmodul aktiverad | Report the per-channel voltage and current readings | . | Uppdateringsintervall för strömmätare | How often to report them | . | Visning av strömvärden på skärm är aktiverad | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Beskrivning | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Meddelanden | Newline-separated list of messages | . | Skicka ljudavisering | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Rotary encoder #1 enabled | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Up/Down/Select input enabled | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Beskrivning | . | CODEC 2 aktiverat | Activate audio module | . | CODEC2 samplingshastighet | Audio quality/bandwidth tradeoff | . | PTT pin | GPIO pin for the push-to-talk button | . | I2S ordval | GPIO pin for I2S WS | . | I2S-data in | GPIO pin for I2S DIN | . | I2S-data ut | GPIO pin for I2S DOUT | . | I2S-klocka | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Beskrivning | . | Fjärrhårdvara aktiverad | Activate remote GPIO access | . | Allow undefined pin access | Allow access to any GPIO pin (security risk) | . | Tillgängliga pin | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Beskrivning | . | Grannskapsinformation aktiverat | Activate neighbor broadcasting | . | Uppdateringsintervall (sekunder) | How often to broadcast neighbor list | . | Skicka över LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Beskrivning | . | LED-läge | Turn the LED on or off | . | Ström | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Beskrivning | . | Detektionssensor aktiverad | Activate detection sensor | . | GPIO-pin att övervaka | GPIO pin connected to sensor | . | Detection trigger type | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Använd INPUT_PULLUP-läge | Enable the pin’s internal pull-up resistor | . | Minsta sändningsintervall (sekunder) | Minimum time between alert broadcasts | . | Statussändningsintervall (sekunder) | Periodic state broadcast interval | . | Skicka ljudavisering med larmmeddelande | Include bell character in alerts | . | Visningsnamn | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Beskrivning | . | PAX-räknare aktiverad | Activate people counting | . | Uppdateringsintervall (sekunder) | How often to report counts | . | Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ", + "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Beskrivning | . | MQTT är aktiverat | Toggle MQTT bridge | . | Adress | MQTT broker address | . | Användarnamn | Authentication username | . | Lösenord | Authentication password | . | Kryptering aktiverad | Encrypt MQTT payloads | . | JSON-utdata aktiverad | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS är aktiverat | Use secure connection | . | Rotämne (root topic) | Base MQTT topic path | . | Proxy till klient aktiverad | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Map reporting | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Beskrivning | . | Jag godkänner. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Beskrivning | . | Seriell aktiverad | Activate serial communication | . | Eko aktiverad | Echo received serial data back | . | Seriellt läge | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Den seriella kommunikationens hastighet | Port speed | . | Timeout | How long to wait before considering an incoming message complete | . | Override console serial port | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Beskrivning | . | Externa aviseringar aktiverad | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Utmatning LED (GPIO) | Pin the LED is wired to | . | Utmatnings-LED aktiv hög | Whether the LED pin is active high or low | . | Utmatning summer (GPIO) | Pin the buzzer is wired to | . | Utmatning vibration (GPIO) | Pin the vibration motor is wired to | . | Använd PWM-summern | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Använd I2S som summer | Send the alert through an I2S audio output instead | . | GPIO Output Duration | How long a single alert lasts | . | Time-out för påminnelse | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Ringsignal | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Beskrivning | . | Lagra & vidarebefordra är aktiverad | Activate store and forward | . | Pulsera | Periodically announce this node’s store-and-forward capability | . | Antal poster | Maximum stored messages | . | Maxstorlek för historik | Max messages to replay | . | Returfönstrets storlek för historik | Time window for replay | . | Server | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Beskrivning | . | Räckvidstest aktiverat | Activate range testing | . | Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Spara .CSV i enheten (endast ESP32) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Beskrivning | . | Skicka enhetstelemetri | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Uppdateringsintervall för enhetsdata | How often to report battery, uptime and channel utilization | . | Mätmodul för miljö aktiverad | Report the attached environment sensors | . | Uppdateringsintervall för miljödata | How often to report them | . | Visning av miljödata på skärm är aktiverad | Also show these readings on the device’s own display | . | Miljömätvärden använder Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Luftkvalitetsmätarmodul aktiverad | Report particulate and CO₂ sensor data | . | Uppdateringsintervall för luftkvalitet | How often to report them | . | Strömmätarmodul aktiverad | Report the per-channel voltage and current readings | . | Uppdateringsintervall för strömmätare | How often to report them | . | Visning av strömvärden på skärm är aktiverad | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Beskrivning | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Meddelanden | Newline-separated list of messages | . | Skicka ljudavisering | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Rotary encoder #1 enabled | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Up/Down/Select input enabled | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Beskrivning | . | CODEC 2 aktiverat | Activate audio module | . | CODEC2 samplingshastighet | Audio quality/bandwidth tradeoff | . | PTT pin | GPIO pin for the push-to-talk button | . | I2S ordval | GPIO pin for I2S WS | . | I2S-data in | GPIO pin for I2S DIN | . | I2S-data ut | GPIO pin for I2S DOUT | . | I2S-klocka | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Beskrivning | . | Fjärrhårdvara aktiverad | Activate remote GPIO access | . | Allow undefined pin access | Allow access to any GPIO pin (security risk) | . | Tillgängliga pin | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Beskrivning | . | Grannskapsinformation aktiverat | Activate neighbor broadcasting | . | Intervall för hämtning av GPS-position | How often to broadcast neighbor list | . | Skicka över LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Beskrivning | . | LED-läge | Turn the LED on or off | . | Ström | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Beskrivning | . | Detektionssensor aktiverad | Activate detection sensor | . | GPIO-pin att övervaka | GPIO pin connected to sensor | . | Detection trigger type | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Använd INPUT_PULLUP-läge | Enable the pin’s internal pull-up resistor | . | Minimum time between detection broadcasts | Minimum time between alert broadcasts | . | State Broadcast Interval | Periodic state broadcast interval | . | Skicka ljudavisering med larmmeddelande | Include bell character in alerts | . | Visningsnamn | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Beskrivning | . | PAX-räknare aktiverad | Activate people counting | . | Intervall för hämtning av GPS-position | How often to report counts | . | WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ", "url": "/Meshtastic-Android/main/sv-rSE/user/settings-module-admin.html#modul-konfiguration", "relUrl": "/sv-rSE/user/settings-module-admin.html#modul-konfiguration" @@ -30227,7 +30227,7 @@ },"4318": { "doc": "Settings — Modules & Admin", "title": "Konfigirasyon modil", - "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Deskripsyon | . | MQTT enabled | Toggle MQTT bridge | . | Address | MQTT broker address | . | Username | Authentication username | . | Password | Authentication password | . | Encryption enabled | Encrypt MQTT payloads | . | JSON output enabled | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS enabled | Use secure connection | . | Root topic | Base MQTT topic path | . | Proxy to client enabled | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Map reporting | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Deskripsyon | . | I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Map reporting interval (seconds) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Deskripsyon | . | Serial enabled | Activate serial communication | . | Echo enabled | Echo received serial data back | . | Serial mode | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Serial baud rate | Port speed | . | Tan pase | How long to wait before considering an incoming message complete | . | Override console serial port | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Deskripsyon | . | External notification enabled | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Output LED (GPIO) | Pin the LED is wired to | . | Output LED active high | Whether the LED pin is active high or low | . | Output buzzer (GPIO) | Pin the buzzer is wired to | . | Output vibra (GPIO) | Pin the vibration motor is wired to | . | Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Use I2S as buzzer | Send the alert through an I2S audio output instead | . | Output duration (milliseconds) | How long a single alert lasts | . | Nag timeout (seconds) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Deskripsyon | . | Store & Forward enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | Number of records | Maximum stored messages | . | History return max | Max messages to replay | . | History return window | Time window for replay | . | Server | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Deskripsyon | . | Range test enabled | Activate range testing | . | Sender message interval (seconds) | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Save .CSV in storage (ESP32 only) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Deskripsyon | . | Send Device Telemetry | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Device metrics update interval | How often to report battery, uptime and channel utilization | . | Environment metrics module enabled | Report the attached environment sensors | . | Environment metrics update interval | How often to report them | . | Environment metrics on-screen enabled | Also show these readings on the device’s own display | . | Environment metrics use Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Air quality metrics module enabled | Report particulate and CO₂ sensor data | . | Air quality metrics update interval | How often to report them | . | Power metrics module enabled | Report the per-channel voltage and current readings | . | Power metrics update interval | How often to report them | . | Power metrics on-screen enabled | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Deskripsyon | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Messages | Newline-separated list of messages | . | Send bell | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Rotary encoder #1 enabled | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Up/Down/Select input enabled | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Deskripsyon | . | CODEC 2 enabled | Activate audio module | . | CODEC2 sample rate | Audio quality/bandwidth tradeoff | . | PTT pin | GPIO pin for the push-to-talk button | . | I2S word select | GPIO pin for I2S WS | . | I2S data in | GPIO pin for I2S DIN | . | I2S data out | GPIO pin for I2S DOUT | . | I2S clock | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Deskripsyon | . | Remote Hardware enabled | Activate remote GPIO access | . | Allow undefined pin access | Allow access to any GPIO pin (security risk) | . | Available pins | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Deskripsyon | . | Neighbor Info enabled | Activate neighbor broadcasting | . | Update interval (seconds) | How often to broadcast neighbor list | . | Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Deskripsyon | . | LED state | Turn the LED on or off | . | Current | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Deskripsyon | . | Detection Sensor enabled | Activate detection sensor | . | GPIO pin to monitor | GPIO pin connected to sensor | . | Detection trigger type | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Use INPUT_PULLUP mode | Enable the pin’s internal pull-up resistor | . | Minimum broadcast (seconds) | Minimum time between alert broadcasts | . | State broadcast (seconds) | Periodic state broadcast interval | . | Send bell with alert message | Include bell character in alerts | . | Friendly name | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Deskripsyon | . | Paxcounter enabled | Activate people counting | . | Update interval (seconds) | How often to report counts | . | Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ", + "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Deskripsyon | . | MQTT enabled | Toggle MQTT bridge | . | Address | MQTT broker address | . | Username | Authentication username | . | Password | Authentication password | . | Encryption enabled | Encrypt MQTT payloads | . | JSON output enabled | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS enabled | Use secure connection | . | Root topic | Base MQTT topic path | . | Proxy to client enabled | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Map reporting | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Deskripsyon | . | I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Deskripsyon | . | Serial enabled | Activate serial communication | . | Echo enabled | Echo received serial data back | . | Serial mode | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Serial baud rate | Port speed | . | Tan pase | How long to wait before considering an incoming message complete | . | Override console serial port | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Deskripsyon | . | External notification enabled | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Output LED (GPIO) | Pin the LED is wired to | . | Output LED active high | Whether the LED pin is active high or low | . | Output buzzer (GPIO) | Pin the buzzer is wired to | . | Output vibra (GPIO) | Pin the vibration motor is wired to | . | Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Use I2S as buzzer | Send the alert through an I2S audio output instead | . | GPIO Output Duration | How long a single alert lasts | . | Nag Timeout | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Deskripsyon | . | Store & Forward enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | Number of records | Maximum stored messages | . | History return max | Max messages to replay | . | History return window | Time window for replay | . | Server | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Deskripsyon | . | Range test enabled | Activate range testing | . | Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Save .CSV in storage (ESP32 only) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Deskripsyon | . | Send Device Telemetry | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Device metrics update interval | How often to report battery, uptime and channel utilization | . | Environment metrics module enabled | Report the attached environment sensors | . | Environment metrics update interval | How often to report them | . | Environment metrics on-screen enabled | Also show these readings on the device’s own display | . | Environment metrics use Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Air quality metrics module enabled | Report particulate and CO₂ sensor data | . | Air quality metrics update interval | How often to report them | . | Power metrics module enabled | Report the per-channel voltage and current readings | . | Power metrics update interval | How often to report them | . | Power metrics on-screen enabled | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Deskripsyon | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Messages | Newline-separated list of messages | . | Send bell | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Rotary encoder #1 enabled | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Up/Down/Select input enabled | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Deskripsyon | . | CODEC 2 enabled | Activate audio module | . | CODEC2 sample rate | Audio quality/bandwidth tradeoff | . | PTT pin | GPIO pin for the push-to-talk button | . | I2S word select | GPIO pin for I2S WS | . | I2S data in | GPIO pin for I2S DIN | . | I2S data out | GPIO pin for I2S DOUT | . | I2S clock | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Deskripsyon | . | Remote Hardware enabled | Activate remote GPIO access | . | Allow undefined pin access | Allow access to any GPIO pin (security risk) | . | Available pins | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Deskripsyon | . | Neighbor Info enabled | Activate neighbor broadcasting | . | Update Interval | How often to broadcast neighbor list | . | Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Deskripsyon | . | LED state | Turn the LED on or off | . | Current | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Deskripsyon | . | Detection Sensor enabled | Activate detection sensor | . | GPIO pin to monitor | GPIO pin connected to sensor | . | Detection trigger type | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Use INPUT_PULLUP mode | Enable the pin’s internal pull-up resistor | . | Minimum time between detection broadcasts | Minimum time between alert broadcasts | . | State Broadcast Interval | Periodic state broadcast interval | . | Send bell with alert message | Include bell character in alerts | . | Friendly name | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Deskripsyon | . | Paxcounter enabled | Activate people counting | . | Update Interval | How often to report counts | . | WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ", "url": "/Meshtastic-Android/main/ht-rHT/user/settings-module-admin.html#konfigirasyon-modil", "relUrl": "/ht-rHT/user/settings-module-admin.html#konfigirasyon-modil" @@ -30262,7 +30262,7 @@ },"4323": { "doc": "Settings — Modules & Admin", "title": "Конфигурација модула", - "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Опис | . | MQTT enabled | Toggle MQTT bridge | . | Адреса | MQTT broker address | . | Корисничко име | Authentication username | . | Лозинка | Authentication password | . | Encryption enabled | Encrypt MQTT payloads | . | JSON output enabled | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS enabled | Use secure connection | . | Root topic | Base MQTT topic path | . | Proxy to client enabled | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Map reporting | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Опис | . | I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Map reporting interval (seconds) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Опис | . | Serial enabled | Activate serial communication | . | Echo enabled | Echo received serial data back | . | Serial mode | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Serial baud rate | Port speed | . | Isteklo vreme | How long to wait before considering an incoming message complete | . | Override console serial port | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Опис | . | External notification enabled | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Output LED (GPIO) | Pin the LED is wired to | . | Output LED active high | Whether the LED pin is active high or low | . | Output buzzer (GPIO) | Pin the buzzer is wired to | . | Output vibra (GPIO) | Pin the vibration motor is wired to | . | Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Use I2S as buzzer | Send the alert through an I2S audio output instead | . | Output duration (milliseconds) | How long a single alert lasts | . | Nag timeout (seconds) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Мелодија звона | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Опис | . | Store & Forward enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | Број записа | Maximum stored messages | . | History return max | Max messages to replay | . | History return window | Time window for replay | . | Сервер | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Опис | . | Range test enabled | Activate range testing | . | Sender message interval (seconds) | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Save .CSV in storage (ESP32 only) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Опис | . | Send Device Telemetry | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Device metrics update interval | How often to report battery, uptime and channel utilization | . | Environment metrics module enabled | Report the attached environment sensors | . | Environment metrics update interval | How often to report them | . | Environment metrics on-screen enabled | Also show these readings on the device’s own display | . | Environment metrics use Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Air quality metrics module enabled | Report particulate and CO₂ sensor data | . | Air quality metrics update interval | How often to report them | . | Power metrics module enabled | Report the per-channel voltage and current readings | . | Power metrics update interval | How often to report them | . | Power metrics on-screen enabled | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Опис | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Поруке | Newline-separated list of messages | . | Send bell | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Rotary encoder #1 enabled | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Up/Down/Select input enabled | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Опис | . | CODEC 2 enabled | Activate audio module | . | CODEC2 sample rate | Audio quality/bandwidth tradeoff | . | PTT pin | GPIO pin for the push-to-talk button | . | I2S word select | GPIO pin for I2S WS | . | I2S data in | GPIO pin for I2S DIN | . | I2S data out | GPIO pin for I2S DOUT | . | I2S clock | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Опис | . | Remote Hardware enabled | Activate remote GPIO access | . | Allow undefined pin access | Allow access to any GPIO pin (security risk) | . | Available pins | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Опис | . | Neighbor Info enabled | Activate neighbor broadcasting | . | Update interval (seconds) | How often to broadcast neighbor list | . | Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Опис | . | LED state | Turn the LED on or off | . | Струја | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Опис | . | Detection Sensor enabled | Activate detection sensor | . | GPIO pin to monitor | GPIO pin connected to sensor | . | Detection trigger type | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Use INPUT_PULLUP mode | Enable the pin’s internal pull-up resistor | . | Minimum broadcast (seconds) | Minimum time between alert broadcasts | . | State broadcast (seconds) | Periodic state broadcast interval | . | Send bell with alert message | Include bell character in alerts | . | Пријатељски назив | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Опис | . | Paxcounter enabled | Activate people counting | . | Update interval (seconds) | How often to report counts | . | Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ", + "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Опис | . | MQTT enabled | Toggle MQTT bridge | . | Адреса | MQTT broker address | . | Корисничко име | Authentication username | . | Лозинка | Authentication password | . | Encryption enabled | Encrypt MQTT payloads | . | JSON output enabled | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS enabled | Use secure connection | . | Root topic | Base MQTT topic path | . | Proxy to client enabled | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Map reporting | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Опис | . | I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Интервал објављивања мапе | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Опис | . | Serial enabled | Activate serial communication | . | Echo enabled | Echo received serial data back | . | Serial mode | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Serial baud rate | Port speed | . | Isteklo vreme | How long to wait before considering an incoming message complete | . | Override console serial port | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Опис | . | External notification enabled | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Output LED (GPIO) | Pin the LED is wired to | . | Output LED active high | Whether the LED pin is active high or low | . | Output buzzer (GPIO) | Pin the buzzer is wired to | . | Output vibra (GPIO) | Pin the vibration motor is wired to | . | Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Use I2S as buzzer | Send the alert through an I2S audio output instead | . | Трајање GPIO излаза | How long a single alert lasts | . | Nag Timeout | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Мелодија звона | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Опис | . | Store & Forward enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | Број записа | Maximum stored messages | . | History return max | Max messages to replay | . | History return window | Time window for replay | . | Сервер | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Опис | . | Range test enabled | Activate range testing | . | Инерварл пошиљаоца | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Save .CSV in storage (ESP32 only) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Опис | . | Send Device Telemetry | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Device metrics update interval | How often to report battery, uptime and channel utilization | . | Environment metrics module enabled | Report the attached environment sensors | . | Environment metrics update interval | How often to report them | . | Environment metrics on-screen enabled | Also show these readings on the device’s own display | . | Environment metrics use Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Air quality metrics module enabled | Report particulate and CO₂ sensor data | . | Air quality metrics update interval | How often to report them | . | Power metrics module enabled | Report the per-channel voltage and current readings | . | Power metrics update interval | How often to report them | . | Power metrics on-screen enabled | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Опис | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Поруке | Newline-separated list of messages | . | Send bell | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Rotary encoder #1 enabled | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Up/Down/Select input enabled | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Опис | . | CODEC 2 enabled | Activate audio module | . | CODEC2 sample rate | Audio quality/bandwidth tradeoff | . | PTT pin | GPIO pin for the push-to-talk button | . | I2S word select | GPIO pin for I2S WS | . | I2S data in | GPIO pin for I2S DIN | . | I2S data out | GPIO pin for I2S DOUT | . | I2S clock | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Опис | . | Remote Hardware enabled | Activate remote GPIO access | . | Allow undefined pin access | Allow access to any GPIO pin (security risk) | . | Available pins | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Опис | . | Neighbor Info enabled | Activate neighbor broadcasting | . | Интервал ажурирања | How often to broadcast neighbor list | . | Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Опис | . | LED state | Turn the LED on or off | . | Струја | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Опис | . | Detection Sensor enabled | Activate detection sensor | . | GPIO pin to monitor | GPIO pin connected to sensor | . | Detection trigger type | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Use INPUT_PULLUP mode | Enable the pin’s internal pull-up resistor | . | Минимално време између емитовања детекције | Minimum time between alert broadcasts | . | Интервал емитовања стања | Periodic state broadcast interval | . | Send bell with alert message | Include bell character in alerts | . | Пријатељски назив | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Опис | . | Paxcounter enabled | Activate people counting | . | Интервал ажурирања | How often to report counts | . | WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ", "url": "/Meshtastic-Android/main/sr-rLatn/user/settings-module-admin.html#%D0%BA%D0%BE%D0%BD%D1%84%D0%B8%D0%B3%D1%83%D1%80%D0%B0%D1%86%D0%B8%D1%98%D0%B0-%D0%BC%D0%BE%D0%B4%D1%83%D0%BB%D0%B0", "relUrl": "/sr-rLatn/user/settings-module-admin.html#конфигурација-модула" @@ -30297,7 +30297,7 @@ },"4328": { "doc": "Settings — Modules & Admin", "title": "Module-configuratie", - "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Beschrijving | . | MQTT ingeschakeld | Toggle MQTT bridge | . | Adres | MQTT broker address | . | Gebruikersnaam | Authentication username | . | Wachtwoord | Authentication password | . | Encryptie ingeschakeld | Encrypt MQTT payloads | . | JSON uitvoer ingeschakeld | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS ingeschakeld | Use secure connection | . | Root topic | Base MQTT topic path | . | Proxy to client ingeschakeld | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Kaartrapportage | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Beschrijving | . | I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Map reporting interval (seconds) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Beschrijving | . | Serieel ingeschakeld | Activate serial communication | . | Echo ingeschakeld | Echo received serial data back | . | Seriële modus | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Serial baud rate | Port speed | . | Time-Out | How long to wait before considering an incoming message complete | . | Override console serial port | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Beschrijving | . | External notification enabled | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Output LED (GPIO) | Pin the LED is wired to | . | Output LED active high | Whether the LED pin is active high or low | . | Output buzzer (GPIO) | Pin the buzzer is wired to | . | Output vibra (GPIO) | Pin the vibration motor is wired to | . | Gebruik PWM zoemer | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Use I2S as buzzer | Send the alert through an I2S audio output instead | . | Output duur (milliseconden) | How long a single alert lasts | . | Nag timeout (seconds) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Beltoon | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Beschrijving | . | Store & Forward enabled | Activate store and forward | . | Hartslag | Periodically announce this node’s store-and-forward capability | . | Aantal records | Maximum stored messages | . | History return max | Max messages to replay | . | History return window | Time window for replay | . | Server | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Beschrijving | . | Range test enabled | Activate range testing | . | Sender message interval (seconds) | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Save .CSV in storage (ESP32 only) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Beschrijving | . | Send Device Telemetry | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Device metrics update interval | How often to report battery, uptime and channel utilization | . | Environment metrics module enabled | Report the attached environment sensors | . | Environment metrics update interval | How often to report them | . | Environment metrics on-screen enabled | Also show these readings on the device’s own display | . | Environment metrics use Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Air quality metrics module enabled | Report particulate and CO₂ sensor data | . | Air quality metrics update interval | How often to report them | . | Power metrics module enabled | Report the per-channel voltage and current readings | . | Power metrics update interval | How often to report them | . | Power metrics on-screen enabled | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Beschrijving | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Berichten | Newline-separated list of messages | . | Verstuur bel | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Rotary encoder #1 enabled | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Up/Down/Select input enabled | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Beschrijving | . | CODEC 2 ingeschakeld | Activate audio module | . | CODEC2 sample rate | Audio quality/bandwidth tradeoff | . | PTT pin | GPIO pin for the push-to-talk button | . | I2S word select | GPIO pin for I2S WS | . | I2S data in | GPIO pin for I2S DIN | . | I2S data out | GPIO pin for I2S DOUT | . | I2S klok | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Beschrijving | . | Externe hardware ingeschakeld | Activate remote GPIO access | . | Allow undefined pin access | Allow access to any GPIO pin (security risk) | . | Beschikbare pinnen | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Beschrijving | . | Neighbor Info enabled | Activate neighbor broadcasting | . | Update-interval (seconden) | How often to broadcast neighbor list | . | Zend over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Beschrijving | . | LED status | Turn the LED on or off | . | Huidige | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Beschrijving | . | Bewegingssensor Ingeschakeld | Activate detection sensor | . | GPIO pin om te monitoren | GPIO pin connected to sensor | . | Detectie trigger type | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Use INPUT_PULLUP mode | Enable the pin’s internal pull-up resistor | . | Minimale broadcast (seconden) | Minimum time between alert broadcasts | . | State broadcast (seconds) | Periodic state broadcast interval | . | Send bell with alert message | Include bell character in alerts | . | Weergavenaam | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Beschrijving | . | Paxcounter ingeschakeld | Activate people counting | . | Update-interval (seconden) | How often to report counts | . | Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ", + "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Beschrijving | . | MQTT ingeschakeld | Toggle MQTT bridge | . | Adres | MQTT broker address | . | Gebruikersnaam | Authentication username | . | Wachtwoord | Authentication password | . | Encryptie ingeschakeld | Encrypt MQTT payloads | . | JSON uitvoer ingeschakeld | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS ingeschakeld | Use secure connection | . | Root topic | Base MQTT topic path | . | Proxy to client ingeschakeld | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Kaartrapportage | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Beschrijving | . | I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Beschrijving | . | Serieel ingeschakeld | Activate serial communication | . | Echo ingeschakeld | Echo received serial data back | . | Seriële modus | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Serial baud rate | Port speed | . | Time-Out | How long to wait before considering an incoming message complete | . | Override console serial port | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Beschrijving | . | External notification enabled | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Output LED (GPIO) | Pin the LED is wired to | . | Output LED active high | Whether the LED pin is active high or low | . | Output buzzer (GPIO) | Pin the buzzer is wired to | . | Output vibra (GPIO) | Pin the vibration motor is wired to | . | Gebruik PWM zoemer | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Use I2S as buzzer | Send the alert through an I2S audio output instead | . | GPIO Output Duration | How long a single alert lasts | . | Nag Timeout | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Beltoon | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Beschrijving | . | Store & Forward enabled | Activate store and forward | . | Hartslag | Periodically announce this node’s store-and-forward capability | . | Aantal records | Maximum stored messages | . | History return max | Max messages to replay | . | History return window | Time window for replay | . | Server | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Beschrijving | . | Range test enabled | Activate range testing | . | Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Save .CSV in storage (ESP32 only) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Beschrijving | . | Send Device Telemetry | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Device metrics update interval | How often to report battery, uptime and channel utilization | . | Environment metrics module enabled | Report the attached environment sensors | . | Environment metrics update interval | How often to report them | . | Environment metrics on-screen enabled | Also show these readings on the device’s own display | . | Environment metrics use Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Air quality metrics module enabled | Report particulate and CO₂ sensor data | . | Air quality metrics update interval | How often to report them | . | Power metrics module enabled | Report the per-channel voltage and current readings | . | Power metrics update interval | How often to report them | . | Power metrics on-screen enabled | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Beschrijving | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Berichten | Newline-separated list of messages | . | Verstuur bel | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Rotary encoder #1 enabled | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Up/Down/Select input enabled | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Beschrijving | . | CODEC 2 ingeschakeld | Activate audio module | . | CODEC2 sample rate | Audio quality/bandwidth tradeoff | . | PTT pin | GPIO pin for the push-to-talk button | . | I2S word select | GPIO pin for I2S WS | . | I2S data in | GPIO pin for I2S DIN | . | I2S data out | GPIO pin for I2S DOUT | . | I2S klok | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Beschrijving | . | Externe hardware ingeschakeld | Activate remote GPIO access | . | Allow undefined pin access | Allow access to any GPIO pin (security risk) | . | Beschikbare pinnen | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Beschrijving | . | Neighbor Info enabled | Activate neighbor broadcasting | . | Update Interval | How often to broadcast neighbor list | . | Zend over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Beschrijving | . | LED status | Turn the LED on or off | . | Huidige | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Beschrijving | . | Bewegingssensor Ingeschakeld | Activate detection sensor | . | GPIO pin om te monitoren | GPIO pin connected to sensor | . | Detectie trigger type | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Use INPUT_PULLUP mode | Enable the pin’s internal pull-up resistor | . | Minimum time between detection broadcasts | Minimum time between alert broadcasts | . | State Broadcast Interval | Periodic state broadcast interval | . | Send bell with alert message | Include bell character in alerts | . | Weergavenaam | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Beschrijving | . | Paxcounter ingeschakeld | Activate people counting | . | Update Interval | How often to report counts | . | WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ", "url": "/Meshtastic-Android/main/nl-rNL/user/settings-module-admin.html#module-configuratie", "relUrl": "/nl-rNL/user/settings-module-admin.html#module-configuratie" @@ -30332,7 +30332,7 @@ },"4333": { "doc": "Settings — Modules & Admin", "title": "Налаштування модуля", - "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Опис | . | MQTT увімкнений | Toggle MQTT bridge | . | Адреса | MQTT broker address | . | Ім’я користувача | Authentication username | . | Пароль | Authentication password | . | Шифрування увімкнено | Encrypt MQTT payloads | . | Вивід JSON увімкнено | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS увімкнений | Use secure connection | . | Кореневий чат | Base MQTT topic path | . | Проксі для клієнта увімкнуто | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT проксі на цьому телефоні | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Відображення на мапі | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Опис | . | Погоджуюся. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Інтервал звітування на мапі (секунди) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Опис | . | Послідовний порт увімкнено | Activate serial communication | . | Відлуння активоване | Echo received serial data back | . | Послідовний режим | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Швидкість послідовного порту | Port speed | . | Таймаут | How long to wait before considering an incoming message complete | . | Перевизначити послідовний порт | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Опис | . | Зовнішні сповіщення увімкнено | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Вихідний LED (GPIO) | Pin the LED is wired to | . | Активний високий рівень світлодіода | Whether the LED pin is active high or low | . | Вихідний гудок (GPIO) | Pin the buzzer is wired to | . | Вихід вібросигналу (GPIO) | Pin the vibration motor is wired to | . | Використовувати зумер із ШІМ-керуванням | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Використовувати I2S як гудок | Send the alert through an I2S audio output instead | . | Тривалість виводу (мілісекунд) | How long a single alert lasts | . | Інтервал нагадувань (секунди) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Мелодія | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Опис | . | Збереження та перенаправлення увімкнено | Activate store and forward | . | Пульсація | Periodically announce this node’s store-and-forward capability | . | Кількість записів | Maximum stored messages | . | Максимальний обсяг історії | Max messages to replay | . | Максимальне вікно історії | Time window for replay | . | Сервер | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Опис | . | Тест на відстань увімкнений | Activate range testing | . | Інтервал надсилання повідомлень (секунди) | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Зберегти .CSV у сховищі (лише ESP32) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Опис | . | Надсилати телеметрію пристрою | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Інтервал оновлення показників пристрою | How often to report battery, uptime and channel utilization | . | Модуль екологічних показників увімкнено | Report the attached environment sensors | . | Інтервал оновлення екологічних показників | How often to report them | . | Екологічні показники на екрані увімкнено | Also show these readings on the device’s own display | . | Екологічні показники використовують шкалу Фаренгейта | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Модуль показників якості повітря увімкнено | Report particulate and CO₂ sensor data | . | Інтервал оновлення показників якості повітря | How often to report them | . | Модуль показників потужності ввімкнено | Report the per-channel voltage and current readings | . | Інтервал оновлення показників потужності | How often to report them | . | Показники потужності на екрані ввімкнено | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Опис | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Повідомлення | Newline-separated list of messages | . | Надіслати дзвіночок | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Енкодер #1 активований | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Увімкнути керування Вгору/Вниз/Вибір | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Опис | . | CODEC 2 увімкнено | Activate audio module | . | Частота дискретизації CODEC2 | Audio quality/bandwidth tradeoff | . | PTT контакт | GPIO pin for the push-to-talk button | . | Вибір слова I2S | GPIO pin for I2S WS | . | Вибір входу I2S | GPIO pin for I2S DIN | . | Вибір виходу I2S | GPIO pin for I2S DOUT | . | I2S тактування | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Опис | . | Конфігурація віддаленого пристрою активована | Activate remote GPIO access | . | Дозволити доступ до невизначених пінів | Allow access to any GPIO pin (security risk) | . | Доступні піни | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Опис | . | Інформацію про сусідів увімкнено | Activate neighbor broadcasting | . | Інтервал оновлення (секунд) | How often to broadcast neighbor list | . | Передавати через LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Опис | . | Стан світлодіоду | Turn the LED on or off | . | Поточний | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Опис | . | Датчик виявлення увімкнено | Activate detection sensor | . | GPIO контакт для моніторингу | GPIO pin connected to sensor | . | Тип тригера виявлення | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Використовувати режим INPUT_PULLUP | Enable the pin’s internal pull-up resistor | . | Мінімальний період розсилки (секунди) | Minimum time between alert broadcasts | . | Інтервал трансляції стану (секунди) | Periodic state broadcast interval | . | Надсилати дзвіночок з тривожним повідомленням | Include bell character in alerts | . | Дружня назва | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Опис | . | Лічильник пристроїв активований | Activate people counting | . | Інтервал оновлення (секунд) | How often to report counts | . | Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ", + "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Опис | . | MQTT увімкнений | Toggle MQTT bridge | . | Адреса | MQTT broker address | . | Ім’я користувача | Authentication username | . | Пароль | Authentication password | . | Шифрування увімкнено | Encrypt MQTT payloads | . | Вивід JSON увімкнено | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS увімкнений | Use secure connection | . | Кореневий чат | Base MQTT topic path | . | Проксі для клієнта увімкнуто | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT проксі на цьому телефоні | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Відображення на мапі | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Опис | . | Погоджуюся. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Опис | . | Послідовний порт увімкнено | Activate serial communication | . | Відлуння активоване | Echo received serial data back | . | Послідовний режим | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Швидкість послідовного порту | Port speed | . | Таймаут | How long to wait before considering an incoming message complete | . | Перевизначити послідовний порт | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Опис | . | Зовнішні сповіщення увімкнено | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Вихідний LED (GPIO) | Pin the LED is wired to | . | Активний високий рівень світлодіода | Whether the LED pin is active high or low | . | Вихідний гудок (GPIO) | Pin the buzzer is wired to | . | Вихід вібросигналу (GPIO) | Pin the vibration motor is wired to | . | Використовувати зумер із ШІМ-керуванням | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Використовувати I2S як гудок | Send the alert through an I2S audio output instead | . | GPIO Output Duration | How long a single alert lasts | . | Nag Timeout | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Мелодія | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Опис | . | Збереження та перенаправлення увімкнено | Activate store and forward | . | Пульсація | Periodically announce this node’s store-and-forward capability | . | Кількість записів | Maximum stored messages | . | Максимальний обсяг історії | Max messages to replay | . | Максимальне вікно історії | Time window for replay | . | Сервер | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Опис | . | Тест на відстань увімкнений | Activate range testing | . | Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Зберегти .CSV у сховищі (лише ESP32) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Опис | . | Надсилати телеметрію пристрою | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Інтервал оновлення показників пристрою | How often to report battery, uptime and channel utilization | . | Модуль екологічних показників увімкнено | Report the attached environment sensors | . | Інтервал оновлення екологічних показників | How often to report them | . | Екологічні показники на екрані увімкнено | Also show these readings on the device’s own display | . | Екологічні показники використовують шкалу Фаренгейта | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Модуль показників якості повітря увімкнено | Report particulate and CO₂ sensor data | . | Інтервал оновлення показників якості повітря | How often to report them | . | Модуль показників потужності ввімкнено | Report the per-channel voltage and current readings | . | Інтервал оновлення показників потужності | How often to report them | . | Показники потужності на екрані ввімкнено | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Опис | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Повідомлення | Newline-separated list of messages | . | Надіслати дзвіночок | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Енкодер #1 активований | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Увімкнути керування Вгору/Вниз/Вибір | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Опис | . | CODEC 2 увімкнено | Activate audio module | . | Частота дискретизації CODEC2 | Audio quality/bandwidth tradeoff | . | PTT контакт | GPIO pin for the push-to-talk button | . | Вибір слова I2S | GPIO pin for I2S WS | . | Вибір входу I2S | GPIO pin for I2S DIN | . | Вибір виходу I2S | GPIO pin for I2S DOUT | . | I2S тактування | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Опис | . | Конфігурація віддаленого пристрою активована | Activate remote GPIO access | . | Дозволити доступ до невизначених пінів | Allow access to any GPIO pin (security risk) | . | Доступні піни | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Опис | . | Інформацію про сусідів увімкнено | Activate neighbor broadcasting | . | Інтервал опитування GPS | How often to broadcast neighbor list | . | Передавати через LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Опис | . | Стан світлодіоду | Turn the LED on or off | . | Поточний | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Опис | . | Датчик виявлення увімкнено | Activate detection sensor | . | GPIO контакт для моніторингу | GPIO pin connected to sensor | . | Тип тригера виявлення | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Використовувати режим INPUT_PULLUP | Enable the pin’s internal pull-up resistor | . | Minimum time between detection broadcasts | Minimum time between alert broadcasts | . | State Broadcast Interval | Periodic state broadcast interval | . | Надсилати дзвіночок з тривожним повідомленням | Include bell character in alerts | . | Дружня назва | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Опис | . | Лічильник пристроїв активований | Activate people counting | . | Інтервал опитування GPS | How often to report counts | . | WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ", "url": "/Meshtastic-Android/main/uk-rUA/user/settings-module-admin.html#%D0%BD%D0%B0%D0%BB%D0%B0%D1%88%D1%82%D1%83%D0%B2%D0%B0%D0%BD%D0%BD%D1%8F-%D0%BC%D0%BE%D0%B4%D1%83%D0%BB%D1%8F", "relUrl": "/uk-rUA/user/settings-module-admin.html#налаштування-модуля" @@ -30367,7 +30367,7 @@ },"4338": { "doc": "Asetukset — Moduulit ja ylläpito", "title": "Moduulin asetukset", - "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Yhdistää verkon viestejä MQTT-välityspalvelimeen ja sieltä takaisin internet-yhteyksiä varten. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Asetus | Kuvaus | . | MQTT käytössä | Ota MQTT-välityspalvelin käyttöön | . | Osoite | MQTT-välityspalvelimen osoite | . | Käyttäjänimi | Todennuksen käyttäjätunnus | . | Salasana | Todennuksen salasana | . | Salaus käytössä | Salaa MQTT-viestisisällöt | . | JSON ulostulo käytössä | Julkaise ja vastaanota MQTT-viestejä JSON-muodossa. Merkitty protobuf-rakenteessa vanhentuneeksi, mutta tämä on edelleen ainoa asetus tähän toimintaan, ja laiteohjelmisto käyttää sitä yhä | . | TLS käytössä | Käytä suojattua yhteyttä | . | Palvelimen osoite (root topic) | MQTT:n perusaihepolku | . | Välityspalvelin käytössä | Anna yhdistetyn puhelimen välittää radion MQTT-liikenne sen sijaan, että radio muodostaisi itse yhteyden välityspalvelimeen | . | MQTT-välityspalvelin tällä puhelimella | Yllä olevan Välitys asiakkaalle käytössä -asetuksen puhelinpään osuus: käyttääkö tämä puhelin kyseistä välitystä. Katso MQTT | . | Karttaraportointi | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Asetus | Kuvaus | . | Hyväksyn. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Karttaraportoinnin aikaväli (sekuntia) | Kuinka usein sijainti julkaistaan. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . Katso MQTT saadaksesi yksityiskohtaisen käyttöoppaan, joka sisältää salauksen, tietosuojan ja välityspalvelimen määrityksen. Serial module . Mahdollistaa sarjaporttiviestinnän ulkoisten laiteintegraatioiden kanssa (GPS-moduulit, anturit tai mukautettu laitteisto). Kun tämä on käytössä, radion sarjaportti voi lähettää ja vastaanottaa protobuf- tai tekstimuotoista dataa, jolloin ulkoiset mikrokontrollerit tai tietokoneet voivat olla vuorovaikutuksessa verkon kanssa. | Asetus | Kuvaus | . | Sarjaportti käytössä | Ota sarjaporttiviestintä käyttöön | . | Palautus päällä | Toista vastaanotettu sarjaporttidata takaisin | . | Sarjaportin tila | Portin käyttämä protokolla – Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, YE.Direct, MeshSolar config, Log tai Log (vain teksti) | . | Vastaanotto / lähetys | Sarjayhteyden GPIO-nastat | . | Sarjaportin nopeus | Portin nopeus | . | Aikakatkaisu | Kuinka kauan odotetaan ennen kuin saapuva viesti katsotaan kokonaiseksi | . | Korvaa konsolin sarjaportti | Ota käyttöön portti, jota virheenkorjauskonsoli normaalisti käyttää | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Hyödyllinen laitteille, joiden täytyy ilmoittaa fyysisesti viestin saapumisesta — erityisen hyödyllinen valvomattomissa tai ulkokäyttöön asennetuissa laitteissa. Käynnistimiä on kaksi – saapuva viesti ja vastaanotettu BEL-ohjausmerkki – ja kumpikin voi ohjata LED-valoa, summeria ja värinämoottoria erikseen, joten käytettävissä on kuusi kytkintä. | Asetus | Kuvaus | . | Ulkoiset ilmoitukset käytössä | Moduulin pääkytkin | . | Hälytysviesti: LED / summeri / värinä | Mitkä lähdöt aktivoituvat saapuvasta viestistä | . | Hälytysmerkki: LED / summeri / värinä | Mitkä lähdöt aktivoituvat vastaanotetusta BEL-ohjausmerkistä | . | Ulostulon LED (GPIO) | LED on kytketty nastaan | . | Ulostulon LED aktiivinen | Onko LED-nasta aktiivinen korkealla vai matalalla tasolla | . | Ulostulon äänimerkki (GPIO) | Summeri on kytketty nastaan | . | Ulostulon värinä (GPIO) | Värinämoottori on kytketty nastaan | . | Käytä PWM-äänimerkkiä | Ohjaa summeria PWM:llä, jolloin voidaan toistaa ääniä yhden kiinteän taajuuden sijaan | . | Käytä I2S protokollaa äänimerkille | Lähetä hälytys sen sijaan I2S-äänilähdön kautta | . | Ulostulon kesto (millisekuntia) | Kuinka kauan yksittäinen hälytys kestää | . | Hälytysaikakatkaisu (sekuntia) | Toista hälytystä tämän ajan, kunnes se kuitataan. 0 poistaa toistuvan muistutuksen käytöstä | . | Soittoääni | PWM-summerilla toistettava RTTTL-soittoääni. Voidaan tuoda tiedostosta | . Store & Forward module . Puskuroi viestejä radioille, jotka ovat tilapäisesti poissa verkosta, ja toimittaa ne, kun nämä radiot yhdistyvät uudelleen. Välttämätön verkoissa, joissa radiot siirtyvät säännöllisesti kuuluvuusalueelle ja sen ulkopuolelle — varmistaa, etteivät viestit katoa lyhyiden yhteyskatkosten aikana. | Asetus | Kuvaus | . | Tallenna ja lähetä edelleen | Ota Varastoi & välitä käyttöön | . | Valvontasignaali | Ilmoita tämän radion varastoi & välitä -ominaisuudesta säännöllisesti | . | Kirjausten määrä | Tallennettujen viestien enimmäismäärä | . | Historian maksimimäärä | Toistettavien viestien enimmäismäärä | . | Historian aikamäärä | Aikaikkuna viestien toistolle | . | Palvelin | Toimi mesh-verkon varastoi & välitä -palvelimena (edellyttää riittävästi muistia, esimerkiksi ESP32 PSRAM:lla) | . 💡 Vinkki: Varastoi & välitä toimii parhaiten radioissa, joissa on runsaasti muistia (ESP32 ja PSRAM). Router-roolin radiot ovat ihanteellisia ehdokkaita, koska ne ovat yleensä jatkuvasti käynnissä. Range Test module . ⚠️ Varoitus: Kuuluvuustesti toimii vain suojatulla ensisijaisella kanavalla. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automaattinen kuuluvuustestityökalu radioiden välisen yhteyden laadun arviointiin. Kun toiminto on käytössä, radio lähettää säännöllisesti testiviestejä kasvavilla laskuriarvoilla. Vastaanottava radio kirjaa nämä viestit, jolloin voit myöhemmin kävellä tai ajaa pois ja analysoida, millä etäisyydellä viestien saapuminen loppui. | Asetus | Kuvaus | . | Kuuluvuustesti käytössä | Ota kuuluvuustesti käyttöön | . | Viestien lähetyksen aikaväli (sekuntia) | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Tallenna .CSV (ESP32 ainoastaan) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Määrittää, mitä telemetriatietoja radiosi jakaa verkkoon. Telemetria sisältää laitteen kuntoon liittyviä tietoja (akun varaustaso, käyttöaika) sekä ympäristöanturien tietoja (lämpötila, kosteus, ilmanpaine). Jokaisella neljällä mittausryhmällä on oma käyttöönottokytkin ja oma mittausväli, joten esimerkiksi akun tila voidaan raportoida usein ja anturitiedot harvemmin. | Asetus | Kuvaus | . | Lähetä laitteen telemetriatiedot | Laitemittausten pääkytkin. Näkyy vain laiteohjelmistoversiossa 2.7.12 ja uudemmissa | . | Laitemittareiden päivitysväli | How often to report battery, uptime and channel utilization | . | Ympäristötietojen moduuli käytössä | Raportoi liitettyjen ympäristöanturien tiedot | . | Ympäristömittareiden päivitysväli | Kuinka usein tiedot raportoidaan | . | Näytä ympäristötiedot näytöllä | Näytä nämä tiedot myös radion omalla näytöllä | . | Käytä Fahrenheit yksikköä | Käytä radion näytössä Fahrenheit-asteita. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Ilmanlaadun tietojen moduuli käytössä | Raportoi hiukkas- ja CO₂-anturin tiedot | . | Ilmanlaatumittareiden päivitysväli | Kuinka usein tiedot raportoidaan | . | Virrankulutuksen moduuli käytössä | Raportoi kanavakohtaiset jännite- ja virtamittaukset | . | Virtamittareiden päivitysväli | Kuinka usein tiedot raportoidaan | . | Virrankulutuksen näyttö käytössä | Näytä virtamittaukset myös radion omalla näytöllä | . Katso Telemetria ja anturit saadaksesi tietoa tuetuista antureista ja määrityssuosituksista. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Määritä luettelo pikaviesteistä, jotka voidaan lähettää ilman yhdistettyä puhelinta — ihanteellinen kenttäkäyttöön. | Asetus | Kuvaus | . | Valmisviesti käytössä | ⚠️ Vanhentunut protobuf-rakenteessa | . | Viestit | Rivinvaihdoilla eroteltu viestiluettelo | . | Lähetä äänimerkki | Lähetä viestin mukana BEL-ohjausmerkki, jotta vastaanottavan radion Ulkoiset ilmoitukset -moduuli voi antaa hälytyksen | . | Kiertovalitsin #1 käytössä | Käytä kiertokoodainta syöttölaitteena | . | GPIO pin for rotary encoder A / B / Press port | Kolme nastaa, joihin kiertokoodain on kytketty | . | Generate input event on Press / CW / CCW | Minkä näppäintapahtuman kukin kiertokoodaimen toiminto tuottaa | . | Ylös/Alas/Valitse syöte käytössä | Erillinen, yksinkertaisempi syöttötapa, jossa käytetään ylös-/alas-/valitse-painikkeita kiertokoodaimen sijaan | . | Salli syöttölähde | ⚠️ Vanhentunut protobuf-rakenteessa | . Audio module . Codec2-äänituki matalan kaistanleveyden puheviestintään verkossa. Tämä on kokeellinen ominaisuus, joka koodaa puheen erittäin pieniksi datapaketeiksi käyttäen Codec2-koodekkia. | Asetus | Kuvaus | . | CODEC 2 käytössä | Ota äänimoduuli käyttöön | . | CODEC2 näytteenottotaajuus | Äänenlaadun ja kaistanleveyden välinen kompromissi | . | PTT-pinni | PTT-painikkeen GPIO-nasta | . | I2S-sanan valinta | GPIO-pinni I2S WS:lle | . | I2S-datatulo | GPIO-nasta I2S DIN:lle | . | I2S-datalähtö | GPIO-pinni I2S DOUT:lle | . | I2S-kello | I2S-bittikellon GPIO-nasta | . ℹ️ Huomautus: Ääniominaisuus edellyttää yhteensopivaa laitteistoa (I2S-mikrofoni ja -kaiutin). Äänenlaatu on hyvin matalakaistainen — ajattele “ymmärrettävää radiopuhetta”, ei puhelinlaatua. Remote Hardware module . GPIO-ohjaus mesh-verkon kautta. Mahdollistaa etäradion lukea tai kirjoittaa GPIO-nastoja toisessa radiossa — hyödyllinen releiden aktivointiin, kytkimien lukemiseen tai ulkoisen laitteiston ohjaamiseen etäältä. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Asetus | Kuvaus | . | Etälaitteen ohjaus käytössä | Ota etä-GPIO-käyttö käyttöön | . | Salli määrittämättömän pinnin käyttö | Salli pääsy mihin tahansa GPIO-nastaan (tietoturvariski) | . | Käytettävissä olevat pinnit | Enintään 4 tämän radion etälukuun tai kirjoitukseen tarjoamaa GPIO-pinniä | . Neighbor Info module . Lähettää tietoa suoraan kuulluista naapureista mahdollistaen verkon topologian kartoituksen. Jokainen käyttöön otettu radio jakaa säännöllisesti luettelon muista radioista, jotka se kuulee, sekä niiden signaalin laadun. | Asetus | Kuvaus | . | Naapuritiedot käytössä | Ota naapuritiedon lähetys käyttöön | . | Päivityksen aikaväli (sekuntia) | Kuinka usein naapuriluettelo lähetetään | . | Lähetä LoRa:n kautta | Lähetä myös naapuritiedot LoRa:n kautta, ei pelkästään MQTT:n tai puhelimen kautta. Ei käytettävissä kanavalla, joka käyttää oletusavainta ja nimeä | . Katso Paikallinen mesh-haku, miten naapuritietoja käytetään mesh-verkon rakenteen tutkimiseen. Ambient Lighting module . Ohjaa tuetuissa laitteissa olevaa NeoPixeliä tai muita osoitteellisia RGB-LEDejä. Voidaan käyttää visuaalisina tilailmaisimina, ilmoitusvaloina tai koriste-efekteinä. | Asetus | Kuvaus | . | LED-tila | Kytke LED päälle tai pois päältä | . | Virta | LED-virran rajoitus (0–31) | . | Punainen / vihreä / sininen | Yksittäisten värikanavien arvot (0–255) | . Detection Sensor module . Muuttaa radiosi liike- tai ovitunnistimeen perustuvaksi hälytysjärjestelmäksi. Kun GPIO-pinni havaitsee tilamuutoksen (liike havaittu, ovi avattu), radio lähettää hälytysviestin verkkoon. | Asetus | Kuvaus | . | Tunnistinsensori käytössä | Ota tunnistusanturi käyttöön | . | GPIO-pinni valvontaa varten | Anturiin kytketty GPIO-pinni | . | Tunnistuksen tyyppi | Miten pinnin tila vastaa havaitsemistapahtumaa (esim. aktiivinen korkea/matala taso tai reunalaukaisu) | . | Käytä INPUT_PULLUP tilaa | Ota pinnin sisäinen ylösvetovastus käyttöön | . | Minimilähetys (sekuntia) | Hälytyslähetysten vähimmäisaika | . | Tilatiedon lähetys (sekuntia) | Tilatiedon lähetysväli | . | Lähetä äänimerkki hälytyssanoman kanssa | Sisällytä soittomerkkimerkki hälytyksiin | . | Käyttäjäystävällinen nimi | Tälle anturille määritetty nimi | . Paxcounter module . Henkilöt, jotka lasketaan WiFi- ja BLE-hakukyselyiden perusteella. Laskee lähellä olevia laitteita kuuntelemalla passiivisesti koepyyntöjä, joita puhelimet ja kannettavat tietokoneet lähettävät etsiessään verkkoja. Saatavilla vain ESP32-laitteissa. | Asetus | Kuvaus | . | PAX-laskuri käytössä | Ota henkilölaskenta käyttöön | . | Päivityksen aikaväli (sekuntia) | Kuinka usein laskentatiedot raportoidaan | . | WiFi-signaalin RSSI-kynnys | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE-signaalin RSSI-kynnys | Sama raja-arvo BLE-mainospaketeille (oletus: -80 dBm) | . 💡 Vinkki: PAX-laskuri on hyödyllinen jalankulkijamäärien arviointiin retkeilyreittien lähtöpisteissä, tapahtumapaikoilla tai muissa kohteissa. Laskentatulokset ovat arvioita — yhdellä henkilöllä voi olla useita laitteita mukana. Status Message module . Tilaviestillä ei ole omaa moduulinäkymää. Sitä muokataan yhdessä muiden radion tunnistetietojen kanssa kohdassa Asetukset → Radio ja käyttäjä. Mesh Beacon module . Lähettää kutsun mesh-verkkoosi ja vastaanottaa muiden lähettämiä kutsuja. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit -integraatio yhteensopivuutta varten ATAK- ja WinTAK-järjestelmien kanssa. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. Katso TAK-integraatio saadaksesi tarkemmat määritys- ja käyttöohjeet. ", + "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Yhdistää verkon viestejä MQTT-välityspalvelimeen ja sieltä takaisin internet-yhteyksiä varten. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Asetus | Kuvaus | . | MQTT käytössä | Ota MQTT-välityspalvelin käyttöön | . | Osoite | MQTT-välityspalvelimen osoite | . | Käyttäjänimi | Todennuksen käyttäjätunnus | . | Salasana | Todennuksen salasana | . | Salaus käytössä | Salaa MQTT-viestisisällöt | . | JSON ulostulo käytössä | Julkaise ja vastaanota MQTT-viestejä JSON-muodossa. Merkitty protobuf-rakenteessa vanhentuneeksi, mutta tämä on edelleen ainoa asetus tähän toimintaan, ja laiteohjelmisto käyttää sitä yhä | . | TLS käytössä | Käytä suojattua yhteyttä | . | Palvelimen osoite (root topic) | MQTT:n perusaihepolku | . | Välityspalvelin käytössä | Anna yhdistetyn puhelimen välittää radion MQTT-liikenne sen sijaan, että radio muodostaisi itse yhteyden välityspalvelimeen | . | MQTT-välityspalvelin tällä puhelimella | Yllä olevan Välitys asiakkaalle käytössä -asetuksen puhelinpään osuus: käyttääkö tämä puhelin kyseistä välitystä. Katso MQTT | . | Karttaraportointi | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Asetus | Kuvaus | . | Hyväksyn. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Map Publish Interval | Kuinka usein sijainti julkaistaan. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . Katso MQTT saadaksesi yksityiskohtaisen käyttöoppaan, joka sisältää salauksen, tietosuojan ja välityspalvelimen määrityksen. Serial module . Mahdollistaa sarjaporttiviestinnän ulkoisten laiteintegraatioiden kanssa (GPS-moduulit, anturit tai mukautettu laitteisto). Kun tämä on käytössä, radion sarjaportti voi lähettää ja vastaanottaa protobuf- tai tekstimuotoista dataa, jolloin ulkoiset mikrokontrollerit tai tietokoneet voivat olla vuorovaikutuksessa verkon kanssa. | Asetus | Kuvaus | . | Sarjaportti käytössä | Ota sarjaporttiviestintä käyttöön | . | Palautus päällä | Toista vastaanotettu sarjaporttidata takaisin | . | Sarjaportin tila | Portin käyttämä protokolla – Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, YE.Direct, MeshSolar config, Log tai Log (vain teksti) | . | Vastaanotto / lähetys | Sarjayhteyden GPIO-nastat | . | Sarjaportin nopeus | Portin nopeus | . | Aikakatkaisu | Kuinka kauan odotetaan ennen kuin saapuva viesti katsotaan kokonaiseksi | . | Korvaa konsolin sarjaportti | Ota käyttöön portti, jota virheenkorjauskonsoli normaalisti käyttää | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Hyödyllinen laitteille, joiden täytyy ilmoittaa fyysisesti viestin saapumisesta — erityisen hyödyllinen valvomattomissa tai ulkokäyttöön asennetuissa laitteissa. Käynnistimiä on kaksi – saapuva viesti ja vastaanotettu BEL-ohjausmerkki – ja kumpikin voi ohjata LED-valoa, summeria ja värinämoottoria erikseen, joten käytettävissä on kuusi kytkintä. | Asetus | Kuvaus | . | Ulkoiset ilmoitukset käytössä | Moduulin pääkytkin | . | Hälytysviesti: LED / summeri / värinä | Mitkä lähdöt aktivoituvat saapuvasta viestistä | . | Hälytysmerkki: LED / summeri / värinä | Mitkä lähdöt aktivoituvat vastaanotetusta BEL-ohjausmerkistä | . | Ulostulon LED (GPIO) | LED on kytketty nastaan | . | Ulostulon LED aktiivinen | Onko LED-nasta aktiivinen korkealla vai matalalla tasolla | . | Ulostulon äänimerkki (GPIO) | Summeri on kytketty nastaan | . | Ulostulon värinä (GPIO) | Värinämoottori on kytketty nastaan | . | Käytä PWM-äänimerkkiä | Ohjaa summeria PWM:llä, jolloin voidaan toistaa ääniä yhden kiinteän taajuuden sijaan | . | Käytä I2S protokollaa äänimerkille | Lähetä hälytys sen sijaan I2S-äänilähdön kautta | . | GPIO Output Duration | Kuinka kauan yksittäinen hälytys kestää | . | Toistokehotuksen aikakatkaisu | Toista hälytystä tämän ajan, kunnes se kuitataan. 0 poistaa toistuvan muistutuksen käytöstä | . | Soittoääni | PWM-summerilla toistettava RTTTL-soittoääni. Voidaan tuoda tiedostosta | . Store & Forward module . Puskuroi viestejä radioille, jotka ovat tilapäisesti poissa verkosta, ja toimittaa ne, kun nämä radiot yhdistyvät uudelleen. Välttämätön verkoissa, joissa radiot siirtyvät säännöllisesti kuuluvuusalueelle ja sen ulkopuolelle — varmistaa, etteivät viestit katoa lyhyiden yhteyskatkosten aikana. | Asetus | Kuvaus | . | Tallenna ja lähetä edelleen | Ota Varastoi & välitä käyttöön | . | Valvontasignaali | Ilmoita tämän radion varastoi & välitä -ominaisuudesta säännöllisesti | . | Kirjausten määrä | Tallennettujen viestien enimmäismäärä | . | Historian maksimimäärä | Toistettavien viestien enimmäismäärä | . | Historian aikamäärä | Aikaikkuna viestien toistolle | . | Palvelin | Toimi mesh-verkon varastoi & välitä -palvelimena (edellyttää riittävästi muistia, esimerkiksi ESP32 PSRAM:lla) | . 💡 Vinkki: Varastoi & välitä toimii parhaiten radioissa, joissa on runsaasti muistia (ESP32 ja PSRAM). Router-roolin radiot ovat ihanteellisia ehdokkaita, koska ne ovat yleensä jatkuvasti käynnissä. Range Test module . ⚠️ Varoitus: Kuuluvuustesti toimii vain suojatulla ensisijaisella kanavalla. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automaattinen kuuluvuustestityökalu radioiden välisen yhteyden laadun arviointiin. Kun toiminto on käytössä, radio lähettää säännöllisesti testiviestejä kasvavilla laskuriarvoilla. Vastaanottava radio kirjaa nämä viestit, jolloin voit myöhemmin kävellä tai ajaa pois ja analysoida, millä etäisyydellä viestien saapuminen loppui. | Asetus | Kuvaus | . | Kuuluvuustesti käytössä | Ota kuuluvuustesti käyttöön | . | Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Tallenna .CSV (ESP32 ainoastaan) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Määrittää, mitä telemetriatietoja radiosi jakaa verkkoon. Telemetria sisältää laitteen kuntoon liittyviä tietoja (akun varaustaso, käyttöaika) sekä ympäristöanturien tietoja (lämpötila, kosteus, ilmanpaine). Jokaisella neljällä mittausryhmällä on oma käyttöönottokytkin ja oma mittausväli, joten esimerkiksi akun tila voidaan raportoida usein ja anturitiedot harvemmin. | Asetus | Kuvaus | . | Lähetä laitteen telemetriatiedot | Laitemittausten pääkytkin. Näkyy vain laiteohjelmistoversiossa 2.7.12 ja uudemmissa | . | Laitemittareiden päivitysväli | How often to report battery, uptime and channel utilization | . | Ympäristötietojen moduuli käytössä | Raportoi liitettyjen ympäristöanturien tiedot | . | Ympäristömittareiden päivitysväli | Kuinka usein tiedot raportoidaan | . | Näytä ympäristötiedot näytöllä | Näytä nämä tiedot myös radion omalla näytöllä | . | Käytä Fahrenheit yksikköä | Käytä radion näytössä Fahrenheit-asteita. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Ilmanlaadun tietojen moduuli käytössä | Raportoi hiukkas- ja CO₂-anturin tiedot | . | Ilmanlaatumittareiden päivitysväli | Kuinka usein tiedot raportoidaan | . | Virrankulutuksen moduuli käytössä | Raportoi kanavakohtaiset jännite- ja virtamittaukset | . | Virtamittareiden päivitysväli | Kuinka usein tiedot raportoidaan | . | Virrankulutuksen näyttö käytössä | Näytä virtamittaukset myös radion omalla näytöllä | . Katso Telemetria ja anturit saadaksesi tietoa tuetuista antureista ja määrityssuosituksista. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Määritä luettelo pikaviesteistä, jotka voidaan lähettää ilman yhdistettyä puhelinta — ihanteellinen kenttäkäyttöön. | Asetus | Kuvaus | . | Valmisviesti käytössä | ⚠️ Vanhentunut protobuf-rakenteessa | . | Viestit | Rivinvaihdoilla eroteltu viestiluettelo | . | Lähetä äänimerkki | Lähetä viestin mukana BEL-ohjausmerkki, jotta vastaanottavan radion Ulkoiset ilmoitukset -moduuli voi antaa hälytyksen | . | Kiertovalitsin #1 käytössä | Käytä kiertokoodainta syöttölaitteena | . | GPIO pin for rotary encoder A / B / Press port | Kolme nastaa, joihin kiertokoodain on kytketty | . | Generate input event on Press / CW / CCW | Minkä näppäintapahtuman kukin kiertokoodaimen toiminto tuottaa | . | Ylös/Alas/Valitse syöte käytössä | Erillinen, yksinkertaisempi syöttötapa, jossa käytetään ylös-/alas-/valitse-painikkeita kiertokoodaimen sijaan | . | Salli syöttölähde | ⚠️ Vanhentunut protobuf-rakenteessa | . Audio module . Codec2-äänituki matalan kaistanleveyden puheviestintään verkossa. Tämä on kokeellinen ominaisuus, joka koodaa puheen erittäin pieniksi datapaketeiksi käyttäen Codec2-koodekkia. | Asetus | Kuvaus | . | CODEC 2 käytössä | Ota äänimoduuli käyttöön | . | CODEC2 näytteenottotaajuus | Äänenlaadun ja kaistanleveyden välinen kompromissi | . | PTT-pinni | PTT-painikkeen GPIO-nasta | . | I2S-sanan valinta | GPIO-pinni I2S WS:lle | . | I2S-datatulo | GPIO-nasta I2S DIN:lle | . | I2S-datalähtö | GPIO-pinni I2S DOUT:lle | . | I2S-kello | I2S-bittikellon GPIO-nasta | . ℹ️ Huomautus: Ääniominaisuus edellyttää yhteensopivaa laitteistoa (I2S-mikrofoni ja -kaiutin). Äänenlaatu on hyvin matalakaistainen — ajattele “ymmärrettävää radiopuhetta”, ei puhelinlaatua. Remote Hardware module . GPIO-ohjaus mesh-verkon kautta. Mahdollistaa etäradion lukea tai kirjoittaa GPIO-nastoja toisessa radiossa — hyödyllinen releiden aktivointiin, kytkimien lukemiseen tai ulkoisen laitteiston ohjaamiseen etäältä. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Asetus | Kuvaus | . | Etälaitteen ohjaus käytössä | Ota etä-GPIO-käyttö käyttöön | . | Salli määrittämättömän pinnin käyttö | Salli pääsy mihin tahansa GPIO-nastaan (tietoturvariski) | . | Käytettävissä olevat pinnit | Enintään 4 tämän radion etälukuun tai kirjoitukseen tarjoamaa GPIO-pinniä | . Neighbor Info module . Lähettää tietoa suoraan kuulluista naapureista mahdollistaen verkon topologian kartoituksen. Jokainen käyttöön otettu radio jakaa säännöllisesti luettelon muista radioista, jotka se kuulee, sekä niiden signaalin laadun. | Asetus | Kuvaus | . | Naapuritiedot käytössä | Ota naapuritiedon lähetys käyttöön | . | GPS-kyselyn aikaväli | Kuinka usein naapuriluettelo lähetetään | . | Lähetä LoRa:n kautta | Lähetä myös naapuritiedot LoRa:n kautta, ei pelkästään MQTT:n tai puhelimen kautta. Ei käytettävissä kanavalla, joka käyttää oletusavainta ja nimeä | . Katso Paikallinen mesh-haku, miten naapuritietoja käytetään mesh-verkon rakenteen tutkimiseen. Ambient Lighting module . Ohjaa tuetuissa laitteissa olevaa NeoPixeliä tai muita osoitteellisia RGB-LEDejä. Voidaan käyttää visuaalisina tilailmaisimina, ilmoitusvaloina tai koriste-efekteinä. | Asetus | Kuvaus | . | LED-tila | Kytke LED päälle tai pois päältä | . | Virta | LED-virran rajoitus (0–31) | . | Punainen / vihreä / sininen | Yksittäisten värikanavien arvot (0–255) | . Detection Sensor module . Muuttaa radiosi liike- tai ovitunnistimeen perustuvaksi hälytysjärjestelmäksi. Kun GPIO-pinni havaitsee tilamuutoksen (liike havaittu, ovi avattu), radio lähettää hälytysviestin verkkoon. | Asetus | Kuvaus | . | Tunnistinsensori käytössä | Ota tunnistusanturi käyttöön | . | GPIO-pinni valvontaa varten | Anturiin kytketty GPIO-pinni | . | Tunnistuksen tyyppi | Miten pinnin tila vastaa havaitsemistapahtumaa (esim. aktiivinen korkea/matala taso tai reunalaukaisu) | . | Käytä INPUT_PULLUP tilaa | Ota pinnin sisäinen ylösvetovastus käyttöön | . | Minimum time between detection broadcasts | Hälytyslähetysten vähimmäisaika | . | State Broadcast Interval | Tilatiedon lähetysväli | . | Lähetä äänimerkki hälytyssanoman kanssa | Sisällytä soittomerkkimerkki hälytyksiin | . | Käyttäjäystävällinen nimi | Tälle anturille määritetty nimi | . Paxcounter module . Henkilöt, jotka lasketaan WiFi- ja BLE-hakukyselyiden perusteella. Laskee lähellä olevia laitteita kuuntelemalla passiivisesti koepyyntöjä, joita puhelimet ja kannettavat tietokoneet lähettävät etsiessään verkkoja. Saatavilla vain ESP32-laitteissa. | Asetus | Kuvaus | . | PAX-laskuri käytössä | Ota henkilölaskenta käyttöön | . | GPS-kyselyn aikaväli | Kuinka usein laskentatiedot raportoidaan | . | WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE Threshold (dBm) | Sama raja-arvo BLE-mainospaketeille (oletus: -80 dBm) | . 💡 Vinkki: PAX-laskuri on hyödyllinen jalankulkijamäärien arviointiin retkeilyreittien lähtöpisteissä, tapahtumapaikoilla tai muissa kohteissa. Laskentatulokset ovat arvioita — yhdellä henkilöllä voi olla useita laitteita mukana. Status Message module . Tilaviestillä ei ole omaa moduulinäkymää. Sitä muokataan yhdessä muiden radion tunnistetietojen kanssa kohdassa Asetukset → Radio ja käyttäjä. Mesh Beacon module . Lähettää kutsun mesh-verkkoosi ja vastaanottaa muiden lähettämiä kutsuja. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit -integraatio yhteensopivuutta varten ATAK- ja WinTAK-järjestelmien kanssa. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. Katso TAK-integraatio saadaksesi tarkemmat määritys- ja käyttöohjeet. ", "url": "/Meshtastic-Android/main/fi-rFI/user/settings-module-admin.html#moduulin-asetukset", "relUrl": "/fi-rFI/user/settings-module-admin.html#moduulin-asetukset" @@ -30395,7 +30395,7 @@ },"4342": { "doc": "Settings — Modules & Admin", "title": "Stillingar aukaeininga", - "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Lýsing | . | MQTT enabled | Toggle MQTT bridge | . | Address | MQTT broker address | . | Username | Authentication username | . | Password | Authentication password | . | Encryption enabled | Encrypt MQTT payloads | . | JSON output enabled | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS enabled | Use secure connection | . | Root topic | Base MQTT topic path | . | Proxy to client enabled | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Map reporting | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Lýsing | . | I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Map reporting interval (seconds) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Lýsing | . | Serial enabled | Activate serial communication | . | Echo enabled | Echo received serial data back | . | Serial mode | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Serial baud rate | Port speed | . | Timeout | How long to wait before considering an incoming message complete | . | Override console serial port | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Lýsing | . | External notification enabled | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Output LED (GPIO) | Pin the LED is wired to | . | Output LED active high | Whether the LED pin is active high or low | . | Output buzzer (GPIO) | Pin the buzzer is wired to | . | Output vibra (GPIO) | Pin the vibration motor is wired to | . | Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Use I2S as buzzer | Send the alert through an I2S audio output instead | . | Output duration (milliseconds) | How long a single alert lasts | . | Nag timeout (seconds) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Lýsing | . | Store & Forward enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | Number of records | Maximum stored messages | . | History return max | Max messages to replay | . | History return window | Time window for replay | . | Server | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Lýsing | . | Range test enabled | Activate range testing | . | Sender message interval (seconds) | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Save .CSV in storage (ESP32 only) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Lýsing | . | Send Device Telemetry | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Device metrics update interval | How often to report battery, uptime and channel utilization | . | Environment metrics module enabled | Report the attached environment sensors | . | Environment metrics update interval | How often to report them | . | Environment metrics on-screen enabled | Also show these readings on the device’s own display | . | Environment metrics use Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Air quality metrics module enabled | Report particulate and CO₂ sensor data | . | Air quality metrics update interval | How often to report them | . | Power metrics module enabled | Report the per-channel voltage and current readings | . | Power metrics update interval | How often to report them | . | Power metrics on-screen enabled | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Lýsing | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Messages | Newline-separated list of messages | . | Send bell | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Rotary encoder #1 enabled | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Up/Down/Select input enabled | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Lýsing | . | CODEC 2 enabled | Activate audio module | . | CODEC2 sample rate | Audio quality/bandwidth tradeoff | . | PTT pin | GPIO pin for the push-to-talk button | . | I2S word select | GPIO pin for I2S WS | . | I2S data in | GPIO pin for I2S DIN | . | I2S data out | GPIO pin for I2S DOUT | . | I2S clock | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Lýsing | . | Remote Hardware enabled | Activate remote GPIO access | . | Allow undefined pin access | Allow access to any GPIO pin (security risk) | . | Available pins | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Lýsing | . | Neighbor Info enabled | Activate neighbor broadcasting | . | Update interval (seconds) | How often to broadcast neighbor list | . | Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Lýsing | . | LED state | Turn the LED on or off | . | Current | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Lýsing | . | Detection Sensor enabled | Activate detection sensor | . | GPIO pin to monitor | GPIO pin connected to sensor | . | Detection trigger type | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Use INPUT_PULLUP mode | Enable the pin’s internal pull-up resistor | . | Minimum broadcast (seconds) | Minimum time between alert broadcasts | . | State broadcast (seconds) | Periodic state broadcast interval | . | Send bell with alert message | Include bell character in alerts | . | Friendly name | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Lýsing | . | Paxcounter enabled | Activate people counting | . | Update interval (seconds) | How often to report counts | . | Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ", + "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Lýsing | . | MQTT enabled | Toggle MQTT bridge | . | Address | MQTT broker address | . | Username | Authentication username | . | Password | Authentication password | . | Encryption enabled | Encrypt MQTT payloads | . | JSON output enabled | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS enabled | Use secure connection | . | Root topic | Base MQTT topic path | . | Proxy to client enabled | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Map reporting | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Lýsing | . | I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Lýsing | . | Serial enabled | Activate serial communication | . | Echo enabled | Echo received serial data back | . | Serial mode | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Serial baud rate | Port speed | . | Timeout | How long to wait before considering an incoming message complete | . | Override console serial port | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Lýsing | . | External notification enabled | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Output LED (GPIO) | Pin the LED is wired to | . | Output LED active high | Whether the LED pin is active high or low | . | Output buzzer (GPIO) | Pin the buzzer is wired to | . | Output vibra (GPIO) | Pin the vibration motor is wired to | . | Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Use I2S as buzzer | Send the alert through an I2S audio output instead | . | GPIO Output Duration | How long a single alert lasts | . | Nag Timeout | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Lýsing | . | Store & Forward enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | Number of records | Maximum stored messages | . | History return max | Max messages to replay | . | History return window | Time window for replay | . | Server | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Lýsing | . | Range test enabled | Activate range testing | . | Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Save .CSV in storage (ESP32 only) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Lýsing | . | Send Device Telemetry | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Device metrics update interval | How often to report battery, uptime and channel utilization | . | Environment metrics module enabled | Report the attached environment sensors | . | Environment metrics update interval | How often to report them | . | Environment metrics on-screen enabled | Also show these readings on the device’s own display | . | Environment metrics use Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Air quality metrics module enabled | Report particulate and CO₂ sensor data | . | Air quality metrics update interval | How often to report them | . | Power metrics module enabled | Report the per-channel voltage and current readings | . | Power metrics update interval | How often to report them | . | Power metrics on-screen enabled | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Lýsing | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Messages | Newline-separated list of messages | . | Send bell | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Rotary encoder #1 enabled | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Up/Down/Select input enabled | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Lýsing | . | CODEC 2 enabled | Activate audio module | . | CODEC2 sample rate | Audio quality/bandwidth tradeoff | . | PTT pin | GPIO pin for the push-to-talk button | . | I2S word select | GPIO pin for I2S WS | . | I2S data in | GPIO pin for I2S DIN | . | I2S data out | GPIO pin for I2S DOUT | . | I2S clock | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Lýsing | . | Remote Hardware enabled | Activate remote GPIO access | . | Allow undefined pin access | Allow access to any GPIO pin (security risk) | . | Available pins | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Lýsing | . | Neighbor Info enabled | Activate neighbor broadcasting | . | Update Interval | How often to broadcast neighbor list | . | Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Lýsing | . | LED state | Turn the LED on or off | . | Current | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Lýsing | . | Detection Sensor enabled | Activate detection sensor | . | GPIO pin to monitor | GPIO pin connected to sensor | . | Detection trigger type | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Use INPUT_PULLUP mode | Enable the pin’s internal pull-up resistor | . | Minimum time between detection broadcasts | Minimum time between alert broadcasts | . | State Broadcast Interval | Periodic state broadcast interval | . | Send bell with alert message | Include bell character in alerts | . | Friendly name | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Lýsing | . | Paxcounter enabled | Activate people counting | . | Update Interval | How often to report counts | . | WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ", "url": "/Meshtastic-Android/main/is-rIS/user/settings-module-admin.html#stillingar-aukaeininga", "relUrl": "/is-rIS/user/settings-module-admin.html#stillingar-aukaeininga" @@ -30430,7 +30430,7 @@ },"4347": { "doc": "Settings — Modules & Admin", "title": "Modulio konfigūracija", - "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Aprašymas | . | MQTT enabled | Toggle MQTT bridge | . | Address | MQTT broker address | . | Username | Authentication username | . | Password | Authentication password | . | Encryption enabled | Encrypt MQTT payloads | . | JSON output enabled | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS enabled | Use secure connection | . | Root topic | Base MQTT topic path | . | Proxy to client enabled | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Map reporting | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Aprašymas | . | I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Map reporting interval (seconds) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Aprašymas | . | Serial enabled | Activate serial communication | . | Echo enabled | Echo received serial data back | . | Serial mode | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Serial baud rate | Port speed | . | Baigėsi laikas | How long to wait before considering an incoming message complete | . | Override console serial port | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Aprašymas | . | External notification enabled | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Output LED (GPIO) | Pin the LED is wired to | . | Output LED active high | Whether the LED pin is active high or low | . | Output buzzer (GPIO) | Pin the buzzer is wired to | . | Output vibra (GPIO) | Pin the vibration motor is wired to | . | Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Use I2S as buzzer | Send the alert through an I2S audio output instead | . | Output duration (milliseconds) | How long a single alert lasts | . | Nag timeout (seconds) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Aprašymas | . | Store & Forward enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | Number of records | Maximum stored messages | . | History return max | Max messages to replay | . | History return window | Time window for replay | . | Server | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Aprašymas | . | Range test enabled | Activate range testing | . | Sender message interval (seconds) | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Save .CSV in storage (ESP32 only) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Aprašymas | . | Send Device Telemetry | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Device metrics update interval | How often to report battery, uptime and channel utilization | . | Environment metrics module enabled | Report the attached environment sensors | . | Environment metrics update interval | How often to report them | . | Environment metrics on-screen enabled | Also show these readings on the device’s own display | . | Environment metrics use Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Air quality metrics module enabled | Report particulate and CO₂ sensor data | . | Air quality metrics update interval | How often to report them | . | Power metrics module enabled | Report the per-channel voltage and current readings | . | Power metrics update interval | How often to report them | . | Power metrics on-screen enabled | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Aprašymas | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Messages | Newline-separated list of messages | . | Send bell | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Rotary encoder #1 enabled | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Up/Down/Select input enabled | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Aprašymas | . | CODEC 2 enabled | Activate audio module | . | CODEC2 sample rate | Audio quality/bandwidth tradeoff | . | PTT pin | GPIO pin for the push-to-talk button | . | I2S word select | GPIO pin for I2S WS | . | I2S data in | GPIO pin for I2S DIN | . | I2S data out | GPIO pin for I2S DOUT | . | I2S clock | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Aprašymas | . | Remote Hardware enabled | Activate remote GPIO access | . | Allow undefined pin access | Allow access to any GPIO pin (security risk) | . | Available pins | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Aprašymas | . | Neighbor Info enabled | Activate neighbor broadcasting | . | Update interval (seconds) | How often to broadcast neighbor list | . | Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Aprašymas | . | LED state | Turn the LED on or off | . | Current | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Aprašymas | . | Detection Sensor enabled | Activate detection sensor | . | GPIO pin to monitor | GPIO pin connected to sensor | . | Detection trigger type | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Use INPUT_PULLUP mode | Enable the pin’s internal pull-up resistor | . | Minimum broadcast (seconds) | Minimum time between alert broadcasts | . | State broadcast (seconds) | Periodic state broadcast interval | . | Send bell with alert message | Include bell character in alerts | . | Friendly name | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Aprašymas | . | Paxcounter enabled | Activate people counting | . | Update interval (seconds) | How often to report counts | . | Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ", + "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Aprašymas | . | MQTT enabled | Toggle MQTT bridge | . | Address | MQTT broker address | . | Username | Authentication username | . | Password | Authentication password | . | Encryption enabled | Encrypt MQTT payloads | . | JSON output enabled | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS enabled | Use secure connection | . | Root topic | Base MQTT topic path | . | Proxy to client enabled | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Map reporting | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Aprašymas | . | I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Aprašymas | . | Serial enabled | Activate serial communication | . | Echo enabled | Echo received serial data back | . | Serial mode | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Serial baud rate | Port speed | . | Baigėsi laikas | How long to wait before considering an incoming message complete | . | Override console serial port | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Aprašymas | . | External notification enabled | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Output LED (GPIO) | Pin the LED is wired to | . | Output LED active high | Whether the LED pin is active high or low | . | Output buzzer (GPIO) | Pin the buzzer is wired to | . | Output vibra (GPIO) | Pin the vibration motor is wired to | . | Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Use I2S as buzzer | Send the alert through an I2S audio output instead | . | GPIO Output Duration | How long a single alert lasts | . | Nag Timeout | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Aprašymas | . | Store & Forward enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | Number of records | Maximum stored messages | . | History return max | Max messages to replay | . | History return window | Time window for replay | . | Server | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Aprašymas | . | Range test enabled | Activate range testing | . | Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Save .CSV in storage (ESP32 only) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Aprašymas | . | Send Device Telemetry | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Device metrics update interval | How often to report battery, uptime and channel utilization | . | Environment metrics module enabled | Report the attached environment sensors | . | Environment metrics update interval | How often to report them | . | Environment metrics on-screen enabled | Also show these readings on the device’s own display | . | Environment metrics use Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Air quality metrics module enabled | Report particulate and CO₂ sensor data | . | Air quality metrics update interval | How often to report them | . | Power metrics module enabled | Report the per-channel voltage and current readings | . | Power metrics update interval | How often to report them | . | Power metrics on-screen enabled | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Aprašymas | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Messages | Newline-separated list of messages | . | Send bell | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Rotary encoder #1 enabled | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Up/Down/Select input enabled | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Aprašymas | . | CODEC 2 enabled | Activate audio module | . | CODEC2 sample rate | Audio quality/bandwidth tradeoff | . | PTT pin | GPIO pin for the push-to-talk button | . | I2S word select | GPIO pin for I2S WS | . | I2S data in | GPIO pin for I2S DIN | . | I2S data out | GPIO pin for I2S DOUT | . | I2S clock | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Aprašymas | . | Remote Hardware enabled | Activate remote GPIO access | . | Allow undefined pin access | Allow access to any GPIO pin (security risk) | . | Available pins | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Aprašymas | . | Neighbor Info enabled | Activate neighbor broadcasting | . | Update Interval | How often to broadcast neighbor list | . | Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Aprašymas | . | LED state | Turn the LED on or off | . | Current | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Aprašymas | . | Detection Sensor enabled | Activate detection sensor | . | GPIO pin to monitor | GPIO pin connected to sensor | . | Detection trigger type | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Use INPUT_PULLUP mode | Enable the pin’s internal pull-up resistor | . | Minimum time between detection broadcasts | Minimum time between alert broadcasts | . | State Broadcast Interval | Periodic state broadcast interval | . | Send bell with alert message | Include bell character in alerts | . | Friendly name | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Aprašymas | . | Paxcounter enabled | Activate people counting | . | Update Interval | How often to report counts | . | WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ", "url": "/Meshtastic-Android/main/lt-rLT/user/settings-module-admin.html#modulio-konfig%C5%ABracija", "relUrl": "/lt-rLT/user/settings-module-admin.html#modulio-konfigūracija" @@ -30465,7 +30465,7 @@ },"4352": { "doc": "Settings — Modules & Admin", "title": "Configuración de módulo", - "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Descrición | . | MQTT enabled | Toggle MQTT bridge | . | Address | MQTT broker address | . | Username | Authentication username | . | Password | Authentication password | . | Encryption enabled | Encrypt MQTT payloads | . | JSON output enabled | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS enabled | Use secure connection | . | Root topic | Base MQTT topic path | . | Proxy to client enabled | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Map reporting | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Descrición | . | I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Map reporting interval (seconds) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Descrición | . | Serial enabled | Activate serial communication | . | Echo enabled | Echo received serial data back | . | Serial mode | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Serial baud rate | Port speed | . | Timeout | How long to wait before considering an incoming message complete | . | Override console serial port | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Descrición | . | External notification enabled | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Output LED (GPIO) | Pin the LED is wired to | . | Output LED active high | Whether the LED pin is active high or low | . | Output buzzer (GPIO) | Pin the buzzer is wired to | . | Output vibra (GPIO) | Pin the vibration motor is wired to | . | Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Use I2S as buzzer | Send the alert through an I2S audio output instead | . | Output duration (milliseconds) | How long a single alert lasts | . | Nag timeout (seconds) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Descrición | . | Store & Forward enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | Number of records | Maximum stored messages | . | History return max | Max messages to replay | . | History return window | Time window for replay | . | Server | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Descrición | . | Range test enabled | Activate range testing | . | Sender message interval (seconds) | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Save .CSV in storage (ESP32 only) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Descrición | . | Send Device Telemetry | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Device metrics update interval | How often to report battery, uptime and channel utilization | . | Environment metrics module enabled | Report the attached environment sensors | . | Environment metrics update interval | How often to report them | . | Environment metrics on-screen enabled | Also show these readings on the device’s own display | . | Environment metrics use Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Air quality metrics module enabled | Report particulate and CO₂ sensor data | . | Air quality metrics update interval | How often to report them | . | Power metrics module enabled | Report the per-channel voltage and current readings | . | Power metrics update interval | How often to report them | . | Power metrics on-screen enabled | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Descrición | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Messages | Newline-separated list of messages | . | Send bell | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Rotary encoder #1 enabled | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Up/Down/Select input enabled | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Descrición | . | CODEC 2 enabled | Activate audio module | . | CODEC2 sample rate | Audio quality/bandwidth tradeoff | . | PTT pin | GPIO pin for the push-to-talk button | . | I2S word select | GPIO pin for I2S WS | . | I2S data in | GPIO pin for I2S DIN | . | I2S data out | GPIO pin for I2S DOUT | . | I2S clock | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Descrición | . | Remote Hardware enabled | Activate remote GPIO access | . | Allow undefined pin access | Allow access to any GPIO pin (security risk) | . | Available pins | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Descrición | . | Neighbor Info enabled | Activate neighbor broadcasting | . | Update interval (seconds) | How often to broadcast neighbor list | . | Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Descrición | . | LED state | Turn the LED on or off | . | Current | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Descrición | . | Detection Sensor enabled | Activate detection sensor | . | GPIO pin to monitor | GPIO pin connected to sensor | . | Detection trigger type | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Use INPUT_PULLUP mode | Enable the pin’s internal pull-up resistor | . | Minimum broadcast (seconds) | Minimum time between alert broadcasts | . | State broadcast (seconds) | Periodic state broadcast interval | . | Send bell with alert message | Include bell character in alerts | . | Friendly name | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Descrición | . | Paxcounter enabled | Activate people counting | . | Update interval (seconds) | How often to report counts | . | Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ", + "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Descrición | . | MQTT enabled | Toggle MQTT bridge | . | Address | MQTT broker address | . | Username | Authentication username | . | Password | Authentication password | . | Encryption enabled | Encrypt MQTT payloads | . | JSON output enabled | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS enabled | Use secure connection | . | Root topic | Base MQTT topic path | . | Proxy to client enabled | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Map reporting | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Descrición | . | I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Descrición | . | Serial enabled | Activate serial communication | . | Echo enabled | Echo received serial data back | . | Serial mode | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Serial baud rate | Port speed | . | Timeout | How long to wait before considering an incoming message complete | . | Override console serial port | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Descrición | . | External notification enabled | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Output LED (GPIO) | Pin the LED is wired to | . | Output LED active high | Whether the LED pin is active high or low | . | Output buzzer (GPIO) | Pin the buzzer is wired to | . | Output vibra (GPIO) | Pin the vibration motor is wired to | . | Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Use I2S as buzzer | Send the alert through an I2S audio output instead | . | GPIO Output Duration | How long a single alert lasts | . | Nag Timeout | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Descrición | . | Store & Forward enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | Number of records | Maximum stored messages | . | History return max | Max messages to replay | . | History return window | Time window for replay | . | Server | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Descrición | . | Range test enabled | Activate range testing | . | Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Save .CSV in storage (ESP32 only) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Descrición | . | Send Device Telemetry | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Device metrics update interval | How often to report battery, uptime and channel utilization | . | Environment metrics module enabled | Report the attached environment sensors | . | Environment metrics update interval | How often to report them | . | Environment metrics on-screen enabled | Also show these readings on the device’s own display | . | Environment metrics use Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Air quality metrics module enabled | Report particulate and CO₂ sensor data | . | Air quality metrics update interval | How often to report them | . | Power metrics module enabled | Report the per-channel voltage and current readings | . | Power metrics update interval | How often to report them | . | Power metrics on-screen enabled | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Descrición | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Messages | Newline-separated list of messages | . | Send bell | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Rotary encoder #1 enabled | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Up/Down/Select input enabled | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Descrición | . | CODEC 2 enabled | Activate audio module | . | CODEC2 sample rate | Audio quality/bandwidth tradeoff | . | PTT pin | GPIO pin for the push-to-talk button | . | I2S word select | GPIO pin for I2S WS | . | I2S data in | GPIO pin for I2S DIN | . | I2S data out | GPIO pin for I2S DOUT | . | I2S clock | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Descrición | . | Remote Hardware enabled | Activate remote GPIO access | . | Allow undefined pin access | Allow access to any GPIO pin (security risk) | . | Available pins | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Descrición | . | Neighbor Info enabled | Activate neighbor broadcasting | . | Update Interval | How often to broadcast neighbor list | . | Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Descrición | . | LED state | Turn the LED on or off | . | Current | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Descrición | . | Detection Sensor enabled | Activate detection sensor | . | GPIO pin to monitor | GPIO pin connected to sensor | . | Detection trigger type | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Use INPUT_PULLUP mode | Enable the pin’s internal pull-up resistor | . | Minimum time between detection broadcasts | Minimum time between alert broadcasts | . | State Broadcast Interval | Periodic state broadcast interval | . | Send bell with alert message | Include bell character in alerts | . | Friendly name | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Descrición | . | Paxcounter enabled | Activate people counting | . | Update Interval | How often to report counts | . | WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ", "url": "/Meshtastic-Android/main/gl-rES/user/settings-module-admin.html#configuraci%C3%B3n-de-m%C3%B3dulo", "relUrl": "/gl-rES/user/settings-module-admin.html#configuración-de-módulo" @@ -30500,7 +30500,7 @@ },"4357": { "doc": "設定：モジュールと管理", "title": "追加機能の設定", - "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . インターネット接続のために、メッシュのメッセージを MQTT サーバーとの間で橋渡しします。 This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | 設定項目 | 説明 | . | MQTTを有効化 | MQTT ブリッジを切り替え | . | アドレス | MQTT サーバーのアドレス | . | ユーザー名 | 認証用のユーザー名 | . | パスワード | 認証用のパスワード | . | 暗号化の有効化 | MQTT ペイロードを暗号化 | . | JSON出力の有効化 | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS の有効化 | セキュアな接続を使用 | . | ルート トピック | MQTT のベーストピックパス | . | クライアントへのプロキシの有効化 | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | このスマートフォンの MQTT プロキシ | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | マップレポート | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | 設定項目 | 説明 | . | 同意します。 | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | マップレポートの間隔 (秒) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . 暗号化、プライバシー、サーバーの設定を含む詳しい使い方は、MQTT を参照してください。 . Serial module . 外部デバイスとの連携（GPS モジュール、センサー、カスタムハードウェア）のために、シリアルポート通信を有効にします。有効にすると、ノードのシリアルポートで protobuf またはテキストデータを送受信でき、外部のマイコンやコンピューターがメッシュとやり取りできるようになります。 . | 設定項目 | 説明 | . | シリアル通信を有効化 | シリアル通信を有効化 | . | Echoを有効化 | 受信したシリアルデータをそのまま返す | . | シリアルモード | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | シリアルボーレイト | Port speed | . | タイムアウト | How long to wait before considering an incoming message complete | . | コンソールのシリアルポートを上書き | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. メッセージ到着時に物理的に知らせる必要があるデバイスに便利です。特に無人設置や屋外設置で役立ちます。 . There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | 設定項目 | 説明 | . | 外部通知を有効化 | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | LED出力 (GPIO) | Pin the LED is wired to | . | LED出力 アクティブハイ | Whether the LED pin is active high or low | . | ブザー出力(GPIO) | Pin the buzzer is wired to | . | バイブレーション出力 (GPIO) | Pin the vibration motor is wired to | . | PWMブザーを使用 | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | I2Sをブザーとして使用 | Send the alert through an I2S audio output instead | . | 出力時間 (ミリ秒) | How long a single alert lasts | . | 繰り返し通知間隔（秒） | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | 着信音 | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . 一時的にオフラインだったノードのためにメッセージをバッファリングし、それらのノードが再接続したときに再送します。ノードが頻繁に圏内・圏外を行き来するメッシュに不可欠です。短時間の切断中にメッセージが失われないようにします。 . | 設定項目 | 説明 | . | 一時保管と転送の有効化 | ストア＆フォワードを有効化 | . | ハートビート | このノードのストア＆フォワード機能を定期的に告知する | . | サーバーの最大保管レコード数 (デフォルト 約11,000レコード) | 保存するメッセージの最大数 | . | リクエスト可能な最大の履歴件数 | 再送するメッセージの最大数 | . | リクエスト可能な履歴の期間 (分) | 再送する時間の範囲 | . | サーバー | メッシュのストア＆フォワードサーバーとして動作する（十分なメモリが必要、例：PSRAM 搭載の ESP32） | . 💡 ヒント： ストア＆フォワードは、十分なメモリを持つノード（PSRAM 搭載の ESP32）で最も良く機能します。ルーターノードは通常は常時起動しているため、理想的な候補です。 . Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. ノード間のリンク品質を評価するための、自動レンジテストツールです。有効にすると、ノードはカウンターを増やしながらテストメッセージを定期的に送信します。受信側のノードがこれらのメッセージを記録するため、歩いたり車で移動したりして、後からどの距離でメッセージが届かなくなったかを分析できます。 . | 設定項目 | 説明 | . | レンジテストを有効化 | レンジテストを有効化 | . | 送信者のメッセージ間隔 (秒) | Time between test transmissions, chosen from a dropdown of fixed intervals | . | ストレージにCSVファイルを保存(ESP32のみ) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . ノードがメッシュと共有するテレメトリデータを制御します。テレメトリには、デバイスの状態（バッテリー、連続稼働時間）と環境センサーのデータ（温度、湿度、気圧）が含まれます。 . Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | 設定項目 | 説明 | . | デバイステレメトリを送信 | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | デバイスメトリクスの更新間隔 | How often to report battery, uptime and channel utilization | . | 環境メトリクスモジュールを有効化 | Report the attached environment sensors | . | 環境メトリクスの更新間隔 | How often to report them | . | 環境メトリクスを画面上で有効化 | Also show these readings on the device’s own display | . | 環境メトリクスは華氏を使用 | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | 空気品質測定モジュールを有効化 | Report particulate and CO₂ sensor data | . | 空気品質メトリクスの更新間隔 | How often to report them | . | 電源メトリクスモジュール有効 | Report the per-channel voltage and current readings | . | 電源メトリクスの更新間隔 | How often to report them | . | 電源メトリクスを画面上で有効化 | Also show power readings on the device’s display | . 対応センサーと設定の推奨事項については、テレメトリとセンサー を参照してください。 . Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). スマートフォンを接続していなくても送信できる、クイック送信メッセージのリストを定義します。フィールドでの使用に最適です。 . | 設定項目 | 説明 | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | メッセージ | 改行で区切ったメッセージのリスト | . | ベルを送信 | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | ロータリーエンコーダ #1 を有効化 | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | 上下/選択入力を有効化 | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . メッシュ上での低帯域幅の音声通信のための、Codec2 音声サポートです。これは、Codec2 コーデックを使って音声を非常に小さなデータパケットにエンコードする、実験的な機能です。 . | 設定項目 | 説明 | . | CODEC 2 を有効化 | オーディオモジュールを有効化 | . | CODEC2 サンプルレート | 音質と帯域幅のトレードオフ | . | PTT端子 | GPIO pin for the push-to-talk button | . | I2S ワードセレクト | I2S WS 用の GPIO ピン | . | I2S データ IN | I2S DIN 用の GPIO ピン | . | I2S データ OUT | I2S DOUT 用の GPIO ピン | . | I2S クロック | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). 音質は非常に低帯域です。「聞き取れる無線の声」程度で、電話並みの品質ではないと考えてください。 . Remote Hardware module . メッシュネットワーク経由での GPIO 制御です。リモートのノードが、別のノードの GPIO ピンを読み書きできるようにします。リレーの作動、スイッチの読み取り、離れた場所からの外部ハードウェア制御に便利です。 . ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | 設定項目 | 説明 | . | リモートハードウェアを有効化 | リモート GPIO アクセスを有効化 | . | 未定義のピンへのアクセスを許可 | 任意の GPIO ピンへのアクセスを許可（セキュリティリスク） | . | 使用可能な端子 | このノードがリモートの読み書き用に公開する GPIO ピン（最大 4 個） | . Neighbor Info module . 直接受信した隣接ノードの情報をブロードキャストし、メッシュのトポロジーマッピングを可能にします。有効にした各ノードは、受信できる他のノードとその信号品質のリストを定期的に共有します。 . | 設定項目 | 説明 | . | 近隣ノード情報を有効化 | 隣接ノードのブロードキャストを有効化 | . | 更新間隔 (秒) | 隣接ノードのリストをブロードキャストする頻度 | . | LoRaで送信 | MQTT／スマートフォンだけでなく、LoRa 経由でも隣接ノード情報をブロードキャストします。デフォルトの鍵と名前を使用しているチャンネルでは利用できません | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . 対応ハードウェア上の、オンボードの NeoPixel やその他のアドレサブル RGB LED を制御します。視覚的なステータス表示、通知ライト、装飾的な演出に使用できます。 . | 設定項目 | 説明 | . | LEDの状態 | LED のオン／オフを切り替え | . | 電流 | LED の電流制限（0〜31） | . | 赤／緑／青 | 各色チャンネルの値（0〜255） | . Detection Sensor module . ノードを、動きやドアを検知するセンサーアラートシステムに変えます。 GPIO ピンが状態の変化（動きの検知、ドアの開放）を検出すると、ノードはメッシュ経由でアラートメッセージをブロードキャストします。 . | 設定項目 | 説明 | . | 検出センサーを有効化 | 検知センサーを有効化 | . | モニターのGPIOピン | センサーに接続された GPIO ピン | . | 検出トリガーの種類 | ピンの状態を検知イベントにどう対応させるか（例：アクティブハイ／ロー、エッジトリガー） | . | INPUT_PULLUP モードを使用 | ピンの内蔵プルアップ抵抗を有効にする | . | 最小ブロードキャスト間隔(秒) | アラートのブロードキャスト間の最小時間 | . | 状態のブロードキャスト間隔 (秒) | 定期的な状態ブロードキャストの間隔 | . | アラートメッセージ付きのベルを送信 | アラートにベル文字を含める | . | 名前 | このセンサーのカスタム名 | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. スマートフォンやノートパソコンがネットワークを探すときに発するプローブ要求を受動的に受信して、近くのデバイスを数えます。 ESP32 デバイスでのみ利用できます。 . | 設定 | 説明 | . | Paxcounter を有効化 | 人数カウントを有効化 | . | 更新間隔 (秒) | カウントを報告する頻度 | . | Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 ヒント： Paxcounter は、登山口やイベント会場などの人出を推定するのに便利です。カウントはおおよその値です。1 人が複数のデバイスを持っていることがあります。 . Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . ATAK および WinTAK と相互運用するための、Team Awareness Kit 連携です。 Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. 詳しい設定と使い方は、TAK 連携 を参照してください。 . ", + "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . インターネット接続のために、メッシュのメッセージを MQTT サーバーとの間で橋渡しします。 This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | 設定項目 | 説明 | . | MQTTを有効化 | MQTT ブリッジを切り替え | . | アドレス | MQTT サーバーのアドレス | . | ユーザー名 | 認証用のユーザー名 | . | パスワード | 認証用のパスワード | . | 暗号化の有効化 | MQTT ペイロードを暗号化 | . | JSON出力の有効化 | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS の有効化 | セキュアな接続を使用 | . | ルート トピック | MQTT のベーストピックパス | . | クライアントへのプロキシの有効化 | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | このスマートフォンの MQTT プロキシ | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | マップレポート | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | 設定項目 | 説明 | . | 同意します。 | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . 暗号化、プライバシー、サーバーの設定を含む詳しい使い方は、MQTT を参照してください。 . Serial module . 外部デバイスとの連携（GPS モジュール、センサー、カスタムハードウェア）のために、シリアルポート通信を有効にします。有効にすると、ノードのシリアルポートで protobuf またはテキストデータを送受信でき、外部のマイコンやコンピューターがメッシュとやり取りできるようになります。 . | 設定項目 | 説明 | . | シリアル通信を有効化 | シリアル通信を有効化 | . | Echoを有効化 | 受信したシリアルデータをそのまま返す | . | シリアルモード | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | シリアルボーレイト | Port speed | . | タイムアウト | How long to wait before considering an incoming message complete | . | コンソールのシリアルポートを上書き | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. メッセージ到着時に物理的に知らせる必要があるデバイスに便利です。特に無人設置や屋外設置で役立ちます。 . There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | 設定項目 | 説明 | . | 外部通知を有効化 | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | LED出力 (GPIO) | Pin the LED is wired to | . | LED出力 アクティブハイ | Whether the LED pin is active high or low | . | ブザー出力(GPIO) | Pin the buzzer is wired to | . | バイブレーション出力 (GPIO) | Pin the vibration motor is wired to | . | PWMブザーを使用 | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | I2Sをブザーとして使用 | Send the alert through an I2S audio output instead | . | GPIO Output Duration | How long a single alert lasts | . | Nag Timeout | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | 着信音 | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . 一時的にオフラインだったノードのためにメッセージをバッファリングし、それらのノードが再接続したときに再送します。ノードが頻繁に圏内・圏外を行き来するメッシュに不可欠です。短時間の切断中にメッセージが失われないようにします。 . | 設定項目 | 説明 | . | 一時保管と転送の有効化 | ストア＆フォワードを有効化 | . | ハートビート | このノードのストア＆フォワード機能を定期的に告知する | . | サーバーの最大保管レコード数 (デフォルト 約11,000レコード) | 保存するメッセージの最大数 | . | リクエスト可能な最大の履歴件数 | 再送するメッセージの最大数 | . | リクエスト可能な履歴の期間 (分) | 再送する時間の範囲 | . | サーバー | メッシュのストア＆フォワードサーバーとして動作する（十分なメモリが必要、例：PSRAM 搭載の ESP32） | . 💡 ヒント： ストア＆フォワードは、十分なメモリを持つノード（PSRAM 搭載の ESP32）で最も良く機能します。ルーターノードは通常は常時起動しているため、理想的な候補です。 . Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. ノード間のリンク品質を評価するための、自動レンジテストツールです。有効にすると、ノードはカウンターを増やしながらテストメッセージを定期的に送信します。受信側のノードがこれらのメッセージを記録するため、歩いたり車で移動したりして、後からどの距離でメッセージが届かなくなったかを分析できます。 . | 設定項目 | 説明 | . | レンジテストを有効化 | レンジテストを有効化 | . | Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals | . | ストレージにCSVファイルを保存(ESP32のみ) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . ノードがメッシュと共有するテレメトリデータを制御します。テレメトリには、デバイスの状態（バッテリー、連続稼働時間）と環境センサーのデータ（温度、湿度、気圧）が含まれます。 . Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | 設定項目 | 説明 | . | デバイステレメトリを送信 | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | デバイスメトリクスの更新間隔 | How often to report battery, uptime and channel utilization | . | 環境メトリクスモジュールを有効化 | Report the attached environment sensors | . | 環境メトリクスの更新間隔 | How often to report them | . | 環境メトリクスを画面上で有効化 | Also show these readings on the device’s own display | . | 環境メトリクスは華氏を使用 | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | 空気品質測定モジュールを有効化 | Report particulate and CO₂ sensor data | . | 空気品質メトリクスの更新間隔 | How often to report them | . | 電源メトリクスモジュール有効 | Report the per-channel voltage and current readings | . | 電源メトリクスの更新間隔 | How often to report them | . | 電源メトリクスを画面上で有効化 | Also show power readings on the device’s display | . 対応センサーと設定の推奨事項については、テレメトリとセンサー を参照してください。 . Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). スマートフォンを接続していなくても送信できる、クイック送信メッセージのリストを定義します。フィールドでの使用に最適です。 . | 設定項目 | 説明 | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | メッセージ | 改行で区切ったメッセージのリスト | . | ベルを送信 | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | ロータリーエンコーダ #1 を有効化 | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | 上下/選択入力を有効化 | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . メッシュ上での低帯域幅の音声通信のための、Codec2 音声サポートです。これは、Codec2 コーデックを使って音声を非常に小さなデータパケットにエンコードする、実験的な機能です。 . | 設定項目 | 説明 | . | CODEC 2 を有効化 | オーディオモジュールを有効化 | . | CODEC2 サンプルレート | 音質と帯域幅のトレードオフ | . | PTT端子 | GPIO pin for the push-to-talk button | . | I2S ワードセレクト | I2S WS 用の GPIO ピン | . | I2S データ IN | I2S DIN 用の GPIO ピン | . | I2S データ OUT | I2S DOUT 用の GPIO ピン | . | I2S クロック | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). 音質は非常に低帯域です。「聞き取れる無線の声」程度で、電話並みの品質ではないと考えてください。 . Remote Hardware module . メッシュネットワーク経由での GPIO 制御です。リモートのノードが、別のノードの GPIO ピンを読み書きできるようにします。リレーの作動、スイッチの読み取り、離れた場所からの外部ハードウェア制御に便利です。 . ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | 設定項目 | 説明 | . | リモートハードウェアを有効化 | リモート GPIO アクセスを有効化 | . | 未定義のピンへのアクセスを許可 | 任意の GPIO ピンへのアクセスを許可（セキュリティリスク） | . | 使用可能な端子 | このノードがリモートの読み書き用に公開する GPIO ピン（最大 4 個） | . Neighbor Info module . 直接受信した隣接ノードの情報をブロードキャストし、メッシュのトポロジーマッピングを可能にします。有効にした各ノードは、受信できる他のノードとその信号品質のリストを定期的に共有します。 . | 設定項目 | 説明 | . | 近隣ノード情報を有効化 | 隣接ノードのブロードキャストを有効化 | . | GPS ポーリング間隔 | 隣接ノードのリストをブロードキャストする頻度 | . | LoRaで送信 | MQTT／スマートフォンだけでなく、LoRa 経由でも隣接ノード情報をブロードキャストします。デフォルトの鍵と名前を使用しているチャンネルでは利用できません | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . 対応ハードウェア上の、オンボードの NeoPixel やその他のアドレサブル RGB LED を制御します。視覚的なステータス表示、通知ライト、装飾的な演出に使用できます。 . | 設定項目 | 説明 | . | LEDの状態 | LED のオン／オフを切り替え | . | 電流 | LED の電流制限（0〜31） | . | 赤／緑／青 | 各色チャンネルの値（0〜255） | . Detection Sensor module . ノードを、動きやドアを検知するセンサーアラートシステムに変えます。 GPIO ピンが状態の変化（動きの検知、ドアの開放）を検出すると、ノードはメッシュ経由でアラートメッセージをブロードキャストします。 . | 設定項目 | 説明 | . | 検出センサーを有効化 | 検知センサーを有効化 | . | モニターのGPIOピン | センサーに接続された GPIO ピン | . | 検出トリガーの種類 | ピンの状態を検知イベントにどう対応させるか（例：アクティブハイ／ロー、エッジトリガー） | . | INPUT_PULLUP モードを使用 | ピンの内蔵プルアップ抵抗を有効にする | . | Minimum time between detection broadcasts | アラートのブロードキャスト間の最小時間 | . | State Broadcast Interval | 定期的な状態ブロードキャストの間隔 | . | アラートメッセージ付きのベルを送信 | アラートにベル文字を含める | . | 名前 | このセンサーのカスタム名 | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. スマートフォンやノートパソコンがネットワークを探すときに発するプローブ要求を受動的に受信して、近くのデバイスを数えます。 ESP32 デバイスでのみ利用できます。 . | 設定 | 説明 | . | Paxcounter を有効化 | 人数カウントを有効化 | . | GPS ポーリング間隔 | カウントを報告する頻度 | . | WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 ヒント： Paxcounter は、登山口やイベント会場などの人出を推定するのに便利です。カウントはおおよその値です。1 人が複数のデバイスを持っていることがあります。 . Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . ATAK および WinTAK と相互運用するための、Team Awareness Kit 連携です。 Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. 詳しい設定と使い方は、TAK 連携 を参照してください。 . ", "url": "/Meshtastic-Android/main/ja-rJP/user/settings-module-admin.html#%E8%BF%BD%E5%8A%A0%E6%A9%9F%E8%83%BD%E3%81%AE%E8%A8%AD%E5%AE%9A", "relUrl": "/ja-rJP/user/settings-module-admin.html#追加機能の設定" @@ -30528,7 +30528,7 @@ },"4361": { "doc": "Settings — Modules & Admin", "title": "Moduleinstellungen", - "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Einstellung | Beschreibung | . | MQTT aktiviert | Toggle MQTT bridge | . | Adresse | MQTT broker address | . | Benutzername | Authentication username | . | Passwort | Authentication password | . | Verschlüsselung aktiviert | Encrypt MQTT payloads | . | JSON-Ausgabe aktiviert | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS aktiviert | Use secure connection | . | Hauptthema | Base MQTT topic path | . | Proxy zu Client aktiviert | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT Proxy auf diesem Handy | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Kartenberichte | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Einstellung | Beschreibung | . | Ich stimme zu. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Kartenberichtsintervall (Sekunden) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Einstellung | Beschreibung | . | Serielle Schnittstelle aktiviert | Activate serial communication | . | Echo aktiviert | Echo received serial data back | . | Serieller Modus | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Serielle Baudrate | Port speed | . | Zeitlimit erreicht | How long to wait before considering an incoming message complete | . | Seriellen Anschluss der Konsole überschreiben | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Einstellung | Beschreibung | . | Externe Benachrichtigungen aktiviert | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Ausgabe LED (GPIO) | Pin the LED is wired to | . | Ausgabe LED aktiv hoch | Whether the LED pin is active high or low | . | Ausgabe Summer (GPIO) | Pin the buzzer is wired to | . | Ausgabe Vibration (GPIO) | Pin the vibration motor is wired to | . | Benutze PWM Summer | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | I2S als Buzzer verwenden | Send the alert through an I2S audio output instead | . | Ausgabedauer (GPIO) | How long a single alert lasts | . | Nervige Verzögerung (Sekunden) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Klingelton | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Einstellung | Beschreibung | . | Speichern & Weiterleiten aktiviert | Activate store and forward | . | Puls | Periodically announce this node’s store-and-forward capability | . | Anzahl Einträge | Maximum stored messages | . | Verlauf Rückgabewert maximal | Max messages to replay | . | Zeitraum Rückgabewert | Time window for replay | . | Server | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Einstellung | Beschreibung | . | Reichweitentest aktiviert | Activate range testing | . | Sendernachrichtenintervall (Sekunden) | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Speichere .CSV im Speicher (nur ESP32) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Einstellung | Beschreibung | . | Gerätetelemetrie senden | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Aktualisierungsintervall für Gerätedaten | How often to report battery, uptime and channel utilization | . | Modul Umweltdaten aktiviert | Report the attached environment sensors | . | Aktualisierungsintervall für Umweltdaten | How often to report them | . | Umweltdatenanzeige aktiviert | Also show these readings on the device’s own display | . | Umweltdaten in Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Modul Luftqualität aktiviert | Report particulate and CO₂ sensor data | . | Aktualisierungsintervall der Luftqualität | How often to report them | . | Modul Energiedaten aktiviert | Report the per-channel voltage and current readings | . | Aktualisierungsintervall für Energiedaten | How often to report them | . | Energiedatenanzeige aktiviert | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Einstellung | Beschreibung | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Nachrichten | Newline-separated list of messages | . | Glocke senden | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Drehencoder #1 aktiviert | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Up/Down/Select Eingang aktiviert | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Einstellung | Beschreibung | . | CODEC 2 aktiviert | Activate audio module | . | CODEC2 Abtastrate | Audio quality/bandwidth tradeoff | . | GPIO Pin PTT | GPIO pin for the push-to-talk button | . | I2S Wortauswahl | GPIO pin for I2S WS | . | I2S Daten Eingang | GPIO pin for I2S DIN | . | I2S Daten Ausgang | GPIO pin for I2S DOUT | . | I2S Takt | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Einstellung | Beschreibung | . | Einstellung entfernte Hardware | Activate remote GPIO access | . | Erlaube undefinierten Pin-Zugriff | Allow access to any GPIO pin (security risk) | . | Verfügbare Pins | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Einstellung | Beschreibung | . | Nachbarinformationen aktiviert | Activate neighbor broadcasting | . | Aktualisierungsintervall (Sekunden) | How often to broadcast neighbor list | . | Übertragen über LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Einstellung | Beschreibung | . | LED Zustand | Turn the LED on or off | . | Stromstärke | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Einstellung | Beschreibung | . | Erkennungssensor aktiviert | Activate detection sensor | . | Zu überwachender GPIO-Pin | GPIO pin connected to sensor | . | Typ der Erkennungsauslösung | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Eingang PULLUP Einstellung | Enable the pin’s internal pull-up resistor | . | Minimale Übertragungszeit (Sekunden) | Minimum time between alert broadcasts | . | Statusübertragung (Sekunden) | Periodic state broadcast interval | . | Glocke mit Warnmeldung senden | Include bell character in alerts | . | Anzeigename | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Einstellung | Beschreibung | . | Besucherzähler aktiviert | Activate people counting | . | Aktualisierungsintervall (Sekunden) | How often to report counts | . | Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. Siehe TAK Integration für detaillierte Einrichtung und Nutzung. ", + "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Einstellung | Beschreibung | . | MQTT aktiviert | Toggle MQTT bridge | . | Adresse | MQTT broker address | . | Benutzername | Authentication username | . | Passwort | Authentication password | . | Verschlüsselung aktiviert | Encrypt MQTT payloads | . | JSON-Ausgabe aktiviert | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS aktiviert | Use secure connection | . | Hauptthema | Base MQTT topic path | . | Proxy zu Client aktiviert | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT Proxy auf diesem Handy | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Kartenberichte | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Einstellung | Beschreibung | . | Ich stimme zu. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Einstellung | Beschreibung | . | Serielle Schnittstelle aktiviert | Activate serial communication | . | Echo aktiviert | Echo received serial data back | . | Serieller Modus | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Serielle Baudrate | Port speed | . | Zeitlimit erreicht | How long to wait before considering an incoming message complete | . | Seriellen Anschluss der Konsole überschreiben | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Einstellung | Beschreibung | . | Externe Benachrichtigungen aktiviert | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Ausgabe LED (GPIO) | Pin the LED is wired to | . | Ausgabe LED aktiv hoch | Whether the LED pin is active high or low | . | Ausgabe Summer (GPIO) | Pin the buzzer is wired to | . | Ausgabe Vibration (GPIO) | Pin the vibration motor is wired to | . | Benutze PWM Summer | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | I2S als Buzzer verwenden | Send the alert through an I2S audio output instead | . | GPIO Output Duration | How long a single alert lasts | . | Nervige Verzögerung | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Klingelton | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Einstellung | Beschreibung | . | Speichern & Weiterleiten aktiviert | Activate store and forward | . | Puls | Periodically announce this node’s store-and-forward capability | . | Anzahl Einträge | Maximum stored messages | . | Verlauf Rückgabewert maximal | Max messages to replay | . | Zeitraum Rückgabewert | Time window for replay | . | Server | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Einstellung | Beschreibung | . | Reichweitentest aktiviert | Activate range testing | . | Sendeintervall | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Speichere .CSV im Speicher (nur ESP32) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Einstellung | Beschreibung | . | Gerätetelemetrie senden | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Aktualisierungsintervall für Gerätedaten | How often to report battery, uptime and channel utilization | . | Modul Umweltdaten aktiviert | Report the attached environment sensors | . | Aktualisierungsintervall für Umweltdaten | How often to report them | . | Umweltdatenanzeige aktiviert | Also show these readings on the device’s own display | . | Umweltdaten in Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Modul Luftqualität aktiviert | Report particulate and CO₂ sensor data | . | Aktualisierungsintervall der Luftqualität | How often to report them | . | Modul Energiedaten aktiviert | Report the per-channel voltage and current readings | . | Aktualisierungsintervall für Energiedaten | How often to report them | . | Energiedatenanzeige aktiviert | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Einstellung | Beschreibung | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Nachrichten | Newline-separated list of messages | . | Glocke senden | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Drehencoder #1 aktiviert | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Up/Down/Select Eingang aktiviert | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Einstellung | Beschreibung | . | CODEC 2 aktiviert | Activate audio module | . | CODEC2 Abtastrate | Audio quality/bandwidth tradeoff | . | GPIO Pin PTT | GPIO pin for the push-to-talk button | . | I2S Wortauswahl | GPIO pin for I2S WS | . | I2S Daten Eingang | GPIO pin for I2S DIN | . | I2S Daten Ausgang | GPIO pin for I2S DOUT | . | I2S Takt | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Einstellung | Beschreibung | . | Einstellung entfernte Hardware | Activate remote GPIO access | . | Erlaube undefinierten Pin-Zugriff | Allow access to any GPIO pin (security risk) | . | Verfügbare Pins | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Einstellung | Beschreibung | . | Nachbarinformationen aktiviert | Activate neighbor broadcasting | . | GPS Abfrageintervall | How often to broadcast neighbor list | . | Übertragen über LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Einstellung | Beschreibung | . | LED Zustand | Turn the LED on or off | . | Stromstärke | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Einstellung | Beschreibung | . | Erkennungssensor aktiviert | Activate detection sensor | . | Zu überwachender GPIO-Pin | GPIO pin connected to sensor | . | Typ der Erkennungsauslösung | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Eingang PULLUP Einstellung | Enable the pin’s internal pull-up resistor | . | Minimum time between detection broadcasts | Minimum time between alert broadcasts | . | Übertragungsintervall | Periodic state broadcast interval | . | Glocke mit Warnmeldung senden | Include bell character in alerts | . | Anzeigename | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Einstellung | Beschreibung | . | Besucherzähler aktiviert | Activate people counting | . | GPS Abfrageintervall | How often to report counts | . | WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. Siehe TAK Integration für detaillierte Einrichtung und Nutzung. ", "url": "/Meshtastic-Android/main/de-rDE/user/settings-module-admin.html#moduleinstellungen", "relUrl": "/de-rDE/user/settings-module-admin.html#moduleinstellungen" @@ -30563,7 +30563,7 @@ },"4366": { "doc": "Settings — Modules & Admin", "title": "إعدادات الجهاز", - "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | الوصف | . | MQTT enabled | Toggle MQTT bridge | . | Address | MQTT broker address | . | Username | Authentication username | . | Password | Authentication password | . | Encryption enabled | Encrypt MQTT payloads | . | JSON output enabled | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS enabled | Use secure connection | . | Root topic | Base MQTT topic path | . | Proxy to client enabled | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Map reporting | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | الوصف | . | I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Map reporting interval (seconds) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | الوصف | . | Serial enabled | Activate serial communication | . | Echo enabled | Echo received serial data back | . | Serial mode | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Serial baud rate | Port speed | . | استغرق وقت طويل | How long to wait before considering an incoming message complete | . | Override console serial port | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | الوصف | . | External notification enabled | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Output LED (GPIO) | Pin the LED is wired to | . | Output LED active high | Whether the LED pin is active high or low | . | Output buzzer (GPIO) | Pin the buzzer is wired to | . | Output vibra (GPIO) | Pin the vibration motor is wired to | . | Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Use I2S as buzzer | Send the alert through an I2S audio output instead | . | Output duration (milliseconds) | How long a single alert lasts | . | Nag timeout (seconds) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | الوصف | . | Store & Forward enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | Number of records | Maximum stored messages | . | History return max | Max messages to replay | . | History return window | Time window for replay | . | Server | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | الوصف | . | Range test enabled | Activate range testing | . | Sender message interval (seconds) | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Save .CSV in storage (ESP32 only) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | الوصف | . | Send Device Telemetry | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Device metrics update interval | How often to report battery, uptime and channel utilization | . | Environment metrics module enabled | Report the attached environment sensors | . | Environment metrics update interval | How often to report them | . | Environment metrics on-screen enabled | Also show these readings on the device’s own display | . | Environment metrics use Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Air quality metrics module enabled | Report particulate and CO₂ sensor data | . | Air quality metrics update interval | How often to report them | . | Power metrics module enabled | Report the per-channel voltage and current readings | . | Power metrics update interval | How often to report them | . | Power metrics on-screen enabled | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | الوصف | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | الرسائل | Newline-separated list of messages | . | Send bell | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Rotary encoder #1 enabled | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Up/Down/Select input enabled | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | الوصف | . | CODEC 2 enabled | Activate audio module | . | CODEC2 sample rate | Audio quality/bandwidth tradeoff | . | PTT pin | GPIO pin for the push-to-talk button | . | I2S word select | GPIO pin for I2S WS | . | I2S data in | GPIO pin for I2S DIN | . | I2S data out | GPIO pin for I2S DOUT | . | I2S clock | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | الوصف | . | Remote Hardware enabled | Activate remote GPIO access | . | Allow undefined pin access | Allow access to any GPIO pin (security risk) | . | Available pins | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | الوصف | . | Neighbor Info enabled | Activate neighbor broadcasting | . | Update interval (seconds) | How often to broadcast neighbor list | . | Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | الوصف | . | LED state | Turn the LED on or off | . | الحالي | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | الوصف | . | Detection Sensor enabled | Activate detection sensor | . | GPIO pin to monitor | GPIO pin connected to sensor | . | Detection trigger type | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Use INPUT_PULLUP mode | Enable the pin’s internal pull-up resistor | . | Minimum broadcast (seconds) | Minimum time between alert broadcasts | . | State broadcast (seconds) | Periodic state broadcast interval | . | Send bell with alert message | Include bell character in alerts | . | Friendly name | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | الوصف | . | Paxcounter enabled | Activate people counting | . | Update interval (seconds) | How often to report counts | . | Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ", + "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | الوصف | . | MQTT enabled | Toggle MQTT bridge | . | Address | MQTT broker address | . | Username | Authentication username | . | Password | Authentication password | . | Encryption enabled | Encrypt MQTT payloads | . | JSON output enabled | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS enabled | Use secure connection | . | Root topic | Base MQTT topic path | . | Proxy to client enabled | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Map reporting | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | الوصف | . | I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | الوصف | . | Serial enabled | Activate serial communication | . | Echo enabled | Echo received serial data back | . | Serial mode | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Serial baud rate | Port speed | . | استغرق وقت طويل | How long to wait before considering an incoming message complete | . | Override console serial port | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | الوصف | . | External notification enabled | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Output LED (GPIO) | Pin the LED is wired to | . | Output LED active high | Whether the LED pin is active high or low | . | Output buzzer (GPIO) | Pin the buzzer is wired to | . | Output vibra (GPIO) | Pin the vibration motor is wired to | . | Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Use I2S as buzzer | Send the alert through an I2S audio output instead | . | GPIO Output Duration | How long a single alert lasts | . | Nag Timeout | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | الوصف | . | Store & Forward enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | Number of records | Maximum stored messages | . | History return max | Max messages to replay | . | History return window | Time window for replay | . | Server | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | الوصف | . | Range test enabled | Activate range testing | . | Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Save .CSV in storage (ESP32 only) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | الوصف | . | Send Device Telemetry | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Device metrics update interval | How often to report battery, uptime and channel utilization | . | Environment metrics module enabled | Report the attached environment sensors | . | Environment metrics update interval | How often to report them | . | Environment metrics on-screen enabled | Also show these readings on the device’s own display | . | Environment metrics use Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Air quality metrics module enabled | Report particulate and CO₂ sensor data | . | Air quality metrics update interval | How often to report them | . | Power metrics module enabled | Report the per-channel voltage and current readings | . | Power metrics update interval | How often to report them | . | Power metrics on-screen enabled | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | الوصف | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | الرسائل | Newline-separated list of messages | . | Send bell | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Rotary encoder #1 enabled | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Up/Down/Select input enabled | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | الوصف | . | CODEC 2 enabled | Activate audio module | . | CODEC2 sample rate | Audio quality/bandwidth tradeoff | . | PTT pin | GPIO pin for the push-to-talk button | . | I2S word select | GPIO pin for I2S WS | . | I2S data in | GPIO pin for I2S DIN | . | I2S data out | GPIO pin for I2S DOUT | . | I2S clock | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | الوصف | . | Remote Hardware enabled | Activate remote GPIO access | . | Allow undefined pin access | Allow access to any GPIO pin (security risk) | . | Available pins | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | الوصف | . | Neighbor Info enabled | Activate neighbor broadcasting | . | Update Interval | How often to broadcast neighbor list | . | Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | الوصف | . | LED state | Turn the LED on or off | . | الحالي | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | الوصف | . | Detection Sensor enabled | Activate detection sensor | . | GPIO pin to monitor | GPIO pin connected to sensor | . | Detection trigger type | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Use INPUT_PULLUP mode | Enable the pin’s internal pull-up resistor | . | Minimum time between detection broadcasts | Minimum time between alert broadcasts | . | State Broadcast Interval | Periodic state broadcast interval | . | Send bell with alert message | Include bell character in alerts | . | Friendly name | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | الوصف | . | Paxcounter enabled | Activate people counting | . | Update Interval | How often to report counts | . | WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ", "url": "/Meshtastic-Android/main/ar-rSA/user/settings-module-admin.html#%D8%A5%D8%B9%D8%AF%D8%A7%D8%AF%D8%A7%D8%AA-%D8%A7%D9%84%D8%AC%D9%87%D8%A7%D8%B2", "relUrl": "/ar-rSA/user/settings-module-admin.html#إعدادات-الجهاز" @@ -30598,7 +30598,7 @@ },"4371": { "doc": "Settings — Modules & Admin", "title": "Konfiguracija modula", - "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Opis | . | MQTT enabled | Toggle MQTT bridge | . | Address | MQTT broker address | . | Username | Authentication username | . | Password | Authentication password | . | Encryption enabled | Encrypt MQTT payloads | . | JSON output enabled | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS enabled | Use secure connection | . | Root topic | Base MQTT topic path | . | Proxy to client enabled | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Map reporting | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Opis | . | I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Map reporting interval (seconds) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Opis | . | Serial enabled | Activate serial communication | . | Echo enabled | Echo received serial data back | . | Serial mode | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Serial baud rate | Port speed | . | Timeout | How long to wait before considering an incoming message complete | . | Override console serial port | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Opis | . | External notification enabled | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Output LED (GPIO) | Pin the LED is wired to | . | Output LED active high | Whether the LED pin is active high or low | . | Output buzzer (GPIO) | Pin the buzzer is wired to | . | Output vibra (GPIO) | Pin the vibration motor is wired to | . | Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Use I2S as buzzer | Send the alert through an I2S audio output instead | . | Output duration (milliseconds) | How long a single alert lasts | . | Nag timeout (seconds) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Opis | . | Store & Forward enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | Number of records | Maximum stored messages | . | History return max | Max messages to replay | . | History return window | Time window for replay | . | Server | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Opis | . | Range test enabled | Activate range testing | . | Sender message interval (seconds) | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Save .CSV in storage (ESP32 only) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Opis | . | Send Device Telemetry | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Device metrics update interval | How often to report battery, uptime and channel utilization | . | Environment metrics module enabled | Report the attached environment sensors | . | Environment metrics update interval | How often to report them | . | Environment metrics on-screen enabled | Also show these readings on the device’s own display | . | Environment metrics use Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Air quality metrics module enabled | Report particulate and CO₂ sensor data | . | Air quality metrics update interval | How often to report them | . | Power metrics module enabled | Report the per-channel voltage and current readings | . | Power metrics update interval | How often to report them | . | Power metrics on-screen enabled | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Opis | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Messages | Newline-separated list of messages | . | Send bell | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Rotary encoder #1 enabled | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Up/Down/Select input enabled | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Opis | . | CODEC 2 enabled | Activate audio module | . | CODEC2 sample rate | Audio quality/bandwidth tradeoff | . | PTT pin | GPIO pin for the push-to-talk button | . | I2S word select | GPIO pin for I2S WS | . | I2S data in | GPIO pin for I2S DIN | . | I2S data out | GPIO pin for I2S DOUT | . | I2S clock | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Opis | . | Remote Hardware enabled | Activate remote GPIO access | . | Allow undefined pin access | Allow access to any GPIO pin (security risk) | . | Available pins | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Opis | . | Neighbor Info enabled | Activate neighbor broadcasting | . | Update interval (seconds) | How often to broadcast neighbor list | . | Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Opis | . | LED state | Turn the LED on or off | . | Current | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Opis | . | Detection Sensor enabled | Activate detection sensor | . | GPIO pin to monitor | GPIO pin connected to sensor | . | Detection trigger type | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Use INPUT_PULLUP mode | Enable the pin’s internal pull-up resistor | . | Minimum broadcast (seconds) | Minimum time between alert broadcasts | . | State broadcast (seconds) | Periodic state broadcast interval | . | Send bell with alert message | Include bell character in alerts | . | Friendly name | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Opis | . | Paxcounter enabled | Activate people counting | . | Update interval (seconds) | How often to report counts | . | Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ", + "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Opis | . | MQTT enabled | Toggle MQTT bridge | . | Address | MQTT broker address | . | Username | Authentication username | . | Password | Authentication password | . | Encryption enabled | Encrypt MQTT payloads | . | JSON output enabled | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS enabled | Use secure connection | . | Root topic | Base MQTT topic path | . | Proxy to client enabled | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Map reporting | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Opis | . | I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Opis | . | Serial enabled | Activate serial communication | . | Echo enabled | Echo received serial data back | . | Serial mode | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Serial baud rate | Port speed | . | Timeout | How long to wait before considering an incoming message complete | . | Override console serial port | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Opis | . | External notification enabled | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Output LED (GPIO) | Pin the LED is wired to | . | Output LED active high | Whether the LED pin is active high or low | . | Output buzzer (GPIO) | Pin the buzzer is wired to | . | Output vibra (GPIO) | Pin the vibration motor is wired to | . | Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Use I2S as buzzer | Send the alert through an I2S audio output instead | . | GPIO Output Duration | How long a single alert lasts | . | Nag Timeout | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Opis | . | Store & Forward enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | Number of records | Maximum stored messages | . | History return max | Max messages to replay | . | History return window | Time window for replay | . | Server | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Opis | . | Range test enabled | Activate range testing | . | Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Save .CSV in storage (ESP32 only) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Opis | . | Send Device Telemetry | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Device metrics update interval | How often to report battery, uptime and channel utilization | . | Environment metrics module enabled | Report the attached environment sensors | . | Environment metrics update interval | How often to report them | . | Environment metrics on-screen enabled | Also show these readings on the device’s own display | . | Environment metrics use Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Air quality metrics module enabled | Report particulate and CO₂ sensor data | . | Air quality metrics update interval | How often to report them | . | Power metrics module enabled | Report the per-channel voltage and current readings | . | Power metrics update interval | How often to report them | . | Power metrics on-screen enabled | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Opis | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Messages | Newline-separated list of messages | . | Send bell | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Rotary encoder #1 enabled | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Up/Down/Select input enabled | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Opis | . | CODEC 2 enabled | Activate audio module | . | CODEC2 sample rate | Audio quality/bandwidth tradeoff | . | PTT pin | GPIO pin for the push-to-talk button | . | I2S word select | GPIO pin for I2S WS | . | I2S data in | GPIO pin for I2S DIN | . | I2S data out | GPIO pin for I2S DOUT | . | I2S clock | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Opis | . | Remote Hardware enabled | Activate remote GPIO access | . | Allow undefined pin access | Allow access to any GPIO pin (security risk) | . | Available pins | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Opis | . | Neighbor Info enabled | Activate neighbor broadcasting | . | Update Interval | How often to broadcast neighbor list | . | Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Opis | . | LED state | Turn the LED on or off | . | Current | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Opis | . | Detection Sensor enabled | Activate detection sensor | . | GPIO pin to monitor | GPIO pin connected to sensor | . | Detection trigger type | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Use INPUT_PULLUP mode | Enable the pin’s internal pull-up resistor | . | Minimum time between detection broadcasts | Minimum time between alert broadcasts | . | State Broadcast Interval | Periodic state broadcast interval | . | Send bell with alert message | Include bell character in alerts | . | Friendly name | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Opis | . | Paxcounter enabled | Activate people counting | . | Update Interval | How often to report counts | . | WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ", "url": "/Meshtastic-Android/main/hr-rHR/user/settings-module-admin.html#konfiguracija-modula", "relUrl": "/hr-rHR/user/settings-module-admin.html#konfiguracija-modula" @@ -30633,7 +30633,7 @@ },"4376": { "doc": "Settings — Modules & Admin", "title": "Configurações dos módulos", - "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Descrição | . | MQTT ativo | Toggle MQTT bridge | . | Endereço | MQTT broker address | . | Utilizador | Authentication username | . | Palavra-passe | Authentication password | . | Encriptação ativada | Encrypt MQTT payloads | . | Saída JSON ativada | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | Ativar TLS | Use secure connection | . | Tópico principal | Base MQTT topic path | . | Enviar através do cliente | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Enviar para o mapa | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Descrição | . | Estou de acordo. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Intervalo de envio (segundos) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Descrição | . | Série ativada | Activate serial communication | . | Eco ativado | Echo received serial data back | . | Modo de série | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Taxa de transmissão série | Port speed | . | Timeout | How long to wait before considering an incoming message complete | . | Substituir porta série do console | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Descrição | . | Ativar notificações externas | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | LED de Saída (GPIO) | Pin the LED is wired to | . | LED de saída ativo alto | Whether the LED pin is active high or low | . | Buzzer de saída (GPIO) | Pin the buzzer is wired to | . | Vibra de saída (GPIO) | Pin the vibration motor is wired to | . | Usar um buzzer PWM | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Usar I2S como buzzer | Send the alert through an I2S audio output instead | . | Duração da Saída (milissegundos) | How long a single alert lasts | . | Tempo limite a incomodar (segundos) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Toque | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Descrição | . | Guardar & encaminhar ativo | Activate store and forward | . | Batimento | Periodically announce this node’s store-and-forward capability | . | Número de registos | Maximum stored messages | . | History return max | Max messages to replay | . | History return window | Time window for replay | . | Servidor | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Descrição | . | Ativar Teste de alcance | Activate range testing | . | Sender message interval (seconds) | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Guardar .CSV no armazenamento (apenas ESP32) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Descrição | . | Send Device Telemetry | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Device metrics update interval | How often to report battery, uptime and channel utilization | . | Módulo de métricas de ambiente ativado | Report the attached environment sensors | . | Environment metrics update interval | How often to report them | . | Mostrar métricas de ambiente no ecrã | Also show these readings on the device’s own display | . | Métricas de Ambiente usam Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Módulo de métricas de qualidade do ar ativado | Report particulate and CO₂ sensor data | . | Air quality metrics update interval | How often to report them | . | Módulo de métricas de energia ativado | Report the per-channel voltage and current readings | . | Power metrics update interval | How often to report them | . | Mostrar métricas de energia no ecrã | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Descrição | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Mensagens | Newline-separated list of messages | . | Enviar sino | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Ativar Codificador rotativo #1 | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Entrada Cima/Baixo/Selecionar ativa | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Descrição | . | CODEC 2 ativado | Activate audio module | . | Taxa de amostragem CODEC2 | Audio quality/bandwidth tradeoff | . | Pin de PTT | GPIO pin for the push-to-talk button | . | Selecionar palavra I2S | GPIO pin for I2S WS | . | Entrada de dados I2S | GPIO pin for I2S DIN | . | Saída de dados I2S | GPIO pin for I2S DOUT | . | Relógio I2S | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Descrição | . | Hardware Remoto ativado | Activate remote GPIO access | . | Permitir acesso indefinido ao pin | Allow access to any GPIO pin (security risk) | . | Pins disponíveis | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Descrição | . | Enviar informações de vizinhos | Activate neighbor broadcasting | . | Intervalo de atualização (segundos) | How often to broadcast neighbor list | . | Enviar por LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Descrição | . | Estado do LED | Turn the LED on or off | . | Atual | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Descrição | . | Sensor de deteção ativado | Activate detection sensor | . | Pin GPIO para monitorizar | GPIO pin connected to sensor | . | Tipo de gatilho de deteção | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Usar o modo INPUT_PULLUP | Enable the pin’s internal pull-up resistor | . | Transmissão mínima (segundos) | Minimum time between alert broadcasts | . | Transmissão de estado (segundos) | Periodic state broadcast interval | . | Enviar sino com mensagem de alerta | Include bell character in alerts | . | Nome amigável | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Descrição | . | Ativar contador de pessoas | Activate people counting | . | Intervalo de atualização (segundos) | How often to report counts | . | Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ", + "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Descrição | . | MQTT ativo | Toggle MQTT bridge | . | Endereço | MQTT broker address | . | Utilizador | Authentication username | . | Palavra-passe | Authentication password | . | Encriptação ativada | Encrypt MQTT payloads | . | Saída JSON ativada | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | Ativar TLS | Use secure connection | . | Tópico principal | Base MQTT topic path | . | Enviar através do cliente | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Enviar para o mapa | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Descrição | . | Estou de acordo. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Descrição | . | Série ativada | Activate serial communication | . | Eco ativado | Echo received serial data back | . | Modo de série | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Taxa de transmissão série | Port speed | . | Timeout | How long to wait before considering an incoming message complete | . | Substituir porta série do console | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Descrição | . | Ativar notificações externas | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | LED de Saída (GPIO) | Pin the LED is wired to | . | LED de saída ativo alto | Whether the LED pin is active high or low | . | Buzzer de saída (GPIO) | Pin the buzzer is wired to | . | Vibra de saída (GPIO) | Pin the vibration motor is wired to | . | Usar um buzzer PWM | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Usar I2S como buzzer | Send the alert through an I2S audio output instead | . | GPIO Output Duration | How long a single alert lasts | . | Nag Timeout | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Toque | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Descrição | . | Guardar & encaminhar ativo | Activate store and forward | . | Batimento | Periodically announce this node’s store-and-forward capability | . | Número de registos | Maximum stored messages | . | History return max | Max messages to replay | . | History return window | Time window for replay | . | Servidor | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Descrição | . | Ativar Teste de alcance | Activate range testing | . | Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Guardar .CSV no armazenamento (apenas ESP32) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Descrição | . | Send Device Telemetry | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Device metrics update interval | How often to report battery, uptime and channel utilization | . | Módulo de métricas de ambiente ativado | Report the attached environment sensors | . | Environment metrics update interval | How often to report them | . | Mostrar métricas de ambiente no ecrã | Also show these readings on the device’s own display | . | Métricas de Ambiente usam Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Módulo de métricas de qualidade do ar ativado | Report particulate and CO₂ sensor data | . | Air quality metrics update interval | How often to report them | . | Módulo de métricas de energia ativado | Report the per-channel voltage and current readings | . | Power metrics update interval | How often to report them | . | Mostrar métricas de energia no ecrã | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Descrição | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Mensagens | Newline-separated list of messages | . | Enviar sino | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Ativar Codificador rotativo #1 | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Entrada Cima/Baixo/Selecionar ativa | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Descrição | . | CODEC 2 ativado | Activate audio module | . | Taxa de amostragem CODEC2 | Audio quality/bandwidth tradeoff | . | Pin de PTT | GPIO pin for the push-to-talk button | . | Selecionar palavra I2S | GPIO pin for I2S WS | . | Entrada de dados I2S | GPIO pin for I2S DIN | . | Saída de dados I2S | GPIO pin for I2S DOUT | . | Relógio I2S | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Descrição | . | Hardware Remoto ativado | Activate remote GPIO access | . | Permitir acesso indefinido ao pin | Allow access to any GPIO pin (security risk) | . | Pins disponíveis | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Descrição | . | Enviar informações de vizinhos | Activate neighbor broadcasting | . | Intervalo de Atualização | How often to broadcast neighbor list | . | Enviar por LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Descrição | . | Estado do LED | Turn the LED on or off | . | Atual | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Descrição | . | Sensor de deteção ativado | Activate detection sensor | . | Pin GPIO para monitorizar | GPIO pin connected to sensor | . | Tipo de gatilho de deteção | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Usar o modo INPUT_PULLUP | Enable the pin’s internal pull-up resistor | . | Minimum time between detection broadcasts | Minimum time between alert broadcasts | . | State Broadcast Interval | Periodic state broadcast interval | . | Enviar sino com mensagem de alerta | Include bell character in alerts | . | Nome amigável | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Descrição | . | Ativar contador de pessoas | Activate people counting | . | Intervalo de Atualização | How often to report counts | . | WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ", "url": "/Meshtastic-Android/main/pt-rPT/user/settings-module-admin.html#configura%C3%A7%C3%B5es-dos-m%C3%B3dulos", "relUrl": "/pt-rPT/user/settings-module-admin.html#configurações-dos-módulos" @@ -30668,7 +30668,7 @@ },"4381": { "doc": "Settings — Modules & Admin", "title": "Ustawienia modułu", - "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Opis | . | Włącz MQTT | Toggle MQTT bridge | . | Adres | MQTT broker address | . | Nazwa użytkownika | Authentication username | . | Hasło | Authentication password | . | Szyfrowanie włączone | Encrypt MQTT payloads | . | Włącz wyjście JSON | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | Włącz TLS | Use secure connection | . | Główny wątek | Base MQTT topic path | . | Proxy to client enabled | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Raportowanie map | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Opis | . | Zgadzam się. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Interwał raportowania map (sekundy) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Opis | . | Włącz tryb serial | Activate serial communication | . | Włącz echo | Echo received serial data back | . | Tryb serial | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Prędkość transmisji | Port speed | . | Limit czasu | How long to wait before considering an incoming message complete | . | Override console serial port | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Opis | . | Powiadomienia zewnętrzne włączone | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Wyjście LED (GPIO) | Pin the LED is wired to | . | Output LED active high | Whether the LED pin is active high or low | . | Wyjście buzzera (GPIO) | Pin the buzzer is wired to | . | Wyjście silnika wibracyjnego (GPIO) | Pin the vibration motor is wired to | . | Użyj buzzer PWM | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Użyj I2S jako buzzer | Send the alert through an I2S audio output instead | . | Czas trwania (w milisekundach) | How long a single alert lasts | . | Nag timeout (seconds) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Dzwonek | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Opis | . | Store & Forward enabled | Activate store and forward | . | Bicie serca | Periodically announce this node’s store-and-forward capability | . | Liczba rekordów | Maximum stored messages | . | Maks zwrotnej historii | Max messages to replay | . | Okno zwrotu historii | Time window for replay | . | Serwer | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Opis | . | Range test enabled | Activate range testing | . | Sender message interval (seconds) | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Save .CSV in storage (ESP32 only) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Opis | . | Send Device Telemetry | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Device metrics update interval | How often to report battery, uptime and channel utilization | . | Environment metrics module enabled | Report the attached environment sensors | . | Environment metrics update interval | How often to report them | . | Environment metrics on-screen enabled | Also show these readings on the device’s own display | . | Environment metrics use Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Włącz moduł metryk jakości powietrza | Report particulate and CO₂ sensor data | . | Czas aktualizacji metryk jakości powietrza | How often to report them | . | Włącz moduł metryk zasilania | Report the per-channel voltage and current readings | . | Czas aktualizacji metryk zasilania | How often to report them | . | Wyświetlaj metryki zasilania na ekranie | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Opis | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Wiadomości | Newline-separated list of messages | . | Send bell | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Rotary encoder #1 enabled | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Up/Down/Select input enabled | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Opis | . | CODEC 2 włączony | Activate audio module | . | Częstotliwość próbkowania CODEC2 | Audio quality/bandwidth tradeoff | . | Pin PTT (Push-To-Talk) | GPIO pin for the push-to-talk button | . | I2S word select | GPIO pin for I2S WS | . | I2S data in | GPIO pin for I2S DIN | . | I2S data out | GPIO pin for I2S DOUT | . | Zegar I2S | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Opis | . | Remote Hardware enabled | Activate remote GPIO access | . | Allow undefined pin access | Allow access to any GPIO pin (security risk) | . | Dostępne piny | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Opis | . | Włącz informacje o sąsiedzie | Activate neighbor broadcasting | . | Częstotliwość aktualizacji (w sekundach) | How often to broadcast neighbor list | . | Nadaj przez LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Opis | . | Stan diody LED | Turn the LED on or off | . | Natężenie | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Opis | . | Czujnik detekcji włączony | Activate detection sensor | . | Pin GPIO do monitorowania | GPIO pin connected to sensor | . | Detection trigger type | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Użyj trybu INPUT_PULLUP | Enable the pin’s internal pull-up resistor | . | Minimalny czas transmisji (sekundy) | Minimum time between alert broadcasts | . | State broadcast (seconds) | Periodic state broadcast interval | . | Send bell with alert message | Include bell character in alerts | . | Przyjazna nazwa | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Opis | . | Paxcounter enabled | Activate people counting | . | Częstotliwość aktualizacji (w sekundach) | How often to report counts | . | Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ", + "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Opis | . | Włącz MQTT | Toggle MQTT bridge | . | Adres | MQTT broker address | . | Nazwa użytkownika | Authentication username | . | Hasło | Authentication password | . | Szyfrowanie włączone | Encrypt MQTT payloads | . | Włącz wyjście JSON | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | Włącz TLS | Use secure connection | . | Główny wątek | Base MQTT topic path | . | Proxy to client enabled | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Raportowanie map | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Opis | . | Zgadzam się. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Opis | . | Włącz tryb serial | Activate serial communication | . | Włącz echo | Echo received serial data back | . | Tryb serial | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Prędkość transmisji | Port speed | . | Limit czasu | How long to wait before considering an incoming message complete | . | Override console serial port | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Opis | . | Powiadomienia zewnętrzne włączone | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Wyjście LED (GPIO) | Pin the LED is wired to | . | Output LED active high | Whether the LED pin is active high or low | . | Wyjście buzzera (GPIO) | Pin the buzzer is wired to | . | Wyjście silnika wibracyjnego (GPIO) | Pin the vibration motor is wired to | . | Użyj buzzer PWM | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Użyj I2S jako buzzer | Send the alert through an I2S audio output instead | . | GPIO Output Duration | How long a single alert lasts | . | Nag Czas przerwy | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Dzwonek | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Opis | . | Store & Forward enabled | Activate store and forward | . | Bicie serca | Periodically announce this node’s store-and-forward capability | . | Liczba rekordów | Maximum stored messages | . | Maks zwrotnej historii | Max messages to replay | . | Okno zwrotu historii | Time window for replay | . | Serwer | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Opis | . | Range test enabled | Activate range testing | . | Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Save .CSV in storage (ESP32 only) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Opis | . | Send Device Telemetry | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Device metrics update interval | How often to report battery, uptime and channel utilization | . | Environment metrics module enabled | Report the attached environment sensors | . | Environment metrics update interval | How often to report them | . | Environment metrics on-screen enabled | Also show these readings on the device’s own display | . | Environment metrics use Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Włącz moduł metryk jakości powietrza | Report particulate and CO₂ sensor data | . | Czas aktualizacji metryk jakości powietrza | How often to report them | . | Włącz moduł metryk zasilania | Report the per-channel voltage and current readings | . | Czas aktualizacji metryk zasilania | How often to report them | . | Wyświetlaj metryki zasilania na ekranie | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Opis | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Wiadomości | Newline-separated list of messages | . | Send bell | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Rotary encoder #1 enabled | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Up/Down/Select input enabled | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Opis | . | CODEC 2 włączony | Activate audio module | . | Częstotliwość próbkowania CODEC2 | Audio quality/bandwidth tradeoff | . | Pin PTT (Push-To-Talk) | GPIO pin for the push-to-talk button | . | I2S word select | GPIO pin for I2S WS | . | I2S data in | GPIO pin for I2S DIN | . | I2S data out | GPIO pin for I2S DOUT | . | Zegar I2S | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Opis | . | Remote Hardware enabled | Activate remote GPIO access | . | Allow undefined pin access | Allow access to any GPIO pin (security risk) | . | Dostępne piny | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Opis | . | Włącz informacje o sąsiedzie | Activate neighbor broadcasting | . | Częstotliwość aktualizacji | How often to broadcast neighbor list | . | Nadaj przez LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Opis | . | Stan diody LED | Turn the LED on or off | . | Natężenie | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Opis | . | Czujnik detekcji włączony | Activate detection sensor | . | Pin GPIO do monitorowania | GPIO pin connected to sensor | . | Detection trigger type | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Użyj trybu INPUT_PULLUP | Enable the pin’s internal pull-up resistor | . | Minimum time between detection broadcasts | Minimum time between alert broadcasts | . | State Broadcast Interval | Periodic state broadcast interval | . | Send bell with alert message | Include bell character in alerts | . | Przyjazna nazwa | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Opis | . | Paxcounter enabled | Activate people counting | . | Częstotliwość aktualizacji | How often to report counts | . | WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ", "url": "/Meshtastic-Android/main/pl-rPL/user/settings-module-admin.html#ustawienia-modu%C5%82u", "relUrl": "/pl-rPL/user/settings-module-admin.html#ustawienia-modułu" @@ -30703,7 +30703,7 @@ },"4386": { "doc": "Settings — Modules & Admin", "title": "模块设定", - "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | 说明 | . | 启用MQTT | Toggle MQTT bridge | . | 地址 | MQTT broker address | . | 用户名称 | Authentication username | . | 密码 | Authentication password | . | 启用加密 | Encrypt MQTT payloads | . | 启用JSON输出 | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | 启用TLS | Use secure connection | . | 根主题 | Base MQTT topic path | . | 启用客户端代理 | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | 在此手机上开启 MQTT 代理 | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | 地图报告 | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | 说明 | . | 我同意。 | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | 地图报告间隔 (秒) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | 说明 | . | 启用串口 | Activate serial communication | . | 启用Echo | Echo received serial data back | . | 串口模式 | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | 串口波特率 | Port speed | . | 超时 | How long to wait before considering an incoming message complete | . | 覆盖控制台串口端口 | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | 说明 | . | 启用外部通知 | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | 输出 LED (GPIO) | Pin the LED is wired to | . | 输出 LED 活动高 | Whether the LED pin is active high or low | . | 输出震动(GPIO) | Pin the buzzer is wired to | . | 输出振动 (GPIO) | Pin the vibration motor is wired to | . | 使用 PWM 蜂鸣器 | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | 使用 I2S 作为蜂鸣器 | Send the alert through an I2S audio output instead | . | 输出持续时间 (毫秒) | How long a single alert lasts | . | 屏幕超时(秒) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | 铃声 | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | 说明 | . | 启用存储和转发 | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | 记录数 | Maximum stored messages | . | 历史记录最大返回值 | Max messages to replay | . | 历史记录返回窗口 | Time window for replay | . | 服务器 | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | 说明 | . | 启用范围测试 | Activate range testing | . | 发件人消息间隔(秒) | Time between test transmissions, chosen from a dropdown of fixed intervals | . | 保存 CSV 到存储 (仅ESP32) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | 说明 | . | 发送设备远程数据 | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | 设备计量更新间隔 | How often to report battery, uptime and channel utilization | . | 启用环境计量模块 | Report the attached environment sensors | . | 环境计量更新间隔 | How often to report them | . | 屏幕显示环境指标 | Also show these readings on the device’s own display | . | 环境测量值使用华氏度 | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | 启用空气质量计量模块 | Report particulate and CO₂ sensor data | . | 空气质量计量更新间隔 | How often to report them | . | 启用电源计量模块 | Report the per-channel voltage and current readings | . | 电量计更新间隔 | How often to report them | . | 在屏幕上启用电源指标 | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | 说明 | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | 消息 | Newline-separated list of messages | . | 发送响铃 | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | 启用旋转编码器 #1 | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | 启用Up/Down/select 输入 | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | 说明 | . | 启用CODEC2 | Activate audio module | . | CODEC2 采样率 | Audio quality/bandwidth tradeoff | . | PTT 引脚 | GPIO pin for the push-to-talk button | . | I2S 字选择 | GPIO pin for I2S WS | . | I2S 数据 IN | GPIO pin for I2S DIN | . | I2S 数据 OUT | GPIO pin for I2S DOUT | . | I2S 时钟 | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | 说明 | . | 启用远程硬件 | Activate remote GPIO access | . | 允许未定义的引脚访问 | Allow access to any GPIO pin (security risk) | . | 可用引脚 | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | 说明 | . | 启用邻居信息 | Activate neighbor broadcasting | . | 更新间隔（秒） | How often to broadcast neighbor list | . | 通过 LoRa 传输 | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | 说明 | . | LED 状态 | Turn the LED on or off | . | 电流 | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | 说明 | . | 启用检测传感器 | Activate detection sensor | . | 显示器的 GPIO 引脚 | GPIO pin connected to sensor | . | 检测触发器类型 | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | 使用 输入上拉 模式 | Enable the pin’s internal pull-up resistor | . | 最小广播时间(秒) | Minimum time between alert broadcasts | . | 状态广播(秒) | Periodic state broadcast interval | . | 发送带有警报消息的响铃声 | Include bell character in alerts | . | 友好名称 | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | 说明 | . | 启用 Paxcount | Activate people counting | . | 更新间隔（秒） | How often to report counts | . | Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ", + "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | 说明 | . | 启用MQTT | Toggle MQTT bridge | . | 地址 | MQTT broker address | . | 用户名称 | Authentication username | . | 密码 | Authentication password | . | 启用加密 | Encrypt MQTT payloads | . | 启用JSON输出 | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | 启用TLS | Use secure connection | . | 根主题 | Base MQTT topic path | . | 启用客户端代理 | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | 在此手机上开启 MQTT 代理 | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | 地图报告 | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | 说明 | . | 我同意。 | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | 地图发布间隔 | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | 说明 | . | 启用串口 | Activate serial communication | . | 启用Echo | Echo received serial data back | . | 串口模式 | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | 串口波特率 | Port speed | . | 超时 | How long to wait before considering an incoming message complete | . | 覆盖控制台串口端口 | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | 说明 | . | 启用外部通知 | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | 输出 LED (GPIO) | Pin the LED is wired to | . | 输出 LED 活动高 | Whether the LED pin is active high or low | . | 输出震动(GPIO) | Pin the buzzer is wired to | . | 输出振动 (GPIO) | Pin the vibration motor is wired to | . | 使用 PWM 蜂鸣器 | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | 使用 I2S 作为蜂鸣器 | Send the alert through an I2S audio output instead | . | GPIO Output Duration | How long a single alert lasts | . | 超时提醒 | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | 铃声 | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | 说明 | . | 启用存储和转发 | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | 记录数 | Maximum stored messages | . | 历史记录最大返回值 | Max messages to replay | . | 历史记录返回窗口 | Time window for replay | . | 服务器 | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | 说明 | . | 启用范围测试 | Activate range testing | . | 发送间隔 | Time between test transmissions, chosen from a dropdown of fixed intervals | . | 保存 CSV 到存储 (仅ESP32) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | 说明 | . | 发送设备远程数据 | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | 设备计量更新间隔 | How often to report battery, uptime and channel utilization | . | 启用环境计量模块 | Report the attached environment sensors | . | 环境计量更新间隔 | How often to report them | . | 屏幕显示环境指标 | Also show these readings on the device’s own display | . | 环境测量值使用华氏度 | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | 启用空气质量计量模块 | Report particulate and CO₂ sensor data | . | 空气质量计量更新间隔 | How often to report them | . | 启用电源计量模块 | Report the per-channel voltage and current readings | . | 电量计更新间隔 | How often to report them | . | 在屏幕上启用电源指标 | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | 说明 | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | 消息 | Newline-separated list of messages | . | 发送响铃 | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | 启用旋转编码器 #1 | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | 启用Up/Down/select 输入 | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | 说明 | . | 启用CODEC2 | Activate audio module | . | CODEC2 采样率 | Audio quality/bandwidth tradeoff | . | PTT 引脚 | GPIO pin for the push-to-talk button | . | I2S 字选择 | GPIO pin for I2S WS | . | I2S 数据 IN | GPIO pin for I2S DIN | . | I2S 数据 OUT | GPIO pin for I2S DOUT | . | I2S 时钟 | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | 说明 | . | 启用远程硬件 | Activate remote GPIO access | . | 允许未定义的引脚访问 | Allow access to any GPIO pin (security risk) | . | 可用引脚 | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | 说明 | . | 启用邻居信息 | Activate neighbor broadcasting | . | GPS 轮询间隔 | How often to broadcast neighbor list | . | 通过 LoRa 传输 | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | 说明 | . | LED 状态 | Turn the LED on or off | . | 电流 | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | 说明 | . | 启用检测传感器 | Activate detection sensor | . | 显示器的 GPIO 引脚 | GPIO pin connected to sensor | . | 检测触发器类型 | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | 使用 输入上拉 模式 | Enable the pin’s internal pull-up resistor | . | Minimum time between detection broadcasts | Minimum time between alert broadcasts | . | State Broadcast Interval | Periodic state broadcast interval | . | 发送带有警报消息的响铃声 | Include bell character in alerts | . | 友好名称 | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | 说明 | . | 启用 Paxcount | Activate people counting | . | GPS 轮询间隔 | How often to report counts | . | WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ", "url": "/Meshtastic-Android/main/zh-rCN/user/settings-module-admin.html#%E6%A8%A1%E5%9D%97%E8%AE%BE%E5%AE%9A", "relUrl": "/zh-rCN/user/settings-module-admin.html#模块设定" @@ -30738,7 +30738,7 @@ },"4391": { "doc": "Settings — Modules & Admin", "title": "Konfigurimi i modulit", - "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Përshkrimi | . | MQTT enabled | Toggle MQTT bridge | . | Address | MQTT broker address | . | Username | Authentication username | . | Password | Authentication password | . | Encryption enabled | Encrypt MQTT payloads | . | JSON output enabled | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS enabled | Use secure connection | . | Root topic | Base MQTT topic path | . | Proxy to client enabled | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Map reporting | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Përshkrimi | . | I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Map reporting interval (seconds) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Përshkrimi | . | Serial enabled | Activate serial communication | . | Echo enabled | Echo received serial data back | . | Serial mode | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Serial baud rate | Port speed | . | Koha e skaduar | How long to wait before considering an incoming message complete | . | Override console serial port | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Përshkrimi | . | External notification enabled | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Output LED (GPIO) | Pin the LED is wired to | . | Output LED active high | Whether the LED pin is active high or low | . | Output buzzer (GPIO) | Pin the buzzer is wired to | . | Output vibra (GPIO) | Pin the vibration motor is wired to | . | Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Use I2S as buzzer | Send the alert through an I2S audio output instead | . | Output duration (milliseconds) | How long a single alert lasts | . | Nag timeout (seconds) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Përshkrimi | . | Store & Forward enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | Number of records | Maximum stored messages | . | History return max | Max messages to replay | . | History return window | Time window for replay | . | Server | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Përshkrimi | . | Range test enabled | Activate range testing | . | Sender message interval (seconds) | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Save .CSV in storage (ESP32 only) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Përshkrimi | . | Send Device Telemetry | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Device metrics update interval | How often to report battery, uptime and channel utilization | . | Environment metrics module enabled | Report the attached environment sensors | . | Environment metrics update interval | How often to report them | . | Environment metrics on-screen enabled | Also show these readings on the device’s own display | . | Environment metrics use Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Air quality metrics module enabled | Report particulate and CO₂ sensor data | . | Air quality metrics update interval | How often to report them | . | Power metrics module enabled | Report the per-channel voltage and current readings | . | Power metrics update interval | How often to report them | . | Power metrics on-screen enabled | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Përshkrimi | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | 訊息 | Newline-separated list of messages | . | Send bell | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Rotary encoder #1 enabled | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Up/Down/Select input enabled | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Përshkrimi | . | CODEC 2 enabled | Activate audio module | . | CODEC2 sample rate | Audio quality/bandwidth tradeoff | . | PTT pin | GPIO pin for the push-to-talk button | . | I2S word select | GPIO pin for I2S WS | . | I2S data in | GPIO pin for I2S DIN | . | I2S data out | GPIO pin for I2S DOUT | . | I2S clock | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Përshkrimi | . | Remote Hardware enabled | Activate remote GPIO access | . | Allow undefined pin access | Allow access to any GPIO pin (security risk) | . | Available pins | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Përshkrimi | . | Neighbor Info enabled | Activate neighbor broadcasting | . | Update interval (seconds) | How often to broadcast neighbor list | . | Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Përshkrimi | . | LED state | Turn the LED on or off | . | Current | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Përshkrimi | . | Detection Sensor enabled | Activate detection sensor | . | GPIO pin to monitor | GPIO pin connected to sensor | . | Detection trigger type | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Use INPUT_PULLUP mode | Enable the pin’s internal pull-up resistor | . | Minimum broadcast (seconds) | Minimum time between alert broadcasts | . | State broadcast (seconds) | Periodic state broadcast interval | . | Send bell with alert message | Include bell character in alerts | . | Friendly name | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Përshkrimi | . | Paxcounter enabled | Activate people counting | . | Update interval (seconds) | How often to report counts | . | Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ", + "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Përshkrimi | . | MQTT enabled | Toggle MQTT bridge | . | Address | MQTT broker address | . | Username | Authentication username | . | Password | Authentication password | . | Encryption enabled | Encrypt MQTT payloads | . | JSON output enabled | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS enabled | Use secure connection | . | Root topic | Base MQTT topic path | . | Proxy to client enabled | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Map reporting | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Përshkrimi | . | I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Përshkrimi | . | Serial enabled | Activate serial communication | . | Echo enabled | Echo received serial data back | . | Serial mode | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Serial baud rate | Port speed | . | Koha e skaduar | How long to wait before considering an incoming message complete | . | Override console serial port | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Përshkrimi | . | External notification enabled | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Output LED (GPIO) | Pin the LED is wired to | . | Output LED active high | Whether the LED pin is active high or low | . | Output buzzer (GPIO) | Pin the buzzer is wired to | . | Output vibra (GPIO) | Pin the vibration motor is wired to | . | Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Use I2S as buzzer | Send the alert through an I2S audio output instead | . | GPIO Output Duration | How long a single alert lasts | . | Nag Timeout | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Përshkrimi | . | Store & Forward enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | Number of records | Maximum stored messages | . | History return max | Max messages to replay | . | History return window | Time window for replay | . | Server | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Përshkrimi | . | Range test enabled | Activate range testing | . | Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Save .CSV in storage (ESP32 only) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Përshkrimi | . | Send Device Telemetry | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Device metrics update interval | How often to report battery, uptime and channel utilization | . | Environment metrics module enabled | Report the attached environment sensors | . | Environment metrics update interval | How often to report them | . | Environment metrics on-screen enabled | Also show these readings on the device’s own display | . | Environment metrics use Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Air quality metrics module enabled | Report particulate and CO₂ sensor data | . | Air quality metrics update interval | How often to report them | . | Power metrics module enabled | Report the per-channel voltage and current readings | . | Power metrics update interval | How often to report them | . | Power metrics on-screen enabled | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Përshkrimi | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | 訊息 | Newline-separated list of messages | . | Send bell | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Rotary encoder #1 enabled | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Up/Down/Select input enabled | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Përshkrimi | . | CODEC 2 enabled | Activate audio module | . | CODEC2 sample rate | Audio quality/bandwidth tradeoff | . | PTT pin | GPIO pin for the push-to-talk button | . | I2S word select | GPIO pin for I2S WS | . | I2S data in | GPIO pin for I2S DIN | . | I2S data out | GPIO pin for I2S DOUT | . | I2S clock | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Përshkrimi | . | Remote Hardware enabled | Activate remote GPIO access | . | Allow undefined pin access | Allow access to any GPIO pin (security risk) | . | Available pins | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Përshkrimi | . | Neighbor Info enabled | Activate neighbor broadcasting | . | Update Interval | How often to broadcast neighbor list | . | Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Përshkrimi | . | LED state | Turn the LED on or off | . | Current | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Përshkrimi | . | Detection Sensor enabled | Activate detection sensor | . | GPIO pin to monitor | GPIO pin connected to sensor | . | Detection trigger type | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Use INPUT_PULLUP mode | Enable the pin’s internal pull-up resistor | . | Minimum time between detection broadcasts | Minimum time between alert broadcasts | . | State Broadcast Interval | Periodic state broadcast interval | . | Send bell with alert message | Include bell character in alerts | . | Friendly name | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Përshkrimi | . | Paxcounter enabled | Activate people counting | . | Update Interval | How often to report counts | . | WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ", "url": "/Meshtastic-Android/main/sq-rAL/user/settings-module-admin.html#konfigurimi-i-modulit", "relUrl": "/sq-rAL/user/settings-module-admin.html#konfigurimi-i-modulit" @@ -30773,7 +30773,7 @@ },"4396": { "doc": "Settings — Modules & Admin", "title": "模組設定", - "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | 設定 | 描述說明 | . | 啟用MQTT服務器 | Toggle MQTT bridge | . | 地址 | MQTT broker address | . | 使用者名稱 | Authentication username | . | 密碼 | Authentication password | . | 加密已啟用 | Encrypt MQTT payloads | . | JSON輸出已啟用 | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS已啟用 | Use secure connection | . | 根話題 | Base MQTT topic path | . | 啟用對客戶端的代理 | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | 地圖報告 | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | 設定 | 描述說明 | . | 我同意。 | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | 地圖報告間隔（秒） | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | 設定 | 描述說明 | . | 啟用序列埠 | Activate serial communication | . | 啟用 Echo | Echo received serial data back | . | 序列埠模式 | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | 序列埠鮑率 | Port speed | . | Timeout - 超時 | How long to wait before considering an incoming message complete | . | 覆蓋控制台序列埠 | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | 設定 | 描述說明 | . | 啟用外部通知 | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | 輸出LED（GPIO） | Pin the LED is wired to | . | 輸出LED 高電平觸發 | Whether the LED pin is active high or low | . | 輸出蜂鳴（GPIO） | Pin the buzzer is wired to | . | 輸出振動（GPIO） | Pin the vibration motor is wired to | . | 使用PWM調製的蜂鳴 | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | 使用 I2S 控制蜂鳴器 | Send the alert through an I2S audio output instead | . | 輸出持續時間（毫秒） | How long a single alert lasts | . | 通知逾時時間（秒） | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | 鈴聲 | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | 設定 | 描述說明 | . | 啟用儲存並轉發 | Activate store and forward | . | 心跳 | Periodically announce this node’s store-and-forward capability | . | 紀錄數目 | Maximum stored messages | . | 歴史紀錄最大返回值 | Max messages to replay | . | 歴史紀錄返回視窗 | Time window for replay | . | 伺服器 | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | 設定 | 描述說明 | . | 啟用範圍測試 | Activate range testing | . | 訊息發送間隔(秒) | Time between test transmissions, chosen from a dropdown of fixed intervals | . | 將 .CSV 保存到內部儲存空間(僅限ESP32) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | 設定 | 描述說明 | . | 傳送裝置遙測資料 | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | 裝置資訊更新間隔 | How often to report battery, uptime and channel utilization | . | 啟用環境資訊模組 | Report the attached environment sensors | . | 環境資訊更新間隔 | How often to report them | . | 在螢幕上顯示環境資訊 | Also show these readings on the device’s own display | . | 環境指標以華氏溫度顯示 | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | 啟用空氣品質模組 | Report particulate and CO₂ sensor data | . | 空氣品質資訊更新間隔 | How often to report them | . | 啟用電池資訊模組 | Report the per-channel voltage and current readings | . | 電源資訊更新間隔 | How often to report them | . | 在螢幕上顯示電量資訊 | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | 設定 | 描述說明 | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | 訊息 | Newline-separated list of messages | . | 發送振鈴 | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | 啟用旋轉編碼器#1 | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | 啟用上下選擇輸入 | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | 設定 | 描述說明 | . | 啟用 CODEC 2 | Activate audio module | . | CODEC2 取樣率 | Audio quality/bandwidth tradeoff | . | PTT針腳 | GPIO pin for the push-to-talk button | . | I2S WS 訊號選擇 | GPIO pin for I2S WS | . | I2S 數據輸入 | GPIO pin for I2S DIN | . | I2S 數據輸出 | GPIO pin for I2S DOUT | . | I2S 時鐘 | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | 設定 | 描述說明 | . | 啟動遠端硬體 | Activate remote GPIO access | . | 允許未定義腳位連接 | Allow access to any GPIO pin (security risk) | . | 可用腳位 | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | 設定 | 描述說明 | . | 啟用鄰居資訊 | Activate neighbor broadcasting | . | 更新間隔（秒） | How often to broadcast neighbor list | . | 通過Lora無線電傳輸 | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | 設定 | 描述說明 | . | LED狀態 | Turn the LED on or off | . | 目前 | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | 設定 | 描述說明 | . | 啟用偵測感測器 | Activate detection sensor | . | 螢幕的 GPIO 腳位 | GPIO pin connected to sensor | . | 偵測觸發類型 | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | 使用輸入上拉模式 | Enable the pin’s internal pull-up resistor | . | 最短廣播間隔 (秒) | Minimum time between alert broadcasts | . | 狀態廣播間隔 (秒) | Periodic state broadcast interval | . | 告警訊息發送提示音 | Include bell character in alerts | . | 顯示名稱 | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | 設定 | 描述說明 | . | 已啟用人流計數（Paxcount） | Activate people counting | . | 更新間隔（秒） | How often to report counts | . | Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ", + "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | 設定 | 描述說明 | . | 啟用MQTT服務器 | Toggle MQTT bridge | . | 地址 | MQTT broker address | . | 使用者名稱 | Authentication username | . | 密碼 | Authentication password | . | 加密已啟用 | Encrypt MQTT payloads | . | JSON輸出已啟用 | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS已啟用 | Use secure connection | . | 根話題 | Base MQTT topic path | . | 啟用對客戶端的代理 | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | 地圖報告 | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | 設定 | 描述說明 | . | 我同意。 | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | 設定 | 描述說明 | . | 啟用序列埠 | Activate serial communication | . | 啟用 Echo | Echo received serial data back | . | 序列埠模式 | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | 序列埠鮑率 | Port speed | . | Timeout - 超時 | How long to wait before considering an incoming message complete | . | 覆蓋控制台序列埠 | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | 設定 | 描述說明 | . | 啟用外部通知 | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | 輸出LED（GPIO） | Pin the LED is wired to | . | 輸出LED 高電平觸發 | Whether the LED pin is active high or low | . | 輸出蜂鳴（GPIO） | Pin the buzzer is wired to | . | 輸出振動（GPIO） | Pin the vibration motor is wired to | . | 使用PWM調製的蜂鳴 | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | 使用 I2S 控制蜂鳴器 | Send the alert through an I2S audio output instead | . | GPIO Output Duration | How long a single alert lasts | . | 持續提醒逾時 | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | 鈴聲 | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | 設定 | 描述說明 | . | 啟用儲存並轉發 | Activate store and forward | . | 心跳 | Periodically announce this node’s store-and-forward capability | . | 紀錄數目 | Maximum stored messages | . | 歴史紀錄最大返回值 | Max messages to replay | . | 歴史紀錄返回視窗 | Time window for replay | . | 伺服器 | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | 設定 | 描述說明 | . | 啟用範圍測試 | Activate range testing | . | 傳送間隔 | Time between test transmissions, chosen from a dropdown of fixed intervals | . | 將 .CSV 保存到內部儲存空間(僅限ESP32) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | 設定 | 描述說明 | . | 傳送裝置遙測資料 | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | 裝置資訊更新間隔 | How often to report battery, uptime and channel utilization | . | 啟用環境資訊模組 | Report the attached environment sensors | . | 環境資訊更新間隔 | How often to report them | . | 在螢幕上顯示環境資訊 | Also show these readings on the device’s own display | . | 環境指標以華氏溫度顯示 | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | 啟用空氣品質模組 | Report particulate and CO₂ sensor data | . | 空氣品質資訊更新間隔 | How often to report them | . | 啟用電池資訊模組 | Report the per-channel voltage and current readings | . | 電源資訊更新間隔 | How often to report them | . | 在螢幕上顯示電量資訊 | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | 設定 | 描述說明 | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | 訊息 | Newline-separated list of messages | . | 發送振鈴 | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | 啟用旋轉編碼器#1 | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | 啟用上下選擇輸入 | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | 設定 | 描述說明 | . | 啟用 CODEC 2 | Activate audio module | . | CODEC2 取樣率 | Audio quality/bandwidth tradeoff | . | PTT針腳 | GPIO pin for the push-to-talk button | . | I2S WS 訊號選擇 | GPIO pin for I2S WS | . | I2S 數據輸入 | GPIO pin for I2S DIN | . | I2S 數據輸出 | GPIO pin for I2S DOUT | . | I2S 時鐘 | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | 設定 | 描述說明 | . | 啟動遠端硬體 | Activate remote GPIO access | . | 允許未定義腳位連接 | Allow access to any GPIO pin (security risk) | . | 可用腳位 | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | 設定 | 描述說明 | . | 啟用鄰居資訊 | Activate neighbor broadcasting | . | GPS 輪詢間隔 | How often to broadcast neighbor list | . | 通過Lora無線電傳輸 | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | 設定 | 描述說明 | . | LED狀態 | Turn the LED on or off | . | 目前 | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | 設定 | 描述說明 | . | 啟用偵測感測器 | Activate detection sensor | . | 螢幕的 GPIO 腳位 | GPIO pin connected to sensor | . | 偵測觸發類型 | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | 使用輸入上拉模式 | Enable the pin’s internal pull-up resistor | . | Minimum time between detection broadcasts | Minimum time between alert broadcasts | . | 狀態廣播間隔 | Periodic state broadcast interval | . | 告警訊息發送提示音 | Include bell character in alerts | . | 顯示名稱 | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | 設定 | 描述說明 | . | 已啟用人流計數（Paxcount） | Activate people counting | . | GPS 輪詢間隔 | How often to report counts | . | WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ", "url": "/Meshtastic-Android/main/zh-rTW/user/settings-module-admin.html#%E6%A8%A1%E7%B5%84%E8%A8%AD%E5%AE%9A", "relUrl": "/zh-rTW/user/settings-module-admin.html#模組設定" @@ -30808,7 +30808,7 @@ },"4401": { "doc": "Sätted - moodulid & admin", "title": "Mooduli sätted", - "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Sildab võrgusõnumeid MQTT vahendajasse ja sealt internetiühenduse loomiseks. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Sätted | Kirjeldus | . | MQTT lubatud | Lükka MQTT sild sisse | . | Aadress | MQTT vahendaja aadress | . | Kasutajatunnus | Authentication username | . | Parool | Authentication password | . | Krüpteerimine lubatud | Krüpteeri MQTT kasutus | . | JSON väljund lubatud | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS lubatud | Use secure connection | . | Juurteema | Baas MQTT teema teekond | . | Kliendi proksi lubatud | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | Selle telefoni MQTT puhverserver | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Kaardi raport | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Sätted | Kirjeldus | . | Nõustun. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Kaardi raporti sagedus (sekund) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . Vaata MQTT üksikasjalikumat kasutusjuhendit, mis sisaldab teavet krüpteerimise, privaatsuse ja vahendaja seadistamise kohta,. Serial module . Võimaldab jadapordi sidet väliste seadmete integreerimiseks (GPS-moodulid, andurid või kohandatud riistvara). Kui lubatud, saab sõlme jadaühendus saata ja vastu võtta protobuf- või tekstiandmeid, võimaldades välistel mikrokontrolleritel või arvutitel võrguga suhelda. | Sätted | Kirjeldus | . | Jadaport lubatud | Aktiveeri jadapordi ühendus | . | Kaja lubatud | Kaja sai jadaandmed tagasi | . | Jadapordi režiim | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Jadapordi kiirus | Port speed | . | Aegunud | How long to wait before considering an incoming message complete | . | Konsooli jadapordi alistamine | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Kasulik seadmetele, mis peavad sõnumi saabumisest füüsiliselt märku andma – eriti kasulik järelevalveta või välistingimustes paigaldamise korral. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Sätted | Kirjeldus | . | Luba Välised teated | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Väljund LED (GPIO) | Pin the LED is wired to | . | Väljund LED aktiivne | Whether the LED pin is active high or low | . | Väljund summer (GPIO) | Pin the buzzer is wired to | . | Väljund värin (GPIO) | Pin the vibration motor is wired to | . | Kasuta PWM summerit | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Kasuta I2S summerina | Send the alert through an I2S audio output instead | . | Väljundi kestvus (millisekundit) | How long a single alert lasts | . | Häire ajalõpp (sekundit) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Helin | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Puhverdab ajutiselt võrguühenduseta olnud sõlmede sõnumeid ja esitab need uuesti, kui need sõlmed taasühenduvad. Hädavajalik kärgvõrgu jaoks, kus sõlmed regulaarselt levialasse lähevad ja levialast välja lähevad — tagab, et lühikeste katkestuste ajal sõnumid kaotsi ei lähe. | Sätted | Kirjeldus | . | Salvesta & Edasta lubatud | Aktiveeri salvesta ja saada | . | Südamelöögid | Periodically announce this node’s store-and-forward capability | . | Kirjete arv | Maximum stored messages | . | Ajalookirjete maksimaalne arv | Max messages to replay | . | Ajalookirjete aken | Time window for replay | . | Server | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Vihje: Salvesta ja edasta töötab kõige paremini rohke mäluga sõlmedes (ESP32 koos PSRAM-iga). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automatiseeritud vahemiku testimise tööriist sõlmede vahelise ühenduse kvaliteedi hindamiseks. Kui lubatud, edastab sõlm perioodiliselt testsõnumeid kasvavate loenduritega. Vastuvõtusõlm logib need sõnumid, võimaldades kõndida või minema sõita ning hiljem analüüsida, millisel kaugusel sõnumite saabumine lakkas. | Sätted | Kirjeldus | . | Ulatustest lubatud | Aktiveeri levi test | . | Saatja sõnumi sagedus (sekundit) | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Salvesta .CSV faili (ainult ESP32) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Juhib, milliseid telemeetriaandmeid sõlm võrguga jagab. Telemeetria sisaldab seadme tervist (aku, tööaeg) ja keskkonnaandurite andmeid (temperatuur, niiskus, rõhk). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Sätted | Kirjeldus | . | Saada seadme telemeetria | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Seadme mõõdikute värskendamise intervall | How often to report battery, uptime and channel utilization | . | Keskkonnamõõdikute lubamine | Report the attached environment sensors | . | Keskkonnamõõdikute värskendamise intervall | How often to report them | . | Keskkonnamõõdikute ekraanil kuvamine lubatud | Also show these readings on the device’s own display | . | Keskkonnamõõdikud kasutavad Fahrenheiti | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Õhukvaliteedi moodul on lubatud | Report particulate and CO₂ sensor data | . | Õhukvaliteedi näidikute värskendamise intervall | How often to report them | . | Toitemõõdiku moodul on lubatud | Report the per-channel voltage and current readings | . | Toitemõõdikute värskendamise intervall | How often to report them | . | Toitemõõdiku ekraanil kuvamine lubatud | Also show power readings on the device’s display | . Vaata Telemeetria & Sensorid toetatud andurite ja sätete soovituste kohta. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Määra nimekiri kiirsõnumitest, mida saab edastada ilma telefoni ühendamata – ideaalne välitöödeks. | Sätted | Kirjeldus | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Sõnumid | Reavahetusega eraldatud sõnumite loend | . | Saada Kõll | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Pöördvalik #1 lubatud | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Üles/Alla/Vali sisend lubatud | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. See on eksperimentaalne funktsioon, mis kodeerib hääle Codec2 koodeki abil väga väikesteks andmepakettideks. | Sätted | Kirjeldus | . | CODEC 2 lubatud | Aktiveeri audio moodul | . | CODEC2 test sagedus | Audio quality/bandwidth tradeoff | . | PTT klemm | GPIO pin for the push-to-talk button | . | I2S sõna valik | GPIO sisend I2S WS jaoks | . | I2S info sisse | GPIO sisend I2S DIN jaoks | . | I2S info välja | GPIO sisend I2S DOUT jaoks | . | I2S kell | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO juhtimine kärgvõrgu kaudu. Võimaldab kaugsõlmel lugeda või kirjutada GPIO sisendkontakte teisel sõlmel – kasulik releede aktiveerimiseks, lülitite lugemiseks või välise riistvara kaugjuhtimiseks. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Sätted | Kirjeldus | . | Kaug riistvara lubatud | Aktiveeri kaugjuurdepääs GPIO-le | . | Luba määratlemata klemmi juurdepääs | Luba juurdepääs mis tahes GPIO sisendile (turvarisk) | . | Saadaval klemmid | Kuni 4 GPIO sisendit, mida see sõlm kauglugemiseks/-kirjutamiseks avab | . Neighbor Info module . Levitab teavet otse kuuldud naabrite kohta, võimaldades kärgvõrgu topoloogia kaardistamist. Iga lubatud sõlm jagab perioodiliselt nimekirja teistest sõlmedest, mida ta kuuleb ja nende signaali kvaliteedist. | Sätted | Kirjeldus | . | Naabruskonna teave lubatud | Aktiveeri naabrite leviring | . | Uuenduste sagedus (sekundit) | Kui tihti naabrite nimekirja levitada | . | Saada LoRa kaudu | Edasta naabriinfot ka LoRa kaudu, mitte ainult MQTT/telefoni kaudu. Vaikimisi võtit ja nime kasutavat kanalit pole saadaval | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Juhib toetatud riistvaral NeoPixeli või muid adresseeritavaid RGB LEDe. Saab kasutada visuaalsete olekuindikaatorite, märgutulede või dekoratiivsete efektide jaoks. | Sätted | Kirjeldus | . | LED olek | Turn the LED on or off | . | Pinge | LED current limit (0–31) | . | Punane / Roheline / Sinine | Individuaalsete värvikanalite väärtused (0–255) | . Detection Sensor module . Muudab sõlme liikumis- või ukseanduri hoiatussüsteemiks. Kui GPIO sisend tuvastab oleku muutuse (liikumine tuvastatud, uks avatud), levitab sõlm kärgvõrgu kaudu hoiatusteate. | Sätted | Kirjeldus | . | Tuvastusandur lubatud | Aktiveeri tuvastusandur | . | GPIO klemmi jälgimine | GPIO sisend on anduriga ühendatud | . | Identifitseerimistüüp | Kuidas klemmi olek vastab tuvastussündmusele (nt aktiivne kõrge/madal, serva poolt käivitatav) | . | Kasuta INPUT_PULLUP režiimi | Enable the pin’s internal pull-up resistor | . | Minimaalne edastusaeg (sekund) | Minimaalne aeg hoiatusteadete levitamisel | . | Oleku edastus (sekund) | Perioodilise oleku levitamise intervall | . | Saada kõll koos hoiatussõnumiga | Lisa märguannetesse hoiatuskella sümbol | . | Kasutajasõbralik nimi | Selle anduri kohandatud nimi | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Loendab lähedalasuvaid seadmeid, kuulates passiivselt sondimistaotlusi, mida telefonid ja sülearvutid võrkude skannimisel edastavad. Available only on ESP32 devices. | Sätted | Kirjeldus | . | Paxcounter lubatud | Aktiveeri inimeste loendamine | . | Uuenduste sagedus (sekundit) | Kui tihti loendeid esitada | . | Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Vihje: Paxloendur on kasulik jalakäijate liikluse hindamiseks matkaradade alguses, ürituste toimumiskohtades või muudes kohtades. Arvud on ligikaudsed – üks inimene võib kaasas kanda mitut seadet. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Meeskonna teadlikkuse komplekti integratsioon ATAKi ja WinTAKi koostalitlusvõime tagamiseks. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. Vaata TAK Integration täpsema seadistamise ja kasutamise kohta. ", + "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Sildab võrgusõnumeid MQTT vahendajasse ja sealt internetiühenduse loomiseks. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Sätted | Kirjeldus | . | MQTT lubatud | Lükka MQTT sild sisse | . | Aadress | MQTT vahendaja aadress | . | Kasutajatunnus | Authentication username | . | Parool | Authentication password | . | Krüpteerimine lubatud | Krüpteeri MQTT kasutus | . | JSON väljund lubatud | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS lubatud | Use secure connection | . | Juurteema | Baas MQTT teema teekond | . | Kliendi proksi lubatud | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | Selle telefoni MQTT puhverserver | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Kaardi raport | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Sätted | Kirjeldus | . | Nõustun. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . Vaata MQTT üksikasjalikumat kasutusjuhendit, mis sisaldab teavet krüpteerimise, privaatsuse ja vahendaja seadistamise kohta,. Serial module . Võimaldab jadapordi sidet väliste seadmete integreerimiseks (GPS-moodulid, andurid või kohandatud riistvara). Kui lubatud, saab sõlme jadaühendus saata ja vastu võtta protobuf- või tekstiandmeid, võimaldades välistel mikrokontrolleritel või arvutitel võrguga suhelda. | Sätted | Kirjeldus | . | Jadaport lubatud | Aktiveeri jadapordi ühendus | . | Kaja lubatud | Kaja sai jadaandmed tagasi | . | Jadapordi režiim | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Jadapordi kiirus | Port speed | . | Aegunud | How long to wait before considering an incoming message complete | . | Konsooli jadapordi alistamine | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Kasulik seadmetele, mis peavad sõnumi saabumisest füüsiliselt märku andma – eriti kasulik järelevalveta või välistingimustes paigaldamise korral. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Sätted | Kirjeldus | . | Luba Välised teated | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Väljund LED (GPIO) | Pin the LED is wired to | . | Väljund LED aktiivne | Whether the LED pin is active high or low | . | Väljund summer (GPIO) | Pin the buzzer is wired to | . | Väljund värin (GPIO) | Pin the vibration motor is wired to | . | Kasuta PWM summerit | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Kasuta I2S summerina | Send the alert through an I2S audio output instead | . | GPIO Output Duration | How long a single alert lasts | . | Nag Timeout | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Helin | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Puhverdab ajutiselt võrguühenduseta olnud sõlmede sõnumeid ja esitab need uuesti, kui need sõlmed taasühenduvad. Hädavajalik kärgvõrgu jaoks, kus sõlmed regulaarselt levialasse lähevad ja levialast välja lähevad — tagab, et lühikeste katkestuste ajal sõnumid kaotsi ei lähe. | Sätted | Kirjeldus | . | Salvesta & Edasta lubatud | Aktiveeri salvesta ja saada | . | Südamelöögid | Periodically announce this node’s store-and-forward capability | . | Kirjete arv | Maximum stored messages | . | Ajalookirjete maksimaalne arv | Max messages to replay | . | Ajalookirjete aken | Time window for replay | . | Server | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Vihje: Salvesta ja edasta töötab kõige paremini rohke mäluga sõlmedes (ESP32 koos PSRAM-iga). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automatiseeritud vahemiku testimise tööriist sõlmede vahelise ühenduse kvaliteedi hindamiseks. Kui lubatud, edastab sõlm perioodiliselt testsõnumeid kasvavate loenduritega. Vastuvõtusõlm logib need sõnumid, võimaldades kõndida või minema sõita ning hiljem analüüsida, millisel kaugusel sõnumite saabumine lakkas. | Sätted | Kirjeldus | . | Ulatustest lubatud | Aktiveeri levi test | . | Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Salvesta .CSV faili (ainult ESP32) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Juhib, milliseid telemeetriaandmeid sõlm võrguga jagab. Telemeetria sisaldab seadme tervist (aku, tööaeg) ja keskkonnaandurite andmeid (temperatuur, niiskus, rõhk). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Sätted | Kirjeldus | . | Saada seadme telemeetria | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Seadme mõõdikute värskendamise intervall | How often to report battery, uptime and channel utilization | . | Keskkonnamõõdikute lubamine | Report the attached environment sensors | . | Keskkonnamõõdikute värskendamise intervall | How often to report them | . | Keskkonnamõõdikute ekraanil kuvamine lubatud | Also show these readings on the device’s own display | . | Keskkonnamõõdikud kasutavad Fahrenheiti | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Õhukvaliteedi moodul on lubatud | Report particulate and CO₂ sensor data | . | Õhukvaliteedi näidikute värskendamise intervall | How often to report them | . | Toitemõõdiku moodul on lubatud | Report the per-channel voltage and current readings | . | Toitemõõdikute värskendamise intervall | How often to report them | . | Toitemõõdiku ekraanil kuvamine lubatud | Also show power readings on the device’s display | . Vaata Telemeetria & Sensorid toetatud andurite ja sätete soovituste kohta. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Määra nimekiri kiirsõnumitest, mida saab edastada ilma telefoni ühendamata – ideaalne välitöödeks. | Sätted | Kirjeldus | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Sõnumid | Reavahetusega eraldatud sõnumite loend | . | Saada Kõll | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Pöördvalik #1 lubatud | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Üles/Alla/Vali sisend lubatud | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. See on eksperimentaalne funktsioon, mis kodeerib hääle Codec2 koodeki abil väga väikesteks andmepakettideks. | Sätted | Kirjeldus | . | CODEC 2 lubatud | Aktiveeri audio moodul | . | CODEC2 test sagedus | Audio quality/bandwidth tradeoff | . | PTT klemm | GPIO pin for the push-to-talk button | . | I2S sõna valik | GPIO sisend I2S WS jaoks | . | I2S info sisse | GPIO sisend I2S DIN jaoks | . | I2S info välja | GPIO sisend I2S DOUT jaoks | . | I2S kell | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO juhtimine kärgvõrgu kaudu. Võimaldab kaugsõlmel lugeda või kirjutada GPIO sisendkontakte teisel sõlmel – kasulik releede aktiveerimiseks, lülitite lugemiseks või välise riistvara kaugjuhtimiseks. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Sätted | Kirjeldus | . | Kaug riistvara lubatud | Aktiveeri kaugjuurdepääs GPIO-le | . | Luba määratlemata klemmi juurdepääs | Luba juurdepääs mis tahes GPIO sisendile (turvarisk) | . | Saadaval klemmid | Kuni 4 GPIO sisendit, mida see sõlm kauglugemiseks/-kirjutamiseks avab | . Neighbor Info module . Levitab teavet otse kuuldud naabrite kohta, võimaldades kärgvõrgu topoloogia kaardistamist. Iga lubatud sõlm jagab perioodiliselt nimekirja teistest sõlmedest, mida ta kuuleb ja nende signaali kvaliteedist. | Sätted | Kirjeldus | . | Naabruskonna teave lubatud | Aktiveeri naabrite leviring | . | GPS-i küsimise intervall | Kui tihti naabrite nimekirja levitada | . | Saada LoRa kaudu | Edasta naabriinfot ka LoRa kaudu, mitte ainult MQTT/telefoni kaudu. Vaikimisi võtit ja nime kasutavat kanalit pole saadaval | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Juhib toetatud riistvaral NeoPixeli või muid adresseeritavaid RGB LEDe. Saab kasutada visuaalsete olekuindikaatorite, märgutulede või dekoratiivsete efektide jaoks. | Sätted | Kirjeldus | . | LED olek | Turn the LED on or off | . | Pinge | LED current limit (0–31) | . | Punane / Roheline / Sinine | Individuaalsete värvikanalite väärtused (0–255) | . Detection Sensor module . Muudab sõlme liikumis- või ukseanduri hoiatussüsteemiks. Kui GPIO sisend tuvastab oleku muutuse (liikumine tuvastatud, uks avatud), levitab sõlm kärgvõrgu kaudu hoiatusteate. | Sätted | Kirjeldus | . | Tuvastusandur lubatud | Aktiveeri tuvastusandur | . | GPIO klemmi jälgimine | GPIO sisend on anduriga ühendatud | . | Identifitseerimistüüp | Kuidas klemmi olek vastab tuvastussündmusele (nt aktiivne kõrge/madal, serva poolt käivitatav) | . | Kasuta INPUT_PULLUP režiimi | Enable the pin’s internal pull-up resistor | . | Minimum time between detection broadcasts | Minimaalne aeg hoiatusteadete levitamisel | . | State Broadcast Interval | Perioodilise oleku levitamise intervall | . | Saada kõll koos hoiatussõnumiga | Lisa märguannetesse hoiatuskella sümbol | . | Kasutajasõbralik nimi | Selle anduri kohandatud nimi | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Loendab lähedalasuvaid seadmeid, kuulates passiivselt sondimistaotlusi, mida telefonid ja sülearvutid võrkude skannimisel edastavad. Available only on ESP32 devices. | Sätted | Kirjeldus | . | Paxcounter lubatud | Aktiveeri inimeste loendamine | . | GPS-i küsimise intervall | Kui tihti loendeid esitada | . | WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Vihje: Paxloendur on kasulik jalakäijate liikluse hindamiseks matkaradade alguses, ürituste toimumiskohtades või muudes kohtades. Arvud on ligikaudsed – üks inimene võib kaasas kanda mitut seadet. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Meeskonna teadlikkuse komplekti integratsioon ATAKi ja WinTAKi koostalitlusvõime tagamiseks. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. Vaata TAK Integration täpsema seadistamise ja kasutamise kohta. ", "url": "/Meshtastic-Android/main/et-rEE/user/settings-module-admin.html#mooduli-s%C3%A4tted", "relUrl": "/et-rEE/user/settings-module-admin.html#mooduli-sätted" @@ -30843,7 +30843,7 @@ },"4406": { "doc": "Settings — Modules & Admin", "title": "Réglages du module", - "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Description | . | MQTT activé | Toggle MQTT bridge | . | Adresse | MQTT broker address | . | Nom d’utilisateur | Authentication username | . | Mot de passe | Authentication password | . | Chiffrement activé | Encrypt MQTT payloads | . | Sortie JSON activée | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS activé | Use secure connection | . | Sujet principal | Base MQTT topic path | . | Proxy pour le client activé | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Rapport cartographique | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Description | . | J’accepte. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Intervalle de rapport cartographique (secondes) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Description | . | Série activée | Activate serial communication | . | Écho activé | Echo received serial data back | . | Mode série | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Vitesse de transmission série | Port speed | . | Délai d’expiration | How long to wait before considering an incoming message complete | . | Outrepasser le port série de la console | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Description | . | Notifications externes activées | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | LED extérieure (GPIO) | Pin the LED is wired to | . | Sortie LED active à l’état haut | Whether the LED pin is active high or low | . | Buzzer extérieur (GPIO) | Pin the buzzer is wired to | . | Sortie vibreur (GPIO) | Pin the vibration motor is wired to | . | Utiliser le buzzer PWM | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Utiliser l’I2S comme buzzer | Send the alert through an I2S audio output instead | . | Durée de sortie (en millisecondes) | How long a single alert lasts | . | Durée de répétition de la sortie (secondes) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Sonnerie | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Description | . | Stocker & Transférer activé | Activate store and forward | . | Battement de cœur (heartbeat) | Periodically announce this node’s store-and-forward capability | . | Nombre d’enregistrements | Maximum stored messages | . | Limite d’historique renvoyé | Max messages to replay | . | Fenêtre de retour d’historique | Time window for replay | . | Serveur | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Description | . | Test de portée activé | Activate range testing | . | Intervalle de message de l’expéditeur (secondes) | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Enregistrer .CSV dans le stockage (ESP32 seulement) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Description | . | Envoyer la télémétrie de l’appareil | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Intervalle de mise à jour des mesures | How often to report battery, uptime and channel utilization | . | Module de métriques de l’environnement activé | Report the attached environment sensors | . | Intervalle de mise à jour des mesures d’environnement | How often to report them | . | Mesures d’environnement à l’écran activées | Also show these readings on the device’s own display | . | Les mesures environnementales utilisent Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Module de mesure de la qualité de l’air activé | Report particulate and CO₂ sensor data | . | Intervalle de mise à jour des mesures de qualité d’air | How often to report them | . | Module de mesure de puissance activé | Report the per-channel voltage and current readings | . | Intervalle de mise à jour des mesures d’alimentation | How often to report them | . | Indicateurs d’alimentation à l’écran activés | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Description | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Messages | Newline-separated list of messages | . | Envoyer une sonnerie | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Encodeur rotatif #1 activé | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Entrée Haut/Bas/Select activée | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Description | . | CODEC 2 activé | Activate audio module | . | Taux d’échantillonnage CODEC2 | Audio quality/bandwidth tradeoff | . | Broche PTT | GPIO pin for the push-to-talk button | . | Selection de mot I2S | GPIO pin for I2S WS | . | Données d’entrée I2S | GPIO pin for I2S DIN | . | Données de sortie I2S | GPIO pin for I2S DOUT | . | Horloge I2C | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Description | . | Matériel distant activé | Activate remote GPIO access | . | Autoriser l’accès non défini aux broches | Allow access to any GPIO pin (security risk) | . | Broches disponibles | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Description | . | Infos de voisinage activées | Activate neighbor broadcasting | . | Intervalle de mise à jour (secondes) | How often to broadcast neighbor list | . | Transmettre par LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Description | . | État de la LED | Turn the LED on or off | . | Actif | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Description | . | Capteur de détection activé | Activate detection sensor | . | Broche GPIO à surveiller | GPIO pin connected to sensor | . | Type du déclencheur de détection | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Utiliser le mode INPUT_PULLUP | Enable the pin’s internal pull-up resistor | . | Diffusion minimale (secondes) | Minimum time between alert broadcasts | . | Diffusion de l’État (secondes) | Periodic state broadcast interval | . | Envoyer une sonnerie avec un message d’alerte | Include bell character in alerts | . | Nom convivial | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Paramètre | Description | . | Paxcounter activé | Activate people counting | . | Intervalle de mise à jour (secondes) | How often to report counts | . | Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ", + "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Description | . | MQTT activé | Toggle MQTT bridge | . | Adresse | MQTT broker address | . | Nom d’utilisateur | Authentication username | . | Mot de passe | Authentication password | . | Chiffrement activé | Encrypt MQTT payloads | . | Sortie JSON activée | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS activé | Use secure connection | . | Sujet principal | Base MQTT topic path | . | Proxy pour le client activé | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Rapport cartographique | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Description | . | J’accepte. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Description | . | Série activée | Activate serial communication | . | Écho activé | Echo received serial data back | . | Mode série | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Vitesse de transmission série | Port speed | . | Délai d’expiration | How long to wait before considering an incoming message complete | . | Outrepasser le port série de la console | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Description | . | Notifications externes activées | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | LED extérieure (GPIO) | Pin the LED is wired to | . | Sortie LED active à l’état haut | Whether the LED pin is active high or low | . | Buzzer extérieur (GPIO) | Pin the buzzer is wired to | . | Sortie vibreur (GPIO) | Pin the vibration motor is wired to | . | Utiliser le buzzer PWM | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Utiliser l’I2S comme buzzer | Send the alert through an I2S audio output instead | . | GPIO Output Duration | How long a single alert lasts | . | Délai d’expiration du message | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Sonnerie | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Description | . | Stocker & Transférer activé | Activate store and forward | . | Battement de cœur (heartbeat) | Periodically announce this node’s store-and-forward capability | . | Nombre d’enregistrements | Maximum stored messages | . | Limite d’historique renvoyé | Max messages to replay | . | Fenêtre de retour d’historique | Time window for replay | . | Serveur | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Description | . | Test de portée activé | Activate range testing | . | Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Enregistrer .CSV dans le stockage (ESP32 seulement) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Description | . | Envoyer la télémétrie de l’appareil | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Intervalle de mise à jour des mesures | How often to report battery, uptime and channel utilization | . | Module de métriques de l’environnement activé | Report the attached environment sensors | . | Intervalle de mise à jour des mesures d’environnement | How often to report them | . | Mesures d’environnement à l’écran activées | Also show these readings on the device’s own display | . | Les mesures environnementales utilisent Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Module de mesure de la qualité de l’air activé | Report particulate and CO₂ sensor data | . | Intervalle de mise à jour des mesures de qualité d’air | How often to report them | . | Module de mesure de puissance activé | Report the per-channel voltage and current readings | . | Intervalle de mise à jour des mesures d’alimentation | How often to report them | . | Indicateurs d’alimentation à l’écran activés | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Description | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Messages | Newline-separated list of messages | . | Envoyer une sonnerie | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Encodeur rotatif #1 activé | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Entrée Haut/Bas/Select activée | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Description | . | CODEC 2 activé | Activate audio module | . | Taux d’échantillonnage CODEC2 | Audio quality/bandwidth tradeoff | . | Broche PTT | GPIO pin for the push-to-talk button | . | Selection de mot I2S | GPIO pin for I2S WS | . | Données d’entrée I2S | GPIO pin for I2S DIN | . | Données de sortie I2S | GPIO pin for I2S DOUT | . | Horloge I2C | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Description | . | Matériel distant activé | Activate remote GPIO access | . | Autoriser l’accès non défini aux broches | Allow access to any GPIO pin (security risk) | . | Broches disponibles | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Description | . | Infos de voisinage activées | Activate neighbor broadcasting | . | Fréquence de récupération GPS | How often to broadcast neighbor list | . | Transmettre par LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Description | . | État de la LED | Turn the LED on or off | . | Actif | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Description | . | Capteur de détection activé | Activate detection sensor | . | Broche GPIO à surveiller | GPIO pin connected to sensor | . | Type du déclencheur de détection | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Utiliser le mode INPUT_PULLUP | Enable the pin’s internal pull-up resistor | . | Minimum time between detection broadcasts | Minimum time between alert broadcasts | . | State Broadcast Interval | Periodic state broadcast interval | . | Envoyer une sonnerie avec un message d’alerte | Include bell character in alerts | . | Nom convivial | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Paramètre | Description | . | Paxcounter activé | Activate people counting | . | Fréquence de récupération GPS | How often to report counts | . | WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ", "url": "/Meshtastic-Android/main/fr-rFR/user/settings-module-admin.html#r%C3%A9glages-du-module", "relUrl": "/fr-rFR/user/settings-module-admin.html#réglages-du-module" @@ -30878,7 +30878,7 @@ },"4411": { "doc": "Settings — Modules & Admin", "title": "Modül ayarları", - "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Açıklaması | . | MQTT etkin | Toggle MQTT bridge | . | Adres | MQTT broker address | . | Kullanıcı adı | Authentication username | . | Şifre | Authentication password | . | Şifreleme etkin | Encrypt MQTT payloads | . | JSON çıktısı etkin | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS etkin | Use secure connection | . | Ana konu | Base MQTT topic path | . | Vekilden istemciye etkin | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Harita raporlama | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Açıklaması | . | Katılıyorum. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Harita raporlama aralığı (saniye) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Açıklaması | . | Seri etkin | Activate serial communication | . | Eko etkin | Echo received serial data back | . | Seri modu | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Seri baud hızı | Port speed | . | Zaman Aşımı | How long to wait before considering an incoming message complete | . | Konsol seri portunu geçersiz kıl | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Açıklaması | . | Harici bildirim etkin | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Çıktı LED (GPIO) | Pin the LED is wired to | . | Çıktı LED aktif yüksek | Whether the LED pin is active high or low | . | Çıktı zırnı (GPIO) | Pin the buzzer is wired to | . | Çıktı titreşim (GPIO) | Pin the vibration motor is wired to | . | PWM zırnı kullan | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | I2S’yi zırnı olarak kullan | Send the alert through an I2S audio output instead | . | Çıktı süresi (milisaniye) | How long a single alert lasts | . | Nag zaman aşımı (saniye) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Zil tipi | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Açıklaması | . | Kaydet & Yönlendir etkin | Activate store and forward | . | Kalp atışı | Periodically announce this node’s store-and-forward capability | . | Kayıt sayısı | Maximum stored messages | . | Geçmiş geri dönüş maksimum | Max messages to replay | . | Geçmiş geri dönüş penceresi | Time window for replay | . | Sunucu | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Açıklaması | . | Menzi testi etkin | Activate range testing | . | Gönderen mesaj aralığı (saniye) | Time between test transmissions, chosen from a dropdown of fixed intervals | . | .CSV’yi depolamada kaydet (sadece ESP32) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Açıklaması | . | Send Device Telemetry | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Device metrics update interval | How often to report battery, uptime and channel utilization | . | Çevre metrikleri modülü etkin | Report the attached environment sensors | . | Environment metrics update interval | How often to report them | . | Çevre metrikleri ekran üzerinde etkin | Also show these readings on the device’s own display | . | Çevre metrikleri Fahrenheit kullan | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Hava kalitesi metrikleri modülü etkin | Report particulate and CO₂ sensor data | . | Air quality metrics update interval | How often to report them | . | Güç metrikleri modülü etkin | Report the per-channel voltage and current readings | . | Power metrics update interval | How often to report them | . | Güç metrikleri ekran üzerinde etkin | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Açıklaması | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Mesajlar | Newline-separated list of messages | . | Zil gönder | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Dönen kodlayıcı #1 etkinleştirildi | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Yukarı/Aşağı/Seçme girişi etkinleştirildi | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Açıklaması | . | CODEC 2 etkinleştirildi | Activate audio module | . | CODEC2 örnekleme hızı | Audio quality/bandwidth tradeoff | . | PTT pini | GPIO pin for the push-to-talk button | . | I2S kelime seçimi | GPIO pin for I2S WS | . | I2S veri girişi | GPIO pin for I2S DIN | . | I2S veri çıkışı | GPIO pin for I2S DOUT | . | I2S saati | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Açıklaması | . | Uzak Donanım etkin | Activate remote GPIO access | . | Tanımlanmamış pin erişimine izin ver | Allow access to any GPIO pin (security risk) | . | Mevcut pinler | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Açıklaması | . | Komşu Bilgisi etkin | Activate neighbor broadcasting | . | Güncelleme aralığı (saniye) | How often to broadcast neighbor list | . | LoRa üzerinden ilet | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Açıklaması | . | LED durumu | Turn the LED on or off | . | Akım | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Açıklaması | . | Algılama Sensörü etkinleştirildi | Activate detection sensor | . | İzlenecek GPIO pini | GPIO pin connected to sensor | . | Algılama tetikleme türü | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | INPUT_PULLUP modu kullan | Enable the pin’s internal pull-up resistor | . | Minimum yayın (saniye) | Minimum time between alert broadcasts | . | Durum yayını (saniye) | Periodic state broadcast interval | . | Uyarı mesajı ile zil gönder | Include bell character in alerts | . | Arkadaşça isim | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Açıklaması | . | Pax sayacı etkin | Activate people counting | . | Güncelleme aralığı (saniye) | How often to report counts | . | Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ", + "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Açıklaması | . | MQTT etkin | Toggle MQTT bridge | . | Adres | MQTT broker address | . | Kullanıcı adı | Authentication username | . | Şifre | Authentication password | . | Şifreleme etkin | Encrypt MQTT payloads | . | JSON çıktısı etkin | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS etkin | Use secure connection | . | Ana konu | Base MQTT topic path | . | Vekilden istemciye etkin | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Harita raporlama | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Açıklaması | . | Katılıyorum. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Açıklaması | . | Seri etkin | Activate serial communication | . | Eko etkin | Echo received serial data back | . | Seri modu | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Seri baud hızı | Port speed | . | Zaman Aşımı | How long to wait before considering an incoming message complete | . | Konsol seri portunu geçersiz kıl | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Açıklaması | . | Harici bildirim etkin | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Çıktı LED (GPIO) | Pin the LED is wired to | . | Çıktı LED aktif yüksek | Whether the LED pin is active high or low | . | Çıktı zırnı (GPIO) | Pin the buzzer is wired to | . | Çıktı titreşim (GPIO) | Pin the vibration motor is wired to | . | PWM zırnı kullan | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | I2S’yi zırnı olarak kullan | Send the alert through an I2S audio output instead | . | GPIO Output Duration | How long a single alert lasts | . | Nag Timeout | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Zil tipi | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Açıklaması | . | Kaydet & Yönlendir etkin | Activate store and forward | . | Kalp atışı | Periodically announce this node’s store-and-forward capability | . | Kayıt sayısı | Maximum stored messages | . | Geçmiş geri dönüş maksimum | Max messages to replay | . | Geçmiş geri dönüş penceresi | Time window for replay | . | Sunucu | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Açıklaması | . | Menzi testi etkin | Activate range testing | . | Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals | . | .CSV’yi depolamada kaydet (sadece ESP32) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Açıklaması | . | Send Device Telemetry | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Device metrics update interval | How often to report battery, uptime and channel utilization | . | Çevre metrikleri modülü etkin | Report the attached environment sensors | . | Environment metrics update interval | How often to report them | . | Çevre metrikleri ekran üzerinde etkin | Also show these readings on the device’s own display | . | Çevre metrikleri Fahrenheit kullan | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Hava kalitesi metrikleri modülü etkin | Report particulate and CO₂ sensor data | . | Air quality metrics update interval | How often to report them | . | Güç metrikleri modülü etkin | Report the per-channel voltage and current readings | . | Power metrics update interval | How often to report them | . | Güç metrikleri ekran üzerinde etkin | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Açıklaması | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Mesajlar | Newline-separated list of messages | . | Zil gönder | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Dönen kodlayıcı #1 etkinleştirildi | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Yukarı/Aşağı/Seçme girişi etkinleştirildi | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Açıklaması | . | CODEC 2 etkinleştirildi | Activate audio module | . | CODEC2 örnekleme hızı | Audio quality/bandwidth tradeoff | . | PTT pini | GPIO pin for the push-to-talk button | . | I2S kelime seçimi | GPIO pin for I2S WS | . | I2S veri girişi | GPIO pin for I2S DIN | . | I2S veri çıkışı | GPIO pin for I2S DOUT | . | I2S saati | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Açıklaması | . | Uzak Donanım etkin | Activate remote GPIO access | . | Tanımlanmamış pin erişimine izin ver | Allow access to any GPIO pin (security risk) | . | Mevcut pinler | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Açıklaması | . | Komşu Bilgisi etkin | Activate neighbor broadcasting | . | Update Interval | How often to broadcast neighbor list | . | LoRa üzerinden ilet | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Açıklaması | . | LED durumu | Turn the LED on or off | . | Akım | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Açıklaması | . | Algılama Sensörü etkinleştirildi | Activate detection sensor | . | İzlenecek GPIO pini | GPIO pin connected to sensor | . | Algılama tetikleme türü | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | INPUT_PULLUP modu kullan | Enable the pin’s internal pull-up resistor | . | Minimum time between detection broadcasts | Minimum time between alert broadcasts | . | State Broadcast Interval | Periodic state broadcast interval | . | Uyarı mesajı ile zil gönder | Include bell character in alerts | . | Arkadaşça isim | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Açıklaması | . | Pax sayacı etkin | Activate people counting | . | Update Interval | How often to report counts | . | WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ", "url": "/Meshtastic-Android/main/tr-rTR/user/settings-module-admin.html#mod%C3%BCl-ayarlar%C4%B1", "relUrl": "/tr-rTR/user/settings-module-admin.html#modül-ayarları" @@ -30913,7 +30913,7 @@ },"4416": { "doc": "Settings — Modules & Admin", "title": "Ρυθμίσεις πρόσθετου", - "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Περιγραφή | . | MQTT enabled | Toggle MQTT bridge | . | Διεύθυνση | MQTT broker address | . | Όνομα χρήστη | Authentication username | . | Κωδικός πρόσβασης | Authentication password | . | Encryption enabled | Encrypt MQTT payloads | . | JSON output enabled | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS enabled | Use secure connection | . | Root topic | Base MQTT topic path | . | Proxy to client enabled | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Map reporting | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Περιγραφή | . | I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Map reporting interval (seconds) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Περιγραφή | . | Serial enabled | Activate serial communication | . | Echo enabled | Echo received serial data back | . | Serial mode | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Serial baud rate | Port speed | . | Λήξη χρονικού ορίου | How long to wait before considering an incoming message complete | . | Override console serial port | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Περιγραφή | . | External notification enabled | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Output LED (GPIO) | Pin the LED is wired to | . | Output LED active high | Whether the LED pin is active high or low | . | Output buzzer (GPIO) | Pin the buzzer is wired to | . | Output vibra (GPIO) | Pin the vibration motor is wired to | . | Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Use I2S as buzzer | Send the alert through an I2S audio output instead | . | Output duration (milliseconds) | How long a single alert lasts | . | Nag timeout (seconds) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Περιγραφή | . | Store & Forward enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | Number of records | Maximum stored messages | . | History return max | Max messages to replay | . | History return window | Time window for replay | . | Server | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Περιγραφή | . | Range test enabled | Activate range testing | . | Sender message interval (seconds) | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Save .CSV in storage (ESP32 only) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Περιγραφή | . | Send Device Telemetry | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Device metrics update interval | How often to report battery, uptime and channel utilization | . | Environment metrics module enabled | Report the attached environment sensors | . | Environment metrics update interval | How often to report them | . | Environment metrics on-screen enabled | Also show these readings on the device’s own display | . | Environment metrics use Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Air quality metrics module enabled | Report particulate and CO₂ sensor data | . | Air quality metrics update interval | How often to report them | . | Power metrics module enabled | Report the per-channel voltage and current readings | . | Power metrics update interval | How often to report them | . | Power metrics on-screen enabled | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Περιγραφή | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Μηνύματα | Newline-separated list of messages | . | Send bell | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Rotary encoder #1 enabled | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Up/Down/Select input enabled | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Περιγραφή | . | CODEC 2 enabled | Activate audio module | . | CODEC2 sample rate | Audio quality/bandwidth tradeoff | . | PTT pin | GPIO pin for the push-to-talk button | . | I2S word select | GPIO pin for I2S WS | . | I2S data in | GPIO pin for I2S DIN | . | I2S data out | GPIO pin for I2S DOUT | . | I2S clock | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Περιγραφή | . | Remote Hardware enabled | Activate remote GPIO access | . | Allow undefined pin access | Allow access to any GPIO pin (security risk) | . | Available pins | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Περιγραφή | . | Neighbor Info enabled | Activate neighbor broadcasting | . | Update interval (seconds) | How often to broadcast neighbor list | . | Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Περιγραφή | . | LED state | Turn the LED on or off | . | Current | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Περιγραφή | . | Detection Sensor enabled | Activate detection sensor | . | GPIO pin to monitor | GPIO pin connected to sensor | . | Detection trigger type | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Use INPUT_PULLUP mode | Enable the pin’s internal pull-up resistor | . | Minimum broadcast (seconds) | Minimum time between alert broadcasts | . | State broadcast (seconds) | Periodic state broadcast interval | . | Send bell with alert message | Include bell character in alerts | . | Friendly name | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Περιγραφή | . | Paxcounter enabled | Activate people counting | . | Update interval (seconds) | How often to report counts | . | Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ", + "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Περιγραφή | . | MQTT enabled | Toggle MQTT bridge | . | Διεύθυνση | MQTT broker address | . | Όνομα χρήστη | Authentication username | . | Κωδικός πρόσβασης | Authentication password | . | Encryption enabled | Encrypt MQTT payloads | . | JSON output enabled | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS enabled | Use secure connection | . | Root topic | Base MQTT topic path | . | Proxy to client enabled | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Map reporting | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Περιγραφή | . | I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Περιγραφή | . | Serial enabled | Activate serial communication | . | Echo enabled | Echo received serial data back | . | Serial mode | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Serial baud rate | Port speed | . | Λήξη χρονικού ορίου | How long to wait before considering an incoming message complete | . | Override console serial port | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Περιγραφή | . | External notification enabled | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Output LED (GPIO) | Pin the LED is wired to | . | Output LED active high | Whether the LED pin is active high or low | . | Output buzzer (GPIO) | Pin the buzzer is wired to | . | Output vibra (GPIO) | Pin the vibration motor is wired to | . | Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Use I2S as buzzer | Send the alert through an I2S audio output instead | . | GPIO Output Duration | How long a single alert lasts | . | Nag Timeout | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Περιγραφή | . | Store & Forward enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | Number of records | Maximum stored messages | . | History return max | Max messages to replay | . | History return window | Time window for replay | . | Server | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Περιγραφή | . | Range test enabled | Activate range testing | . | Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Save .CSV in storage (ESP32 only) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Περιγραφή | . | Send Device Telemetry | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Device metrics update interval | How often to report battery, uptime and channel utilization | . | Environment metrics module enabled | Report the attached environment sensors | . | Environment metrics update interval | How often to report them | . | Environment metrics on-screen enabled | Also show these readings on the device’s own display | . | Environment metrics use Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Air quality metrics module enabled | Report particulate and CO₂ sensor data | . | Air quality metrics update interval | How often to report them | . | Power metrics module enabled | Report the per-channel voltage and current readings | . | Power metrics update interval | How often to report them | . | Power metrics on-screen enabled | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Περιγραφή | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Μηνύματα | Newline-separated list of messages | . | Send bell | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Rotary encoder #1 enabled | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Up/Down/Select input enabled | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Περιγραφή | . | CODEC 2 enabled | Activate audio module | . | CODEC2 sample rate | Audio quality/bandwidth tradeoff | . | PTT pin | GPIO pin for the push-to-talk button | . | I2S word select | GPIO pin for I2S WS | . | I2S data in | GPIO pin for I2S DIN | . | I2S data out | GPIO pin for I2S DOUT | . | I2S clock | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Περιγραφή | . | Remote Hardware enabled | Activate remote GPIO access | . | Allow undefined pin access | Allow access to any GPIO pin (security risk) | . | Available pins | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Περιγραφή | . | Neighbor Info enabled | Activate neighbor broadcasting | . | Update Interval | How often to broadcast neighbor list | . | Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Περιγραφή | . | LED state | Turn the LED on or off | . | Current | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Περιγραφή | . | Detection Sensor enabled | Activate detection sensor | . | GPIO pin to monitor | GPIO pin connected to sensor | . | Detection trigger type | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Use INPUT_PULLUP mode | Enable the pin’s internal pull-up resistor | . | Minimum time between detection broadcasts | Minimum time between alert broadcasts | . | State Broadcast Interval | Periodic state broadcast interval | . | Send bell with alert message | Include bell character in alerts | . | Friendly name | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Περιγραφή | . | Paxcounter enabled | Activate people counting | . | Update Interval | How often to report counts | . | WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ", "url": "/Meshtastic-Android/main/el-rGR/user/settings-module-admin.html#%CF%81%CF%85%CE%B8%CE%BC%CE%AF%CF%83%CE%B5%CE%B9%CF%82-%CF%80%CF%81%CF%8C%CF%83%CE%B8%CE%B5%CF%84%CE%BF%CF%85", "relUrl": "/el-rGR/user/settings-module-admin.html#ρυθμίσεις-πρόσθετου" @@ -30948,7 +30948,7 @@ },"4421": { "doc": "Settings — Modules & Admin", "title": "Configurare modul", - "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Descriere | . | MQTT activat | Toggle MQTT bridge | . | Adresă | MQTT broker address | . | Nume de utilizator | Authentication username | . | Parolă | Authentication password | . | Criptare activată | Encrypt MQTT payloads | . | Ieșire JSON activată | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS activat | Use secure connection | . | Temă rădăcină | Base MQTT topic path | . | Proxy-ul pentru client activat | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Raportarea hărții | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Descriere | . | Sunt de acord | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Intervalul de raportare hartă (secunde) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Descriere | . | Serial activat | Activate serial communication | . | Echo activat | Echo received serial data back | . | Mod serial | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Rata baud-ului serial | Port speed | . | Expirat | How long to wait before considering an incoming message complete | . | Suprascrie portul serial al consolei | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Descriere | . | Notificare externă activată | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | LED ieșire (GPIO) | Pin the LED is wired to | . | LED de ieșire activ ridicat | Whether the LED pin is active high or low | . | Buzzer ieșire (GPIO) | Pin the buzzer is wired to | . | Ieșire vibrație (GPIO) | Pin the vibration motor is wired to | . | Utilizează buzzer PWM | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Utilizează I2S ca buzzer | Send the alert through an I2S audio output instead | . | Durată ieșire (milisecunde) | How long a single alert lasts | . | Durată notificare (secunde) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Sonerie | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Descriere | . | Reținere și redirecționare activată | Activate store and forward | . | Puls | Periodically announce this node’s store-and-forward capability | . | Numarul de inregistrari | Maximum stored messages | . | istoric număr maxim de retur | Max messages to replay | . | Fereastra de returnare a istoricului | Time window for replay | . | Server | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Descriere | . | Testul de gamă activat | Activate range testing | . | Interval mesaj expeditor (secunde) | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Salvați .CSV doar în memorie (ESP32) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Descriere | . | Trimite telemetrie dispozitiv | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Intervalul de actualizare a parametrilor dispozitivului | How often to report battery, uptime and channel utilization | . | Modul de măsurare mediu activat | Report the attached environment sensors | . | Interval actualizare valori mediu | How often to report them | . | Valorile de mediu pe ecran sunt activate | Also show these readings on the device’s own display | . | Valorile de mediu utilizează Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Air quality metrics module enabled | Report particulate and CO₂ sensor data | . | Interval actualizare măsurători de calitate a aerului | How often to report them | . | Modul de măsurare putere activat | Report the per-channel voltage and current readings | . | Interval actualizare măsurători de putere | How often to report them | . | Valori pe ecran activate | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Descriere | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Mesaje | Newline-separated list of messages | . | Trimite clopoțel | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Encoder rotativ #1 activat | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Intrare sus/jos/selectare activată | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Descriere | . | CODEC 2 activat | Activate audio module | . | Rată de eșantionare CODEC2 | Audio quality/bandwidth tradeoff | . | Pin PTT | GPIO pin for the push-to-talk button | . | Selectare cuvânt I2S | GPIO pin for I2S WS | . | Intrare date I2S | GPIO pin for I2S DIN | . | Ieșire date I2S | GPIO pin for I2S DOUT | . | Ceas I2S | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Descriere | . | Hardware extern activat | Activate remote GPIO access | . | Permite acces Pin nedefinit | Allow access to any GPIO pin (security risk) | . | Pin-uri disponibile | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Descriere | . | Info vecin activat | Activate neighbor broadcasting | . | Interval de actualizare (secunde) | How often to broadcast neighbor list | . | Transmite peste LoRA | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Descriere | . | Stare LED | Turn the LED on or off | . | Actual | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Descriere | . | Senzor detectare activat | Activate detection sensor | . | Pin GPIO de monitorizat | GPIO pin connected to sensor | . | Tip declanșator detectare | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Folosește modul INPUT_PULLUP | Enable the pin’s internal pull-up resistor | . | Difuzare minimă (secunde) | Minimum time between alert broadcasts | . | Difuzare stare (secunde) | Periodic state broadcast interval | . | Trimite clopoțelul cu mesaj de alertă | Include bell character in alerts | . | Nume comun | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Descriere | . | Paxcounter activat | Activate people counting | . | Interval de actualizare (secunde) | How often to report counts | . | Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ", + "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Descriere | . | MQTT activat | Toggle MQTT bridge | . | Adresă | MQTT broker address | . | Nume de utilizator | Authentication username | . | Parolă | Authentication password | . | Criptare activată | Encrypt MQTT payloads | . | Ieșire JSON activată | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS activat | Use secure connection | . | Temă rădăcină | Base MQTT topic path | . | Proxy-ul pentru client activat | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Raportarea hărții | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Descriere | . | Sunt de acord | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Descriere | . | Serial activat | Activate serial communication | . | Echo activat | Echo received serial data back | . | Mod serial | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Rata baud-ului serial | Port speed | . | Expirat | How long to wait before considering an incoming message complete | . | Suprascrie portul serial al consolei | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Descriere | . | Notificare externă activată | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | LED ieșire (GPIO) | Pin the LED is wired to | . | LED de ieșire activ ridicat | Whether the LED pin is active high or low | . | Buzzer ieșire (GPIO) | Pin the buzzer is wired to | . | Ieșire vibrație (GPIO) | Pin the vibration motor is wired to | . | Utilizează buzzer PWM | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Utilizează I2S ca buzzer | Send the alert through an I2S audio output instead | . | GPIO Output Duration | How long a single alert lasts | . | Nag Timeout | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Sonerie | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Descriere | . | Reținere și redirecționare activată | Activate store and forward | . | Puls | Periodically announce this node’s store-and-forward capability | . | Numarul de inregistrari | Maximum stored messages | . | istoric număr maxim de retur | Max messages to replay | . | Fereastra de returnare a istoricului | Time window for replay | . | Server | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Descriere | . | Testul de gamă activat | Activate range testing | . | Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Salvați .CSV doar în memorie (ESP32) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Descriere | . | Trimite telemetrie dispozitiv | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Intervalul de actualizare a parametrilor dispozitivului | How often to report battery, uptime and channel utilization | . | Modul de măsurare mediu activat | Report the attached environment sensors | . | Interval actualizare valori mediu | How often to report them | . | Valorile de mediu pe ecran sunt activate | Also show these readings on the device’s own display | . | Valorile de mediu utilizează Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Air quality metrics module enabled | Report particulate and CO₂ sensor data | . | Interval actualizare măsurători de calitate a aerului | How often to report them | . | Modul de măsurare putere activat | Report the per-channel voltage and current readings | . | Interval actualizare măsurători de putere | How often to report them | . | Valori pe ecran activate | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Descriere | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Mesaje | Newline-separated list of messages | . | Trimite clopoțel | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Encoder rotativ #1 activat | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Intrare sus/jos/selectare activată | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Descriere | . | CODEC 2 activat | Activate audio module | . | Rată de eșantionare CODEC2 | Audio quality/bandwidth tradeoff | . | Pin PTT | GPIO pin for the push-to-talk button | . | Selectare cuvânt I2S | GPIO pin for I2S WS | . | Intrare date I2S | GPIO pin for I2S DIN | . | Ieșire date I2S | GPIO pin for I2S DOUT | . | Ceas I2S | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Descriere | . | Hardware extern activat | Activate remote GPIO access | . | Permite acces Pin nedefinit | Allow access to any GPIO pin (security risk) | . | Pin-uri disponibile | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Descriere | . | Info vecin activat | Activate neighbor broadcasting | . | Interval de actualizare GPS | How often to broadcast neighbor list | . | Transmite peste LoRA | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Descriere | . | Stare LED | Turn the LED on or off | . | Actual | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Descriere | . | Senzor detectare activat | Activate detection sensor | . | Pin GPIO de monitorizat | GPIO pin connected to sensor | . | Tip declanșator detectare | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Folosește modul INPUT_PULLUP | Enable the pin’s internal pull-up resistor | . | Minimum time between detection broadcasts | Minimum time between alert broadcasts | . | State Broadcast Interval | Periodic state broadcast interval | . | Trimite clopoțelul cu mesaj de alertă | Include bell character in alerts | . | Nume comun | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Descriere | . | Paxcounter activat | Activate people counting | . | Interval de actualizare GPS | How often to report counts | . | WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ", "url": "/Meshtastic-Android/main/ro-rRO/user/settings-module-admin.html#configurare-modul", "relUrl": "/ro-rRO/user/settings-module-admin.html#configurare-modul" @@ -30983,7 +30983,7 @@ },"4426": { "doc": "Settings — Modules & Admin", "title": "הגדרות מודולות", - "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | תיאור | . | MQTT enabled | Toggle MQTT bridge | . | Address | MQTT broker address | . | Username | Authentication username | . | Password | Authentication password | . | Encryption enabled | Encrypt MQTT payloads | . | JSON output enabled | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS enabled | Use secure connection | . | Root topic | Base MQTT topic path | . | Proxy to client enabled | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Map reporting | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | תיאור | . | I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Map reporting interval (seconds) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | תיאור | . | Serial enabled | Activate serial communication | . | Echo enabled | Echo received serial data back | . | Serial mode | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Serial baud rate | Port speed | . | Timeout | How long to wait before considering an incoming message complete | . | Override console serial port | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | תיאור | . | External notification enabled | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Output LED (GPIO) | Pin the LED is wired to | . | Output LED active high | Whether the LED pin is active high or low | . | Output buzzer (GPIO) | Pin the buzzer is wired to | . | Output vibra (GPIO) | Pin the vibration motor is wired to | . | Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Use I2S as buzzer | Send the alert through an I2S audio output instead | . | Output duration (milliseconds) | How long a single alert lasts | . | Nag timeout (seconds) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | תיאור | . | Store & Forward enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | Number of records | Maximum stored messages | . | History return max | Max messages to replay | . | History return window | Time window for replay | . | Server | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | תיאור | . | Range test enabled | Activate range testing | . | Sender message interval (seconds) | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Save .CSV in storage (ESP32 only) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | תיאור | . | Send Device Telemetry | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Device metrics update interval | How often to report battery, uptime and channel utilization | . | Environment metrics module enabled | Report the attached environment sensors | . | Environment metrics update interval | How often to report them | . | Environment metrics on-screen enabled | Also show these readings on the device’s own display | . | Environment metrics use Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Air quality metrics module enabled | Report particulate and CO₂ sensor data | . | Air quality metrics update interval | How often to report them | . | Power metrics module enabled | Report the per-channel voltage and current readings | . | Power metrics update interval | How often to report them | . | Power metrics on-screen enabled | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | תיאור | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | הודעות | Newline-separated list of messages | . | Send bell | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Rotary encoder #1 enabled | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Up/Down/Select input enabled | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | תיאור | . | CODEC 2 enabled | Activate audio module | . | CODEC2 sample rate | Audio quality/bandwidth tradeoff | . | PTT pin | GPIO pin for the push-to-talk button | . | I2S word select | GPIO pin for I2S WS | . | I2S data in | GPIO pin for I2S DIN | . | I2S data out | GPIO pin for I2S DOUT | . | I2S clock | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | תיאור | . | Remote Hardware enabled | Activate remote GPIO access | . | Allow undefined pin access | Allow access to any GPIO pin (security risk) | . | Available pins | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | תיאור | . | Neighbor Info enabled | Activate neighbor broadcasting | . | Update interval (seconds) | How often to broadcast neighbor list | . | Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | תיאור | . | LED state | Turn the LED on or off | . | Current | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | תיאור | . | Detection Sensor enabled | Activate detection sensor | . | GPIO pin to monitor | GPIO pin connected to sensor | . | Detection trigger type | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Use INPUT_PULLUP mode | Enable the pin’s internal pull-up resistor | . | Minimum broadcast (seconds) | Minimum time between alert broadcasts | . | State broadcast (seconds) | Periodic state broadcast interval | . | Send bell with alert message | Include bell character in alerts | . | Friendly name | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | תיאור | . | Paxcounter enabled | Activate people counting | . | Update interval (seconds) | How often to report counts | . | Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ", + "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | תיאור | . | MQTT enabled | Toggle MQTT bridge | . | Address | MQTT broker address | . | Username | Authentication username | . | Password | Authentication password | . | Encryption enabled | Encrypt MQTT payloads | . | JSON output enabled | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS enabled | Use secure connection | . | Root topic | Base MQTT topic path | . | Proxy to client enabled | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Map reporting | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | תיאור | . | I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | תיאור | . | Serial enabled | Activate serial communication | . | Echo enabled | Echo received serial data back | . | Serial mode | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Serial baud rate | Port speed | . | Timeout | How long to wait before considering an incoming message complete | . | Override console serial port | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | תיאור | . | External notification enabled | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Output LED (GPIO) | Pin the LED is wired to | . | Output LED active high | Whether the LED pin is active high or low | . | Output buzzer (GPIO) | Pin the buzzer is wired to | . | Output vibra (GPIO) | Pin the vibration motor is wired to | . | Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Use I2S as buzzer | Send the alert through an I2S audio output instead | . | GPIO Output Duration | How long a single alert lasts | . | Nag Timeout | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | תיאור | . | Store & Forward enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | Number of records | Maximum stored messages | . | History return max | Max messages to replay | . | History return window | Time window for replay | . | Server | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | תיאור | . | Range test enabled | Activate range testing | . | Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Save .CSV in storage (ESP32 only) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | תיאור | . | Send Device Telemetry | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Device metrics update interval | How often to report battery, uptime and channel utilization | . | Environment metrics module enabled | Report the attached environment sensors | . | Environment metrics update interval | How often to report them | . | Environment metrics on-screen enabled | Also show these readings on the device’s own display | . | Environment metrics use Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Air quality metrics module enabled | Report particulate and CO₂ sensor data | . | Air quality metrics update interval | How often to report them | . | Power metrics module enabled | Report the per-channel voltage and current readings | . | Power metrics update interval | How often to report them | . | Power metrics on-screen enabled | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | תיאור | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | הודעות | Newline-separated list of messages | . | Send bell | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Rotary encoder #1 enabled | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Up/Down/Select input enabled | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | תיאור | . | CODEC 2 enabled | Activate audio module | . | CODEC2 sample rate | Audio quality/bandwidth tradeoff | . | PTT pin | GPIO pin for the push-to-talk button | . | I2S word select | GPIO pin for I2S WS | . | I2S data in | GPIO pin for I2S DIN | . | I2S data out | GPIO pin for I2S DOUT | . | I2S clock | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | תיאור | . | Remote Hardware enabled | Activate remote GPIO access | . | Allow undefined pin access | Allow access to any GPIO pin (security risk) | . | Available pins | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | תיאור | . | Neighbor Info enabled | Activate neighbor broadcasting | . | Update Interval | How often to broadcast neighbor list | . | Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | תיאור | . | LED state | Turn the LED on or off | . | Current | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | תיאור | . | Detection Sensor enabled | Activate detection sensor | . | GPIO pin to monitor | GPIO pin connected to sensor | . | Detection trigger type | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Use INPUT_PULLUP mode | Enable the pin’s internal pull-up resistor | . | Minimum time between detection broadcasts | Minimum time between alert broadcasts | . | State Broadcast Interval | Periodic state broadcast interval | . | Send bell with alert message | Include bell character in alerts | . | Friendly name | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | תיאור | . | Paxcounter enabled | Activate people counting | . | Update Interval | How often to report counts | . | WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ", "url": "/Meshtastic-Android/main/iw-rIL/user/settings-module-admin.html#%D7%94%D7%92%D7%93%D7%A8%D7%95%D7%AA-%D7%9E%D7%95%D7%93%D7%95%D7%9C%D7%95%D7%AA", "relUrl": "/iw-rIL/user/settings-module-admin.html#הגדרות-מודולות" @@ -31018,7 +31018,7 @@ },"4431": { "doc": "Settings — Modules & Admin", "title": "Configuração de módulos", - "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Descrição | . | MQTT habilitado | Toggle MQTT bridge | . | Endereço | MQTT broker address | . | Nome de usuário | Authentication username | . | Senha | Authentication password | . | Criptografia ativada | Encrypt MQTT payloads | . | Saída JSON ativada | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS ativado | Use secure connection | . | Tópico principal | Base MQTT topic path | . | Proxy para cliente ativado | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Relatório de mapa | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Descrição | . | Eu concordo. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Intervalo de relatório de mapa (segundos) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Descrição | . | Serial ativado | Activate serial communication | . | Eco habilitado | Echo received serial data back | . | Modo de série | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Taxa de transmissão série | Port speed | . | Tempo esgotado | How long to wait before considering an incoming message complete | . | Substituir porta série do console | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Descrição | . | Notificação Externa habilitada | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | LED de Saída (GPIO) | Pin the LED is wired to | . | LED de saída habilitado alto | Whether the LED pin is active high or low | . | Saída Campainha (GPIO) | Pin the buzzer is wired to | . | Vibra de saída (GPIO) | Pin the vibration motor is wired to | . | Usar uma campainha PWM | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Usar I2S como campainha | Send the alert through an I2S audio output instead | . | Duração da Saída (milissegundos) | How long a single alert lasts | . | Tempo limite do Nag (segundos) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Toque | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Descrição | . | Guardar e Encaminhar ativado | Activate store and forward | . | Batimento | Periodically announce this node’s store-and-forward capability | . | Número de registros | Maximum stored messages | . | Histórico de retorno máximo | Max messages to replay | . | Janela de retorno do histórico | Time window for replay | . | Servidor | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Descrição | . | Teste de distância ativado | Activate range testing | . | Intervalo de mensagem do remetente (segundos) | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Salvar .CSV no armazenamento (apenas ESP32) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Descrição | . | Send Device Telemetry | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Device metrics update interval | How often to report battery, uptime and channel utilization | . | Módulo de métricas do ambiente ativado | Report the attached environment sensors | . | Environment metrics update interval | How often to report them | . | Métricas de ambiente na tela habilitado | Also show these readings on the device’s own display | . | Métricas de Ambiente usam Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Módulo de métricas de qualidade do ar habilitado | Report particulate and CO₂ sensor data | . | Air quality metrics update interval | How often to report them | . | Módulo de métricas de energia habilitado | Report the per-channel voltage and current readings | . | Power metrics update interval | How often to report them | . | Métricas de ambiente na tela habilitado | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Descrição | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Mensagens | Newline-separated list of messages | . | Enviar sino | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Codificador rotativo #1 ativado | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Entrada Cima/Baixo/Selecionar ativada | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Descrição | . | CODEC 2 ativado | Activate audio module | . | Taxa de amostragem CODEC2 | Audio quality/bandwidth tradeoff | . | Pino de PTT | GPIO pin for the push-to-talk button | . | CS I2S | GPIO pin for I2S WS | . | MOSI I2S | GPIO pin for I2S DIN | . | MISO I2S | GPIO pin for I2S DOUT | . | CLK I2S | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Descrição | . | Hardware Remoto ativado | Activate remote GPIO access | . | Permitir acesso indefinido ao pino | Allow access to any GPIO pin (security risk) | . | Pinos disponíveis | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Descrição | . | Informações do Vizinho ativado | Activate neighbor broadcasting | . | Intervalo de atualização (segundos) | How often to broadcast neighbor list | . | Transmitir por LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Descrição | . | Estado do LED | Turn the LED on or off | . | Atual | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Descrição | . | Sensor de Detecção ativado | Activate detection sensor | . | Pino GPIO para monitorar | GPIO pin connected to sensor | . | Tipo de gatilho de deteção | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Usar o modo INPUT_PULLUP | Enable the pin’s internal pull-up resistor | . | Transmissão mínima (segundos) | Minimum time between alert broadcasts | . | Transmissão de estado (segundos) | Periodic state broadcast interval | . | Enviar sino com mensagem de alerta | Include bell character in alerts | . | Nome amigável | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Descrição | . | Contador de Pessoas ativado | Activate people counting | . | Intervalo de atualização (segundos) | How often to report counts | . | Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ", + "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Descrição | . | MQTT habilitado | Toggle MQTT bridge | . | Endereço | MQTT broker address | . | Nome de usuário | Authentication username | . | Senha | Authentication password | . | Criptografia ativada | Encrypt MQTT payloads | . | Saída JSON ativada | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS ativado | Use secure connection | . | Tópico principal | Base MQTT topic path | . | Proxy para cliente ativado | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Relatório de mapa | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Descrição | . | Eu concordo. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Descrição | . | Serial ativado | Activate serial communication | . | Eco habilitado | Echo received serial data back | . | Modo de série | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Taxa de transmissão série | Port speed | . | Tempo esgotado | How long to wait before considering an incoming message complete | . | Substituir porta série do console | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Descrição | . | Notificação Externa habilitada | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | LED de Saída (GPIO) | Pin the LED is wired to | . | LED de saída habilitado alto | Whether the LED pin is active high or low | . | Saída Campainha (GPIO) | Pin the buzzer is wired to | . | Vibra de saída (GPIO) | Pin the vibration motor is wired to | . | Usar uma campainha PWM | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Usar I2S como campainha | Send the alert through an I2S audio output instead | . | GPIO Output Duration | How long a single alert lasts | . | Nag Timeout | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Toque | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Descrição | . | Guardar e Encaminhar ativado | Activate store and forward | . | Batimento | Periodically announce this node’s store-and-forward capability | . | Número de registros | Maximum stored messages | . | Histórico de retorno máximo | Max messages to replay | . | Janela de retorno do histórico | Time window for replay | . | Servidor | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Descrição | . | Teste de distância ativado | Activate range testing | . | Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Salvar .CSV no armazenamento (apenas ESP32) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Descrição | . | Send Device Telemetry | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Device metrics update interval | How often to report battery, uptime and channel utilization | . | Módulo de métricas do ambiente ativado | Report the attached environment sensors | . | Environment metrics update interval | How often to report them | . | Métricas de ambiente na tela habilitado | Also show these readings on the device’s own display | . | Métricas de Ambiente usam Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Módulo de métricas de qualidade do ar habilitado | Report particulate and CO₂ sensor data | . | Air quality metrics update interval | How often to report them | . | Módulo de métricas de energia habilitado | Report the per-channel voltage and current readings | . | Power metrics update interval | How often to report them | . | Métricas de ambiente na tela habilitado | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Descrição | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Mensagens | Newline-separated list of messages | . | Enviar sino | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Codificador rotativo #1 ativado | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Entrada Cima/Baixo/Selecionar ativada | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Descrição | . | CODEC 2 ativado | Activate audio module | . | Taxa de amostragem CODEC2 | Audio quality/bandwidth tradeoff | . | Pino de PTT | GPIO pin for the push-to-talk button | . | CS I2S | GPIO pin for I2S WS | . | MOSI I2S | GPIO pin for I2S DIN | . | MISO I2S | GPIO pin for I2S DOUT | . | CLK I2S | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Descrição | . | Hardware Remoto ativado | Activate remote GPIO access | . | Permitir acesso indefinido ao pino | Allow access to any GPIO pin (security risk) | . | Pinos disponíveis | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Descrição | . | Informações do Vizinho ativado | Activate neighbor broadcasting | . | Update Interval | How often to broadcast neighbor list | . | Transmitir por LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Descrição | . | Estado do LED | Turn the LED on or off | . | Atual | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Descrição | . | Sensor de Detecção ativado | Activate detection sensor | . | Pino GPIO para monitorar | GPIO pin connected to sensor | . | Tipo de gatilho de deteção | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Usar o modo INPUT_PULLUP | Enable the pin’s internal pull-up resistor | . | Minimum time between detection broadcasts | Minimum time between alert broadcasts | . | State Broadcast Interval | Periodic state broadcast interval | . | Enviar sino com mensagem de alerta | Include bell character in alerts | . | Nome amigável | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Descrição | . | Contador de Pessoas ativado | Activate people counting | . | Update Interval | How often to report counts | . | WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ", "url": "/Meshtastic-Android/main/pt-rBR/user/settings-module-admin.html#configura%C3%A7%C3%A3o-de-m%C3%B3dulos", "relUrl": "/pt-rBR/user/settings-module-admin.html#configuração-de-módulos" @@ -31102,7 +31102,7 @@ },"4443": { "doc": "Settings — Radio & User", "title": "Configuration", - "content": "Konfigurácia Zariadenia . On Settings → Device configuration → Device. | Setting | Popis | Predvolené | . | Device Role | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Rebroadcast Mode | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Node Info Broadcast Interval | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Double Tap as Button | Treat a double tap as a button press | Disabled | . | Triple Click Ad Hoc Ping | Send an ad-hoc position ping on a triple click | Enabled | . | LED Heartbeat | Blink the status LED periodically | Enabled | . | Time Zone | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . Konfigurácia LoRa . On Settings → LoRa. | Setting | Popis | Predvolené | . | Región | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Presets | Speed/range tradeoff | LongFast | . | Number of Hops | Maximum retransmit hops | 3 | . | Transmit Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Šírka pásma | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Frequency Slot | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Transmit Enabled | Turning this off makes the node receive-only | On | . | Override Duty Cycle | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | . | Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | . | RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | . | PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Rýchlosť | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Konfigurácia Displeju . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Popis | . | Screen on for | How long the display stays lit before sleeping | . | Carousel interval | How often the node cycles between screens on its own | . | Display mode | Screen layout/density used by the firmware | . | Display units | Metric or Imperial on the node’s screen | . | Use 12h clock format | Show the node’s clock as 12-hour rather than 24-hour | . | Bold Heading | Draw the screen’s heading text in bold | . | Otoč Obrazovku | Rotate the display 180° for an inverted mounting | . | OLED type | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Wake on tap or motion | Light the screen when the node is tapped or moved | . | Compass orientation | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Always point north | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Position Config . On Settings → Device configuration → Position. | Setting | Popis | . | GPS Mode (Physical Hardware) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Polling Interval | How often the node asks its GPS for a fix | . | Broadcastový Interval | How often the position is shared with the mesh | . | Inteligentná poloha | Broadcast based on movement rather than purely on the clock | . | Smart Interval | With Smart Position on, the shortest gap between broadcasts | . | Smart Distance | With Smart Position on, how far you must move before broadcasting | . | Fixná Pozícia | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Position Flags | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Power Config . On Settings → Device configuration → Power. | Setting | Popis | . | Enable power saving mode | Let the node sleep aggressively between activity | . | Shutdown on power loss | Power the device down after external power disappears | . | Super deep sleep duration | How long the deepest sleep state lasts | . | Minimum wake time | The shortest time the node stays awake once woken | . | Wait for Bluetooth duration | How long to wait for a phone to connect before sleeping | . | ADC multiplier override | Turn on a manual correction for battery-voltage readings | . | ADC multiplier override ratio | The correction factor itself, used only when the override is on | . | Battery INA_2XX I2C address | Address of an external INA-series power sensor, if fitted | . Konfigurácia siete . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Popis | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Heslo | Network password | . | Ethernet zapnutý | Use a wired connection on hardware that has one | . | IPv4 režim | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | NTP server | Time synchronization server | . | rsyslog server | Remote logging server | . Konfigurácia Bluetooth . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Popis | . | Bluetooth zapnuté | Enable/disable BLE radio | . | Režim párovania | Fixed PIN, Random PIN, or No PIN | . | Pevný PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Security Config . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Popis | . | Verejný kľúč | Your node’s public key (read-only) | . | Admin Key | Keys permitted to administer this node remotely — up to three | . | Súkromný kľúč | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Regenerate Private Key | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Serial console | Serial console over the Stream API | . | Debug log API enabled | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Managed Mode | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Backup Keys | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ", + "content": "Konfigurácia Zariadenia . On Settings → Device configuration → Device. | Setting | Popis | Predvolené | . | Device Role | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Rebroadcast Mode | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Node Info Broadcast Interval | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Double Tap as Button | Treat a double tap as a button press | Disabled | . | Triple Click Ad Hoc Ping | Send an ad-hoc position ping on a triple click | Enabled | . | LED Heartbeat | Blink the status LED periodically | Enabled | . | Time Zone | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . Konfigurácia LoRa . On Settings → LoRa. | Setting | Popis | Predvolené | . | Región | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Presets | Speed/range tradeoff | LongFast | . | Number of Hops | Maximum retransmit hops | 3 | . | Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) | . | Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Šírka pásma | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Frequency Slot | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Transmit Enabled | Turning this off makes the node receive-only | On | . | Override Duty Cycle | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | . | Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | . | RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | . | PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Rýchlosť | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Konfigurácia Displeju . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Popis | . | Screen on for | How long the display stays lit before sleeping | . | Carousel interval | How often the node cycles between screens on its own | . | Display mode | Screen layout/density used by the firmware | . | Display units | Metric or Imperial on the node’s screen | . | Use 12h clock format | Show the node’s clock as 12-hour rather than 24-hour | . | Bold Heading | Draw the screen’s heading text in bold | . | Otoč Obrazovku | Rotate the display 180° for an inverted mounting | . | OLED type | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Wake on tap or motion | Light the screen when the node is tapped or moved | . | Compass orientation | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Always point north | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Position Config . On Settings → Device configuration → Position. | Setting | Popis | . | GPS Mode (Physical Hardware) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Polling Interval | How often the node asks its GPS for a fix | . | Broadcastový Interval | How often the position is shared with the mesh | . | Inteligentná poloha | Broadcast based on movement rather than purely on the clock | . | Smart Interval | With Smart Position on, the shortest gap between broadcasts | . | Smart Distance | With Smart Position on, how far you must move before broadcasting | . | Fixná Pozícia | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Position Flags | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Power Config . On Settings → Device configuration → Power. | Setting | Popis | . | Enable power saving mode | Let the node sleep aggressively between activity | . | Shutdown on power loss | Power the device down after external power disappears | . | Super deep sleep duration | How long the deepest sleep state lasts | . | Minimum wake time | The shortest time the node stays awake once woken | . | Wait for Bluetooth duration | How long to wait for a phone to connect before sleeping | . | ADC multiplier override | Turn on a manual correction for battery-voltage readings | . | ADC multiplier override ratio | The correction factor itself, used only when the override is on | . | Battery INA_2XX I2C address | Address of an external INA-series power sensor, if fitted | . Konfigurácia siete . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Popis | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Heslo | Network password | . | Ethernet zapnutý | Use a wired connection on hardware that has one | . | IPv4 režim | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | NTP server | Time synchronization server | . | rsyslog server | Remote logging server | . Konfigurácia Bluetooth . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Popis | . | Bluetooth zapnuté | Enable/disable BLE radio | . | Režim párovania | Fixed PIN, Random PIN, or No PIN | . | Pevný PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Security Config . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Popis | . | Verejný kľúč | Your node’s public key (read-only) | . | Admin Key | Keys permitted to administer this node remotely — up to three | . | Súkromný kľúč | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Regenerate Private Key | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Serial console | Serial console over the Stream API | . | Debug log API enabled | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Managed Mode | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Backup Keys | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ", "url": "/Meshtastic-Android/main/sk-rSK/user/settings-radio-user.html#configuration", "relUrl": "/sk-rSK/user/settings-radio-user.html#configuration" @@ -31144,7 +31144,7 @@ },"4449": { "doc": "Settings — Radio & User", "title": "Конфигурация", - "content": "Device Config . On Settings → Device configuration → Device. | Setting | Апісанне | Default | . | Device Role | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Rebroadcast Mode | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Node Info Broadcast Interval | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Double Tap as Button | Treat a double tap as a button press | Disabled | . | Triple Click Ad Hoc Ping | Send an ad-hoc position ping on a triple click | Уключана | . | LED Heartbeat | Blink the status LED periodically | Уключана | . | Time Zone | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRa Config . On Settings → LoRa. | Setting | Апісанне | Default | . | Рэгіён | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Presets | Speed/range tradeoff | LongFast | . | Number of Hops | Maximum retransmit hops | 3 | . | Transmit Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Frequency Slot | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Transmit Enabled | Turning this off makes the node receive-only | On | . | Override Duty Cycle | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | . | Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | . | RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | . | PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Хуткасць | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Апісанне | . | Screen on for | How long the display stays lit before sleeping | . | Carousel interval | How often the node cycles between screens on its own | . | Display mode | Screen layout/density used by the firmware | . | Display units | Metric or Imperial on the node’s screen | . | Use 12h clock format | Show the node’s clock as 12-hour rather than 24-hour | . | Bold Heading | Draw the screen’s heading text in bold | . | Flip screen | Rotate the display 180° for an inverted mounting | . | Тып OLED | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Wake on tap or motion | Light the screen when the node is tapped or moved | . | Compass orientation | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Always point north | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Position Config . On Settings → Device configuration → Position. | Setting | Апісанне | . | GPS Mode (Physical Hardware) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Polling Interval | How often the node asks its GPS for a fix | . | Broadcast Interval | How often the position is shared with the mesh | . | Smart Position | Broadcast based on movement rather than purely on the clock | . | Smart Interval | With Smart Position on, the shortest gap between broadcasts | . | Smart Distance | With Smart Position on, how far you must move before broadcasting | . | Fixed Position | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Position Flags | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Power Config . On Settings → Device configuration → Power. | Setting | Апісанне | . | Enable power saving mode | Let the node sleep aggressively between activity | . | Shutdown on power loss | Power the device down after external power disappears | . | Super deep sleep duration | How long the deepest sleep state lasts | . | Minimum wake time | The shortest time the node stays awake once woken | . | Wait for Bluetooth duration | How long to wait for a phone to connect before sleeping | . | ADC multiplier override | Turn on a manual correction for battery-voltage readings | . | ADC multiplier override ratio | The correction factor itself, used only when the override is on | . | Battery INA_2XX I2C address | Address of an external INA-series power sensor, if fitted | . Network Config . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Апісанне | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Пароль | Network password | . | Ethernet enabled | Use a wired connection on hardware that has one | . | IPv4 mode | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | NTP server | Time synchronization server | . | rsyslog server | Remote logging server | . Bluetooth Config . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Апісанне | . | Bluetooth enabled | Enable/disable BLE radio | . | Pairing mode | Fixed PIN, Random PIN, or No PIN | . | Fixed PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Security Config . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Апісанне | . | Public Key | Your node’s public key (read-only) | . | Admin Key | Keys permitted to administer this node remotely — up to three | . | Прыватны ключ | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Regenerate Private Key | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Serial console | Serial console over the Stream API | . | Debug log API enabled | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Managed Mode | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Backup Keys | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ", + "content": "Device Config . On Settings → Device configuration → Device. | Setting | Апісанне | Default | . | Device Role | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Rebroadcast Mode | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Node Info Broadcast Interval | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Double Tap as Button | Treat a double tap as a button press | Disabled | . | Triple Click Ad Hoc Ping | Send an ad-hoc position ping on a triple click | Уключана | . | LED Heartbeat | Blink the status LED periodically | Уключана | . | Time Zone | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRa Config . On Settings → LoRa. | Setting | Апісанне | Default | . | Рэгіён | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Presets | Speed/range tradeoff | LongFast | . | Number of Hops | Maximum retransmit hops | 3 | . | Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) | . | Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Frequency Slot | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Transmit Enabled | Turning this off makes the node receive-only | On | . | Override Duty Cycle | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | . | Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | . | RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | . | PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Хуткасць | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Апісанне | . | Screen on for | How long the display stays lit before sleeping | . | Carousel interval | How often the node cycles between screens on its own | . | Display mode | Screen layout/density used by the firmware | . | Display units | Metric or Imperial on the node’s screen | . | Use 12h clock format | Show the node’s clock as 12-hour rather than 24-hour | . | Bold Heading | Draw the screen’s heading text in bold | . | Flip screen | Rotate the display 180° for an inverted mounting | . | Тып OLED | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Wake on tap or motion | Light the screen when the node is tapped or moved | . | Compass orientation | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Always point north | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Position Config . On Settings → Device configuration → Position. | Setting | Апісанне | . | GPS Mode (Physical Hardware) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Polling Interval | How often the node asks its GPS for a fix | . | Broadcast Interval | How often the position is shared with the mesh | . | Smart Position | Broadcast based on movement rather than purely on the clock | . | Smart Interval | With Smart Position on, the shortest gap between broadcasts | . | Smart Distance | With Smart Position on, how far you must move before broadcasting | . | Fixed Position | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Position Flags | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Power Config . On Settings → Device configuration → Power. | Setting | Апісанне | . | Enable power saving mode | Let the node sleep aggressively between activity | . | Shutdown on power loss | Power the device down after external power disappears | . | Super deep sleep duration | How long the deepest sleep state lasts | . | Minimum wake time | The shortest time the node stays awake once woken | . | Wait for Bluetooth duration | How long to wait for a phone to connect before sleeping | . | ADC multiplier override | Turn on a manual correction for battery-voltage readings | . | ADC multiplier override ratio | The correction factor itself, used only when the override is on | . | Battery INA_2XX I2C address | Address of an external INA-series power sensor, if fitted | . Network Config . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Апісанне | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Пароль | Network password | . | Ethernet enabled | Use a wired connection on hardware that has one | . | IPv4 mode | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | NTP server | Time synchronization server | . | rsyslog server | Remote logging server | . Bluetooth Config . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Апісанне | . | Bluetooth enabled | Enable/disable BLE radio | . | Pairing mode | Fixed PIN, Random PIN, or No PIN | . | Fixed PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Security Config . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Апісанне | . | Public Key | Your node’s public key (read-only) | . | Admin Key | Keys permitted to administer this node remotely — up to three | . | Прыватны ключ | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Regenerate Private Key | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Serial console | Serial console over the Stream API | . | Debug log API enabled | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Managed Mode | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Backup Keys | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ", "url": "/Meshtastic-Android/main/be-rBY/user/settings-radio-user.html#%D0%BA%D0%BE%D0%BD%D1%84%D0%B8%D0%B3%D1%83%D1%80%D0%B0%D1%86%D0%B8%D1%8F", "relUrl": "/be-rBY/user/settings-radio-user.html#конфигурация" @@ -31186,7 +31186,7 @@ },"4455": { "doc": "Settings — Radio & User", "title": "Configurazione", - "content": "Configurazione Dispositivo . On Settings → Device configuration → Device. | Impostazione | Descrizione | Predefinito | . | Ruolo Del Dispositivo | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Modalità Ritrasmissione | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Intervallo Di Trasmissione Info Nodo | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Doppio tocco come pressione pulsante | Treat a double tap as a button press | Disabled | . | Triple Click Ad Hoc Ping | Send an ad-hoc position ping on a triple click | Abilitato | . | Battito Cuore Led | Blink the status LED periodically | Abilitato | . | Fuso Orario | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . Configurazione LoRa . On Settings → LoRa. | Impostazione | Descrizione | Predefinito | . | Regione | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Preset | Speed/range tradeoff | LongFast | . | Numero di Hop | Maximum retransmit hops | 3 | . | Potenza di Trasmissione | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Sovrascrivi Frequenza | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Usa Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Larghezza di banda | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Slot di Frequenza | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Trasmissione Abilitata | Turning this off makes the node receive-only | On | . | Ignora limite di Duty Cycle | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Disattivato | . | Ignora MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | OK per MQTT | Allow your packets to be forwarded to MQTT by gateways | Disattivato | . | Migliora guadagno in Ricezione | Extra receive gain on SX126x radios; costs a little current | Disattivato | . | Ventola PA disabilitata | Turn off the power-amplifier fan on hardware that has one | Disattivato | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Velocità | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6,25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3,52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1,95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0,34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0,18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Configurazione Schermo . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Impostazione | Descrizione | . | Tieni lo schermo acceso per | How long the display stays lit before sleeping | . | Durata di ogni schermata | How often the node cycles between screens on its own | . | Modalità schermo | Screen layout/density used by the firmware | . | Unità di misura visualizzata | Metric or Imperial on the node’s screen | . | Usa formato orologio 12h | Show the node’s clock as 12-hour rather than 24-hour | . | Intestazione in grassetto | Draw the screen’s heading text in bold | . | Capovolgi schermo | Rotate the display 180° for an inverted mounting | . | Tipo OLED | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Accendi lo schermo al tocco o al movimento | Light the screen when the node is tapped or moved | . | Orientamento bussola | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Punta sempre a nord | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Configurazione Posizione . On Settings → Device configuration → Position. | Impostazione | Descrizione | . | Modalità GPS (Hardware Fisico) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | Intervallo Interrogazione GPS | How often the node asks its GPS for a fix | . | Intervallo Di Trasmissione | How often the position is shared with the mesh | . | Posizione Smart | Broadcast based on movement rather than purely on the clock | . | Intervallo Intelligente | With Smart Position on, the shortest gap between broadcasts | . | Distanza Intelligente | With Smart Position on, how far you must move before broadcasting | . | Posizione Fissa | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Flag Di Posizione | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Configurazione Alimentazione . On Settings → Device configuration → Power. | Impostazione | Descrizione | . | Abilita modalità risparmio energetico | Let the node sleep aggressively between activity | . | Spegnimento in mancanza di alimentazione | Power the device down after external power disappears | . | Durata super deep sleep | How long the deepest sleep state lasts | . | Tempo minimo di risveglio | The shortest time the node stays awake once woken | . | Durata attesa Bluetooth | How long to wait for a phone to connect before sleeping | . | Sovrascrivi moltiplicatore ADC | Turn on a manual correction for battery-voltage readings | . | Sovrascrivi rapporto moltiplicatore ADC | The correction factor itself, used only when the override is on | . | Indirizzo INA_2XX I2C della batteria | Address of an external INA-series power sensor, if fitted | . Configurazione Della Rete . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Impostazione | Descrizione | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Password | Password di rete | . | Ethernet abilitato | Use a wired connection on hardware that has one | . | Modalità IPv4 | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | Trasmissione UDP | Share mesh traffic with other nodes over the local network | . | Server NTP | Time synchronization server | . | server rsyslog | Remote logging server | . Configurazione Bluetooth . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Impostazione | Descrizione | . | Bluetooth attivo | Enable/disable BLE radio | . | Modalità abbinamento | Fixed PIN, Random PIN, or No PIN | . | PIN Fisso | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Configurazione Sicurezza . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Impostazione | Descrizione | . | Chiave Pubblica | Your node’s public key (read-only) | . | Chiave Amministratore | Keys permitted to administer this node remotely — up to three | . | Chiave Privata | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Rigenera Chiavi Private | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Console seriale | Serial console over the Stream API | . | Debug log API abilitato | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Modalità Gestita | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Backup chiavi | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Livello di protezione | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Avvii rimanenti | How many device boots the unlocked state survives | . | Ore alla scadenza | Wall-clock lifetime of the unlocked state | . | Limite di sessione (minuti) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ", + "content": "Configurazione Dispositivo . On Settings → Device configuration → Device. | Impostazione | Descrizione | Predefinito | . | Ruolo Del Dispositivo | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Modalità Ritrasmissione | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Intervallo Di Trasmissione Info Nodo | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Doppio tocco come pressione pulsante | Treat a double tap as a button press | Disabled | . | Triple Click Ad Hoc Ping | Send an ad-hoc position ping on a triple click | Abilitato | . | Battito Cuore Led | Blink the status LED periodically | Abilitato | . | Fuso Orario | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . Configurazione LoRa . On Settings → LoRa. | Impostazione | Descrizione | Predefinito | . | Regione | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Preset | Speed/range tradeoff | LongFast | . | Numero di Hop | Maximum retransmit hops | 3 | . | Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) | . | Sovrascrivi Frequenza | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Usa Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Larghezza di banda | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Slot di Frequenza | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Trasmissione Abilitata | Turning this off makes the node receive-only | On | . | Ignora limite di Duty Cycle | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Disattivato | . | Ignora MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | OK per MQTT | Allow your packets to be forwarded to MQTT by gateways | Disattivato | . | Migliora guadagno in Ricezione | Extra receive gain on SX126x radios; costs a little current | Disattivato | . | Ventola PA disabilitata | Turn off the power-amplifier fan on hardware that has one | Disattivato | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Velocità | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6,25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3,52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1,95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0,34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0,18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Configurazione Schermo . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Impostazione | Descrizione | . | Tieni lo schermo acceso per | How long the display stays lit before sleeping | . | Durata di ogni schermata | How often the node cycles between screens on its own | . | Modalità schermo | Screen layout/density used by the firmware | . | Unità di misura visualizzata | Metric or Imperial on the node’s screen | . | Usa formato orologio 12h | Show the node’s clock as 12-hour rather than 24-hour | . | Intestazione in grassetto | Draw the screen’s heading text in bold | . | Capovolgi schermo | Rotate the display 180° for an inverted mounting | . | Tipo OLED | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Accendi lo schermo al tocco o al movimento | Light the screen when the node is tapped or moved | . | Orientamento bussola | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Punta sempre a nord | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Configurazione Posizione . On Settings → Device configuration → Position. | Impostazione | Descrizione | . | Modalità GPS (Hardware Fisico) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | Intervallo Interrogazione GPS | How often the node asks its GPS for a fix | . | Intervallo Di Trasmissione | How often the position is shared with the mesh | . | Posizione Smart | Broadcast based on movement rather than purely on the clock | . | Intervallo Intelligente | With Smart Position on, the shortest gap between broadcasts | . | Distanza Intelligente | With Smart Position on, how far you must move before broadcasting | . | Posizione Fissa | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Flag Di Posizione | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Configurazione Alimentazione . On Settings → Device configuration → Power. | Impostazione | Descrizione | . | Abilita modalità risparmio energetico | Let the node sleep aggressively between activity | . | Spegnimento in mancanza di alimentazione | Power the device down after external power disappears | . | Durata super deep sleep | How long the deepest sleep state lasts | . | Tempo minimo di risveglio | The shortest time the node stays awake once woken | . | Durata attesa Bluetooth | How long to wait for a phone to connect before sleeping | . | Sovrascrivi moltiplicatore ADC | Turn on a manual correction for battery-voltage readings | . | Sovrascrivi rapporto moltiplicatore ADC | The correction factor itself, used only when the override is on | . | Indirizzo INA_2XX I2C della batteria | Address of an external INA-series power sensor, if fitted | . Configurazione Della Rete . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Impostazione | Descrizione | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Password | Password di rete | . | Ethernet abilitato | Use a wired connection on hardware that has one | . | Modalità IPv4 | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | Trasmissione UDP | Share mesh traffic with other nodes over the local network | . | Server NTP | Time synchronization server | . | server rsyslog | Remote logging server | . Configurazione Bluetooth . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Impostazione | Descrizione | . | Bluetooth attivo | Enable/disable BLE radio | . | Modalità abbinamento | Fixed PIN, Random PIN, or No PIN | . | PIN Fisso | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Configurazione Sicurezza . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Impostazione | Descrizione | . | Chiave Pubblica | Your node’s public key (read-only) | . | Chiave Amministratore | Keys permitted to administer this node remotely — up to three | . | Chiave Privata | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Rigenera Chiavi Private | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Console seriale | Serial console over the Stream API | . | Debug log API abilitato | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Modalità Gestita | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Backup chiavi | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Livello di protezione | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Avvii rimanenti | How many device boots the unlocked state survives | . | Ore alla scadenza | Wall-clock lifetime of the unlocked state | . | Limite di sessione (minuti) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ", "url": "/Meshtastic-Android/main/it-rIT/user/settings-radio-user.html#configurazione", "relUrl": "/it-rIT/user/settings-radio-user.html#configurazione" @@ -31228,7 +31228,7 @@ },"4461": { "doc": "Settings — Radio & User", "title": "Configuración", - "content": "Configuración del dispositivo . On Settings → Device configuration → Device. | Setting | Descripción | Por defecto | . | Rol del dispositivo | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Modo de retransmisión | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Intervalo de transmisión de información del nodo | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Doble pulsación como botón | Treat a double tap as a button press | Disabled | . | Triple pulsación para enviar un ping | Send an ad-hoc position ping on a triple click | Habilitado | . | Latido LED | Blink the status LED periodically | Habilitado | . | Zona horaria | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . Configuración LoRa . On Settings → LoRa. | Setting | Descripción | Por defecto | . | Región | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Predefinidos | Speed/range tradeoff | LongFast | . | Número de saltos | Maximum retransmit hops | 3 | . | Potencia de transmisión | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Sobreescribir frecuencia | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Usar predefinido | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Factor de dispersión | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Ratio de Codificación | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Ancho de banda | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Banda de Frecuencia | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Transmisión habilitada | Turning this off makes the node receive-only | On | . | Sobreescribir el Tiempo de Trabajo | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | . | Ignorar Paquetes MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Permitir MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | . | Aumentar ganancia de RX | Extra receive gain on SX126x radios; costs a little current | Off | . | Ventilador del Amplificador apagado | Turn off the power-amplifier fan on hardware that has one | Off | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Velocidad | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Configuración de pantalla . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Descripción | . | Pantalla activa durante | How long the display stays lit before sleeping | . | Intervalo de carrusel | How often the node cycles between screens on its own | . | Modo de la pantalla | Screen layout/density used by the firmware | . | Unidades en pantalla | Metric or Imperial on the node’s screen | . | Utilizar el formato de 12h para el reloj | Show the node’s clock as 12-hour rather than 24-hour | . | Encabezado en negrita | Draw the screen’s heading text in bold | . | Girar la pantalla 180º | Rotate the display 180° for an inverted mounting | . | Tipo de OLED | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Despertar al tocar o al mover | Light the screen when the node is tapped or moved | . | Orientación de la brújula | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Siempre apuntar al norte | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Configuración de la posición . On Settings → Device configuration → Position. | Setting | Descripción | . | Modo GPS (dispositivo físico) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Polling Interval | How often the node asks its GPS for a fix | . | Intervalo de Difusión | How often the position is shared with the mesh | . | Ubicación inteligente | Broadcast based on movement rather than purely on the clock | . | Smart Interval | With Smart Position on, the shortest gap between broadcasts | . | Smart Distance | With Smart Position on, how far you must move before broadcasting | . | Posición fija | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Marcas de posición | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Configuración de elecenergía . On Settings → Device configuration → Power. | Setting | Descripción | . | Activar el modo ahorro de energía | Let the node sleep aggressively between activity | . | Apagar al perder energía | Power the device down after external power disappears | . | Duración del sueño súper profundo | How long the deepest sleep state lasts | . | Minimum wake time | The shortest time the node stays awake once woken | . | Esperar Bluetooth durante | How long to wait for a phone to connect before sleeping | . | Sobreescribir multiplicador ADC | Turn on a manual correction for battery-voltage readings | . | Sobreescribir relación del multiplicador ADC | The correction factor itself, used only when the override is on | . | Dirección I2C del INA_2xx para la batería | Address of an external INA-series power sensor, if fitted | . Configuración de la red . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Descripción | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID (Nombre la Red) | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Contraseña | Contraseña de red | . | Ethernet del Nodo Activado | Use a wired connection on hardware that has one | . | Modo IPv4 | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | Servidor NTP | Time synchronization server | . | Servidor rsyslog | Remote logging server | . Configuración Bluetooth . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Descripción | . | Bluetooth activado | Enable/disable BLE radio | . | Modo de emparejamiento | Fixed PIN, Random PIN, or No PIN | . | Pin fijo | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Configuración de la seguridad . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Descripción | . | Clave Pública | Your node’s public key (read-only) | . | Contraseña de administrador | Keys permitted to administer this node remotely — up to three | . | Clave privada | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Regenerar clave privada | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Consola serial | Serial console over the Stream API | . | API de registro de depuración habilitada | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Modo “ya terminado de configurar” | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Backup Keys | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ", + "content": "Configuración del dispositivo . On Settings → Device configuration → Device. | Setting | Descripción | Por defecto | . | Rol del dispositivo | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Modo de retransmisión | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Intervalo de transmisión de información del nodo | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Doble pulsación como botón | Treat a double tap as a button press | Disabled | . | Triple pulsación para enviar un ping | Send an ad-hoc position ping on a triple click | Habilitado | . | Latido LED | Blink the status LED periodically | Habilitado | . | Zona horaria | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . Configuración LoRa . On Settings → LoRa. | Setting | Descripción | Por defecto | . | Región | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Predefinidos | Speed/range tradeoff | LongFast | . | Número de saltos | Maximum retransmit hops | 3 | . | Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) | . | Sobreescribir frecuencia | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Usar predefinido | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Factor de dispersión | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Ratio de Codificación | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Ancho de banda | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Banda de Frecuencia | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Transmisión habilitada | Turning this off makes the node receive-only | On | . | Sobreescribir el Tiempo de Trabajo | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | . | Ignorar Paquetes MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Permitir MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | . | Aumentar ganancia de RX | Extra receive gain on SX126x radios; costs a little current | Off | . | Ventilador del Amplificador apagado | Turn off the power-amplifier fan on hardware that has one | Off | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Velocidad | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Configuración de pantalla . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Descripción | . | Pantalla activa durante | How long the display stays lit before sleeping | . | Intervalo de carrusel | How often the node cycles between screens on its own | . | Modo de la pantalla | Screen layout/density used by the firmware | . | Unidades en pantalla | Metric or Imperial on the node’s screen | . | Utilizar el formato de 12h para el reloj | Show the node’s clock as 12-hour rather than 24-hour | . | Encabezado en negrita | Draw the screen’s heading text in bold | . | Girar la pantalla 180º | Rotate the display 180° for an inverted mounting | . | Tipo de OLED | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Despertar al tocar o al mover | Light the screen when the node is tapped or moved | . | Orientación de la brújula | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Siempre apuntar al norte | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Configuración de la posición . On Settings → Device configuration → Position. | Setting | Descripción | . | Modo GPS (dispositivo físico) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Polling Interval | How often the node asks its GPS for a fix | . | Intervalo de Difusión | How often the position is shared with the mesh | . | Ubicación inteligente | Broadcast based on movement rather than purely on the clock | . | Smart Interval | With Smart Position on, the shortest gap between broadcasts | . | Smart Distance | With Smart Position on, how far you must move before broadcasting | . | Posición fija | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Marcas de posición | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Configuración de elecenergía . On Settings → Device configuration → Power. | Setting | Descripción | . | Activar el modo ahorro de energía | Let the node sleep aggressively between activity | . | Apagar al perder energía | Power the device down after external power disappears | . | Duración del sueño súper profundo | How long the deepest sleep state lasts | . | Minimum wake time | The shortest time the node stays awake once woken | . | Esperar Bluetooth durante | How long to wait for a phone to connect before sleeping | . | Sobreescribir multiplicador ADC | Turn on a manual correction for battery-voltage readings | . | Sobreescribir relación del multiplicador ADC | The correction factor itself, used only when the override is on | . | Dirección I2C del INA_2xx para la batería | Address of an external INA-series power sensor, if fitted | . Configuración de la red . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Descripción | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID (Nombre la Red) | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Contraseña | Contraseña de red | . | Ethernet del Nodo Activado | Use a wired connection on hardware that has one | . | Modo IPv4 | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | Servidor NTP | Time synchronization server | . | Servidor rsyslog | Remote logging server | . Configuración Bluetooth . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Descripción | . | Bluetooth activado | Enable/disable BLE radio | . | Modo de emparejamiento | Fixed PIN, Random PIN, or No PIN | . | Pin fijo | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Configuración de la seguridad . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Descripción | . | Clave Pública | Your node’s public key (read-only) | . | Contraseña de administrador | Keys permitted to administer this node remotely — up to three | . | Clave privada | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Regenerar clave privada | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Consola serial | Serial console over the Stream API | . | API de registro de depuración habilitada | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Modo “ya terminado de configurar” | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Backup Keys | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ", "url": "/Meshtastic-Android/main/es-rES/user/settings-radio-user.html#configuraci%C3%B3n", "relUrl": "/es-rES/user/settings-radio-user.html#configuración" @@ -31270,7 +31270,7 @@ },"4467": { "doc": "Settings — Radio & User", "title": "Configuration", - "content": "Device Config . On Settings → Device configuration → Device. | Setting | Opis | Default | . | Device Role | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Rebroadcast Mode | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Node Info Broadcast Interval | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Double Tap as Button | Treat a double tap as a button press | Disabled | . | Triple Click Ad Hoc Ping | Send an ad-hoc position ping on a triple click | Enabled | . | LED Heartbeat | Blink the status LED periodically | Enabled | . | Time Zone | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRa Config . On Settings → LoRa. | Setting | Opis | Default | . | Regija | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Presets | Speed/range tradeoff | LongFast | . | Number of Hops | Maximum retransmit hops | 3 | . | Transmit Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Frequency Slot | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Transmit Enabled | Turning this off makes the node receive-only | On | . | Override Duty Cycle | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | . | Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | . | RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | . | PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Speed | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Opis | . | Screen on for | How long the display stays lit before sleeping | . | Carousel interval | How often the node cycles between screens on its own | . | Display mode | Screen layout/density used by the firmware | . | Display units | Metric or Imperial on the node’s screen | . | Use 12h clock format | Show the node’s clock as 12-hour rather than 24-hour | . | Bold Heading | Draw the screen’s heading text in bold | . | Flip screen | Rotate the display 180° for an inverted mounting | . | OLED type | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Wake on tap or motion | Light the screen when the node is tapped or moved | . | Compass orientation | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Always point north | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Position Config . On Settings → Device configuration → Position. | Setting | Opis | . | GPS Mode (Physical Hardware) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Polling Interval | How often the node asks its GPS for a fix | . | Broadcast Interval | How often the position is shared with the mesh | . | Smart Position | Broadcast based on movement rather than purely on the clock | . | Smart Interval | With Smart Position on, the shortest gap between broadcasts | . | Smart Distance | With Smart Position on, how far you must move before broadcasting | . | Fixed Position | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Position Flags | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Power Config . On Settings → Device configuration → Power. | Setting | Opis | . | Enable power saving mode | Let the node sleep aggressively between activity | . | Shutdown on power loss | Power the device down after external power disappears | . | Super deep sleep duration | How long the deepest sleep state lasts | . | Minimum wake time | The shortest time the node stays awake once woken | . | Wait for Bluetooth duration | How long to wait for a phone to connect before sleeping | . | ADC multiplier override | Turn on a manual correction for battery-voltage readings | . | ADC multiplier override ratio | The correction factor itself, used only when the override is on | . | Battery INA_2XX I2C address | Address of an external INA-series power sensor, if fitted | . Network Config . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Opis | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Password | Network password | . | Ethernet enabled | Use a wired connection on hardware that has one | . | IPv4 mode | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | NTP server | Time synchronization server | . | rsyslog server | Remote logging server | . Bluetooth Config . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Opis | . | Bluetooth enabled | Enable/disable BLE radio | . | Pairing mode | Fixed PIN, Random PIN, or No PIN | . | Fixed PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Security Config . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Opis | . | Javni ključ | Your node’s public key (read-only) | . | Admin Key | Keys permitted to administer this node remotely — up to three | . | Zasebni ključ | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Regenerate Private Key | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Serial console | Serial console over the Stream API | . | Debug log API enabled | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Managed Mode | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Backup Keys | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ", + "content": "Device Config . On Settings → Device configuration → Device. | Setting | Opis | Default | . | Device Role | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Rebroadcast Mode | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Node Info Broadcast Interval | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Double Tap as Button | Treat a double tap as a button press | Disabled | . | Triple Click Ad Hoc Ping | Send an ad-hoc position ping on a triple click | Enabled | . | LED Heartbeat | Blink the status LED periodically | Enabled | . | Time Zone | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRa Config . On Settings → LoRa. | Setting | Opis | Default | . | Regija | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Presets | Speed/range tradeoff | LongFast | . | Number of Hops | Maximum retransmit hops | 3 | . | Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) | . | Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Frequency Slot | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Transmit Enabled | Turning this off makes the node receive-only | On | . | Override Duty Cycle | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | . | Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | . | RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | . | PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Speed | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Opis | . | Screen on for | How long the display stays lit before sleeping | . | Carousel interval | How often the node cycles between screens on its own | . | Display mode | Screen layout/density used by the firmware | . | Display units | Metric or Imperial on the node’s screen | . | Use 12h clock format | Show the node’s clock as 12-hour rather than 24-hour | . | Bold Heading | Draw the screen’s heading text in bold | . | Flip screen | Rotate the display 180° for an inverted mounting | . | OLED type | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Wake on tap or motion | Light the screen when the node is tapped or moved | . | Compass orientation | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Always point north | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Position Config . On Settings → Device configuration → Position. | Setting | Opis | . | GPS Mode (Physical Hardware) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Polling Interval | How often the node asks its GPS for a fix | . | Broadcast Interval | How often the position is shared with the mesh | . | Smart Position | Broadcast based on movement rather than purely on the clock | . | Smart Interval | With Smart Position on, the shortest gap between broadcasts | . | Smart Distance | With Smart Position on, how far you must move before broadcasting | . | Fixed Position | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Position Flags | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Power Config . On Settings → Device configuration → Power. | Setting | Opis | . | Enable power saving mode | Let the node sleep aggressively between activity | . | Shutdown on power loss | Power the device down after external power disappears | . | Super deep sleep duration | How long the deepest sleep state lasts | . | Minimum wake time | The shortest time the node stays awake once woken | . | Wait for Bluetooth duration | How long to wait for a phone to connect before sleeping | . | ADC multiplier override | Turn on a manual correction for battery-voltage readings | . | ADC multiplier override ratio | The correction factor itself, used only when the override is on | . | Battery INA_2XX I2C address | Address of an external INA-series power sensor, if fitted | . Network Config . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Opis | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Password | Network password | . | Ethernet enabled | Use a wired connection on hardware that has one | . | IPv4 mode | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | NTP server | Time synchronization server | . | rsyslog server | Remote logging server | . Bluetooth Config . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Opis | . | Bluetooth enabled | Enable/disable BLE radio | . | Pairing mode | Fixed PIN, Random PIN, or No PIN | . | Fixed PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Security Config . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Opis | . | Javni ključ | Your node’s public key (read-only) | . | Admin Key | Keys permitted to administer this node remotely — up to three | . | Zasebni ključ | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Regenerate Private Key | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Serial console | Serial console over the Stream API | . | Debug log API enabled | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Managed Mode | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Backup Keys | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ", "url": "/Meshtastic-Android/main/sl-rSI/user/settings-radio-user.html#configuration", "relUrl": "/sl-rSI/user/settings-radio-user.html#configuration" @@ -31312,7 +31312,7 @@ },"4473": { "doc": "Settings — Radio & User", "title": "Configuration", - "content": "Device Config . On Settings → Device configuration → Device. | Setting | Beskrivelse | Default | . | Device Role | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Rebroadcast Mode | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Node Info Broadcast Interval | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Double Tap as Button | Treat a double tap as a button press | Disabled | . | Triple Click Ad Hoc Ping | Send an ad-hoc position ping on a triple click | Enabled | . | LED Heartbeat | Blink the status LED periodically | Enabled | . | Time Zone | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRa Config . On Settings → LoRa. | Setting | Beskrivelse | Default | . | Region | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Presets | Speed/range tradeoff | LongFast | . | Number of Hops | Maximum retransmit hops | 3 | . | Transmit Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Frequency Slot | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Transmit Enabled | Turning this off makes the node receive-only | On | . | Override Duty Cycle | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | . | Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | . | RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | . | PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Speed | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Beskrivelse | . | Screen on for | How long the display stays lit before sleeping | . | Carousel interval | How often the node cycles between screens on its own | . | Display mode | Screen layout/density used by the firmware | . | Display units | Metric or Imperial on the node’s screen | . | Use 12h clock format | Show the node’s clock as 12-hour rather than 24-hour | . | Bold Heading | Draw the screen’s heading text in bold | . | Flip screen | Rotate the display 180° for an inverted mounting | . | OLED type | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Wake on tap or motion | Light the screen when the node is tapped or moved | . | Compass orientation | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Always point north | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Position Config . On Settings → Device configuration → Position. | Setting | Beskrivelse | . | GPS Mode (Physical Hardware) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Polling Interval | How often the node asks its GPS for a fix | . | Broadcast Interval | How often the position is shared with the mesh | . | Smart Position | Broadcast based on movement rather than purely on the clock | . | Smart Interval | With Smart Position on, the shortest gap between broadcasts | . | Smart Distance | With Smart Position on, how far you must move before broadcasting | . | Fixed Position | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Position Flags | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Power Config . On Settings → Device configuration → Power. | Setting | Beskrivelse | . | Enable power saving mode | Let the node sleep aggressively between activity | . | Shutdown on power loss | Power the device down after external power disappears | . | Super deep sleep duration | How long the deepest sleep state lasts | . | Minimum wake time | The shortest time the node stays awake once woken | . | Wait for Bluetooth duration | How long to wait for a phone to connect before sleeping | . | ADC multiplier override | Turn on a manual correction for battery-voltage readings | . | ADC multiplier override ratio | The correction factor itself, used only when the override is on | . | Battery INA_2XX I2C address | Address of an external INA-series power sensor, if fitted | . Network Config . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Beskrivelse | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Password | Network password | . | Ethernet enabled | Use a wired connection on hardware that has one | . | IPv4 mode | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | NTP server | Time synchronization server | . | rsyslog server | Remote logging server | . Bluetooth Config . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Beskrivelse | . | Bluetooth enabled | Enable/disable BLE radio | . | Pairing mode | Fixed PIN, Random PIN, or No PIN | . | Fixed PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Security Config . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Beskrivelse | . | Offentlig nøkkel | Your node’s public key (read-only) | . | Admin Key | Keys permitted to administer this node remotely — up to three | . | Privat nøkkel | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Regenerate Private Key | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Serial console | Serial console over the Stream API | . | Debug log API enabled | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Managed Mode | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Backup Keys | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ", + "content": "Device Config . On Settings → Device configuration → Device. | Setting | Beskrivelse | Default | . | Device Role | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Rebroadcast Mode | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Node Info Broadcast Interval | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Double Tap as Button | Treat a double tap as a button press | Disabled | . | Triple Click Ad Hoc Ping | Send an ad-hoc position ping on a triple click | Enabled | . | LED Heartbeat | Blink the status LED periodically | Enabled | . | Time Zone | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRa Config . On Settings → LoRa. | Setting | Beskrivelse | Default | . | Region | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Presets | Speed/range tradeoff | LongFast | . | Number of Hops | Maximum retransmit hops | 3 | . | Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) | . | Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Frequency Slot | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Transmit Enabled | Turning this off makes the node receive-only | On | . | Override Duty Cycle | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | . | Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | . | RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | . | PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Speed | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Beskrivelse | . | Screen on for | How long the display stays lit before sleeping | . | Carousel interval | How often the node cycles between screens on its own | . | Display mode | Screen layout/density used by the firmware | . | Display units | Metric or Imperial on the node’s screen | . | Use 12h clock format | Show the node’s clock as 12-hour rather than 24-hour | . | Bold Heading | Draw the screen’s heading text in bold | . | Flip screen | Rotate the display 180° for an inverted mounting | . | OLED type | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Wake on tap or motion | Light the screen when the node is tapped or moved | . | Compass orientation | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Always point north | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Position Config . On Settings → Device configuration → Position. | Setting | Beskrivelse | . | GPS Mode (Physical Hardware) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Polling Interval | How often the node asks its GPS for a fix | . | Broadcast Interval | How often the position is shared with the mesh | . | Smart Position | Broadcast based on movement rather than purely on the clock | . | Smart Interval | With Smart Position on, the shortest gap between broadcasts | . | Smart Distance | With Smart Position on, how far you must move before broadcasting | . | Fixed Position | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Position Flags | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Power Config . On Settings → Device configuration → Power. | Setting | Beskrivelse | . | Enable power saving mode | Let the node sleep aggressively between activity | . | Shutdown on power loss | Power the device down after external power disappears | . | Super deep sleep duration | How long the deepest sleep state lasts | . | Minimum wake time | The shortest time the node stays awake once woken | . | Wait for Bluetooth duration | How long to wait for a phone to connect before sleeping | . | ADC multiplier override | Turn on a manual correction for battery-voltage readings | . | ADC multiplier override ratio | The correction factor itself, used only when the override is on | . | Battery INA_2XX I2C address | Address of an external INA-series power sensor, if fitted | . Network Config . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Beskrivelse | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Password | Network password | . | Ethernet enabled | Use a wired connection on hardware that has one | . | IPv4 mode | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | NTP server | Time synchronization server | . | rsyslog server | Remote logging server | . Bluetooth Config . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Beskrivelse | . | Bluetooth enabled | Enable/disable BLE radio | . | Pairing mode | Fixed PIN, Random PIN, or No PIN | . | Fixed PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Security Config . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Beskrivelse | . | Offentlig nøkkel | Your node’s public key (read-only) | . | Admin Key | Keys permitted to administer this node remotely — up to three | . | Privat nøkkel | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Regenerate Private Key | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Serial console | Serial console over the Stream API | . | Debug log API enabled | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Managed Mode | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Backup Keys | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ", "url": "/Meshtastic-Android/main/no-rNO/user/settings-radio-user.html#configuration", "relUrl": "/no-rNO/user/settings-radio-user.html#configuration" @@ -31354,7 +31354,7 @@ },"4479": { "doc": "Settings — Radio & User", "title": "Configuration", - "content": "Eszközbeállítások . On Settings → Device configuration → Device. | Setting | Leírás | Alapértelmezett | . | Eszköz szerepköre | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Újrasugárzási mód | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Csomópont-információ sugárzási időköze | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Dupla koppintás mint gomb | Treat a double tap as a button press | Disabled | . | Háromszori kattintás – ad hoc ping | Send an ad-hoc position ping on a triple click | Engedélyezve | . | LED ütemjelzés | Blink the status LED periodically | Engedélyezve | . | Időzóna | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRa beállítások . On Settings → LoRa. | Setting | Leírás | Alapértelmezett | . | Régió | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Előbeállítások | Speed/range tradeoff | LongFast | . | Ugrások száma | Maximum retransmit hops | 3 | . | Adásteljesítmény | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frekvencia felülbírálása | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Előbeállítás használata | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Szórási Faktor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Kódolási ráta | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Sávszélesség | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Frekvencia sáv | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Adás engedélyezve | Turning this off makes the node receive-only | On | . | Duty Cycle felülbírálása | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | . | MQTT figyelmen kívül hagyása | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | MQTT-re továbbítható | Allow your packets to be forwarded to MQTT by gateways | Off | . | RX fokozott erősítés | Extra receive gain on SX126x radios; costs a little current | Off | . | PA ventilátor letiltva | Turn off the power-amplifier fan on hardware that has one | Off | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Sebesség | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Kijelző beállítások . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Leírás | . | Kijelző bekapcsolva ennyi ideig | How long the display stays lit before sleeping | . | Karusszel időköz | How often the node cycles between screens on its own | . | Kijelző mód | Screen layout/density used by the firmware | . | Mértékegységek megjelenítése | Metric or Imperial on the node’s screen | . | 12 órás időformátum használata | Show the node’s clock as 12-hour rather than 24-hour | . | Félkövér címsor | Draw the screen’s heading text in bold | . | Kijelző megfordítása | Rotate the display 180° for an inverted mounting | . | OLED típus | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Érintésre vagy mozgásra ébresztés | Light the screen when the node is tapped or moved | . | Iránytű tájolás | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Mindig észak felé mutasson | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Pozíció beállítások . On Settings → Device configuration → Position. | Setting | Leírás | . | GPS mód (fizikai hardver) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Polling Interval | How often the node asks its GPS for a fix | . | Sugárzási időköz | How often the position is shared with the mesh | . | Intelligens pozíció | Broadcast based on movement rather than purely on the clock | . | Smart Interval | With Smart Position on, the shortest gap between broadcasts | . | Smart Distance | With Smart Position on, how far you must move before broadcasting | . | Rögzített pozíció | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Pozíció jelzők (flags) | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Energia-beállítások . On Settings → Device configuration → Power. | Setting | Leírás | . | Energiatakarékos mód engedélyezése | Let the node sleep aggressively between activity | . | Leállítás áramszünet esetén | Power the device down after external power disappears | . | Szuper mélyalvás időtartama | How long the deepest sleep state lasts | . | Minimális ébrenléti idő | The shortest time the node stays awake once woken | . | Bluetooth-várakozás időtartama | How long to wait for a phone to connect before sleeping | . | ADC szorzó felülbírálása | Turn on a manual correction for battery-voltage readings | . | ADC szorzó felülbírálási arány | The correction factor itself, used only when the override is on | . | Akkumulátor INA_2XX I2C-cím | Address of an external INA-series power sensor, if fitted | . Hálózati beállítások . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Leírás | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Jelszó | Network password | . | Ethernet engedélyezve | Use a wired connection on hardware that has one | . | IPv4 mód | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | NTP szerver | Time synchronization server | . | rsyslog szerver | Remote logging server | . Bluetooth beállítások . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Leírás | . | Bluetooth engedélyezve | Enable/disable BLE radio | . | Párosítási mód | Fixed PIN, Random PIN, or No PIN | . | Rögzített PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Biztonsági beállítások . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Leírás | . | Nyilvános kulcs | Your node’s public key (read-only) | . | Admin kulcs | Keys permitted to administer this node remotely — up to three | . | Privát kulcs | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Privát kulcs újragenerálása | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Soros konzol | Serial console over the Stream API | . | Hibakeresési napló API engedélyezve | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Felügyelt mód | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Backup Keys | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ", + "content": "Eszközbeállítások . On Settings → Device configuration → Device. | Setting | Leírás | Alapértelmezett | . | Eszköz szerepköre | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Újrasugárzási mód | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Csomópont-információ sugárzási időköze | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Dupla koppintás mint gomb | Treat a double tap as a button press | Disabled | . | Háromszori kattintás – ad hoc ping | Send an ad-hoc position ping on a triple click | Engedélyezve | . | LED ütemjelzés | Blink the status LED periodically | Engedélyezve | . | Időzóna | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRa beállítások . On Settings → LoRa. | Setting | Leírás | Alapértelmezett | . | Régió | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Előbeállítások | Speed/range tradeoff | LongFast | . | Ugrások száma | Maximum retransmit hops | 3 | . | Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) | . | Frekvencia felülbírálása | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Előbeállítás használata | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Szórási Faktor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Kódolási ráta | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Sávszélesség | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Frekvencia sáv | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Adás engedélyezve | Turning this off makes the node receive-only | On | . | Duty Cycle felülbírálása | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | . | MQTT figyelmen kívül hagyása | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | MQTT-re továbbítható | Allow your packets to be forwarded to MQTT by gateways | Off | . | RX fokozott erősítés | Extra receive gain on SX126x radios; costs a little current | Off | . | PA ventilátor letiltva | Turn off the power-amplifier fan on hardware that has one | Off | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Sebesség | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Kijelző beállítások . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Leírás | . | Kijelző bekapcsolva ennyi ideig | How long the display stays lit before sleeping | . | Karusszel időköz | How often the node cycles between screens on its own | . | Kijelző mód | Screen layout/density used by the firmware | . | Mértékegységek megjelenítése | Metric or Imperial on the node’s screen | . | 12 órás időformátum használata | Show the node’s clock as 12-hour rather than 24-hour | . | Félkövér címsor | Draw the screen’s heading text in bold | . | Kijelző megfordítása | Rotate the display 180° for an inverted mounting | . | OLED típus | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Érintésre vagy mozgásra ébresztés | Light the screen when the node is tapped or moved | . | Iránytű tájolás | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Mindig észak felé mutasson | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Pozíció beállítások . On Settings → Device configuration → Position. | Setting | Leírás | . | GPS mód (fizikai hardver) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Polling Interval | How often the node asks its GPS for a fix | . | Sugárzási időköz | How often the position is shared with the mesh | . | Intelligens pozíció | Broadcast based on movement rather than purely on the clock | . | Smart Interval | With Smart Position on, the shortest gap between broadcasts | . | Smart Distance | With Smart Position on, how far you must move before broadcasting | . | Rögzített pozíció | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Pozíció jelzők (flags) | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Energia-beállítások . On Settings → Device configuration → Power. | Setting | Leírás | . | Energiatakarékos mód engedélyezése | Let the node sleep aggressively between activity | . | Leállítás áramszünet esetén | Power the device down after external power disappears | . | Szuper mélyalvás időtartama | How long the deepest sleep state lasts | . | Minimális ébrenléti idő | The shortest time the node stays awake once woken | . | Bluetooth-várakozás időtartama | How long to wait for a phone to connect before sleeping | . | ADC szorzó felülbírálása | Turn on a manual correction for battery-voltage readings | . | ADC szorzó felülbírálási arány | The correction factor itself, used only when the override is on | . | Akkumulátor INA_2XX I2C-cím | Address of an external INA-series power sensor, if fitted | . Hálózati beállítások . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Leírás | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Jelszó | Network password | . | Ethernet engedélyezve | Use a wired connection on hardware that has one | . | IPv4 mód | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | NTP szerver | Time synchronization server | . | rsyslog szerver | Remote logging server | . Bluetooth beállítások . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Leírás | . | Bluetooth engedélyezve | Enable/disable BLE radio | . | Párosítási mód | Fixed PIN, Random PIN, or No PIN | . | Rögzített PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Biztonsági beállítások . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Leírás | . | Nyilvános kulcs | Your node’s public key (read-only) | . | Admin kulcs | Keys permitted to administer this node remotely — up to three | . | Privát kulcs | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Privát kulcs újragenerálása | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Soros konzol | Serial console over the Stream API | . | Hibakeresési napló API engedélyezve | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Felügyelt mód | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Backup Keys | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ", "url": "/Meshtastic-Android/main/hu-rHU/user/settings-radio-user.html#configuration", "relUrl": "/hu-rHU/user/settings-radio-user.html#configuration" @@ -31396,7 +31396,7 @@ },"4485": { "doc": "Настройки - Радио и пользователь", "title": "Настройки", - "content": "Настройки устройства . On Settings → Device configuration → Device. | Настройка | Описание | По умолчанию | . | Роль устройства | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Режим ретрансляции | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Интервал вещания передачи информации об узле | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Двойное нажатие как кнопка | Treat a double tap as a button press | Включено | . | Маякнуть при тройном нажатии | Send an ad-hoc position ping on a triple click | Включено | . | Сердцебиение светодиодом | Blink the status LED periodically | Включено | . | Часовой пояс | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . Настройка LoRa . On Settings → LoRa. | Настройка | Описание | По умолчанию | . | Регион / Страна | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Не установлено (необходимо настроить) | . | Шаблоны | Компромисс между скоростью и дальностью | LongFast | . | Количество прыжков | Максимальное количество ретрансляций | 3 | . | Мощность передатчика | Мощность передачи (дБм); 0 = максимально разрешённая для региона | 0 (максимум региона) | . | Переопределить частоту | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Использовать шаблон | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Коэффициент распространения | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Частота кодирования | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Ширина канала | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Частота слота | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Передача включена | Turning this off makes the node receive-only | On | . | Переопределить рабочий цикл | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Выкл | . | Игнорировать MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | ОК в MQTT | Allow your packets to be forwarded to MQTT by gateways | Выкл | . | Усиление RX | Extra receive gain on SX126x radios; costs a little current | Выкл | . | PA вентилятор выключен | Turn off the power-amplifier fan on hardware that has one | Выкл | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. Смотрите руководство по настройке региона на сайте meshtastic.org для получения подробной информации. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Совет: Значения порога SNR специально отрицательные. LoRa может декодировать сигналы ниже уровня шума, поэтому более отрицательный предел означает, что пресет допускает более слабый, шумный сигнал (больший радиус действия). Смотрите Как работает измеритель сигнала для полного объяснения. | Предустановка | Диапазон | Скорость | Предел SNR | Лучше всего для | . | Short Turbo | ~1 км | 21.9 кб/с | −7.5 дБ | Плотная городская застройка с прямой видимостью; приложения, требующие высокой передачи данных | . | Short Fast | ~3 км | 10.9 кб/с | −7.5 дБ | Городские районы; здания в пределах нескольких кварталов | . | Short Slow | ~5 км | 6.25 kbps | -10 дБ | Пригородная зона с коротким диапазоном; умеренная плотность застройки | . | Medium Fast | ~5 км | 3.52 kbps | −12.5 дБ | Пригородные районы; умеренная плотность застройки | . | Medium Slow | ~8 км | 1.95 kbps | -15 дБ | Пригородный/сельский; умеренный диапазон со сниженной скоростью | . | Long Turbo | ~10 км | 1.34 kbps | −17.5 дБ | Диапазон, похожий на Long Fast, но с полосой пропускания 500 кГц; более высокая пропускная способность | . | Long Fast | ~10 км | 1.1 кб/с | −17.5 дБ | Общее использование (по умолчанию) — сбалансированный диапазон и скорость | . | Long Moderate | ~20 км | 0.34 кб/с | −17.5 дБ | Сельская местность с некоторым рельефом; случайное использование | . | Lite Fast | ~5 км | 1.76 kbps | −12.5 дБ | Диапазон RU 866 МГц SRD (ширина полосы 125 кГц); аналогично Medium Fast | . | Lite Slow | ~10 км | 0.98 kbps | -15 дБ | Диапазон RU 866 МГц SRD (ширина полосы 125 кГц); аналогично Long Fast | . | Narrow Fast | ~5 км | 2.28 kbps | −7.5 дБ | Диапазон RU 868 МГц (полоса пропускания 62,5 кГц); предотвращает помехи с другими устройствами | . | Narrow Slow | ~10 км | 1.30 kbps | -10 дБ | Диапазон RU 868 МГц (ширина полосы 62,5 кГц); аналогично Long Fast | . | Medium Turbo | ~5 км | 7.0 kbps | −12.5 дБ | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 км | 0.68 kbps | −7.5 дБ | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 км | 0.33 kbps | -10 дБ | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 км | 0.18 кб/с | −20 дБ | ⚠️ Устарел — всё ещё доступен для выбора, но может быть удален в будущих версиях прошивки | . | Very Long Slow | ~40+ км | 0.09 кб/с | −20 дБ | ⚠️ Устарел — всё ещё доступен для выбора, но может быть удален в будущих версиях прошивки | . i Примечание: В этой таблице используются общие короткие имена. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . Предустановка модема управляет основным компромиссом между дальностью и скоростью передачи данных: . | Медленные предустановки используют большее распространение, что позволяет декодировать сигналы при более слабых уровнях сигнала (ниже порога SNR). Это означает большую дальность, но меньше байт в секунду. | Быстрые предустановки передают больше данных за одну передачу, но требуют более сильного сигнала для декодирования. | . Практическое руководство: . | Городская сеть (много нод, короткие расстояния): Используй Long Fast (по умолчанию) или Short Fast. Более высокая скорость означает меньшее переполнение канала эфирного времени, когда многие ноды используют канал. | Сельская/разреженная сеть (мало нод, большие расстояния): Используй Long Moderate. Дальность важнее скорости, когда ноды находятся далеко друг от друга. | Соответствие нормативным требованиям RU 866/868 МГц: Используй Lite Fast, Lite Slow, Narrow Fast или Narrow Slow — они оптимизированы для диапазонов RU SRD/868 МГц с более узкой полосой пропускания. | Фиксированные инфраструктурные связи: Используй Short Turbo или Long Turbo для выделенных соединений точка-точка с хорошими антеннами и прямой видимостью. | Смешанные среды: Используй Long Fast — это настройка по умолчанию в сообществе и она обеспечит совместимость с другими в вашем регионе. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Преимущество высоты (вершина холма, крыша) значительно увеличивает эффективную дальность. Хорошо размещённый маршрутизатор с Long Fast часто может превзойти наземную ноду с Long Slow. Параметры дисплея . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Настройка | Описание | . | Включать экран на | How long the display stays lit before sleeping | . | Интервал карусели | How often the node cycles between screens on its own | . | Режим экрана | Screen layout/density used by the firmware | . | Система измерения | Metric or Imperial on the node’s screen | . | Использовать 12-часовой формат времени | Show the node’s clock as 12-hour rather than 24-hour | . | Выделять заголовок жирным | Draw the screen’s heading text in bold | . | Повернуть экран | Rotate the display 180° for an inverted mounting | . | Тип OLED | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Включать экран при касании или движении | Light the screen when the node is tapped or moved | . | Направление компаса | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Всегда указывать на север | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Настройки местоположения . On Settings → Device configuration → Position. | Настройка | Описание | . | Режим GPS (физическое оборудование) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | Интервал опроса GPS | How often the node asks its GPS for a fix | . | Период рассылки | How often the position is shared with the mesh | . | Умная позиция | Broadcast based on movement rather than purely on the clock | . | Умный интервал | With Smart Position on, the shortest gap between broadcasts | . | Умное расстояние | With Smart Position on, how far you must move before broadcasting | . | Фиксированная позиция | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Флаги позиции | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Настройка питания . On Settings → Device configuration → Power. | Настройка | Описание | . | Включить режим энергосбережения | Let the node sleep aggressively between activity | . | Выключение при потере мощности | Power the device down after external power disappears | . | Длительность супер-глубокого сна | How long the deepest sleep state lasts | . | Минимальное время бодрствования | The shortest time the node stays awake once woken | . | Длительность ожидания Bluetooth | How long to wait for a phone to connect before sleeping | . | Коэффициент переопределения ADC | Turn on a manual correction for battery-voltage readings | . | Коэффициент переопределения ADC | The correction factor itself, used only when the override is on | . | I2C-адрес INA_2XX батареи | Address of an external INA-series power sensor, if fitted | . Настройка сети . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Настройка | Описание | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | Название сети | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Пароль | Пароль сети | . | Ethernet включен | Use a wired connection on hardware that has one | . | Режим IPv4 | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP трансляция | Share mesh traffic with other nodes over the local network | . | NTP-сервер | Сервер синхронизации времени | . | Сервер rsyslog | Удалённый сервер логирования | . Настройка Bluetooth . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Настройка | Описание | . | Bluetooth включен | Включение/отключение BLE радиостанции | . | Режим сопряжения | Фиксированный PIN, случайный PIN или без PIN | . | Фиксированный PIN-код | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Настройки безопасности . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Настройка | Описание | . | Публичный ключ | Публичный ключ твоей ноды (только для чтения) | . | Ключ администратора | Keys permitted to administer this node remotely — up to three | . | Приватный ключ | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Пересоздать приватный ключ | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Канал администратора включен | ⚠️ Удалено — теперь настраивается автоматически при установке ключа администратора | . | Консоль COM-порта | Serial console over the Stream API | . | API журнала отладки включен | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Управляемый режим | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Резервное копирование | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Восстановить ключи | Запишисать сохранённые ключи обратно на ноду (доступно, как только есть резервная копия) | . | Удалить резервную копию ключа | Remove the stored key backup from this phone | . | Уровень защиты | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | Что она делает | . | Осталось загрузок | How many device boots the unlocked state survives | . | Часов до истечения | Wall-clock lifetime of the unlocked state | . | Ограничение сессии (минуты) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ", + "content": "Настройки устройства . On Settings → Device configuration → Device. | Настройка | Описание | По умолчанию | . | Роль устройства | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Режим ретрансляции | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Интервал вещания передачи информации об узле | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Двойное нажатие как кнопка | Treat a double tap as a button press | Включено | . | Маякнуть при тройном нажатии | Send an ad-hoc position ping on a triple click | Включено | . | Сердцебиение светодиодом | Blink the status LED periodically | Включено | . | Часовой пояс | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . Настройка LoRa . On Settings → LoRa. | Настройка | Описание | По умолчанию | . | Регион / Страна | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Не установлено (необходимо настроить) | . | Шаблоны | Компромисс между скоростью и дальностью | LongFast | . | Количество прыжков | Максимальное количество ретрансляций | 3 | . | Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (максимум региона) | . | Переопределить частоту | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Использовать шаблон | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Коэффициент распространения | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Частота кодирования | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Ширина канала | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Частота слота | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Передача включена | Turning this off makes the node receive-only | On | . | Переопределить рабочий цикл | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Выкл | . | Игнорировать MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | ОК в MQTT | Allow your packets to be forwarded to MQTT by gateways | Выкл | . | Усиление RX | Extra receive gain on SX126x radios; costs a little current | Выкл | . | PA вентилятор выключен | Turn off the power-amplifier fan on hardware that has one | Выкл | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. Смотрите руководство по настройке региона на сайте meshtastic.org для получения подробной информации. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Совет: Значения порога SNR специально отрицательные. LoRa может декодировать сигналы ниже уровня шума, поэтому более отрицательный предел означает, что пресет допускает более слабый, шумный сигнал (больший радиус действия). Смотрите Как работает измеритель сигнала для полного объяснения. | Предустановка | Диапазон | Скорость | Предел SNR | Лучше всего для | . | Short Turbo | ~1 км | 21.9 кб/с | −7.5 дБ | Плотная городская застройка с прямой видимостью; приложения, требующие высокой передачи данных | . | Short Fast | ~3 км | 10.9 кб/с | −7.5 дБ | Городские районы; здания в пределах нескольких кварталов | . | Short Slow | ~5 км | 6.25 kbps | -10 дБ | Пригородная зона с коротким диапазоном; умеренная плотность застройки | . | Medium Fast | ~5 км | 3.52 kbps | −12.5 дБ | Пригородные районы; умеренная плотность застройки | . | Medium Slow | ~8 км | 1.95 kbps | -15 дБ | Пригородный/сельский; умеренный диапазон со сниженной скоростью | . | Long Turbo | ~10 км | 1.34 kbps | −17.5 дБ | Диапазон, похожий на Long Fast, но с полосой пропускания 500 кГц; более высокая пропускная способность | . | Long Fast | ~10 км | 1.1 кб/с | −17.5 дБ | Общее использование (по умолчанию) — сбалансированный диапазон и скорость | . | Long Moderate | ~20 км | 0.34 кб/с | −17.5 дБ | Сельская местность с некоторым рельефом; случайное использование | . | Lite Fast | ~5 км | 1.76 kbps | −12.5 дБ | Диапазон RU 866 МГц SRD (ширина полосы 125 кГц); аналогично Medium Fast | . | Lite Slow | ~10 км | 0.98 kbps | -15 дБ | Диапазон RU 866 МГц SRD (ширина полосы 125 кГц); аналогично Long Fast | . | Narrow Fast | ~5 км | 2.28 kbps | −7.5 дБ | Диапазон RU 868 МГц (полоса пропускания 62,5 кГц); предотвращает помехи с другими устройствами | . | Narrow Slow | ~10 км | 1.30 kbps | -10 дБ | Диапазон RU 868 МГц (ширина полосы 62,5 кГц); аналогично Long Fast | . | Medium Turbo | ~5 км | 7.0 kbps | −12.5 дБ | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 км | 0.68 kbps | −7.5 дБ | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 км | 0.33 kbps | -10 дБ | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 км | 0.18 кб/с | −20 дБ | ⚠️ Устарел — всё ещё доступен для выбора, но может быть удален в будущих версиях прошивки | . | Very Long Slow | ~40+ км | 0.09 кб/с | −20 дБ | ⚠️ Устарел — всё ещё доступен для выбора, но может быть удален в будущих версиях прошивки | . i Примечание: В этой таблице используются общие короткие имена. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . Предустановка модема управляет основным компромиссом между дальностью и скоростью передачи данных: . | Медленные предустановки используют большее распространение, что позволяет декодировать сигналы при более слабых уровнях сигнала (ниже порога SNR). Это означает большую дальность, но меньше байт в секунду. | Быстрые предустановки передают больше данных за одну передачу, но требуют более сильного сигнала для декодирования. | . Практическое руководство: . | Городская сеть (много нод, короткие расстояния): Используй Long Fast (по умолчанию) или Short Fast. Более высокая скорость означает меньшее переполнение канала эфирного времени, когда многие ноды используют канал. | Сельская/разреженная сеть (мало нод, большие расстояния): Используй Long Moderate. Дальность важнее скорости, когда ноды находятся далеко друг от друга. | Соответствие нормативным требованиям RU 866/868 МГц: Используй Lite Fast, Lite Slow, Narrow Fast или Narrow Slow — они оптимизированы для диапазонов RU SRD/868 МГц с более узкой полосой пропускания. | Фиксированные инфраструктурные связи: Используй Short Turbo или Long Turbo для выделенных соединений точка-точка с хорошими антеннами и прямой видимостью. | Смешанные среды: Используй Long Fast — это настройка по умолчанию в сообществе и она обеспечит совместимость с другими в вашем регионе. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Преимущество высоты (вершина холма, крыша) значительно увеличивает эффективную дальность. Хорошо размещённый маршрутизатор с Long Fast часто может превзойти наземную ноду с Long Slow. Параметры дисплея . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Настройка | Описание | . | Включать экран на | How long the display stays lit before sleeping | . | Интервал карусели | How often the node cycles between screens on its own | . | Режим экрана | Screen layout/density used by the firmware | . | Система измерения | Metric or Imperial on the node’s screen | . | Использовать 12-часовой формат времени | Show the node’s clock as 12-hour rather than 24-hour | . | Выделять заголовок жирным | Draw the screen’s heading text in bold | . | Повернуть экран | Rotate the display 180° for an inverted mounting | . | Тип OLED | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Включать экран при касании или движении | Light the screen when the node is tapped or moved | . | Направление компаса | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Всегда указывать на север | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Настройки местоположения . On Settings → Device configuration → Position. | Настройка | Описание | . | Режим GPS (физическое оборудование) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | Интервал опроса GPS | How often the node asks its GPS for a fix | . | Период рассылки | How often the position is shared with the mesh | . | Умная позиция | Broadcast based on movement rather than purely on the clock | . | Умный интервал | With Smart Position on, the shortest gap between broadcasts | . | Умное расстояние | With Smart Position on, how far you must move before broadcasting | . | Фиксированная позиция | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Флаги позиции | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Настройка питания . On Settings → Device configuration → Power. | Настройка | Описание | . | Включить режим энергосбережения | Let the node sleep aggressively between activity | . | Выключение при потере мощности | Power the device down after external power disappears | . | Длительность супер-глубокого сна | How long the deepest sleep state lasts | . | Минимальное время бодрствования | The shortest time the node stays awake once woken | . | Длительность ожидания Bluetooth | How long to wait for a phone to connect before sleeping | . | Коэффициент переопределения ADC | Turn on a manual correction for battery-voltage readings | . | Коэффициент переопределения ADC | The correction factor itself, used only when the override is on | . | I2C-адрес INA_2XX батареи | Address of an external INA-series power sensor, if fitted | . Настройка сети . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Настройка | Описание | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | Название сети | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Пароль | Пароль сети | . | Ethernet включен | Use a wired connection on hardware that has one | . | Режим IPv4 | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP трансляция | Share mesh traffic with other nodes over the local network | . | NTP-сервер | Сервер синхронизации времени | . | Сервер rsyslog | Удалённый сервер логирования | . Настройка Bluetooth . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Настройка | Описание | . | Bluetooth включен | Включение/отключение BLE радиостанции | . | Режим сопряжения | Фиксированный PIN, случайный PIN или без PIN | . | Фиксированный PIN-код | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Настройки безопасности . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Настройка | Описание | . | Публичный ключ | Публичный ключ твоей ноды (только для чтения) | . | Ключ администратора | Keys permitted to administer this node remotely — up to three | . | Приватный ключ | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Пересоздать приватный ключ | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Канал администратора включен | ⚠️ Удалено — теперь настраивается автоматически при установке ключа администратора | . | Консоль COM-порта | Serial console over the Stream API | . | API журнала отладки включен | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Управляемый режим | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Резервное копирование | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Восстановить ключи | Запишисать сохранённые ключи обратно на ноду (доступно, как только есть резервная копия) | . | Удалить резервную копию ключа | Remove the stored key backup from this phone | . | Уровень защиты | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | Что она делает | . | Осталось загрузок | How many device boots the unlocked state survives | . | Часов до истечения | Wall-clock lifetime of the unlocked state | . | Ограничение сессии (минуты) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ", "url": "/Meshtastic-Android/main/ru-rRU/user/settings-radio-user.html#%D0%BD%D0%B0%D1%81%D1%82%D1%80%D0%BE%D0%B9%D0%BA%D0%B8", "relUrl": "/ru-rRU/user/settings-radio-user.html#настройки" @@ -31431,7 +31431,7 @@ },"4490": { "doc": "Settings — Radio & User", "title": "Nastavení", - "content": "Nastavení zařízení . On Settings → Device configuration → Device. | Nastavení | Popis | Výchozí | . | Role zařízení | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Režim opětovného vysílání | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Interval vysílání Node Info | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Dvojité klepnutí jako stisk tlačítka | Treat a double tap as a button press | Disabled | . | Okamžitý ping (trojitý stisk) | Send an ad-hoc position ping on a triple click | Povoleno | . | Blikání LED při provozu | Blink the status LED periodically | Povoleno | . | Časové pásmo | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRa nastavení . On Settings → LoRa. | Nastavení | Popis | Výchozí | . | Region | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Předvolby | Speed/range tradeoff | LongFast | . | Počet skoků | Maximum retransmit hops | 3 | . | Vysílací výkon | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Ruční nastavení frekvence | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Použít předvolbu | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Šířka pásma | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Frekvenční slot | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Vysílání povoleno | Turning this off makes the node receive-only | On | . | Přepsat pracovní cyklus | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Vypnuto | . | Ignorovat MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | OK do MQTT | Allow your packets to be forwarded to MQTT by gateways | Vypnuto | . | Zvýšené zesílení přijímače (RX) | Extra receive gain on SX126x radios; costs a little current | Vypnuto | . | PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Vypnuto | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Rychlost | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Nastavení zobrazení . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Nastavení | Popis | . | Obrazovka zapnutá po dobu | How long the display stays lit before sleeping | . | Interval přepínání obrazovek | How often the node cycles between screens on its own | . | Režim obrazovky | Screen layout/density used by the firmware | . | Zobrazení jednotek | Metric or Imperial on the node’s screen | . | Použít 12h formát hodin | Show the node’s clock as 12-hour rather than 24-hour | . | Tučný nadpis | Draw the screen’s heading text in bold | . | Překlopit obrazovku | Rotate the display 180° for an inverted mounting | . | Typ OLED displeje | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Probuzení klepnutím nebo pohybem | Light the screen when the node is tapped or moved | . | Orientace kompasu | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Vždy ukazovat na sever | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Nastavení pozice . On Settings → Device configuration → Position. | Nastavení | Popis | . | Režim GPS (fyzický modul) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | Interval aktualizace GPS | How often the node asks its GPS for a fix | . | Interval vysílání | How often the position is shared with the mesh | . | Chytrá poloha | Broadcast based on movement rather than purely on the clock | . | Chytrý Interval | With Smart Position on, the shortest gap between broadcasts | . | Chytrá vzdálenost | With Smart Position on, how far you must move before broadcasting | . | Pevná poloha | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Příznaky polohy | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Nastavení napájení . On Settings → Device configuration → Power. | Nastavení | Popis | . | Povolit úsporný režim | Let the node sleep aggressively between activity | . | Vypnutí při ztrátě napájení | Power the device down after external power disappears | . | Doba super hlubokého spánku | How long the deepest sleep state lasts | . | Minimální doba probuzení | The shortest time the node stays awake once woken | . | Doba čekání na Bluetooth | How long to wait for a phone to connect before sleeping | . | Přepsání násobiče ADC | Turn on a manual correction for battery-voltage readings | . | Vlastní hodnota násobiče pro ADC | The correction factor itself, used only when the override is on | . | Adresa INA_2XX I2C baterie | Address of an external INA-series power sensor, if fitted | . Nastavení sítě . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Nastavení | Popis | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Heslo | Network password | . | Ethernet povolen | Use a wired connection on hardware that has one | . | Režim IPv4 | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP vysílání | Share mesh traffic with other nodes over the local network | . | NTP server | Time synchronization server | . | rsyslog server | Remote logging server | . Nastavení bluetooth . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Nastavení | Popis | . | Bluetooth povoleno | Enable/disable BLE radio | . | Režim párování | Fixed PIN, Random PIN, or No PIN | . | Pevný PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Nastavení zabezpečení . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Nastavení | Popis | . | Veřejný klíč | Your node’s public key (read-only) | . | Administrátorský klíč | Keys permitted to administer this node remotely — up to three | . | Soukromý klíč | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Obnovit soukromý klíč | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Sériová komunikace | Serial console over the Stream API | . | Ladící protokol API povolen | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Řízený režim | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Záloha klíčů | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Obnovit klíče | Write the backed-up keys back to the node (available once a backup exists) | . | Smazat zálohu klíče | Remove the stored key backup from this phone | . | Úroveň ochrany | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Zbývající počet restartů | How many device boots the unlocked state survives | . | Hodiny do vypršení platnosti | Wall-clock lifetime of the unlocked state | . | Limit relace (minuty) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ", + "content": "Nastavení zařízení . On Settings → Device configuration → Device. | Nastavení | Popis | Výchozí | . | Role zařízení | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Režim opětovného vysílání | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Interval vysílání Node Info | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Dvojité klepnutí jako stisk tlačítka | Treat a double tap as a button press | Disabled | . | Okamžitý ping (trojitý stisk) | Send an ad-hoc position ping on a triple click | Povoleno | . | Blikání LED při provozu | Blink the status LED periodically | Povoleno | . | Časové pásmo | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRa nastavení . On Settings → LoRa. | Nastavení | Popis | Výchozí | . | Region | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Předvolby | Speed/range tradeoff | LongFast | . | Počet skoků | Maximum retransmit hops | 3 | . | Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) | . | Ruční nastavení frekvence | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Použít předvolbu | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Šířka pásma | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Frekvenční slot | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Vysílání povoleno | Turning this off makes the node receive-only | On | . | Přepsat pracovní cyklus | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Vypnuto | . | Ignorovat MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | OK do MQTT | Allow your packets to be forwarded to MQTT by gateways | Vypnuto | . | Zvýšené zesílení přijímače (RX) | Extra receive gain on SX126x radios; costs a little current | Vypnuto | . | PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Vypnuto | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Rychlost | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Nastavení zobrazení . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Nastavení | Popis | . | Obrazovka zapnutá po dobu | How long the display stays lit before sleeping | . | Interval přepínání obrazovek | How often the node cycles between screens on its own | . | Režim obrazovky | Screen layout/density used by the firmware | . | Zobrazení jednotek | Metric or Imperial on the node’s screen | . | Použít 12h formát hodin | Show the node’s clock as 12-hour rather than 24-hour | . | Tučný nadpis | Draw the screen’s heading text in bold | . | Překlopit obrazovku | Rotate the display 180° for an inverted mounting | . | Typ OLED displeje | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Probuzení klepnutím nebo pohybem | Light the screen when the node is tapped or moved | . | Orientace kompasu | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Vždy ukazovat na sever | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Nastavení pozice . On Settings → Device configuration → Position. | Nastavení | Popis | . | Režim GPS (fyzický modul) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | Interval aktualizace GPS | How often the node asks its GPS for a fix | . | Interval vysílání | How often the position is shared with the mesh | . | Chytrá poloha | Broadcast based on movement rather than purely on the clock | . | Chytrý Interval | With Smart Position on, the shortest gap between broadcasts | . | Chytrá vzdálenost | With Smart Position on, how far you must move before broadcasting | . | Pevná poloha | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Příznaky polohy | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Nastavení napájení . On Settings → Device configuration → Power. | Nastavení | Popis | . | Povolit úsporný režim | Let the node sleep aggressively between activity | . | Vypnutí při ztrátě napájení | Power the device down after external power disappears | . | Doba super hlubokého spánku | How long the deepest sleep state lasts | . | Minimální doba probuzení | The shortest time the node stays awake once woken | . | Doba čekání na Bluetooth | How long to wait for a phone to connect before sleeping | . | Přepsání násobiče ADC | Turn on a manual correction for battery-voltage readings | . | Vlastní hodnota násobiče pro ADC | The correction factor itself, used only when the override is on | . | Adresa INA_2XX I2C baterie | Address of an external INA-series power sensor, if fitted | . Nastavení sítě . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Nastavení | Popis | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Heslo | Network password | . | Ethernet povolen | Use a wired connection on hardware that has one | . | Režim IPv4 | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP vysílání | Share mesh traffic with other nodes over the local network | . | NTP server | Time synchronization server | . | rsyslog server | Remote logging server | . Nastavení bluetooth . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Nastavení | Popis | . | Bluetooth povoleno | Enable/disable BLE radio | . | Režim párování | Fixed PIN, Random PIN, or No PIN | . | Pevný PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Nastavení zabezpečení . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Nastavení | Popis | . | Veřejný klíč | Your node’s public key (read-only) | . | Administrátorský klíč | Keys permitted to administer this node remotely — up to three | . | Soukromý klíč | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Obnovit soukromý klíč | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Sériová komunikace | Serial console over the Stream API | . | Ladící protokol API povolen | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Řízený režim | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Záloha klíčů | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Obnovit klíče | Write the backed-up keys back to the node (available once a backup exists) | . | Smazat zálohu klíče | Remove the stored key backup from this phone | . | Úroveň ochrany | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Zbývající počet restartů | How many device boots the unlocked state survives | . | Hodiny do vypršení platnosti | Wall-clock lifetime of the unlocked state | . | Limit relace (minuty) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ", "url": "/Meshtastic-Android/main/cs-rCZ/user/settings-radio-user.html#nastaven%C3%AD", "relUrl": "/cs-rCZ/user/settings-radio-user.html#nastavení" @@ -31473,7 +31473,7 @@ },"4496": { "doc": "Settings — Radio & User", "title": "Конфигурация", - "content": "Конфигуриране на устройството . On Settings → Device configuration → Device. | Настройка | Описание | По подразбиране | . | Роля на устройството | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Режим на препредаване | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Node Info Broadcast Interval | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Double Tap as Button | Treat a double tap as a button press | Disabled | . | Triple Click Ad Hoc Ping | Send an ad-hoc position ping on a triple click | Активиран | . | LED Heartbeat | Blink the status LED periodically | Активиран | . | Часова зона | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . Конфигуриране на LoRa . On Settings → LoRa. | Настройка | Описание | По подразбиране | . | Регион | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Предварително зададени | Speed/range tradeoff | LongFast | . | Брой отскоци | Maximum retransmit hops | 3 | . | Мощност на предаване | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Използване на предварително зададени настройки | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Широчина на честотната лента | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Честотен слот | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Предаването е активирано | Turning this off makes the node receive-only | On | . | Override Duty Cycle | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | . | Игнориране на MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | . | RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | . | PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Диапазон | Скорост | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Конфигуриране на дисплея . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Настройка | Описание | . | Екранът е включен за | How long the display stays lit before sleeping | . | Carousel interval | How often the node cycles between screens on its own | . | Режим на дисплея | Screen layout/density used by the firmware | . | Показвани единици | Metric or Imperial on the node’s screen | . | Използване на 12ч формат | Show the node’s clock as 12-hour rather than 24-hour | . | Удебелен заглавен шрифт | Draw the screen’s heading text in bold | . | Обръщане на екрана | Rotate the display 180° for an inverted mounting | . | Тип на OLED | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Събуждане при докосване или движение | Light the screen when the node is tapped or moved | . | Ориентация на компаса | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Always point north | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Конфигуриране на позицията . On Settings → Device configuration → Position. | Настройка | Описание | . | Режим на GPS (физически хардуер) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Polling Interval | How often the node asks its GPS for a fix | . | Интервал на излъчване | How often the position is shared with the mesh | . | Интелигентна позиция | Broadcast based on movement rather than purely on the clock | . | Smart Interval | With Smart Position on, the shortest gap between broadcasts | . | Smart Distance | With Smart Position on, how far you must move before broadcasting | . | Фиксирана позиция | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Position Flags | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Конфигуриране на захранването . On Settings → Device configuration → Power. | Настройка | Описание | . | Активиране на енергоспестяващ режим | Let the node sleep aggressively between activity | . | Изключване при загуба на захранване | Power the device down after external power disappears | . | Продължителност на супер дълбок сън | How long the deepest sleep state lasts | . | Минимално време за събуждане | The shortest time the node stays awake once woken | . | Wait for Bluetooth duration | How long to wait for a phone to connect before sleeping | . | ADC multiplier override | Turn on a manual correction for battery-voltage readings | . | ADC multiplier override ratio | The correction factor itself, used only when the override is on | . | I2C адрес на батерията INA_2XX | Address of an external INA-series power sensor, if fitted | . Конфигуриране на мрежата . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Настройка | Описание | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Парола | Парола за мрежата | . | Ethernet е активиран | Use a wired connection on hardware that has one | . | Режим на IPv4 | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | NTP сървър | Time synchronization server | . | rsyslog сървър | Remote logging server | . Конфигуриране на Bluetooth . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Настройка | Описание | . | Bluetooth е активиран | Enable/disable BLE radio | . | Режим на сдвояване | Fixed PIN, Random PIN, or No PIN | . | Фиксиран ПИН | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Конфигуриране на сигурността . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Настройка | Описание | . | Публичен ключ | Your node’s public key (read-only) | . | Администраторски ключ | Keys permitted to administer this node remotely — up to three | . | Частен ключ | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Регенериране на частния ключ | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Серийна конзола | Serial console over the Stream API | . | Debug log API enabled | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Управляем режим | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Backup Keys | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | Какво прави | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ", + "content": "Конфигуриране на устройството . On Settings → Device configuration → Device. | Настройка | Описание | По подразбиране | . | Роля на устройството | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Режим на препредаване | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Node Info Broadcast Interval | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Double Tap as Button | Treat a double tap as a button press | Disabled | . | Triple Click Ad Hoc Ping | Send an ad-hoc position ping on a triple click | Активиран | . | LED Heartbeat | Blink the status LED periodically | Активиран | . | Часова зона | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . Конфигуриране на LoRa . On Settings → LoRa. | Настройка | Описание | По подразбиране | . | Регион | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Предварително зададени | Speed/range tradeoff | LongFast | . | Брой отскоци | Maximum retransmit hops | 3 | . | Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) | . | Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Използване на предварително зададени настройки | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Широчина на честотната лента | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Честотен слот | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Предаването е активирано | Turning this off makes the node receive-only | On | . | Override Duty Cycle | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | . | Игнориране на MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | . | RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | . | PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Диапазон | Скорост | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Конфигуриране на дисплея . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Настройка | Описание | . | Екранът е включен за | How long the display stays lit before sleeping | . | Carousel interval | How often the node cycles between screens on its own | . | Режим на дисплея | Screen layout/density used by the firmware | . | Показвани единици | Metric or Imperial on the node’s screen | . | Използване на 12ч формат | Show the node’s clock as 12-hour rather than 24-hour | . | Удебелен заглавен шрифт | Draw the screen’s heading text in bold | . | Обръщане на екрана | Rotate the display 180° for an inverted mounting | . | Тип на OLED | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Събуждане при докосване или движение | Light the screen when the node is tapped or moved | . | Ориентация на компаса | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Always point north | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Конфигуриране на позицията . On Settings → Device configuration → Position. | Настройка | Описание | . | Режим на GPS (физически хардуер) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Polling Interval | How often the node asks its GPS for a fix | . | Интервал на излъчване | How often the position is shared with the mesh | . | Интелигентна позиция | Broadcast based on movement rather than purely on the clock | . | Smart Interval | With Smart Position on, the shortest gap between broadcasts | . | Smart Distance | With Smart Position on, how far you must move before broadcasting | . | Фиксирана позиция | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Position Flags | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Конфигуриране на захранването . On Settings → Device configuration → Power. | Настройка | Описание | . | Активиране на енергоспестяващ режим | Let the node sleep aggressively between activity | . | Изключване при загуба на захранване | Power the device down after external power disappears | . | Продължителност на супер дълбок сън | How long the deepest sleep state lasts | . | Минимално време за събуждане | The shortest time the node stays awake once woken | . | Wait for Bluetooth duration | How long to wait for a phone to connect before sleeping | . | ADC multiplier override | Turn on a manual correction for battery-voltage readings | . | ADC multiplier override ratio | The correction factor itself, used only when the override is on | . | I2C адрес на батерията INA_2XX | Address of an external INA-series power sensor, if fitted | . Конфигуриране на мрежата . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Настройка | Описание | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Парола | Парола за мрежата | . | Ethernet е активиран | Use a wired connection on hardware that has one | . | Режим на IPv4 | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | NTP сървър | Time synchronization server | . | rsyslog сървър | Remote logging server | . Конфигуриране на Bluetooth . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Настройка | Описание | . | Bluetooth е активиран | Enable/disable BLE radio | . | Режим на сдвояване | Fixed PIN, Random PIN, or No PIN | . | Фиксиран ПИН | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Конфигуриране на сигурността . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Настройка | Описание | . | Публичен ключ | Your node’s public key (read-only) | . | Администраторски ключ | Keys permitted to administer this node remotely — up to three | . | Частен ключ | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Регенериране на частния ключ | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Серийна конзола | Serial console over the Stream API | . | Debug log API enabled | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Управляем режим | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Backup Keys | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | Какво прави | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ", "url": "/Meshtastic-Android/main/bg-rBG/user/settings-radio-user.html#%D0%BA%D0%BE%D0%BD%D1%84%D0%B8%D0%B3%D1%83%D1%80%D0%B0%D1%86%D0%B8%D1%8F", "relUrl": "/bg-rBG/user/settings-radio-user.html#конфигурация" @@ -31515,7 +31515,7 @@ },"4502": { "doc": "Settings — Radio & User", "title": "Configuration", - "content": "Device Config . On Settings → Device configuration → Device. | Setting | Cur síos | Default | . | Device Role | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Rebroadcast Mode | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Node Info Broadcast Interval | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Double Tap as Button | Treat a double tap as a button press | Disabled | . | Triple Click Ad Hoc Ping | Send an ad-hoc position ping on a triple click | Enabled | . | LED Heartbeat | Blink the status LED periodically | Enabled | . | Time Zone | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRa Config . On Settings → LoRa. | Setting | Cur síos | Default | . | Réigiún | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Presets | Speed/range tradeoff | LongFast | . | Number of Hops | Maximum retransmit hops | 3 | . | Transmit Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Frequency Slot | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Transmit Enabled | Turning this off makes the node receive-only | On | . | Override Duty Cycle | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | . | Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | . | RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | . | PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Speed | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Cur síos | . | Screen on for | How long the display stays lit before sleeping | . | Carousel interval | How often the node cycles between screens on its own | . | Display mode | Screen layout/density used by the firmware | . | Display units | Metric or Imperial on the node’s screen | . | Use 12h clock format | Show the node’s clock as 12-hour rather than 24-hour | . | Bold Heading | Draw the screen’s heading text in bold | . | Flip screen | Rotate the display 180° for an inverted mounting | . | OLED type | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Wake on tap or motion | Light the screen when the node is tapped or moved | . | Compass orientation | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Always point north | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Position Config . On Settings → Device configuration → Position. | Setting | Cur síos | . | GPS Mode (Physical Hardware) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Polling Interval | How often the node asks its GPS for a fix | . | Broadcast Interval | How often the position is shared with the mesh | . | Smart Position | Broadcast based on movement rather than purely on the clock | . | Smart Interval | With Smart Position on, the shortest gap between broadcasts | . | Smart Distance | With Smart Position on, how far you must move before broadcasting | . | Fixed Position | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Position Flags | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Power Config . On Settings → Device configuration → Power. | Setting | Cur síos | . | Enable power saving mode | Let the node sleep aggressively between activity | . | Shutdown on power loss | Power the device down after external power disappears | . | Super deep sleep duration | How long the deepest sleep state lasts | . | Minimum wake time | The shortest time the node stays awake once woken | . | Wait for Bluetooth duration | How long to wait for a phone to connect before sleeping | . | ADC multiplier override | Turn on a manual correction for battery-voltage readings | . | ADC multiplier override ratio | The correction factor itself, used only when the override is on | . | Battery INA_2XX I2C address | Address of an external INA-series power sensor, if fitted | . Network Config . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Cur síos | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Password | Network password | . | Ethernet enabled | Use a wired connection on hardware that has one | . | IPv4 mode | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | NTP server | Time synchronization server | . | rsyslog server | Remote logging server | . Bluetooth Config . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Cur síos | . | Bluetooth enabled | Enable/disable BLE radio | . | Pairing mode | Fixed PIN, Random PIN, or No PIN | . | Fixed PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Security Config . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Cur síos | . | Public Key | Your node’s public key (read-only) | . | Admin Key | Keys permitted to administer this node remotely — up to three | . | Private Key | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Regenerate Private Key | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Serial console | Serial console over the Stream API | . | Debug log API enabled | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Managed Mode | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Backup Keys | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ", + "content": "Device Config . On Settings → Device configuration → Device. | Setting | Cur síos | Default | . | Device Role | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Rebroadcast Mode | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Node Info Broadcast Interval | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Double Tap as Button | Treat a double tap as a button press | Disabled | . | Triple Click Ad Hoc Ping | Send an ad-hoc position ping on a triple click | Enabled | . | LED Heartbeat | Blink the status LED periodically | Enabled | . | Time Zone | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRa Config . On Settings → LoRa. | Setting | Cur síos | Default | . | Réigiún | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Presets | Speed/range tradeoff | LongFast | . | Number of Hops | Maximum retransmit hops | 3 | . | Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) | . | Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Frequency Slot | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Transmit Enabled | Turning this off makes the node receive-only | On | . | Override Duty Cycle | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | . | Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | . | RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | . | PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Speed | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Cur síos | . | Screen on for | How long the display stays lit before sleeping | . | Carousel interval | How often the node cycles between screens on its own | . | Display mode | Screen layout/density used by the firmware | . | Display units | Metric or Imperial on the node’s screen | . | Use 12h clock format | Show the node’s clock as 12-hour rather than 24-hour | . | Bold Heading | Draw the screen’s heading text in bold | . | Flip screen | Rotate the display 180° for an inverted mounting | . | OLED type | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Wake on tap or motion | Light the screen when the node is tapped or moved | . | Compass orientation | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Always point north | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Position Config . On Settings → Device configuration → Position. | Setting | Cur síos | . | GPS Mode (Physical Hardware) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Polling Interval | How often the node asks its GPS for a fix | . | Broadcast Interval | How often the position is shared with the mesh | . | Smart Position | Broadcast based on movement rather than purely on the clock | . | Smart Interval | With Smart Position on, the shortest gap between broadcasts | . | Smart Distance | With Smart Position on, how far you must move before broadcasting | . | Fixed Position | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Position Flags | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Power Config . On Settings → Device configuration → Power. | Setting | Cur síos | . | Enable power saving mode | Let the node sleep aggressively between activity | . | Shutdown on power loss | Power the device down after external power disappears | . | Super deep sleep duration | How long the deepest sleep state lasts | . | Minimum wake time | The shortest time the node stays awake once woken | . | Wait for Bluetooth duration | How long to wait for a phone to connect before sleeping | . | ADC multiplier override | Turn on a manual correction for battery-voltage readings | . | ADC multiplier override ratio | The correction factor itself, used only when the override is on | . | Battery INA_2XX I2C address | Address of an external INA-series power sensor, if fitted | . Network Config . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Cur síos | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Password | Network password | . | Ethernet enabled | Use a wired connection on hardware that has one | . | IPv4 mode | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | NTP server | Time synchronization server | . | rsyslog server | Remote logging server | . Bluetooth Config . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Cur síos | . | Bluetooth enabled | Enable/disable BLE radio | . | Pairing mode | Fixed PIN, Random PIN, or No PIN | . | Fixed PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Security Config . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Cur síos | . | Public Key | Your node’s public key (read-only) | . | Admin Key | Keys permitted to administer this node remotely — up to three | . | Private Key | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Regenerate Private Key | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Serial console | Serial console over the Stream API | . | Debug log API enabled | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Managed Mode | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Backup Keys | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ", "url": "/Meshtastic-Android/main/ga-rIE/user/settings-radio-user.html#configuration", "relUrl": "/ga-rIE/user/settings-radio-user.html#configuration" @@ -31557,7 +31557,7 @@ },"4508": { "doc": "Settings — Radio & User", "title": "Configuration", - "content": "Configuration de l’appareil . On Settings → Device configuration → Device. | Setting | Description | Par défaut | . | Rôle de l’appareil | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Mode de réémission | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Intervalle de diffusion des infos nœud | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Double clic comme appui sur le bouton | Treat a double tap as a button press | Désactivé | . | Triple clic pour faire un ping Ad Hoc | Send an ad-hoc position ping on a triple click | Activé | . | LED de vérification de fonctionnement (heartbeat) | Blink the status LED periodically | Activé | . | Fuseau horaire | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . Configuration LoRa . On Settings → LoRa. | Setting | Description | Par défaut | . | Région | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Préréglages | Speed/range tradeoff | LongFast | . | Nombre de sauts | Maximum retransmit hops | 3 | . | Puissance d’émission | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Remplacer la fréquence | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Utiliser un préréglage | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Facteur de propagation | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Taux de codage | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Bande Passante | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Slot de fréquence | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Transmission activée | Turning this off makes the node receive-only | On | . | Autoriser le dépassement du temps d’émission autorisé par heure | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Éteint | . | Ignorer MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Transmission des paquets vers MQTT | Allow your packets to be forwarded to MQTT by gateways | Éteint | . | Gain RX Boosté | Extra receive gain on SX126x radios; costs a little current | Éteint | . | Ventilateur PA désactivé | Turn off the power-amplifier fan on hardware that has one | Éteint | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Vitesse | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Configuration de l’écran . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Description | . | Écran allumé pour | How long the display stays lit before sleeping | . | Intervalle du carrousel | How often the node cycles between screens on its own | . | Mode d’affichage | Screen layout/density used by the firmware | . | Unités d’affichage | Metric or Imperial on the node’s screen | . | Utiliser le format horaire 12h | Show the node’s clock as 12-hour rather than 24-hour | . | Titre en gras | Draw the screen’s heading text in bold | . | Inverser l’écran | Rotate the display 180° for an inverted mounting | . | Type d’OLED | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Réveil par appui ou mouvement | Light the screen when the node is tapped or moved | . | Orientation de la boussole | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Toujours pointer vers le nord | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Configuration de la position . On Settings → Device configuration → Position. | Setting | Description | . | Mode GPS (matériel physique) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | Fréquence de récupération GPS | How often the node asks its GPS for a fix | . | Intervalle de diffusion | How often the position is shared with the mesh | . | Position Intelligente | Broadcast based on movement rather than purely on the clock | . | Intervalle intelligent | With Smart Position on, the shortest gap between broadcasts | . | Distance intelligente | With Smart Position on, how far you must move before broadcasting | . | Position fixe | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Champs de position | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Configuration de l’alimentation . On Settings → Device configuration → Power. | Setting | Description | . | Activer le mode économie d’énergie | Let the node sleep aggressively between activity | . | Arrêt en cas de perte d’alimentation | Power the device down after external power disappears | . | Durée du sommeil extra profond | How long the deepest sleep state lasts | . | Durée minimale de réveil | The shortest time the node stays awake once woken | . | Durée d’attente max du Bluetooth | How long to wait for a phone to connect before sleeping | . | Remplacer le multiplicateur ADC | Turn on a manual correction for battery-voltage readings | . | Facteur de remplacement du multiplicateur ADC | The correction factor itself, used only when the override is on | . | Adresse I2C de la batterie INA_2XX | Address of an external INA-series power sensor, if fitted | . Configuration du réseau . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Description | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Mot de passe | Mot de passe du réseau | . | Ethernet activé | Use a wired connection on hardware that has one | . | Mode IPv4 | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | Serveur NTP | Time synchronization server | . | Serveur Rsyslog | Remote logging server | . Configuration Bluetooth . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Description | . | Bluetooth activé | Enable/disable BLE radio | . | Mode d’appariement | Fixed PIN, Random PIN, or No PIN | . | Code PIN fixe | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Configuration de sécurité . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Description | . | Clé publique | Your node’s public key (read-only) | . | Clé Admin | Keys permitted to administer this node remotely — up to three | . | Clé privée | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Régénérer la clé privée | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Console série | Serial console over the Stream API | . | API de journalisation de débogage activée | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Mode géré | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Sauvegarder les clés | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Heures jusqu’à expiration | Wall-clock lifetime of the unlocked state | . | Limite de sessions (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ", + "content": "Configuration de l’appareil . On Settings → Device configuration → Device. | Setting | Description | Par défaut | . | Rôle de l’appareil | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Mode de réémission | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Intervalle de diffusion des infos nœud | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Double clic comme appui sur le bouton | Treat a double tap as a button press | Désactivé | . | Triple clic pour faire un ping Ad Hoc | Send an ad-hoc position ping on a triple click | Activé | . | LED de vérification de fonctionnement (heartbeat) | Blink the status LED periodically | Activé | . | Fuseau horaire | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . Configuration LoRa . On Settings → LoRa. | Setting | Description | Par défaut | . | Région | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Préréglages | Speed/range tradeoff | LongFast | . | Nombre de sauts | Maximum retransmit hops | 3 | . | Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) | . | Remplacer la fréquence | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Utiliser un préréglage | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Facteur de propagation | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Taux de codage | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Bande Passante | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Slot de fréquence | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Transmission activée | Turning this off makes the node receive-only | On | . | Autoriser le dépassement du temps d’émission autorisé par heure | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Éteint | . | Ignorer MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Transmission des paquets vers MQTT | Allow your packets to be forwarded to MQTT by gateways | Éteint | . | Gain RX Boosté | Extra receive gain on SX126x radios; costs a little current | Éteint | . | Ventilateur PA désactivé | Turn off the power-amplifier fan on hardware that has one | Éteint | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Vitesse | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Configuration de l’écran . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Description | . | Écran allumé pour | How long the display stays lit before sleeping | . | Intervalle du carrousel | How often the node cycles between screens on its own | . | Mode d’affichage | Screen layout/density used by the firmware | . | Unités d’affichage | Metric or Imperial on the node’s screen | . | Utiliser le format horaire 12h | Show the node’s clock as 12-hour rather than 24-hour | . | Titre en gras | Draw the screen’s heading text in bold | . | Inverser l’écran | Rotate the display 180° for an inverted mounting | . | Type d’OLED | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Réveil par appui ou mouvement | Light the screen when the node is tapped or moved | . | Orientation de la boussole | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Toujours pointer vers le nord | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Configuration de la position . On Settings → Device configuration → Position. | Setting | Description | . | Mode GPS (matériel physique) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | Fréquence de récupération GPS | How often the node asks its GPS for a fix | . | Intervalle de diffusion | How often the position is shared with the mesh | . | Position Intelligente | Broadcast based on movement rather than purely on the clock | . | Intervalle intelligent | With Smart Position on, the shortest gap between broadcasts | . | Distance intelligente | With Smart Position on, how far you must move before broadcasting | . | Position fixe | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Champs de position | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Configuration de l’alimentation . On Settings → Device configuration → Power. | Setting | Description | . | Activer le mode économie d’énergie | Let the node sleep aggressively between activity | . | Arrêt en cas de perte d’alimentation | Power the device down after external power disappears | . | Durée du sommeil extra profond | How long the deepest sleep state lasts | . | Durée minimale de réveil | The shortest time the node stays awake once woken | . | Durée d’attente max du Bluetooth | How long to wait for a phone to connect before sleeping | . | Remplacer le multiplicateur ADC | Turn on a manual correction for battery-voltage readings | . | Facteur de remplacement du multiplicateur ADC | The correction factor itself, used only when the override is on | . | Adresse I2C de la batterie INA_2XX | Address of an external INA-series power sensor, if fitted | . Configuration du réseau . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Description | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Mot de passe | Mot de passe du réseau | . | Ethernet activé | Use a wired connection on hardware that has one | . | Mode IPv4 | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | Serveur NTP | Time synchronization server | . | Serveur Rsyslog | Remote logging server | . Configuration Bluetooth . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Description | . | Bluetooth activé | Enable/disable BLE radio | . | Mode d’appariement | Fixed PIN, Random PIN, or No PIN | . | Code PIN fixe | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Configuration de sécurité . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Description | . | Clé publique | Your node’s public key (read-only) | . | Clé Admin | Keys permitted to administer this node remotely — up to three | . | Clé privée | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Régénérer la clé privée | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Console série | Serial console over the Stream API | . | API de journalisation de débogage activée | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Mode géré | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Sauvegarder les clés | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Heures jusqu’à expiration | Wall-clock lifetime of the unlocked state | . | Limite de sessions (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ", "url": "/Meshtastic-Android/main/fr-rCA/user/settings-radio-user.html#configuration", "relUrl": "/fr-rCA/user/settings-radio-user.html#configuration" @@ -31599,7 +31599,7 @@ },"4514": { "doc": "Settings — Radio & User", "title": "Configuration", - "content": "Подешавања уређаја . On Settings → Device configuration → Device. | Setting | Опис | Подразумевано | . | Улога уређаја | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Режим реемитовања | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Интервал емитовања информација о чвору | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Двоструки додир као дугме | Treat a double tap as a button press | Онемогућено | . | Троструки клик за Ad Hoc пинг | Send an ad-hoc position ping on a triple click | Омогућено | . | LED срчани откуцаји | Blink the status LED periodically | Омогућено | . | Временска зона | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRA подешавања . On Settings → LoRa. | Setting | Опис | Подразумевано | . | Регион | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Унапред подешено | Speed/range tradeoff | LongFast | . | Number of Hops | Maximum retransmit hops | 3 | . | Transmit Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Измена фреквенције | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Користи предефинисано подешавање | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Фактор ширења | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Стопа кодирања | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Проток | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Фреквенцијски слот | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Трансмитер укључен | Turning this off makes the node receive-only | On | . | Override Duty Cycle | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Искључен | . | Игнориши MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Позитиван за MQTT | Allow your packets to be forwarded to MQTT by gateways | Искључен | . | Појачање пријемника | Extra receive gain on SX126x radios; costs a little current | Искључен | . | PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Искључен | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Брзина | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Подешавања приказа . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Опис | . | Екран укључен за | How long the display stays lit before sleeping | . | Carousel interval | How often the node cycles between screens on its own | . | Display mode | Screen layout/density used by the firmware | . | Display units | Metric or Imperial on the node’s screen | . | Use 12h clock format | Show the node’s clock as 12-hour rather than 24-hour | . | Bold Heading | Draw the screen’s heading text in bold | . | Flip screen | Rotate the display 180° for an inverted mounting | . | OLED type | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Wake on tap or motion | Light the screen when the node is tapped or moved | . | Compass orientation | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Увек усмеравајте на север | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Подешавања позиције . On Settings → Device configuration → Position. | Setting | Опис | . | GPS Mode (Physical Hardware) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Polling Interval | How often the node asks its GPS for a fix | . | Интервал емитовања | How often the position is shared with the mesh | . | Паметно позиционирање | Broadcast based on movement rather than purely on the clock | . | Smart Interval | With Smart Position on, the shortest gap between broadcasts | . | Smart Distance | With Smart Position on, how far you must move before broadcasting | . | Фиксна локација | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Заставице позиције | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Подешавања напајња . On Settings → Device configuration → Power. | Setting | Опис | . | Enable power saving mode | Let the node sleep aggressively between activity | . | Shutdown on power loss | Power the device down after external power disappears | . | Super deep sleep duration | How long the deepest sleep state lasts | . | Minimum wake time | The shortest time the node stays awake once woken | . | Wait for Bluetooth duration | How long to wait for a phone to connect before sleeping | . | ADC multiplier override | Turn on a manual correction for battery-voltage readings | . | ADC multiplier override ratio | The correction factor itself, used only when the override is on | . | Battery INA_2XX I2C address | Address of an external INA-series power sensor, if fitted | . Конфигурација мреже . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Опис | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Лозинка | Network password | . | Ethernet enabled | Use a wired connection on hardware that has one | . | IPv4 mode | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | NTP server | Time synchronization server | . | rsyslog server | Remote logging server | . Блутут подешавања . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Опис | . | Bluetooth enabled | Enable/disable BLE radio | . | Pairing mode | Fixed PIN, Random PIN, or No PIN | . | Fixed PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Сигурносна подешавања . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Опис | . | Јавни кључ | Your node’s public key (read-only) | . | Admin Key | Keys permitted to administer this node remotely — up to three | . | Приватни кључ | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Regenerate Private Key | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Serial console | Serial console over the Stream API | . | Debug log API enabled | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Managed Mode | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Backup Keys | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ", + "content": "Подешавања уређаја . On Settings → Device configuration → Device. | Setting | Опис | Подразумевано | . | Улога уређаја | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Режим реемитовања | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Интервал емитовања информација о чвору | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Двоструки додир као дугме | Treat a double tap as a button press | Онемогућено | . | Троструки клик за Ad Hoc пинг | Send an ad-hoc position ping on a triple click | Омогућено | . | LED срчани откуцаји | Blink the status LED periodically | Омогућено | . | Временска зона | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRA подешавања . On Settings → LoRa. | Setting | Опис | Подразумевано | . | Регион | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Унапред подешено | Speed/range tradeoff | LongFast | . | Number of Hops | Maximum retransmit hops | 3 | . | Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) | . | Измена фреквенције | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Користи предефинисано подешавање | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Фактор ширења | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Стопа кодирања | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Проток | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Фреквенцијски слот | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Трансмитер укључен | Turning this off makes the node receive-only | On | . | Override Duty Cycle | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Искључен | . | Игнориши MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Позитиван за MQTT | Allow your packets to be forwarded to MQTT by gateways | Искључен | . | Појачање пријемника | Extra receive gain on SX126x radios; costs a little current | Искључен | . | PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Искључен | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Брзина | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Подешавања приказа . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Опис | . | Екран укључен за | How long the display stays lit before sleeping | . | Carousel interval | How often the node cycles between screens on its own | . | Display mode | Screen layout/density used by the firmware | . | Display units | Metric or Imperial on the node’s screen | . | Use 12h clock format | Show the node’s clock as 12-hour rather than 24-hour | . | Bold Heading | Draw the screen’s heading text in bold | . | Flip screen | Rotate the display 180° for an inverted mounting | . | OLED type | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Wake on tap or motion | Light the screen when the node is tapped or moved | . | Compass orientation | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Увек усмеравајте на север | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Подешавања позиције . On Settings → Device configuration → Position. | Setting | Опис | . | GPS Mode (Physical Hardware) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Polling Interval | How often the node asks its GPS for a fix | . | Интервал емитовања | How often the position is shared with the mesh | . | Паметно позиционирање | Broadcast based on movement rather than purely on the clock | . | Smart Interval | With Smart Position on, the shortest gap between broadcasts | . | Smart Distance | With Smart Position on, how far you must move before broadcasting | . | Фиксна локација | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Заставице позиције | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Подешавања напајња . On Settings → Device configuration → Power. | Setting | Опис | . | Enable power saving mode | Let the node sleep aggressively between activity | . | Shutdown on power loss | Power the device down after external power disappears | . | Super deep sleep duration | How long the deepest sleep state lasts | . | Minimum wake time | The shortest time the node stays awake once woken | . | Wait for Bluetooth duration | How long to wait for a phone to connect before sleeping | . | ADC multiplier override | Turn on a manual correction for battery-voltage readings | . | ADC multiplier override ratio | The correction factor itself, used only when the override is on | . | Battery INA_2XX I2C address | Address of an external INA-series power sensor, if fitted | . Конфигурација мреже . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Опис | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Лозинка | Network password | . | Ethernet enabled | Use a wired connection on hardware that has one | . | IPv4 mode | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | NTP server | Time synchronization server | . | rsyslog server | Remote logging server | . Блутут подешавања . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Опис | . | Bluetooth enabled | Enable/disable BLE radio | . | Pairing mode | Fixed PIN, Random PIN, or No PIN | . | Fixed PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Сигурносна подешавања . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Опис | . | Јавни кључ | Your node’s public key (read-only) | . | Admin Key | Keys permitted to administer this node remotely — up to three | . | Приватни кључ | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Regenerate Private Key | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Serial console | Serial console over the Stream API | . | Debug log API enabled | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Managed Mode | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Backup Keys | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ", "url": "/Meshtastic-Android/main/srp/user/settings-radio-user.html#configuration", "relUrl": "/srp/user/settings-radio-user.html#configuration" @@ -31641,7 +31641,7 @@ },"4520": { "doc": "Settings — Radio & User", "title": "Configuration", - "content": "Device Config . On Settings → Device configuration → Device. | Setting | Descripció | Default | . | Device Role | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Rebroadcast Mode | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Node Info Broadcast Interval | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Double Tap as Button | Treat a double tap as a button press | Disabled | . | Triple Click Ad Hoc Ping | Send an ad-hoc position ping on a triple click | Enabled | . | LED Heartbeat | Blink the status LED periodically | Enabled | . | Time Zone | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRa Config . On Settings → LoRa. | Setting | Descripció | Default | . | Regió | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Presets | Speed/range tradeoff | LongFast | . | Number of Hops | Maximum retransmit hops | 3 | . | Transmit Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Frequency Slot | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Transmit Enabled | Turning this off makes the node receive-only | On | . | Override Duty Cycle | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | . | Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | . | RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | . | PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Speed | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Descripció | . | Screen on for | How long the display stays lit before sleeping | . | Carousel interval | How often the node cycles between screens on its own | . | Display mode | Screen layout/density used by the firmware | . | Display units | Metric or Imperial on the node’s screen | . | Use 12h clock format | Show the node’s clock as 12-hour rather than 24-hour | . | Bold Heading | Draw the screen’s heading text in bold | . | Flip screen | Rotate the display 180° for an inverted mounting | . | OLED type | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Wake on tap or motion | Light the screen when the node is tapped or moved | . | Compass orientation | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Always point north | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Position Config . On Settings → Device configuration → Position. | Setting | Descripció | . | GPS Mode (Physical Hardware) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Polling Interval | How often the node asks its GPS for a fix | . | Broadcast Interval | How often the position is shared with the mesh | . | Smart Position | Broadcast based on movement rather than purely on the clock | . | Smart Interval | With Smart Position on, the shortest gap between broadcasts | . | Smart Distance | With Smart Position on, how far you must move before broadcasting | . | Fixed Position | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Position Flags | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Power Config . On Settings → Device configuration → Power. | Setting | Descripció | . | Enable power saving mode | Let the node sleep aggressively between activity | . | Shutdown on power loss | Power the device down after external power disappears | . | Super deep sleep duration | How long the deepest sleep state lasts | . | Minimum wake time | The shortest time the node stays awake once woken | . | Wait for Bluetooth duration | How long to wait for a phone to connect before sleeping | . | ADC multiplier override | Turn on a manual correction for battery-voltage readings | . | ADC multiplier override ratio | The correction factor itself, used only when the override is on | . | Battery INA_2XX I2C address | Address of an external INA-series power sensor, if fitted | . Network Config . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Descripció | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Password | Network password | . | Ethernet enabled | Use a wired connection on hardware that has one | . | IPv4 mode | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | NTP server | Time synchronization server | . | rsyslog server | Remote logging server | . Bluetooth Config . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Descripció | . | Bluetooth enabled | Enable/disable BLE radio | . | Pairing mode | Fixed PIN, Random PIN, or No PIN | . | Fixed PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Security Config . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Descripció | . | Public Key | Your node’s public key (read-only) | . | Admin Key | Keys permitted to administer this node remotely — up to three | . | Private Key | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Regenerate Private Key | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Serial console | Serial console over the Stream API | . | Debug log API enabled | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Managed Mode | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Backup Keys | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ", + "content": "Device Config . On Settings → Device configuration → Device. | Setting | Descripció | Default | . | Device Role | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Rebroadcast Mode | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Node Info Broadcast Interval | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Double Tap as Button | Treat a double tap as a button press | Disabled | . | Triple Click Ad Hoc Ping | Send an ad-hoc position ping on a triple click | Enabled | . | LED Heartbeat | Blink the status LED periodically | Enabled | . | Time Zone | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRa Config . On Settings → LoRa. | Setting | Descripció | Default | . | Regió | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Presets | Speed/range tradeoff | LongFast | . | Number of Hops | Maximum retransmit hops | 3 | . | Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) | . | Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Frequency Slot | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Transmit Enabled | Turning this off makes the node receive-only | On | . | Override Duty Cycle | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | . | Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | . | RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | . | PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Speed | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Descripció | . | Screen on for | How long the display stays lit before sleeping | . | Carousel interval | How often the node cycles between screens on its own | . | Display mode | Screen layout/density used by the firmware | . | Display units | Metric or Imperial on the node’s screen | . | Use 12h clock format | Show the node’s clock as 12-hour rather than 24-hour | . | Bold Heading | Draw the screen’s heading text in bold | . | Flip screen | Rotate the display 180° for an inverted mounting | . | OLED type | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Wake on tap or motion | Light the screen when the node is tapped or moved | . | Compass orientation | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Always point north | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Position Config . On Settings → Device configuration → Position. | Setting | Descripció | . | GPS Mode (Physical Hardware) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Polling Interval | How often the node asks its GPS for a fix | . | Broadcast Interval | How often the position is shared with the mesh | . | Smart Position | Broadcast based on movement rather than purely on the clock | . | Smart Interval | With Smart Position on, the shortest gap between broadcasts | . | Smart Distance | With Smart Position on, how far you must move before broadcasting | . | Fixed Position | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Position Flags | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Power Config . On Settings → Device configuration → Power. | Setting | Descripció | . | Enable power saving mode | Let the node sleep aggressively between activity | . | Shutdown on power loss | Power the device down after external power disappears | . | Super deep sleep duration | How long the deepest sleep state lasts | . | Minimum wake time | The shortest time the node stays awake once woken | . | Wait for Bluetooth duration | How long to wait for a phone to connect before sleeping | . | ADC multiplier override | Turn on a manual correction for battery-voltage readings | . | ADC multiplier override ratio | The correction factor itself, used only when the override is on | . | Battery INA_2XX I2C address | Address of an external INA-series power sensor, if fitted | . Network Config . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Descripció | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Password | Network password | . | Ethernet enabled | Use a wired connection on hardware that has one | . | IPv4 mode | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | NTP server | Time synchronization server | . | rsyslog server | Remote logging server | . Bluetooth Config . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Descripció | . | Bluetooth enabled | Enable/disable BLE radio | . | Pairing mode | Fixed PIN, Random PIN, or No PIN | . | Fixed PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Security Config . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Descripció | . | Public Key | Your node’s public key (read-only) | . | Admin Key | Keys permitted to administer this node remotely — up to three | . | Private Key | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Regenerate Private Key | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Serial console | Serial console over the Stream API | . | Debug log API enabled | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Managed Mode | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Backup Keys | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ", "url": "/Meshtastic-Android/main/ca-rES/user/settings-radio-user.html#configuration", "relUrl": "/ca-rES/user/settings-radio-user.html#configuration" @@ -31683,7 +31683,7 @@ },"4526": { "doc": "Settings — Radio & User", "title": "설정", - "content": "장치 설정 . On Settings → Device configuration → Device. | Setting | 설명 | 기본값 | . | Device Role | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | 중계 모드 | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | 노드 정보 발송 주기 | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Double Tap as Button | Treat a double tap as a button press | Disabled | . | Triple Click Ad Hoc Ping | Send an ad-hoc position ping on a triple click | 활성화 | . | LED Heartbeat | Blink the status LED periodically | 활성화 | . | Time Zone | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRa 설정 . On Settings → LoRa. | Setting | 설명 | 기본값 | . | 지역 | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Presets | Speed/range tradeoff | LongFast | . | Number of Hops | Maximum retransmit hops | 3 | . | 전송 출력 | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | 프리셋 사용 | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Coding rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | 대역폭 | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | 주파수 슬롯 | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | 전송 활성화 | Turning this off makes the node receive-only | On | . | Duty Cycle 무시 | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | . | MQTT로 부터 수신 무시 | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | . | RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | . | PA fan 비활성화됨 | Turn off the power-amplifier fan on hardware that has one | Off | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Speed | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. 화면 설정 . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | 설명 | . | Screen on for | How long the display stays lit before sleeping | . | Carousel interval | How often the node cycles between screens on its own | . | 디스플레이 모드 | Screen layout/density used by the firmware | . | 단위 표시 | Metric or Imperial on the node’s screen | . | 12시간제 보기 | Show the node’s clock as 12-hour rather than 24-hour | . | 상태표시줄 볼드체 | Draw the screen’s heading text in bold | . | 화면 뒤집기 | Rotate the display 180° for an inverted mounting | . | OLED type | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Wake on tap or motion | Light the screen when the node is tapped or moved | . | 나침반 방향 | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Always point north | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . 위치 설정 . On Settings → Device configuration → Position. | Setting | 설명 | . | GPS Mode (Physical Hardware) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Polling Interval | How often the node asks its GPS for a fix | . | 전송 간격 | How often the position is shared with the mesh | . | Smart Position | Broadcast based on movement rather than purely on the clock | . | Smart Interval | With Smart Position on, the shortest gap between broadcasts | . | Smart Distance | With Smart Position on, how far you must move before broadcasting | . | Fixed Position | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Position Flags | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . 전원 설정 . On Settings → Device configuration → Power. | Setting | 설명 | . | 저전력 모드 설정 | Let the node sleep aggressively between activity | . | Shutdown on power loss | Power the device down after external power disappears | . | Super deep sleep duration | How long the deepest sleep state lasts | . | Minimum wake time | The shortest time the node stays awake once woken | . | Wait for Bluetooth duration | How long to wait for a phone to connect before sleeping | . | ADC multiplier override | Turn on a manual correction for battery-voltage readings | . | ADC multiplier override ratio | The correction factor itself, used only when the override is on | . | Battery INA_2XX I2C address | Address of an external INA-series power sensor, if fitted | . 네트워크 설정 . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | 설명 | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | 비밀번호 | 네트워크 암호 | . | 이더넷 활성화 | Use a wired connection on hardware that has one | . | IPv4 모드 | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | NTP 서버 | Time synchronization server | . | rsyslog 서버 | Remote logging server | . 블루투스 설정 . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | 설명 | . | 블루투스 활성화 | Enable/disable BLE radio | . | 페어링 모드 | Fixed PIN, Random PIN, or No PIN | . | 고정 PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . 보안 설정 . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | 설명 | . | 공개 키 | Your node’s public key (read-only) | . | Admin 키 | Keys permitted to administer this node remotely — up to three | . | 개인 키 | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | 개인 키 다시 생성하기 | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | 시리얼 콘솔 | Serial console over the Stream API | . | Debug log API enabled | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | 관리 모드 | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Backup Keys | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ", + "content": "장치 설정 . On Settings → Device configuration → Device. | Setting | 설명 | 기본값 | . | Device Role | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | 중계 모드 | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | 노드 정보 발송 주기 | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Double Tap as Button | Treat a double tap as a button press | Disabled | . | Triple Click Ad Hoc Ping | Send an ad-hoc position ping on a triple click | 활성화 | . | LED Heartbeat | Blink the status LED periodically | 활성화 | . | Time Zone | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRa 설정 . On Settings → LoRa. | Setting | 설명 | 기본값 | . | 지역 | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Presets | Speed/range tradeoff | LongFast | . | Number of Hops | Maximum retransmit hops | 3 | . | Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) | . | Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | 프리셋 사용 | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Coding rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | 대역폭 | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | 주파수 슬롯 | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | 전송 활성화 | Turning this off makes the node receive-only | On | . | Duty Cycle 무시 | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | . | MQTT로 부터 수신 무시 | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | . | RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | . | PA fan 비활성화됨 | Turn off the power-amplifier fan on hardware that has one | Off | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Speed | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. 화면 설정 . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | 설명 | . | Screen on for | How long the display stays lit before sleeping | . | Carousel interval | How often the node cycles between screens on its own | . | 디스플레이 모드 | Screen layout/density used by the firmware | . | 단위 표시 | Metric or Imperial on the node’s screen | . | 12시간제 보기 | Show the node’s clock as 12-hour rather than 24-hour | . | 상태표시줄 볼드체 | Draw the screen’s heading text in bold | . | 화면 뒤집기 | Rotate the display 180° for an inverted mounting | . | OLED type | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Wake on tap or motion | Light the screen when the node is tapped or moved | . | 나침반 방향 | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Always point north | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . 위치 설정 . On Settings → Device configuration → Position. | Setting | 설명 | . | GPS Mode (Physical Hardware) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Polling Interval | How often the node asks its GPS for a fix | . | 전송 간격 | How often the position is shared with the mesh | . | Smart Position | Broadcast based on movement rather than purely on the clock | . | Smart Interval | With Smart Position on, the shortest gap between broadcasts | . | Smart Distance | With Smart Position on, how far you must move before broadcasting | . | Fixed Position | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Position Flags | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . 전원 설정 . On Settings → Device configuration → Power. | Setting | 설명 | . | 저전력 모드 설정 | Let the node sleep aggressively between activity | . | Shutdown on power loss | Power the device down after external power disappears | . | Super deep sleep duration | How long the deepest sleep state lasts | . | Minimum wake time | The shortest time the node stays awake once woken | . | Wait for Bluetooth duration | How long to wait for a phone to connect before sleeping | . | ADC multiplier override | Turn on a manual correction for battery-voltage readings | . | ADC multiplier override ratio | The correction factor itself, used only when the override is on | . | Battery INA_2XX I2C address | Address of an external INA-series power sensor, if fitted | . 네트워크 설정 . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | 설명 | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | 비밀번호 | 네트워크 암호 | . | 이더넷 활성화 | Use a wired connection on hardware that has one | . | IPv4 모드 | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | NTP 서버 | Time synchronization server | . | rsyslog 서버 | Remote logging server | . 블루투스 설정 . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | 설명 | . | 블루투스 활성화 | Enable/disable BLE radio | . | 페어링 모드 | Fixed PIN, Random PIN, or No PIN | . | 고정 PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . 보안 설정 . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | 설명 | . | 공개 키 | Your node’s public key (read-only) | . | Admin 키 | Keys permitted to administer this node remotely — up to three | . | 개인 키 | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | 개인 키 다시 생성하기 | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | 시리얼 콘솔 | Serial console over the Stream API | . | Debug log API enabled | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | 관리 모드 | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Backup Keys | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ", "url": "/Meshtastic-Android/main/ko-rKR/user/settings-radio-user.html#%EC%84%A4%EC%A0%95", "relUrl": "/ko-rKR/user/settings-radio-user.html#설정" @@ -31725,7 +31725,7 @@ },"4532": { "doc": "Settings — Radio & User", "title": "Konfiguration", - "content": "Enhetskonfiguration . On Settings → Device configuration → Device. | Setting | Beskrivning | Förvald | . | Enhetens roll | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Återutsändningsläge | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Sändningsintervall för nod-info | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Dubbeltryck som knapptryck | Treat a double tap as a button press | Disabled | . | Triple Click Ad Hoc Ping | Send an ad-hoc position ping on a triple click | Aktiverad | . | LED pulsering | Blink the status LED periodically | Aktiverad | . | Tidszon | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRa Config . On Settings → LoRa. | Setting | Beskrivning | Förvald | . | Region | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Förval | Speed/range tradeoff | LongFast | . | Antal hopp | Maximum retransmit hops | 3 | . | Sändningseffekt | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Åsidosätt | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Använd förinställning | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Spridningsfaktor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Kodningshastighet | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Bandbredd | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Frekvens-slot | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Sändning aktiverad | Turning this off makes the node receive-only | On | . | Ersätt gräns för driftsperiod | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Av | . | Ignorera MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Ok till MQTT | Allow your packets to be forwarded to MQTT by gateways | Av | . | RX förstärkt gain | Extra receive gain on SX126x radios; costs a little current | Av | . | PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Av | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Hastighet | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Beskrivning | . | Håll skärmen tänd | How long the display stays lit before sleeping | . | Carousel interval | How often the node cycles between screens on its own | . | Visningsläge | Screen layout/density used by the firmware | . | Visa enheter | Metric or Imperial on the node’s screen | . | Använd 12-timmarsformat | Show the node’s clock as 12-hour rather than 24-hour | . | Fetstil för rubriktext | Draw the screen’s heading text in bold | . | Vänd skärmen | Rotate the display 180° for an inverted mounting | . | OLED-typ | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Vakna vid tryck eller rörelse | Light the screen when the node is tapped or moved | . | Kompassriktning | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Peka alltid mot norr | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Position Config . On Settings → Device configuration → Position. | Setting | Beskrivning | . | GPS-läge (fysisk maskinvara) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | Intervall för hämtning av GPS-position | How often the node asks its GPS for a fix | . | Sändningsintervall | How often the position is shared with the mesh | . | Smart position | Broadcast based on movement rather than purely on the clock | . | Smart intervall | With Smart Position on, the shortest gap between broadcasts | . | Smart distans | With Smart Position on, how far you must move before broadcasting | . | Fast plats | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Positionsflaggor | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Ströminställningar . On Settings → Device configuration → Power. | Setting | Beskrivning | . | Aktivera strömsparläge | Let the node sleep aggressively between activity | . | Stäng av vid strömförlust | Power the device down after external power disappears | . | Tid för djup strömsparläge | How long the deepest sleep state lasts | . | Minimum wake time | The shortest time the node stays awake once woken | . | Vänta in Bluetooth (sekunder) | How long to wait for a phone to connect before sleeping | . | ADC multiplier override | Turn on a manual correction for battery-voltage readings | . | ADC multiplier override ratio | The correction factor itself, used only when the override is on | . | Batteriets INA_2XX I2C-adress | Address of an external INA-series power sensor, if fitted | . Network Config . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Beskrivning | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Lösenord | Nätverkslösenord | . | Ethernet är aktiverat | Use a wired connection on hardware that has one | . | IPv4-läge | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | NTP-server | Time synchronization server | . | rsyslog-server | Remote logging server | . Bluetooth-inställningar . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Beskrivning | . | Bluetooth är aktiverad | Enable/disable BLE radio | . | Parkopplingsläge | Fixed PIN, Random PIN, or No PIN | . | Fast PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Security Config . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Beskrivning | . | Publik nyckel | Your node’s public key (read-only) | . | Admin-nyckel | Keys permitted to administer this node remotely — up to three | . | Privat nyckel | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Förnya nyckel | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Seriell konsol | Serial console over the Stream API | . | API för debugloggen igång | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Hanterat läge | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Säkerhetskopiera nycklar | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Skyddsnivå | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ", + "content": "Enhetskonfiguration . On Settings → Device configuration → Device. | Setting | Beskrivning | Förvald | . | Enhetens roll | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Återutsändningsläge | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Sändningsintervall för nod-info | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Dubbeltryck som knapptryck | Treat a double tap as a button press | Disabled | . | Triple Click Ad Hoc Ping | Send an ad-hoc position ping on a triple click | Aktiverad | . | LED pulsering | Blink the status LED periodically | Aktiverad | . | Tidszon | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRa Config . On Settings → LoRa. | Setting | Beskrivning | Förvald | . | Region | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Förval | Speed/range tradeoff | LongFast | . | Antal hopp | Maximum retransmit hops | 3 | . | Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) | . | Åsidosätt | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Använd förinställning | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Spridningsfaktor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Kodningshastighet | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Bandbredd | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Frekvens-slot | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Sändning aktiverad | Turning this off makes the node receive-only | On | . | Ersätt gräns för driftsperiod | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Av | . | Ignorera MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Ok till MQTT | Allow your packets to be forwarded to MQTT by gateways | Av | . | RX förstärkt gain | Extra receive gain on SX126x radios; costs a little current | Av | . | PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Av | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Hastighet | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Beskrivning | . | Håll skärmen tänd | How long the display stays lit before sleeping | . | Carousel interval | How often the node cycles between screens on its own | . | Visningsläge | Screen layout/density used by the firmware | . | Visa enheter | Metric or Imperial on the node’s screen | . | Använd 12-timmarsformat | Show the node’s clock as 12-hour rather than 24-hour | . | Fetstil för rubriktext | Draw the screen’s heading text in bold | . | Vänd skärmen | Rotate the display 180° for an inverted mounting | . | OLED-typ | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Vakna vid tryck eller rörelse | Light the screen when the node is tapped or moved | . | Kompassriktning | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Peka alltid mot norr | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Position Config . On Settings → Device configuration → Position. | Setting | Beskrivning | . | GPS-läge (fysisk maskinvara) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | Intervall för hämtning av GPS-position | How often the node asks its GPS for a fix | . | Sändningsintervall | How often the position is shared with the mesh | . | Smart position | Broadcast based on movement rather than purely on the clock | . | Smart intervall | With Smart Position on, the shortest gap between broadcasts | . | Smart distans | With Smart Position on, how far you must move before broadcasting | . | Fast plats | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Positionsflaggor | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Ströminställningar . On Settings → Device configuration → Power. | Setting | Beskrivning | . | Aktivera strömsparläge | Let the node sleep aggressively between activity | . | Stäng av vid strömförlust | Power the device down after external power disappears | . | Tid för djup strömsparläge | How long the deepest sleep state lasts | . | Minimum wake time | The shortest time the node stays awake once woken | . | Vänta in Bluetooth (sekunder) | How long to wait for a phone to connect before sleeping | . | ADC multiplier override | Turn on a manual correction for battery-voltage readings | . | ADC multiplier override ratio | The correction factor itself, used only when the override is on | . | Batteriets INA_2XX I2C-adress | Address of an external INA-series power sensor, if fitted | . Network Config . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Beskrivning | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Lösenord | Nätverkslösenord | . | Ethernet är aktiverat | Use a wired connection on hardware that has one | . | IPv4-läge | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | NTP-server | Time synchronization server | . | rsyslog-server | Remote logging server | . Bluetooth-inställningar . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Beskrivning | . | Bluetooth är aktiverad | Enable/disable BLE radio | . | Parkopplingsläge | Fixed PIN, Random PIN, or No PIN | . | Fast PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Security Config . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Beskrivning | . | Publik nyckel | Your node’s public key (read-only) | . | Admin-nyckel | Keys permitted to administer this node remotely — up to three | . | Privat nyckel | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Förnya nyckel | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Seriell konsol | Serial console over the Stream API | . | API för debugloggen igång | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Hanterat läge | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Säkerhetskopiera nycklar | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Skyddsnivå | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ", "url": "/Meshtastic-Android/main/sv-rSE/user/settings-radio-user.html#konfiguration", "relUrl": "/sv-rSE/user/settings-radio-user.html#konfiguration" @@ -31767,7 +31767,7 @@ },"4538": { "doc": "Settings — Radio & User", "title": "Configuration", - "content": "Device Config . On Settings → Device configuration → Device. | Setting | Deskripsyon | Default | . | Device Role | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Rebroadcast Mode | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Node Info Broadcast Interval | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Double Tap as Button | Treat a double tap as a button press | Disabled | . | Triple Click Ad Hoc Ping | Send an ad-hoc position ping on a triple click | Enabled | . | LED Heartbeat | Blink the status LED periodically | Enabled | . | Time Zone | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRa Config . On Settings → LoRa. | Setting | Deskripsyon | Default | . | Rejyon | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Presets | Speed/range tradeoff | LongFast | . | Number of Hops | Maximum retransmit hops | 3 | . | Transmit Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Frequency Slot | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Transmit Enabled | Turning this off makes the node receive-only | On | . | Override Duty Cycle | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | . | Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | . | RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | . | PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Speed | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Deskripsyon | . | Screen on for | How long the display stays lit before sleeping | . | Carousel interval | How often the node cycles between screens on its own | . | Display mode | Screen layout/density used by the firmware | . | Display units | Metric or Imperial on the node’s screen | . | Use 12h clock format | Show the node’s clock as 12-hour rather than 24-hour | . | Bold Heading | Draw the screen’s heading text in bold | . | Flip screen | Rotate the display 180° for an inverted mounting | . | OLED type | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Wake on tap or motion | Light the screen when the node is tapped or moved | . | Compass orientation | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Always point north | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Position Config . On Settings → Device configuration → Position. | Setting | Deskripsyon | . | GPS Mode (Physical Hardware) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Polling Interval | How often the node asks its GPS for a fix | . | Broadcast Interval | How often the position is shared with the mesh | . | Smart Position | Broadcast based on movement rather than purely on the clock | . | Smart Interval | With Smart Position on, the shortest gap between broadcasts | . | Smart Distance | With Smart Position on, how far you must move before broadcasting | . | Fixed Position | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Position Flags | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Power Config . On Settings → Device configuration → Power. | Setting | Deskripsyon | . | Enable power saving mode | Let the node sleep aggressively between activity | . | Shutdown on power loss | Power the device down after external power disappears | . | Super deep sleep duration | How long the deepest sleep state lasts | . | Minimum wake time | The shortest time the node stays awake once woken | . | Wait for Bluetooth duration | How long to wait for a phone to connect before sleeping | . | ADC multiplier override | Turn on a manual correction for battery-voltage readings | . | ADC multiplier override ratio | The correction factor itself, used only when the override is on | . | Battery INA_2XX I2C address | Address of an external INA-series power sensor, if fitted | . Network Config . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Deskripsyon | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Password | Network password | . | Ethernet enabled | Use a wired connection on hardware that has one | . | IPv4 mode | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | NTP server | Time synchronization server | . | rsyslog server | Remote logging server | . Bluetooth Config . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Deskripsyon | . | Bluetooth enabled | Enable/disable BLE radio | . | Pairing mode | Fixed PIN, Random PIN, or No PIN | . | Fixed PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Security Config . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Deskripsyon | . | Public Key | Your node’s public key (read-only) | . | Admin Key | Keys permitted to administer this node remotely — up to three | . | Private Key | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Regenerate Private Key | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Serial console | Serial console over the Stream API | . | Debug log API enabled | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Managed Mode | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Backup Keys | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ", + "content": "Device Config . On Settings → Device configuration → Device. | Setting | Deskripsyon | Default | . | Device Role | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Rebroadcast Mode | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Node Info Broadcast Interval | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Double Tap as Button | Treat a double tap as a button press | Disabled | . | Triple Click Ad Hoc Ping | Send an ad-hoc position ping on a triple click | Enabled | . | LED Heartbeat | Blink the status LED periodically | Enabled | . | Time Zone | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRa Config . On Settings → LoRa. | Setting | Deskripsyon | Default | . | Rejyon | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Presets | Speed/range tradeoff | LongFast | . | Number of Hops | Maximum retransmit hops | 3 | . | Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) | . | Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Frequency Slot | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Transmit Enabled | Turning this off makes the node receive-only | On | . | Override Duty Cycle | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | . | Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | . | RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | . | PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Speed | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Deskripsyon | . | Screen on for | How long the display stays lit before sleeping | . | Carousel interval | How often the node cycles between screens on its own | . | Display mode | Screen layout/density used by the firmware | . | Display units | Metric or Imperial on the node’s screen | . | Use 12h clock format | Show the node’s clock as 12-hour rather than 24-hour | . | Bold Heading | Draw the screen’s heading text in bold | . | Flip screen | Rotate the display 180° for an inverted mounting | . | OLED type | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Wake on tap or motion | Light the screen when the node is tapped or moved | . | Compass orientation | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Always point north | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Position Config . On Settings → Device configuration → Position. | Setting | Deskripsyon | . | GPS Mode (Physical Hardware) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Polling Interval | How often the node asks its GPS for a fix | . | Broadcast Interval | How often the position is shared with the mesh | . | Smart Position | Broadcast based on movement rather than purely on the clock | . | Smart Interval | With Smart Position on, the shortest gap between broadcasts | . | Smart Distance | With Smart Position on, how far you must move before broadcasting | . | Fixed Position | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Position Flags | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Power Config . On Settings → Device configuration → Power. | Setting | Deskripsyon | . | Enable power saving mode | Let the node sleep aggressively between activity | . | Shutdown on power loss | Power the device down after external power disappears | . | Super deep sleep duration | How long the deepest sleep state lasts | . | Minimum wake time | The shortest time the node stays awake once woken | . | Wait for Bluetooth duration | How long to wait for a phone to connect before sleeping | . | ADC multiplier override | Turn on a manual correction for battery-voltage readings | . | ADC multiplier override ratio | The correction factor itself, used only when the override is on | . | Battery INA_2XX I2C address | Address of an external INA-series power sensor, if fitted | . Network Config . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Deskripsyon | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Password | Network password | . | Ethernet enabled | Use a wired connection on hardware that has one | . | IPv4 mode | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | NTP server | Time synchronization server | . | rsyslog server | Remote logging server | . Bluetooth Config . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Deskripsyon | . | Bluetooth enabled | Enable/disable BLE radio | . | Pairing mode | Fixed PIN, Random PIN, or No PIN | . | Fixed PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Security Config . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Deskripsyon | . | Public Key | Your node’s public key (read-only) | . | Admin Key | Keys permitted to administer this node remotely — up to three | . | Private Key | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Regenerate Private Key | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Serial console | Serial console over the Stream API | . | Debug log API enabled | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Managed Mode | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Backup Keys | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ", "url": "/Meshtastic-Android/main/ht-rHT/user/settings-radio-user.html#configuration", "relUrl": "/ht-rHT/user/settings-radio-user.html#configuration" @@ -31809,7 +31809,7 @@ },"4544": { "doc": "Settings — Radio & User", "title": "Configuration", - "content": "Подешавања уређаја . On Settings → Device configuration → Device. | Setting | Опис | Подразумевано | . | Улога уређаја | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Режим реемитовања | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Интервал емитовања информација о чвору | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Двоструки додир као дугме | Treat a double tap as a button press | Онемогућено | . | Троструки клик за Ad Hoc пинг | Send an ad-hoc position ping on a triple click | Омогућено | . | LED срчани откуцаји | Blink the status LED periodically | Омогућено | . | Временска зона | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRA подешавања . On Settings → LoRa. | Setting | Опис | Подразумевано | . | Регион | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Унапред подешено | Speed/range tradeoff | LongFast | . | Number of Hops | Maximum retransmit hops | 3 | . | Transmit Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Измена фреквенције | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Користи предефинисано подешавање | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Фактор ширења | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Стопа кодирања | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Проток | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Фреквенцијски слот | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Трансмитер укључен | Turning this off makes the node receive-only | On | . | Override Duty Cycle | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Искључен | . | Игнориши MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Позитиван за MQTT | Allow your packets to be forwarded to MQTT by gateways | Искључен | . | Појачање пријемника | Extra receive gain on SX126x radios; costs a little current | Искључен | . | PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Искључен | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Брзина | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Подешавања приказа . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Опис | . | Екран укључен за | How long the display stays lit before sleeping | . | Carousel interval | How often the node cycles between screens on its own | . | Display mode | Screen layout/density used by the firmware | . | Display units | Metric or Imperial on the node’s screen | . | Use 12h clock format | Show the node’s clock as 12-hour rather than 24-hour | . | Bold Heading | Draw the screen’s heading text in bold | . | Flip screen | Rotate the display 180° for an inverted mounting | . | OLED type | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Wake on tap or motion | Light the screen when the node is tapped or moved | . | Compass orientation | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Увек усмеравајте на север | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Подешавања позиције . On Settings → Device configuration → Position. | Setting | Опис | . | GPS Mode (Physical Hardware) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Polling Interval | How often the node asks its GPS for a fix | . | Интервал емитовања | How often the position is shared with the mesh | . | Паметно позиционирање | Broadcast based on movement rather than purely on the clock | . | Smart Interval | With Smart Position on, the shortest gap between broadcasts | . | Smart Distance | With Smart Position on, how far you must move before broadcasting | . | Фиксна локација | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Заставице позиције | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Подешавања напајња . On Settings → Device configuration → Power. | Setting | Опис | . | Enable power saving mode | Let the node sleep aggressively between activity | . | Shutdown on power loss | Power the device down after external power disappears | . | Super deep sleep duration | How long the deepest sleep state lasts | . | Minimum wake time | The shortest time the node stays awake once woken | . | Wait for Bluetooth duration | How long to wait for a phone to connect before sleeping | . | ADC multiplier override | Turn on a manual correction for battery-voltage readings | . | ADC multiplier override ratio | The correction factor itself, used only when the override is on | . | Battery INA_2XX I2C address | Address of an external INA-series power sensor, if fitted | . Конфигурација мреже . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Опис | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Лозинка | Network password | . | Ethernet enabled | Use a wired connection on hardware that has one | . | IPv4 mode | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | NTP server | Time synchronization server | . | rsyslog server | Remote logging server | . Блутут подешавања . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Опис | . | Bluetooth enabled | Enable/disable BLE radio | . | Pairing mode | Fixed PIN, Random PIN, or No PIN | . | Fixed PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Сигурносна подешавања . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Опис | . | Javni ključ | Your node’s public key (read-only) | . | Admin Key | Keys permitted to administer this node remotely — up to three | . | Privatni ključ | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Regenerate Private Key | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Serial console | Serial console over the Stream API | . | Debug log API enabled | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Managed Mode | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Backup Keys | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ", + "content": "Подешавања уређаја . On Settings → Device configuration → Device. | Setting | Опис | Подразумевано | . | Улога уређаја | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Режим реемитовања | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Интервал емитовања информација о чвору | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Двоструки додир као дугме | Treat a double tap as a button press | Онемогућено | . | Троструки клик за Ad Hoc пинг | Send an ad-hoc position ping on a triple click | Омогућено | . | LED срчани откуцаји | Blink the status LED periodically | Омогућено | . | Временска зона | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRA подешавања . On Settings → LoRa. | Setting | Опис | Подразумевано | . | Регион | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Унапред подешено | Speed/range tradeoff | LongFast | . | Number of Hops | Maximum retransmit hops | 3 | . | Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) | . | Измена фреквенције | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Користи предефинисано подешавање | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Фактор ширења | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Стопа кодирања | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Проток | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Фреквенцијски слот | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Трансмитер укључен | Turning this off makes the node receive-only | On | . | Override Duty Cycle | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Искључен | . | Игнориши MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Позитиван за MQTT | Allow your packets to be forwarded to MQTT by gateways | Искључен | . | Појачање пријемника | Extra receive gain on SX126x radios; costs a little current | Искључен | . | PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Искључен | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Брзина | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Подешавања приказа . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Опис | . | Екран укључен за | How long the display stays lit before sleeping | . | Carousel interval | How often the node cycles between screens on its own | . | Display mode | Screen layout/density used by the firmware | . | Display units | Metric or Imperial on the node’s screen | . | Use 12h clock format | Show the node’s clock as 12-hour rather than 24-hour | . | Bold Heading | Draw the screen’s heading text in bold | . | Flip screen | Rotate the display 180° for an inverted mounting | . | OLED type | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Wake on tap or motion | Light the screen when the node is tapped or moved | . | Compass orientation | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Увек усмеравајте на север | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Подешавања позиције . On Settings → Device configuration → Position. | Setting | Опис | . | GPS Mode (Physical Hardware) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Polling Interval | How often the node asks its GPS for a fix | . | Интервал емитовања | How often the position is shared with the mesh | . | Паметно позиционирање | Broadcast based on movement rather than purely on the clock | . | Smart Interval | With Smart Position on, the shortest gap between broadcasts | . | Smart Distance | With Smart Position on, how far you must move before broadcasting | . | Фиксна локација | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Заставице позиције | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Подешавања напајња . On Settings → Device configuration → Power. | Setting | Опис | . | Enable power saving mode | Let the node sleep aggressively between activity | . | Shutdown on power loss | Power the device down after external power disappears | . | Super deep sleep duration | How long the deepest sleep state lasts | . | Minimum wake time | The shortest time the node stays awake once woken | . | Wait for Bluetooth duration | How long to wait for a phone to connect before sleeping | . | ADC multiplier override | Turn on a manual correction for battery-voltage readings | . | ADC multiplier override ratio | The correction factor itself, used only when the override is on | . | Battery INA_2XX I2C address | Address of an external INA-series power sensor, if fitted | . Конфигурација мреже . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Опис | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Лозинка | Network password | . | Ethernet enabled | Use a wired connection on hardware that has one | . | IPv4 mode | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | NTP server | Time synchronization server | . | rsyslog server | Remote logging server | . Блутут подешавања . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Опис | . | Bluetooth enabled | Enable/disable BLE radio | . | Pairing mode | Fixed PIN, Random PIN, or No PIN | . | Fixed PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Сигурносна подешавања . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Опис | . | Javni ključ | Your node’s public key (read-only) | . | Admin Key | Keys permitted to administer this node remotely — up to three | . | Privatni ključ | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Regenerate Private Key | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Serial console | Serial console over the Stream API | . | Debug log API enabled | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Managed Mode | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Backup Keys | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ", "url": "/Meshtastic-Android/main/sr-rLatn/user/settings-radio-user.html#configuration", "relUrl": "/sr-rLatn/user/settings-radio-user.html#configuration" @@ -31851,7 +31851,7 @@ },"4550": { "doc": "Settings — Radio & User", "title": "Configuration", - "content": "Apparaat Configuratie . On Settings → Device configuration → Device. | Setting | Beschrijving | Standaard | . | Device Role | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Rebroadcast Mode | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Node Info Broadcast Interval | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Double Tap as Button | Treat a double tap as a button press | Disabled | . | Triple Click Ad Hoc Ping | Send an ad-hoc position ping on a triple click | Enabled | . | LED Heartbeat | Blink the status LED periodically | Enabled | . | Time Zone | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRa Configuratie . On Settings → LoRa. | Setting | Beschrijving | Standaard | . | Regio | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Presets | Speed/range tradeoff | LongFast | . | Number of Hops | Maximum retransmit hops | 3 | . | Transmit Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Bandbreedte | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Frequency Slot | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Transmit Enabled | Turning this off makes the node receive-only | On | . | Overschrijf Duty Cycle | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | . | Negeer MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | . | RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | . | PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Speed | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Weergave Configuratie . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Beschrijving | . | Screen on for | How long the display stays lit before sleeping | . | Carousel interval | How often the node cycles between screens on its own | . | Weergavemodus | Screen layout/density used by the firmware | . | Geef eenheden weer | Metric or Imperial on the node’s screen | . | Use 12h clock format | Show the node’s clock as 12-hour rather than 24-hour | . | Bold Heading | Draw the screen’s heading text in bold | . | Scherm omdraaien | Rotate the display 180° for an inverted mounting | . | OLED type | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Wake on tap or motion | Light the screen when the node is tapped or moved | . | Kompas oriëntatie | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Always point north | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Positie Configuratie . On Settings → Device configuration → Position. | Setting | Beschrijving | . | GPS Mode (Physical Hardware) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Polling Interval | How often the node asks its GPS for a fix | . | Broadcast Interval | How often the position is shared with the mesh | . | Smart Position | Broadcast based on movement rather than purely on the clock | . | Smart Interval | With Smart Position on, the shortest gap between broadcasts | . | Smart Distance | With Smart Position on, how far you must move before broadcasting | . | Fixed Position | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Position Flags | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Energie configuratie . On Settings → Device configuration → Power. | Setting | Beschrijving | . | Energiebesparingsmodus inschakelen | Let the node sleep aggressively between activity | . | Shutdown on power loss | Power the device down after external power disappears | . | Super deep sleep duration | How long the deepest sleep state lasts | . | Minimum wake time | The shortest time the node stays awake once woken | . | Wait for Bluetooth duration | How long to wait for a phone to connect before sleeping | . | ADC multiplier override | Turn on a manual correction for battery-voltage readings | . | ADC multiplier override ratio | The correction factor itself, used only when the override is on | . | Battery INA_2XX I2C address | Address of an external INA-series power sensor, if fitted | . Netwerkconfiguratie . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Beschrijving | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Wachtwoord | Network password | . | Ethernet ingeschakeld | Use a wired connection on hardware that has one | . | IPv4 modus | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | NTP server | Time synchronization server | . | rsyslog server | Remote logging server | . Bluetooth Configuratie . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Beschrijving | . | Bluetooth ingeschakeld | Enable/disable BLE radio | . | Koppelmodus | Fixed PIN, Random PIN, or No PIN | . | Vaste PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Beveiligings Configuratie . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Beschrijving | . | Publieke sleutel | Your node’s public key (read-only) | . | Admin Sleutel | Keys permitted to administer this node remotely — up to three | . | Privésleutel | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Regenerate Private Key | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Seriële console | Serial console over the Stream API | . | Debug log API enabled | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Beheerde modus | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Backup Keys | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ", + "content": "Apparaat Configuratie . On Settings → Device configuration → Device. | Setting | Beschrijving | Standaard | . | Device Role | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Rebroadcast Mode | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Node Info Broadcast Interval | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Double Tap as Button | Treat a double tap as a button press | Disabled | . | Triple Click Ad Hoc Ping | Send an ad-hoc position ping on a triple click | Enabled | . | LED Heartbeat | Blink the status LED periodically | Enabled | . | Time Zone | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRa Configuratie . On Settings → LoRa. | Setting | Beschrijving | Standaard | . | Regio | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Presets | Speed/range tradeoff | LongFast | . | Number of Hops | Maximum retransmit hops | 3 | . | Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) | . | Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Bandbreedte | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Frequency Slot | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Transmit Enabled | Turning this off makes the node receive-only | On | . | Overschrijf Duty Cycle | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | . | Negeer MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | . | RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | . | PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Speed | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Weergave Configuratie . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Beschrijving | . | Screen on for | How long the display stays lit before sleeping | . | Carousel interval | How often the node cycles between screens on its own | . | Weergavemodus | Screen layout/density used by the firmware | . | Geef eenheden weer | Metric or Imperial on the node’s screen | . | Use 12h clock format | Show the node’s clock as 12-hour rather than 24-hour | . | Bold Heading | Draw the screen’s heading text in bold | . | Scherm omdraaien | Rotate the display 180° for an inverted mounting | . | OLED type | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Wake on tap or motion | Light the screen when the node is tapped or moved | . | Kompas oriëntatie | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Always point north | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Positie Configuratie . On Settings → Device configuration → Position. | Setting | Beschrijving | . | GPS Mode (Physical Hardware) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Polling Interval | How often the node asks its GPS for a fix | . | Broadcast Interval | How often the position is shared with the mesh | . | Smart Position | Broadcast based on movement rather than purely on the clock | . | Smart Interval | With Smart Position on, the shortest gap between broadcasts | . | Smart Distance | With Smart Position on, how far you must move before broadcasting | . | Fixed Position | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Position Flags | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Energie configuratie . On Settings → Device configuration → Power. | Setting | Beschrijving | . | Energiebesparingsmodus inschakelen | Let the node sleep aggressively between activity | . | Shutdown on power loss | Power the device down after external power disappears | . | Super deep sleep duration | How long the deepest sleep state lasts | . | Minimum wake time | The shortest time the node stays awake once woken | . | Wait for Bluetooth duration | How long to wait for a phone to connect before sleeping | . | ADC multiplier override | Turn on a manual correction for battery-voltage readings | . | ADC multiplier override ratio | The correction factor itself, used only when the override is on | . | Battery INA_2XX I2C address | Address of an external INA-series power sensor, if fitted | . Netwerkconfiguratie . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Beschrijving | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Wachtwoord | Network password | . | Ethernet ingeschakeld | Use a wired connection on hardware that has one | . | IPv4 modus | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | NTP server | Time synchronization server | . | rsyslog server | Remote logging server | . Bluetooth Configuratie . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Beschrijving | . | Bluetooth ingeschakeld | Enable/disable BLE radio | . | Koppelmodus | Fixed PIN, Random PIN, or No PIN | . | Vaste PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Beveiligings Configuratie . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Beschrijving | . | Publieke sleutel | Your node’s public key (read-only) | . | Admin Sleutel | Keys permitted to administer this node remotely — up to three | . | Privésleutel | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Regenerate Private Key | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Seriële console | Serial console over the Stream API | . | Debug log API enabled | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Beheerde modus | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Backup Keys | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ", "url": "/Meshtastic-Android/main/nl-rNL/user/settings-radio-user.html#configuration", "relUrl": "/nl-rNL/user/settings-radio-user.html#configuration" @@ -31893,7 +31893,7 @@ },"4556": { "doc": "Settings — Radio & User", "title": "Налаштування", - "content": "Налаштування пристрою . On Settings → Device configuration → Device. | Setting | Опис | За замовчуванням | . | Роль пристрою | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Режим ретрансляції | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Інтервал розсилки даних про вузол | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Подвійний дотик як натискання кнопки | Treat a double tap as a button press | Disabled | . | Швидка перевірка зв’язку потрійним натисканням | Send an ad-hoc position ping on a triple click | Увімкнено | . | Частота мигання світлодіоду | Blink the status LED periodically | Увімкнено | . | Часовий пояс | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . Налаштування LoRa . On Settings → LoRa. | Setting | Опис | За замовчуванням | . | Регіон | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Пресети | Speed/range tradeoff | LongFast | . | К-ть стрибків | Maximum retransmit hops | 3 | . | Потужність передачі | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Перевизначити частоту | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Використовувати пресет | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Показник розширення сигналу | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Швидкість кодування | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Ширина смуги пропускання | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Слот частоти | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Передача активована | Turning this off makes the node receive-only | On | . | Ігнорувати обмеження завантаженості каналу | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | . | Ігнорувати MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | MQTT: Готово | Allow your packets to be forwarded to MQTT by gateways | Off | . | Підсилення передачі | Extra receive gain on SX126x radios; costs a little current | Off | . | Вентилятор вимкнений | Turn off the power-amplifier fan on hardware that has one | Off | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Швидкість | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Налаштування дисплею . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Опис | . | Екран включено для | How long the display stays lit before sleeping | . | Інтервал гортання каруселі | How often the node cycles between screens on its own | . | Режим екрану | Screen layout/density used by the firmware | . | Одиниці виміру | Metric or Imperial on the node’s screen | . | Використовувати 12-г формат часу | Show the node’s clock as 12-hour rather than 24-hour | . | Жирні заголовки | Draw the screen’s heading text in bold | . | Перевернути екран | Rotate the display 180° for an inverted mounting | . | Тип OLED | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Прокидання дотиком або рухом | Light the screen when the node is tapped or moved | . | Орієнтація компаса | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Завжди вказувати на північ | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Position Config . On Settings → Device configuration → Position. | Setting | Опис | . | Режим GPS (Фізичний пристрій) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | Інтервал опитування GPS | How often the node asks its GPS for a fix | . | Інтервал трансляції | How often the position is shared with the mesh | . | Інтелектуальне передавання позиції | Broadcast based on movement rather than purely on the clock | . | Інтелектуальний інтервал | With Smart Position on, the shortest gap between broadcasts | . | Інтелектуальна дистанція | With Smart Position on, how far you must move before broadcasting | . | Фіксована позиція | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Прапорці місцеположення | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Налаштування живлення . On Settings → Device configuration → Power. | Setting | Опис | . | Увімкнути енергоощадний режим | Let the node sleep aggressively between activity | . | Вимкнути при втраті живлення | Power the device down after external power disappears | . | Тривалість глибокого сну | How long the deepest sleep state lasts | . | Мінімальний час в робочому режимі | The shortest time the node stays awake once woken | . | Тривалість очікування Bluetooth | How long to wait for a phone to connect before sleeping | . | Корекція множника напруги | Turn on a manual correction for battery-voltage readings | . | Множник корекції напруги | The correction factor itself, used only when the override is on | . | I2C адреса INA_2XX батареї | Address of an external INA-series power sensor, if fitted | . Налаштування мережі . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Опис | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Пароль | Network password | . | Ethernet увімкнено | Use a wired connection on hardware that has one | . | Режим IPv4 | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | NTP-сервер | Time synchronization server | . | rsyslog-сервер | Remote logging server | . Налаштування Bluetooth . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Опис | . | Bluetooth увімкнено | Enable/disable BLE radio | . | Режим створення пари | Fixed PIN, Random PIN, or No PIN | . | Фіксований PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Налаштування безпеки . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Опис | . | Відкритий ключ | Your node’s public key (read-only) | . | Ключ адміністратора | Keys permitted to administer this node remotely — up to three | . | Приватний ключ | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Згенерувати закритий ключ | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Серійна консоль | Serial console over the Stream API | . | API журналу відладки увімкнено | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Керований режим | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Резервні ключі | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ", + "content": "Налаштування пристрою . On Settings → Device configuration → Device. | Setting | Опис | За замовчуванням | . | Роль пристрою | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Режим ретрансляції | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Інтервал розсилки даних про вузол | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Подвійний дотик як натискання кнопки | Treat a double tap as a button press | Disabled | . | Швидка перевірка зв’язку потрійним натисканням | Send an ad-hoc position ping on a triple click | Увімкнено | . | Частота мигання світлодіоду | Blink the status LED periodically | Увімкнено | . | Часовий пояс | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . Налаштування LoRa . On Settings → LoRa. | Setting | Опис | За замовчуванням | . | Регіон | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Пресети | Speed/range tradeoff | LongFast | . | К-ть стрибків | Maximum retransmit hops | 3 | . | Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) | . | Перевизначити частоту | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Використовувати пресет | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Показник розширення сигналу | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Швидкість кодування | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Ширина смуги пропускання | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Слот частоти | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Передача активована | Turning this off makes the node receive-only | On | . | Ігнорувати обмеження завантаженості каналу | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | . | Ігнорувати MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | MQTT: Готово | Allow your packets to be forwarded to MQTT by gateways | Off | . | Підсилення передачі | Extra receive gain on SX126x radios; costs a little current | Off | . | Вентилятор вимкнений | Turn off the power-amplifier fan on hardware that has one | Off | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Швидкість | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Налаштування дисплею . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Опис | . | Екран включено для | How long the display stays lit before sleeping | . | Інтервал гортання каруселі | How often the node cycles between screens on its own | . | Режим екрану | Screen layout/density used by the firmware | . | Одиниці виміру | Metric or Imperial on the node’s screen | . | Використовувати 12-г формат часу | Show the node’s clock as 12-hour rather than 24-hour | . | Жирні заголовки | Draw the screen’s heading text in bold | . | Перевернути екран | Rotate the display 180° for an inverted mounting | . | Тип OLED | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Прокидання дотиком або рухом | Light the screen when the node is tapped or moved | . | Орієнтація компаса | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Завжди вказувати на північ | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Position Config . On Settings → Device configuration → Position. | Setting | Опис | . | Режим GPS (Фізичний пристрій) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | Інтервал опитування GPS | How often the node asks its GPS for a fix | . | Інтервал трансляції | How often the position is shared with the mesh | . | Інтелектуальне передавання позиції | Broadcast based on movement rather than purely on the clock | . | Інтелектуальний інтервал | With Smart Position on, the shortest gap between broadcasts | . | Інтелектуальна дистанція | With Smart Position on, how far you must move before broadcasting | . | Фіксована позиція | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Прапорці місцеположення | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Налаштування живлення . On Settings → Device configuration → Power. | Setting | Опис | . | Увімкнути енергоощадний режим | Let the node sleep aggressively between activity | . | Вимкнути при втраті живлення | Power the device down after external power disappears | . | Тривалість глибокого сну | How long the deepest sleep state lasts | . | Мінімальний час в робочому режимі | The shortest time the node stays awake once woken | . | Тривалість очікування Bluetooth | How long to wait for a phone to connect before sleeping | . | Корекція множника напруги | Turn on a manual correction for battery-voltage readings | . | Множник корекції напруги | The correction factor itself, used only when the override is on | . | I2C адреса INA_2XX батареї | Address of an external INA-series power sensor, if fitted | . Налаштування мережі . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Опис | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Пароль | Network password | . | Ethernet увімкнено | Use a wired connection on hardware that has one | . | Режим IPv4 | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | NTP-сервер | Time synchronization server | . | rsyslog-сервер | Remote logging server | . Налаштування Bluetooth . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Опис | . | Bluetooth увімкнено | Enable/disable BLE radio | . | Режим створення пари | Fixed PIN, Random PIN, or No PIN | . | Фіксований PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Налаштування безпеки . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Опис | . | Відкритий ключ | Your node’s public key (read-only) | . | Ключ адміністратора | Keys permitted to administer this node remotely — up to three | . | Приватний ключ | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Згенерувати закритий ключ | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Серійна консоль | Serial console over the Stream API | . | API журналу відладки увімкнено | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Керований режим | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Резервні ключі | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ", "url": "/Meshtastic-Android/main/uk-rUA/user/settings-radio-user.html#%D0%BD%D0%B0%D0%BB%D0%B0%D1%88%D1%82%D1%83%D0%B2%D0%B0%D0%BD%D0%BD%D1%8F", "relUrl": "/uk-rUA/user/settings-radio-user.html#налаштування" @@ -31935,7 +31935,7 @@ },"4562": { "doc": "Asetukset — Radio ja käyttäjä", "title": "Asetukset", - "content": "Laitteen asetukset . On Settings → Device configuration → Device. | Asetus | Kuvaus | Oletus | . | Laitteen rooli | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Uudelleenlähetyksen tila | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Laitteen tietojen lähetyksen aikaväli | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Kaksoisnapautus painikkeena | Käsittele kaksoisnapautus painikkeen painalluksena | Ei käytössä | . | Kolmoisklikkaus Ad Hoc -pingille | Lähetä kertaluonteinen sijaintipyyntö kolminkertaisella painalluksella | Käytössä | . | Ledin valvontasignaali | Vilkuta tilan merkkilediä säännöllisesti | Käytössä | . | Aikavyöhyke | Laitteen kellon POSIX-aikavyöhyke. Painikkeilla voit kopioida puhelimesi aikavyöhykkeen tai tyhjentää kentän | — | . | Painikkeen / summerin GPIO | Lisäasetukset: GPIO-nastat, joihin painike ja summeri on kytketty | — | . LoRa:n asetukset . On Settings → LoRa. | Asetus | Kuvaus | Oletus | . | Alue | Taajuusalueen sääntelyalue. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Ei asetettu (on määritettävä) | . | Esiasetukset | Nopeuden ja kantaman välinen kompromissi | LongFast | . | Hyppyjen määrä | Suurin hyppyjen määrä | 3 | . | Lähetysteho | Lähetysteho (dBm): 0 = alueen sallima enimmäisteho | 0 (alueen enimmäisteho) | . | Taajuuden ohitus | Ohittaa lasketun käyttötaajuuden (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (käytä laskettua arvoa) | . | Käytä esiasetusta | Oletusarvoisesti käytössä. Poista tämä käytöstä, jos haluat määrittää hajotuskerroin-, koodausnopeus- ja kaistanleveysasetukset käsin modeemiesiasetuksen sijaan | Käytössä | . | Levennyskerroin (Spread Factor) | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | Esiasetuksesta | . | Koodausnopeus | Vain manuaalitilassa: 5–8. Suurempi virheenkorjaus lisää lähetysaikaa | Esiasetuksesta | . | Kaistanleveys | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | Esiasetuksesta | . | Taajuuspaikka | Määrittää, mitä alueen taajuusväliä käytetään. 0 muodostetaan ensisijaisen kanavan nimestä | 0 (automaattinen) | . | Lähetys käytössä | Tämän poistaminen käytöstä tekee radiosta vain vastaanottavan | Käytössä | . | Ohita käyttöaste (Duty Cycle) | Ohittaa alueen lähetysajan käyttörajoituksen. Laitonta useimmilla alueilla. Ota käyttöön vain, jos radioamatöörilupasi sallii sen | Pois | . | Ohita MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | MQTT päällä | Salli yhdyskäytävien välittää pakettisi MQTT:hen | Pois | . | RX tehostettu vahvistus | Lisävastaanottovahvistus SX126x-radioille. Kuluttaa hieman enemmän virtaa | Pois | . | PA tuuletin pois käytöstä | Poista päätevahvistimen tuuletin käytöstä laitteissa, joissa sellainen on | Pois | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Tärkeää: Käyttö väärällä alueasetuksella voi rikkoa paikallisia radiomääräyksiä. Katso alueasetusten määritysopas meshtastic.org-sivustolta saadaksesi lisätietoja. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Vinkki: SNR-raja-arvot ovat tarkoituksella negatiivisia. LoRa pystyy purkamaan signaaleja kohinatason alapuolelta, joten negatiivisempi raja tarkoittaa, että esiasetus sietää heikomman ja kohinaisemman signaalin (suurempi kantama). Katso Miten signaalimittari toimii saadaksesi täydellisen selityksen. | Esiasetus | Kantama | Nopeus | SNR-raja | Paras käyttöön | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Tiheä kaupunkiympäristö suoralla näköyhteydellä; paljon dataa siirtävät sovellukset | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Kaupunkialueet, rakennuksia muutaman korttelin säteellä | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Lyhyen kantaman esikaupunkialueet; kohtalainen rakennustiheys | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Esikaupunkialueet; kohtalainen rakennustiheys | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Esikaupunki-/maaseutualueet; kohtalainen kantama ja hitaampi nopeus | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Samankaltainen kantama kuin Long Fast -asetuksella, mutta 500 kHz:n kaistanleveydellä; suurempi tiedonsiirtonopeus | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | Yleiskäyttö (oletus) — tasapaino kantaman ja nopeuden välillä | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Maaseutualueet, joissa on jonkin verran maastonmuotoja; satunnainen käyttö | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD -alue (125 kHz BW); verrattavissa Medium Fast -asetukseen | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD -alue (125 kHz BW); verrattavissa Long Fast -asetukseen | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz -alue (62,5 kHz BW); välttää häiriöitä muiden laitteiden kanssa | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz -alue (62,5 kHz BW); verrattavissa Long Fast -asetukseen | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Vanhentunut — edelleen valittavissa, mutta voidaan poistaa tulevassa laiteohjelmistoversiossa | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Vanhentunut — edelleen valittavissa, mutta voidaan poistaa tulevassa laiteohjelmistoversiossa | . ℹ️ Huomautus: Tässä taulukossa käytetään yleisesti käytössä olevia lyhyitä nimiä. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . Modeemiesiasetus määrittää tärkeimmän kompromissin kantaman ja tiedonsiirtonopeuden välillä: . | Hitaammat esiasetukset käyttävät enemmän hajautusta, jolloin signaali voidaan purkaa heikommilla signaalitasoilla (alempi SNR-raja). Tämä tarkoittaa pidempää kantamaa, mutta vähemmän tavuja sekunnissa. | Nopeammat esiasetukset siirtävät enemmän dataa, mutta vaativat vahvemman signaalin purkamista varten. | . Käytännön ohje: . | Kaupunkiverkko (paljon radioita, lyhyet etäisyydet): Käytä Long Fast -asetusta (oletus) tai Short Fast -asetusta. Suurempi nopeus tarkoittaa vähemmän käyttöasteruuhkaa, kun monet radiot jakavat saman kanavan. | Maaseutu tai harva verkko (vähän radioita, pitkät etäisyydet): Käytä Long Moderate -asetusta. Kantama on tärkeämpi kuin nopeus, kun radiot ovat kaukana toisistaan. | EU 866/868 MHz -alueen säädösten noudattaminen: Käytä Lite Fast, Lite Slow, Narrow Fast tai Narrow Slow -asetuksia — ne on optimoitu EU:n SRD/868 MHz -alueille kapeammilla kaistanleveyksillä. | Kiinteät infrastruktuurilinkit: Käytä Short Turbo- tai Long Turbo -asetusta erillisille pisteestä pisteeseen -linkeille, joissa on hyvät antennit ja suora näköyhteys. | Sekaverkot: Pysy Long Fast -asetuksessa — se on yhteisön oletusasetus ja varmistaa yhteensopivuuden alueesi muiden käyttäjien kanssa. | . Kaikkien samalla kanavalla olevien radioiden on käytettävä samaa modeemiesiasetusta. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. Modeemiesiasetukset-taulukon kantama-arviot perustuvat tasaiseen maastoon ja vaatimattomiin antenneihin. Korkeuseroetu (mäki, rakennuksen katto) kasvattaa käytännön kantamaa huomattavasti. Hyvin sijoitettu Long Fast -asetusta käyttävä Router voi usein toimia paremmin kuin maan tasalla oleva Long Slow -asetusta käyttävä radio. Näytön asetukset . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Asetus | Kuvaus | . | Näytön päälläoloaika | Kuinka kauan näyttö pysyy päällä ennen siirtymistä lepotilaan | . | Karusellin aikaväli | How often the node cycles between screens on its own | . | Näyttötila | Laiteohjelmiston käyttämä näytön asettelu/tiheys | . | Näyttöyksiköt | Metric or Imperial on the node’s screen | . | Käytä 12 tunnin kelloa | Show the node’s clock as 12-hour rather than 24-hour | . | Lihavoitu otsikko | Näytä näytön otsikkoteksti lihavoituna | . | Käännä näyttö | Kierrä näyttö 180° ylösalaisin asennusta varten | . | OLED-tyyppi | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Herätä napautuksesta tai liikkeestä | Light the screen when the node is tapped or moved | . | Kompassin suuntaus | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Osoita aina pohjoiseen | Lukitsee kompassinäytön näyttämään pohjoiseen sen sijaan, että se kääntyisi kulkusuunnan mukaan. Riippumaton kompassin suunnasta — kumpikaan ei korvaa toista | . Sijainnin asetukset . On Settings → Device configuration → Position. | Asetus | Kuvaus | . | GPS-tila (fyysinen laitteisto) | Kolmitilainen: GPS käytössä, poistettu käytöstä tai ei käytettävissä. Ei pelkkä käytössä / poistettu käytöstä -asetus | . | GPS-kyselyn aikaväli | How often the node asks its GPS for a fix | . | Lähetyksen aikaväli | Kuinka usein sijainti jaetaan mesh-verkkoon | . | Älykäs sijainti | Lähettää sijainnin liikkeen perusteella pelkän aikavälin sijaan | . | Älykäs aikaväli | Älykäs sijainti -toiminnon ollessa käytössä lyhin sallittu aika sijaintilähetysten välillä | . | Älykäs etäisyys | Älykäs sijainti -toiminnon ollessa käytössä, kuinka pitkän matkan on liikuttava ennen sijainnin lähettämistä | . | Kiinteä sijainti | Käytä käsin syötettyä leveyspiiriä, pituuspiiriä ja korkeutta GPS:n sijaan | . | Sijaintimerkinnät | Asetusryhmä, jolla valitaan, mitkä tiedot liitetään sijaintiin — kuten korkeus, viitekehys, tarkkuus, näkyvissä olevat satelliitit, aikaleima ja muut tiedot | . | GPS EN / Vastaanotto / Lähetys GPIO | Lisäasetukset: nastat, joihin GPS-moduuli on kytketty | . Virran asetukset . On Settings → Device configuration → Power. | Asetus | Kuvaus | . | Ota virransäästötila käyttöön | Let the node sleep aggressively between activity | . | Sammuta virran katketessa | Sammuta laite, kun ulkoinen virta katkeaa | . | Super-syväunen kesto | Kuinka kauan syvin lepotila kestää | . | Vähimmäisherätyksen kesto | The shortest time the node stays awake once woken | . | Bluetoothin odotusaika | Kuinka kauan odotetaan puhelimen yhteyden muodostumista ennen lepotilaan siirtymistä | . | ADC-kertoimen ohitus | Ota akun jännitemittauksille käyttöön manuaalinen korjaus | . | Korvaava AD-muuntimen kerroin | Korjauskerroin, käytössä vain kun manuaalinen korjaus on käytössä | . | INA_2XX-akun valvontapiirin I2C-osoite | Ulkoisen INA-sarjan tehoanturin osoite, jos sellainen on asennettu | . Verkon asetukset . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Asetus | Kuvaus | . | WiFi käytössä | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Verkon nimi, johon yhdistetään. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Salasana | Verkon salasana | . | Ethernet käytössä | Käytä langallista yhteyttä sitä tukevalla laitteistolla | . | IPv4-tila | DHCP, or a static address configured with the four fields that follow | . | WiFi IP / Aliverkko / Yhdyskäytävä / DNS | Kiinteä IP-osoite, käytössä vain kun IPv4-tila on kiinteä | . | UDP-lähetys | Jaa mesh-verkon liikenne muiden radioiden kanssa lähiverkon kautta | . | NTP palvelin | Ajan synkronointipalvelin (NTP-palvelin) | . | rsyslog-palvelin | Etätietojen palvelin | . Bluetooth asetukset . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Asetus | Kuvaus | . | Bluetooth käytössä | Ota Bluetooth-radio käyttöön tai poista käytöstä | . | Paritustila | Kiinteä PIN-koodi, satunnainen PIN-koodi tai ei PIN-koodia | . | Kiinteä PIN-koodi | Pariliitoksen PIN-koodi. Siinä on oltava täsmälleen kuusi numeroa — kenttä hylkää kaikki muut arvot | . Turvallisuusasetukset . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Asetus | Kuvaus | . | Julkinen avain | Radiosi julkinen avain (vain luku) | . | Ylläpitäjän avain | Avaimet, joilla tätä radiota voidaan hallita etänä – enintään kolme | . | Yksityinen avain | Radiosi yksityinen avain (säilytä turvallisesti). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Luo uusi yksityinen avain | Luo tälle radiolle uuden avainparin vahvistuksen jälkeen. Kaikkien vanhan avaimesi tunteneiden vertaisradioiden on opittava uusi avain | . | Ylläpitokanava käytössä | ⚠️ Poistettu — määritetään nyt automaattisesti, kun ylläpitoavain asetetaan | . | Sarjaporttikonsoli | Serial console over the Stream API | . | Vianetsintälokirajapinta käytössä | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Hallintatila | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Voidaan valita vasta, kun järjestelmänvalvojan avain on määritetty | . | Varmuuskopioi avaimet | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Palauta avaimet | Kirjoita varmuuskopioidut avaimet takaisin radioon (käytettävissä, kun varmuuskopio on olemassa) | . | Poista avaimen varmuuskopio | Remove the stored key backup from this phone | . | Suojaustaso | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lukitustila . Lukitustila salaa laitteen tallennustilan ja edellyttää tunnuslausetta jokaiselle yhteydelle. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Tunnuslauseen lisäksi määrität rajat, joiden täyttyessä istunto päättyy automaattisesti: . | Kenttä | Mitä se tekee | . | Jäljellä olevat käynnistykset | Kuinka monen käynnistyksen ajan avattu tila säilyy | . | Tuntia vanhenemiseen saakka | Avatun tilan enimmäiskesto | . | Istunnon enimmäiskesto (minuuttia) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Kun lukitustila on käytössä, tässä lukee Aktiivinen – tallennustila salattu, tämä yhteys todennettu, kun yhteys on avattu, tai Aktiivinen – avaa tämä yhteys antamalla tunnuslause, kun sitä ei ole avattu. Lukitse nyt päättää nykyisen istunnon välittömästi. Toistuvat virheelliset tunnuslauseet rajoitetaan odotusajalla, ennen kuin voit yrittää uudelleen. ⚠️ Varoitus: Tunnuslausetta ei voi palauttaa. Jos kadotat sen, laite on tyhjennettävä sen palauttamiseksi, jolloin sen avaimet, kanavat ja asetukset poistuvat. ", + "content": "Laitteen asetukset . On Settings → Device configuration → Device. | Asetus | Kuvaus | Oletus | . | Laitteen rooli | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Uudelleenlähetyksen tila | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Laitteen tietojen lähetyksen aikaväli | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Kaksoisnapautus painikkeena | Käsittele kaksoisnapautus painikkeen painalluksena | Ei käytössä | . | Kolmoisklikkaus Ad Hoc -pingille | Lähetä kertaluonteinen sijaintipyyntö kolminkertaisella painalluksella | Käytössä | . | Ledin valvontasignaali | Vilkuta tilan merkkilediä säännöllisesti | Käytössä | . | Aikavyöhyke | Laitteen kellon POSIX-aikavyöhyke. Painikkeilla voit kopioida puhelimesi aikavyöhykkeen tai tyhjentää kentän | — | . | Painikkeen / summerin GPIO | Lisäasetukset: GPIO-nastat, joihin painike ja summeri on kytketty | — | . LoRa:n asetukset . On Settings → LoRa. | Asetus | Kuvaus | Oletus | . | Alue | Taajuusalueen sääntelyalue. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Ei asetettu (on määritettävä) | . | Esiasetukset | Nopeuden ja kantaman välinen kompromissi | LongFast | . | Hyppyjen määrä | Suurin hyppyjen määrä | 3 | . | Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (alueen enimmäisteho) | . | Taajuuden ohitus | Ohittaa lasketun käyttötaajuuden (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (käytä laskettua arvoa) | . | Käytä esiasetusta | Oletusarvoisesti käytössä. Poista tämä käytöstä, jos haluat määrittää hajotuskerroin-, koodausnopeus- ja kaistanleveysasetukset käsin modeemiesiasetuksen sijaan | Käytössä | . | Levennyskerroin (Spread Factor) | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | Esiasetuksesta | . | Koodausnopeus | Vain manuaalitilassa: 5–8. Suurempi virheenkorjaus lisää lähetysaikaa | Esiasetuksesta | . | Kaistanleveys | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | Esiasetuksesta | . | Taajuuspaikka | Määrittää, mitä alueen taajuusväliä käytetään. 0 muodostetaan ensisijaisen kanavan nimestä | 0 (automaattinen) | . | Lähetys käytössä | Tämän poistaminen käytöstä tekee radiosta vain vastaanottavan | Käytössä | . | Ohita käyttöaste (Duty Cycle) | Ohittaa alueen lähetysajan käyttörajoituksen. Laitonta useimmilla alueilla. Ota käyttöön vain, jos radioamatöörilupasi sallii sen | Pois | . | Ohita MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | MQTT päällä | Salli yhdyskäytävien välittää pakettisi MQTT:hen | Pois | . | RX tehostettu vahvistus | Lisävastaanottovahvistus SX126x-radioille. Kuluttaa hieman enemmän virtaa | Pois | . | PA tuuletin pois käytöstä | Poista päätevahvistimen tuuletin käytöstä laitteissa, joissa sellainen on | Pois | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Tärkeää: Käyttö väärällä alueasetuksella voi rikkoa paikallisia radiomääräyksiä. Katso alueasetusten määritysopas meshtastic.org-sivustolta saadaksesi lisätietoja. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Vinkki: SNR-raja-arvot ovat tarkoituksella negatiivisia. LoRa pystyy purkamaan signaaleja kohinatason alapuolelta, joten negatiivisempi raja tarkoittaa, että esiasetus sietää heikomman ja kohinaisemman signaalin (suurempi kantama). Katso Miten signaalimittari toimii saadaksesi täydellisen selityksen. | Esiasetus | Kantama | Nopeus | SNR-raja | Paras käyttöön | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Tiheä kaupunkiympäristö suoralla näköyhteydellä; paljon dataa siirtävät sovellukset | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Kaupunkialueet, rakennuksia muutaman korttelin säteellä | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Lyhyen kantaman esikaupunkialueet; kohtalainen rakennustiheys | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Esikaupunkialueet; kohtalainen rakennustiheys | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Esikaupunki-/maaseutualueet; kohtalainen kantama ja hitaampi nopeus | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Samankaltainen kantama kuin Long Fast -asetuksella, mutta 500 kHz:n kaistanleveydellä; suurempi tiedonsiirtonopeus | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | Yleiskäyttö (oletus) — tasapaino kantaman ja nopeuden välillä | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Maaseutualueet, joissa on jonkin verran maastonmuotoja; satunnainen käyttö | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD -alue (125 kHz BW); verrattavissa Medium Fast -asetukseen | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD -alue (125 kHz BW); verrattavissa Long Fast -asetukseen | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz -alue (62,5 kHz BW); välttää häiriöitä muiden laitteiden kanssa | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz -alue (62,5 kHz BW); verrattavissa Long Fast -asetukseen | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Vanhentunut — edelleen valittavissa, mutta voidaan poistaa tulevassa laiteohjelmistoversiossa | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Vanhentunut — edelleen valittavissa, mutta voidaan poistaa tulevassa laiteohjelmistoversiossa | . ℹ️ Huomautus: Tässä taulukossa käytetään yleisesti käytössä olevia lyhyitä nimiä. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . Modeemiesiasetus määrittää tärkeimmän kompromissin kantaman ja tiedonsiirtonopeuden välillä: . | Hitaammat esiasetukset käyttävät enemmän hajautusta, jolloin signaali voidaan purkaa heikommilla signaalitasoilla (alempi SNR-raja). Tämä tarkoittaa pidempää kantamaa, mutta vähemmän tavuja sekunnissa. | Nopeammat esiasetukset siirtävät enemmän dataa, mutta vaativat vahvemman signaalin purkamista varten. | . Käytännön ohje: . | Kaupunkiverkko (paljon radioita, lyhyet etäisyydet): Käytä Long Fast -asetusta (oletus) tai Short Fast -asetusta. Suurempi nopeus tarkoittaa vähemmän käyttöasteruuhkaa, kun monet radiot jakavat saman kanavan. | Maaseutu tai harva verkko (vähän radioita, pitkät etäisyydet): Käytä Long Moderate -asetusta. Kantama on tärkeämpi kuin nopeus, kun radiot ovat kaukana toisistaan. | EU 866/868 MHz -alueen säädösten noudattaminen: Käytä Lite Fast, Lite Slow, Narrow Fast tai Narrow Slow -asetuksia — ne on optimoitu EU:n SRD/868 MHz -alueille kapeammilla kaistanleveyksillä. | Kiinteät infrastruktuurilinkit: Käytä Short Turbo- tai Long Turbo -asetusta erillisille pisteestä pisteeseen -linkeille, joissa on hyvät antennit ja suora näköyhteys. | Sekaverkot: Pysy Long Fast -asetuksessa — se on yhteisön oletusasetus ja varmistaa yhteensopivuuden alueesi muiden käyttäjien kanssa. | . Kaikkien samalla kanavalla olevien radioiden on käytettävä samaa modeemiesiasetusta. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. Modeemiesiasetukset-taulukon kantama-arviot perustuvat tasaiseen maastoon ja vaatimattomiin antenneihin. Korkeuseroetu (mäki, rakennuksen katto) kasvattaa käytännön kantamaa huomattavasti. Hyvin sijoitettu Long Fast -asetusta käyttävä Router voi usein toimia paremmin kuin maan tasalla oleva Long Slow -asetusta käyttävä radio. Näytön asetukset . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Asetus | Kuvaus | . | Näytön päälläoloaika | Kuinka kauan näyttö pysyy päällä ennen siirtymistä lepotilaan | . | Karusellin aikaväli | How often the node cycles between screens on its own | . | Näyttötila | Laiteohjelmiston käyttämä näytön asettelu/tiheys | . | Näyttöyksiköt | Metric or Imperial on the node’s screen | . | Käytä 12 tunnin kelloa | Show the node’s clock as 12-hour rather than 24-hour | . | Lihavoitu otsikko | Näytä näytön otsikkoteksti lihavoituna | . | Käännä näyttö | Kierrä näyttö 180° ylösalaisin asennusta varten | . | OLED-tyyppi | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Herätä napautuksesta tai liikkeestä | Light the screen when the node is tapped or moved | . | Kompassin suuntaus | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Osoita aina pohjoiseen | Lukitsee kompassinäytön näyttämään pohjoiseen sen sijaan, että se kääntyisi kulkusuunnan mukaan. Riippumaton kompassin suunnasta — kumpikaan ei korvaa toista | . Sijainnin asetukset . On Settings → Device configuration → Position. | Asetus | Kuvaus | . | GPS-tila (fyysinen laitteisto) | Kolmitilainen: GPS käytössä, poistettu käytöstä tai ei käytettävissä. Ei pelkkä käytössä / poistettu käytöstä -asetus | . | GPS-kyselyn aikaväli | How often the node asks its GPS for a fix | . | Lähetyksen aikaväli | Kuinka usein sijainti jaetaan mesh-verkkoon | . | Älykäs sijainti | Lähettää sijainnin liikkeen perusteella pelkän aikavälin sijaan | . | Älykäs aikaväli | Älykäs sijainti -toiminnon ollessa käytössä lyhin sallittu aika sijaintilähetysten välillä | . | Älykäs etäisyys | Älykäs sijainti -toiminnon ollessa käytössä, kuinka pitkän matkan on liikuttava ennen sijainnin lähettämistä | . | Kiinteä sijainti | Käytä käsin syötettyä leveyspiiriä, pituuspiiriä ja korkeutta GPS:n sijaan | . | Sijaintimerkinnät | Asetusryhmä, jolla valitaan, mitkä tiedot liitetään sijaintiin — kuten korkeus, viitekehys, tarkkuus, näkyvissä olevat satelliitit, aikaleima ja muut tiedot | . | GPS EN / Vastaanotto / Lähetys GPIO | Lisäasetukset: nastat, joihin GPS-moduuli on kytketty | . Virran asetukset . On Settings → Device configuration → Power. | Asetus | Kuvaus | . | Ota virransäästötila käyttöön | Let the node sleep aggressively between activity | . | Sammuta virran katketessa | Sammuta laite, kun ulkoinen virta katkeaa | . | Super-syväunen kesto | Kuinka kauan syvin lepotila kestää | . | Vähimmäisherätyksen kesto | The shortest time the node stays awake once woken | . | Bluetoothin odotusaika | Kuinka kauan odotetaan puhelimen yhteyden muodostumista ennen lepotilaan siirtymistä | . | ADC-kertoimen ohitus | Ota akun jännitemittauksille käyttöön manuaalinen korjaus | . | Korvaava AD-muuntimen kerroin | Korjauskerroin, käytössä vain kun manuaalinen korjaus on käytössä | . | INA_2XX-akun valvontapiirin I2C-osoite | Ulkoisen INA-sarjan tehoanturin osoite, jos sellainen on asennettu | . Verkon asetukset . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Asetus | Kuvaus | . | WiFi käytössä | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Verkon nimi, johon yhdistetään. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Salasana | Verkon salasana | . | Ethernet käytössä | Käytä langallista yhteyttä sitä tukevalla laitteistolla | . | IPv4-tila | DHCP, or a static address configured with the four fields that follow | . | WiFi IP / Aliverkko / Yhdyskäytävä / DNS | Kiinteä IP-osoite, käytössä vain kun IPv4-tila on kiinteä | . | UDP-lähetys | Jaa mesh-verkon liikenne muiden radioiden kanssa lähiverkon kautta | . | NTP palvelin | Ajan synkronointipalvelin (NTP-palvelin) | . | rsyslog-palvelin | Etätietojen palvelin | . Bluetooth asetukset . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Asetus | Kuvaus | . | Bluetooth käytössä | Ota Bluetooth-radio käyttöön tai poista käytöstä | . | Paritustila | Kiinteä PIN-koodi, satunnainen PIN-koodi tai ei PIN-koodia | . | Kiinteä PIN-koodi | Pariliitoksen PIN-koodi. Siinä on oltava täsmälleen kuusi numeroa — kenttä hylkää kaikki muut arvot | . Turvallisuusasetukset . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Asetus | Kuvaus | . | Julkinen avain | Radiosi julkinen avain (vain luku) | . | Ylläpitäjän avain | Avaimet, joilla tätä radiota voidaan hallita etänä – enintään kolme | . | Yksityinen avain | Radiosi yksityinen avain (säilytä turvallisesti). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Luo uusi yksityinen avain | Luo tälle radiolle uuden avainparin vahvistuksen jälkeen. Kaikkien vanhan avaimesi tunteneiden vertaisradioiden on opittava uusi avain | . | Ylläpitokanava käytössä | ⚠️ Poistettu — määritetään nyt automaattisesti, kun ylläpitoavain asetetaan | . | Sarjaporttikonsoli | Serial console over the Stream API | . | Vianetsintälokirajapinta käytössä | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Hallintatila | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Voidaan valita vasta, kun järjestelmänvalvojan avain on määritetty | . | Varmuuskopioi avaimet | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Palauta avaimet | Kirjoita varmuuskopioidut avaimet takaisin radioon (käytettävissä, kun varmuuskopio on olemassa) | . | Poista avaimen varmuuskopio | Remove the stored key backup from this phone | . | Suojaustaso | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lukitustila . Lukitustila salaa laitteen tallennustilan ja edellyttää tunnuslausetta jokaiselle yhteydelle. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Tunnuslauseen lisäksi määrität rajat, joiden täyttyessä istunto päättyy automaattisesti: . | Kenttä | Mitä se tekee | . | Jäljellä olevat käynnistykset | Kuinka monen käynnistyksen ajan avattu tila säilyy | . | Tuntia vanhenemiseen saakka | Avatun tilan enimmäiskesto | . | Istunnon enimmäiskesto (minuuttia) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Kun lukitustila on käytössä, tässä lukee Aktiivinen – tallennustila salattu, tämä yhteys todennettu, kun yhteys on avattu, tai Aktiivinen – avaa tämä yhteys antamalla tunnuslause, kun sitä ei ole avattu. Lukitse nyt päättää nykyisen istunnon välittömästi. Toistuvat virheelliset tunnuslauseet rajoitetaan odotusajalla, ennen kuin voit yrittää uudelleen. ⚠️ Varoitus: Tunnuslausetta ei voi palauttaa. Jos kadotat sen, laite on tyhjennettävä sen palauttamiseksi, jolloin sen avaimet, kanavat ja asetukset poistuvat. ", "url": "/Meshtastic-Android/main/fi-rFI/user/settings-radio-user.html#asetukset", "relUrl": "/fi-rFI/user/settings-radio-user.html#asetukset" @@ -31970,7 +31970,7 @@ },"4567": { "doc": "Settings — Radio & User", "title": "Configuration", - "content": "Device Config . On Settings → Device configuration → Device. | Setting | Lýsing | Default | . | Device Role | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Rebroadcast Mode | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Node Info Broadcast Interval | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Double Tap as Button | Treat a double tap as a button press | Disabled | . | Triple Click Ad Hoc Ping | Send an ad-hoc position ping on a triple click | Enabled | . | LED Heartbeat | Blink the status LED periodically | Enabled | . | Time Zone | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRa Config . On Settings → LoRa. | Setting | Lýsing | Default | . | Svæði | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Presets | Speed/range tradeoff | LongFast | . | Number of Hops | Maximum retransmit hops | 3 | . | Transmit Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Frequency Slot | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Transmit Enabled | Turning this off makes the node receive-only | On | . | Override Duty Cycle | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | . | Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | . | RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | . | PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Speed | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Lýsing | . | Screen on for | How long the display stays lit before sleeping | . | Carousel interval | How often the node cycles between screens on its own | . | Display mode | Screen layout/density used by the firmware | . | Display units | Metric or Imperial on the node’s screen | . | Use 12h clock format | Show the node’s clock as 12-hour rather than 24-hour | . | Bold Heading | Draw the screen’s heading text in bold | . | Flip screen | Rotate the display 180° for an inverted mounting | . | OLED type | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Wake on tap or motion | Light the screen when the node is tapped or moved | . | Compass orientation | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Always point north | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Position Config . On Settings → Device configuration → Position. | Setting | Lýsing | . | GPS Mode (Physical Hardware) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Polling Interval | How often the node asks its GPS for a fix | . | Broadcast Interval | How often the position is shared with the mesh | . | Smart Position | Broadcast based on movement rather than purely on the clock | . | Smart Interval | With Smart Position on, the shortest gap between broadcasts | . | Smart Distance | With Smart Position on, how far you must move before broadcasting | . | Fixed Position | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Position Flags | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Power Config . On Settings → Device configuration → Power. | Setting | Lýsing | . | Enable power saving mode | Let the node sleep aggressively between activity | . | Shutdown on power loss | Power the device down after external power disappears | . | Super deep sleep duration | How long the deepest sleep state lasts | . | Minimum wake time | The shortest time the node stays awake once woken | . | Wait for Bluetooth duration | How long to wait for a phone to connect before sleeping | . | ADC multiplier override | Turn on a manual correction for battery-voltage readings | . | ADC multiplier override ratio | The correction factor itself, used only when the override is on | . | Battery INA_2XX I2C address | Address of an external INA-series power sensor, if fitted | . Network Config . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Lýsing | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Password | Network password | . | Ethernet enabled | Use a wired connection on hardware that has one | . | IPv4 mode | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | NTP server | Time synchronization server | . | rsyslog server | Remote logging server | . Bluetooth Config . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Lýsing | . | Bluetooth enabled | Enable/disable BLE radio | . | Pairing mode | Fixed PIN, Random PIN, or No PIN | . | Fixed PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Security Config . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Lýsing | . | Public Key | Your node’s public key (read-only) | . | Admin Key | Keys permitted to administer this node remotely — up to three | . | Private Key | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Regenerate Private Key | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Serial console | Serial console over the Stream API | . | Debug log API enabled | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Managed Mode | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Backup Keys | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ", + "content": "Device Config . On Settings → Device configuration → Device. | Setting | Lýsing | Default | . | Device Role | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Rebroadcast Mode | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Node Info Broadcast Interval | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Double Tap as Button | Treat a double tap as a button press | Disabled | . | Triple Click Ad Hoc Ping | Send an ad-hoc position ping on a triple click | Enabled | . | LED Heartbeat | Blink the status LED periodically | Enabled | . | Time Zone | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRa Config . On Settings → LoRa. | Setting | Lýsing | Default | . | Svæði | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Presets | Speed/range tradeoff | LongFast | . | Number of Hops | Maximum retransmit hops | 3 | . | Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) | . | Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Frequency Slot | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Transmit Enabled | Turning this off makes the node receive-only | On | . | Override Duty Cycle | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | . | Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | . | RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | . | PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Speed | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Lýsing | . | Screen on for | How long the display stays lit before sleeping | . | Carousel interval | How often the node cycles between screens on its own | . | Display mode | Screen layout/density used by the firmware | . | Display units | Metric or Imperial on the node’s screen | . | Use 12h clock format | Show the node’s clock as 12-hour rather than 24-hour | . | Bold Heading | Draw the screen’s heading text in bold | . | Flip screen | Rotate the display 180° for an inverted mounting | . | OLED type | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Wake on tap or motion | Light the screen when the node is tapped or moved | . | Compass orientation | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Always point north | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Position Config . On Settings → Device configuration → Position. | Setting | Lýsing | . | GPS Mode (Physical Hardware) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Polling Interval | How often the node asks its GPS for a fix | . | Broadcast Interval | How often the position is shared with the mesh | . | Smart Position | Broadcast based on movement rather than purely on the clock | . | Smart Interval | With Smart Position on, the shortest gap between broadcasts | . | Smart Distance | With Smart Position on, how far you must move before broadcasting | . | Fixed Position | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Position Flags | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Power Config . On Settings → Device configuration → Power. | Setting | Lýsing | . | Enable power saving mode | Let the node sleep aggressively between activity | . | Shutdown on power loss | Power the device down after external power disappears | . | Super deep sleep duration | How long the deepest sleep state lasts | . | Minimum wake time | The shortest time the node stays awake once woken | . | Wait for Bluetooth duration | How long to wait for a phone to connect before sleeping | . | ADC multiplier override | Turn on a manual correction for battery-voltage readings | . | ADC multiplier override ratio | The correction factor itself, used only when the override is on | . | Battery INA_2XX I2C address | Address of an external INA-series power sensor, if fitted | . Network Config . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Lýsing | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Password | Network password | . | Ethernet enabled | Use a wired connection on hardware that has one | . | IPv4 mode | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | NTP server | Time synchronization server | . | rsyslog server | Remote logging server | . Bluetooth Config . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Lýsing | . | Bluetooth enabled | Enable/disable BLE radio | . | Pairing mode | Fixed PIN, Random PIN, or No PIN | . | Fixed PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Security Config . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Lýsing | . | Public Key | Your node’s public key (read-only) | . | Admin Key | Keys permitted to administer this node remotely — up to three | . | Private Key | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Regenerate Private Key | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Serial console | Serial console over the Stream API | . | Debug log API enabled | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Managed Mode | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Backup Keys | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ", "url": "/Meshtastic-Android/main/is-rIS/user/settings-radio-user.html#configuration", "relUrl": "/is-rIS/user/settings-radio-user.html#configuration" @@ -32012,7 +32012,7 @@ },"4573": { "doc": "Settings — Radio & User", "title": "Configuration", - "content": "Device Config . On Settings → Device configuration → Device. | Setting | Aprašymas | Default | . | Device Role | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Rebroadcast Mode | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Node Info Broadcast Interval | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Double Tap as Button | Treat a double tap as a button press | Disabled | . | Triple Click Ad Hoc Ping | Send an ad-hoc position ping on a triple click | Enabled | . | LED Heartbeat | Blink the status LED periodically | Enabled | . | Time Zone | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRa Config . On Settings → LoRa. | Setting | Aprašymas | Default | . | Regionas | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Presets | Speed/range tradeoff | LongFast | . | Number of Hops | Maximum retransmit hops | 3 | . | Transmit Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Frequency Slot | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Transmit Enabled | Turning this off makes the node receive-only | On | . | Override Duty Cycle | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | . | Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | . | RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | . | PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Speed | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Aprašymas | . | Screen on for | How long the display stays lit before sleeping | . | Carousel interval | How often the node cycles between screens on its own | . | Display mode | Screen layout/density used by the firmware | . | Display units | Metric or Imperial on the node’s screen | . | Use 12h clock format | Show the node’s clock as 12-hour rather than 24-hour | . | Bold Heading | Draw the screen’s heading text in bold | . | Flip screen | Rotate the display 180° for an inverted mounting | . | OLED type | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Wake on tap or motion | Light the screen when the node is tapped or moved | . | Compass orientation | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Always point north | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Position Config . On Settings → Device configuration → Position. | Setting | Aprašymas | . | GPS Mode (Physical Hardware) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Polling Interval | How often the node asks its GPS for a fix | . | Broadcast Interval | How often the position is shared with the mesh | . | Smart Position | Broadcast based on movement rather than purely on the clock | . | Smart Interval | With Smart Position on, the shortest gap between broadcasts | . | Smart Distance | With Smart Position on, how far you must move before broadcasting | . | Fixed Position | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Position Flags | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Power Config . On Settings → Device configuration → Power. | Setting | Aprašymas | . | Enable power saving mode | Let the node sleep aggressively between activity | . | Shutdown on power loss | Power the device down after external power disappears | . | Super deep sleep duration | How long the deepest sleep state lasts | . | Minimum wake time | The shortest time the node stays awake once woken | . | Wait for Bluetooth duration | How long to wait for a phone to connect before sleeping | . | ADC multiplier override | Turn on a manual correction for battery-voltage readings | . | ADC multiplier override ratio | The correction factor itself, used only when the override is on | . | Battery INA_2XX I2C address | Address of an external INA-series power sensor, if fitted | . Network Config . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Aprašymas | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Password | Network password | . | Ethernet enabled | Use a wired connection on hardware that has one | . | IPv4 mode | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | NTP server | Time synchronization server | . | rsyslog server | Remote logging server | . Bluetooth Config . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Aprašymas | . | Bluetooth enabled | Enable/disable BLE radio | . | Pairing mode | Fixed PIN, Random PIN, or No PIN | . | Fixed PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Security Config . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Aprašymas | . | Viešasis raktas | Your node’s public key (read-only) | . | Admin Key | Keys permitted to administer this node remotely — up to three | . | Privatus raktas | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Regenerate Private Key | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Serial console | Serial console over the Stream API | . | Debug log API enabled | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Managed Mode | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Backup Keys | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ", + "content": "Device Config . On Settings → Device configuration → Device. | Setting | Aprašymas | Default | . | Device Role | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Rebroadcast Mode | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Node Info Broadcast Interval | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Double Tap as Button | Treat a double tap as a button press | Disabled | . | Triple Click Ad Hoc Ping | Send an ad-hoc position ping on a triple click | Enabled | . | LED Heartbeat | Blink the status LED periodically | Enabled | . | Time Zone | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRa Config . On Settings → LoRa. | Setting | Aprašymas | Default | . | Regionas | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Presets | Speed/range tradeoff | LongFast | . | Number of Hops | Maximum retransmit hops | 3 | . | Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) | . | Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Frequency Slot | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Transmit Enabled | Turning this off makes the node receive-only | On | . | Override Duty Cycle | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | . | Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | . | RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | . | PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Speed | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Aprašymas | . | Screen on for | How long the display stays lit before sleeping | . | Carousel interval | How often the node cycles between screens on its own | . | Display mode | Screen layout/density used by the firmware | . | Display units | Metric or Imperial on the node’s screen | . | Use 12h clock format | Show the node’s clock as 12-hour rather than 24-hour | . | Bold Heading | Draw the screen’s heading text in bold | . | Flip screen | Rotate the display 180° for an inverted mounting | . | OLED type | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Wake on tap or motion | Light the screen when the node is tapped or moved | . | Compass orientation | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Always point north | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Position Config . On Settings → Device configuration → Position. | Setting | Aprašymas | . | GPS Mode (Physical Hardware) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Polling Interval | How often the node asks its GPS for a fix | . | Broadcast Interval | How often the position is shared with the mesh | . | Smart Position | Broadcast based on movement rather than purely on the clock | . | Smart Interval | With Smart Position on, the shortest gap between broadcasts | . | Smart Distance | With Smart Position on, how far you must move before broadcasting | . | Fixed Position | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Position Flags | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Power Config . On Settings → Device configuration → Power. | Setting | Aprašymas | . | Enable power saving mode | Let the node sleep aggressively between activity | . | Shutdown on power loss | Power the device down after external power disappears | . | Super deep sleep duration | How long the deepest sleep state lasts | . | Minimum wake time | The shortest time the node stays awake once woken | . | Wait for Bluetooth duration | How long to wait for a phone to connect before sleeping | . | ADC multiplier override | Turn on a manual correction for battery-voltage readings | . | ADC multiplier override ratio | The correction factor itself, used only when the override is on | . | Battery INA_2XX I2C address | Address of an external INA-series power sensor, if fitted | . Network Config . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Aprašymas | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Password | Network password | . | Ethernet enabled | Use a wired connection on hardware that has one | . | IPv4 mode | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | NTP server | Time synchronization server | . | rsyslog server | Remote logging server | . Bluetooth Config . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Aprašymas | . | Bluetooth enabled | Enable/disable BLE radio | . | Pairing mode | Fixed PIN, Random PIN, or No PIN | . | Fixed PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Security Config . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Aprašymas | . | Viešasis raktas | Your node’s public key (read-only) | . | Admin Key | Keys permitted to administer this node remotely — up to three | . | Privatus raktas | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Regenerate Private Key | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Serial console | Serial console over the Stream API | . | Debug log API enabled | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Managed Mode | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Backup Keys | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ", "url": "/Meshtastic-Android/main/lt-rLT/user/settings-radio-user.html#configuration", "relUrl": "/lt-rLT/user/settings-radio-user.html#configuration" @@ -32054,7 +32054,7 @@ },"4579": { "doc": "Settings — Radio & User", "title": "Configuration", - "content": "Device Config . On Settings → Device configuration → Device. | Setting | Descrición | Default | . | Device Role | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Rebroadcast Mode | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Node Info Broadcast Interval | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Double Tap as Button | Treat a double tap as a button press | Disabled | . | Triple Click Ad Hoc Ping | Send an ad-hoc position ping on a triple click | Enabled | . | LED Heartbeat | Blink the status LED periodically | Enabled | . | Time Zone | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRa Config . On Settings → LoRa. | Setting | Descrición | Default | . | Rexión | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Presets | Speed/range tradeoff | LongFast | . | Number of Hops | Maximum retransmit hops | 3 | . | Transmit Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Frequency Slot | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Transmit Enabled | Turning this off makes the node receive-only | On | . | Override Duty Cycle | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | . | Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | . | RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | . | PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Speed | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Descrición | . | Screen on for | How long the display stays lit before sleeping | . | Carousel interval | How often the node cycles between screens on its own | . | Display mode | Screen layout/density used by the firmware | . | Display units | Metric or Imperial on the node’s screen | . | Use 12h clock format | Show the node’s clock as 12-hour rather than 24-hour | . | Bold Heading | Draw the screen’s heading text in bold | . | Flip screen | Rotate the display 180° for an inverted mounting | . | OLED type | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Wake on tap or motion | Light the screen when the node is tapped or moved | . | Compass orientation | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Always point north | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Position Config . On Settings → Device configuration → Position. | Setting | Descrición | . | GPS Mode (Physical Hardware) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Polling Interval | How often the node asks its GPS for a fix | . | Broadcast Interval | How often the position is shared with the mesh | . | Smart Position | Broadcast based on movement rather than purely on the clock | . | Smart Interval | With Smart Position on, the shortest gap between broadcasts | . | Smart Distance | With Smart Position on, how far you must move before broadcasting | . | Fixed Position | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Position Flags | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Power Config . On Settings → Device configuration → Power. | Setting | Descrición | . | Enable power saving mode | Let the node sleep aggressively between activity | . | Shutdown on power loss | Power the device down after external power disappears | . | Super deep sleep duration | How long the deepest sleep state lasts | . | Minimum wake time | The shortest time the node stays awake once woken | . | Wait for Bluetooth duration | How long to wait for a phone to connect before sleeping | . | ADC multiplier override | Turn on a manual correction for battery-voltage readings | . | ADC multiplier override ratio | The correction factor itself, used only when the override is on | . | Battery INA_2XX I2C address | Address of an external INA-series power sensor, if fitted | . Network Config . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Descrición | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Password | Network password | . | Ethernet enabled | Use a wired connection on hardware that has one | . | IPv4 mode | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | NTP server | Time synchronization server | . | rsyslog server | Remote logging server | . Bluetooth Config . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Descrición | . | Bluetooth enabled | Enable/disable BLE radio | . | Pairing mode | Fixed PIN, Random PIN, or No PIN | . | Fixed PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Security Config . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Descrición | . | Public Key | Your node’s public key (read-only) | . | Admin Key | Keys permitted to administer this node remotely — up to three | . | Private Key | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Regenerate Private Key | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Serial console | Serial console over the Stream API | . | Debug log API enabled | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Managed Mode | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Backup Keys | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ", + "content": "Device Config . On Settings → Device configuration → Device. | Setting | Descrición | Default | . | Device Role | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Rebroadcast Mode | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Node Info Broadcast Interval | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Double Tap as Button | Treat a double tap as a button press | Disabled | . | Triple Click Ad Hoc Ping | Send an ad-hoc position ping on a triple click | Enabled | . | LED Heartbeat | Blink the status LED periodically | Enabled | . | Time Zone | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRa Config . On Settings → LoRa. | Setting | Descrición | Default | . | Rexión | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Presets | Speed/range tradeoff | LongFast | . | Number of Hops | Maximum retransmit hops | 3 | . | Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) | . | Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Frequency Slot | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Transmit Enabled | Turning this off makes the node receive-only | On | . | Override Duty Cycle | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | . | Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | . | RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | . | PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Speed | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Descrición | . | Screen on for | How long the display stays lit before sleeping | . | Carousel interval | How often the node cycles between screens on its own | . | Display mode | Screen layout/density used by the firmware | . | Display units | Metric or Imperial on the node’s screen | . | Use 12h clock format | Show the node’s clock as 12-hour rather than 24-hour | . | Bold Heading | Draw the screen’s heading text in bold | . | Flip screen | Rotate the display 180° for an inverted mounting | . | OLED type | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Wake on tap or motion | Light the screen when the node is tapped or moved | . | Compass orientation | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Always point north | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Position Config . On Settings → Device configuration → Position. | Setting | Descrición | . | GPS Mode (Physical Hardware) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Polling Interval | How often the node asks its GPS for a fix | . | Broadcast Interval | How often the position is shared with the mesh | . | Smart Position | Broadcast based on movement rather than purely on the clock | . | Smart Interval | With Smart Position on, the shortest gap between broadcasts | . | Smart Distance | With Smart Position on, how far you must move before broadcasting | . | Fixed Position | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Position Flags | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Power Config . On Settings → Device configuration → Power. | Setting | Descrición | . | Enable power saving mode | Let the node sleep aggressively between activity | . | Shutdown on power loss | Power the device down after external power disappears | . | Super deep sleep duration | How long the deepest sleep state lasts | . | Minimum wake time | The shortest time the node stays awake once woken | . | Wait for Bluetooth duration | How long to wait for a phone to connect before sleeping | . | ADC multiplier override | Turn on a manual correction for battery-voltage readings | . | ADC multiplier override ratio | The correction factor itself, used only when the override is on | . | Battery INA_2XX I2C address | Address of an external INA-series power sensor, if fitted | . Network Config . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Descrición | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Password | Network password | . | Ethernet enabled | Use a wired connection on hardware that has one | . | IPv4 mode | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | NTP server | Time synchronization server | . | rsyslog server | Remote logging server | . Bluetooth Config . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Descrición | . | Bluetooth enabled | Enable/disable BLE radio | . | Pairing mode | Fixed PIN, Random PIN, or No PIN | . | Fixed PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Security Config . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Descrición | . | Public Key | Your node’s public key (read-only) | . | Admin Key | Keys permitted to administer this node remotely — up to three | . | Private Key | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Regenerate Private Key | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Serial console | Serial console over the Stream API | . | Debug log API enabled | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Managed Mode | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Backup Keys | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ", "url": "/Meshtastic-Android/main/gl-rES/user/settings-radio-user.html#configuration", "relUrl": "/gl-rES/user/settings-radio-user.html#configuration" @@ -32096,7 +32096,7 @@ },"4585": { "doc": "設定：無線機とユーザー", "title": "設定", - "content": "デバイスの設定 . On Settings → Device configuration → Device. | 設定項目 | 説明 | デフォルト | . | デバイスの役割 | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | 再ブロードキャストモード | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | ノード情報のブロードキャスト間隔 | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | ダブルタップをボタンとして使用 | Treat a double tap as a button press | 無効 | . | トリプルクリックでアドホック Ping | Send an ad-hoc position ping on a triple click | 有効 | . | LED ハートビート | Blink the status LED periodically | 有効 | . | タイムゾーン | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRa設定 . On Settings → LoRa. | 設定項目 | 説明 | デフォルト | . | リージョン | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | 未設定（要設定） | . | プリセット | 速度と距離のトレードオフ | LongFast | . | ホップ数 | 再送信の最大ホップ数 | 3 | . | 送信出力 | 送信出力（dBm）。0 = リージョンで許可された最大値 | 0（リージョン最大） | . | 周波数の上書き | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | プリセットを使用 | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | 拡散率 | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | 符号化レート | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | 帯域 | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | 周波数スロット | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | 送信を有効化 | Turning this off makes the node receive-only | On | . | デューティサイクルを上書き | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | オフ | . | MQTT を無視 | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | MQTT への送信を許可 | Allow your packets to be forwarded to MQTT by gateways | オフ | . | RX ブーストゲイン | Extra receive gain on SX126x radios; costs a little current | オフ | . | PAファン無効 | Turn off the power-amplifier fan on hardware that has one | オフ | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. 詳しくは、meshtastic.org の リージョン設定ガイド を参照してください。 . Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 ヒント： SNR 限界の値は意図的に負の数になっています。 LoRa はノイズフロアを下回る信号でも復調できるため、より負の大きい限界値ほど、そのプリセットは弱くノイズの多い信号に耐えられます（より遠くまで届きます）。詳しい説明は、信号メーターの仕組み を参照してください。 . | プリセット | 距離 | 速度 | SNR 限界 | 最適な用途 | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | 見通しのある高密度な都市部。データ量の多い用途 | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | 都市の住宅街。数ブロック以内の建物 | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | 郊外の短距離。中程度の建物密度 | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | 郊外エリア。中程度の建物密度 | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | 郊外・地方。中程度の距離で低速 | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Long Fast と同程度の距離だが 500 kHz 帯域幅。スループットが速い | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | 一般用途（デフォルト）：距離と速度のバランスが良い | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | 起伏のある地方。ときどき使う用途 | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD 帯（125 kHz 帯域幅）。Medium Fast に相当 | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD 帯（125 kHz 帯域幅）。Long Fast に相当 | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz 帯（62.5 kHz 帯域幅）。他のデバイスとの干渉を避ける | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz 帯（62.5 kHz 帯域幅）。Long Fast に相当 | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ 非推奨：まだ選択できますが、将来のファームウェアリリースで削除される可能性があります | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ 非推奨：まだ選択できますが、将来のファームウェアリリースで削除される可能性があります | . ℹ️ 注意： この表では、一般的な短い名前を使用しています。 The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . モデムプリセットは、距離とデータ速度の基本的なトレードオフを制御します： . | 遅いプリセットは拡散をより多く使い、より弱い信号レベルでも復調できるようにします（SNR 限界が低い）。これは、より遠くまで届く一方で、1 秒あたりのバイト数が少ないことを意味します。 | 速いプリセットは 1 回の送信でより多くのデータを詰め込みますが、復調にはより強い信号が必要です。 | . 実用的な指針： . | 都市部のメッシュ（多数のノード、短距離）： Long Fast（デフォルト）または Short Fast を使用します。速度が速いほど、多くのノードがチャンネルを共有するときの電波利用時間の輻輳が減ります。 | 地方・まばらなメッシュ（少数のノード、長距離）： Long Moderate を使用します。ノードが離れている場合は、速度よりも距離が重要です。 | EU 866／868 MHz の規制対応： Lite Fast、Lite Slow、Narrow Fast、Narrow Slow を使用します。これらは、より狭い帯域幅で EU の SRD／868 MHz 帯に最適化されています。 | 固定インフラのリンク： 良好なアンテナと見通しがある専用のポイントツーポイントリンクには、Short Turbo または Long Turbo を使用します。 | 混在した環境： Long Fast のままにします。これはコミュニティのデフォルトで、地域内の他のユーザーとの互換性を確保します。 | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. 高所（丘の上、屋上）にあると、実効的な距離が大幅に伸びます。適切に設置された Long Fast のルーターは、地上に置かれた Long Slow のノードを上回ることがよくあります。 . 表示設定 . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | 設定項目 | 説明 | . | 画面オンの時間 | How long the display stays lit before sleeping | . | カルーセルの間隔 | How often the node cycles between screens on its own | . | 表示モード | Screen layout/density used by the firmware | . | 表示単位 | Metric or Imperial on the node’s screen | . | 12時間の時計形式を使用 | Show the node’s clock as 12-hour rather than 24-hour | . | 太字の見出し | Draw the screen’s heading text in bold | . | 画面反転 | Rotate the display 180° for an inverted mounting | . | OLED タイプ | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | タップまたは動作で起動 | Light the screen when the node is tapped or moved | . | コンパスの向き | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | 常に北を上にする | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . 位置情報設定 . On Settings → Device configuration → Position. | 設定項目 | 説明 | . | GPS モード（物理ハードウェア） | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS ポーリング間隔 | How often the node asks its GPS for a fix | . | ブロードキャスト間隔 | How often the position is shared with the mesh | . | スマート位置 | Broadcast based on movement rather than purely on the clock | . | スマート間隔 | With Smart Position on, the shortest gap between broadcasts | . | スマート距離 | With Smart Position on, how far you must move before broadcasting | . | 固定位置 | Use a manually entered latitude, longitude and altitude instead of the GPS | . | 位置情報フラグ | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . 電源設定 . On Settings → Device configuration → Power. | 設定項目 | 説明 | . | 省電力モードを有効化 | Let the node sleep aggressively between activity | . | 電源喪失時にシャットダウン | Power the device down after external power disappears | . | スーパーディープスリープの時間 | How long the deepest sleep state lasts | . | 最小起動時間 | The shortest time the node stays awake once woken | . | Bluetooth 待機時間 | How long to wait for a phone to connect before sleeping | . | ADC倍率のオーバーライド | Turn on a manual correction for battery-voltage readings | . | ADC倍率のオーバーライド比 | The correction factor itself, used only when the override is on | . | バッテリー INA_2XX I2C アドレス | Address of an external INA-series power sensor, if fitted | . ネットワーク設定 . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | 設定項目 | 説明 | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | パスワード | ネットワークのパスワード | . | イーサネット有効 | Use a wired connection on hardware that has one | . | IPv4 モード | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP ブロードキャスト | Share mesh traffic with other nodes over the local network | . | NTPサーバー | 時刻同期サーバー | . | rsyslogサーバー | リモートログサーバー | . Bluetooth 設定 . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | 設定項目 | 説明 | . | Bluetoothを有効 | BLE 無線の有効／無効 | . | ペアリングモード | 固定 PIN、ランダム PIN、または PIN なし | . | 固定 PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . セキュリティ設定 . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | 設定項目 | 説明 | . | 公開鍵 | ノードの公開鍵（読み取り専用） | . | 管理者鍵 | Keys permitted to administer this node remotely — up to three | . | 秘密鍵 | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | 秘密鍵を再生成 | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | 管理チャンネルを有効化 | ⚠️ 削除されました：管理者キーを設定すると自動的に構成されるようになりました | . | シリアルコンソール | Serial console over the Stream API | . | デバッグログAPIを有効化 | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | 管理モード | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | 鍵をバックアップ | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | 鍵を復元 | バックアップした鍵をノードに書き戻します（バックアップがある場合に利用可能） | . | 鍵のバックアップを削除 | Remove the stored key backup from this phone | . | 保護レベル | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | 内容 | . | 残りの起動回数 | How many device boots the unlocked state survives | . | 有効期限までの時間 | Wall-clock lifetime of the unlocked state | . | セッション上限（分） | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ", + "content": "デバイスの設定 . On Settings → Device configuration → Device. | 設定項目 | 説明 | デフォルト | . | デバイスの役割 | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | 再ブロードキャストモード | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | ノード情報のブロードキャスト間隔 | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | ダブルタップをボタンとして使用 | Treat a double tap as a button press | 無効 | . | トリプルクリックでアドホック Ping | Send an ad-hoc position ping on a triple click | 有効 | . | LED ハートビート | Blink the status LED periodically | 有効 | . | タイムゾーン | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRa設定 . On Settings → LoRa. | 設定項目 | 説明 | デフォルト | . | リージョン | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | 未設定（要設定） | . | プリセット | 速度と距離のトレードオフ | LongFast | . | ホップ数 | 再送信の最大ホップ数 | 3 | . | Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0（リージョン最大） | . | 周波数の上書き | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | プリセットを使用 | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | 拡散率 | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | 符号化レート | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | 帯域 | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | 周波数スロット | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | 送信を有効化 | Turning this off makes the node receive-only | On | . | デューティサイクルを上書き | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | オフ | . | MQTT を無視 | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | MQTT への送信を許可 | Allow your packets to be forwarded to MQTT by gateways | オフ | . | RX ブーストゲイン | Extra receive gain on SX126x radios; costs a little current | オフ | . | PAファン無効 | Turn off the power-amplifier fan on hardware that has one | オフ | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. 詳しくは、meshtastic.org の リージョン設定ガイド を参照してください。 . Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 ヒント： SNR 限界の値は意図的に負の数になっています。 LoRa はノイズフロアを下回る信号でも復調できるため、より負の大きい限界値ほど、そのプリセットは弱くノイズの多い信号に耐えられます（より遠くまで届きます）。詳しい説明は、信号メーターの仕組み を参照してください。 . | プリセット | 距離 | 速度 | SNR 限界 | 最適な用途 | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | 見通しのある高密度な都市部。データ量の多い用途 | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | 都市の住宅街。数ブロック以内の建物 | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | 郊外の短距離。中程度の建物密度 | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | 郊外エリア。中程度の建物密度 | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | 郊外・地方。中程度の距離で低速 | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Long Fast と同程度の距離だが 500 kHz 帯域幅。スループットが速い | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | 一般用途（デフォルト）：距離と速度のバランスが良い | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | 起伏のある地方。ときどき使う用途 | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD 帯（125 kHz 帯域幅）。Medium Fast に相当 | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD 帯（125 kHz 帯域幅）。Long Fast に相当 | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz 帯（62.5 kHz 帯域幅）。他のデバイスとの干渉を避ける | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz 帯（62.5 kHz 帯域幅）。Long Fast に相当 | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ 非推奨：まだ選択できますが、将来のファームウェアリリースで削除される可能性があります | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ 非推奨：まだ選択できますが、将来のファームウェアリリースで削除される可能性があります | . ℹ️ 注意： この表では、一般的な短い名前を使用しています。 The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . モデムプリセットは、距離とデータ速度の基本的なトレードオフを制御します： . | 遅いプリセットは拡散をより多く使い、より弱い信号レベルでも復調できるようにします（SNR 限界が低い）。これは、より遠くまで届く一方で、1 秒あたりのバイト数が少ないことを意味します。 | 速いプリセットは 1 回の送信でより多くのデータを詰め込みますが、復調にはより強い信号が必要です。 | . 実用的な指針： . | 都市部のメッシュ（多数のノード、短距離）： Long Fast（デフォルト）または Short Fast を使用します。速度が速いほど、多くのノードがチャンネルを共有するときの電波利用時間の輻輳が減ります。 | 地方・まばらなメッシュ（少数のノード、長距離）： Long Moderate を使用します。ノードが離れている場合は、速度よりも距離が重要です。 | EU 866／868 MHz の規制対応： Lite Fast、Lite Slow、Narrow Fast、Narrow Slow を使用します。これらは、より狭い帯域幅で EU の SRD／868 MHz 帯に最適化されています。 | 固定インフラのリンク： 良好なアンテナと見通しがある専用のポイントツーポイントリンクには、Short Turbo または Long Turbo を使用します。 | 混在した環境： Long Fast のままにします。これはコミュニティのデフォルトで、地域内の他のユーザーとの互換性を確保します。 | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. 高所（丘の上、屋上）にあると、実効的な距離が大幅に伸びます。適切に設置された Long Fast のルーターは、地上に置かれた Long Slow のノードを上回ることがよくあります。 . 表示設定 . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | 設定項目 | 説明 | . | 画面オンの時間 | How long the display stays lit before sleeping | . | カルーセルの間隔 | How often the node cycles between screens on its own | . | 表示モード | Screen layout/density used by the firmware | . | 表示単位 | Metric or Imperial on the node’s screen | . | 12時間の時計形式を使用 | Show the node’s clock as 12-hour rather than 24-hour | . | 太字の見出し | Draw the screen’s heading text in bold | . | 画面反転 | Rotate the display 180° for an inverted mounting | . | OLED タイプ | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | タップまたは動作で起動 | Light the screen when the node is tapped or moved | . | コンパスの向き | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | 常に北を上にする | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . 位置情報設定 . On Settings → Device configuration → Position. | 設定項目 | 説明 | . | GPS モード（物理ハードウェア） | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS ポーリング間隔 | How often the node asks its GPS for a fix | . | ブロードキャスト間隔 | How often the position is shared with the mesh | . | スマート位置 | Broadcast based on movement rather than purely on the clock | . | スマート間隔 | With Smart Position on, the shortest gap between broadcasts | . | スマート距離 | With Smart Position on, how far you must move before broadcasting | . | 固定位置 | Use a manually entered latitude, longitude and altitude instead of the GPS | . | 位置情報フラグ | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . 電源設定 . On Settings → Device configuration → Power. | 設定項目 | 説明 | . | 省電力モードを有効化 | Let the node sleep aggressively between activity | . | 電源喪失時にシャットダウン | Power the device down after external power disappears | . | スーパーディープスリープの時間 | How long the deepest sleep state lasts | . | 最小起動時間 | The shortest time the node stays awake once woken | . | Bluetooth 待機時間 | How long to wait for a phone to connect before sleeping | . | ADC倍率のオーバーライド | Turn on a manual correction for battery-voltage readings | . | ADC倍率のオーバーライド比 | The correction factor itself, used only when the override is on | . | バッテリー INA_2XX I2C アドレス | Address of an external INA-series power sensor, if fitted | . ネットワーク設定 . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | 設定項目 | 説明 | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | パスワード | ネットワークのパスワード | . | イーサネット有効 | Use a wired connection on hardware that has one | . | IPv4 モード | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP ブロードキャスト | Share mesh traffic with other nodes over the local network | . | NTPサーバー | 時刻同期サーバー | . | rsyslogサーバー | リモートログサーバー | . Bluetooth 設定 . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | 設定項目 | 説明 | . | Bluetoothを有効 | BLE 無線の有効／無効 | . | ペアリングモード | 固定 PIN、ランダム PIN、または PIN なし | . | 固定 PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . セキュリティ設定 . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | 設定項目 | 説明 | . | 公開鍵 | ノードの公開鍵（読み取り専用） | . | 管理者鍵 | Keys permitted to administer this node remotely — up to three | . | 秘密鍵 | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | 秘密鍵を再生成 | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | 管理チャンネルを有効化 | ⚠️ 削除されました：管理者キーを設定すると自動的に構成されるようになりました | . | シリアルコンソール | Serial console over the Stream API | . | デバッグログAPIを有効化 | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | 管理モード | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | 鍵をバックアップ | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | 鍵を復元 | バックアップした鍵をノードに書き戻します（バックアップがある場合に利用可能） | . | 鍵のバックアップを削除 | Remove the stored key backup from this phone | . | 保護レベル | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | 内容 | . | 残りの起動回数 | How many device boots the unlocked state survives | . | 有効期限までの時間 | Wall-clock lifetime of the unlocked state | . | セッション上限（分） | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ", "url": "/Meshtastic-Android/main/ja-rJP/user/settings-radio-user.html#%E8%A8%AD%E5%AE%9A", "relUrl": "/ja-rJP/user/settings-radio-user.html#設定" @@ -32131,7 +32131,7 @@ },"4590": { "doc": "Settings — Radio & User", "title": "Einstellungen", - "content": "Geräteeinstellungen . On Settings → Device configuration → Device. | Einstellung | Beschreibung | Standardwert | . | Geräterolle | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | ‘CLIENT’ | . | Weiterleitungsmodus | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Knoteninfo Übertragungsintervall | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Doppelklick als Taste | Treat a double tap as a button press | Deaktiviert | . | Dreifachklick für Ping | Send an ad-hoc position ping on a triple click | Aktiviert | . | Puls LED | Blink the status LED periodically | Aktiviert | . | Zeitzone | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRa Einstellungen . On Settings → LoRa. | Einstellung | Beschreibung | Standardwert | . | Region | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Voreinstellungen | Speed/range tradeoff | LongFast | . | Anzahl der Weiterleitungen | Maximum retransmit hops | 3 | . | Sendeleistung | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequenz überschreiben | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Voreinstellung verwenden | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Spreizfaktor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Fehlerkorrektur | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Bandbreite | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Frequenzschlitz | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Senden aktiviert | Turning this off makes the node receive-only | On | . | Duty-Cycle überschreiben | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Aus | . | MQTT ignorieren | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | OK für MQTT | Allow your packets to be forwarded to MQTT by gateways | Aus | . | Empfangsverstärkung | Extra receive gain on SX126x radios; costs a little current | Aus | . | PA Fan deaktiviert | Turn off the power-amplifier fan on hardware that has one | Aus | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Bereich | Geschwindigkeit | SNR Limit | Best For | . | SHORT_TURBO | ~1 km | 21.9 kbps | −7,5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6,25 kbit/s | −10 dB | Suburban short-range; moderate building density | . | MEDIUM_FAST | ~5 km | 3,52 kbit/s | −12.5 dB | Suburban areas; moderate building density | . | MEDIUM_SLOW | ~8 km | 1,95 kbit/s | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0,34 kbit/s | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7,5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12,5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7,5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0,18 kbit/s | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | Einhaltung der EU-Vorschriften für 866/868 MHz: Verwenden Sie Lite Fast, Lite Slow, Narrow Fast oder Narrow Slow – diese sind für die EU-SRD-/868-MHz-Bänder mit geringerer Bandbreite optimiert. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Anzeigeeinstellungen . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Einstellung | Beschreibung | . | Bildschirm eingeschaltet für | How long the display stays lit before sleeping | . | Karussellintervall | How often the node cycles between screens on its own | . | Anzeigemodus | Screen layout/density used by the firmware | . | Anzeigeeinheiten | Metric or Imperial on the node’s screen | . | 12h Uhrformat verwenden | Show the node’s clock as 12-hour rather than 24-hour | . | Fette Überschrift | Draw the screen’s heading text in bold | . | Bildschirm spiegeln | Rotate the display 180° for an inverted mounting | . | OLED Typ | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Aufwachen durch Tippen oder Bewegung | Light the screen when the node is tapped or moved | . | Kompassausrichtung | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Immer nach Norden zeigen | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Standorteinstellungen . On Settings → Device configuration → Position. | Einstellung | Beschreibung | . | GPS-Chip (Hardware) Modus | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Abfrageintervall | How often the node asks its GPS for a fix | . | Übertragungsintervall | How often the position is shared with the mesh | . | Intelligente Position | Broadcast based on movement rather than purely on the clock | . | Intelligentes Intervall | With Smart Position on, the shortest gap between broadcasts | . | Intelligente Entfernung | With Smart Position on, how far you must move before broadcasting | . | Fester Standort | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Standort Optionen | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Energie Einstellungen . On Settings → Device configuration → Power. | Einstellung | Beschreibung | . | Energiesparmodus aktivieren | Let the node sleep aggressively between activity | . | Herunterfahren bei Stromausfall | Power the device down after external power disappears | . | Dauer Supertiefschlaf | How long the deepest sleep state lasts | . | Minimale Aufwachzeit | The shortest time the node stays awake once woken | . | Zeit für Warten auf Bluetooth | How long to wait for a phone to connect before sleeping | . | ADC Multiplikationsfaktor | Turn on a manual correction for battery-voltage readings | . | ADC Multiplikator Überschreibungsverhältnis | The correction factor itself, used only when the override is on | . | Akku INA_2XX I2C Adresse | Address of an external INA-series power sensor, if fitted | . Netzwerkeinstellungen . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Einstellung | Beschreibung | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Passwort | Netzwerkpasswort | . | Ethernet aktiviert | Use a wired connection on hardware that has one | . | IPv4 Modus | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP Übertragung | Share mesh traffic with other nodes over the local network | . | NTP Server | Time synchronization server | . | rsyslog Server | Remote logging server | . Bluetooth Einstellungen . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Einstellung | Beschreibung | . | Bluetooth aktiviert | Enable/disable BLE radio | . | Kopplungsmodus | Fixed PIN, Random PIN, or No PIN | . | Feste PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Sicherheitseinstellungen . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Einstellung | Beschreibung | . | Öffentlicher Schlüssel | Your node’s public key (read-only) | . | Administrativer Schlüssel | Keys permitted to administer this node remotely — up to three | . | Privater Schlüssel | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Privaten Schlüssel neu erstellen | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Serielle Konsole | Serial console over the Stream API | . | Debug-Protokoll-API aktiviert | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Verwalteter Modus | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Schlüssel sichern | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Schutzstufe | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Stunden bis zum Ablauf | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ", + "content": "Geräteeinstellungen . On Settings → Device configuration → Device. | Einstellung | Beschreibung | Standardwert | . | Geräterolle | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | ‘CLIENT’ | . | Weiterleitungsmodus | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Knoteninfo Übertragungsintervall | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Doppelklick als Taste | Treat a double tap as a button press | Deaktiviert | . | Dreifachklick für Ping | Send an ad-hoc position ping on a triple click | Aktiviert | . | Puls LED | Blink the status LED periodically | Aktiviert | . | Zeitzone | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRa Einstellungen . On Settings → LoRa. | Einstellung | Beschreibung | Standardwert | . | Region | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Voreinstellungen | Speed/range tradeoff | LongFast | . | Anzahl der Weiterleitungen | Maximum retransmit hops | 3 | . | Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) | . | Frequenz überschreiben | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Voreinstellung verwenden | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Spreizfaktor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Fehlerkorrektur | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Bandbreite | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Frequenzschlitz | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Senden aktiviert | Turning this off makes the node receive-only | On | . | Duty-Cycle überschreiben | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Aus | . | MQTT ignorieren | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | OK für MQTT | Allow your packets to be forwarded to MQTT by gateways | Aus | . | Empfangsverstärkung | Extra receive gain on SX126x radios; costs a little current | Aus | . | PA Fan deaktiviert | Turn off the power-amplifier fan on hardware that has one | Aus | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Bereich | Geschwindigkeit | SNR Limit | Best For | . | SHORT_TURBO | ~1 km | 21.9 kbps | −7,5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6,25 kbit/s | −10 dB | Suburban short-range; moderate building density | . | MEDIUM_FAST | ~5 km | 3,52 kbit/s | −12.5 dB | Suburban areas; moderate building density | . | MEDIUM_SLOW | ~8 km | 1,95 kbit/s | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0,34 kbit/s | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7,5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12,5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7,5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0,18 kbit/s | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | Einhaltung der EU-Vorschriften für 866/868 MHz: Verwenden Sie Lite Fast, Lite Slow, Narrow Fast oder Narrow Slow – diese sind für die EU-SRD-/868-MHz-Bänder mit geringerer Bandbreite optimiert. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Anzeigeeinstellungen . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Einstellung | Beschreibung | . | Bildschirm eingeschaltet für | How long the display stays lit before sleeping | . | Karussellintervall | How often the node cycles between screens on its own | . | Anzeigemodus | Screen layout/density used by the firmware | . | Anzeigeeinheiten | Metric or Imperial on the node’s screen | . | 12h Uhrformat verwenden | Show the node’s clock as 12-hour rather than 24-hour | . | Fette Überschrift | Draw the screen’s heading text in bold | . | Bildschirm spiegeln | Rotate the display 180° for an inverted mounting | . | OLED Typ | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Aufwachen durch Tippen oder Bewegung | Light the screen when the node is tapped or moved | . | Kompassausrichtung | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Immer nach Norden zeigen | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Standorteinstellungen . On Settings → Device configuration → Position. | Einstellung | Beschreibung | . | GPS-Chip (Hardware) Modus | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Abfrageintervall | How often the node asks its GPS for a fix | . | Übertragungsintervall | How often the position is shared with the mesh | . | Intelligente Position | Broadcast based on movement rather than purely on the clock | . | Intelligentes Intervall | With Smart Position on, the shortest gap between broadcasts | . | Intelligente Entfernung | With Smart Position on, how far you must move before broadcasting | . | Fester Standort | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Standort Optionen | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Energie Einstellungen . On Settings → Device configuration → Power. | Einstellung | Beschreibung | . | Energiesparmodus aktivieren | Let the node sleep aggressively between activity | . | Herunterfahren bei Stromausfall | Power the device down after external power disappears | . | Dauer Supertiefschlaf | How long the deepest sleep state lasts | . | Minimale Aufwachzeit | The shortest time the node stays awake once woken | . | Zeit für Warten auf Bluetooth | How long to wait for a phone to connect before sleeping | . | ADC Multiplikationsfaktor | Turn on a manual correction for battery-voltage readings | . | ADC Multiplikator Überschreibungsverhältnis | The correction factor itself, used only when the override is on | . | Akku INA_2XX I2C Adresse | Address of an external INA-series power sensor, if fitted | . Netzwerkeinstellungen . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Einstellung | Beschreibung | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Passwort | Netzwerkpasswort | . | Ethernet aktiviert | Use a wired connection on hardware that has one | . | IPv4 Modus | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP Übertragung | Share mesh traffic with other nodes over the local network | . | NTP Server | Time synchronization server | . | rsyslog Server | Remote logging server | . Bluetooth Einstellungen . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Einstellung | Beschreibung | . | Bluetooth aktiviert | Enable/disable BLE radio | . | Kopplungsmodus | Fixed PIN, Random PIN, or No PIN | . | Feste PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Sicherheitseinstellungen . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Einstellung | Beschreibung | . | Öffentlicher Schlüssel | Your node’s public key (read-only) | . | Administrativer Schlüssel | Keys permitted to administer this node remotely — up to three | . | Privater Schlüssel | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Privaten Schlüssel neu erstellen | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Serielle Konsole | Serial console over the Stream API | . | Debug-Protokoll-API aktiviert | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Verwalteter Modus | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Schlüssel sichern | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Schutzstufe | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Stunden bis zum Ablauf | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ", "url": "/Meshtastic-Android/main/de-rDE/user/settings-radio-user.html#einstellungen", "relUrl": "/de-rDE/user/settings-radio-user.html#einstellungen" @@ -32173,7 +32173,7 @@ },"4596": { "doc": "Settings — Radio & User", "title": "Configuration", - "content": "Device Config . On Settings → Device configuration → Device. | Setting | الوصف | Default | . | Device Role | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Rebroadcast Mode | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Node Info Broadcast Interval | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Double Tap as Button | Treat a double tap as a button press | Disabled | . | Triple Click Ad Hoc Ping | Send an ad-hoc position ping on a triple click | Enabled | . | LED Heartbeat | Blink the status LED periodically | Enabled | . | Time Zone | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRa Config . On Settings → LoRa. | Setting | الوصف | Default | . | الجهة | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Presets | Speed/range tradeoff | LongFast | . | Number of Hops | Maximum retransmit hops | 3 | . | Transmit Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Frequency Slot | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Transmit Enabled | Turning this off makes the node receive-only | On | . | Override Duty Cycle | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | . | Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | . | RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | . | PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Speed | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | الوصف | . | Screen on for | How long the display stays lit before sleeping | . | Carousel interval | How often the node cycles between screens on its own | . | Display mode | Screen layout/density used by the firmware | . | Display units | Metric or Imperial on the node’s screen | . | Use 12h clock format | Show the node’s clock as 12-hour rather than 24-hour | . | Bold Heading | Draw the screen’s heading text in bold | . | Flip screen | Rotate the display 180° for an inverted mounting | . | OLED type | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Wake on tap or motion | Light the screen when the node is tapped or moved | . | Compass orientation | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Always point north | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Position Config . On Settings → Device configuration → Position. | Setting | الوصف | . | GPS Mode (Physical Hardware) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Polling Interval | How often the node asks its GPS for a fix | . | Broadcast Interval | How often the position is shared with the mesh | . | Smart Position | Broadcast based on movement rather than purely on the clock | . | Smart Interval | With Smart Position on, the shortest gap between broadcasts | . | Smart Distance | With Smart Position on, how far you must move before broadcasting | . | Fixed Position | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Position Flags | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Power Config . On Settings → Device configuration → Power. | Setting | الوصف | . | Enable power saving mode | Let the node sleep aggressively between activity | . | Shutdown on power loss | Power the device down after external power disappears | . | Super deep sleep duration | How long the deepest sleep state lasts | . | Minimum wake time | The shortest time the node stays awake once woken | . | Wait for Bluetooth duration | How long to wait for a phone to connect before sleeping | . | ADC multiplier override | Turn on a manual correction for battery-voltage readings | . | ADC multiplier override ratio | The correction factor itself, used only when the override is on | . | Battery INA_2XX I2C address | Address of an external INA-series power sensor, if fitted | . Network Config . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | الوصف | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Password | Network password | . | Ethernet enabled | Use a wired connection on hardware that has one | . | IPv4 mode | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | NTP server | Time synchronization server | . | rsyslog server | Remote logging server | . Bluetooth Config . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | الوصف | . | Bluetooth enabled | Enable/disable BLE radio | . | Pairing mode | Fixed PIN, Random PIN, or No PIN | . | Fixed PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Security Config . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | الوصف | . | Public Key | Your node’s public key (read-only) | . | Admin Key | Keys permitted to administer this node remotely — up to three | . | Private Key | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Regenerate Private Key | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Serial console | Serial console over the Stream API | . | Debug log API enabled | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Managed Mode | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Backup Keys | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ", + "content": "Device Config . On Settings → Device configuration → Device. | Setting | الوصف | Default | . | Device Role | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Rebroadcast Mode | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Node Info Broadcast Interval | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Double Tap as Button | Treat a double tap as a button press | Disabled | . | Triple Click Ad Hoc Ping | Send an ad-hoc position ping on a triple click | Enabled | . | LED Heartbeat | Blink the status LED periodically | Enabled | . | Time Zone | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRa Config . On Settings → LoRa. | Setting | الوصف | Default | . | الجهة | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Presets | Speed/range tradeoff | LongFast | . | Number of Hops | Maximum retransmit hops | 3 | . | Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) | . | Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Frequency Slot | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Transmit Enabled | Turning this off makes the node receive-only | On | . | Override Duty Cycle | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | . | Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | . | RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | . | PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Speed | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | الوصف | . | Screen on for | How long the display stays lit before sleeping | . | Carousel interval | How often the node cycles between screens on its own | . | Display mode | Screen layout/density used by the firmware | . | Display units | Metric or Imperial on the node’s screen | . | Use 12h clock format | Show the node’s clock as 12-hour rather than 24-hour | . | Bold Heading | Draw the screen’s heading text in bold | . | Flip screen | Rotate the display 180° for an inverted mounting | . | OLED type | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Wake on tap or motion | Light the screen when the node is tapped or moved | . | Compass orientation | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Always point north | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Position Config . On Settings → Device configuration → Position. | Setting | الوصف | . | GPS Mode (Physical Hardware) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Polling Interval | How often the node asks its GPS for a fix | . | Broadcast Interval | How often the position is shared with the mesh | . | Smart Position | Broadcast based on movement rather than purely on the clock | . | Smart Interval | With Smart Position on, the shortest gap between broadcasts | . | Smart Distance | With Smart Position on, how far you must move before broadcasting | . | Fixed Position | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Position Flags | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Power Config . On Settings → Device configuration → Power. | Setting | الوصف | . | Enable power saving mode | Let the node sleep aggressively between activity | . | Shutdown on power loss | Power the device down after external power disappears | . | Super deep sleep duration | How long the deepest sleep state lasts | . | Minimum wake time | The shortest time the node stays awake once woken | . | Wait for Bluetooth duration | How long to wait for a phone to connect before sleeping | . | ADC multiplier override | Turn on a manual correction for battery-voltage readings | . | ADC multiplier override ratio | The correction factor itself, used only when the override is on | . | Battery INA_2XX I2C address | Address of an external INA-series power sensor, if fitted | . Network Config . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | الوصف | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Password | Network password | . | Ethernet enabled | Use a wired connection on hardware that has one | . | IPv4 mode | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | NTP server | Time synchronization server | . | rsyslog server | Remote logging server | . Bluetooth Config . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | الوصف | . | Bluetooth enabled | Enable/disable BLE radio | . | Pairing mode | Fixed PIN, Random PIN, or No PIN | . | Fixed PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Security Config . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | الوصف | . | Public Key | Your node’s public key (read-only) | . | Admin Key | Keys permitted to administer this node remotely — up to three | . | Private Key | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Regenerate Private Key | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Serial console | Serial console over the Stream API | . | Debug log API enabled | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Managed Mode | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Backup Keys | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ", "url": "/Meshtastic-Android/main/ar-rSA/user/settings-radio-user.html#configuration", "relUrl": "/ar-rSA/user/settings-radio-user.html#configuration" @@ -32215,7 +32215,7 @@ },"4602": { "doc": "Settings — Radio & User", "title": "Configuration", - "content": "Device Config . On Settings → Device configuration → Device. | Setting | Opis | Zadano | . | Device Role | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Rebroadcast Mode | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Node Info Broadcast Interval | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Double Tap as Button | Treat a double tap as a button press | Disabled | . | Triple Click Ad Hoc Ping | Send an ad-hoc position ping on a triple click | Enabled | . | LED Heartbeat | Blink the status LED periodically | Enabled | . | Time Zone | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRa Config . On Settings → LoRa. | Setting | Opis | Zadano | . | Regija | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Presets | Speed/range tradeoff | LongFast | . | Number of Hops | Maximum retransmit hops | 3 | . | Transmit Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Frequency Slot | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Transmit Enabled | Turning this off makes the node receive-only | On | . | Override Duty Cycle | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | . | Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | . | RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | . | PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Speed | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Opis | . | Screen on for | How long the display stays lit before sleeping | . | Carousel interval | How often the node cycles between screens on its own | . | Display mode | Screen layout/density used by the firmware | . | Display units | Metric or Imperial on the node’s screen | . | Use 12h clock format | Show the node’s clock as 12-hour rather than 24-hour | . | Bold Heading | Draw the screen’s heading text in bold | . | Flip screen | Rotate the display 180° for an inverted mounting | . | OLED type | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Wake on tap or motion | Light the screen when the node is tapped or moved | . | Compass orientation | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Always point north | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Position Config . On Settings → Device configuration → Position. | Setting | Opis | . | GPS Mode (Physical Hardware) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Polling Interval | How often the node asks its GPS for a fix | . | Broadcast Interval | How often the position is shared with the mesh | . | Smart Position | Broadcast based on movement rather than purely on the clock | . | Smart Interval | With Smart Position on, the shortest gap between broadcasts | . | Smart Distance | With Smart Position on, how far you must move before broadcasting | . | Fixed Position | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Position Flags | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Power Config . On Settings → Device configuration → Power. | Setting | Opis | . | Enable power saving mode | Let the node sleep aggressively between activity | . | Shutdown on power loss | Power the device down after external power disappears | . | Super deep sleep duration | How long the deepest sleep state lasts | . | Minimum wake time | The shortest time the node stays awake once woken | . | Wait for Bluetooth duration | How long to wait for a phone to connect before sleeping | . | ADC multiplier override | Turn on a manual correction for battery-voltage readings | . | ADC multiplier override ratio | The correction factor itself, used only when the override is on | . | Battery INA_2XX I2C address | Address of an external INA-series power sensor, if fitted | . Network Config . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Opis | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Password | Network password | . | Ethernet enabled | Use a wired connection on hardware that has one | . | IPv4 mode | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | NTP server | Time synchronization server | . | rsyslog server | Remote logging server | . Postavke Bluetootha . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Opis | . | Bluetooth enabled | Enable/disable BLE radio | . | Pairing mode | Fixed PIN, Random PIN, or No PIN | . | Fixed PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Security Config . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Opis | . | Public Key | Your node’s public key (read-only) | . | Admin Key | Keys permitted to administer this node remotely — up to three | . | Private Key | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Regenerate Private Key | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Serial console | Serial console over the Stream API | . | Debug log API enabled | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Managed Mode | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Backup Keys | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ", + "content": "Device Config . On Settings → Device configuration → Device. | Setting | Opis | Zadano | . | Device Role | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Rebroadcast Mode | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Node Info Broadcast Interval | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Double Tap as Button | Treat a double tap as a button press | Disabled | . | Triple Click Ad Hoc Ping | Send an ad-hoc position ping on a triple click | Enabled | . | LED Heartbeat | Blink the status LED periodically | Enabled | . | Time Zone | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRa Config . On Settings → LoRa. | Setting | Opis | Zadano | . | Regija | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Presets | Speed/range tradeoff | LongFast | . | Number of Hops | Maximum retransmit hops | 3 | . | Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) | . | Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Frequency Slot | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Transmit Enabled | Turning this off makes the node receive-only | On | . | Override Duty Cycle | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | . | Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | . | RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | . | PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Speed | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Opis | . | Screen on for | How long the display stays lit before sleeping | . | Carousel interval | How often the node cycles between screens on its own | . | Display mode | Screen layout/density used by the firmware | . | Display units | Metric or Imperial on the node’s screen | . | Use 12h clock format | Show the node’s clock as 12-hour rather than 24-hour | . | Bold Heading | Draw the screen’s heading text in bold | . | Flip screen | Rotate the display 180° for an inverted mounting | . | OLED type | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Wake on tap or motion | Light the screen when the node is tapped or moved | . | Compass orientation | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Always point north | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Position Config . On Settings → Device configuration → Position. | Setting | Opis | . | GPS Mode (Physical Hardware) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Polling Interval | How often the node asks its GPS for a fix | . | Broadcast Interval | How often the position is shared with the mesh | . | Smart Position | Broadcast based on movement rather than purely on the clock | . | Smart Interval | With Smart Position on, the shortest gap between broadcasts | . | Smart Distance | With Smart Position on, how far you must move before broadcasting | . | Fixed Position | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Position Flags | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Power Config . On Settings → Device configuration → Power. | Setting | Opis | . | Enable power saving mode | Let the node sleep aggressively between activity | . | Shutdown on power loss | Power the device down after external power disappears | . | Super deep sleep duration | How long the deepest sleep state lasts | . | Minimum wake time | The shortest time the node stays awake once woken | . | Wait for Bluetooth duration | How long to wait for a phone to connect before sleeping | . | ADC multiplier override | Turn on a manual correction for battery-voltage readings | . | ADC multiplier override ratio | The correction factor itself, used only when the override is on | . | Battery INA_2XX I2C address | Address of an external INA-series power sensor, if fitted | . Network Config . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Opis | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Password | Network password | . | Ethernet enabled | Use a wired connection on hardware that has one | . | IPv4 mode | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | NTP server | Time synchronization server | . | rsyslog server | Remote logging server | . Postavke Bluetootha . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Opis | . | Bluetooth enabled | Enable/disable BLE radio | . | Pairing mode | Fixed PIN, Random PIN, or No PIN | . | Fixed PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Security Config . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Opis | . | Public Key | Your node’s public key (read-only) | . | Admin Key | Keys permitted to administer this node remotely — up to three | . | Private Key | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Regenerate Private Key | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Serial console | Serial console over the Stream API | . | Debug log API enabled | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Managed Mode | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Backup Keys | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ", "url": "/Meshtastic-Android/main/hr-rHR/user/settings-radio-user.html#configuration", "relUrl": "/hr-rHR/user/settings-radio-user.html#configuration" @@ -32257,7 +32257,7 @@ },"4608": { "doc": "Settings — Radio & User", "title": "Configuração", - "content": "Configuração do Dispositivo . On Settings → Device configuration → Device. | Setting | Descrição | Predefinição | . | Device Role | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Rebroadcast Mode | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Node Info Broadcast Interval | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Double Tap as Button | Treat a double tap as a button press | Disabled | . | Triple Click Ad Hoc Ping | Send an ad-hoc position ping on a triple click | Enabled | . | LED Heartbeat | Blink the status LED periodically | Enabled | . | Time Zone | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . Configuração de LoRa . On Settings → LoRa. | Setting | Descrição | Predefinição | . | Região | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Presets | Speed/range tradeoff | LongFast | . | Number of Hops | Maximum retransmit hops | 3 | . | Transmit Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Largura de banda | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Frequency Slot | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Transmit Enabled | Turning this off makes the node receive-only | On | . | Ignorar ciclo de trabalho | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | . | Ignorar MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | . | RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | . | PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Speed | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Configuração do Ecrã . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Descrição | . | Screen on for | How long the display stays lit before sleeping | . | Carousel interval | How often the node cycles between screens on its own | . | Modo de visualização | Screen layout/density used by the firmware | . | Unidade de visualização | Metric or Imperial on the node’s screen | . | Usar formato de relógio 12h | Show the node’s clock as 12-hour rather than 24-hour | . | Bold Heading | Draw the screen’s heading text in bold | . | Inverter ecrã | Rotate the display 180° for an inverted mounting | . | OLED type | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Wake on tap or motion | Light the screen when the node is tapped or moved | . | Orientação da bússola | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Always point north | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Configuração da posição . On Settings → Device configuration → Position. | Setting | Descrição | . | GPS Mode (Physical Hardware) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Polling Interval | How often the node asks its GPS for a fix | . | Intervalo de difusão | How often the position is shared with the mesh | . | Posição Inteligente | Broadcast based on movement rather than purely on the clock | . | Smart Interval | With Smart Position on, the shortest gap between broadcasts | . | Smart Distance | With Smart Position on, how far you must move before broadcasting | . | Posição fixa | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Position Flags | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Configuração de Energia . On Settings → Device configuration → Power. | Setting | Descrição | . | Ativar modo de poupança de energia | Let the node sleep aggressively between activity | . | Shutdown on power loss | Power the device down after external power disappears | . | Super deep sleep duration | How long the deepest sleep state lasts | . | Minimum wake time | The shortest time the node stays awake once woken | . | Wait for Bluetooth duration | How long to wait for a phone to connect before sleeping | . | ADC multiplier override | Turn on a manual correction for battery-voltage readings | . | Alterar rácio do multiplicador ADC | The correction factor itself, used only when the override is on | . | Endereço I2C da bateria INA_2XX | Address of an external INA-series power sensor, if fitted | . Configuração de Rede . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Descrição | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Palavra-passe | Network password | . | Ethernet ativada | Use a wired connection on hardware that has one | . | Modo IPv4 | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | Servidor NTP | Time synchronization server | . | servidor rsyslog | Remote logging server | . Configuração de Bluetooth . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Descrição | . | Bluetooth ativado | Enable/disable BLE radio | . | Modo de emparelhamento | Fixed PIN, Random PIN, or No PIN | . | PIN fixo | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Configuração de Segurança . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Descrição | . | Chave pública | Your node’s public key (read-only) | . | Chave do Administrador | Keys permitted to administer this node remotely — up to three | . | Chave privada | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Regenerate Private Key | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Consola de série | Serial console over the Stream API | . | API de histórico de depuração ativada | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Modo Administrado | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Backup Keys | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ", + "content": "Configuração do Dispositivo . On Settings → Device configuration → Device. | Setting | Descrição | Predefinição | . | Device Role | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Rebroadcast Mode | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Node Info Broadcast Interval | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Double Tap as Button | Treat a double tap as a button press | Disabled | . | Triple Click Ad Hoc Ping | Send an ad-hoc position ping on a triple click | Enabled | . | LED Heartbeat | Blink the status LED periodically | Enabled | . | Time Zone | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . Configuração de LoRa . On Settings → LoRa. | Setting | Descrição | Predefinição | . | Região | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Presets | Speed/range tradeoff | LongFast | . | Number of Hops | Maximum retransmit hops | 3 | . | Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) | . | Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Largura de banda | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Frequency Slot | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Transmit Enabled | Turning this off makes the node receive-only | On | . | Ignorar ciclo de trabalho | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | . | Ignorar MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | . | RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | . | PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Speed | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Configuração do Ecrã . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Descrição | . | Screen on for | How long the display stays lit before sleeping | . | Carousel interval | How often the node cycles between screens on its own | . | Modo de visualização | Screen layout/density used by the firmware | . | Unidade de visualização | Metric or Imperial on the node’s screen | . | Usar formato de relógio 12h | Show the node’s clock as 12-hour rather than 24-hour | . | Bold Heading | Draw the screen’s heading text in bold | . | Inverter ecrã | Rotate the display 180° for an inverted mounting | . | OLED type | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Wake on tap or motion | Light the screen when the node is tapped or moved | . | Orientação da bússola | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Always point north | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Configuração da posição . On Settings → Device configuration → Position. | Setting | Descrição | . | GPS Mode (Physical Hardware) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Polling Interval | How often the node asks its GPS for a fix | . | Intervalo de difusão | How often the position is shared with the mesh | . | Posição Inteligente | Broadcast based on movement rather than purely on the clock | . | Smart Interval | With Smart Position on, the shortest gap between broadcasts | . | Smart Distance | With Smart Position on, how far you must move before broadcasting | . | Posição fixa | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Position Flags | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Configuração de Energia . On Settings → Device configuration → Power. | Setting | Descrição | . | Ativar modo de poupança de energia | Let the node sleep aggressively between activity | . | Shutdown on power loss | Power the device down after external power disappears | . | Super deep sleep duration | How long the deepest sleep state lasts | . | Minimum wake time | The shortest time the node stays awake once woken | . | Wait for Bluetooth duration | How long to wait for a phone to connect before sleeping | . | ADC multiplier override | Turn on a manual correction for battery-voltage readings | . | Alterar rácio do multiplicador ADC | The correction factor itself, used only when the override is on | . | Endereço I2C da bateria INA_2XX | Address of an external INA-series power sensor, if fitted | . Configuração de Rede . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Descrição | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Palavra-passe | Network password | . | Ethernet ativada | Use a wired connection on hardware that has one | . | Modo IPv4 | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | Servidor NTP | Time synchronization server | . | servidor rsyslog | Remote logging server | . Configuração de Bluetooth . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Descrição | . | Bluetooth ativado | Enable/disable BLE radio | . | Modo de emparelhamento | Fixed PIN, Random PIN, or No PIN | . | PIN fixo | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Configuração de Segurança . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Descrição | . | Chave pública | Your node’s public key (read-only) | . | Chave do Administrador | Keys permitted to administer this node remotely — up to three | . | Chave privada | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Regenerate Private Key | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Consola de série | Serial console over the Stream API | . | API de histórico de depuração ativada | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Modo Administrado | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Backup Keys | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ", "url": "/Meshtastic-Android/main/pt-rPT/user/settings-radio-user.html#configura%C3%A7%C3%A3o", "relUrl": "/pt-rPT/user/settings-radio-user.html#configuração" @@ -32299,7 +32299,7 @@ },"4614": { "doc": "Settings — Radio & User", "title": "Konfiguracja", - "content": "Konfiguracja urządzenia . On Settings → Device configuration → Device. | Setting | Opis | Domyślny | . | Rola urządzenia | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Tryb retransmisji | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Interwał transmisji informacji o węźle | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Podwójne dotknięcie jako naciśnięcie przycisku | Treat a double tap as a button press | Wyłączony | . | Triple Click Ad Hoc Ping | Send an ad-hoc position ping on a triple click | Włączony | . | LED bicia serca | Blink the status LED periodically | Włączony | . | Strefa czasowa | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . Konfiguracja LoRa . On Settings → LoRa. | Setting | Opis | Domyślny | . | Region | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Presety | Speed/range tradeoff | LongFast | . | Number of Hops | Maximum retransmit hops | 3 | . | Moc nadawania | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Użyj predefiniowanych ustawień | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Szybkość kodowania | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Pasmo | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Slot częstotliwości | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Transmisja włączona | Turning this off makes the node receive-only | On | . | Nadpisz cykl pracy | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Wyłączony | . | Zignoruj MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Ok dla MQTT | Allow your packets to be forwarded to MQTT by gateways | Wyłączony | . | RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Wyłączony | . | PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Wyłączony | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Prędkość | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Konfiguracja wyświetlacza . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Opis | . | Ekran włączony na | How long the display stays lit before sleeping | . | Interwał karuzeli | How often the node cycles between screens on its own | . | Tryb wyświetlania | Screen layout/density used by the firmware | . | Wyświetlana jednostka | Metric or Imperial on the node’s screen | . | Użyj formatu 12-godzinnego | Show the node’s clock as 12-hour rather than 24-hour | . | Pogrubiony nagłówek | Draw the screen’s heading text in bold | . | Odwróć ekran | Rotate the display 180° for an inverted mounting | . | Typ ekranu OLED | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Wybudź przy dotknięciu lub ruchu | Light the screen when the node is tapped or moved | . | Orientacja kompasu | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Zawsze wskazywać na północ | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Konfiguracja pozycjonowania . On Settings → Device configuration → Position. | Setting | Opis | . | GPS Mode (Physical Hardware) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Polling Interval | How often the node asks its GPS for a fix | . | Interwał transmisji | How often the position is shared with the mesh | . | Inteligentne Pozycjonowanie | Broadcast based on movement rather than purely on the clock | . | Smart Interval | With Smart Position on, the shortest gap between broadcasts | . | Smart Distance | With Smart Position on, how far you must move before broadcasting | . | Położenie stałe | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Flagi położenia | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Konfiguracja zarządzania energią . On Settings → Device configuration → Power. | Setting | Opis | . | Włącz tryb oszczędzania energii | Let the node sleep aggressively between activity | . | Shutdown on power loss | Power the device down after external power disappears | . | Super deep sleep duration | How long the deepest sleep state lasts | . | Minimum wake time | The shortest time the node stays awake once woken | . | Wait for Bluetooth duration | How long to wait for a phone to connect before sleeping | . | ADC multiplier override | Turn on a manual correction for battery-voltage readings | . | ADC multiplier override ratio | The correction factor itself, used only when the override is on | . | Battery INA_2XX I2C address | Address of an external INA-series power sensor, if fitted | . Konfiguracja sieci . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Opis | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Hasło | Hasło do sieci | . | Ethernet włączony | Use a wired connection on hardware that has one | . | Tryb IPv4 | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | Serwer NTP | Time synchronization server | . | Serwer rsyslog | Remote logging server | . Konfiguracja Bluetooth . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Opis | . | Bluetooth włączony | Enable/disable BLE radio | . | Tryb parowania | Fixed PIN, Random PIN, or No PIN | . | Stały PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Konfiguracja zabezpieczeń . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Opis | . | Klucz publiczny | Your node’s public key (read-only) | . | Klucz administratora | Keys permitted to administer this node remotely — up to three | . | Klucz prywatny | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Regenerate Private Key | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Serial console | Serial console over the Stream API | . | Debug log API enabled | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Managed Mode | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Klucze zapasowe | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ", + "content": "Konfiguracja urządzenia . On Settings → Device configuration → Device. | Setting | Opis | Domyślny | . | Rola urządzenia | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Tryb retransmisji | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Interwał transmisji informacji o węźle | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Podwójne dotknięcie jako naciśnięcie przycisku | Treat a double tap as a button press | Wyłączony | . | Triple Click Ad Hoc Ping | Send an ad-hoc position ping on a triple click | Włączony | . | LED bicia serca | Blink the status LED periodically | Włączony | . | Strefa czasowa | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . Konfiguracja LoRa . On Settings → LoRa. | Setting | Opis | Domyślny | . | Region | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Presety | Speed/range tradeoff | LongFast | . | Number of Hops | Maximum retransmit hops | 3 | . | Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) | . | Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Użyj predefiniowanych ustawień | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Szybkość kodowania | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Pasmo | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Slot częstotliwości | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Transmisja włączona | Turning this off makes the node receive-only | On | . | Nadpisz cykl pracy | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Wyłączony | . | Zignoruj MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Ok dla MQTT | Allow your packets to be forwarded to MQTT by gateways | Wyłączony | . | RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Wyłączony | . | PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Wyłączony | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Prędkość | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Konfiguracja wyświetlacza . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Opis | . | Ekran włączony na | How long the display stays lit before sleeping | . | Interwał karuzeli | How often the node cycles between screens on its own | . | Tryb wyświetlania | Screen layout/density used by the firmware | . | Wyświetlana jednostka | Metric or Imperial on the node’s screen | . | Użyj formatu 12-godzinnego | Show the node’s clock as 12-hour rather than 24-hour | . | Pogrubiony nagłówek | Draw the screen’s heading text in bold | . | Odwróć ekran | Rotate the display 180° for an inverted mounting | . | Typ ekranu OLED | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Wybudź przy dotknięciu lub ruchu | Light the screen when the node is tapped or moved | . | Orientacja kompasu | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Zawsze wskazywać na północ | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Konfiguracja pozycjonowania . On Settings → Device configuration → Position. | Setting | Opis | . | GPS Mode (Physical Hardware) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Polling Interval | How often the node asks its GPS for a fix | . | Interwał transmisji | How often the position is shared with the mesh | . | Inteligentne Pozycjonowanie | Broadcast based on movement rather than purely on the clock | . | Smart Interval | With Smart Position on, the shortest gap between broadcasts | . | Smart Distance | With Smart Position on, how far you must move before broadcasting | . | Położenie stałe | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Flagi położenia | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Konfiguracja zarządzania energią . On Settings → Device configuration → Power. | Setting | Opis | . | Włącz tryb oszczędzania energii | Let the node sleep aggressively between activity | . | Shutdown on power loss | Power the device down after external power disappears | . | Super deep sleep duration | How long the deepest sleep state lasts | . | Minimum wake time | The shortest time the node stays awake once woken | . | Wait for Bluetooth duration | How long to wait for a phone to connect before sleeping | . | ADC multiplier override | Turn on a manual correction for battery-voltage readings | . | ADC multiplier override ratio | The correction factor itself, used only when the override is on | . | Battery INA_2XX I2C address | Address of an external INA-series power sensor, if fitted | . Konfiguracja sieci . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Opis | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Hasło | Hasło do sieci | . | Ethernet włączony | Use a wired connection on hardware that has one | . | Tryb IPv4 | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | Serwer NTP | Time synchronization server | . | Serwer rsyslog | Remote logging server | . Konfiguracja Bluetooth . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Opis | . | Bluetooth włączony | Enable/disable BLE radio | . | Tryb parowania | Fixed PIN, Random PIN, or No PIN | . | Stały PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Konfiguracja zabezpieczeń . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Opis | . | Klucz publiczny | Your node’s public key (read-only) | . | Klucz administratora | Keys permitted to administer this node remotely — up to three | . | Klucz prywatny | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Regenerate Private Key | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Serial console | Serial console over the Stream API | . | Debug log API enabled | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Managed Mode | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Klucze zapasowe | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ", "url": "/Meshtastic-Android/main/pl-rPL/user/settings-radio-user.html#konfiguracja", "relUrl": "/pl-rPL/user/settings-radio-user.html#konfiguracja" @@ -32341,7 +32341,7 @@ },"4620": { "doc": "Settings — Radio & User", "title": "Configuration", - "content": "设备配置 . On Settings → Device configuration → Device. | Setting | 说明 | 默认 | . | 设备角色 | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | 转播模式 | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | 节点信息广播间隔 | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | 双击作为按钮 | Treat a double tap as a button press | 禁用 | . | 快速按3下 向所有节点发送紧急广播 | Send an ad-hoc position ping on a triple click | Enabled | . | LED 心跳 | Blink the status LED periodically | Enabled | . | 时区 | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRa 配置 . On Settings → LoRa. | Setting | 说明 | 默认 | . | 区域 | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | 预设 | Speed/range tradeoff | LongFast | . | 节点数 | Maximum retransmit hops | 3 | . | 发送强度 | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | 频率覆盖 | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | 使用预设 | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | 扩散因子 | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | 编码率 | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | 带宽 | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | 频率时隙 | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | 启用传输 | Turning this off makes the node receive-only | On | . | 覆盖占空比 | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | 关闭 | . | 忽略 MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | 使用MQTT | Allow your packets to be forwarded to MQTT by gateways | 关闭 | . | RX 增益 | Extra receive gain on SX126x radios; costs a little current | 关闭 | . | PA风扇已禁用 | Turn off the power-amplifier fan on hardware that has one | 关闭 | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | 速度 | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. 屏幕配置 . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | 说明 | . | 开启屏幕 | How long the display stays lit before sleeping | . | 轮播间隔 | How often the node cycles between screens on its own | . | 显示模式 | Screen layout/density used by the firmware | . | 显示单位 | Metric or Imperial on the node’s screen | . | 使用 12 小时制格式 | Show the node’s clock as 12-hour rather than 24-hour | . | 加粗标题 | Draw the screen’s heading text in bold | . | 翻转屏幕 | Rotate the display 180° for an inverted mounting | . | OLED 类型 | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | 点击或移动时唤醒屏幕 | Light the screen when the node is tapped or moved | . | 罗盘方向 | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | 总是朝北 | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . 定位配置 . On Settings → Device configuration → Position. | Setting | 说明 | . | GPS 模式 (物理硬件) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS 轮询间隔 | How often the node asks its GPS for a fix | . | 广播间隔 | How often the position is shared with the mesh | . | 智能位置 | Broadcast based on movement rather than purely on the clock | . | 自动时间间隔 | With Smart Position on, the shortest gap between broadcasts | . | 自动距离大小 | With Smart Position on, how far you must move before broadcasting | . | 固定位置 | Use a manually entered latitude, longitude and altitude instead of the GPS | . | 位置信息数据包 | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . 电源配置 . On Settings → Device configuration → Power. | Setting | 说明 | . | 启用节能模式 | Let the node sleep aggressively between activity | . | 断电时关机 | Power the device down after external power disappears | . | 深度睡眠时间 | How long the deepest sleep state lasts | . | 最小唤醒时间 | The shortest time the node stays awake once woken | . | 等待蓝牙持续时间 | How long to wait for a phone to connect before sleeping | . | ADC 倍数覆盖 | Turn on a manual correction for battery-voltage readings | . | ADC乘数修正比率 | The correction factor itself, used only when the override is on | . | 电池INA_2XX I2C 地址 | Address of an external INA-series power sensor, if fitted | . 网络配置 . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | 说明 | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | 密码 | 网络密码 | . | 启用以太网 | Use a wired connection on hardware that has one | . | IPv4模式 | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP 广播 | Share mesh traffic with other nodes over the local network | . | NTP 服务器 | Time synchronization server | . | rsyslog 服务器 | Remote logging server | . 蓝牙配置 . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | 说明 | . | 启用蓝牙 | Enable/disable BLE radio | . | 配对模式 | Fixed PIN, Random PIN, or No PIN | . | 固定PIN码 | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . 安全配置 . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | 说明 | . | 公钥 | Your node’s public key (read-only) | . | 管理员密钥 | Keys permitted to administer this node remotely — up to three | . | 私钥 | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | 重新生成私钥 | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | 串口控制 | Serial console over the Stream API | . | 启用调试日志 API | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | 管理模式 | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | 备份密钥 | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | 恢复密钥 | Write the backed-up keys back to the node (available once a backup exists) | . | 删除密钥备份 | Remove the stored key backup from this phone | . | 安全等级 | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | 剩余启动次数 | How many device boots the unlocked state survives | . | 距离失效还有多少小时 | Wall-clock lifetime of the unlocked state | . | 会话上限 (分钟) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ", + "content": "设备配置 . On Settings → Device configuration → Device. | Setting | 说明 | 默认 | . | 设备角色 | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | 转播模式 | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | 节点信息广播间隔 | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | 双击作为按钮 | Treat a double tap as a button press | 禁用 | . | 快速按3下 向所有节点发送紧急广播 | Send an ad-hoc position ping on a triple click | Enabled | . | LED 心跳 | Blink the status LED periodically | Enabled | . | 时区 | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRa 配置 . On Settings → LoRa. | Setting | 说明 | 默认 | . | 区域 | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | 预设 | Speed/range tradeoff | LongFast | . | 节点数 | Maximum retransmit hops | 3 | . | Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) | . | 频率覆盖 | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | 使用预设 | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | 扩散因子 | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | 编码率 | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | 带宽 | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | 频率时隙 | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | 启用传输 | Turning this off makes the node receive-only | On | . | 覆盖占空比 | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | 关闭 | . | 忽略 MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | 使用MQTT | Allow your packets to be forwarded to MQTT by gateways | 关闭 | . | RX 增益 | Extra receive gain on SX126x radios; costs a little current | 关闭 | . | PA风扇已禁用 | Turn off the power-amplifier fan on hardware that has one | 关闭 | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | 速度 | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. 屏幕配置 . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | 说明 | . | 开启屏幕 | How long the display stays lit before sleeping | . | 轮播间隔 | How often the node cycles between screens on its own | . | 显示模式 | Screen layout/density used by the firmware | . | 显示单位 | Metric or Imperial on the node’s screen | . | 使用 12 小时制格式 | Show the node’s clock as 12-hour rather than 24-hour | . | 加粗标题 | Draw the screen’s heading text in bold | . | 翻转屏幕 | Rotate the display 180° for an inverted mounting | . | OLED 类型 | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | 点击或移动时唤醒屏幕 | Light the screen when the node is tapped or moved | . | 罗盘方向 | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | 总是朝北 | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . 定位配置 . On Settings → Device configuration → Position. | Setting | 说明 | . | GPS 模式 (物理硬件) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS 轮询间隔 | How often the node asks its GPS for a fix | . | 广播间隔 | How often the position is shared with the mesh | . | 智能位置 | Broadcast based on movement rather than purely on the clock | . | 自动时间间隔 | With Smart Position on, the shortest gap between broadcasts | . | 自动距离大小 | With Smart Position on, how far you must move before broadcasting | . | 固定位置 | Use a manually entered latitude, longitude and altitude instead of the GPS | . | 位置信息数据包 | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . 电源配置 . On Settings → Device configuration → Power. | Setting | 说明 | . | 启用节能模式 | Let the node sleep aggressively between activity | . | 断电时关机 | Power the device down after external power disappears | . | 深度睡眠时间 | How long the deepest sleep state lasts | . | 最小唤醒时间 | The shortest time the node stays awake once woken | . | 等待蓝牙持续时间 | How long to wait for a phone to connect before sleeping | . | ADC 倍数覆盖 | Turn on a manual correction for battery-voltage readings | . | ADC乘数修正比率 | The correction factor itself, used only when the override is on | . | 电池INA_2XX I2C 地址 | Address of an external INA-series power sensor, if fitted | . 网络配置 . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | 说明 | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | 密码 | 网络密码 | . | 启用以太网 | Use a wired connection on hardware that has one | . | IPv4模式 | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP 广播 | Share mesh traffic with other nodes over the local network | . | NTP 服务器 | Time synchronization server | . | rsyslog 服务器 | Remote logging server | . 蓝牙配置 . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | 说明 | . | 启用蓝牙 | Enable/disable BLE radio | . | 配对模式 | Fixed PIN, Random PIN, or No PIN | . | 固定PIN码 | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . 安全配置 . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | 说明 | . | 公钥 | Your node’s public key (read-only) | . | 管理员密钥 | Keys permitted to administer this node remotely — up to three | . | 私钥 | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | 重新生成私钥 | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | 串口控制 | Serial console over the Stream API | . | 启用调试日志 API | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | 管理模式 | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | 备份密钥 | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | 恢复密钥 | Write the backed-up keys back to the node (available once a backup exists) | . | 删除密钥备份 | Remove the stored key backup from this phone | . | 安全等级 | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | 剩余启动次数 | How many device boots the unlocked state survives | . | 距离失效还有多少小时 | Wall-clock lifetime of the unlocked state | . | 会话上限 (分钟) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ", "url": "/Meshtastic-Android/main/zh-rCN/user/settings-radio-user.html#configuration", "relUrl": "/zh-rCN/user/settings-radio-user.html#configuration" @@ -32383,7 +32383,7 @@ },"4626": { "doc": "Settings — Radio & User", "title": "Configuration", - "content": "Device Config . On Settings → Device configuration → Device. | Setting | Përshkrimi | Default | . | Device Role | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Rebroadcast Mode | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Node Info Broadcast Interval | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Double Tap as Button | Treat a double tap as a button press | Disabled | . | Triple Click Ad Hoc Ping | Send an ad-hoc position ping on a triple click | Enabled | . | LED Heartbeat | Blink the status LED periodically | Enabled | . | Time Zone | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRa Config . On Settings → LoRa. | Setting | Përshkrimi | Default | . | Rajon | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Presets | Speed/range tradeoff | LongFast | . | Number of Hops | Maximum retransmit hops | 3 | . | Transmit Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Frequency Slot | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Transmit Enabled | Turning this off makes the node receive-only | On | . | Override Duty Cycle | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | . | Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | . | RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | . | PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Speed | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Përshkrimi | . | Screen on for | How long the display stays lit before sleeping | . | Carousel interval | How often the node cycles between screens on its own | . | Display mode | Screen layout/density used by the firmware | . | Display units | Metric or Imperial on the node’s screen | . | Use 12h clock format | Show the node’s clock as 12-hour rather than 24-hour | . | Bold Heading | Draw the screen’s heading text in bold | . | Flip screen | Rotate the display 180° for an inverted mounting | . | OLED type | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Wake on tap or motion | Light the screen when the node is tapped or moved | . | Compass orientation | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Always point north | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Position Config . On Settings → Device configuration → Position. | Setting | Përshkrimi | . | GPS Mode (Physical Hardware) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Polling Interval | How often the node asks its GPS for a fix | . | Broadcast Interval | How often the position is shared with the mesh | . | Smart Position | Broadcast based on movement rather than purely on the clock | . | Smart Interval | With Smart Position on, the shortest gap between broadcasts | . | Smart Distance | With Smart Position on, how far you must move before broadcasting | . | Fixed Position | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Position Flags | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Power Config . On Settings → Device configuration → Power. | Setting | Përshkrimi | . | Enable power saving mode | Let the node sleep aggressively between activity | . | Shutdown on power loss | Power the device down after external power disappears | . | Super deep sleep duration | How long the deepest sleep state lasts | . | Minimum wake time | The shortest time the node stays awake once woken | . | Wait for Bluetooth duration | How long to wait for a phone to connect before sleeping | . | ADC multiplier override | Turn on a manual correction for battery-voltage readings | . | ADC multiplier override ratio | The correction factor itself, used only when the override is on | . | Battery INA_2XX I2C address | Address of an external INA-series power sensor, if fitted | . Network Config . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Përshkrimi | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Password | Network password | . | Ethernet enabled | Use a wired connection on hardware that has one | . | IPv4 mode | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | NTP server | Time synchronization server | . | rsyslog server | Remote logging server | . Bluetooth Config . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Përshkrimi | . | Bluetooth enabled | Enable/disable BLE radio | . | Pairing mode | Fixed PIN, Random PIN, or No PIN | . | Fixed PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Security Config . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Përshkrimi | . | Public Key | Your node’s public key (read-only) | . | Admin Key | Keys permitted to administer this node remotely — up to three | . | Private Key | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Regenerate Private Key | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Serial console | Serial console over the Stream API | . | Debug log API enabled | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Managed Mode | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Backup Keys | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ", + "content": "Device Config . On Settings → Device configuration → Device. | Setting | Përshkrimi | Default | . | Device Role | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Rebroadcast Mode | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Node Info Broadcast Interval | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Double Tap as Button | Treat a double tap as a button press | Disabled | . | Triple Click Ad Hoc Ping | Send an ad-hoc position ping on a triple click | Enabled | . | LED Heartbeat | Blink the status LED periodically | Enabled | . | Time Zone | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRa Config . On Settings → LoRa. | Setting | Përshkrimi | Default | . | Rajon | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Presets | Speed/range tradeoff | LongFast | . | Number of Hops | Maximum retransmit hops | 3 | . | Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) | . | Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Frequency Slot | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Transmit Enabled | Turning this off makes the node receive-only | On | . | Override Duty Cycle | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | . | Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | . | RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | . | PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Speed | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Përshkrimi | . | Screen on for | How long the display stays lit before sleeping | . | Carousel interval | How often the node cycles between screens on its own | . | Display mode | Screen layout/density used by the firmware | . | Display units | Metric or Imperial on the node’s screen | . | Use 12h clock format | Show the node’s clock as 12-hour rather than 24-hour | . | Bold Heading | Draw the screen’s heading text in bold | . | Flip screen | Rotate the display 180° for an inverted mounting | . | OLED type | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Wake on tap or motion | Light the screen when the node is tapped or moved | . | Compass orientation | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Always point north | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Position Config . On Settings → Device configuration → Position. | Setting | Përshkrimi | . | GPS Mode (Physical Hardware) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Polling Interval | How often the node asks its GPS for a fix | . | Broadcast Interval | How often the position is shared with the mesh | . | Smart Position | Broadcast based on movement rather than purely on the clock | . | Smart Interval | With Smart Position on, the shortest gap between broadcasts | . | Smart Distance | With Smart Position on, how far you must move before broadcasting | . | Fixed Position | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Position Flags | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Power Config . On Settings → Device configuration → Power. | Setting | Përshkrimi | . | Enable power saving mode | Let the node sleep aggressively between activity | . | Shutdown on power loss | Power the device down after external power disappears | . | Super deep sleep duration | How long the deepest sleep state lasts | . | Minimum wake time | The shortest time the node stays awake once woken | . | Wait for Bluetooth duration | How long to wait for a phone to connect before sleeping | . | ADC multiplier override | Turn on a manual correction for battery-voltage readings | . | ADC multiplier override ratio | The correction factor itself, used only when the override is on | . | Battery INA_2XX I2C address | Address of an external INA-series power sensor, if fitted | . Network Config . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Përshkrimi | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Password | Network password | . | Ethernet enabled | Use a wired connection on hardware that has one | . | IPv4 mode | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | NTP server | Time synchronization server | . | rsyslog server | Remote logging server | . Bluetooth Config . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Përshkrimi | . | Bluetooth enabled | Enable/disable BLE radio | . | Pairing mode | Fixed PIN, Random PIN, or No PIN | . | Fixed PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Security Config . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Përshkrimi | . | Public Key | Your node’s public key (read-only) | . | Admin Key | Keys permitted to administer this node remotely — up to three | . | Private Key | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Regenerate Private Key | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Serial console | Serial console over the Stream API | . | Debug log API enabled | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Managed Mode | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Backup Keys | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ", "url": "/Meshtastic-Android/main/sq-rAL/user/settings-radio-user.html#configuration", "relUrl": "/sq-rAL/user/settings-radio-user.html#configuration" @@ -32425,7 +32425,7 @@ },"4632": { "doc": "Settings — Radio & User", "title": "設定", - "content": "設備設置 . On Settings → Device configuration → Device. | 設定 | 描述說明 | 默認 | . | 裝置角色 | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | ## Rebroadcast Mode轉發廣播模式 | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | 節點資訊廣播間隔 | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | 雙擊觸發按鈕功能 | Treat a double tap as a button press | Disabled | . | 三擊執行 Ad Hoc Ping | Send an ad-hoc position ping on a triple click | 已啟用 | . | LED 心跳指示 | Blink the status LED periodically | 已啟用 | . | 時區 | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRa規劃 . On Settings → LoRa. | 設定 | 描述說明 | 默認 | . | 地區 | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | 預設配置 | Speed/range tradeoff | LongFast | . | 中繼次數 | Maximum retransmit hops | 3 | . | 傳輸功率 | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | 手動設定頻率 | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | 使用預設值 | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | 擴頻因子 | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | 編碼率 | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | 頻寬 | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | 頻率槽 | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | 已啟用發射 | Turning this off makes the node receive-only | On | . | 覆蓋工作週期/佔空比 | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | . | 忽略 MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | 允許轉發至 MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | . | 接收增益提升 | Extra receive gain on SX126x radios; costs a little current | Off | . | 停用PA風扇 | Turn off the power-amplifier fan on hardware that has one | Off | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | 範圍 | 速度 | SNR Limit | Best For | . | 短 Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | 短 快 | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | 短 慢 | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | 中等快 | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | 中等慢 | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | 長度中等的 | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. 顯示設置 . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | 設定 | 描述說明 | . | 螢幕開啟持續時間 | How long the display stays lit before sleeping | . | 輪播間隔 | How often the node cycles between screens on its own | . | 顯示模式 | Screen layout/density used by the firmware | . | 顯示單位 | Metric or Imperial on the node’s screen | . | 使用12小時制 | Show the node’s clock as 12-hour rather than 24-hour | . | 粗體字 | Draw the screen’s heading text in bold | . | 翻轉畫面 | Rotate the display 180° for an inverted mounting | . | OLED 類型 | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | 輕觸或移動喚醒 | Light the screen when the node is tapped or moved | . | 羅盤朝向 | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | 始終指向北方 | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . 位置設定 . On Settings → Device configuration → Position. | 設定 | 描述說明 | . | GPS 模式（實體硬體） | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS 輪詢間隔 | How often the node asks its GPS for a fix | . | 廣播間隔 | How often the position is shared with the mesh | . | 智慧定位 | Broadcast based on movement rather than purely on the clock | . | 智慧間隔 | With Smart Position on, the shortest gap between broadcasts | . | 智慧距離 | With Smart Position on, how far you must move before broadcasting | . | 固定位置 | Use a manually entered latitude, longitude and altitude instead of the GPS | . | 位置旗標 | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . 電源設定 . On Settings → Device configuration → Power. | 設定 | 描述說明 | . | 啟用省電模式 | Let the node sleep aggressively between activity | . | 電源中斷時關機 | Power the device down after external power disappears | . | 超深度睡眠時長 | How long the deepest sleep state lasts | . | 最小喚醒時間 | The shortest time the node stays awake once woken | . | 藍牙等待持續時間 | How long to wait for a phone to connect before sleeping | . | ADC 校正係數 | Turn on a manual correction for battery-voltage readings | . | ADC乘數修正比率 | The correction factor itself, used only when the override is on | . | 電池 INA_2XX I2C 地址 | Address of an external INA-series power sensor, if fitted | . 網路配置 . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | 設定 | 描述說明 | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | 密碼 | 網路密碼 | . | 啟用以太網 | Use a wired connection on hardware that has one | . | 第四代IP模式 | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP 廣播 | Share mesh traffic with other nodes over the local network | . | 時間伺服器 | Time synchronization server | . | rsyslog伺服器 | Remote logging server | . 藍牙配置 . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | 設定 | 描述說明 | . | 藍牙已啟用 | Enable/disable BLE radio | . | 配對模式 | Fixed PIN, Random PIN, or No PIN | . | 固定 PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . 安全性設定 . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | 設定 | 描述說明 | . | 公鑰 | Your node’s public key (read-only) | . | 管理金鑰 | Keys permitted to administer this node remotely — up to three | . | 私鑰 | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | 重新產生私鑰 | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | 序列控制台 | Serial console over the Stream API | . | 啟用除錯日誌 API | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | 管理模式 | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | 備份金鑰 | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ", + "content": "設備設置 . On Settings → Device configuration → Device. | 設定 | 描述說明 | 默認 | . | 裝置角色 | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | ## Rebroadcast Mode轉發廣播模式 | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | 節點資訊廣播間隔 | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | 雙擊觸發按鈕功能 | Treat a double tap as a button press | Disabled | . | 三擊執行 Ad Hoc Ping | Send an ad-hoc position ping on a triple click | 已啟用 | . | LED 心跳指示 | Blink the status LED periodically | 已啟用 | . | 時區 | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRa規劃 . On Settings → LoRa. | 設定 | 描述說明 | 默認 | . | 地區 | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | 預設配置 | Speed/range tradeoff | LongFast | . | 中繼次數 | Maximum retransmit hops | 3 | . | Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) | . | 手動設定頻率 | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | 使用預設值 | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | 擴頻因子 | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | 編碼率 | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | 頻寬 | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | 頻率槽 | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | 已啟用發射 | Turning this off makes the node receive-only | On | . | 覆蓋工作週期/佔空比 | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | . | 忽略 MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | 允許轉發至 MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | . | 接收增益提升 | Extra receive gain on SX126x radios; costs a little current | Off | . | 停用PA風扇 | Turn off the power-amplifier fan on hardware that has one | Off | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | 範圍 | 速度 | SNR Limit | Best For | . | 短 Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | 短 快 | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | 短 慢 | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | 中等快 | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | 中等慢 | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | 長度中等的 | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. 顯示設置 . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | 設定 | 描述說明 | . | 螢幕開啟持續時間 | How long the display stays lit before sleeping | . | 輪播間隔 | How often the node cycles between screens on its own | . | 顯示模式 | Screen layout/density used by the firmware | . | 顯示單位 | Metric or Imperial on the node’s screen | . | 使用12小時制 | Show the node’s clock as 12-hour rather than 24-hour | . | 粗體字 | Draw the screen’s heading text in bold | . | 翻轉畫面 | Rotate the display 180° for an inverted mounting | . | OLED 類型 | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | 輕觸或移動喚醒 | Light the screen when the node is tapped or moved | . | 羅盤朝向 | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | 始終指向北方 | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . 位置設定 . On Settings → Device configuration → Position. | 設定 | 描述說明 | . | GPS 模式（實體硬體） | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS 輪詢間隔 | How often the node asks its GPS for a fix | . | 廣播間隔 | How often the position is shared with the mesh | . | 智慧定位 | Broadcast based on movement rather than purely on the clock | . | 智慧間隔 | With Smart Position on, the shortest gap between broadcasts | . | 智慧距離 | With Smart Position on, how far you must move before broadcasting | . | 固定位置 | Use a manually entered latitude, longitude and altitude instead of the GPS | . | 位置旗標 | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . 電源設定 . On Settings → Device configuration → Power. | 設定 | 描述說明 | . | 啟用省電模式 | Let the node sleep aggressively between activity | . | 電源中斷時關機 | Power the device down after external power disappears | . | 超深度睡眠時長 | How long the deepest sleep state lasts | . | 最小喚醒時間 | The shortest time the node stays awake once woken | . | 藍牙等待持續時間 | How long to wait for a phone to connect before sleeping | . | ADC 校正係數 | Turn on a manual correction for battery-voltage readings | . | ADC乘數修正比率 | The correction factor itself, used only when the override is on | . | 電池 INA_2XX I2C 地址 | Address of an external INA-series power sensor, if fitted | . 網路配置 . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | 設定 | 描述說明 | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | 密碼 | 網路密碼 | . | 啟用以太網 | Use a wired connection on hardware that has one | . | 第四代IP模式 | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP 廣播 | Share mesh traffic with other nodes over the local network | . | 時間伺服器 | Time synchronization server | . | rsyslog伺服器 | Remote logging server | . 藍牙配置 . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | 設定 | 描述說明 | . | 藍牙已啟用 | Enable/disable BLE radio | . | 配對模式 | Fixed PIN, Random PIN, or No PIN | . | 固定 PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . 安全性設定 . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | 設定 | 描述說明 | . | 公鑰 | Your node’s public key (read-only) | . | 管理金鑰 | Keys permitted to administer this node remotely — up to three | . | 私鑰 | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | 重新產生私鑰 | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | 序列控制台 | Serial console over the Stream API | . | 啟用除錯日誌 API | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | 管理模式 | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | 備份金鑰 | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ", "url": "/Meshtastic-Android/main/zh-rTW/user/settings-radio-user.html#%E8%A8%AD%E5%AE%9A", "relUrl": "/zh-rTW/user/settings-radio-user.html#設定" @@ -32467,7 +32467,7 @@ },"4638": { "doc": "Seaded — raadio ja kasutaja", "title": "Sätted", - "content": "Seadme sätted . On Settings → Device configuration → Device. | Sätted | Kirjeldus | Vaikimisi | . | Seadme roll | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Kordusülekannete režiim | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Sõlme teabe edastamise intervall | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Topeltpuudutus nupuna | Treat a double tap as a button press | Keelatud | . | Kolmekordne klõps Ad Hoc Ping | Send an ad-hoc position ping on a triple click | Lubatud | . | Südamelöögi LED | Blink the status LED periodically | Lubatud | . | Ajavöönd | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRa sätted . On Settings → LoRa. | Sätted | Kirjeldus | Vaikimisi | . | Regioon | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Määramata (tuleb seadistada) | . | Eelseadistused | Speed/range tradeoff | LongFast | . | Hüpete arv | Maks uuesti saadetud hüpet | 3 | . | Saatevõimsus | Transmission power (dBm); 0 = max allowed for region | 0 (regiooni maks) | . | Tühista sagedus | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Kasuta eelseadistust | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Levitustegur | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Kodeerimiskiirus | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Ribalaius | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Sageduspesa | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Edastus lubatud | Turning this off makes the node receive-only | On | . | Töötsükli tühistamine | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Väljas | . | Keela MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Ok MQTTi | Allow your packets to be forwarded to MQTT by gateways | Väljas | . | RX võimendatud võimendus | Extra receive gain on SX126x radios; costs a little current | Väljas | . | PA ventilaator keelatud | Turn off the power-amplifier fan on hardware that has one | Väljas | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. Lisateabe saamiseks vaadake regiooni seadistamise juhendit aadressil meshtastic.org. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Vihje: SNR-i piirväärtused on meelega negatiivsed. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Kiirus | SNR limiit | Parim | . | Short Turbo | ~1 km | 21,9 kbps | −7,5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10,9 kbps | −7,5 dB | Linnaosad; hooned mõne kvartali raadiuses | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Äärelinna lühimaa; mõõdukas hoonestustihedus | . | Medium Fast | ~5 km | 3.52 kbps | −12,5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17,5 dB | Sarnane ulatus kui Pikk Kauge, aga 500 kHz ribalaiusega; kiirem läbilaskevõime | . | Long Fast | ~10 km | 1,1 kbps | −17,5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0,34 kbps | −17,5 dB | Maapiirkond, mõningase maastikuga; aeg-ajalt kasutatav | . | Lite Fast | ~5 km | 1.76 kbps | −12,5 dB | EL 866 MHz SRD sagedusala (125 kHz ribalaius); võrreldav Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EL 866 MHz SRD sagedusala (125 kHz ribalaius); võrreldav Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7,5 dB | EL 868 MHz sagedusala (62,5 kHz sagedusriba); väldib häireid teiste seadmetega | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EL 868 MHz sagedusala (62,5 kHz ribalaius); võrreldav Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12,5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7,5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0,18 kbps | −20 dB | ⚠️ Vananenud — endiselt valitav, kuid võidakse tulevases püsivara versioonis eemaldada | . | Very Long Slow | ~40+ km | 0,09 kbps | −20 dB | ⚠️ Vananenud — endiselt valitav, kuid võidakse tulevases püsivara versioonis eemaldada | . ℹ️ Märkus: Selles tabelis kasutatakse üldlevinud lühinimesid. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). See tähendab pikemat ulatust, aga vähem baite sekundis. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Linnavõrk (palju sõlmi, lühikesed vahemaad): Kasutage valikut Long Fast (vaikimisi) või Short Fast. Suurem kiirus tähendab väiksemat eetriaega, kui kanalit jagavad paljud sõlmed. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | Vastavus EL 866/868 MHz regulatsioonidele: Kasuta Lite Fast, Lite Slow, Narrow Fast või Narrow Slow – need on optimeeritud kitsama ribalaiusega EL SRD/868 MHz sagedusaladele. | Fikseeritud taristuühendused: Kasutage Short Turbo või Long Turbo spetsiaalsete punkt-punkti ühenduste jaoks, millel on head antennid ja otsenähtavus. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Kõrguse eelis (mäetipp, katus) suurendab märgatavalt efektiivset ulatust. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Ekraani sätted . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Sätted | Kirjeldus | . | Ekraan sisse lülitatud | How long the display stays lit before sleeping | . | Karusselli intervall | How often the node cycles between screens on its own | . | Ekraani režiim | Screen layout/density used by the firmware | . | Ekraani ühikud | Metric or Imperial on the node’s screen | . | Kasuta 12 tunni formaati | Show the node’s clock as 12-hour rather than 24-hour | . | Paks pealkiri | Draw the screen’s heading text in bold | . | Keera ekraani | Rotate the display 180° for an inverted mounting | . | OLED tüüp | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Ärata puudutusega või liigutusega | Light the screen when the node is tapped or moved | . | Kompassi suund | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Suund alati põhi | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Asukoha sätted . On Settings → Device configuration → Position. | Sätted | Kirjeldus | . | GPS-režiim (riistvara) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS-i küsimise intervall | How often the node asks its GPS for a fix | . | Levitamise inteintervall | How often the position is shared with the mesh | . | Nutikas asukoht | Broadcast based on movement rather than purely on the clock | . | Nutikas intervall | With Smart Position on, the shortest gap between broadcasts | . | Nutikas kaugus | With Smart Position on, how far you must move before broadcasting | . | Määratud asukoht | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Asukoha lipp | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Toite sätted . On Settings → Device configuration → Power. | Sätted | Kirjeldus | . | Luba energiasäästurežiim | Let the node sleep aggressively between activity | . | Väljalülitamine voolukatkestuse korral | Power the device down after external power disappears | . | Super sügava une kestus | How long the deepest sleep state lasts | . | Minimaalne ärkveloleku aeg | The shortest time the node stays awake once woken | . | Oota Bluetoothi ​​kestust | How long to wait for a phone to connect before sleeping | . | ADC kordaja tühistamine | Turn on a manual correction for battery-voltage readings | . | Asenda ADC kordistaja suhe | The correction factor itself, used only when the override is on | . | Aku INA_2XX I2C aadress | Address of an external INA-series power sensor, if fitted | . Võrgu sätted . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Sätted | Kirjeldus | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Parool | Network password | . | Ethernet lubatud | Use a wired connection on hardware that has one | . | IPv4 režiim | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP levitamine | Share mesh traffic with other nodes over the local network | . | NTP server | Time synchronization server | . | rsyslog server | Kauglogimise server | . Sinihamba sätted . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Sätted | Kirjeldus | . | Sinihammas lubatud | Enable/disable BLE radio | . | Sidumine | Määratud PIN kood, juhuslik PIN kood või PIN koodi pole | . | Fikseeritud PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Turva sätted . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Sätted | Kirjeldus | . | Avalik võti | Sinu sõlme avalik võti (kirjutuskaitstud) | . | Administraatori võti | Keys permitted to administer this node remotely — up to three | . | Salajane võti | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Loo uus privaatvõti | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin kanal lubatud | ⚠️ Eemaldatud — nüüd seadistatakse automaatselt, kui administraatori võti on määratud | . | Jadapordi konsool | Serial console over the Stream API | . | Silumislogi API lubatud | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Hallatud režiim | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Taastevõtmed | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Taasta võtmed | Kirjuta varundatud võtmed tagasi sõlme (saadaval siis, kui varukoopia on olemas) | . | Kustuta taastevõtmed | Remove the stored key backup from this phone | . | Kaitsetase | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Käivitusi alles | How many device boots the unlocked state survives | . | Tunde kuni kehtivusaja lõpuni | Wall-clock lifetime of the unlocked state | . | Seansi limiit (minutid) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ", + "content": "Seadme sätted . On Settings → Device configuration → Device. | Sätted | Kirjeldus | Vaikimisi | . | Seadme roll | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Kordusülekannete režiim | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Sõlme teabe edastamise intervall | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Topeltpuudutus nupuna | Treat a double tap as a button press | Keelatud | . | Kolmekordne klõps Ad Hoc Ping | Send an ad-hoc position ping on a triple click | Lubatud | . | Südamelöögi LED | Blink the status LED periodically | Lubatud | . | Ajavöönd | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRa sätted . On Settings → LoRa. | Sätted | Kirjeldus | Vaikimisi | . | Regioon | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Määramata (tuleb seadistada) | . | Eelseadistused | Speed/range tradeoff | LongFast | . | Hüpete arv | Maks uuesti saadetud hüpet | 3 | . | Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (regiooni maks) | . | Tühista sagedus | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Kasuta eelseadistust | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Levitustegur | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Kodeerimiskiirus | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Ribalaius | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Sageduspesa | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Edastus lubatud | Turning this off makes the node receive-only | On | . | Töötsükli tühistamine | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Väljas | . | Keela MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Ok MQTTi | Allow your packets to be forwarded to MQTT by gateways | Väljas | . | RX võimendatud võimendus | Extra receive gain on SX126x radios; costs a little current | Väljas | . | PA ventilaator keelatud | Turn off the power-amplifier fan on hardware that has one | Väljas | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. Lisateabe saamiseks vaadake regiooni seadistamise juhendit aadressil meshtastic.org. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Vihje: SNR-i piirväärtused on meelega negatiivsed. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Kiirus | SNR limiit | Parim | . | Short Turbo | ~1 km | 21,9 kbps | −7,5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10,9 kbps | −7,5 dB | Linnaosad; hooned mõne kvartali raadiuses | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Äärelinna lühimaa; mõõdukas hoonestustihedus | . | Medium Fast | ~5 km | 3.52 kbps | −12,5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17,5 dB | Sarnane ulatus kui Pikk Kauge, aga 500 kHz ribalaiusega; kiirem läbilaskevõime | . | Long Fast | ~10 km | 1,1 kbps | −17,5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0,34 kbps | −17,5 dB | Maapiirkond, mõningase maastikuga; aeg-ajalt kasutatav | . | Lite Fast | ~5 km | 1.76 kbps | −12,5 dB | EL 866 MHz SRD sagedusala (125 kHz ribalaius); võrreldav Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EL 866 MHz SRD sagedusala (125 kHz ribalaius); võrreldav Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7,5 dB | EL 868 MHz sagedusala (62,5 kHz sagedusriba); väldib häireid teiste seadmetega | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EL 868 MHz sagedusala (62,5 kHz ribalaius); võrreldav Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12,5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7,5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0,18 kbps | −20 dB | ⚠️ Vananenud — endiselt valitav, kuid võidakse tulevases püsivara versioonis eemaldada | . | Very Long Slow | ~40+ km | 0,09 kbps | −20 dB | ⚠️ Vananenud — endiselt valitav, kuid võidakse tulevases püsivara versioonis eemaldada | . ℹ️ Märkus: Selles tabelis kasutatakse üldlevinud lühinimesid. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). See tähendab pikemat ulatust, aga vähem baite sekundis. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Linnavõrk (palju sõlmi, lühikesed vahemaad): Kasutage valikut Long Fast (vaikimisi) või Short Fast. Suurem kiirus tähendab väiksemat eetriaega, kui kanalit jagavad paljud sõlmed. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | Vastavus EL 866/868 MHz regulatsioonidele: Kasuta Lite Fast, Lite Slow, Narrow Fast või Narrow Slow – need on optimeeritud kitsama ribalaiusega EL SRD/868 MHz sagedusaladele. | Fikseeritud taristuühendused: Kasutage Short Turbo või Long Turbo spetsiaalsete punkt-punkti ühenduste jaoks, millel on head antennid ja otsenähtavus. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Kõrguse eelis (mäetipp, katus) suurendab märgatavalt efektiivset ulatust. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Ekraani sätted . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Sätted | Kirjeldus | . | Ekraan sisse lülitatud | How long the display stays lit before sleeping | . | Karusselli intervall | How often the node cycles between screens on its own | . | Ekraani režiim | Screen layout/density used by the firmware | . | Ekraani ühikud | Metric or Imperial on the node’s screen | . | Kasuta 12 tunni formaati | Show the node’s clock as 12-hour rather than 24-hour | . | Paks pealkiri | Draw the screen’s heading text in bold | . | Keera ekraani | Rotate the display 180° for an inverted mounting | . | OLED tüüp | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Ärata puudutusega või liigutusega | Light the screen when the node is tapped or moved | . | Kompassi suund | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Suund alati põhi | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Asukoha sätted . On Settings → Device configuration → Position. | Sätted | Kirjeldus | . | GPS-režiim (riistvara) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS-i küsimise intervall | How often the node asks its GPS for a fix | . | Levitamise inteintervall | How often the position is shared with the mesh | . | Nutikas asukoht | Broadcast based on movement rather than purely on the clock | . | Nutikas intervall | With Smart Position on, the shortest gap between broadcasts | . | Nutikas kaugus | With Smart Position on, how far you must move before broadcasting | . | Määratud asukoht | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Asukoha lipp | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Toite sätted . On Settings → Device configuration → Power. | Sätted | Kirjeldus | . | Luba energiasäästurežiim | Let the node sleep aggressively between activity | . | Väljalülitamine voolukatkestuse korral | Power the device down after external power disappears | . | Super sügava une kestus | How long the deepest sleep state lasts | . | Minimaalne ärkveloleku aeg | The shortest time the node stays awake once woken | . | Oota Bluetoothi ​​kestust | How long to wait for a phone to connect before sleeping | . | ADC kordaja tühistamine | Turn on a manual correction for battery-voltage readings | . | Asenda ADC kordistaja suhe | The correction factor itself, used only when the override is on | . | Aku INA_2XX I2C aadress | Address of an external INA-series power sensor, if fitted | . Võrgu sätted . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Sätted | Kirjeldus | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Parool | Network password | . | Ethernet lubatud | Use a wired connection on hardware that has one | . | IPv4 režiim | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP levitamine | Share mesh traffic with other nodes over the local network | . | NTP server | Time synchronization server | . | rsyslog server | Kauglogimise server | . Sinihamba sätted . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Sätted | Kirjeldus | . | Sinihammas lubatud | Enable/disable BLE radio | . | Sidumine | Määratud PIN kood, juhuslik PIN kood või PIN koodi pole | . | Fikseeritud PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Turva sätted . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Sätted | Kirjeldus | . | Avalik võti | Sinu sõlme avalik võti (kirjutuskaitstud) | . | Administraatori võti | Keys permitted to administer this node remotely — up to three | . | Salajane võti | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Loo uus privaatvõti | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin kanal lubatud | ⚠️ Eemaldatud — nüüd seadistatakse automaatselt, kui administraatori võti on määratud | . | Jadapordi konsool | Serial console over the Stream API | . | Silumislogi API lubatud | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Hallatud režiim | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Taastevõtmed | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Taasta võtmed | Kirjuta varundatud võtmed tagasi sõlme (saadaval siis, kui varukoopia on olemas) | . | Kustuta taastevõtmed | Remove the stored key backup from this phone | . | Kaitsetase | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Käivitusi alles | How many device boots the unlocked state survives | . | Tunde kuni kehtivusaja lõpuni | Wall-clock lifetime of the unlocked state | . | Seansi limiit (minutid) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ", "url": "/Meshtastic-Android/main/et-rEE/user/settings-radio-user.html#s%C3%A4tted", "relUrl": "/et-rEE/user/settings-radio-user.html#sätted" @@ -32502,7 +32502,7 @@ },"4643": { "doc": "Settings — Radio & User", "title": "Configuration", - "content": "Configuration de l’appareil . On Settings → Device configuration → Device. | Setting | Description | Par défaut | . | Rôle de l’appareil | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Mode de réémission | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Intervalle de diffusion des infos nœud | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Double clic comme appui sur le bouton | Treat a double tap as a button press | Désactivé | . | Triple clic pour faire un ping Ad Hoc | Send an ad-hoc position ping on a triple click | Activé | . | LED de vérification de fonctionnement (heartbeat) | Blink the status LED periodically | Activé | . | Fuseau horaire | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . Configuration LoRa . On Settings → LoRa. | Setting | Description | Par défaut | . | Région | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Préréglages | Speed/range tradeoff | LongFast | . | Nombre de sauts | Maximum retransmit hops | 3 | . | Puissance d’émission | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Remplacer la fréquence | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Utiliser un préréglage | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Facteur de propagation | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Taux de codage | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Bande Passante | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Slot de fréquence | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Transmission activée | Turning this off makes the node receive-only | On | . | Autoriser le dépassement du temps d’émission autorisé par heure | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Éteint | . | Ignorer MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Transmission des paquets vers MQTT | Allow your packets to be forwarded to MQTT by gateways | Éteint | . | Gain RX Boosté | Extra receive gain on SX126x radios; costs a little current | Éteint | . | Ventilateur PA désactivé | Turn off the power-amplifier fan on hardware that has one | Éteint | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Vitesse | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Configuration de l’écran . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Description | . | Écran allumé pour | How long the display stays lit before sleeping | . | Intervalle du carrousel | How often the node cycles between screens on its own | . | Mode d’affichage | Screen layout/density used by the firmware | . | Unités d’affichage | Metric or Imperial on the node’s screen | . | Utiliser le format horaire 12h | Show the node’s clock as 12-hour rather than 24-hour | . | Titre en gras | Draw the screen’s heading text in bold | . | Inverser l’écran | Rotate the display 180° for an inverted mounting | . | Type d’OLED | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Réveil par appui ou mouvement | Light the screen when the node is tapped or moved | . | Orientation de la boussole | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Toujours pointer vers le nord | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Configuration de la position . On Settings → Device configuration → Position. | Setting | Description | . | Mode GPS (matériel physique) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | Fréquence de récupération GPS | How often the node asks its GPS for a fix | . | Intervalle de diffusion | How often the position is shared with the mesh | . | Position Intelligente | Broadcast based on movement rather than purely on the clock | . | Intervalle intelligent | With Smart Position on, the shortest gap between broadcasts | . | Distance intelligente | With Smart Position on, how far you must move before broadcasting | . | Position fixe | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Champs de position | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Configuration de l’alimentation . On Settings → Device configuration → Power. | Setting | Description | . | Activer le mode économie d’énergie | Let the node sleep aggressively between activity | . | Arrêt en cas de perte d’alimentation | Power the device down after external power disappears | . | Durée du sommeil extra profond | How long the deepest sleep state lasts | . | Durée minimale de réveil | The shortest time the node stays awake once woken | . | Durée d’attente max du Bluetooth | How long to wait for a phone to connect before sleeping | . | Remplacer le multiplicateur ADC | Turn on a manual correction for battery-voltage readings | . | Facteur de remplacement du multiplicateur ADC | The correction factor itself, used only when the override is on | . | Adresse I2C de la batterie INA_2XX | Address of an external INA-series power sensor, if fitted | . Configuration du réseau . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Description | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Mot de passe | Mot de passe du réseau | . | Ethernet activé | Use a wired connection on hardware that has one | . | Mode IPv4 | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | Serveur NTP | Time synchronization server | . | Serveur Rsyslog | Remote logging server | . Configuration Bluetooth . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Description | . | Bluetooth activé | Enable/disable BLE radio | . | Mode d’appariement | Fixed PIN, Random PIN, or No PIN | . | Code PIN fixe | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Configuration de sécurité . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Description | . | Clé publique | Your node’s public key (read-only) | . | Clé Admin | Keys permitted to administer this node remotely — up to three | . | Clé privée | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Régénérer la clé privée | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Console série | Serial console over the Stream API | . | API de journalisation de débogage activée | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Mode géré | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Sauvegarder les clés | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Heures jusqu’à expiration | Wall-clock lifetime of the unlocked state | . | Limite de sessions (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ", + "content": "Configuration de l’appareil . On Settings → Device configuration → Device. | Setting | Description | Par défaut | . | Rôle de l’appareil | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Mode de réémission | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Intervalle de diffusion des infos nœud | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Double clic comme appui sur le bouton | Treat a double tap as a button press | Désactivé | . | Triple clic pour faire un ping Ad Hoc | Send an ad-hoc position ping on a triple click | Activé | . | LED de vérification de fonctionnement (heartbeat) | Blink the status LED periodically | Activé | . | Fuseau horaire | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . Configuration LoRa . On Settings → LoRa. | Setting | Description | Par défaut | . | Région | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Préréglages | Speed/range tradeoff | LongFast | . | Nombre de sauts | Maximum retransmit hops | 3 | . | Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) | . | Remplacer la fréquence | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Utiliser un préréglage | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Facteur de propagation | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Taux de codage | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Bande Passante | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Slot de fréquence | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Transmission activée | Turning this off makes the node receive-only | On | . | Autoriser le dépassement du temps d’émission autorisé par heure | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Éteint | . | Ignorer MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Transmission des paquets vers MQTT | Allow your packets to be forwarded to MQTT by gateways | Éteint | . | Gain RX Boosté | Extra receive gain on SX126x radios; costs a little current | Éteint | . | Ventilateur PA désactivé | Turn off the power-amplifier fan on hardware that has one | Éteint | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Vitesse | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Configuration de l’écran . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Description | . | Écran allumé pour | How long the display stays lit before sleeping | . | Intervalle du carrousel | How often the node cycles between screens on its own | . | Mode d’affichage | Screen layout/density used by the firmware | . | Unités d’affichage | Metric or Imperial on the node’s screen | . | Utiliser le format horaire 12h | Show the node’s clock as 12-hour rather than 24-hour | . | Titre en gras | Draw the screen’s heading text in bold | . | Inverser l’écran | Rotate the display 180° for an inverted mounting | . | Type d’OLED | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Réveil par appui ou mouvement | Light the screen when the node is tapped or moved | . | Orientation de la boussole | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Toujours pointer vers le nord | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Configuration de la position . On Settings → Device configuration → Position. | Setting | Description | . | Mode GPS (matériel physique) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | Fréquence de récupération GPS | How often the node asks its GPS for a fix | . | Intervalle de diffusion | How often the position is shared with the mesh | . | Position Intelligente | Broadcast based on movement rather than purely on the clock | . | Intervalle intelligent | With Smart Position on, the shortest gap between broadcasts | . | Distance intelligente | With Smart Position on, how far you must move before broadcasting | . | Position fixe | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Champs de position | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Configuration de l’alimentation . On Settings → Device configuration → Power. | Setting | Description | . | Activer le mode économie d’énergie | Let the node sleep aggressively between activity | . | Arrêt en cas de perte d’alimentation | Power the device down after external power disappears | . | Durée du sommeil extra profond | How long the deepest sleep state lasts | . | Durée minimale de réveil | The shortest time the node stays awake once woken | . | Durée d’attente max du Bluetooth | How long to wait for a phone to connect before sleeping | . | Remplacer le multiplicateur ADC | Turn on a manual correction for battery-voltage readings | . | Facteur de remplacement du multiplicateur ADC | The correction factor itself, used only when the override is on | . | Adresse I2C de la batterie INA_2XX | Address of an external INA-series power sensor, if fitted | . Configuration du réseau . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Description | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Mot de passe | Mot de passe du réseau | . | Ethernet activé | Use a wired connection on hardware that has one | . | Mode IPv4 | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | Serveur NTP | Time synchronization server | . | Serveur Rsyslog | Remote logging server | . Configuration Bluetooth . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Description | . | Bluetooth activé | Enable/disable BLE radio | . | Mode d’appariement | Fixed PIN, Random PIN, or No PIN | . | Code PIN fixe | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Configuration de sécurité . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Description | . | Clé publique | Your node’s public key (read-only) | . | Clé Admin | Keys permitted to administer this node remotely — up to three | . | Clé privée | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Régénérer la clé privée | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Console série | Serial console over the Stream API | . | API de journalisation de débogage activée | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Mode géré | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Sauvegarder les clés | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Heures jusqu’à expiration | Wall-clock lifetime of the unlocked state | . | Limite de sessions (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ", "url": "/Meshtastic-Android/main/fr-rFR/user/settings-radio-user.html#configuration", "relUrl": "/fr-rFR/user/settings-radio-user.html#configuration" @@ -32544,7 +32544,7 @@ },"4649": { "doc": "Settings — Radio & User", "title": "Yapılandırma", - "content": "Cihaz Ayarı . On Settings → Device configuration → Device. | Setting | Açıklaması | Varsayılan | . | Device Role | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Rebroadcast Mode | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Node Bilgisi Yayın Aralığı | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Double Tap as Button | Treat a double tap as a button press | Disabled | . | Triple Click Ad Hoc Ping | Send an ad-hoc position ping on a triple click | Açık | . | LED Heartbeat | Blink the status LED periodically | Açık | . | Time Zone | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRa Ayarı . On Settings → LoRa. | Setting | Açıklaması | Varsayılan | . | Bölge | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Presets | Speed/range tradeoff | LongFast | . | Number of Hops | Maximum retransmit hops | 3 | . | Transmit Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Bant genişliği | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Frequency Slot | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Transmit Enabled | Turning this off makes the node receive-only | On | . | Görev Döngüsünü Geçersiz Kıl | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | . | MQTT’yi Yoksay | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | . | RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | . | PA fanı devre dışı | Turn off the power-amplifier fan on hardware that has one | Off | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Speed | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Akran Ayarı . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Açıklaması | . | Screen on for | How long the display stays lit before sleeping | . | Carousel interval | How often the node cycles between screens on its own | . | Görüntü Modu | Screen layout/density used by the firmware | . | Görüntü Birimleri | Metric or Imperial on the node’s screen | . | 12h saat formatını kullan | Show the node’s clock as 12-hour rather than 24-hour | . | Bold Heading | Draw the screen’s heading text in bold | . | Ekranı Çevir | Rotate the display 180° for an inverted mounting | . | OLED type | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Wake on tap or motion | Light the screen when the node is tapped or moved | . | Pusula yönü | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Always point north | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Konum Ayarı . On Settings → Device configuration → Position. | Setting | Açıklaması | . | GPS Mode (Physical Hardware) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Polling Interval | How often the node asks its GPS for a fix | . | Broadcast Interval | How often the position is shared with the mesh | . | Smart Position | Broadcast based on movement rather than purely on the clock | . | Smart Interval | With Smart Position on, the shortest gap between broadcasts | . | Smart Distance | With Smart Position on, how far you must move before broadcasting | . | Fixed Position | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Position Flags | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Güç Ayarı . On Settings → Device configuration → Power. | Setting | Açıklaması | . | Güç tasarrufu modunu etkinleştir | Let the node sleep aggressively between activity | . | Shutdown on power loss | Power the device down after external power disappears | . | Super deep sleep duration | How long the deepest sleep state lasts | . | Minimum wake time | The shortest time the node stays awake once woken | . | Wait for Bluetooth duration | How long to wait for a phone to connect before sleeping | . | ADC multiplier override | Turn on a manual correction for battery-voltage readings | . | ADC çarpanını geçersiz kılma oranı | The correction factor itself, used only when the override is on | . | Pilin INA_2XX I2C adresi | Address of an external INA-series power sensor, if fitted | . Ağ Ayarı . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Açıklaması | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Şifre | Ağ şifresi | . | Ethernet etkin | Use a wired connection on hardware that has one | . | IPv4 modu | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | NTP sunucusu | Time synchronization server | . | rsyslog sunucusu | Remote logging server | . Bluetooth Ayarı . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Açıklaması | . | Bluetooth Etkin | Enable/disable BLE radio | . | Eşleştirme Modu | Fixed PIN, Random PIN, or No PIN | . | Sabit PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Güvenlik Ayarı . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Açıklaması | . | Genel Anahtar | Your node’s public key (read-only) | . | Yönetici Anahtarı | Keys permitted to administer this node remotely — up to three | . | Özel Anahtar | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Regenerate Private Key | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Seri konsol | Serial console over the Stream API | . | Hata ayıklama kaydı API’si etkin | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Yönetilen Mod | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Anahtarları Yedekle | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ", + "content": "Cihaz Ayarı . On Settings → Device configuration → Device. | Setting | Açıklaması | Varsayılan | . | Device Role | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Rebroadcast Mode | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Node Bilgisi Yayın Aralığı | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Double Tap as Button | Treat a double tap as a button press | Disabled | . | Triple Click Ad Hoc Ping | Send an ad-hoc position ping on a triple click | Açık | . | LED Heartbeat | Blink the status LED periodically | Açık | . | Time Zone | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRa Ayarı . On Settings → LoRa. | Setting | Açıklaması | Varsayılan | . | Bölge | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Presets | Speed/range tradeoff | LongFast | . | Number of Hops | Maximum retransmit hops | 3 | . | Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) | . | Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Bant genişliği | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Frequency Slot | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Transmit Enabled | Turning this off makes the node receive-only | On | . | Görev Döngüsünü Geçersiz Kıl | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | . | MQTT’yi Yoksay | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | . | RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | . | PA fanı devre dışı | Turn off the power-amplifier fan on hardware that has one | Off | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Speed | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Akran Ayarı . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Açıklaması | . | Screen on for | How long the display stays lit before sleeping | . | Carousel interval | How often the node cycles between screens on its own | . | Görüntü Modu | Screen layout/density used by the firmware | . | Görüntü Birimleri | Metric or Imperial on the node’s screen | . | 12h saat formatını kullan | Show the node’s clock as 12-hour rather than 24-hour | . | Bold Heading | Draw the screen’s heading text in bold | . | Ekranı Çevir | Rotate the display 180° for an inverted mounting | . | OLED type | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Wake on tap or motion | Light the screen when the node is tapped or moved | . | Pusula yönü | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Always point north | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Konum Ayarı . On Settings → Device configuration → Position. | Setting | Açıklaması | . | GPS Mode (Physical Hardware) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Polling Interval | How often the node asks its GPS for a fix | . | Broadcast Interval | How often the position is shared with the mesh | . | Smart Position | Broadcast based on movement rather than purely on the clock | . | Smart Interval | With Smart Position on, the shortest gap between broadcasts | . | Smart Distance | With Smart Position on, how far you must move before broadcasting | . | Fixed Position | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Position Flags | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Güç Ayarı . On Settings → Device configuration → Power. | Setting | Açıklaması | . | Güç tasarrufu modunu etkinleştir | Let the node sleep aggressively between activity | . | Shutdown on power loss | Power the device down after external power disappears | . | Super deep sleep duration | How long the deepest sleep state lasts | . | Minimum wake time | The shortest time the node stays awake once woken | . | Wait for Bluetooth duration | How long to wait for a phone to connect before sleeping | . | ADC multiplier override | Turn on a manual correction for battery-voltage readings | . | ADC çarpanını geçersiz kılma oranı | The correction factor itself, used only when the override is on | . | Pilin INA_2XX I2C adresi | Address of an external INA-series power sensor, if fitted | . Ağ Ayarı . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Açıklaması | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Şifre | Ağ şifresi | . | Ethernet etkin | Use a wired connection on hardware that has one | . | IPv4 modu | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | NTP sunucusu | Time synchronization server | . | rsyslog sunucusu | Remote logging server | . Bluetooth Ayarı . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Açıklaması | . | Bluetooth Etkin | Enable/disable BLE radio | . | Eşleştirme Modu | Fixed PIN, Random PIN, or No PIN | . | Sabit PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Güvenlik Ayarı . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Açıklaması | . | Genel Anahtar | Your node’s public key (read-only) | . | Yönetici Anahtarı | Keys permitted to administer this node remotely — up to three | . | Özel Anahtar | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Regenerate Private Key | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Seri konsol | Serial console over the Stream API | . | Hata ayıklama kaydı API’si etkin | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Yönetilen Mod | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Anahtarları Yedekle | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ", "url": "/Meshtastic-Android/main/tr-rTR/user/settings-radio-user.html#yap%C4%B1land%C4%B1rma", "relUrl": "/tr-rTR/user/settings-radio-user.html#yapılandırma" @@ -32586,7 +32586,7 @@ },"4655": { "doc": "Settings — Radio & User", "title": "Configuration", - "content": "Device Config . On Settings → Device configuration → Device. | Setting | Περιγραφή | Default | . | Device Role | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Rebroadcast Mode | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Node Info Broadcast Interval | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Double Tap as Button | Treat a double tap as a button press | Disabled | . | Triple Click Ad Hoc Ping | Send an ad-hoc position ping on a triple click | Enabled | . | LED Heartbeat | Blink the status LED periodically | Enabled | . | Time Zone | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRa Config . On Settings → LoRa. | Setting | Περιγραφή | Default | . | Περιφέρεια | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Presets | Speed/range tradeoff | LongFast | . | Number of Hops | Maximum retransmit hops | 3 | . | Transmit Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Frequency Slot | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Transmit Enabled | Turning this off makes the node receive-only | On | . | Override Duty Cycle | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | . | Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | . | RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | . | PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Speed | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Περιγραφή | . | Screen on for | How long the display stays lit before sleeping | . | Carousel interval | How often the node cycles between screens on its own | . | Display mode | Screen layout/density used by the firmware | . | Display units | Metric or Imperial on the node’s screen | . | Use 12h clock format | Show the node’s clock as 12-hour rather than 24-hour | . | Bold Heading | Draw the screen’s heading text in bold | . | Flip screen | Rotate the display 180° for an inverted mounting | . | OLED type | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Wake on tap or motion | Light the screen when the node is tapped or moved | . | Compass orientation | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Always point north | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Position Config . On Settings → Device configuration → Position. | Setting | Περιγραφή | . | GPS Mode (Physical Hardware) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Polling Interval | How often the node asks its GPS for a fix | . | Broadcast Interval | How often the position is shared with the mesh | . | Smart Position | Broadcast based on movement rather than purely on the clock | . | Smart Interval | With Smart Position on, the shortest gap between broadcasts | . | Smart Distance | With Smart Position on, how far you must move before broadcasting | . | Fixed Position | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Position Flags | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Power Config . On Settings → Device configuration → Power. | Setting | Περιγραφή | . | Enable power saving mode | Let the node sleep aggressively between activity | . | Shutdown on power loss | Power the device down after external power disappears | . | Super deep sleep duration | How long the deepest sleep state lasts | . | Minimum wake time | The shortest time the node stays awake once woken | . | Wait for Bluetooth duration | How long to wait for a phone to connect before sleeping | . | ADC multiplier override | Turn on a manual correction for battery-voltage readings | . | ADC multiplier override ratio | The correction factor itself, used only when the override is on | . | Battery INA_2XX I2C address | Address of an external INA-series power sensor, if fitted | . Network Config . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Περιγραφή | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Κωδικός πρόσβασης | Network password | . | Ethernet enabled | Use a wired connection on hardware that has one | . | IPv4 mode | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | NTP server | Time synchronization server | . | rsyslog server | Remote logging server | . Ρυθμίσεις Bluetooth . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Περιγραφή | . | Bluetooth enabled | Enable/disable BLE radio | . | Pairing mode | Fixed PIN, Random PIN, or No PIN | . | Fixed PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Security Config . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Περιγραφή | . | Δημόσιο Κλειδί | Your node’s public key (read-only) | . | Admin Key | Keys permitted to administer this node remotely — up to three | . | Ιδιωτικό Κλειδί | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Regenerate Private Key | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Serial console | Serial console over the Stream API | . | Debug log API enabled | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Managed Mode | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Backup Keys | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ", + "content": "Device Config . On Settings → Device configuration → Device. | Setting | Περιγραφή | Default | . | Device Role | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Rebroadcast Mode | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Node Info Broadcast Interval | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Double Tap as Button | Treat a double tap as a button press | Disabled | . | Triple Click Ad Hoc Ping | Send an ad-hoc position ping on a triple click | Enabled | . | LED Heartbeat | Blink the status LED periodically | Enabled | . | Time Zone | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRa Config . On Settings → LoRa. | Setting | Περιγραφή | Default | . | Περιφέρεια | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Presets | Speed/range tradeoff | LongFast | . | Number of Hops | Maximum retransmit hops | 3 | . | Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) | . | Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Frequency Slot | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Transmit Enabled | Turning this off makes the node receive-only | On | . | Override Duty Cycle | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | . | Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | . | RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | . | PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Speed | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Περιγραφή | . | Screen on for | How long the display stays lit before sleeping | . | Carousel interval | How often the node cycles between screens on its own | . | Display mode | Screen layout/density used by the firmware | . | Display units | Metric or Imperial on the node’s screen | . | Use 12h clock format | Show the node’s clock as 12-hour rather than 24-hour | . | Bold Heading | Draw the screen’s heading text in bold | . | Flip screen | Rotate the display 180° for an inverted mounting | . | OLED type | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Wake on tap or motion | Light the screen when the node is tapped or moved | . | Compass orientation | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Always point north | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Position Config . On Settings → Device configuration → Position. | Setting | Περιγραφή | . | GPS Mode (Physical Hardware) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Polling Interval | How often the node asks its GPS for a fix | . | Broadcast Interval | How often the position is shared with the mesh | . | Smart Position | Broadcast based on movement rather than purely on the clock | . | Smart Interval | With Smart Position on, the shortest gap between broadcasts | . | Smart Distance | With Smart Position on, how far you must move before broadcasting | . | Fixed Position | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Position Flags | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Power Config . On Settings → Device configuration → Power. | Setting | Περιγραφή | . | Enable power saving mode | Let the node sleep aggressively between activity | . | Shutdown on power loss | Power the device down after external power disappears | . | Super deep sleep duration | How long the deepest sleep state lasts | . | Minimum wake time | The shortest time the node stays awake once woken | . | Wait for Bluetooth duration | How long to wait for a phone to connect before sleeping | . | ADC multiplier override | Turn on a manual correction for battery-voltage readings | . | ADC multiplier override ratio | The correction factor itself, used only when the override is on | . | Battery INA_2XX I2C address | Address of an external INA-series power sensor, if fitted | . Network Config . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Περιγραφή | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Κωδικός πρόσβασης | Network password | . | Ethernet enabled | Use a wired connection on hardware that has one | . | IPv4 mode | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | NTP server | Time synchronization server | . | rsyslog server | Remote logging server | . Ρυθμίσεις Bluetooth . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Περιγραφή | . | Bluetooth enabled | Enable/disable BLE radio | . | Pairing mode | Fixed PIN, Random PIN, or No PIN | . | Fixed PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Security Config . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Περιγραφή | . | Δημόσιο Κλειδί | Your node’s public key (read-only) | . | Admin Key | Keys permitted to administer this node remotely — up to three | . | Ιδιωτικό Κλειδί | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Regenerate Private Key | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Serial console | Serial console over the Stream API | . | Debug log API enabled | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Managed Mode | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Backup Keys | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ", "url": "/Meshtastic-Android/main/el-rGR/user/settings-radio-user.html#configuration", "relUrl": "/el-rGR/user/settings-radio-user.html#configuration" @@ -32628,7 +32628,7 @@ },"4661": { "doc": "Settings — Radio & User", "title": "Configuration", - "content": "Device Config . On Settings → Device configuration → Device. | Setting | Descriere | Prestabilit | . | Rolul dispozitivului | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Mod de redifuzare | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Intervalul de difuzare a informațiilor nodului | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Apăsare dublă ca buton | Treat a double tap as a button press | Disabled | . | Apăsare triplă pentru ping Ad Hoc | Send an ad-hoc position ping on a triple click | Activat | . | Puls LED | Blink the status LED periodically | Activat | . | Fus orar | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRa Config . On Settings → LoRa. | Setting | Descriere | Prestabilit | . | Regiune | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Presetări | Speed/range tradeoff | LongFast | . | Numărul de Hops | Maximum retransmit hops | 3 | . | Putere transmisie | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Suprascriere frecvență | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Utilizare presetare | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Factor de răspândire | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Rata de codificare | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Lățime bandă | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Slot pentru frecvenţă | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Transmisie activată | Turning this off makes the node receive-only | On | . | Suprascrie ciclul de obligații | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | . | Ignoră MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Acceptă MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | . | Amplificare RX amplificată | Extra receive gain on SX126x radios; costs a little current | Off | . | Ventilator PA dezactivat | Turn off the power-amplifier fan on hardware that has one | Off | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Viteza | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Descriere | . | Ecran pornit pentru | How long the display stays lit before sleeping | . | Intervalul caruselului | How often the node cycles between screens on its own | . | Mod ecran | Screen layout/density used by the firmware | . | Unități de măsură afișate | Metric or Imperial on the node’s screen | . | Utilizaţi formatul ceasului 12h | Show the node’s clock as 12-hour rather than 24-hour | . | Direcție îngroșat | Draw the screen’s heading text in bold | . | Rotire ecran | Rotate the display 180° for an inverted mounting | . | Tip OLED | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Trezire la apăsare sau mișcare | Light the screen when the node is tapped or moved | . | Orientarea busolei | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Indică mereu spre nord | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Position Config . On Settings → Device configuration → Position. | Setting | Descriere | . | Mod GPS (hardware fizic) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | Interval de actualizare GPS | How often the node asks its GPS for a fix | . | Interval de difuzare | How often the position is shared with the mesh | . | Poziție inteligentă | Broadcast based on movement rather than purely on the clock | . | Interval inteligent | With Smart Position on, the shortest gap between broadcasts | . | Distanță inteligentă | With Smart Position on, how far you must move before broadcasting | . | Poziție fixă | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Steaguri poziție | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Configurare Putere . On Settings → Device configuration → Power. | Setting | Descriere | . | Activează modul de economisire a energiei | Let the node sleep aggressively between activity | . | Închidere la pierderea de energie | Power the device down after external power disappears | . | Durată maximă de somn | How long the deepest sleep state lasts | . | Durata minimă a trezirii | The shortest time the node stays awake once woken | . | Așteptați pentru durata Bluetooth | How long to wait for a phone to connect before sleeping | . | Suprascriere multiplicator ADC | Turn on a manual correction for battery-voltage readings | . | Raportul suprascrierii multiplicatorului ADC | The correction factor itself, used only when the override is on | . | Adresa baterie INA_2XX I2C | Address of an external INA-series power sensor, if fitted | . Network Config . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Descriere | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | Numele rețelei | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Parolă | Network password | . | Ethernet activat | Use a wired connection on hardware that has one | . | Mod IPv4 | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | Server NTP | Time synchronization server | . | server rsyslog | Remote logging server | . Configurare Bluetooth . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Descriere | . | Bluetooth activat | Enable/disable BLE radio | . | Mod împerechere | Fixed PIN, Random PIN, or No PIN | . | PIN fix | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Security Config . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Descriere | . | Chei publice | Your node’s public key (read-only) | . | Cheie Administrator | Keys permitted to administer this node remotely — up to three | . | Cheia privată | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Regenerează Cheia privată | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Consolă serială | Serial console over the Stream API | . | Debug log API activat | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Mod Gestionat | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Backup Keys | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ", + "content": "Device Config . On Settings → Device configuration → Device. | Setting | Descriere | Prestabilit | . | Rolul dispozitivului | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Mod de redifuzare | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Intervalul de difuzare a informațiilor nodului | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Apăsare dublă ca buton | Treat a double tap as a button press | Disabled | . | Apăsare triplă pentru ping Ad Hoc | Send an ad-hoc position ping on a triple click | Activat | . | Puls LED | Blink the status LED periodically | Activat | . | Fus orar | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRa Config . On Settings → LoRa. | Setting | Descriere | Prestabilit | . | Regiune | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Presetări | Speed/range tradeoff | LongFast | . | Numărul de Hops | Maximum retransmit hops | 3 | . | Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) | . | Suprascriere frecvență | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Utilizare presetare | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Factor de răspândire | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Rata de codificare | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Lățime bandă | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Slot pentru frecvenţă | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Transmisie activată | Turning this off makes the node receive-only | On | . | Suprascrie ciclul de obligații | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | . | Ignoră MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Acceptă MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | . | Amplificare RX amplificată | Extra receive gain on SX126x radios; costs a little current | Off | . | Ventilator PA dezactivat | Turn off the power-amplifier fan on hardware that has one | Off | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Viteza | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Descriere | . | Ecran pornit pentru | How long the display stays lit before sleeping | . | Intervalul caruselului | How often the node cycles between screens on its own | . | Mod ecran | Screen layout/density used by the firmware | . | Unități de măsură afișate | Metric or Imperial on the node’s screen | . | Utilizaţi formatul ceasului 12h | Show the node’s clock as 12-hour rather than 24-hour | . | Direcție îngroșat | Draw the screen’s heading text in bold | . | Rotire ecran | Rotate the display 180° for an inverted mounting | . | Tip OLED | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Trezire la apăsare sau mișcare | Light the screen when the node is tapped or moved | . | Orientarea busolei | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Indică mereu spre nord | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Position Config . On Settings → Device configuration → Position. | Setting | Descriere | . | Mod GPS (hardware fizic) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | Interval de actualizare GPS | How often the node asks its GPS for a fix | . | Interval de difuzare | How often the position is shared with the mesh | . | Poziție inteligentă | Broadcast based on movement rather than purely on the clock | . | Interval inteligent | With Smart Position on, the shortest gap between broadcasts | . | Distanță inteligentă | With Smart Position on, how far you must move before broadcasting | . | Poziție fixă | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Steaguri poziție | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Configurare Putere . On Settings → Device configuration → Power. | Setting | Descriere | . | Activează modul de economisire a energiei | Let the node sleep aggressively between activity | . | Închidere la pierderea de energie | Power the device down after external power disappears | . | Durată maximă de somn | How long the deepest sleep state lasts | . | Durata minimă a trezirii | The shortest time the node stays awake once woken | . | Așteptați pentru durata Bluetooth | How long to wait for a phone to connect before sleeping | . | Suprascriere multiplicator ADC | Turn on a manual correction for battery-voltage readings | . | Raportul suprascrierii multiplicatorului ADC | The correction factor itself, used only when the override is on | . | Adresa baterie INA_2XX I2C | Address of an external INA-series power sensor, if fitted | . Network Config . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Descriere | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | Numele rețelei | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Parolă | Network password | . | Ethernet activat | Use a wired connection on hardware that has one | . | Mod IPv4 | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | Server NTP | Time synchronization server | . | server rsyslog | Remote logging server | . Configurare Bluetooth . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Descriere | . | Bluetooth activat | Enable/disable BLE radio | . | Mod împerechere | Fixed PIN, Random PIN, or No PIN | . | PIN fix | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Security Config . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Descriere | . | Chei publice | Your node’s public key (read-only) | . | Cheie Administrator | Keys permitted to administer this node remotely — up to three | . | Cheia privată | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Regenerează Cheia privată | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Consolă serială | Serial console over the Stream API | . | Debug log API activat | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Mod Gestionat | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Backup Keys | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ", "url": "/Meshtastic-Android/main/ro-rRO/user/settings-radio-user.html#configuration", "relUrl": "/ro-rRO/user/settings-radio-user.html#configuration" @@ -32670,7 +32670,7 @@ },"4667": { "doc": "Settings — Radio & User", "title": "Configuration", - "content": "Device Config . On Settings → Device configuration → Device. | Setting | תיאור | Default | . | Device Role | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Rebroadcast Mode | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Node Info Broadcast Interval | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Double Tap as Button | Treat a double tap as a button press | Disabled | . | Triple Click Ad Hoc Ping | Send an ad-hoc position ping on a triple click | Enabled | . | LED Heartbeat | Blink the status LED periodically | Enabled | . | Time Zone | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRa Config . On Settings → LoRa. | Setting | תיאור | Default | . | אזור | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Presets | Speed/range tradeoff | LongFast | . | Number of Hops | Maximum retransmit hops | 3 | . | Transmit Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Frequency Slot | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Transmit Enabled | Turning this off makes the node receive-only | On | . | Override Duty Cycle | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | . | Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | . | RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | . | PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Speed | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | תיאור | . | Screen on for | How long the display stays lit before sleeping | . | Carousel interval | How often the node cycles between screens on its own | . | Display mode | Screen layout/density used by the firmware | . | Display units | Metric or Imperial on the node’s screen | . | Use 12h clock format | Show the node’s clock as 12-hour rather than 24-hour | . | Bold Heading | Draw the screen’s heading text in bold | . | Flip screen | Rotate the display 180° for an inverted mounting | . | OLED type | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Wake on tap or motion | Light the screen when the node is tapped or moved | . | Compass orientation | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Always point north | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Position Config . On Settings → Device configuration → Position. | Setting | תיאור | . | GPS Mode (Physical Hardware) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Polling Interval | How often the node asks its GPS for a fix | . | Broadcast Interval | How often the position is shared with the mesh | . | Smart Position | Broadcast based on movement rather than purely on the clock | . | Smart Interval | With Smart Position on, the shortest gap between broadcasts | . | Smart Distance | With Smart Position on, how far you must move before broadcasting | . | Fixed Position | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Position Flags | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Power Config . On Settings → Device configuration → Power. | Setting | תיאור | . | Enable power saving mode | Let the node sleep aggressively between activity | . | Shutdown on power loss | Power the device down after external power disappears | . | Super deep sleep duration | How long the deepest sleep state lasts | . | Minimum wake time | The shortest time the node stays awake once woken | . | Wait for Bluetooth duration | How long to wait for a phone to connect before sleeping | . | ADC multiplier override | Turn on a manual correction for battery-voltage readings | . | ADC multiplier override ratio | The correction factor itself, used only when the override is on | . | Battery INA_2XX I2C address | Address of an external INA-series power sensor, if fitted | . Network Config . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | תיאור | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Password | Network password | . | Ethernet enabled | Use a wired connection on hardware that has one | . | IPv4 mode | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | NTP server | Time synchronization server | . | rsyslog server | Remote logging server | . Bluetooth Config . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | תיאור | . | Bluetooth enabled | Enable/disable BLE radio | . | Pairing mode | Fixed PIN, Random PIN, or No PIN | . | Fixed PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Security Config . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | תיאור | . | Public Key | Your node’s public key (read-only) | . | Admin Key | Keys permitted to administer this node remotely — up to three | . | Private Key | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Regenerate Private Key | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Serial console | Serial console over the Stream API | . | Debug log API enabled | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Managed Mode | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Backup Keys | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ", + "content": "Device Config . On Settings → Device configuration → Device. | Setting | תיאור | Default | . | Device Role | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Rebroadcast Mode | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Node Info Broadcast Interval | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Double Tap as Button | Treat a double tap as a button press | Disabled | . | Triple Click Ad Hoc Ping | Send an ad-hoc position ping on a triple click | Enabled | . | LED Heartbeat | Blink the status LED periodically | Enabled | . | Time Zone | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRa Config . On Settings → LoRa. | Setting | תיאור | Default | . | אזור | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Presets | Speed/range tradeoff | LongFast | . | Number of Hops | Maximum retransmit hops | 3 | . | Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) | . | Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Frequency Slot | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Transmit Enabled | Turning this off makes the node receive-only | On | . | Override Duty Cycle | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | . | Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | . | RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | . | PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Speed | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | תיאור | . | Screen on for | How long the display stays lit before sleeping | . | Carousel interval | How often the node cycles between screens on its own | . | Display mode | Screen layout/density used by the firmware | . | Display units | Metric or Imperial on the node’s screen | . | Use 12h clock format | Show the node’s clock as 12-hour rather than 24-hour | . | Bold Heading | Draw the screen’s heading text in bold | . | Flip screen | Rotate the display 180° for an inverted mounting | . | OLED type | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Wake on tap or motion | Light the screen when the node is tapped or moved | . | Compass orientation | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Always point north | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Position Config . On Settings → Device configuration → Position. | Setting | תיאור | . | GPS Mode (Physical Hardware) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Polling Interval | How often the node asks its GPS for a fix | . | Broadcast Interval | How often the position is shared with the mesh | . | Smart Position | Broadcast based on movement rather than purely on the clock | . | Smart Interval | With Smart Position on, the shortest gap between broadcasts | . | Smart Distance | With Smart Position on, how far you must move before broadcasting | . | Fixed Position | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Position Flags | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Power Config . On Settings → Device configuration → Power. | Setting | תיאור | . | Enable power saving mode | Let the node sleep aggressively between activity | . | Shutdown on power loss | Power the device down after external power disappears | . | Super deep sleep duration | How long the deepest sleep state lasts | . | Minimum wake time | The shortest time the node stays awake once woken | . | Wait for Bluetooth duration | How long to wait for a phone to connect before sleeping | . | ADC multiplier override | Turn on a manual correction for battery-voltage readings | . | ADC multiplier override ratio | The correction factor itself, used only when the override is on | . | Battery INA_2XX I2C address | Address of an external INA-series power sensor, if fitted | . Network Config . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | תיאור | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Password | Network password | . | Ethernet enabled | Use a wired connection on hardware that has one | . | IPv4 mode | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | NTP server | Time synchronization server | . | rsyslog server | Remote logging server | . Bluetooth Config . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | תיאור | . | Bluetooth enabled | Enable/disable BLE radio | . | Pairing mode | Fixed PIN, Random PIN, or No PIN | . | Fixed PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Security Config . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | תיאור | . | Public Key | Your node’s public key (read-only) | . | Admin Key | Keys permitted to administer this node remotely — up to three | . | Private Key | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Regenerate Private Key | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Serial console | Serial console over the Stream API | . | Debug log API enabled | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Managed Mode | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Backup Keys | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ", "url": "/Meshtastic-Android/main/iw-rIL/user/settings-radio-user.html#configuration", "relUrl": "/iw-rIL/user/settings-radio-user.html#configuration" @@ -32712,7 +32712,7 @@ },"4673": { "doc": "Settings — Radio & User", "title": "Configuration", - "content": "Configuração do Dispositivo . On Settings → Device configuration → Device. | Setting | Descrição | Padrão | . | Device Role | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Rebroadcast Mode | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Node Info Broadcast Interval | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Double Tap as Button | Treat a double tap as a button press | Disabled | . | Triple Click Ad Hoc Ping | Send an ad-hoc position ping on a triple click | Enabled | . | LED Heartbeat | Blink the status LED periodically | Enabled | . | Time Zone | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . Configuração do LoRa . On Settings → LoRa. | Setting | Descrição | Padrão | . | Região | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Presets | Speed/range tradeoff | LongFast | . | Number of Hops | Maximum retransmit hops | 3 | . | Transmit Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Largura da banda | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Frequency Slot | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Transmit Enabled | Turning this off makes the node receive-only | On | . | Ignorar ciclo de trabalho | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | . | Ignorar MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | . | RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | . | Ventilador do PA desativado | Turn off the power-amplifier fan on hardware that has one | Off | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Velocidade | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Configuração da Tela . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Descrição | . | Screen on for | How long the display stays lit before sleeping | . | Carousel interval | How often the node cycles between screens on its own | . | Modo da tela | Screen layout/density used by the firmware | . | Unidades de exibição | Metric or Imperial on the node’s screen | . | Usar formato de relógio 12h | Show the node’s clock as 12-hour rather than 24-hour | . | Bold Heading | Draw the screen’s heading text in bold | . | Inverter tela | Rotate the display 180° for an inverted mounting | . | OLED type | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Wake on tap or motion | Light the screen when the node is tapped or moved | . | Orientação da bússola | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Always point north | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Configuração da Posição . On Settings → Device configuration → Position. | Setting | Descrição | . | GPS Mode (Physical Hardware) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Polling Interval | How often the node asks its GPS for a fix | . | Broadcast Interval | How often the position is shared with the mesh | . | Smart Position | Broadcast based on movement rather than purely on the clock | . | Smart Interval | With Smart Position on, the shortest gap between broadcasts | . | Smart Distance | With Smart Position on, how far you must move before broadcasting | . | Fixed Position | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Position Flags | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Configuração de Energia . On Settings → Device configuration → Power. | Setting | Descrição | . | Ativar modo de economia de energia | Let the node sleep aggressively between activity | . | Shutdown on power loss | Power the device down after external power disappears | . | Super deep sleep duration | How long the deepest sleep state lasts | . | Minimum wake time | The shortest time the node stays awake once woken | . | Wait for Bluetooth duration | How long to wait for a phone to connect before sleeping | . | ADC multiplier override | Turn on a manual correction for battery-voltage readings | . | Alterar proporção do multiplicador ADC | The correction factor itself, used only when the override is on | . | Endereço I2C da bateria INA_2XX | Address of an external INA-series power sensor, if fitted | . Configuração de Rede . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Descrição | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Senha | Network password | . | Ethernet ativado | Use a wired connection on hardware that has one | . | Modo IPv4 | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | Servidor NTP | Time synchronization server | . | Servidor rsyslog | Remote logging server | . Configuração do Bluetooth . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Descrição | . | Bluetooth habilitado | Enable/disable BLE radio | . | Modo de pareamento | Fixed PIN, Random PIN, or No PIN | . | PIN fixo | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Configurações de Segurança . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Descrição | . | Chave Publica | Your node’s public key (read-only) | . | Chave do Administrador | Keys permitted to administer this node remotely — up to three | . | Chave Privada | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Regenerar a chave privada | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Console serial | Serial console over the Stream API | . | API de logs de depuração ativada | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Modo Administrado | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Backup Keys | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ", + "content": "Configuração do Dispositivo . On Settings → Device configuration → Device. | Setting | Descrição | Padrão | . | Device Role | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Rebroadcast Mode | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Node Info Broadcast Interval | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Double Tap as Button | Treat a double tap as a button press | Disabled | . | Triple Click Ad Hoc Ping | Send an ad-hoc position ping on a triple click | Enabled | . | LED Heartbeat | Blink the status LED periodically | Enabled | . | Time Zone | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . Configuração do LoRa . On Settings → LoRa. | Setting | Descrição | Padrão | . | Região | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Presets | Speed/range tradeoff | LongFast | . | Number of Hops | Maximum retransmit hops | 3 | . | Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) | . | Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Largura da banda | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Frequency Slot | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Transmit Enabled | Turning this off makes the node receive-only | On | . | Ignorar ciclo de trabalho | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | . | Ignorar MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | . | RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | . | Ventilador do PA desativado | Turn off the power-amplifier fan on hardware that has one | Off | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Velocidade | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Configuração da Tela . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Descrição | . | Screen on for | How long the display stays lit before sleeping | . | Carousel interval | How often the node cycles between screens on its own | . | Modo da tela | Screen layout/density used by the firmware | . | Unidades de exibição | Metric or Imperial on the node’s screen | . | Usar formato de relógio 12h | Show the node’s clock as 12-hour rather than 24-hour | . | Bold Heading | Draw the screen’s heading text in bold | . | Inverter tela | Rotate the display 180° for an inverted mounting | . | OLED type | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Wake on tap or motion | Light the screen when the node is tapped or moved | . | Orientação da bússola | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Always point north | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Configuração da Posição . On Settings → Device configuration → Position. | Setting | Descrição | . | GPS Mode (Physical Hardware) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Polling Interval | How often the node asks its GPS for a fix | . | Broadcast Interval | How often the position is shared with the mesh | . | Smart Position | Broadcast based on movement rather than purely on the clock | . | Smart Interval | With Smart Position on, the shortest gap between broadcasts | . | Smart Distance | With Smart Position on, how far you must move before broadcasting | . | Fixed Position | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Position Flags | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Configuração de Energia . On Settings → Device configuration → Power. | Setting | Descrição | . | Ativar modo de economia de energia | Let the node sleep aggressively between activity | . | Shutdown on power loss | Power the device down after external power disappears | . | Super deep sleep duration | How long the deepest sleep state lasts | . | Minimum wake time | The shortest time the node stays awake once woken | . | Wait for Bluetooth duration | How long to wait for a phone to connect before sleeping | . | ADC multiplier override | Turn on a manual correction for battery-voltage readings | . | Alterar proporção do multiplicador ADC | The correction factor itself, used only when the override is on | . | Endereço I2C da bateria INA_2XX | Address of an external INA-series power sensor, if fitted | . Configuração de Rede . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Descrição | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Senha | Network password | . | Ethernet ativado | Use a wired connection on hardware that has one | . | Modo IPv4 | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | Servidor NTP | Time synchronization server | . | Servidor rsyslog | Remote logging server | . Configuração do Bluetooth . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Descrição | . | Bluetooth habilitado | Enable/disable BLE radio | . | Modo de pareamento | Fixed PIN, Random PIN, or No PIN | . | PIN fixo | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Configurações de Segurança . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Descrição | . | Chave Publica | Your node’s public key (read-only) | . | Chave do Administrador | Keys permitted to administer this node remotely — up to three | . | Chave Privada | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Regenerar a chave privada | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Console serial | Serial console over the Stream API | . | API de logs de depuração ativada | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Modo Administrado | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Backup Keys | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ", "url": "/Meshtastic-Android/main/pt-rBR/user/settings-radio-user.html#configuration", "relUrl": "/pt-rBR/user/settings-radio-user.html#configuration" diff --git a/main/be-rBY/user/discovery.html b/main/be-rBY/user/discovery.html index 2b940eda7e..c8605adec0 100644 --- a/main/be-rBY/user/discovery.html +++ b/main/be-rBY/user/discovery.html @@ -5,4 +5,4 @@ ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) -

Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:.

What to look for What it means
All hops show Good SNR (green) Healthy path — messages flow reliably
One hop shows a poor SNR (orange or red) Weak link — this relay segment is fragile
Many hops (4+) Long path — consider repositioning a node to shorten it
Different path on retry Mesh is adapting — multiple routes exist (this is good!)

💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network.

Troubleshooting with Traceroute

  • No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key.
  • Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa.
  • Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position.
  • Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric.

Neighbor Info

The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh.

Enabling Neighbor Info

  1. Navigate to Settings → Module configuration → Neighbor Info.
  2. Enable the module.
  3. Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
  4. Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air.

Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.

Viewing neighbor data

  • Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors.
  • Each neighbor entry shows the node that was directly heard and its signal quality.
  • Combine neighbor data from multiple nodes to understand the full mesh topology.

ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further.

Node list as a discovery tool

The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively.

Finding new nodes

  • Sort by Last heard to see the most recently active nodes at the top.
  • Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes.

Assessing connectivity

  • Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed.
  • Sort by Distance to find nearby nodes and verify they’re reachable.
  • Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge).

Infrastructure audit

  • Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes.
  • Check their signal quality and last-heard times to verify your infrastructure nodes are healthy.

See Nodes for full details on filtering and sorting options.

Tips for Mesh exploration

  • Start with traceroute — it gives you immediate, actionable information about a specific path.
  • Enable Neighbor Info on key nodes — especially routers and repeaters, to build a picture of the backbone.
  • Check the map — node positions on the Map combined with signal data help you understand why some links are strong and others are weak.
  • Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly.
+

Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:.

What to look for What it means
All hops show Good SNR (green) Healthy path — messages flow reliably
One hop shows a poor SNR (orange or red) Weak link — this relay segment is fragile
Many hops (4+) Long path — consider repositioning a node to shorten it
Different path on retry Mesh is adapting — multiple routes exist (this is good!)

💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network.

Troubleshooting with Traceroute

  • No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key.
  • Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa.
  • Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position.
  • Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric.

Neighbor Info

The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh.

Enabling Neighbor Info

  1. Navigate to Settings → Module configuration → Neighbor Info.
  2. Enable the module.
  3. Set Update Interval. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
  4. Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air.

Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.

Viewing neighbor data

  • Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors.
  • Each neighbor entry shows the node that was directly heard and its signal quality.
  • Combine neighbor data from multiple nodes to understand the full mesh topology.

ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further.

Node list as a discovery tool

The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively.

Finding new nodes

  • Sort by Last heard to see the most recently active nodes at the top.
  • Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes.

Assessing connectivity

  • Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed.
  • Sort by Distance to find nearby nodes and verify they’re reachable.
  • Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge).

Infrastructure audit

  • Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes.
  • Check their signal quality and last-heard times to verify your infrastructure nodes are healthy.

See Nodes for full details on filtering and sorting options.

Tips for Mesh exploration

  • Start with traceroute — it gives you immediate, actionable information about a specific path.
  • Enable Neighbor Info on key nodes — especially routers and repeaters, to build a picture of the backbone.
  • Check the map — node positions on the Map combined with signal data help you understand why some links are strong and others are weak.
  • Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly.
diff --git a/main/be-rBY/user/mqtt.html b/main/be-rBY/user/mqtt.html index 6fe89155d0..c8685816ec 100644 --- a/main/be-rBY/user/mqtt.html +++ b/main/be-rBY/user/mqtt.html @@ -1,2 +1,2 @@ MQTT | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Беларуская
Meshtastic Docs ↗

🌐 Беларуская — Community translation View in English

MQTT

MQTT bridges your Meshtastic mesh network to the internet, enabling long-range communication beyond radio range.

Абзор

The MQTT module connects your node to an MQTT broker, allowing:

  • Messages to reach nodes on different physical meshes via the internet
  • Integration with home automation and monitoring systems
  • Publishing node positions to the public Meshtastic map
  • Custom data pipelines for logging and alerting

How It Works 

[Your Node] → Radio → [Gateway Node with Wi-Fi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node]
-

A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh.

Конфигурация

Enabling MQTT

  1. Navigate to Settings → Module configuration → MQTT.
  2. Enable the MQTT module.
  3. Configure the broker connection:
Setting Апісанне Default
Address MQTT broker hostname mqtt.meshtastic.org
Username Broker authentication meshdev
Password Broker authentication large4cats
Root topic Base topic for messages msh, which the radio rewrites to msh/<REGION> once you set a region
Encryption enabled Encrypt MQTT payload Уключана
JSON output enabled Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it Disabled
TLS enabled Secure connection to broker Disabled
Map reporting Report position to public map Disabled
Proxy to client enabled Relay MQTT through the connected phone Disabled

Connection Status and Test Connection

The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here.

Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason.

MQTT Proxy on This Phone

If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection.

ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them.

The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration.

Default Meshtastic Broker

The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing.

When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without).

🔒 Privacy: Messages on the public broker are readable by anyone subscribed. Always use channel encryption for private communications.

Private Broker

For better privacy and control, you can run your own MQTT broker:

  • Mosquitto (lightweight, open-source)
  • HiveMQ
  • EMQX

Configure your node to point to your private broker with appropriate credentials.

Map Reporting

When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.

Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.

Reports appear at meshmap.net and similar community map services.

🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published.

Direction Апісанне
Uplink Messages from mesh → MQTT broker
Downlink Messages from MQTT broker → mesh

Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on.

Message Formats

MQTT carries two payload formats:

Format Апісанне Use case
Protobuf Binary Meshtastic protobuf encoding Node-to-node mesh bridging
JSON Human-readable JSON on the /2/json/ topic Consumers outside the mesh (dashboards, home automation)

ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads.

Encryption & Privacy

Understanding the layered encryption model:

  1. Channel encryption happens on the mesh before MQTT. If your channel has a PSK, the MQTT payload is already encrypted — the broker and any subscribers see only the ciphertext.
  2. Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard.
  3. TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping.

🔒 Security: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications.

Best Practices

  • Use channel-level encryption (PSK) on channels that bridge to MQTT
  • Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes memory)
  • Use a private broker for sensitive deployments
  • Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh
  • Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back

Troubleshooting

MQTT Not Connecting

  • Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself.
  • Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces.
  • Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443).
  • DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly.

Messages Not Bridging

  • Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway.
  • Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage.
  • Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root.
  • Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway.
  • Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in.
+

A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh.

Конфигурация

Enabling MQTT

  1. Navigate to Settings → Module configuration → MQTT.
  2. Enable the MQTT module.
  3. Configure the broker connection:
Setting Апісанне Default
Address MQTT broker hostname mqtt.meshtastic.org
Username Broker authentication meshdev
Password Broker authentication large4cats
Root topic Base topic for messages msh, which the radio rewrites to msh/<REGION> once you set a region
Encryption enabled Encrypt MQTT payload Уключана
JSON output enabled Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it Disabled
TLS enabled Secure connection to broker Disabled
Map reporting Report position to public map Disabled
Proxy to client enabled Relay MQTT through the connected phone Disabled

Connection Status and Test Connection

The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here.

Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason.

MQTT Proxy on This Phone

If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection.

ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them.

The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration.

Default Meshtastic Broker

The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing.

When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without).

🔒 Privacy: Messages on the public broker are readable by anyone subscribed. Always use channel encryption for private communications.

Private Broker

For better privacy and control, you can run your own MQTT broker:

  • Mosquitto (lightweight, open-source)
  • HiveMQ
  • EMQX

Configure your node to point to your private broker with appropriate credentials.

Map Reporting

When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.

Turning it on opens a consent card. Turn on I agree. and choose a Map Publish Interval of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.

Reports appear at meshmap.net and similar community map services.

🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published.

Direction Апісанне
Uplink Messages from mesh → MQTT broker
Downlink Messages from MQTT broker → mesh

Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on.

Message Formats

MQTT carries two payload formats:

Format Апісанне Use case
Protobuf Binary Meshtastic protobuf encoding Node-to-node mesh bridging
JSON Human-readable JSON on the /2/json/ topic Consumers outside the mesh (dashboards, home automation)

ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads.

Encryption & Privacy

Understanding the layered encryption model:

  1. Channel encryption happens on the mesh before MQTT. If your channel has a PSK, the MQTT payload is already encrypted — the broker and any subscribers see only the ciphertext.
  2. Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard.
  3. TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping.

🔒 Security: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications.

Best Practices

  • Use channel-level encryption (PSK) on channels that bridge to MQTT
  • Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes memory)
  • Use a private broker for sensitive deployments
  • Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh
  • Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back

Troubleshooting

MQTT Not Connecting

  • Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself.
  • Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces.
  • Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443).
  • DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly.

Messages Not Bridging

  • Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway.
  • Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage.
  • Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root.
  • Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway.
  • Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in.
diff --git a/main/be-rBY/user/settings-module-admin.html b/main/be-rBY/user/settings-module-admin.html index b2d1555ff8..d582353f77 100644 --- a/main/be-rBY/user/settings-module-admin.html +++ b/main/be-rBY/user/settings-module-admin.html @@ -1 +1 @@ - Settings — Modules & Admin | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Беларуская
Meshtastic Docs ↗

🌐 Беларуская — Community translation View in English

Settings — Modules & Admin

Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.

💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.

Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:

A toggle setting in the on position

A dropdown setting, expanded to show its list of options

A text field setting with a value entered

A module settings card with its title and grouped controls

Module configuration

Every module lives under Settings → Module configuration.

⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes.

MQTT module

Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.

Setting Апісанне
MQTT enabled Toggle MQTT bridge
Address MQTT broker address
Імя карыстальніка Authentication username
Пароль Authentication password
Encryption enabled Encrypt MQTT payloads
JSON output enabled Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS enabled Use secure connection
Root topic Base MQTT topic path
Proxy to client enabled Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy on this phone The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT
Map reporting Publish position to the public map — see the Map reporting group that follows

Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:

Setting Апісанне
I agree. Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map reporting interval (seconds) How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered

See MQTT for a detailed usage guide including encryption, privacy, and broker setup.

Serial module

Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.

Setting Апісанне
Serial enabled Activate serial communication
Echo enabled Echo received serial data back
Serial mode Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX GPIO pins for the serial connection
Serial baud rate Port speed
Скончыўся час чакання How long to wait before considering an incoming message complete
Override console serial port Take over the port the debug console normally uses

External Notification module

Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.

There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.

Setting Апісанне
External notification enabled Master toggle for the module
Alert message LED / buzzer / vibra Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra Which outputs fire on a received bell character
Output LED (GPIO) Pin the LED is wired to
Output LED active high Whether the LED pin is active high or low
Output buzzer (GPIO) Pin the buzzer is wired to
Output vibra (GPIO) Pin the vibration motor is wired to
Use PWM buzzer Drive the buzzer with PWM, which allows tones rather than a single pitch
Use I2S as buzzer Send the alert through an I2S audio output instead
Output duration (milliseconds) How long a single alert lasts
Nag timeout (seconds) Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Ringtone The tone played on a PWM buzzer, in RTTTL. Can be imported from a file

Store & Forward module

Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.

Setting Апісанне
Store & Forward enabled Activate store and forward
Heartbeat Periodically announce this node’s store-and-forward capability
Number of records Maximum stored messages
History return max Max messages to replay
History return window Time window for replay
Сервер Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)

💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.

Range Test module

⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.

Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.

Setting Апісанне
Range test enabled Activate range testing
Sender message interval (seconds) Time between test transmissions, chosen from a dropdown of fixed intervals
Save .CSV in storage (ESP32 only) Log received test data to the node’s own filesystem. ESP32 hardware only

Telemetry module

Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).

Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.

Setting Апісанне
Send Device Telemetry Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval How often to report battery, uptime and channel utilization
Environment metrics module enabled Report the attached environment sensors
Environment metrics update interval How often to report them
Environment metrics on-screen enabled Also show these readings on the device’s own display
Environment metrics use Fahrenheit Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Air quality metrics module enabled Report particulate and CO₂ sensor data
Air quality metrics update interval How often to report them
Power metrics module enabled Report the per-channel voltage and current readings
Power metrics update interval How often to report them
Power metrics on-screen enabled Also show power readings on the device’s display

See Telemetry & Sensors for supported sensors and configuration recommendations.

Canned Message module

Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.

Setting Апісанне
Canned message enabled ⚠️ Deprecated in the protobuf schema
Паведамленні Newline-separated list of messages
Send bell Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Rotary encoder #1 enabled Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port The three pins the encoder is wired to
Generate input event on Press / CW / CCW Which key event each encoder action produces
Up/Down/Select input enabled A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source ⚠️ Deprecated in the protobuf schema

Audio module

Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.

Setting Апісанне
CODEC 2 enabled Activate audio module
CODEC2 sample rate Audio quality/bandwidth tradeoff
PTT pin GPIO pin for the push-to-talk button
I2S word select GPIO pin for I2S WS
I2S data in GPIO pin for I2S DIN
I2S data out GPIO pin for I2S DOUT
I2S clock GPIO pin for the I2S bit clock

ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.

Remote Hardware module

GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.

⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.

Setting Апісанне
Remote Hardware enabled Activate remote GPIO access
Allow undefined pin access Allow access to any GPIO pin (security risk)
Available pins Up to 4 GPIO pins this node exposes for remote read/write

Neighbor Info module

Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.

Setting Апісанне
Neighbor Info enabled Activate neighbor broadcasting
Update interval (seconds) How often to broadcast neighbor list
Transmit over LoRa Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name

See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.

Ambient Lighting module

Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.

Setting Апісанне
LED state Turn the LED on or off
3 LED current limit (0–31)
Red / Green / Blue Individual color channel values (0–255)

Detection Sensor module

Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.

Setting Апісанне
Detection Sensor enabled Activate detection sensor
GPIO pin to monitor GPIO pin connected to sensor
Detection trigger type How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Use INPUT_PULLUP mode Enable the pin’s internal pull-up resistor
Minimum broadcast (seconds) Minimum time between alert broadcasts
State broadcast (seconds) Periodic state broadcast interval
Send bell with alert message Include bell character in alerts
Friendly name Custom name for this sensor

Paxcounter module

People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.

Setting Апісанне
Paxcounter enabled Activate people counting
Update interval (seconds) How often to report counts
Wi-Fi RSSI threshold Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE RSSI threshold The same cut-off for BLE advertisements (defaults to −80 dBm)

💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.

Status Message module

The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.

Mesh Beacon module

Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.

TAK module

Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.

Administration

Remote Administration

Remotely configure nodes that share your admin key:

  1. Select the target node in the node list.
  2. Navigate to Settings for that node.
  3. Modify configuration.
  4. Tap Save — changes are sent over the mesh.

⚠️ Important: Requires an admin key configured on both your node and the target node.

Device Actions

Settings → Administration holds five one-shot actions, each behind a confirmation dialog:

Action What it does
Set time Sends your phone’s clock to the node
Перазагрузіць Restarts the node
Shutdown Powers the node down
Factory reset Returns every setting to its factory default
NodeDB reset Clears the node database. This dialog carries a Preserve Favorites? switch

⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.

Backup & Restore

Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.

Advanced

Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.

Clean Node Database

Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.

  • Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
  • Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.

The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.

Панэль адладкі

Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.

App Settings

The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:

Privacy

  • Allow analytics and crash reporting — opt in or out of diagnostics.
  • Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
  • Homoglyph encoding — how look-alike characters in names are handled.

Appearance

  • Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
  • Theme and Language.
  • Show full message timestamps.

Persistence

  • A cache limit for how much history is kept.
  • Export rangetest packets, Export all packets and Export node database.

On their own

  • Node Layout — how much detail each row of the node list shows.
  • Wi-Fi Provisioning for mPWRD-OS — see Connections.
  • Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
  • System AI — appears only where app functions are available; see App Functions.

A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.

О нас

Settings → About carries the app’s own identity rather than the node’s:

Three sections:

  • What is Meshtastic? — a short description of the project.
  • Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
  • Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.

The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.

Acknowledgements

Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.

Troubleshooting remote admin

  • “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
  • Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
  • Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
+ Settings — Modules & Admin | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Беларуская
Meshtastic Docs ↗

🌐 Беларуская — Community translation View in English

Settings — Modules & Admin

Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.

💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.

Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:

A toggle setting in the on position

A dropdown setting, expanded to show its list of options

A text field setting with a value entered

A module settings card with its title and grouped controls

Module configuration

Every module lives under Settings → Module configuration.

⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes.

MQTT module

Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.

Setting Апісанне
MQTT enabled Toggle MQTT bridge
Address MQTT broker address
Імя карыстальніка Authentication username
Пароль Authentication password
Encryption enabled Encrypt MQTT payloads
JSON output enabled Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS enabled Use secure connection
Root topic Base MQTT topic path
Proxy to client enabled Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy on this phone The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT
Map reporting Publish position to the public map — see the Map reporting group that follows

Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:

Setting Апісанне
I agree. Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered

See MQTT for a detailed usage guide including encryption, privacy, and broker setup.

Serial module

Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.

Setting Апісанне
Serial enabled Activate serial communication
Echo enabled Echo received serial data back
Serial mode Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX GPIO pins for the serial connection
Serial baud rate Port speed
Скончыўся час чакання How long to wait before considering an incoming message complete
Override console serial port Take over the port the debug console normally uses

External Notification module

Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.

There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.

Setting Апісанне
External notification enabled Master toggle for the module
Alert message LED / buzzer / vibra Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra Which outputs fire on a received bell character
Output LED (GPIO) Pin the LED is wired to
Output LED active high Whether the LED pin is active high or low
Output buzzer (GPIO) Pin the buzzer is wired to
Output vibra (GPIO) Pin the vibration motor is wired to
Use PWM buzzer Drive the buzzer with PWM, which allows tones rather than a single pitch
Use I2S as buzzer Send the alert through an I2S audio output instead
GPIO Output Duration How long a single alert lasts
Nag Timeout Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Ringtone The tone played on a PWM buzzer, in RTTTL. Can be imported from a file

Store & Forward module

Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.

Setting Апісанне
Store & Forward enabled Activate store and forward
Heartbeat Periodically announce this node’s store-and-forward capability
Number of records Maximum stored messages
History return max Max messages to replay
History return window Time window for replay
Сервер Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)

💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.

Range Test module

⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.

Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.

Setting Апісанне
Range test enabled Activate range testing
Sender Interval Time between test transmissions, chosen from a dropdown of fixed intervals
Save .CSV in storage (ESP32 only) Log received test data to the node’s own filesystem. ESP32 hardware only

Telemetry module

Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).

Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.

Setting Апісанне
Send Device Telemetry Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval How often to report battery, uptime and channel utilization
Environment metrics module enabled Report the attached environment sensors
Environment metrics update interval How often to report them
Environment metrics on-screen enabled Also show these readings on the device’s own display
Environment metrics use Fahrenheit Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Air quality metrics module enabled Report particulate and CO₂ sensor data
Air quality metrics update interval How often to report them
Power metrics module enabled Report the per-channel voltage and current readings
Power metrics update interval How often to report them
Power metrics on-screen enabled Also show power readings on the device’s display

See Telemetry & Sensors for supported sensors and configuration recommendations.

Canned Message module

Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.

Setting Апісанне
Canned message enabled ⚠️ Deprecated in the protobuf schema
Паведамленні Newline-separated list of messages
Send bell Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Rotary encoder #1 enabled Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port The three pins the encoder is wired to
Generate input event on Press / CW / CCW Which key event each encoder action produces
Up/Down/Select input enabled A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source ⚠️ Deprecated in the protobuf schema

Audio module

Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.

Setting Апісанне
CODEC 2 enabled Activate audio module
CODEC2 sample rate Audio quality/bandwidth tradeoff
PTT pin GPIO pin for the push-to-talk button
I2S word select GPIO pin for I2S WS
I2S data in GPIO pin for I2S DIN
I2S data out GPIO pin for I2S DOUT
I2S clock GPIO pin for the I2S bit clock

ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.

Remote Hardware module

GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.

⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.

Setting Апісанне
Remote Hardware enabled Activate remote GPIO access
Allow undefined pin access Allow access to any GPIO pin (security risk)
Available pins Up to 4 GPIO pins this node exposes for remote read/write

Neighbor Info module

Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.

Setting Апісанне
Neighbor Info enabled Activate neighbor broadcasting
Update Interval How often to broadcast neighbor list
Transmit over LoRa Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name

See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.

Ambient Lighting module

Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.

Setting Апісанне
LED state Turn the LED on or off
3 LED current limit (0–31)
Red / Green / Blue Individual color channel values (0–255)

Detection Sensor module

Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.

Setting Апісанне
Detection Sensor enabled Activate detection sensor
GPIO pin to monitor GPIO pin connected to sensor
Detection trigger type How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Use INPUT_PULLUP mode Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts Minimum time between alert broadcasts
State Broadcast Interval Periodic state broadcast interval
Send bell with alert message Include bell character in alerts
Friendly name Custom name for this sensor

Paxcounter module

People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.

Setting Апісанне
Paxcounter enabled Activate people counting
Update Interval How often to report counts
WiFi Threshold (dBm) Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm) The same cut-off for BLE advertisements (defaults to −80 dBm)

💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.

Status Message module

The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.

Mesh Beacon module

Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.

TAK module

Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.

Administration

Remote Administration

Remotely configure nodes that share your admin key:

  1. Select the target node in the node list.
  2. Navigate to Settings for that node.
  3. Modify configuration.
  4. Tap Save — changes are sent over the mesh.

⚠️ Important: Requires an admin key configured on both your node and the target node.

Device Actions

Settings → Administration holds five one-shot actions, each behind a confirmation dialog:

Action What it does
Set time Sends your phone’s clock to the node
Перазагрузіць Restarts the node
Shutdown Powers the node down
Factory reset Returns every setting to its factory default
NodeDB reset Clears the node database. This dialog carries a Preserve Favorites? switch

⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.

Backup & Restore

Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.

Advanced

Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.

Clean Node Database

Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.

  • Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
  • Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.

The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.

Панэль адладкі

Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.

App Settings

The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:

Privacy

  • Allow analytics and crash reporting — opt in or out of diagnostics.
  • Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
  • Homoglyph encoding — how look-alike characters in names are handled.

Appearance

  • Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
  • Theme and Language.
  • Show full message timestamps.

Persistence

  • A cache limit for how much history is kept.
  • Export rangetest packets, Export all packets and Export node database.

On their own

  • Node Layout — how much detail each row of the node list shows.
  • Wi-Fi Provisioning for mPWRD-OS — see Connections.
  • Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
  • System AI — appears only where app functions are available; see App Functions.

A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.

О нас

Settings → About carries the app’s own identity rather than the node’s:

Three sections:

  • What is Meshtastic? — a short description of the project.
  • Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
  • Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.

The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.

Acknowledgements

Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.

Troubleshooting remote admin

  • “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
  • Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
  • Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
diff --git a/main/be-rBY/user/settings-radio-user.html b/main/be-rBY/user/settings-radio-user.html index a83d935049..9cae40b2f3 100644 --- a/main/be-rBY/user/settings-radio-user.html +++ b/main/be-rBY/user/settings-radio-user.html @@ -1 +1 @@ - Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Беларуская
Meshtastic Docs ↗

🌐 Беларуская — Community translation View in English

Settings — Radio & User

Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How these screens work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Апісанне
Long Name Your display name (up to 39 characters)
Short Name 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Unmessageable Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur node (Ham) Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in.

Конфигурация

Device Config

On Settings → Device configuration → Device.

Setting Апісанне Default
Device Role Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Rebroadcast Mode How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Node Info Broadcast Interval How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Double Tap as Button Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Уключана
LED Heartbeat Blink the status LED periodically Уключана
Time Zone POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it —
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to —

LoRa Config

On Settings → LoRa.

Setting Апісанне Default
Рэгіён Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number Unset (must configure)
Presets Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Transmit Power Transmission power (dBm); 0 = max allowed for region 0 (region max)
Frequency Override Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Use Preset On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead From preset
Coding Rate Manual mode only: 5–8. More redundancy costs airtime From preset
Bandwidth Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Frequency Slot Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmit Enabled Turning this off makes the node receive-only On
Override Duty Cycle Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
Ignore MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok to MQTT Allow your packets to be forwarded to MQTT by gateways Off
RX Boosted Gain Extra receive gain on SX126x radios; costs a little current Off
PA fan disabled Turn off the power-amplifier fan on hardware that has one Off

The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set.

Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Хуткасць SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a modem preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Display Config

On Settings → Device configuration → Display. These control the node’s own screen, not the app’s.

Setting Апісанне
Screen on for How long the display stays lit before sleeping
Carousel interval How often the node cycles between screens on its own
Display mode Screen layout/density used by the firmware
Display units Metric or Imperial on the node’s screen
Use 12h clock format Show the node’s clock as 12-hour rather than 24-hour
Bold Heading Draw the screen’s heading text in bold
Flip screen Rotate the display 180° for an inverted mounting
Тып OLED Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED
Wake on tap or motion Light the screen when the node is tapped or moved
Compass orientation Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each
Always point north Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Position Config

On Settings → Device configuration → Position.

Setting Апісанне
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the node asks its GPS for a fix
Broadcast Interval How often the position is shared with the mesh
Smart Position Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Fixed Position Use a manually entered latitude, longitude and altitude instead of the GPS
Position Flags A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Power Config

On Settings → Device configuration → Power.

Setting Апісанне
Enable power saving mode Let the node sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the node stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC multiplier override ratio The correction factor itself, used only when the override is on
Battery INA_2XX I2C address Address of an external INA-series power sensor, if fitted

Network Config

On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node.

Setting Апісанне
Wi-Fi enabled Enable the Wi-Fi node (ESP32 nodes)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Пароль Network password
Ethernet enabled Use a wired connection on hardware that has one
IPv4 mode DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP server Time synchronization server
rsyslog server Remote logging server

Network Config with a static IPv4 address entered

Bluetooth Config

On Settings → Device configuration → Bluetooth, on nodes with Bluetooth.

Setting Апісанне
Bluetooth enabled Enable/disable BLE radio
Pairing mode Fixed PIN, Random PIN, or No PIN
Fixed PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Security Config

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

Setting Апісанне
Public Key Your node’s public key (read-only)
Admin Key Keys permitted to administer this node remotely — up to three
Прыватны ключ Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it
Regenerate Private Key Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Serial console Serial console over the Stream API
Debug log API enabled Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth
Managed Mode Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.

+ Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Беларуская
Meshtastic Docs ↗

🌐 Беларуская — Community translation View in English

Settings — Radio & User

Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How these screens work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Апісанне
Long Name Your display name (up to 39 characters)
Short Name 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Unmessageable Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur node (Ham) Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in.

Конфигурация

Device Config

On Settings → Device configuration → Device.

Setting Апісанне Default
Device Role Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Rebroadcast Mode How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Node Info Broadcast Interval How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Double Tap as Button Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Уключана
LED Heartbeat Blink the status LED periodically Уключана
Time Zone POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it —
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to —

LoRa Config

On Settings → LoRa.

Setting Апісанне Default
Рэгіён Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number Unset (must configure)
Presets Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Transmit Power (dBm) Transmission power; 0 = max allowed for region 0 (region max)
Frequency Override Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Use Preset On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead From preset
Coding Rate Manual mode only: 5–8. More redundancy costs airtime From preset
Bandwidth Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Frequency Slot Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmit Enabled Turning this off makes the node receive-only On
Override Duty Cycle Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
Ignore MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok to MQTT Allow your packets to be forwarded to MQTT by gateways Off
RX Boosted Gain Extra receive gain on SX126x radios; costs a little current Off
PA fan disabled Turn off the power-amplifier fan on hardware that has one Off

The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set.

Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Хуткасць SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a modem preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Display Config

On Settings → Device configuration → Display. These control the node’s own screen, not the app’s.

Setting Апісанне
Screen on for How long the display stays lit before sleeping
Carousel interval How often the node cycles between screens on its own
Display mode Screen layout/density used by the firmware
Display units Metric or Imperial on the node’s screen
Use 12h clock format Show the node’s clock as 12-hour rather than 24-hour
Bold Heading Draw the screen’s heading text in bold
Flip screen Rotate the display 180° for an inverted mounting
Тып OLED Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED
Wake on tap or motion Light the screen when the node is tapped or moved
Compass orientation Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each
Always point north Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Position Config

On Settings → Device configuration → Position.

Setting Апісанне
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the node asks its GPS for a fix
Broadcast Interval How often the position is shared with the mesh
Smart Position Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Fixed Position Use a manually entered latitude, longitude and altitude instead of the GPS
Position Flags A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Power Config

On Settings → Device configuration → Power.

Setting Апісанне
Enable power saving mode Let the node sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the node stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC multiplier override ratio The correction factor itself, used only when the override is on
Battery INA_2XX I2C address Address of an external INA-series power sensor, if fitted

Network Config

On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node.

Setting Апісанне
Wi-Fi enabled Enable the Wi-Fi node (ESP32 nodes)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Пароль Network password
Ethernet enabled Use a wired connection on hardware that has one
IPv4 mode DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP server Time synchronization server
rsyslog server Remote logging server

Network Config with a static IPv4 address entered

Bluetooth Config

On Settings → Device configuration → Bluetooth, on nodes with Bluetooth.

Setting Апісанне
Bluetooth enabled Enable/disable BLE radio
Pairing mode Fixed PIN, Random PIN, or No PIN
Fixed PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Security Config

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

Setting Апісанне
Public Key Your node’s public key (read-only)
Admin Key Keys permitted to administer this node remotely — up to three
Прыватны ключ Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it
Regenerate Private Key Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Serial console Serial console over the Stream API
Debug log API enabled Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth
Managed Mode Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.

diff --git a/main/bg-rBG/user/discovery.html b/main/bg-rBG/user/discovery.html index 2a150f864f..bf4eb3ddf0 100644 --- a/main/bg-rBG/user/discovery.html +++ b/main/bg-rBG/user/discovery.html @@ -5,4 +5,4 @@ ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) -

Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:.

What to look for What it means
All hops show Good SNR (green) Healthy path — messages flow reliably
One hop shows a poor SNR (orange or red) Weak link — this relay segment is fragile
Many hops (4+) Long path — consider repositioning a node to shorten it
Different path on retry Mesh is adapting — multiple routes exist (this is good!)

💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network.

Troubleshooting with Traceroute

  • No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key.
  • Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa.
  • Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position.
  • Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric.

Neighbor Info

The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh.

Enabling Neighbor Info

  1. Navigate to Settings → Module configuration → Neighbor Info.
  2. Enable the module.
  3. Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
  4. Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air.

Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.

Viewing neighbor data

  • Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors.
  • Each neighbor entry shows the node that was directly heard and its signal quality.
  • Combine neighbor data from multiple nodes to understand the full mesh topology.

ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further.

Node list as a discovery tool

The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively.

Finding new nodes

  • Sort by Last heard to see the most recently active nodes at the top.
  • Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes.

Assessing connectivity

  • Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed.
  • Sort by Distance to find nearby nodes and verify they’re reachable.
  • Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge).

Infrastructure audit

  • Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes.
  • Check their signal quality and last-heard times to verify your infrastructure nodes are healthy.

See Nodes for full details on filtering and sorting options.

Tips for Mesh exploration

  • Start with traceroute — it gives you immediate, actionable information about a specific path.
  • Enable Neighbor Info on key nodes — especially routers and repeaters, to build a picture of the backbone.
  • Check the map — node positions on the Map combined with signal data help you understand why some links are strong and others are weak.
  • Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly.

Свързани теми

+

Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:.

What to look for What it means
All hops show Good SNR (green) Healthy path — messages flow reliably
One hop shows a poor SNR (orange or red) Weak link — this relay segment is fragile
Many hops (4+) Long path — consider repositioning a node to shorten it
Different path on retry Mesh is adapting — multiple routes exist (this is good!)

💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network.

Troubleshooting with Traceroute

  • No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key.
  • Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa.
  • Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position.
  • Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric.

Neighbor Info

The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh.

Enabling Neighbor Info

  1. Navigate to Settings → Module configuration → Neighbor Info.
  2. Enable the module.
  3. Set Update Interval. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
  4. Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air.

Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.

Viewing neighbor data

  • Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors.
  • Each neighbor entry shows the node that was directly heard and its signal quality.
  • Combine neighbor data from multiple nodes to understand the full mesh topology.

ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further.

Node list as a discovery tool

The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively.

Finding new nodes

  • Sort by Last heard to see the most recently active nodes at the top.
  • Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes.

Assessing connectivity

  • Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed.
  • Sort by Distance to find nearby nodes and verify they’re reachable.
  • Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge).

Infrastructure audit

  • Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes.
  • Check their signal quality and last-heard times to verify your infrastructure nodes are healthy.

See Nodes for full details on filtering and sorting options.

Tips for Mesh exploration

  • Start with traceroute — it gives you immediate, actionable information about a specific path.
  • Enable Neighbor Info on key nodes — especially routers and repeaters, to build a picture of the backbone.
  • Check the map — node positions on the Map combined with signal data help you understand why some links are strong and others are weak.
  • Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly.

Свързани теми

diff --git a/main/bg-rBG/user/mqtt.html b/main/bg-rBG/user/mqtt.html index cfc8e6b4a8..8204bddd97 100644 --- a/main/bg-rBG/user/mqtt.html +++ b/main/bg-rBG/user/mqtt.html @@ -1,2 +1,2 @@ MQTT | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Български
Meshtastic Docs ↗

🌐 Български — Community translation View in English

MQTT

MQTT bridges your Meshtastic mesh network to the internet, enabling long-range communication beyond radio range.

Преглед

The MQTT module connects your node to an MQTT broker, allowing:

  • Messages to reach nodes on different physical meshes via the internet
  • Integration with home automation and monitoring systems
  • Publishing node positions to the public Meshtastic map
  • Custom data pipelines for logging and alerting

Как работи 

[Your Node] → Radio → [Gateway Node with Wi-Fi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node]
-

A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh.

Конфигурация

Enabling MQTT

  1. Navigate to Settings → Module configuration → MQTT.
  2. Enable the MQTT module.
  3. Configure the broker connection:
Настройка Описание По подразбиране
Address MQTT broker hostname mqtt.meshtastic.org
Username Broker authentication meshdev
Password Broker authentication large4cats
Root topic Base topic for messages msh, which the radio rewrites to msh/<REGION> once you set a region
Encryption enabled Encrypt MQTT payload Активиран
JSON output enabled Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it Disabled
TLS enabled Secure connection to broker Disabled
Map reporting Report position to public map Disabled
Proxy to client enabled Relay MQTT through the connected phone Disabled

Connection Status and Test Connection

The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here.

Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason.

MQTT Proxy on This Phone

If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection.

ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them.

The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration.

Default Meshtastic Broker

The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing.

When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without).

🔒 Privacy: Messages on the public broker are readable by anyone subscribed. Always use channel encryption for private communications.

Private Broker

За по-добра поверителност и контрол, можете да управлявате свой собствен MQTT брокер:

  • Mosquitto (lightweight, open-source)
  • HiveMQ
  • EMQX

Configure your node to point to your private broker with appropriate credentials.

Map Reporting

When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.

Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.

Reports appear at meshmap.net and similar community map services.

🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published.

Direction Описание
Uplink Messages from mesh → MQTT broker
Downlink Messages from MQTT broker → mesh

Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on.

Message Formats

MQTT carries two payload formats:

Format Описание Use case
Protobuf Binary Meshtastic protobuf encoding Node-to-node mesh bridging
JSON Human-readable JSON on the /2/json/ topic Consumers outside the mesh (dashboards, home automation)

ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads.

Encryption & Privacy

Understanding the layered encryption model:

  1. Channel encryption happens on the mesh before MQTT. If your channel has a PSK, the MQTT payload is already encrypted — the broker and any subscribers see only the ciphertext.
  2. Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard.
  3. TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping.

🔒 Security: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications.

Най-добри практики

  • Use channel-level encryption (PSK) on channels that bridge to MQTT
  • Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes memory)
  • Use a private broker for sensitive deployments
  • Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh
  • Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back

Отстраняване на неизправности

MQTT Not Connecting

  • Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself.
  • Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces.
  • Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443).
  • DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly.

Messages Not Bridging

  • Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway.
  • Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage.
  • Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root.
  • Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway.
  • Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in.

Свързани теми

+

A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh.

Конфигурация

Enabling MQTT

  1. Navigate to Settings → Module configuration → MQTT.
  2. Enable the MQTT module.
  3. Configure the broker connection:
Настройка Описание По подразбиране
Address MQTT broker hostname mqtt.meshtastic.org
Username Broker authentication meshdev
Password Broker authentication large4cats
Root topic Base topic for messages msh, which the radio rewrites to msh/<REGION> once you set a region
Encryption enabled Encrypt MQTT payload Активиран
JSON output enabled Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it Disabled
TLS enabled Secure connection to broker Disabled
Map reporting Report position to public map Disabled
Proxy to client enabled Relay MQTT through the connected phone Disabled

Connection Status and Test Connection

The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here.

Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason.

MQTT Proxy on This Phone

If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection.

ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them.

The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration.

Default Meshtastic Broker

The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing.

When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without).

🔒 Privacy: Messages on the public broker are readable by anyone subscribed. Always use channel encryption for private communications.

Private Broker

За по-добра поверителност и контрол, можете да управлявате свой собствен MQTT брокер:

  • Mosquitto (lightweight, open-source)
  • HiveMQ
  • EMQX

Configure your node to point to your private broker with appropriate credentials.

Map Reporting

When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.

Turning it on opens a consent card. Turn on I agree. and choose a Map Publish Interval of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.

Reports appear at meshmap.net and similar community map services.

🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published.

Direction Описание
Uplink Messages from mesh → MQTT broker
Downlink Messages from MQTT broker → mesh

Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on.

Message Formats

MQTT carries two payload formats:

Format Описание Use case
Protobuf Binary Meshtastic protobuf encoding Node-to-node mesh bridging
JSON Human-readable JSON on the /2/json/ topic Consumers outside the mesh (dashboards, home automation)

ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads.

Encryption & Privacy

Understanding the layered encryption model:

  1. Channel encryption happens on the mesh before MQTT. If your channel has a PSK, the MQTT payload is already encrypted — the broker and any subscribers see only the ciphertext.
  2. Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard.
  3. TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping.

🔒 Security: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications.

Най-добри практики

  • Use channel-level encryption (PSK) on channels that bridge to MQTT
  • Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes memory)
  • Use a private broker for sensitive deployments
  • Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh
  • Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back

Отстраняване на неизправности

MQTT Not Connecting

  • Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself.
  • Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces.
  • Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443).
  • DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly.

Messages Not Bridging

  • Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway.
  • Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage.
  • Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root.
  • Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway.
  • Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in.

Свързани теми

diff --git a/main/bg-rBG/user/settings-module-admin.html b/main/bg-rBG/user/settings-module-admin.html index 5ce97fdf3d..4e42479b8a 100644 --- a/main/bg-rBG/user/settings-module-admin.html +++ b/main/bg-rBG/user/settings-module-admin.html @@ -1 +1 @@ - Settings — Modules & Admin | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Български
Meshtastic Docs ↗

🌐 Български — Community translation View in English

Settings — Modules & Admin

Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.

💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.

Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:

A toggle setting in the on position

A dropdown setting, expanded to show its list of options

A text field setting with a value entered

A module settings card with its title and grouped controls

Конфигуриране на модулите

Every module lives under Settings → Module configuration.

⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes.

MQTT module

Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.

Настройка Описание
MQTT е активиран Toggle MQTT bridge
Адрес MQTT broker address
Потребителско име Authentication username
Парола Authentication password
Криптирането е активирано Encrypt MQTT payloads
JSON output enabled Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS е активиран Use secure connection
Root topic Base MQTT topic path
Прокси към клиент е активиран Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT прокси на този телефон The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT
Map reporting Publish position to the public map — see the Map reporting group that follows

Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:

Настройка Описание
Съгласен съм. Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map reporting interval (seconds) How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered

See MQTT for a detailed usage guide including encryption, privacy, and broker setup.

Serial module

Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.

Настройка Описание
Серийната връзка е активирана Activate serial communication
Echo е активирано Echo received serial data back
Сериен режим Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX GPIO pins for the serial connection
Серийна скорост на предаване Port speed
Timeout How long to wait before considering an incoming message complete
Override console serial port Take over the port the debug console normally uses

External Notification module

Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.

There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.

Настройка Описание
Външните известия са активирани Master toggle for the module
Alert message LED / buzzer / vibra Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra Which outputs fire on a received bell character
Output LED (GPIO) Pin the LED is wired to
Output LED active high Whether the LED pin is active high or low
Output buzzer (GPIO) Pin the buzzer is wired to
Output vibra (GPIO) Pin the vibration motor is wired to
Използване на PWM зумер Drive the buzzer with PWM, which allows tones rather than a single pitch
Use I2S as buzzer Send the alert through an I2S audio output instead
Output duration (milliseconds) How long a single alert lasts
Nag timeout (seconds) Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Тон на звънене The tone played on a PWM buzzer, in RTTTL. Can be imported from a file

Store & Forward module

Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.

Настройка Описание
Съхраняване & препращане е активиран Activate store and forward
Heartbeat Periodically announce this node’s store-and-forward capability
Брой записи Maximum stored messages
History return max Max messages to replay
History return window Time window for replay
Сървър Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)

💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.

Range Test module

⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.

Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.

Настройка Описание
Тест на обхвата е активиран Activate range testing
Sender message interval (seconds) Time between test transmissions, chosen from a dropdown of fixed intervals
Запазване на .CSV в хранилище (само за ESP32) Log received test data to the node’s own filesystem. ESP32 hardware only

Telemetry module

Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).

Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.

Настройка Описание
Изпращане на телеметрия на устройството Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Интервал на актуализиране на показателите на устройството How often to report battery, uptime and channel utilization
Модулът за измерване на околната среда е активиран Report the attached environment sensors
Интервал на актуализиране на показателите за средата How often to report them
Показателите на околната среда на екрана са активирани Also show these readings on the device’s own display
Показателите на околната среда използват Фаренхайт Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Модулът за показатели за качеството на въздуха е активиран Report particulate and CO₂ sensor data
Интервал на актуализиране на показателите за качеството на въздуха How often to report them
Power metrics module enabled Report the per-channel voltage and current readings
Power metrics update interval How often to report them
Power metrics on-screen enabled Also show power readings on the device’s display

See Telemetry & Sensors for supported sensors and configuration recommendations.

Canned Message module

Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.

Настройка Описание
Canned message enabled ⚠️ Deprecated in the protobuf schema
Съобщения Newline-separated list of messages
Send bell Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Ротационен енкодер #1 е активиран Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port The three pins the encoder is wired to
Generate input event on Press / CW / CCW Which key event each encoder action produces
Up/Down/Select input enabled A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source ⚠️ Deprecated in the protobuf schema

Audio module

Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.

Настройка Описание
CODEC 2 е активиран Activate audio module
CODEC2 sample rate Audio quality/bandwidth tradeoff
Пин за РТТ GPIO pin for the push-to-talk button
I2S word select GPIO pin for I2S WS
I2S data in GPIO pin for I2S DIN
I2S data out GPIO pin for I2S DOUT
I2S clock GPIO pin for the I2S bit clock

ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.

Remote Hardware module

GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.

⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.

Настройка Описание
Отдалечен хардуер е активиран Activate remote GPIO access
Allow undefined pin access Allow access to any GPIO pin (security risk)
Налични пинове Up to 4 GPIO pins this node exposes for remote read/write

Neighbor Info module

Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.

Настройка Описание
Neighbor Info enabled Activate neighbor broadcasting
Интервал на актуализиране (секунди) How often to broadcast neighbor list
Предаване през LoRa Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name

See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.

Ambient Lighting module

Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.

Настройка Описание
LED за състояние Turn the LED on or off
Текущ LED current limit (0–31)
Red / Green / Blue Individual color channel values (0–255)

Detection Sensor module

Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.

Настройка Описание
Detection Sensor enabled Activate detection sensor
GPIO pin to monitor GPIO pin connected to sensor
Detection trigger type How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Използване на режим INPUT_PULLUP Enable the pin’s internal pull-up resistor
Minimum broadcast (seconds) Minimum time between alert broadcasts
State broadcast (seconds) Periodic state broadcast interval
Send bell with alert message Include bell character in alerts
Приятелско име Custom name for this sensor

Paxcounter module

People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.

Настройка Описание
Paxcounter е активиран Activate people counting
Интервал на актуализиране (секунди) How often to report counts
Wi-Fi RSSI threshold Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE RSSI threshold The same cut-off for BLE advertisements (defaults to −80 dBm)

💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.

Status Message module

The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.

Mesh Beacon module

Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.

TAK module

Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.

Администриране

Отдалечено администриране

Remotely configure nodes that share your admin key:

  1. Select the target node in the node list.
  2. Navigate to Settings for that node.
  3. Modify configuration.
  4. Tap Save — changes are sent over the mesh.

⚠️ Important: Requires an admin key configured on both your node and the target node.

Device Actions

Settings → Administration holds five one-shot actions, each behind a confirmation dialog:

Действие Какво прави
Set time Sends your phone’s clock to the node
Рестартиране Restarts the node
Изключване Powers the node down
Фабрично нулиране Returns every setting to its factory default
Нулиране на базата данни с възли Clears the node database. This dialog carries a Preserve Favorites? switch

⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.

Архивиране & Възстановяване

Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.

Разширени

Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.

Почистване на базата данни с възлите

Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.

  • Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
  • Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.

The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.

Панел за отстраняване на грешки

Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.

App Settings

The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:

Privacy

  • Allow analytics and crash reporting — opt in or out of diagnostics.
  • Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
  • Homoglyph encoding — how look-alike characters in names are handled.

Appearance

  • Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
  • Theme and Language.
  • Show full message timestamps.

Persistence

  • A cache limit for how much history is kept.
  • Export rangetest packets, Export all packets and Export node database.

On their own

  • Node Layout — how much detail each row of the node list shows.
  • Wi-Fi Provisioning for mPWRD-OS — see Connections.
  • Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
  • System AI — appears only where app functions are available; see App Functions.

A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.

Относно

Settings → About carries the app’s own identity rather than the node’s:

Three sections:

  • What is Meshtastic? — a short description of the project.
  • Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
  • Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.

The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.

Благодарности

Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.

Troubleshooting remote admin

  • “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
  • Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
  • Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
+ Settings — Modules & Admin | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Български
Meshtastic Docs ↗

🌐 Български — Community translation View in English

Settings — Modules & Admin

Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.

💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.

Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:

A toggle setting in the on position

A dropdown setting, expanded to show its list of options

A text field setting with a value entered

A module settings card with its title and grouped controls

Конфигуриране на модулите

Every module lives under Settings → Module configuration.

⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes.

MQTT module

Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.

Настройка Описание
MQTT е активиран Toggle MQTT bridge
Адрес MQTT broker address
Потребителско име Authentication username
Парола Authentication password
Криптирането е активирано Encrypt MQTT payloads
JSON output enabled Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS е активиран Use secure connection
Root topic Base MQTT topic path
Прокси към клиент е активиран Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT прокси на този телефон The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT
Map reporting Publish position to the public map — see the Map reporting group that follows

Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:

Настройка Описание
Съгласен съм. Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered

See MQTT for a detailed usage guide including encryption, privacy, and broker setup.

Serial module

Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.

Настройка Описание
Серийната връзка е активирана Activate serial communication
Echo е активирано Echo received serial data back
Сериен режим Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX GPIO pins for the serial connection
Серийна скорост на предаване Port speed
Timeout How long to wait before considering an incoming message complete
Override console serial port Take over the port the debug console normally uses

External Notification module

Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.

There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.

Настройка Описание
Външните известия са активирани Master toggle for the module
Alert message LED / buzzer / vibra Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra Which outputs fire on a received bell character
Output LED (GPIO) Pin the LED is wired to
Output LED active high Whether the LED pin is active high or low
Output buzzer (GPIO) Pin the buzzer is wired to
Output vibra (GPIO) Pin the vibration motor is wired to
Използване на PWM зумер Drive the buzzer with PWM, which allows tones rather than a single pitch
Use I2S as buzzer Send the alert through an I2S audio output instead
GPIO Output Duration How long a single alert lasts
Nag Timeout Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Тон на звънене The tone played on a PWM buzzer, in RTTTL. Can be imported from a file

Store & Forward module

Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.

Настройка Описание
Съхраняване & препращане е активиран Activate store and forward
Heartbeat Periodically announce this node’s store-and-forward capability
Брой записи Maximum stored messages
History return max Max messages to replay
History return window Time window for replay
Сървър Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)

💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.

Range Test module

⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.

Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.

Настройка Описание
Тест на обхвата е активиран Activate range testing
Sender Interval Time between test transmissions, chosen from a dropdown of fixed intervals
Запазване на .CSV в хранилище (само за ESP32) Log received test data to the node’s own filesystem. ESP32 hardware only

Telemetry module

Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).

Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.

Настройка Описание
Изпращане на телеметрия на устройството Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Интервал на актуализиране на показателите на устройството How often to report battery, uptime and channel utilization
Модулът за измерване на околната среда е активиран Report the attached environment sensors
Интервал на актуализиране на показателите за средата How often to report them
Показателите на околната среда на екрана са активирани Also show these readings on the device’s own display
Показателите на околната среда използват Фаренхайт Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Модулът за показатели за качеството на въздуха е активиран Report particulate and CO₂ sensor data
Интервал на актуализиране на показателите за качеството на въздуха How often to report them
Power metrics module enabled Report the per-channel voltage and current readings
Power metrics update interval How often to report them
Power metrics on-screen enabled Also show power readings on the device’s display

See Telemetry & Sensors for supported sensors and configuration recommendations.

Canned Message module

Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.

Настройка Описание
Canned message enabled ⚠️ Deprecated in the protobuf schema
Съобщения Newline-separated list of messages
Send bell Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Ротационен енкодер #1 е активиран Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port The three pins the encoder is wired to
Generate input event on Press / CW / CCW Which key event each encoder action produces
Up/Down/Select input enabled A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source ⚠️ Deprecated in the protobuf schema

Audio module

Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.

Настройка Описание
CODEC 2 е активиран Activate audio module
CODEC2 sample rate Audio quality/bandwidth tradeoff
Пин за РТТ GPIO pin for the push-to-talk button
I2S word select GPIO pin for I2S WS
I2S data in GPIO pin for I2S DIN
I2S data out GPIO pin for I2S DOUT
I2S clock GPIO pin for the I2S bit clock

ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.

Remote Hardware module

GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.

⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.

Настройка Описание
Отдалечен хардуер е активиран Activate remote GPIO access
Allow undefined pin access Allow access to any GPIO pin (security risk)
Налични пинове Up to 4 GPIO pins this node exposes for remote read/write

Neighbor Info module

Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.

Настройка Описание
Neighbor Info enabled Activate neighbor broadcasting
Интервал на актуализиране How often to broadcast neighbor list
Предаване през LoRa Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name

See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.

Ambient Lighting module

Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.

Настройка Описание
LED за състояние Turn the LED on or off
Текущ LED current limit (0–31)
Red / Green / Blue Individual color channel values (0–255)

Detection Sensor module

Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.

Настройка Описание
Detection Sensor enabled Activate detection sensor
GPIO pin to monitor GPIO pin connected to sensor
Detection trigger type How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Използване на режим INPUT_PULLUP Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts Minimum time between alert broadcasts
State Broadcast Interval Periodic state broadcast interval
Send bell with alert message Include bell character in alerts
Приятелско име Custom name for this sensor

Paxcounter module

People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.

Настройка Описание
Paxcounter е активиран Activate people counting
Интервал на актуализиране How often to report counts
WiFi Threshold (dBm) Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm) The same cut-off for BLE advertisements (defaults to −80 dBm)

💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.

Status Message module

The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.

Mesh Beacon module

Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.

TAK module

Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.

Администриране

Отдалечено администриране

Remotely configure nodes that share your admin key:

  1. Select the target node in the node list.
  2. Navigate to Settings for that node.
  3. Modify configuration.
  4. Tap Save — changes are sent over the mesh.

⚠️ Important: Requires an admin key configured on both your node and the target node.

Device Actions

Settings → Administration holds five one-shot actions, each behind a confirmation dialog:

Действие Какво прави
Set time Sends your phone’s clock to the node
Рестартиране Restarts the node
Изключване Powers the node down
Фабрично нулиране Returns every setting to its factory default
Нулиране на базата данни с възли Clears the node database. This dialog carries a Preserve Favorites? switch

⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.

Архивиране & Възстановяване

Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.

Разширени

Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.

Почистване на базата данни с възлите

Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.

  • Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
  • Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.

The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.

Панел за отстраняване на грешки

Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.

App Settings

The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:

Privacy

  • Allow analytics and crash reporting — opt in or out of diagnostics.
  • Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
  • Homoglyph encoding — how look-alike characters in names are handled.

Appearance

  • Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
  • Theme and Language.
  • Show full message timestamps.

Persistence

  • A cache limit for how much history is kept.
  • Export rangetest packets, Export all packets and Export node database.

On their own

  • Node Layout — how much detail each row of the node list shows.
  • Wi-Fi Provisioning for mPWRD-OS — see Connections.
  • Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
  • System AI — appears only where app functions are available; see App Functions.

A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.

Относно

Settings → About carries the app’s own identity rather than the node’s:

Three sections:

  • What is Meshtastic? — a short description of the project.
  • Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
  • Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.

The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.

Благодарности

Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.

Troubleshooting remote admin

  • “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
  • Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
  • Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
diff --git a/main/bg-rBG/user/settings-radio-user.html b/main/bg-rBG/user/settings-radio-user.html index fdcac39d6c..4c83c0ed79 100644 --- a/main/bg-rBG/user/settings-radio-user.html +++ b/main/bg-rBG/user/settings-radio-user.html @@ -1 +1 @@ - Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Български
Meshtastic Docs ↗

🌐 Български — Community translation View in English

Settings — Radio & User

Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How these screens work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Екранна снимка
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

Потребителски настройки

User Profile

On Settings → User.

Настройка Описание
Дълго име Your display name (up to 39 characters)
Кратко име 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Без съобщения Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur node (Ham) Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in.

Конфигурация

Конфигуриране на устройството

On Settings → Device configuration → Device.

Настройка Описание По подразбиране
Роля на устройството Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Режим на препредаване How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Node Info Broadcast Interval How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Double Tap as Button Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Активиран
LED Heartbeat Blink the status LED periodically Активиран
Часова зона POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it —
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to —

Конфигуриране на LoRa

On Settings → LoRa.

Настройка Описание По подразбиране
Регион Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number Unset (must configure)
Предварително зададени Speed/range tradeoff LongFast
Брой отскоци Maximum retransmit hops 3
Мощност на предаване Transmission power (dBm); 0 = max allowed for region 0 (region max)
Frequency Override Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Използване на предварително зададени настройки On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead From preset
Coding Rate Manual mode only: 5–8. More redundancy costs airtime From preset
Широчина на честотната лента Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Честотен слот Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Предаването е активирано Turning this off makes the node receive-only On
Override Duty Cycle Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
Игнориране на MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok to MQTT Allow your packets to be forwarded to MQTT by gateways Off
RX Boosted Gain Extra receive gain on SX126x radios; costs a little current Off
PA fan disabled Turn off the power-amplifier fan on hardware that has one Off

The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set.

Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Диапазон Скорост SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a modem preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Конфигуриране на дисплея

On Settings → Device configuration → Display. These control the node’s own screen, not the app’s.

Настройка Описание
Екранът е включен за How long the display stays lit before sleeping
Carousel interval How often the node cycles between screens on its own
Режим на дисплея Screen layout/density used by the firmware
Показвани единици Metric or Imperial on the node’s screen
Използване на 12ч формат Show the node’s clock as 12-hour rather than 24-hour
Удебелен заглавен шрифт Draw the screen’s heading text in bold
Обръщане на екрана Rotate the display 180° for an inverted mounting
Тип на OLED Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED
Събуждане при докосване или движение Light the screen when the node is tapped or moved
Ориентация на компаса Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each
Always point north Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Конфигуриране на позицията

On Settings → Device configuration → Position.

Настройка Описание
Режим на GPS (физически хардуер) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the node asks its GPS for a fix
Интервал на излъчване How often the position is shared with the mesh
Интелигентна позиция Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Фиксирана позиция Use a manually entered latitude, longitude and altitude instead of the GPS
Position Flags A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Конфигуриране на захранването

On Settings → Device configuration → Power.

Настройка Описание
Активиране на енергоспестяващ режим Let the node sleep aggressively between activity
Изключване при загуба на захранване Power the device down after external power disappears
Продължителност на супер дълбок сън How long the deepest sleep state lasts
Минимално време за събуждане The shortest time the node stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC multiplier override ratio The correction factor itself, used only when the override is on
I2C адрес на батерията INA_2XX Address of an external INA-series power sensor, if fitted

Конфигуриране на мрежата

On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node.

Настройка Описание
Wi-Fi enabled Enable the Wi-Fi node (ESP32 nodes)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Парола Парола за мрежата
Ethernet е активиран Use a wired connection on hardware that has one
Режим на IPv4 DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP сървър Time synchronization server
rsyslog сървър Remote logging server

Network Config with a static IPv4 address entered

Конфигуриране на Bluetooth

On Settings → Device configuration → Bluetooth, on nodes with Bluetooth.

Настройка Описание
Bluetooth е активиран Enable/disable BLE radio
Режим на сдвояване Fixed PIN, Random PIN, or No PIN
Фиксиран ПИН PIN code for pairing. Must be exactly six digits — the field rejects anything else

Конфигуриране на сигурността

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

Настройка Описание
Публичен ключ Your node’s public key (read-only)
Администраторски ключ Keys permitted to administer this node remotely — up to three
Частен ключ Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it
Регенериране на частния ключ Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Серийна конзола Serial console over the Stream API
Debug log API enabled Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth
Управляем режим Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device.

Alongside the passphrase you set the limits that end a session automatically:

Field Какво прави
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.

+ Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Български
Meshtastic Docs ↗

🌐 Български — Community translation View in English

Settings — Radio & User

Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How these screens work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Екранна снимка
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

Потребителски настройки

User Profile

On Settings → User.

Настройка Описание
Дълго име Your display name (up to 39 characters)
Кратко име 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Без съобщения Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur node (Ham) Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in.

Конфигурация

Конфигуриране на устройството

On Settings → Device configuration → Device.

Настройка Описание По подразбиране
Роля на устройството Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Режим на препредаване How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Node Info Broadcast Interval How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Double Tap as Button Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Активиран
LED Heartbeat Blink the status LED periodically Активиран
Часова зона POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it —
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to —

Конфигуриране на LoRa

On Settings → LoRa.

Настройка Описание По подразбиране
Регион Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number Unset (must configure)
Предварително зададени Speed/range tradeoff LongFast
Брой отскоци Maximum retransmit hops 3
Transmit Power (dBm) Transmission power; 0 = max allowed for region 0 (region max)
Frequency Override Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Използване на предварително зададени настройки On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead From preset
Coding Rate Manual mode only: 5–8. More redundancy costs airtime From preset
Широчина на честотната лента Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Честотен слот Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Предаването е активирано Turning this off makes the node receive-only On
Override Duty Cycle Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
Игнориране на MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok to MQTT Allow your packets to be forwarded to MQTT by gateways Off
RX Boosted Gain Extra receive gain on SX126x radios; costs a little current Off
PA fan disabled Turn off the power-amplifier fan on hardware that has one Off

The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set.

Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Диапазон Скорост SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a modem preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Конфигуриране на дисплея

On Settings → Device configuration → Display. These control the node’s own screen, not the app’s.

Настройка Описание
Екранът е включен за How long the display stays lit before sleeping
Carousel interval How often the node cycles between screens on its own
Режим на дисплея Screen layout/density used by the firmware
Показвани единици Metric or Imperial on the node’s screen
Използване на 12ч формат Show the node’s clock as 12-hour rather than 24-hour
Удебелен заглавен шрифт Draw the screen’s heading text in bold
Обръщане на екрана Rotate the display 180° for an inverted mounting
Тип на OLED Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED
Събуждане при докосване или движение Light the screen when the node is tapped or moved
Ориентация на компаса Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each
Always point north Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Конфигуриране на позицията

On Settings → Device configuration → Position.

Настройка Описание
Режим на GPS (физически хардуер) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the node asks its GPS for a fix
Интервал на излъчване How often the position is shared with the mesh
Интелигентна позиция Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Фиксирана позиция Use a manually entered latitude, longitude and altitude instead of the GPS
Position Flags A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Конфигуриране на захранването

On Settings → Device configuration → Power.

Настройка Описание
Активиране на енергоспестяващ режим Let the node sleep aggressively between activity
Изключване при загуба на захранване Power the device down after external power disappears
Продължителност на супер дълбок сън How long the deepest sleep state lasts
Минимално време за събуждане The shortest time the node stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC multiplier override ratio The correction factor itself, used only when the override is on
I2C адрес на батерията INA_2XX Address of an external INA-series power sensor, if fitted

Конфигуриране на мрежата

On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node.

Настройка Описание
Wi-Fi enabled Enable the Wi-Fi node (ESP32 nodes)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Парола Парола за мрежата
Ethernet е активиран Use a wired connection on hardware that has one
Режим на IPv4 DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP сървър Time synchronization server
rsyslog сървър Remote logging server

Network Config with a static IPv4 address entered

Конфигуриране на Bluetooth

On Settings → Device configuration → Bluetooth, on nodes with Bluetooth.

Настройка Описание
Bluetooth е активиран Enable/disable BLE radio
Режим на сдвояване Fixed PIN, Random PIN, or No PIN
Фиксиран ПИН PIN code for pairing. Must be exactly six digits — the field rejects anything else

Конфигуриране на сигурността

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

Настройка Описание
Публичен ключ Your node’s public key (read-only)
Администраторски ключ Keys permitted to administer this node remotely — up to three
Частен ключ Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it
Регенериране на частния ключ Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Серийна конзола Serial console over the Stream API
Debug log API enabled Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth
Управляем режим Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device.

Alongside the passphrase you set the limits that end a session automatically:

Field Какво прави
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.

diff --git a/main/ca-rES/user/discovery.html b/main/ca-rES/user/discovery.html index f70727bb7a..c6620183fa 100644 --- a/main/ca-rES/user/discovery.html +++ b/main/ca-rES/user/discovery.html @@ -5,4 +5,4 @@ ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) -

Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:.

What to look for What it means
All hops show Good SNR (green) Healthy path — messages flow reliably
One hop shows a poor SNR (orange or red) Weak link — this relay segment is fragile
Many hops (4+) Long path — consider repositioning a node to shorten it
Different path on retry Mesh is adapting — multiple routes exist (this is good!)

💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network.

Troubleshooting with Traceroute

  • No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key.
  • Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa.
  • Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position.
  • Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric.

Neighbor Info

The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh.

Enabling Neighbor Info

  1. Navigate to Settings → Module configuration → Neighbor Info.
  2. Enable the module.
  3. Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
  4. Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air.

Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.

Viewing neighbor data

  • Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors.
  • Each neighbor entry shows the node that was directly heard and its signal quality.
  • Combine neighbor data from multiple nodes to understand the full mesh topology.

ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further.

Node list as a discovery tool

The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively.

Finding new nodes

  • Sort by Last heard to see the most recently active nodes at the top.
  • Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes.

Assessing connectivity

  • Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed.
  • Sort by Distance to find nearby nodes and verify they’re reachable.
  • Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge).

Infrastructure audit

  • Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes.
  • Check their signal quality and last-heard times to verify your infrastructure nodes are healthy.

See Nodes for full details on filtering and sorting options.

Tips for Mesh exploration

  • Start with traceroute — it gives you immediate, actionable information about a specific path.
  • Enable Neighbor Info on key nodes — especially routers and repeaters, to build a picture of the backbone.
  • Check the map — node positions on the Map combined with signal data help you understand why some links are strong and others are weak.
  • Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly.
+

Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:.

What to look for What it means
All hops show Good SNR (green) Healthy path — messages flow reliably
One hop shows a poor SNR (orange or red) Weak link — this relay segment is fragile
Many hops (4+) Long path — consider repositioning a node to shorten it
Different path on retry Mesh is adapting — multiple routes exist (this is good!)

💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network.

Troubleshooting with Traceroute

  • No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key.
  • Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa.
  • Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position.
  • Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric.

Neighbor Info

The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh.

Enabling Neighbor Info

  1. Navigate to Settings → Module configuration → Neighbor Info.
  2. Enable the module.
  3. Set Update Interval. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
  4. Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air.

Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.

Viewing neighbor data

  • Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors.
  • Each neighbor entry shows the node that was directly heard and its signal quality.
  • Combine neighbor data from multiple nodes to understand the full mesh topology.

ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further.

Node list as a discovery tool

The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively.

Finding new nodes

  • Sort by Last heard to see the most recently active nodes at the top.
  • Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes.

Assessing connectivity

  • Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed.
  • Sort by Distance to find nearby nodes and verify they’re reachable.
  • Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge).

Infrastructure audit

  • Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes.
  • Check their signal quality and last-heard times to verify your infrastructure nodes are healthy.

See Nodes for full details on filtering and sorting options.

Tips for Mesh exploration

  • Start with traceroute — it gives you immediate, actionable information about a specific path.
  • Enable Neighbor Info on key nodes — especially routers and repeaters, to build a picture of the backbone.
  • Check the map — node positions on the Map combined with signal data help you understand why some links are strong and others are weak.
  • Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly.
diff --git a/main/ca-rES/user/mqtt.html b/main/ca-rES/user/mqtt.html index 6874e5b86e..d52665bbd5 100644 --- a/main/ca-rES/user/mqtt.html +++ b/main/ca-rES/user/mqtt.html @@ -1,2 +1,2 @@ MQTT | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Català
Meshtastic Docs ↗

🌐 Català — Community translation View in English

MQTT

MQTT bridges your Meshtastic mesh network to the internet, enabling long-range communication beyond radio range.

Overview

The MQTT module connects your node to an MQTT broker, allowing:

  • Messages to reach nodes on different physical meshes via the internet
  • Integration with home automation and monitoring systems
  • Publishing node positions to the public Meshtastic map
  • Custom data pipelines for logging and alerting

How It Works 

[Your Node] → Radio → [Gateway Node with Wi-Fi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node]
-

A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh.

Configuration

Enabling MQTT

  1. Navigate to Settings → Module configuration → MQTT.
  2. Enable the MQTT module.
  3. Configure the broker connection:
Setting Descripció Default
Address MQTT broker hostname mqtt.meshtastic.org
Username Broker authentication meshdev
Password Broker authentication large4cats
Root topic Base topic for messages msh, which the radio rewrites to msh/<REGION> once you set a region
Encryption enabled Encrypt MQTT payload Enabled
JSON output enabled Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it Disabled
TLS enabled Secure connection to broker Disabled
Map reporting Report position to public map Disabled
Proxy to client enabled Relay MQTT through the connected phone Disabled

Connection Status and Test Connection

The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here.

Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason.

MQTT Proxy on This Phone

If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection.

ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them.

The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration.

Default Meshtastic Broker

The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing.

When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without).

🔒 Privacy: Messages on the public broker are readable by anyone subscribed. Always use channel encryption for private communications.

Private Broker

For better privacy and control, you can run your own MQTT broker:

  • Mosquitto (lightweight, open-source)
  • HiveMQ
  • EMQX

Configure your node to point to your private broker with appropriate credentials.

Map Reporting

When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.

Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.

Reports appear at meshmap.net and similar community map services.

🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published.

Direction Descripció
Uplink Messages from mesh → MQTT broker
Downlink Messages from MQTT broker → mesh

Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on.

Message Formats

MQTT carries two payload formats:

Format Descripció Use case
Protobuf Binary Meshtastic protobuf encoding Node-to-node mesh bridging
JSON Human-readable JSON on the /2/json/ topic Consumers outside the mesh (dashboards, home automation)

ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads.

Encryption & Privacy

Understanding the layered encryption model:

  1. Channel encryption happens on the mesh before MQTT. If your channel has a PSK, the MQTT payload is already encrypted — the broker and any subscribers see only the ciphertext.
  2. Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard.
  3. TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping.

🔒 Security: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications.

Best Practices

  • Use channel-level encryption (PSK) on channels that bridge to MQTT
  • Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes memory)
  • Use a private broker for sensitive deployments
  • Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh
  • Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back

Troubleshooting

MQTT Not Connecting

  • Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself.
  • Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces.
  • Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443).
  • DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly.

Messages Not Bridging

  • Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway.
  • Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage.
  • Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root.
  • Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway.
  • Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in.
+

A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh.

Configuration

Enabling MQTT

  1. Navigate to Settings → Module configuration → MQTT.
  2. Enable the MQTT module.
  3. Configure the broker connection:
Setting Descripció Default
Address MQTT broker hostname mqtt.meshtastic.org
Username Broker authentication meshdev
Password Broker authentication large4cats
Root topic Base topic for messages msh, which the radio rewrites to msh/<REGION> once you set a region
Encryption enabled Encrypt MQTT payload Enabled
JSON output enabled Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it Disabled
TLS enabled Secure connection to broker Disabled
Map reporting Report position to public map Disabled
Proxy to client enabled Relay MQTT through the connected phone Disabled

Connection Status and Test Connection

The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here.

Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason.

MQTT Proxy on This Phone

If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection.

ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them.

The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration.

Default Meshtastic Broker

The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing.

When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without).

🔒 Privacy: Messages on the public broker are readable by anyone subscribed. Always use channel encryption for private communications.

Private Broker

For better privacy and control, you can run your own MQTT broker:

  • Mosquitto (lightweight, open-source)
  • HiveMQ
  • EMQX

Configure your node to point to your private broker with appropriate credentials.

Map Reporting

When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.

Turning it on opens a consent card. Turn on I agree. and choose a Map Publish Interval of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.

Reports appear at meshmap.net and similar community map services.

🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published.

Direction Descripció
Uplink Messages from mesh → MQTT broker
Downlink Messages from MQTT broker → mesh

Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on.

Message Formats

MQTT carries two payload formats:

Format Descripció Use case
Protobuf Binary Meshtastic protobuf encoding Node-to-node mesh bridging
JSON Human-readable JSON on the /2/json/ topic Consumers outside the mesh (dashboards, home automation)

ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads.

Encryption & Privacy

Understanding the layered encryption model:

  1. Channel encryption happens on the mesh before MQTT. If your channel has a PSK, the MQTT payload is already encrypted — the broker and any subscribers see only the ciphertext.
  2. Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard.
  3. TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping.

🔒 Security: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications.

Best Practices

  • Use channel-level encryption (PSK) on channels that bridge to MQTT
  • Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes memory)
  • Use a private broker for sensitive deployments
  • Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh
  • Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back

Troubleshooting

MQTT Not Connecting

  • Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself.
  • Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces.
  • Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443).
  • DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly.

Messages Not Bridging

  • Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway.
  • Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage.
  • Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root.
  • Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway.
  • Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in.
diff --git a/main/ca-rES/user/settings-module-admin.html b/main/ca-rES/user/settings-module-admin.html index 99c3f97e07..75ec664e15 100644 --- a/main/ca-rES/user/settings-module-admin.html +++ b/main/ca-rES/user/settings-module-admin.html @@ -1 +1 @@ - Settings — Modules & Admin | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Català
Meshtastic Docs ↗

🌐 Català — Community translation View in English

Settings — Modules & Admin

Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.

💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.

Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:

A toggle setting in the on position

A dropdown setting, expanded to show its list of options

A text field setting with a value entered

A module settings card with its title and grouped controls

Configuració de mòdul

Every module lives under Settings → Module configuration.

⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes.

MQTT module

Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.

Setting Descripció
MQTT enabled Toggle MQTT bridge
Address MQTT broker address
Username Authentication username
Password Authentication password
Encryption enabled Encrypt MQTT payloads
JSON output enabled Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS enabled Use secure connection
Root topic Base MQTT topic path
Proxy to client enabled Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy on this phone The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT
Map reporting Publish position to the public map — see the Map reporting group that follows

Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:

Setting Descripció
I agree. Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map reporting interval (seconds) How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered

See MQTT for a detailed usage guide including encryption, privacy, and broker setup.

Serial module

Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.

Setting Descripció
Serial enabled Activate serial communication
Echo enabled Echo received serial data back
Serial mode Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX GPIO pins for the serial connection
Serial baud rate Port speed
Temps esgotat How long to wait before considering an incoming message complete
Override console serial port Take over the port the debug console normally uses

External Notification module

Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.

There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.

Setting Descripció
External notification enabled Master toggle for the module
Alert message LED / buzzer / vibra Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra Which outputs fire on a received bell character
Output LED (GPIO) Pin the LED is wired to
Output LED active high Whether the LED pin is active high or low
Output buzzer (GPIO) Pin the buzzer is wired to
Output vibra (GPIO) Pin the vibration motor is wired to
Use PWM buzzer Drive the buzzer with PWM, which allows tones rather than a single pitch
Use I2S as buzzer Send the alert through an I2S audio output instead
Output duration (milliseconds) How long a single alert lasts
Nag timeout (seconds) Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Ringtone The tone played on a PWM buzzer, in RTTTL. Can be imported from a file

Store & Forward module

Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.

Setting Descripció
Store & Forward enabled Activate store and forward
Heartbeat Periodically announce this node’s store-and-forward capability
Number of records Maximum stored messages
History return max Max messages to replay
History return window Time window for replay
Server Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)

💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.

Range Test module

⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.

Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.

Setting Descripció
Range test enabled Activate range testing
Sender message interval (seconds) Time between test transmissions, chosen from a dropdown of fixed intervals
Save .CSV in storage (ESP32 only) Log received test data to the node’s own filesystem. ESP32 hardware only

Telemetry module

Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).

Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.

Setting Descripció
Send Device Telemetry Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval How often to report battery, uptime and channel utilization
Environment metrics module enabled Report the attached environment sensors
Environment metrics update interval How often to report them
Environment metrics on-screen enabled Also show these readings on the device’s own display
Environment metrics use Fahrenheit Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Air quality metrics module enabled Report particulate and CO₂ sensor data
Air quality metrics update interval How often to report them
Power metrics module enabled Report the per-channel voltage and current readings
Power metrics update interval How often to report them
Power metrics on-screen enabled Also show power readings on the device’s display

See Telemetry & Sensors for supported sensors and configuration recommendations.

Canned Message module

Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.

Setting Descripció
Canned message enabled ⚠️ Deprecated in the protobuf schema
Messages Newline-separated list of messages
Send bell Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Rotary encoder #1 enabled Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port The three pins the encoder is wired to
Generate input event on Press / CW / CCW Which key event each encoder action produces
Up/Down/Select input enabled A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source ⚠️ Deprecated in the protobuf schema

Audio module

Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.

Setting Descripció
CODEC 2 enabled Activate audio module
CODEC2 sample rate Audio quality/bandwidth tradeoff
PTT pin GPIO pin for the push-to-talk button
I2S word select GPIO pin for I2S WS
I2S data in GPIO pin for I2S DIN
I2S data out GPIO pin for I2S DOUT
I2S clock GPIO pin for the I2S bit clock

ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.

Remote Hardware module

GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.

⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.

Setting Descripció
Remote Hardware enabled Activate remote GPIO access
Allow undefined pin access Allow access to any GPIO pin (security risk)
Available pins Up to 4 GPIO pins this node exposes for remote read/write

Neighbor Info module

Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.

Setting Descripció
Neighbor Info enabled Activate neighbor broadcasting
Update interval (seconds) How often to broadcast neighbor list
Transmit over LoRa Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name

See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.

Ambient Lighting module

Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.

Setting Descripció
LED state Turn the LED on or off
Current LED current limit (0–31)
Red / Green / Blue Individual color channel values (0–255)

Detection Sensor module

Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.

Setting Descripció
Detection Sensor enabled Activate detection sensor
GPIO pin to monitor GPIO pin connected to sensor
Detection trigger type How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Use INPUT_PULLUP mode Enable the pin’s internal pull-up resistor
Minimum broadcast (seconds) Minimum time between alert broadcasts
State broadcast (seconds) Periodic state broadcast interval
Send bell with alert message Include bell character in alerts
Friendly name Custom name for this sensor

Paxcounter module

People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.

Setting Descripció
Paxcounter enabled Activate people counting
Update interval (seconds) How often to report counts
Wi-Fi RSSI threshold Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE RSSI threshold The same cut-off for BLE advertisements (defaults to −80 dBm)

💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.

Status Message module

The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.

Mesh Beacon module

Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.

TAK module

Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.

Administration

Remote Administration

Remotely configure nodes that share your admin key:

  1. Select the target node in the node list.
  2. Navigate to Settings for that node.
  3. Modify configuration.
  4. Tap Save — changes are sent over the mesh.

⚠️ Important: Requires an admin key configured on both your node and the target node.

Device Actions

Settings → Administration holds five one-shot actions, each behind a confirmation dialog:

Action What it does
Set time Sends your phone’s clock to the node
Reiniciar Restarts the node
Apagar Powers the node down
Restauració dels paràmetres de fàbrica Returns every setting to its factory default
Restablir NodeDB Clears the node database. This dialog carries a Preserve Favorites? switch

⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.

Backup & Restore

Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.

Advanced

Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.

Clean Node Database

Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.

  • Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
  • Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.

The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.

Panell de depuració

Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.

App Settings

The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:

Privacy

  • Allow analytics and crash reporting — opt in or out of diagnostics.
  • Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
  • Homoglyph encoding — how look-alike characters in names are handled.

Appearance

  • Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
  • Theme and Language.
  • Show full message timestamps.

Persistence

  • A cache limit for how much history is kept.
  • Export rangetest packets, Export all packets and Export node database.

On their own

  • Node Layout — how much detail each row of the node list shows.
  • Wi-Fi Provisioning for mPWRD-OS — see Connections.
  • Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
  • System AI — appears only where app functions are available; see App Functions.

A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.

Sobre

Settings → About carries the app’s own identity rather than the node’s:

Three sections:

  • What is Meshtastic? — a short description of the project.
  • Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
  • Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.

The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.

Acknowledgements

Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.

Troubleshooting remote admin

  • “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
  • Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
  • Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
+ Settings — Modules & Admin | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Català
Meshtastic Docs ↗

🌐 Català — Community translation View in English

Settings — Modules & Admin

Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.

💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.

Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:

A toggle setting in the on position

A dropdown setting, expanded to show its list of options

A text field setting with a value entered

A module settings card with its title and grouped controls

Configuració de mòdul

Every module lives under Settings → Module configuration.

⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes.

MQTT module

Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.

Setting Descripció
MQTT enabled Toggle MQTT bridge
Address MQTT broker address
Username Authentication username
Password Authentication password
Encryption enabled Encrypt MQTT payloads
JSON output enabled Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS enabled Use secure connection
Root topic Base MQTT topic path
Proxy to client enabled Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy on this phone The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT
Map reporting Publish position to the public map — see the Map reporting group that follows

Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:

Setting Descripció
I agree. Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered

See MQTT for a detailed usage guide including encryption, privacy, and broker setup.

Serial module

Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.

Setting Descripció
Serial enabled Activate serial communication
Echo enabled Echo received serial data back
Serial mode Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX GPIO pins for the serial connection
Serial baud rate Port speed
Temps esgotat How long to wait before considering an incoming message complete
Override console serial port Take over the port the debug console normally uses

External Notification module

Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.

There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.

Setting Descripció
External notification enabled Master toggle for the module
Alert message LED / buzzer / vibra Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra Which outputs fire on a received bell character
Output LED (GPIO) Pin the LED is wired to
Output LED active high Whether the LED pin is active high or low
Output buzzer (GPIO) Pin the buzzer is wired to
Output vibra (GPIO) Pin the vibration motor is wired to
Use PWM buzzer Drive the buzzer with PWM, which allows tones rather than a single pitch
Use I2S as buzzer Send the alert through an I2S audio output instead
GPIO Output Duration How long a single alert lasts
Nag Timeout Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Ringtone The tone played on a PWM buzzer, in RTTTL. Can be imported from a file

Store & Forward module

Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.

Setting Descripció
Store & Forward enabled Activate store and forward
Heartbeat Periodically announce this node’s store-and-forward capability
Number of records Maximum stored messages
History return max Max messages to replay
History return window Time window for replay
Server Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)

💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.

Range Test module

⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.

Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.

Setting Descripció
Range test enabled Activate range testing
Sender Interval Time between test transmissions, chosen from a dropdown of fixed intervals
Save .CSV in storage (ESP32 only) Log received test data to the node’s own filesystem. ESP32 hardware only

Telemetry module

Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).

Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.

Setting Descripció
Send Device Telemetry Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval How often to report battery, uptime and channel utilization
Environment metrics module enabled Report the attached environment sensors
Environment metrics update interval How often to report them
Environment metrics on-screen enabled Also show these readings on the device’s own display
Environment metrics use Fahrenheit Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Air quality metrics module enabled Report particulate and CO₂ sensor data
Air quality metrics update interval How often to report them
Power metrics module enabled Report the per-channel voltage and current readings
Power metrics update interval How often to report them
Power metrics on-screen enabled Also show power readings on the device’s display

See Telemetry & Sensors for supported sensors and configuration recommendations.

Canned Message module

Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.

Setting Descripció
Canned message enabled ⚠️ Deprecated in the protobuf schema
Messages Newline-separated list of messages
Send bell Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Rotary encoder #1 enabled Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port The three pins the encoder is wired to
Generate input event on Press / CW / CCW Which key event each encoder action produces
Up/Down/Select input enabled A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source ⚠️ Deprecated in the protobuf schema

Audio module

Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.

Setting Descripció
CODEC 2 enabled Activate audio module
CODEC2 sample rate Audio quality/bandwidth tradeoff
PTT pin GPIO pin for the push-to-talk button
I2S word select GPIO pin for I2S WS
I2S data in GPIO pin for I2S DIN
I2S data out GPIO pin for I2S DOUT
I2S clock GPIO pin for the I2S bit clock

ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.

Remote Hardware module

GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.

⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.

Setting Descripció
Remote Hardware enabled Activate remote GPIO access
Allow undefined pin access Allow access to any GPIO pin (security risk)
Available pins Up to 4 GPIO pins this node exposes for remote read/write

Neighbor Info module

Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.

Setting Descripció
Neighbor Info enabled Activate neighbor broadcasting
Update Interval How often to broadcast neighbor list
Transmit over LoRa Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name

See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.

Ambient Lighting module

Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.

Setting Descripció
LED state Turn the LED on or off
Current LED current limit (0–31)
Red / Green / Blue Individual color channel values (0–255)

Detection Sensor module

Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.

Setting Descripció
Detection Sensor enabled Activate detection sensor
GPIO pin to monitor GPIO pin connected to sensor
Detection trigger type How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Use INPUT_PULLUP mode Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts Minimum time between alert broadcasts
State Broadcast Interval Periodic state broadcast interval
Send bell with alert message Include bell character in alerts
Friendly name Custom name for this sensor

Paxcounter module

People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.

Setting Descripció
Paxcounter enabled Activate people counting
Update Interval How often to report counts
WiFi Threshold (dBm) Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm) The same cut-off for BLE advertisements (defaults to −80 dBm)

💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.

Status Message module

The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.

Mesh Beacon module

Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.

TAK module

Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.

Administration

Remote Administration

Remotely configure nodes that share your admin key:

  1. Select the target node in the node list.
  2. Navigate to Settings for that node.
  3. Modify configuration.
  4. Tap Save — changes are sent over the mesh.

⚠️ Important: Requires an admin key configured on both your node and the target node.

Device Actions

Settings → Administration holds five one-shot actions, each behind a confirmation dialog:

Action What it does
Set time Sends your phone’s clock to the node
Reiniciar Restarts the node
Apagar Powers the node down
Restauració dels paràmetres de fàbrica Returns every setting to its factory default
Restablir NodeDB Clears the node database. This dialog carries a Preserve Favorites? switch

⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.

Backup & Restore

Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.

Advanced

Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.

Clean Node Database

Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.

  • Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
  • Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.

The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.

Panell de depuració

Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.

App Settings

The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:

Privacy

  • Allow analytics and crash reporting — opt in or out of diagnostics.
  • Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
  • Homoglyph encoding — how look-alike characters in names are handled.

Appearance

  • Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
  • Theme and Language.
  • Show full message timestamps.

Persistence

  • A cache limit for how much history is kept.
  • Export rangetest packets, Export all packets and Export node database.

On their own

  • Node Layout — how much detail each row of the node list shows.
  • Wi-Fi Provisioning for mPWRD-OS — see Connections.
  • Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
  • System AI — appears only where app functions are available; see App Functions.

A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.

Sobre

Settings → About carries the app’s own identity rather than the node’s:

Three sections:

  • What is Meshtastic? — a short description of the project.
  • Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
  • Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.

The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.

Acknowledgements

Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.

Troubleshooting remote admin

  • “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
  • Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
  • Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
diff --git a/main/ca-rES/user/settings-radio-user.html b/main/ca-rES/user/settings-radio-user.html index 3ce73af404..e99381264c 100644 --- a/main/ca-rES/user/settings-radio-user.html +++ b/main/ca-rES/user/settings-radio-user.html @@ -1 +1 @@ - Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Català
Meshtastic Docs ↗

🌐 Català — Community translation View in English

Settings — Radio & User

Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How these screens work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Descripció
Long Name Your display name (up to 39 characters)
Short Name 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Unmessageable Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur node (Ham) Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in.

Configuration

Device Config

On Settings → Device configuration → Device.

Setting Descripció Default
Device Role Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Rebroadcast Mode How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Node Info Broadcast Interval How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Double Tap as Button Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Enabled
LED Heartbeat Blink the status LED periodically Enabled
Time Zone POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it —
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to —

LoRa Config

On Settings → LoRa.

Setting Descripció Default
Regió Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number Unset (must configure)
Presets Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Transmit Power Transmission power (dBm); 0 = max allowed for region 0 (region max)
Frequency Override Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Use Preset On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead From preset
Coding Rate Manual mode only: 5–8. More redundancy costs airtime From preset
Bandwidth Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Frequency Slot Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmit Enabled Turning this off makes the node receive-only On
Override Duty Cycle Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
Ignore MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok to MQTT Allow your packets to be forwarded to MQTT by gateways Off
RX Boosted Gain Extra receive gain on SX126x radios; costs a little current Off
PA fan disabled Turn off the power-amplifier fan on hardware that has one Off

The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set.

Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Speed SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a modem preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Display Config

On Settings → Device configuration → Display. These control the node’s own screen, not the app’s.

Setting Descripció
Screen on for How long the display stays lit before sleeping
Carousel interval How often the node cycles between screens on its own
Display mode Screen layout/density used by the firmware
Display units Metric or Imperial on the node’s screen
Use 12h clock format Show the node’s clock as 12-hour rather than 24-hour
Bold Heading Draw the screen’s heading text in bold
Flip screen Rotate the display 180° for an inverted mounting
OLED type Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED
Wake on tap or motion Light the screen when the node is tapped or moved
Compass orientation Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each
Always point north Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Position Config

On Settings → Device configuration → Position.

Setting Descripció
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the node asks its GPS for a fix
Broadcast Interval How often the position is shared with the mesh
Smart Position Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Fixed Position Use a manually entered latitude, longitude and altitude instead of the GPS
Position Flags A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Power Config

On Settings → Device configuration → Power.

Setting Descripció
Enable power saving mode Let the node sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the node stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC multiplier override ratio The correction factor itself, used only when the override is on
Battery INA_2XX I2C address Address of an external INA-series power sensor, if fitted

Network Config

On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node.

Setting Descripció
Wi-Fi enabled Enable the Wi-Fi node (ESP32 nodes)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Password Network password
Ethernet enabled Use a wired connection on hardware that has one
IPv4 mode DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP server Time synchronization server
rsyslog server Remote logging server

Network Config with a static IPv4 address entered

Bluetooth Config

On Settings → Device configuration → Bluetooth, on nodes with Bluetooth.

Setting Descripció
Bluetooth enabled Enable/disable BLE radio
Pairing mode Fixed PIN, Random PIN, or No PIN
Fixed PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Security Config

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

Setting Descripció
Public Key Your node’s public key (read-only)
Admin Key Keys permitted to administer this node remotely — up to three
Private Key Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it
Regenerate Private Key Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Serial console Serial console over the Stream API
Debug log API enabled Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth
Managed Mode Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.

+ Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Català
Meshtastic Docs ↗

🌐 Català — Community translation View in English

Settings — Radio & User

Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How these screens work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Descripció
Long Name Your display name (up to 39 characters)
Short Name 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Unmessageable Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur node (Ham) Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in.

Configuration

Device Config

On Settings → Device configuration → Device.

Setting Descripció Default
Device Role Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Rebroadcast Mode How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Node Info Broadcast Interval How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Double Tap as Button Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Enabled
LED Heartbeat Blink the status LED periodically Enabled
Time Zone POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it —
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to —

LoRa Config

On Settings → LoRa.

Setting Descripció Default
Regió Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number Unset (must configure)
Presets Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Transmit Power (dBm) Transmission power; 0 = max allowed for region 0 (region max)
Frequency Override Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Use Preset On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead From preset
Coding Rate Manual mode only: 5–8. More redundancy costs airtime From preset
Bandwidth Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Frequency Slot Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmit Enabled Turning this off makes the node receive-only On
Override Duty Cycle Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
Ignore MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok to MQTT Allow your packets to be forwarded to MQTT by gateways Off
RX Boosted Gain Extra receive gain on SX126x radios; costs a little current Off
PA fan disabled Turn off the power-amplifier fan on hardware that has one Off

The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set.

Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Speed SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a modem preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Display Config

On Settings → Device configuration → Display. These control the node’s own screen, not the app’s.

Setting Descripció
Screen on for How long the display stays lit before sleeping
Carousel interval How often the node cycles between screens on its own
Display mode Screen layout/density used by the firmware
Display units Metric or Imperial on the node’s screen
Use 12h clock format Show the node’s clock as 12-hour rather than 24-hour
Bold Heading Draw the screen’s heading text in bold
Flip screen Rotate the display 180° for an inverted mounting
OLED type Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED
Wake on tap or motion Light the screen when the node is tapped or moved
Compass orientation Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each
Always point north Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Position Config

On Settings → Device configuration → Position.

Setting Descripció
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the node asks its GPS for a fix
Broadcast Interval How often the position is shared with the mesh
Smart Position Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Fixed Position Use a manually entered latitude, longitude and altitude instead of the GPS
Position Flags A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Power Config

On Settings → Device configuration → Power.

Setting Descripció
Enable power saving mode Let the node sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the node stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC multiplier override ratio The correction factor itself, used only when the override is on
Battery INA_2XX I2C address Address of an external INA-series power sensor, if fitted

Network Config

On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node.

Setting Descripció
Wi-Fi enabled Enable the Wi-Fi node (ESP32 nodes)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Password Network password
Ethernet enabled Use a wired connection on hardware that has one
IPv4 mode DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP server Time synchronization server
rsyslog server Remote logging server

Network Config with a static IPv4 address entered

Bluetooth Config

On Settings → Device configuration → Bluetooth, on nodes with Bluetooth.

Setting Descripció
Bluetooth enabled Enable/disable BLE radio
Pairing mode Fixed PIN, Random PIN, or No PIN
Fixed PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Security Config

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

Setting Descripció
Public Key Your node’s public key (read-only)
Admin Key Keys permitted to administer this node remotely — up to three
Private Key Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it
Regenerate Private Key Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Serial console Serial console over the Stream API
Debug log API enabled Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth
Managed Mode Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.

diff --git a/main/cs-rCZ/user/discovery.html b/main/cs-rCZ/user/discovery.html index d606fd543c..db9e216dc6 100644 --- a/main/cs-rCZ/user/discovery.html +++ b/main/cs-rCZ/user/discovery.html @@ -5,4 +5,4 @@ ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) -

Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:.

What to look for What it means
All hops show Good SNR (green) Healthy path — messages flow reliably
One hop shows a poor SNR (orange or red) Weak link — this relay segment is fragile
Many hops (4+) Long path — consider repositioning a node to shorten it
Different path on retry Mesh is adapting — multiple routes exist (this is good!)

💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network.

Troubleshooting with Traceroute

  • No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key.
  • Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa.
  • Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position.
  • Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric.

Informace o sousedech

The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh.

Enabling Neighbor Info

  1. Navigate to Settings → Module configuration → Neighbor Info.
  2. Enable the module.
  3. Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
  4. Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air.

Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.

Viewing neighbor data

  • Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors.
  • Each neighbor entry shows the node that was directly heard and its signal quality.
  • Combine neighbor data from multiple nodes to understand the full mesh topology.

ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further.

Node list as a discovery tool

The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively.

Finding new nodes

  • Sort by Last heard to see the most recently active nodes at the top.
  • Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes.

Assessing connectivity

  • Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed.
  • Sort by Distance to find nearby nodes and verify they’re reachable.
  • Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge).

Infrastructure audit

  • Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes.
  • Check their signal quality and last-heard times to verify your infrastructure nodes are healthy.

See Nodes for full details on filtering and sorting options.

Tips for Mesh exploration

  • Start with traceroute — it gives you immediate, actionable information about a specific path.
  • Enable Neighbor Info on key nodes — especially routers and repeaters, to build a picture of the backbone.
  • Check the map — node positions on the Map combined with signal data help you understand why some links are strong and others are weak.
  • Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly.
+

Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:.

What to look for What it means
All hops show Good SNR (green) Healthy path — messages flow reliably
One hop shows a poor SNR (orange or red) Weak link — this relay segment is fragile
Many hops (4+) Long path — consider repositioning a node to shorten it
Different path on retry Mesh is adapting — multiple routes exist (this is good!)

💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network.

Troubleshooting with Traceroute

  • No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key.
  • Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa.
  • Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position.
  • Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric.

Informace o sousedech

The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh.

Enabling Neighbor Info

  1. Navigate to Settings → Module configuration → Neighbor Info.
  2. Enable the module.
  3. Set Update Interval. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
  4. Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air.

Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.

Viewing neighbor data

  • Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors.
  • Each neighbor entry shows the node that was directly heard and its signal quality.
  • Combine neighbor data from multiple nodes to understand the full mesh topology.

ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further.

Node list as a discovery tool

The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively.

Finding new nodes

  • Sort by Last heard to see the most recently active nodes at the top.
  • Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes.

Assessing connectivity

  • Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed.
  • Sort by Distance to find nearby nodes and verify they’re reachable.
  • Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge).

Infrastructure audit

  • Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes.
  • Check their signal quality and last-heard times to verify your infrastructure nodes are healthy.

See Nodes for full details on filtering and sorting options.

Tips for Mesh exploration

  • Start with traceroute — it gives you immediate, actionable information about a specific path.
  • Enable Neighbor Info on key nodes — especially routers and repeaters, to build a picture of the backbone.
  • Check the map — node positions on the Map combined with signal data help you understand why some links are strong and others are weak.
  • Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly.
diff --git a/main/cs-rCZ/user/mqtt.html b/main/cs-rCZ/user/mqtt.html index adb1fa9244..54c2cfa714 100644 --- a/main/cs-rCZ/user/mqtt.html +++ b/main/cs-rCZ/user/mqtt.html @@ -1,2 +1,2 @@ MQTT | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Čeština
Meshtastic Docs ↗

🌐 Čeština — Community translation View in English

MQTT

MQTT bridges your Meshtastic mesh network to the internet, enabling long-range communication beyond radio range.

Overview

The MQTT module connects your node to an MQTT broker, allowing:

  • Messages to reach nodes on different physical meshes via the internet
  • Integration with home automation and monitoring systems
  • Publishing node positions to the public Meshtastic map
  • Custom data pipelines for logging and alerting

How It Works 

[Your Node] → Radio → [Gateway Node with Wi-Fi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node]
-

A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh.

Nastavení

Enabling MQTT

  1. Navigate to Settings → Module configuration → MQTT.
  2. Enable the MQTT module.
  3. Configure the broker connection:
Nastavení Popis Výchozí
Address MQTT broker hostname mqtt.meshtastic.org
Username Broker authentication meshdev
Password Broker authentication large4cats
Root topic Base topic for messages msh, which the radio rewrites to msh/<REGION> once you set a region
Encryption enabled Encrypt MQTT payload Povoleno
JSON output enabled Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it Disabled
TLS enabled Secure connection to broker Disabled
Map reporting Report position to public map Disabled
Proxy to client enabled Relay MQTT through the connected phone Disabled

Connection Status and Test Connection

The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here.

Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason.

MQTT Proxy on This Phone

If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection.

ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them.

The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration.

Default Meshtastic Broker

The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing.

When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without).

🔒 Privacy: Messages on the public broker are readable by anyone subscribed. Always use channel encryption for private communications.

Private Broker

For better privacy and control, you can run your own MQTT broker:

  • Mosquitto (lightweight, open-source)
  • HiveMQ
  • EMQX

Configure your node to point to your private broker with appropriate credentials.

Map Reporting

When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.

Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.

Reports appear at meshmap.net and similar community map services.

🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published.

Direction Popis
Uplink Messages from mesh → MQTT broker
Downlink Messages from MQTT broker → mesh

Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on.

Message Formats

MQTT carries two payload formats:

Format Popis Use case
Protobuf Binary Meshtastic protobuf encoding Node-to-node mesh bridging
JSON Human-readable JSON on the /2/json/ topic Consumers outside the mesh (dashboards, home automation)

ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads.

Encryption & Privacy

Understanding the layered encryption model:

  1. Channel encryption happens on the mesh before MQTT. If your channel has a PSK, the MQTT payload is already encrypted — the broker and any subscribers see only the ciphertext.
  2. Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard.
  3. TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping.

🔒 Security: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications.

Best Practices

  • Use channel-level encryption (PSK) on channels that bridge to MQTT
  • Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes memory)
  • Use a private broker for sensitive deployments
  • Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh
  • Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back

Troubleshooting

MQTT Not Connecting

  • Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself.
  • Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces.
  • Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443).
  • DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly.

Messages Not Bridging

  • Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway.
  • Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage.
  • Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root.
  • Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway.
  • Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in.
+

A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh.

Nastavení

Enabling MQTT

  1. Navigate to Settings → Module configuration → MQTT.
  2. Enable the MQTT module.
  3. Configure the broker connection:
Nastavení Popis Výchozí
Address MQTT broker hostname mqtt.meshtastic.org
Username Broker authentication meshdev
Password Broker authentication large4cats
Root topic Base topic for messages msh, which the radio rewrites to msh/<REGION> once you set a region
Encryption enabled Encrypt MQTT payload Povoleno
JSON output enabled Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it Disabled
TLS enabled Secure connection to broker Disabled
Map reporting Report position to public map Disabled
Proxy to client enabled Relay MQTT through the connected phone Disabled

Connection Status and Test Connection

The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here.

Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason.

MQTT Proxy on This Phone

If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection.

ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them.

The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration.

Default Meshtastic Broker

The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing.

When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without).

🔒 Privacy: Messages on the public broker are readable by anyone subscribed. Always use channel encryption for private communications.

Private Broker

For better privacy and control, you can run your own MQTT broker:

  • Mosquitto (lightweight, open-source)
  • HiveMQ
  • EMQX

Configure your node to point to your private broker with appropriate credentials.

Map Reporting

When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.

Turning it on opens a consent card. Turn on I agree. and choose a Map Publish Interval of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.

Reports appear at meshmap.net and similar community map services.

🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published.

Direction Popis
Uplink Messages from mesh → MQTT broker
Downlink Messages from MQTT broker → mesh

Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on.

Message Formats

MQTT carries two payload formats:

Format Popis Use case
Protobuf Binary Meshtastic protobuf encoding Node-to-node mesh bridging
JSON Human-readable JSON on the /2/json/ topic Consumers outside the mesh (dashboards, home automation)

ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads.

Encryption & Privacy

Understanding the layered encryption model:

  1. Channel encryption happens on the mesh before MQTT. If your channel has a PSK, the MQTT payload is already encrypted — the broker and any subscribers see only the ciphertext.
  2. Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard.
  3. TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping.

🔒 Security: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications.

Best Practices

  • Use channel-level encryption (PSK) on channels that bridge to MQTT
  • Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes memory)
  • Use a private broker for sensitive deployments
  • Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh
  • Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back

Troubleshooting

MQTT Not Connecting

  • Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself.
  • Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces.
  • Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443).
  • DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly.

Messages Not Bridging

  • Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway.
  • Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage.
  • Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root.
  • Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway.
  • Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in.
diff --git a/main/cs-rCZ/user/settings-module-admin.html b/main/cs-rCZ/user/settings-module-admin.html index 87c789c04f..553e85f108 100644 --- a/main/cs-rCZ/user/settings-module-admin.html +++ b/main/cs-rCZ/user/settings-module-admin.html @@ -1 +1 @@ - Settings — Modules & Admin | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Čeština
Meshtastic Docs ↗

🌐 Čeština — Community translation View in English

Settings — Modules & Admin

Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.

💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.

Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:

A toggle setting in the on position

A dropdown setting, expanded to show its list of options

A text field setting with a value entered

A module settings card with its title and grouped controls

Nastavení modulů

Every module lives under Settings → Module configuration.

⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes.

MQTT module

Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.

Nastavení Popis
MQTT povoleno Toggle MQTT bridge
Adresa MQTT broker address
Uživatelské jméno Authentication username
Heslo Authentication password
Šifrování povoleno Encrypt MQTT payloads
JSON výstup povolen Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS povoleno Use secure connection
Kořenové téma Base MQTT topic path
Proxy na klienta povoleno Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy na tomto telefonu The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT
Hlášení mapy Publish position to the public map — see the Map reporting group that follows

Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:

Nastavení Popis
Souhlasím. Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Interval hlášení mapy How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered

See MQTT for a detailed usage guide including encryption, privacy, and broker setup.

Serial module

Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.

Nastavení Popis
Sériová komunikace povolena Activate serial communication
Povolit echo Echo received serial data back
Sériový režim Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX GPIO pins for the serial connection
Rychlost sériového přenosu Port speed
Vypršel čas spojení How long to wait before considering an incoming message complete
Přepsat sériový port komunikace Take over the port the debug console normally uses

External Notification module

Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.

There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.

Nastavení Popis
Externí oznámení povoleno Master toggle for the module
Alert message LED / buzzer / vibra Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra Which outputs fire on a received bell character
Výstupní LED (GPIO) Pin the LED is wired to
Výstupní LED aktivní při HIGH Whether the LED pin is active high or low
Výstupní pin bzučáku (GPIO) Pin the buzzer is wired to
Výstupní pin vybračního motorku (GPIO) Pin the vibration motor is wired to
Použít PWM bzučák Drive the buzzer with PWM, which allows tones rather than a single pitch
Použít I2S jako bzučák Send the alert through an I2S audio output instead
Doba trvání výstupu (v milisekundách) How long a single alert lasts
Interval opakovaného zvonění Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Vyzváněcí tón The tone played on a PWM buzzer, in RTTTL. Can be imported from a file

Store & Forward module

Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.

Nastavení Popis
Uložit a přeposlat povoleno Activate store and forward
Pulzující LED Periodically announce this node’s store-and-forward capability
Počet záznamů Maximum stored messages
Max. počet záznamů historie Max messages to replay
Časové okno historie Time window for replay
Server Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)

💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.

Range Test module

⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.

Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.

Nastavení Popis
Test pokrytí povolen Activate range testing
Interval odesílání zpráv Time between test transmissions, chosen from a dropdown of fixed intervals
Uložit .CSV do úložiště (pouze ESP32) Log received test data to the node’s own filesystem. ESP32 hardware only

Telemetry module

Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).

Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.

Nastavení Popis
Odesílat telemetrii zařízení Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Interval aktualizace metrik zařízení How often to report battery, uptime and channel utilization
Modul měření životního prostředí povolen Report the attached environment sensors
Interval aktualizace měření životního prostředí How often to report them
Zobrazení měření životního prostředí povoleno Also show these readings on the device’s own display
Měření životního prostředí používá Fahrenheit Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Modul měření kvality ovzduší povolen Report particulate and CO₂ sensor data
Interval aktualizace měření kvality ovzduší How often to report them
Modul měření spotřeby povolen Report the per-channel voltage and current readings
Interval aktualizace měření napájení How often to report them
Měření spotřeby na obrazovce povoleno Also show power readings on the device’s display

See Telemetry & Sensors for supported sensors and configuration recommendations.

Canned Message module

Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.

Nastavení Popis
Canned message enabled ⚠️ Deprecated in the protobuf schema
Zprávy Newline-separated list of messages
Odeslat zvonek Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Rotační enkodér #1 povolen Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port The three pins the encoder is wired to
Generate input event on Press / CW / CCW Which key event each encoder action produces
Vstup Nahoru/Dolů/Výběr povolen A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source ⚠️ Deprecated in the protobuf schema

Audio module

Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.

Nastavení Popis
CODEC 2 enabled Activate audio module
CODEC2 sample rate Audio quality/bandwidth tradeoff
PTT pin GPIO pin for the push-to-talk button
I2S výběr slov GPIO pin for I2S WS
I2S vstupní data GPIO pin for I2S DIN
I2S výstupní data GPIO pin for I2S DOUT
I2S clock GPIO pin for the I2S bit clock

ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.

Remote Hardware module

GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.

⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.

Nastavení Popis
Vzdálený modul povolen Activate remote GPIO access
Povolit přiřazení nedefinovaného pinu Allow access to any GPIO pin (security risk)
Dostupné piny Up to 4 GPIO pins this node exposes for remote read/write

Neighbor Info module

Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.

Nastavení Popis
Informace o sousedech povoleny Activate neighbor broadcasting
Interval aktualizace (v sekundách) How often to broadcast neighbor list
Přenos přes LoRa Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name

See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.

Ambient Lighting module

Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.

Nastavení Popis
Stav LED Turn the LED on or off
Proud LED current limit (0–31)
Red / Green / Blue Individual color channel values (0–255)

Detection Sensor module

Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.

Nastavení Popis
Detekční senzor povolen Activate detection sensor
GPIO pin ke sledování GPIO pin connected to sensor
Typ spouštění detekce How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Použít INPUT_PULLUP režim Enable the pin’s internal pull-up resistor
Minimální vysílání (sekundy) Minimum time between alert broadcasts
Vysílání stavu (v sekundách) Periodic state broadcast interval
Poslat zvonek s výstražnou zprávou Include bell character in alerts
Přezdívka Custom name for this sensor

Paxcounter module

People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.

Nastavení Popis
Paxcounter povolen Activate people counting
Interval aktualizace (v sekundách) How often to report counts
Wi-Fi RSSI threshold Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE RSSI threshold The same cut-off for BLE advertisements (defaults to −80 dBm)

💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.

Status Message module

The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.

Mesh Beacon module

Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.

TAK module

Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.

Administrace

Vzdálená administrace

Remotely configure nodes that share your admin key:

  1. Select the target node in the node list.
  2. Navigate to Settings for that node.
  3. Modify configuration.
  4. Tap Save — changes are sent over the mesh.

⚠️ Important: Requires an admin key configured on both your node and the target node.

Device Actions

Settings → Administration holds five one-shot actions, each behind a confirmation dialog:

Action What it does
Nastavení času Sends your phone’s clock to the node
Restartovat Restarts the node
Vypnout Powers the node down
Obnovení továrního nastavení Returns every setting to its factory default
Reset NodeDB Clears the node database. This dialog carries a Preserve Favorites? switch

⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.

Zálohování a obnovení

Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.

Rozšířené

Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.

Vyčistit databázi uzlů

Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.

  • Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
  • Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.

The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.

Panel pro ladění

Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.

App Settings

The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:

Privacy

  • Allow analytics and crash reporting — opt in or out of diagnostics.
  • Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
  • Homoglyph encoding — how look-alike characters in names are handled.

Appearance

  • Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
  • Theme and Language.
  • Show full message timestamps.

Persistence

  • A cache limit for how much history is kept.
  • Export rangetest packets, Export all packets and Export node database.

On their own

  • Node Layout — how much detail each row of the node list shows.
  • Wi-Fi Provisioning for mPWRD-OS — see Connections.
  • Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
  • System AI — appears only where app functions are available; see App Functions.

A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.

O aplikaci

Settings → About carries the app’s own identity rather than the node’s:

Three sections:

  • What is Meshtastic? — a short description of the project.
  • Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
  • Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.

The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.

Poděkování

Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.

Troubleshooting remote admin

  • “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
  • Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
  • Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
+ Settings — Modules & Admin | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Čeština
Meshtastic Docs ↗

🌐 Čeština — Community translation View in English

Settings — Modules & Admin

Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.

💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.

Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:

A toggle setting in the on position

A dropdown setting, expanded to show its list of options

A text field setting with a value entered

A module settings card with its title and grouped controls

Nastavení modulů

Every module lives under Settings → Module configuration.

⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes.

MQTT module

Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.

Nastavení Popis
MQTT povoleno Toggle MQTT bridge
Adresa MQTT broker address
Uživatelské jméno Authentication username
Heslo Authentication password
Šifrování povoleno Encrypt MQTT payloads
JSON výstup povolen Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS povoleno Use secure connection
Kořenové téma Base MQTT topic path
Proxy na klienta povoleno Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy na tomto telefonu The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT
Hlášení mapy Publish position to the public map — see the Map reporting group that follows

Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:

Nastavení Popis
Souhlasím. Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered

See MQTT for a detailed usage guide including encryption, privacy, and broker setup.

Serial module

Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.

Nastavení Popis
Sériová komunikace povolena Activate serial communication
Povolit echo Echo received serial data back
Sériový režim Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX GPIO pins for the serial connection
Rychlost sériového přenosu Port speed
Vypršel čas spojení How long to wait before considering an incoming message complete
Přepsat sériový port komunikace Take over the port the debug console normally uses

External Notification module

Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.

There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.

Nastavení Popis
Externí oznámení povoleno Master toggle for the module
Alert message LED / buzzer / vibra Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra Which outputs fire on a received bell character
Výstupní LED (GPIO) Pin the LED is wired to
Výstupní LED aktivní při HIGH Whether the LED pin is active high or low
Výstupní pin bzučáku (GPIO) Pin the buzzer is wired to
Výstupní pin vybračního motorku (GPIO) Pin the vibration motor is wired to
Použít PWM bzučák Drive the buzzer with PWM, which allows tones rather than a single pitch
Použít I2S jako bzučák Send the alert through an I2S audio output instead
GPIO Output Duration How long a single alert lasts
Nag Timeout Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Vyzváněcí tón The tone played on a PWM buzzer, in RTTTL. Can be imported from a file

Store & Forward module

Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.

Nastavení Popis
Uložit a přeposlat povoleno Activate store and forward
Pulzující LED Periodically announce this node’s store-and-forward capability
Počet záznamů Maximum stored messages
Max. počet záznamů historie Max messages to replay
Časové okno historie Time window for replay
Server Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)

💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.

Range Test module

⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.

Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.

Nastavení Popis
Test pokrytí povolen Activate range testing
Sender Interval Time between test transmissions, chosen from a dropdown of fixed intervals
Uložit .CSV do úložiště (pouze ESP32) Log received test data to the node’s own filesystem. ESP32 hardware only

Telemetry module

Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).

Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.

Nastavení Popis
Odesílat telemetrii zařízení Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Interval aktualizace metrik zařízení How often to report battery, uptime and channel utilization
Modul měření životního prostředí povolen Report the attached environment sensors
Interval aktualizace měření životního prostředí How often to report them
Zobrazení měření životního prostředí povoleno Also show these readings on the device’s own display
Měření životního prostředí používá Fahrenheit Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Modul měření kvality ovzduší povolen Report particulate and CO₂ sensor data
Interval aktualizace měření kvality ovzduší How often to report them
Modul měření spotřeby povolen Report the per-channel voltage and current readings
Interval aktualizace měření napájení How often to report them
Měření spotřeby na obrazovce povoleno Also show power readings on the device’s display

See Telemetry & Sensors for supported sensors and configuration recommendations.

Canned Message module

Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.

Nastavení Popis
Canned message enabled ⚠️ Deprecated in the protobuf schema
Zprávy Newline-separated list of messages
Odeslat zvonek Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Rotační enkodér #1 povolen Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port The three pins the encoder is wired to
Generate input event on Press / CW / CCW Which key event each encoder action produces
Vstup Nahoru/Dolů/Výběr povolen A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source ⚠️ Deprecated in the protobuf schema

Audio module

Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.

Nastavení Popis
CODEC 2 enabled Activate audio module
CODEC2 sample rate Audio quality/bandwidth tradeoff
PTT pin GPIO pin for the push-to-talk button
I2S výběr slov GPIO pin for I2S WS
I2S vstupní data GPIO pin for I2S DIN
I2S výstupní data GPIO pin for I2S DOUT
I2S clock GPIO pin for the I2S bit clock

ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.

Remote Hardware module

GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.

⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.

Nastavení Popis
Vzdálený modul povolen Activate remote GPIO access
Povolit přiřazení nedefinovaného pinu Allow access to any GPIO pin (security risk)
Dostupné piny Up to 4 GPIO pins this node exposes for remote read/write

Neighbor Info module

Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.

Nastavení Popis
Informace o sousedech povoleny Activate neighbor broadcasting
Interval aktualizace GPS How often to broadcast neighbor list
Přenos přes LoRa Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name

See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.

Ambient Lighting module

Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.

Nastavení Popis
Stav LED Turn the LED on or off
Proud LED current limit (0–31)
Red / Green / Blue Individual color channel values (0–255)

Detection Sensor module

Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.

Nastavení Popis
Detekční senzor povolen Activate detection sensor
GPIO pin ke sledování GPIO pin connected to sensor
Typ spouštění detekce How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Použít INPUT_PULLUP režim Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts Minimum time between alert broadcasts
State Broadcast Interval Periodic state broadcast interval
Poslat zvonek s výstražnou zprávou Include bell character in alerts
Přezdívka Custom name for this sensor

Paxcounter module

People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.

Nastavení Popis
Paxcounter povolen Activate people counting
Interval aktualizace GPS How often to report counts
WiFi Threshold (dBm) Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm) The same cut-off for BLE advertisements (defaults to −80 dBm)

💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.

Status Message module

The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.

Mesh Beacon module

Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.

TAK module

Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.

Administrace

Vzdálená administrace

Remotely configure nodes that share your admin key:

  1. Select the target node in the node list.
  2. Navigate to Settings for that node.
  3. Modify configuration.
  4. Tap Save — changes are sent over the mesh.

⚠️ Important: Requires an admin key configured on both your node and the target node.

Device Actions

Settings → Administration holds five one-shot actions, each behind a confirmation dialog:

Action What it does
Nastavení času Sends your phone’s clock to the node
Restartovat Restarts the node
Vypnout Powers the node down
Obnovení továrního nastavení Returns every setting to its factory default
Reset NodeDB Clears the node database. This dialog carries a Preserve Favorites? switch

⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.

Zálohování a obnovení

Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.

Rozšířené

Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.

Vyčistit databázi uzlů

Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.

  • Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
  • Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.

The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.

Panel pro ladění

Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.

App Settings

The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:

Privacy

  • Allow analytics and crash reporting — opt in or out of diagnostics.
  • Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
  • Homoglyph encoding — how look-alike characters in names are handled.

Appearance

  • Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
  • Theme and Language.
  • Show full message timestamps.

Persistence

  • A cache limit for how much history is kept.
  • Export rangetest packets, Export all packets and Export node database.

On their own

  • Node Layout — how much detail each row of the node list shows.
  • Wi-Fi Provisioning for mPWRD-OS — see Connections.
  • Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
  • System AI — appears only where app functions are available; see App Functions.

A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.

O aplikaci

Settings → About carries the app’s own identity rather than the node’s:

Three sections:

  • What is Meshtastic? — a short description of the project.
  • Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
  • Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.

The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.

Poděkování

Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.

Troubleshooting remote admin

  • “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
  • Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
  • Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
diff --git a/main/cs-rCZ/user/settings-radio-user.html b/main/cs-rCZ/user/settings-radio-user.html index e6b17d5db3..65d6c5a5b6 100644 --- a/main/cs-rCZ/user/settings-radio-user.html +++ b/main/cs-rCZ/user/settings-radio-user.html @@ -1 +1 @@ - Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Čeština
Meshtastic Docs ↗

🌐 Čeština — Community translation View in English

Settings — Radio & User

Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How these screens work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Nastavení Popis
Dlouhé jméno Your display name (up to 39 characters)
Krátké jméno 4-character abbreviated name
Stavová zpráva A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Nepřijímá zprávy Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur node (Ham) Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in.

Nastavení

Nastavení zařízení

On Settings → Device configuration → Device.

Nastavení Popis Výchozí
Role zařízení Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Režim opětovného vysílání How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Interval vysílání Node Info How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Dvojité klepnutí jako stisk tlačítka Treat a double tap as a button press Disabled
Okamžitý ping (trojitý stisk) Send an ad-hoc position ping on a triple click Povoleno
Blikání LED při provozu Blink the status LED periodically Povoleno
Časové pásmo POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it —
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to —

LoRa nastavení

On Settings → LoRa.

Nastavení Popis Výchozí
Region Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number Unset (must configure)
Předvolby Speed/range tradeoff LongFast
Počet skoků Maximum retransmit hops 3
Vysílací výkon Transmission power (dBm); 0 = max allowed for region 0 (region max)
Ruční nastavení frekvence Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Použít předvolbu On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead From preset
Coding Rate Manual mode only: 5–8. More redundancy costs airtime From preset
Šířka pásma Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Frekvenční slot Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Vysílání povoleno Turning this off makes the node receive-only On
Přepsat pracovní cyklus Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Vypnuto
Ignorovat MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
OK do MQTT Allow your packets to be forwarded to MQTT by gateways Vypnuto
Zvýšené zesílení přijímače (RX) Extra receive gain on SX126x radios; costs a little current Vypnuto
PA fan disabled Turn off the power-amplifier fan on hardware that has one Vypnuto

The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set.

Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Rychlost SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a modem preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Nastavení zobrazení

On Settings → Device configuration → Display. These control the node’s own screen, not the app’s.

Nastavení Popis
Obrazovka zapnutá po dobu How long the display stays lit before sleeping
Interval přepínání obrazovek How often the node cycles between screens on its own
Režim obrazovky Screen layout/density used by the firmware
Zobrazení jednotek Metric or Imperial on the node’s screen
Použít 12h formát hodin Show the node’s clock as 12-hour rather than 24-hour
Tučný nadpis Draw the screen’s heading text in bold
Překlopit obrazovku Rotate the display 180° for an inverted mounting
Typ OLED displeje Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED
Probuzení klepnutím nebo pohybem Light the screen when the node is tapped or moved
Orientace kompasu Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each
Vždy ukazovat na sever Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Nastavení pozice

On Settings → Device configuration → Position.

Nastavení Popis
Režim GPS (fyzický modul) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
Interval aktualizace GPS How often the node asks its GPS for a fix
Interval vysílání How often the position is shared with the mesh
Chytrá poloha Broadcast based on movement rather than purely on the clock
Chytrý Interval With Smart Position on, the shortest gap between broadcasts
Chytrá vzdálenost With Smart Position on, how far you must move before broadcasting
Pevná poloha Use a manually entered latitude, longitude and altitude instead of the GPS
Příznaky polohy A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Nastavení napájení

On Settings → Device configuration → Power.

Nastavení Popis
Povolit úsporný režim Let the node sleep aggressively between activity
Vypnutí při ztrátě napájení Power the device down after external power disappears
Doba super hlubokého spánku How long the deepest sleep state lasts
Minimální doba probuzení The shortest time the node stays awake once woken
Doba čekání na Bluetooth How long to wait for a phone to connect before sleeping
Přepsání násobiče ADC Turn on a manual correction for battery-voltage readings
Vlastní hodnota násobiče pro ADC The correction factor itself, used only when the override is on
Adresa INA_2XX I2C baterie Address of an external INA-series power sensor, if fitted

Nastavení sítě

On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node.

Nastavení Popis
Wi-Fi enabled Enable the Wi-Fi node (ESP32 nodes)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Heslo Network password
Ethernet povolen Use a wired connection on hardware that has one
Režim IPv4 DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP vysílání Share mesh traffic with other nodes over the local network
NTP server Time synchronization server
rsyslog server Remote logging server

Network Config with a static IPv4 address entered

Nastavení bluetooth

On Settings → Device configuration → Bluetooth, on nodes with Bluetooth.

Nastavení Popis
Bluetooth povoleno Enable/disable BLE radio
Režim párování Fixed PIN, Random PIN, or No PIN
Pevný PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Nastavení zabezpečení

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

Nastavení Popis
Veřejný klíč Your node’s public key (read-only)
Administrátorský klíč Keys permitted to administer this node remotely — up to three
Soukromý klíč Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it
Obnovit soukromý klíč Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Sériová komunikace Serial console over the Stream API
Ladící protokol API povolen Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth
Řízený režim Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set
Záloha klíčů Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Obnovit klíče Write the backed-up keys back to the node (available once a backup exists)
Smazat zálohu klíče Remove the stored key backup from this phone
Úroveň ochrany How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Zbývající počet restartů How many device boots the unlocked state survives
Hodiny do vypršení platnosti Wall-clock lifetime of the unlocked state
Limit relace (minuty) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.

+ Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Čeština
Meshtastic Docs ↗

🌐 Čeština — Community translation View in English

Settings — Radio & User

Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How these screens work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Nastavení Popis
Dlouhé jméno Your display name (up to 39 characters)
Krátké jméno 4-character abbreviated name
Stavová zpráva A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Nepřijímá zprávy Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur node (Ham) Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in.

Nastavení

Nastavení zařízení

On Settings → Device configuration → Device.

Nastavení Popis Výchozí
Role zařízení Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Režim opětovného vysílání How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Interval vysílání Node Info How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Dvojité klepnutí jako stisk tlačítka Treat a double tap as a button press Disabled
Okamžitý ping (trojitý stisk) Send an ad-hoc position ping on a triple click Povoleno
Blikání LED při provozu Blink the status LED periodically Povoleno
Časové pásmo POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it —
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to —

LoRa nastavení

On Settings → LoRa.

Nastavení Popis Výchozí
Region Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number Unset (must configure)
Předvolby Speed/range tradeoff LongFast
Počet skoků Maximum retransmit hops 3
Transmit Power (dBm) Transmission power; 0 = max allowed for region 0 (region max)
Ruční nastavení frekvence Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Použít předvolbu On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead From preset
Coding Rate Manual mode only: 5–8. More redundancy costs airtime From preset
Šířka pásma Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Frekvenční slot Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Vysílání povoleno Turning this off makes the node receive-only On
Přepsat pracovní cyklus Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Vypnuto
Ignorovat MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
OK do MQTT Allow your packets to be forwarded to MQTT by gateways Vypnuto
Zvýšené zesílení přijímače (RX) Extra receive gain on SX126x radios; costs a little current Vypnuto
PA fan disabled Turn off the power-amplifier fan on hardware that has one Vypnuto

The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set.

Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Rychlost SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a modem preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Nastavení zobrazení

On Settings → Device configuration → Display. These control the node’s own screen, not the app’s.

Nastavení Popis
Obrazovka zapnutá po dobu How long the display stays lit before sleeping
Interval přepínání obrazovek How often the node cycles between screens on its own
Režim obrazovky Screen layout/density used by the firmware
Zobrazení jednotek Metric or Imperial on the node’s screen
Použít 12h formát hodin Show the node’s clock as 12-hour rather than 24-hour
Tučný nadpis Draw the screen’s heading text in bold
Překlopit obrazovku Rotate the display 180° for an inverted mounting
Typ OLED displeje Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED
Probuzení klepnutím nebo pohybem Light the screen when the node is tapped or moved
Orientace kompasu Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each
Vždy ukazovat na sever Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Nastavení pozice

On Settings → Device configuration → Position.

Nastavení Popis
Režim GPS (fyzický modul) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
Interval aktualizace GPS How often the node asks its GPS for a fix
Interval vysílání How often the position is shared with the mesh
Chytrá poloha Broadcast based on movement rather than purely on the clock
Chytrý Interval With Smart Position on, the shortest gap between broadcasts
Chytrá vzdálenost With Smart Position on, how far you must move before broadcasting
Pevná poloha Use a manually entered latitude, longitude and altitude instead of the GPS
Příznaky polohy A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Nastavení napájení

On Settings → Device configuration → Power.

Nastavení Popis
Povolit úsporný režim Let the node sleep aggressively between activity
Vypnutí při ztrátě napájení Power the device down after external power disappears
Doba super hlubokého spánku How long the deepest sleep state lasts
Minimální doba probuzení The shortest time the node stays awake once woken
Doba čekání na Bluetooth How long to wait for a phone to connect before sleeping
Přepsání násobiče ADC Turn on a manual correction for battery-voltage readings
Vlastní hodnota násobiče pro ADC The correction factor itself, used only when the override is on
Adresa INA_2XX I2C baterie Address of an external INA-series power sensor, if fitted

Nastavení sítě

On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node.

Nastavení Popis
Wi-Fi enabled Enable the Wi-Fi node (ESP32 nodes)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Heslo Network password
Ethernet povolen Use a wired connection on hardware that has one
Režim IPv4 DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP vysílání Share mesh traffic with other nodes over the local network
NTP server Time synchronization server
rsyslog server Remote logging server

Network Config with a static IPv4 address entered

Nastavení bluetooth

On Settings → Device configuration → Bluetooth, on nodes with Bluetooth.

Nastavení Popis
Bluetooth povoleno Enable/disable BLE radio
Režim párování Fixed PIN, Random PIN, or No PIN
Pevný PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Nastavení zabezpečení

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

Nastavení Popis
Veřejný klíč Your node’s public key (read-only)
Administrátorský klíč Keys permitted to administer this node remotely — up to three
Soukromý klíč Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it
Obnovit soukromý klíč Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Sériová komunikace Serial console over the Stream API
Ladící protokol API povolen Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth
Řízený režim Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set
Záloha klíčů Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Obnovit klíče Write the backed-up keys back to the node (available once a backup exists)
Smazat zálohu klíče Remove the stored key backup from this phone
Úroveň ochrany How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Zbývající počet restartů How many device boots the unlocked state survives
Hodiny do vypršení platnosti Wall-clock lifetime of the unlocked state
Limit relace (minuty) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.

diff --git a/main/de-rDE/user/discovery.html b/main/de-rDE/user/discovery.html index 33fe134967..2e41c282dc 100644 --- a/main/de-rDE/user/discovery.html +++ b/main/de-rDE/user/discovery.html @@ -5,4 +5,4 @@ ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) -

Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:.

What to look for What it means
All hops show Good SNR (green) Healthy path — messages flow reliably
One hop shows a poor SNR (orange or red) Weak link — this relay segment is fragile
Many hops (4+) Long path — consider repositioning a node to shorten it
Different path on retry Mesh is adapting — multiple routes exist (this is good!)

💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network.

Troubleshooting with Traceroute

  • No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key.
  • Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa.
  • Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position.
  • Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric.

Nachbarinformation

The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh.

Enabling Neighbor Info

  1. Navigate to Settings → Module configuration → Neighbor Info.
  2. Enable the module.
  3. Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
  4. Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air.

Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.

Viewing neighbor data

  • Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors.
  • Each neighbor entry shows the node that was directly heard and its signal quality.
  • Combine neighbor data from multiple nodes to understand the full mesh topology.

ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further.

Node list as a discovery tool

The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively.

Finding new nodes

  • Sort by Last heard to see the most recently active nodes at the top.
  • Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes.

Assessing connectivity

  • Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed.
  • Sort by Distance to find nearby nodes and verify they’re reachable.
  • Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge).

Infrastructure audit

  • Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes.
  • Check their signal quality and last-heard times to verify your infrastructure nodes are healthy.

See Nodes for full details on filtering and sorting options.

Tips for Mesh exploration

  • Start with traceroute — it gives you immediate, actionable information about a specific path.
  • Enable Neighbor Info on key nodes — especially routers and repeaters, to build a picture of the backbone.
  • Check the map — node positions on the Map combined with signal data help you understand why some links are strong and others are weak.
  • Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly.

Verwandte Themen

+

Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:.

What to look for What it means
All hops show Good SNR (green) Healthy path — messages flow reliably
One hop shows a poor SNR (orange or red) Weak link — this relay segment is fragile
Many hops (4+) Long path — consider repositioning a node to shorten it
Different path on retry Mesh is adapting — multiple routes exist (this is good!)

💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network.

Troubleshooting with Traceroute

  • No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key.
  • Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa.
  • Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position.
  • Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric.

Nachbarinformation

The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh.

Enabling Neighbor Info

  1. Navigate to Settings → Module configuration → Neighbor Info.
  2. Enable the module.
  3. Set Update Interval. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
  4. Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air.

Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.

Viewing neighbor data

  • Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors.
  • Each neighbor entry shows the node that was directly heard and its signal quality.
  • Combine neighbor data from multiple nodes to understand the full mesh topology.

ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further.

Node list as a discovery tool

The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively.

Finding new nodes

  • Sort by Last heard to see the most recently active nodes at the top.
  • Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes.

Assessing connectivity

  • Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed.
  • Sort by Distance to find nearby nodes and verify they’re reachable.
  • Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge).

Infrastructure audit

  • Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes.
  • Check their signal quality and last-heard times to verify your infrastructure nodes are healthy.

See Nodes for full details on filtering and sorting options.

Tips for Mesh exploration

  • Start with traceroute — it gives you immediate, actionable information about a specific path.
  • Enable Neighbor Info on key nodes — especially routers and repeaters, to build a picture of the backbone.
  • Check the map — node positions on the Map combined with signal data help you understand why some links are strong and others are weak.
  • Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly.

Verwandte Themen

diff --git a/main/de-rDE/user/mqtt.html b/main/de-rDE/user/mqtt.html index 3819420dbc..d16955e6d3 100644 --- a/main/de-rDE/user/mqtt.html +++ b/main/de-rDE/user/mqtt.html @@ -1,2 +1,2 @@ MQTT | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Deutsch
Meshtastic Docs ↗

🌐 Deutsch — Community translation View in English

MQTT

MQTT bridges your Meshtastic mesh network to the internet, enabling long-range communication beyond radio range.

Übersicht

The MQTT module connects your node to an MQTT broker, allowing:

  • Messages to reach nodes on different physical meshes via the internet
  • Integration with home automation and monitoring systems
  • Publishing node positions to the public Meshtastic map
  • Custom data pipelines for logging and alerting

So funktioniert’s 

[Your Node] → Radio → [Gateway Node with Wi-Fi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node]
-

A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh.

Einstellungen

MQTT aktivieren

  1. Navigate to Settings → Module configuration → MQTT.
  2. Enable the MQTT module.
  3. Configure the broker connection:
Einstellung Beschreibung Standardwert
Address MQTT broker hostname mqtt.meshtastic.org
Username Broker authentication meshdev
Password Broker authentication large4cats
Root topic Base topic for messages msh, which the radio rewrites to msh/<REGION> once you set a region
Encryption enabled Encrypt MQTT payload Aktiviert
JSON output enabled Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it Deaktiviert
TLS enabled Secure connection to broker Deaktiviert
Map reporting Report position to public map Deaktiviert
Proxy to client enabled Relay MQTT through the connected phone Deaktiviert

Connection Status and Test Connection

The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here.

Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason.

MQTT Proxy on This Phone

If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection.

ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them.

The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration.

Default Meshtastic Broker

The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing.

When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without).

🔒 Privacy: Messages on the public broker are readable by anyone subscribed. Always use channel encryption for private communications.

Private Broker

For better privacy and control, you can run your own MQTT broker:

  • Mosquitto (lightweight, open-source)
  • HiveMQ
  • EMQX

Configure your node to point to your private broker with appropriate credentials.

Map Reporting

When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.

Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.

Reports appear at meshmap.net and similar community map services.

🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published.

Direction Beschreibung
Uplink Messages from mesh → MQTT broker
Downlink Messages from MQTT broker → mesh

Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on.

Message Formats

MQTT carries two payload formats:

Format Beschreibung Use case
Protobuf Binary Meshtastic protobuf encoding Node-to-node mesh bridging
JSON Human-readable JSON on the /2/json/ topic Consumers outside the mesh (dashboards, home automation)

ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads.

Encryption & Privacy

Understanding the layered encryption model:

  1. Channel encryption happens on the mesh before MQTT. If your channel has a PSK, the MQTT payload is already encrypted — the broker and any subscribers see only the ciphertext.
  2. Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard.
  3. TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping.

🔒 Security: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications.

Bewährte Praktiken

  • Use channel-level encryption (PSK) on channels that bridge to MQTT
  • Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes memory)
  • Use a private broker for sensitive deployments
  • Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh
  • Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back

Fehlerbehebung

MQTT Not Connecting

  • Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself.
  • Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces.
  • Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443).
  • DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly.

Messages Not Bridging

  • Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway.
  • Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage.
  • Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root.
  • Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway.
  • Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in.
+

A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh.

Einstellungen

MQTT aktivieren

  1. Navigate to Settings → Module configuration → MQTT.
  2. Enable the MQTT module.
  3. Configure the broker connection:
Einstellung Beschreibung Standardwert
Address MQTT broker hostname mqtt.meshtastic.org
Username Broker authentication meshdev
Password Broker authentication large4cats
Root topic Base topic for messages msh, which the radio rewrites to msh/<REGION> once you set a region
Encryption enabled Encrypt MQTT payload Aktiviert
JSON output enabled Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it Deaktiviert
TLS enabled Secure connection to broker Deaktiviert
Map reporting Report position to public map Deaktiviert
Proxy to client enabled Relay MQTT through the connected phone Deaktiviert

Connection Status and Test Connection

The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here.

Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason.

MQTT Proxy on This Phone

If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection.

ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them.

The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration.

Default Meshtastic Broker

The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing.

When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without).

🔒 Privacy: Messages on the public broker are readable by anyone subscribed. Always use channel encryption for private communications.

Private Broker

For better privacy and control, you can run your own MQTT broker:

  • Mosquitto (lightweight, open-source)
  • HiveMQ
  • EMQX

Configure your node to point to your private broker with appropriate credentials.

Map Reporting

When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.

Turning it on opens a consent card. Turn on I agree. and choose a Map Publish Interval of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.

Reports appear at meshmap.net and similar community map services.

🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published.

Direction Beschreibung
Uplink Messages from mesh → MQTT broker
Downlink Messages from MQTT broker → mesh

Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on.

Message Formats

MQTT carries two payload formats:

Format Beschreibung Use case
Protobuf Binary Meshtastic protobuf encoding Node-to-node mesh bridging
JSON Human-readable JSON on the /2/json/ topic Consumers outside the mesh (dashboards, home automation)

ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads.

Encryption & Privacy

Understanding the layered encryption model:

  1. Channel encryption happens on the mesh before MQTT. If your channel has a PSK, the MQTT payload is already encrypted — the broker and any subscribers see only the ciphertext.
  2. Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard.
  3. TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping.

🔒 Security: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications.

Bewährte Praktiken

  • Use channel-level encryption (PSK) on channels that bridge to MQTT
  • Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes memory)
  • Use a private broker for sensitive deployments
  • Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh
  • Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back

Fehlerbehebung

MQTT Not Connecting

  • Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself.
  • Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces.
  • Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443).
  • DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly.

Messages Not Bridging

  • Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway.
  • Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage.
  • Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root.
  • Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway.
  • Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in.
diff --git a/main/de-rDE/user/settings-module-admin.html b/main/de-rDE/user/settings-module-admin.html index ca6707f0e1..ce1ef6f509 100644 --- a/main/de-rDE/user/settings-module-admin.html +++ b/main/de-rDE/user/settings-module-admin.html @@ -1 +1 @@ - Settings — Modules & Admin | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Deutsch
Meshtastic Docs ↗

🌐 Deutsch — Community translation View in English

Settings — Modules & Admin

Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.

💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.

Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:

A toggle setting in the on position

A dropdown setting, expanded to show its list of options

A text field setting with a value entered

A module settings card with its title and grouped controls

Moduleinstellungen

Every module lives under Settings → Module configuration.

⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes.

MQTT module

Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.

Einstellung Beschreibung
MQTT aktiviert Toggle MQTT bridge
Adresse MQTT broker address
Benutzername Authentication username
Passwort Authentication password
Verschlüsselung aktiviert Encrypt MQTT payloads
JSON-Ausgabe aktiviert Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS aktiviert Use secure connection
Hauptthema Base MQTT topic path
Proxy zu Client aktiviert Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT Proxy auf diesem Handy The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT
Kartenberichte Publish position to the public map — see the Map reporting group that follows

Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:

Einstellung Beschreibung
Ich stimme zu. Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Kartenberichtsintervall (Sekunden) How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered

See MQTT for a detailed usage guide including encryption, privacy, and broker setup.

Serial module

Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.

Einstellung Beschreibung
Serielle Schnittstelle aktiviert Activate serial communication
Echo aktiviert Echo received serial data back
Serieller Modus Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX GPIO pins for the serial connection
Serielle Baudrate Port speed
Zeitlimit erreicht How long to wait before considering an incoming message complete
Seriellen Anschluss der Konsole überschreiben Take over the port the debug console normally uses

External Notification module

Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.

There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.

Einstellung Beschreibung
Externe Benachrichtigungen aktiviert Master toggle for the module
Alert message LED / buzzer / vibra Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra Which outputs fire on a received bell character
Ausgabe LED (GPIO) Pin the LED is wired to
Ausgabe LED aktiv hoch Whether the LED pin is active high or low
Ausgabe Summer (GPIO) Pin the buzzer is wired to
Ausgabe Vibration (GPIO) Pin the vibration motor is wired to
Benutze PWM Summer Drive the buzzer with PWM, which allows tones rather than a single pitch
I2S als Buzzer verwenden Send the alert through an I2S audio output instead
Ausgabedauer (GPIO) How long a single alert lasts
Nervige Verzögerung (Sekunden) Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Klingelton The tone played on a PWM buzzer, in RTTTL. Can be imported from a file

Store & Forward module

Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.

Einstellung Beschreibung
Speichern & Weiterleiten aktiviert Activate store and forward
Puls Periodically announce this node’s store-and-forward capability
Anzahl Einträge Maximum stored messages
Verlauf Rückgabewert maximal Max messages to replay
Zeitraum Rückgabewert Time window for replay
Server Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)

💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.

Range Test module

⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.

Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.

Einstellung Beschreibung
Reichweitentest aktiviert Activate range testing
Sendernachrichtenintervall (Sekunden) Time between test transmissions, chosen from a dropdown of fixed intervals
Speichere .CSV im Speicher (nur ESP32) Log received test data to the node’s own filesystem. ESP32 hardware only

Telemetry module

Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).

Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.

Einstellung Beschreibung
Gerätetelemetrie senden Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Aktualisierungsintervall für Gerätedaten How often to report battery, uptime and channel utilization
Modul Umweltdaten aktiviert Report the attached environment sensors
Aktualisierungsintervall für Umweltdaten How often to report them
Umweltdatenanzeige aktiviert Also show these readings on the device’s own display
Umweltdaten in Fahrenheit Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Modul Luftqualität aktiviert Report particulate and CO₂ sensor data
Aktualisierungsintervall der Luftqualität How often to report them
Modul Energiedaten aktiviert Report the per-channel voltage and current readings
Aktualisierungsintervall für Energiedaten How often to report them
Energiedatenanzeige aktiviert Also show power readings on the device’s display

See Telemetry & Sensors for supported sensors and configuration recommendations.

Canned Message module

Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.

Einstellung Beschreibung
Canned message enabled ⚠️ Deprecated in the protobuf schema
Nachrichten Newline-separated list of messages
Glocke senden Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Drehencoder #1 aktiviert Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port The three pins the encoder is wired to
Generate input event on Press / CW / CCW Which key event each encoder action produces
Up/Down/Select Eingang aktiviert A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source ⚠️ Deprecated in the protobuf schema

Audio module

Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.

Einstellung Beschreibung
CODEC 2 aktiviert Activate audio module
CODEC2 Abtastrate Audio quality/bandwidth tradeoff
GPIO Pin PTT GPIO pin for the push-to-talk button
I2S Wortauswahl GPIO pin for I2S WS
I2S Daten Eingang GPIO pin for I2S DIN
I2S Daten Ausgang GPIO pin for I2S DOUT
I2S Takt GPIO pin for the I2S bit clock

ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.

Remote Hardware module

GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.

⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.

Einstellung Beschreibung
Einstellung entfernte Hardware Activate remote GPIO access
Erlaube undefinierten Pin-Zugriff Allow access to any GPIO pin (security risk)
Verfügbare Pins Up to 4 GPIO pins this node exposes for remote read/write

Neighbor Info module

Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.

Einstellung Beschreibung
Nachbarinformationen aktiviert Activate neighbor broadcasting
Aktualisierungsintervall (Sekunden) How often to broadcast neighbor list
Übertragen über LoRa Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name

See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.

Ambient Lighting module

Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.

Einstellung Beschreibung
LED Zustand Turn the LED on or off
Stromstärke LED current limit (0–31)
Red / Green / Blue Individual color channel values (0–255)

Detection Sensor module

Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.

Einstellung Beschreibung
Erkennungssensor aktiviert Activate detection sensor
Zu überwachender GPIO-Pin GPIO pin connected to sensor
Typ der Erkennungsauslösung How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Eingang PULLUP Einstellung Enable the pin’s internal pull-up resistor
Minimale Übertragungszeit (Sekunden) Minimum time between alert broadcasts
Statusübertragung (Sekunden) Periodic state broadcast interval
Glocke mit Warnmeldung senden Include bell character in alerts
Anzeigename Custom name for this sensor

Paxcounter module

People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.

Einstellung Beschreibung
Besucherzähler aktiviert Activate people counting
Aktualisierungsintervall (Sekunden) How often to report counts
Wi-Fi RSSI threshold Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE RSSI threshold The same cut-off for BLE advertisements (defaults to −80 dBm)

💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.

Status Message module

The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.

Mesh Beacon module

Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.

TAK module

Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. Siehe TAK Integration für detaillierte Einrichtung und Nutzung.

Einstellung

Ferneinstellung

Remotely configure nodes that share your admin key:

  1. Select the target node in the node list.
  2. Navigate to Settings for that node.
  3. Modify configuration.
  4. Tap Save — changes are sent over the mesh.

⚠️ Important: Requires an admin key configured on both your node and the target node.

Device Actions

Settings → Administration holds five one-shot actions, each behind a confirmation dialog:

Action What it does
Set time Sends your phone’s clock to the node
Neustart Restarts the node
Herunterfahren Powers the node down
Auf Werkseinstellungen zurücksetzen Returns every setting to its factory default
Node-Datenbank zurücksetzen Clears the node database. This dialog carries a Preserve Favorites? switch

⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.

Sichern & Wiederherstellen

Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.

Fortgeschritten

Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.

Knotendatenbank leeren

Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.

  • Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
  • Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.

The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.

Debug-Ausgaben

Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.

App Einstellungen

The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:

Privacy

  • Allow analytics and crash reporting — opt in or out of diagnostics.
  • Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
  • Homoglyph encoding — how look-alike characters in names are handled.

Appearance

  • Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
  • Theme and Language.
  • Show full message timestamps.

Persistence

  • A cache limit for how much history is kept.
  • Export rangetest packets, Export all packets and Export node database.

On their own

  • Node Layout — how much detail each row of the node list shows.
  • Wi-Fi Provisioning for mPWRD-OS — see Connections.
  • Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
  • System AI — appears only where app functions are available; see App Functions.

A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.

Über

Settings → About carries the app’s own identity rather than the node’s:

Three sections:

  • What is Meshtastic? — a short description of the project.
  • Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
  • Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.

The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.

Danksagungen

Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.

Troubleshooting remote admin

  • “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
  • Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
  • Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
+ Settings — Modules & Admin | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Deutsch
Meshtastic Docs ↗

🌐 Deutsch — Community translation View in English

Settings — Modules & Admin

Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.

💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.

Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:

A toggle setting in the on position

A dropdown setting, expanded to show its list of options

A text field setting with a value entered

A module settings card with its title and grouped controls

Moduleinstellungen

Every module lives under Settings → Module configuration.

⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes.

MQTT module

Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.

Einstellung Beschreibung
MQTT aktiviert Toggle MQTT bridge
Adresse MQTT broker address
Benutzername Authentication username
Passwort Authentication password
Verschlüsselung aktiviert Encrypt MQTT payloads
JSON-Ausgabe aktiviert Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS aktiviert Use secure connection
Hauptthema Base MQTT topic path
Proxy zu Client aktiviert Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT Proxy auf diesem Handy The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT
Kartenberichte Publish position to the public map — see the Map reporting group that follows

Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:

Einstellung Beschreibung
Ich stimme zu. Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered

See MQTT for a detailed usage guide including encryption, privacy, and broker setup.

Serial module

Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.

Einstellung Beschreibung
Serielle Schnittstelle aktiviert Activate serial communication
Echo aktiviert Echo received serial data back
Serieller Modus Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX GPIO pins for the serial connection
Serielle Baudrate Port speed
Zeitlimit erreicht How long to wait before considering an incoming message complete
Seriellen Anschluss der Konsole überschreiben Take over the port the debug console normally uses

External Notification module

Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.

There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.

Einstellung Beschreibung
Externe Benachrichtigungen aktiviert Master toggle for the module
Alert message LED / buzzer / vibra Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra Which outputs fire on a received bell character
Ausgabe LED (GPIO) Pin the LED is wired to
Ausgabe LED aktiv hoch Whether the LED pin is active high or low
Ausgabe Summer (GPIO) Pin the buzzer is wired to
Ausgabe Vibration (GPIO) Pin the vibration motor is wired to
Benutze PWM Summer Drive the buzzer with PWM, which allows tones rather than a single pitch
I2S als Buzzer verwenden Send the alert through an I2S audio output instead
GPIO Output Duration How long a single alert lasts
Nervige Verzögerung Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Klingelton The tone played on a PWM buzzer, in RTTTL. Can be imported from a file

Store & Forward module

Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.

Einstellung Beschreibung
Speichern & Weiterleiten aktiviert Activate store and forward
Puls Periodically announce this node’s store-and-forward capability
Anzahl Einträge Maximum stored messages
Verlauf Rückgabewert maximal Max messages to replay
Zeitraum Rückgabewert Time window for replay
Server Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)

💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.

Range Test module

⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.

Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.

Einstellung Beschreibung
Reichweitentest aktiviert Activate range testing
Sendeintervall Time between test transmissions, chosen from a dropdown of fixed intervals
Speichere .CSV im Speicher (nur ESP32) Log received test data to the node’s own filesystem. ESP32 hardware only

Telemetry module

Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).

Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.

Einstellung Beschreibung
Gerätetelemetrie senden Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Aktualisierungsintervall für Gerätedaten How often to report battery, uptime and channel utilization
Modul Umweltdaten aktiviert Report the attached environment sensors
Aktualisierungsintervall für Umweltdaten How often to report them
Umweltdatenanzeige aktiviert Also show these readings on the device’s own display
Umweltdaten in Fahrenheit Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Modul Luftqualität aktiviert Report particulate and CO₂ sensor data
Aktualisierungsintervall der Luftqualität How often to report them
Modul Energiedaten aktiviert Report the per-channel voltage and current readings
Aktualisierungsintervall für Energiedaten How often to report them
Energiedatenanzeige aktiviert Also show power readings on the device’s display

See Telemetry & Sensors for supported sensors and configuration recommendations.

Canned Message module

Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.

Einstellung Beschreibung
Canned message enabled ⚠️ Deprecated in the protobuf schema
Nachrichten Newline-separated list of messages
Glocke senden Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Drehencoder #1 aktiviert Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port The three pins the encoder is wired to
Generate input event on Press / CW / CCW Which key event each encoder action produces
Up/Down/Select Eingang aktiviert A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source ⚠️ Deprecated in the protobuf schema

Audio module

Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.

Einstellung Beschreibung
CODEC 2 aktiviert Activate audio module
CODEC2 Abtastrate Audio quality/bandwidth tradeoff
GPIO Pin PTT GPIO pin for the push-to-talk button
I2S Wortauswahl GPIO pin for I2S WS
I2S Daten Eingang GPIO pin for I2S DIN
I2S Daten Ausgang GPIO pin for I2S DOUT
I2S Takt GPIO pin for the I2S bit clock

ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.

Remote Hardware module

GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.

⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.

Einstellung Beschreibung
Einstellung entfernte Hardware Activate remote GPIO access
Erlaube undefinierten Pin-Zugriff Allow access to any GPIO pin (security risk)
Verfügbare Pins Up to 4 GPIO pins this node exposes for remote read/write

Neighbor Info module

Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.

Einstellung Beschreibung
Nachbarinformationen aktiviert Activate neighbor broadcasting
GPS Abfrageintervall How often to broadcast neighbor list
Übertragen über LoRa Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name

See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.

Ambient Lighting module

Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.

Einstellung Beschreibung
LED Zustand Turn the LED on or off
Stromstärke LED current limit (0–31)
Red / Green / Blue Individual color channel values (0–255)

Detection Sensor module

Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.

Einstellung Beschreibung
Erkennungssensor aktiviert Activate detection sensor
Zu überwachender GPIO-Pin GPIO pin connected to sensor
Typ der Erkennungsauslösung How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Eingang PULLUP Einstellung Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts Minimum time between alert broadcasts
Übertragungsintervall Periodic state broadcast interval
Glocke mit Warnmeldung senden Include bell character in alerts
Anzeigename Custom name for this sensor

Paxcounter module

People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.

Einstellung Beschreibung
Besucherzähler aktiviert Activate people counting
GPS Abfrageintervall How often to report counts
WiFi Threshold (dBm) Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm) The same cut-off for BLE advertisements (defaults to −80 dBm)

💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.

Status Message module

The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.

Mesh Beacon module

Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.

TAK module

Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. Siehe TAK Integration für detaillierte Einrichtung und Nutzung.

Einstellung

Ferneinstellung

Remotely configure nodes that share your admin key:

  1. Select the target node in the node list.
  2. Navigate to Settings for that node.
  3. Modify configuration.
  4. Tap Save — changes are sent over the mesh.

⚠️ Important: Requires an admin key configured on both your node and the target node.

Device Actions

Settings → Administration holds five one-shot actions, each behind a confirmation dialog:

Action What it does
Set time Sends your phone’s clock to the node
Neustart Restarts the node
Herunterfahren Powers the node down
Auf Werkseinstellungen zurücksetzen Returns every setting to its factory default
Node-Datenbank zurücksetzen Clears the node database. This dialog carries a Preserve Favorites? switch

⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.

Sichern & Wiederherstellen

Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.

Fortgeschritten

Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.

Knotendatenbank leeren

Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.

  • Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
  • Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.

The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.

Debug-Ausgaben

Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.

App Einstellungen

The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:

Privacy

  • Allow analytics and crash reporting — opt in or out of diagnostics.
  • Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
  • Homoglyph encoding — how look-alike characters in names are handled.

Appearance

  • Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
  • Theme and Language.
  • Show full message timestamps.

Persistence

  • A cache limit for how much history is kept.
  • Export rangetest packets, Export all packets and Export node database.

On their own

  • Node Layout — how much detail each row of the node list shows.
  • Wi-Fi Provisioning for mPWRD-OS — see Connections.
  • Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
  • System AI — appears only where app functions are available; see App Functions.

A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.

Über

Settings → About carries the app’s own identity rather than the node’s:

Three sections:

  • What is Meshtastic? — a short description of the project.
  • Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
  • Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.

The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.

Danksagungen

Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.

Troubleshooting remote admin

  • “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
  • Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
  • Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
diff --git a/main/de-rDE/user/settings-radio-user.html b/main/de-rDE/user/settings-radio-user.html index 77a2c0e2e1..fadca0e7ad 100644 --- a/main/de-rDE/user/settings-radio-user.html +++ b/main/de-rDE/user/settings-radio-user.html @@ -1 +1 @@ - Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Deutsch
Meshtastic Docs ↗

🌐 Deutsch — Community translation View in English

Settings — Radio & User

Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How these screens work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Bildschirmfoto
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

Benutzereinstellungen

User Profile

On Settings → User.

Einstellung Beschreibung
Langer Name Your display name (up to 39 characters)
Kurzname 4-character abbreviated name
Statusmeldung A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Nicht erreichbar Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur node (Ham) Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in.

Einstellungen

Geräteeinstellungen

On Settings → Device configuration → Device.

Einstellung Beschreibung Standardwert
Geräterolle Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first ‘CLIENT’
Weiterleitungsmodus How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Knoteninfo Übertragungsintervall How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Doppelklick als Taste Treat a double tap as a button press Deaktiviert
Dreifachklick für Ping Send an ad-hoc position ping on a triple click Aktiviert
Puls LED Blink the status LED periodically Aktiviert
Zeitzone POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it —
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to —

LoRa Einstellungen

On Settings → LoRa.

Einstellung Beschreibung Standardwert
Region Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number Unset (must configure)
Voreinstellungen Speed/range tradeoff LongFast
Anzahl der Weiterleitungen Maximum retransmit hops 3
Sendeleistung Transmission power (dBm); 0 = max allowed for region 0 (region max)
Frequenz überschreiben Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Voreinstellung verwenden On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spreizfaktor Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead From preset
Fehlerkorrektur Manual mode only: 5–8. More redundancy costs airtime From preset
Bandbreite Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Frequenzschlitz Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Senden aktiviert Turning this off makes the node receive-only On
Duty-Cycle überschreiben Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Aus
MQTT ignorieren Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
OK für MQTT Allow your packets to be forwarded to MQTT by gateways Aus
Empfangsverstärkung Extra receive gain on SX126x radios; costs a little current Aus
PA Fan deaktiviert Turn off the power-amplifier fan on hardware that has one Aus

The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set.

Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Bereich Geschwindigkeit SNR Limit Best For
SHORT_TURBO ~1 km 21.9 kbps −7,5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6,25 kbit/s −10 dB Suburban short-range; moderate building density
MEDIUM_FAST ~5 km 3,52 kbit/s −12.5 dB Suburban areas; moderate building density
MEDIUM_SLOW ~8 km 1,95 kbit/s −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0,34 kbit/s −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7,5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12,5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7,5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements
Long Slow ~30 km 0,18 kbit/s −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a modem preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • Einhaltung der EU-Vorschriften für 866/868 MHz: Verwenden Sie Lite Fast, Lite Slow, Narrow Fast oder Narrow Slow – diese sind für die EU-SRD-/868-MHz-Bänder mit geringerer Bandbreite optimiert.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Anzeigeeinstellungen

On Settings → Device configuration → Display. These control the node’s own screen, not the app’s.

Einstellung Beschreibung
Bildschirm eingeschaltet für How long the display stays lit before sleeping
Karussellintervall How often the node cycles between screens on its own
Anzeigemodus Screen layout/density used by the firmware
Anzeigeeinheiten Metric or Imperial on the node’s screen
12h Uhrformat verwenden Show the node’s clock as 12-hour rather than 24-hour
Fette Überschrift Draw the screen’s heading text in bold
Bildschirm spiegeln Rotate the display 180° for an inverted mounting
OLED Typ Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED
Aufwachen durch Tippen oder Bewegung Light the screen when the node is tapped or moved
Kompassausrichtung Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each
Immer nach Norden zeigen Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Standorteinstellungen

On Settings → Device configuration → Position.

Einstellung Beschreibung
GPS-Chip (Hardware) Modus Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Abfrageintervall How often the node asks its GPS for a fix
Übertragungsintervall How often the position is shared with the mesh
Intelligente Position Broadcast based on movement rather than purely on the clock
Intelligentes Intervall With Smart Position on, the shortest gap between broadcasts
Intelligente Entfernung With Smart Position on, how far you must move before broadcasting
Fester Standort Use a manually entered latitude, longitude and altitude instead of the GPS
Standort Optionen A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Energie Einstellungen

On Settings → Device configuration → Power.

Einstellung Beschreibung
Energiesparmodus aktivieren Let the node sleep aggressively between activity
Herunterfahren bei Stromausfall Power the device down after external power disappears
Dauer Supertiefschlaf How long the deepest sleep state lasts
Minimale Aufwachzeit The shortest time the node stays awake once woken
Zeit für Warten auf Bluetooth How long to wait for a phone to connect before sleeping
ADC Multiplikationsfaktor Turn on a manual correction for battery-voltage readings
ADC Multiplikator Überschreibungsverhältnis The correction factor itself, used only when the override is on
Akku INA_2XX I2C Adresse Address of an external INA-series power sensor, if fitted

Netzwerkeinstellungen

On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node.

Einstellung Beschreibung
Wi-Fi enabled Enable the Wi-Fi node (ESP32 nodes)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Passwort Netzwerkpasswort
Ethernet aktiviert Use a wired connection on hardware that has one
IPv4 Modus DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP Übertragung Share mesh traffic with other nodes over the local network
NTP Server Time synchronization server
rsyslog Server Remote logging server

Network Config with a static IPv4 address entered

Bluetooth Einstellungen

On Settings → Device configuration → Bluetooth, on nodes with Bluetooth.

Einstellung Beschreibung
Bluetooth aktiviert Enable/disable BLE radio
Kopplungsmodus Fixed PIN, Random PIN, or No PIN
Feste PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Sicherheitseinstellungen

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

Einstellung Beschreibung
Öffentlicher Schlüssel Your node’s public key (read-only)
Administrativer Schlüssel Keys permitted to administer this node remotely — up to three
Privater Schlüssel Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it
Privaten Schlüssel neu erstellen Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Serielle Konsole Serial console over the Stream API
Debug-Protokoll-API aktiviert Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth
Verwalteter Modus Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set
Schlüssel sichern Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Schutzstufe How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Stunden bis zum Ablauf Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.

+ Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Deutsch
Meshtastic Docs ↗

🌐 Deutsch — Community translation View in English

Settings — Radio & User

Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How these screens work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Bildschirmfoto
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

Benutzereinstellungen

User Profile

On Settings → User.

Einstellung Beschreibung
Langer Name Your display name (up to 39 characters)
Kurzname 4-character abbreviated name
Statusmeldung A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Nicht erreichbar Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur node (Ham) Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in.

Einstellungen

Geräteeinstellungen

On Settings → Device configuration → Device.

Einstellung Beschreibung Standardwert
Geräterolle Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first ‘CLIENT’
Weiterleitungsmodus How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Knoteninfo Übertragungsintervall How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Doppelklick als Taste Treat a double tap as a button press Deaktiviert
Dreifachklick für Ping Send an ad-hoc position ping on a triple click Aktiviert
Puls LED Blink the status LED periodically Aktiviert
Zeitzone POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it —
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to —

LoRa Einstellungen

On Settings → LoRa.

Einstellung Beschreibung Standardwert
Region Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number Unset (must configure)
Voreinstellungen Speed/range tradeoff LongFast
Anzahl der Weiterleitungen Maximum retransmit hops 3
Transmit Power (dBm) Transmission power; 0 = max allowed for region 0 (region max)
Frequenz überschreiben Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Voreinstellung verwenden On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spreizfaktor Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead From preset
Fehlerkorrektur Manual mode only: 5–8. More redundancy costs airtime From preset
Bandbreite Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Frequenzschlitz Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Senden aktiviert Turning this off makes the node receive-only On
Duty-Cycle überschreiben Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Aus
MQTT ignorieren Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
OK für MQTT Allow your packets to be forwarded to MQTT by gateways Aus
Empfangsverstärkung Extra receive gain on SX126x radios; costs a little current Aus
PA Fan deaktiviert Turn off the power-amplifier fan on hardware that has one Aus

The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set.

Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Bereich Geschwindigkeit SNR Limit Best For
SHORT_TURBO ~1 km 21.9 kbps −7,5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6,25 kbit/s −10 dB Suburban short-range; moderate building density
MEDIUM_FAST ~5 km 3,52 kbit/s −12.5 dB Suburban areas; moderate building density
MEDIUM_SLOW ~8 km 1,95 kbit/s −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0,34 kbit/s −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7,5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12,5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7,5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements
Long Slow ~30 km 0,18 kbit/s −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a modem preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • Einhaltung der EU-Vorschriften für 866/868 MHz: Verwenden Sie Lite Fast, Lite Slow, Narrow Fast oder Narrow Slow – diese sind für die EU-SRD-/868-MHz-Bänder mit geringerer Bandbreite optimiert.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Anzeigeeinstellungen

On Settings → Device configuration → Display. These control the node’s own screen, not the app’s.

Einstellung Beschreibung
Bildschirm eingeschaltet für How long the display stays lit before sleeping
Karussellintervall How often the node cycles between screens on its own
Anzeigemodus Screen layout/density used by the firmware
Anzeigeeinheiten Metric or Imperial on the node’s screen
12h Uhrformat verwenden Show the node’s clock as 12-hour rather than 24-hour
Fette Überschrift Draw the screen’s heading text in bold
Bildschirm spiegeln Rotate the display 180° for an inverted mounting
OLED Typ Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED
Aufwachen durch Tippen oder Bewegung Light the screen when the node is tapped or moved
Kompassausrichtung Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each
Immer nach Norden zeigen Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Standorteinstellungen

On Settings → Device configuration → Position.

Einstellung Beschreibung
GPS-Chip (Hardware) Modus Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Abfrageintervall How often the node asks its GPS for a fix
Übertragungsintervall How often the position is shared with the mesh
Intelligente Position Broadcast based on movement rather than purely on the clock
Intelligentes Intervall With Smart Position on, the shortest gap between broadcasts
Intelligente Entfernung With Smart Position on, how far you must move before broadcasting
Fester Standort Use a manually entered latitude, longitude and altitude instead of the GPS
Standort Optionen A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Energie Einstellungen

On Settings → Device configuration → Power.

Einstellung Beschreibung
Energiesparmodus aktivieren Let the node sleep aggressively between activity
Herunterfahren bei Stromausfall Power the device down after external power disappears
Dauer Supertiefschlaf How long the deepest sleep state lasts
Minimale Aufwachzeit The shortest time the node stays awake once woken
Zeit für Warten auf Bluetooth How long to wait for a phone to connect before sleeping
ADC Multiplikationsfaktor Turn on a manual correction for battery-voltage readings
ADC Multiplikator Überschreibungsverhältnis The correction factor itself, used only when the override is on
Akku INA_2XX I2C Adresse Address of an external INA-series power sensor, if fitted

Netzwerkeinstellungen

On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node.

Einstellung Beschreibung
Wi-Fi enabled Enable the Wi-Fi node (ESP32 nodes)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Passwort Netzwerkpasswort
Ethernet aktiviert Use a wired connection on hardware that has one
IPv4 Modus DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP Übertragung Share mesh traffic with other nodes over the local network
NTP Server Time synchronization server
rsyslog Server Remote logging server

Network Config with a static IPv4 address entered

Bluetooth Einstellungen

On Settings → Device configuration → Bluetooth, on nodes with Bluetooth.

Einstellung Beschreibung
Bluetooth aktiviert Enable/disable BLE radio
Kopplungsmodus Fixed PIN, Random PIN, or No PIN
Feste PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Sicherheitseinstellungen

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

Einstellung Beschreibung
Öffentlicher Schlüssel Your node’s public key (read-only)
Administrativer Schlüssel Keys permitted to administer this node remotely — up to three
Privater Schlüssel Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it
Privaten Schlüssel neu erstellen Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Serielle Konsole Serial console over the Stream API
Debug-Protokoll-API aktiviert Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth
Verwalteter Modus Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set
Schlüssel sichern Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Schutzstufe How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Stunden bis zum Ablauf Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.

diff --git a/main/docs/ar-rSA/user/discovery.html b/main/docs/ar-rSA/user/discovery.html index cc1533fa41..c591f23a3d 100644 --- a/main/docs/ar-rSA/user/discovery.html +++ b/main/docs/ar-rSA/user/discovery.html @@ -161,7 +161,7 @@ The Neighbor Info module lets each node broadcast a list of the nodes it can **d 1. Navigate to **Settings → Module configuration → Neighbor Info**. 2. Enable the module. -3. Set **Update interval (seconds)**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. +3. Set **Update Interval**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. 4. Turn on **Transmit over LoRa**. Without it, your neighbor list goes only to MQTT and to this app, never over the air. Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. diff --git a/main/docs/ar-rSA/user/mqtt.html b/main/docs/ar-rSA/user/mqtt.html index 717aea0066..e514de1b49 100644 --- a/main/docs/ar-rSA/user/mqtt.html +++ b/main/docs/ar-rSA/user/mqtt.html @@ -90,7 +90,7 @@ Configure your node to point to your private broker with appropriate credentials When **Map reporting** is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. -Turning it on opens a consent card. Turn on **I agree.** and choose a **Map reporting interval (seconds)** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. +Turning it on opens a consent card. Turn on **I agree.** and choose a **Map Publish Interval** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at [meshmap.net](https://meshmap.net) and similar community map services. diff --git a/main/docs/ar-rSA/user/settings-module-admin.html b/main/docs/ar-rSA/user/settings-module-admin.html index 72840f8049..e5d12ac0b7 100644 --- a/main/docs/ar-rSA/user/settings-module-admin.html +++ b/main/docs/ar-rSA/user/settings-module-admin.html @@ -51,11 +51,11 @@ Turning **Map reporting** on reveals a consent card headed _Consent to Share Une via MQTT_, with an **I agree.** switch under it. The rest of the card doesn't exist on screen until you agree: - Setting | الوصف | - --------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | - I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it | - Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units | - Map reporting interval (seconds) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | + Setting | الوصف | + ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | + I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it | + Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units | + Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | See [MQTT](mqtt) for a detailed usage guide including encryption, privacy, and broker setup. @@ -80,20 +80,20 @@ Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devi There are two independent triggers — an incoming **message**, and a received **bell** character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. - Setting | الوصف | - ------------------------------------------------- | --------------------------------------------------------------------------------------------------- | - External notification enabled | Master toggle for the module | - Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | - Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | - Output LED (GPIO) | Pin the LED is wired to | - Output LED active high | Whether the LED pin is active high or low | - Output buzzer (GPIO) | Pin the buzzer is wired to | - Output vibra (GPIO) | Pin the vibration motor is wired to | - Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | - Use I2S as buzzer | Send the alert through an I2S audio output instead | - Output duration (milliseconds) | How long a single alert lasts | - Nag timeout (seconds) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | - Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | + Setting | الوصف | + --------------------------------------- | --------------------------------------------------------------------------------------------------- | + External notification enabled | Master toggle for the module | + Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | + Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | + Output LED (GPIO) | Pin the LED is wired to | + Output LED active high | Whether the LED pin is active high or low | + Output buzzer (GPIO) | Pin the buzzer is wired to | + Output vibra (GPIO) | Pin the vibration motor is wired to | + Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | + Use I2S as buzzer | Send the alert through an I2S audio output instead | + GPIO Output Duration | How long a single alert lasts | + Nag Timeout | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | + Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | ### Store & Forward module @@ -122,7 +122,7 @@ Automated range testing tool for evaluating link quality between nodes. When ena Setting | الوصف | -------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- | Range test enabled | Activate range testing | - Sender message interval (seconds) | Time between test transmissions, chosen from a dropdown of fixed intervals | + Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals | Save .CSV in storage (ESP32 only) | Log received test data to the node's own filesystem. ESP32 hardware only | ### Telemetry module @@ -195,11 +195,11 @@ GPIO control over the mesh network. Allows a remote node to read or write GPIO p Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. - Setting | الوصف | - -------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | - Neighbor Info enabled | Activate neighbor broadcasting | - Update interval (seconds) | How often to broadcast neighbor list | - Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | + Setting | الوصف | + --------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | + Neighbor Info enabled | Activate neighbor broadcasting | + Update Interval | How often to broadcast neighbor list | + Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | See [Local Mesh Discovery](discovery) for how to use neighbor data for mesh topology exploration. @@ -217,27 +217,27 @@ Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. C Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. - Setting | الوصف | - ---------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | - Detection Sensor enabled | Activate detection sensor | - GPIO pin to monitor | GPIO pin connected to sensor | - Detection trigger type | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) | - Use INPUT_PULLUP mode | Enable the pin's internal pull-up resistor | - Minimum broadcast (seconds) | Minimum time between alert broadcasts | - State broadcast (seconds) | Periodic state broadcast interval | - Send bell with alert message | Include bell character in alerts | - Friendly name | Custom name for this sensor | + Setting | الوصف | + ------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------- | + Detection Sensor enabled | Activate detection sensor | + GPIO pin to monitor | GPIO pin connected to sensor | + Detection trigger type | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) | + Use INPUT_PULLUP mode | Enable the pin's internal pull-up resistor | + Minimum time between detection broadcasts | Minimum time between alert broadcasts | + State Broadcast Interval | Periodic state broadcast interval | + Send bell with alert message | Include bell character in alerts | + Friendly name | Custom name for this sensor | ### Paxcounter module People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. - Setting | الوصف | - -------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | - Paxcounter enabled | Activate people counting | - Update interval (seconds) | How often to report counts | - Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) | - BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | + Setting | الوصف | + --------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | + Paxcounter enabled | Activate people counting | + Update Interval | How often to report counts | + WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) | + BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) | > 💡 **Tip:** Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. diff --git a/main/docs/ar-rSA/user/settings-radio-user.html b/main/docs/ar-rSA/user/settings-radio-user.html index bc9d914984..7b19d1b9fd 100644 --- a/main/docs/ar-rSA/user/settings-radio-user.html +++ b/main/docs/ar-rSA/user/settings-radio-user.html @@ -71,24 +71,24 @@ On **Settings → Device configuration → Device**. On **Settings → LoRa**. - Setting | الوصف | Default | - ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- | - الجهة | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) | - Presets | Speed/range tradeoff | LongFast | - Number of Hops | Maximum retransmit hops | 3 | - Transmit Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | - Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | - Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | - Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset | - Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | - Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset | - Frequency Slot | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) | - Transmit Enabled | Turning this off makes the node receive-only | On | - Override Duty Cycle | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | - Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | - Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | - RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | - PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | + Setting | الوصف | Default | + --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- | + الجهة | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) | + Presets | Speed/range tradeoff | LongFast | + Number of Hops | Maximum retransmit hops | 3 | + Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) | + Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | + Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | + Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset | + Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | + Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset | + Frequency Slot | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) | + Transmit Enabled | Turning this off makes the node receive-only | On | + Override Duty Cycle | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | + Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | + Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | + RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | + PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn't appear in another. Changing region can therefore leave your current preset diff --git a/main/docs/be-rBY/user/discovery.html b/main/docs/be-rBY/user/discovery.html index e100bbd4c2..5eee40d630 100644 --- a/main/docs/be-rBY/user/discovery.html +++ b/main/docs/be-rBY/user/discovery.html @@ -161,7 +161,7 @@ The Neighbor Info module lets each node broadcast a list of the nodes it can **d 1. Navigate to **Settings → Module configuration → Neighbor Info**. 2. Enable the module. -3. Set **Update interval (seconds)**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. +3. Set **Update Interval**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. 4. Turn on **Transmit over LoRa**. Without it, your neighbor list goes only to MQTT and to this app, never over the air. Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. diff --git a/main/docs/be-rBY/user/mqtt.html b/main/docs/be-rBY/user/mqtt.html index f61b3755f2..4c052eb5b5 100644 --- a/main/docs/be-rBY/user/mqtt.html +++ b/main/docs/be-rBY/user/mqtt.html @@ -90,7 +90,7 @@ Configure your node to point to your private broker with appropriate credentials When **Map reporting** is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. -Turning it on opens a consent card. Turn on **I agree.** and choose a **Map reporting interval (seconds)** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. +Turning it on opens a consent card. Turn on **I agree.** and choose a **Map Publish Interval** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at [meshmap.net](https://meshmap.net) and similar community map services. diff --git a/main/docs/be-rBY/user/settings-module-admin.html b/main/docs/be-rBY/user/settings-module-admin.html index 1edfb5f47b..7ec22ede21 100644 --- a/main/docs/be-rBY/user/settings-module-admin.html +++ b/main/docs/be-rBY/user/settings-module-admin.html @@ -51,11 +51,11 @@ Turning **Map reporting** on reveals a consent card headed _Consent to Share Une via MQTT_, with an **I agree.** switch under it. The rest of the card doesn't exist on screen until you agree: - Setting | Апісанне | - --------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | - I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it | - Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units | - Map reporting interval (seconds) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | + Setting | Апісанне | + ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | + I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it | + Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units | + Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | See [MQTT](mqtt) for a detailed usage guide including encryption, privacy, and broker setup. @@ -80,20 +80,20 @@ Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devi There are two independent triggers — an incoming **message**, and a received **bell** character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. - Setting | Апісанне | - ------------------------------------------------- | --------------------------------------------------------------------------------------------------- | - External notification enabled | Master toggle for the module | - Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | - Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | - Output LED (GPIO) | Pin the LED is wired to | - Output LED active high | Whether the LED pin is active high or low | - Output buzzer (GPIO) | Pin the buzzer is wired to | - Output vibra (GPIO) | Pin the vibration motor is wired to | - Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | - Use I2S as buzzer | Send the alert through an I2S audio output instead | - Output duration (milliseconds) | How long a single alert lasts | - Nag timeout (seconds) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | - Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | + Setting | Апісанне | + --------------------------------------- | --------------------------------------------------------------------------------------------------- | + External notification enabled | Master toggle for the module | + Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | + Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | + Output LED (GPIO) | Pin the LED is wired to | + Output LED active high | Whether the LED pin is active high or low | + Output buzzer (GPIO) | Pin the buzzer is wired to | + Output vibra (GPIO) | Pin the vibration motor is wired to | + Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | + Use I2S as buzzer | Send the alert through an I2S audio output instead | + GPIO Output Duration | How long a single alert lasts | + Nag Timeout | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | + Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | ### Store & Forward module @@ -122,7 +122,7 @@ Automated range testing tool for evaluating link quality between nodes. When ena Setting | Апісанне | -------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- | Range test enabled | Activate range testing | - Sender message interval (seconds) | Time between test transmissions, chosen from a dropdown of fixed intervals | + Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals | Save .CSV in storage (ESP32 only) | Log received test data to the node's own filesystem. ESP32 hardware only | ### Telemetry module @@ -195,11 +195,11 @@ GPIO control over the mesh network. Allows a remote node to read or write GPIO p Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. - Setting | Апісанне | - -------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | - Neighbor Info enabled | Activate neighbor broadcasting | - Update interval (seconds) | How often to broadcast neighbor list | - Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | + Setting | Апісанне | + --------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | + Neighbor Info enabled | Activate neighbor broadcasting | + Update Interval | How often to broadcast neighbor list | + Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | See [Local Mesh Discovery](discovery) for how to use neighbor data for mesh topology exploration. @@ -217,27 +217,27 @@ Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. C Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. - Setting | Апісанне | - ---------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | - Detection Sensor enabled | Activate detection sensor | - GPIO pin to monitor | GPIO pin connected to sensor | - Detection trigger type | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) | - Use INPUT_PULLUP mode | Enable the pin's internal pull-up resistor | - Minimum broadcast (seconds) | Minimum time between alert broadcasts | - State broadcast (seconds) | Periodic state broadcast interval | - Send bell with alert message | Include bell character in alerts | - Friendly name | Custom name for this sensor | + Setting | Апісанне | + ------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------- | + Detection Sensor enabled | Activate detection sensor | + GPIO pin to monitor | GPIO pin connected to sensor | + Detection trigger type | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) | + Use INPUT_PULLUP mode | Enable the pin's internal pull-up resistor | + Minimum time between detection broadcasts | Minimum time between alert broadcasts | + State Broadcast Interval | Periodic state broadcast interval | + Send bell with alert message | Include bell character in alerts | + Friendly name | Custom name for this sensor | ### Paxcounter module People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. - Setting | Апісанне | - -------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | - Paxcounter enabled | Activate people counting | - Update interval (seconds) | How often to report counts | - Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) | - BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | + Setting | Апісанне | + --------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | + Paxcounter enabled | Activate people counting | + Update Interval | How often to report counts | + WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) | + BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) | > 💡 **Tip:** Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. diff --git a/main/docs/be-rBY/user/settings-radio-user.html b/main/docs/be-rBY/user/settings-radio-user.html index 02bf6b4cf8..5310cf2670 100644 --- a/main/docs/be-rBY/user/settings-radio-user.html +++ b/main/docs/be-rBY/user/settings-radio-user.html @@ -71,24 +71,24 @@ On **Settings → Device configuration → Device**. On **Settings → LoRa**. - Setting | Апісанне | Default | - ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- | - Рэгіён | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) | - Presets | Speed/range tradeoff | LongFast | - Number of Hops | Maximum retransmit hops | 3 | - Transmit Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | - Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | - Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | - Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset | - Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | - Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset | - Frequency Slot | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) | - Transmit Enabled | Turning this off makes the node receive-only | On | - Override Duty Cycle | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | - Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | - Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | - RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | - PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | + Setting | Апісанне | Default | + --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- | + Рэгіён | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) | + Presets | Speed/range tradeoff | LongFast | + Number of Hops | Maximum retransmit hops | 3 | + Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) | + Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | + Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | + Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset | + Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | + Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset | + Frequency Slot | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) | + Transmit Enabled | Turning this off makes the node receive-only | On | + Override Duty Cycle | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | + Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | + Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | + RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | + PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn't appear in another. Changing region can therefore leave your current preset diff --git a/main/docs/bg-rBG/user/discovery.html b/main/docs/bg-rBG/user/discovery.html index e5d91ac2f1..e186c713c8 100644 --- a/main/docs/bg-rBG/user/discovery.html +++ b/main/docs/bg-rBG/user/discovery.html @@ -161,7 +161,7 @@ The Neighbor Info module lets each node broadcast a list of the nodes it can **d 1. Navigate to **Settings → Module configuration → Neighbor Info**. 2. Enable the module. -3. Set **Update interval (seconds)**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. +3. Set **Update Interval**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. 4. Turn on **Transmit over LoRa**. Without it, your neighbor list goes only to MQTT and to this app, never over the air. Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. diff --git a/main/docs/bg-rBG/user/mqtt.html b/main/docs/bg-rBG/user/mqtt.html index 0b54fb0c2d..8f1bcd2af6 100644 --- a/main/docs/bg-rBG/user/mqtt.html +++ b/main/docs/bg-rBG/user/mqtt.html @@ -90,7 +90,7 @@ Configure your node to point to your private broker with appropriate credentials When **Map reporting** is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. -Turning it on opens a consent card. Turn on **I agree.** and choose a **Map reporting interval (seconds)** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. +Turning it on opens a consent card. Turn on **I agree.** and choose a **Map Publish Interval** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at [meshmap.net](https://meshmap.net) and similar community map services. diff --git a/main/docs/bg-rBG/user/settings-module-admin.html b/main/docs/bg-rBG/user/settings-module-admin.html index 409a0db6b6..d0aaa51c08 100644 --- a/main/docs/bg-rBG/user/settings-module-admin.html +++ b/main/docs/bg-rBG/user/settings-module-admin.html @@ -51,11 +51,11 @@ Turning **Map reporting** on reveals a consent card headed _Consent to Share Une via MQTT_, with an **I agree.** switch under it. The rest of the card doesn't exist on screen until you agree: - Настройка | Описание | - --------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | - Съгласен съм. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it | - Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units | - Map reporting interval (seconds) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | + Настройка | Описание | + ----------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | + Съгласен съм. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it | + Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units | + Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | See [MQTT](mqtt) for a detailed usage guide including encryption, privacy, and broker setup. @@ -80,20 +80,20 @@ Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devi There are two independent triggers — an incoming **message**, and a received **bell** character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. - Настройка | Описание | - ------------------------------------------------- | --------------------------------------------------------------------------------------------------- | - Външните известия са активирани | Master toggle for the module | - Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | - Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | - Output LED (GPIO) | Pin the LED is wired to | - Output LED active high | Whether the LED pin is active high or low | - Output buzzer (GPIO) | Pin the buzzer is wired to | - Output vibra (GPIO) | Pin the vibration motor is wired to | - Използване на PWM зумер | Drive the buzzer with PWM, which allows tones rather than a single pitch | - Use I2S as buzzer | Send the alert through an I2S audio output instead | - Output duration (milliseconds) | How long a single alert lasts | - Nag timeout (seconds) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | - Тон на звънене | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | + Настройка | Описание | + --------------------------------------- | --------------------------------------------------------------------------------------------------- | + Външните известия са активирани | Master toggle for the module | + Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | + Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | + Output LED (GPIO) | Pin the LED is wired to | + Output LED active high | Whether the LED pin is active high or low | + Output buzzer (GPIO) | Pin the buzzer is wired to | + Output vibra (GPIO) | Pin the vibration motor is wired to | + Използване на PWM зумер | Drive the buzzer with PWM, which allows tones rather than a single pitch | + Use I2S as buzzer | Send the alert through an I2S audio output instead | + GPIO Output Duration | How long a single alert lasts | + Nag Timeout | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | + Тон на звънене | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | ### Store & Forward module @@ -122,7 +122,7 @@ Automated range testing tool for evaluating link quality between nodes. When ena Настройка | Описание | -------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- | Тест на обхвата е активиран | Activate range testing | - Sender message interval (seconds) | Time between test transmissions, chosen from a dropdown of fixed intervals | + Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals | Запазване на .CSV в хранилище (само за ESP32) | Log received test data to the node's own filesystem. ESP32 hardware only | ### Telemetry module @@ -195,11 +195,11 @@ GPIO control over the mesh network. Allows a remote node to read or write GPIO p Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. - Настройка | Описание | - ------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------ | - Neighbor Info enabled | Activate neighbor broadcasting | - Интервал на актуализиране (секунди) | How often to broadcast neighbor list | - Предаване през LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | + Настройка | Описание | + ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | + Neighbor Info enabled | Activate neighbor broadcasting | + Интервал на актуализиране | How often to broadcast neighbor list | + Предаване през LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | See [Local Mesh Discovery](discovery) for how to use neighbor data for mesh topology exploration. @@ -223,8 +223,8 @@ Turns your node into a motion or door sensor alert system. When a GPIO pin detec GPIO pin to monitor | GPIO pin connected to sensor | Detection trigger type | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) | Използване на режим INPUT_PULLUP | Enable the pin's internal pull-up resistor | - Minimum broadcast (seconds) | Minimum time between alert broadcasts | - State broadcast (seconds) | Periodic state broadcast interval | + Minimum time between detection broadcasts | Minimum time between alert broadcasts | + State Broadcast Interval | Periodic state broadcast interval | Send bell with alert message | Include bell character in alerts | Приятелско име | Custom name for this sensor | @@ -232,12 +232,12 @@ Turns your node into a motion or door sensor alert system. When a GPIO pin detec People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. - Настройка | Описание | - ------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------- | - Paxcounter е активиран | Activate people counting | - Интервал на актуализиране (секунди) | How often to report counts | - Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) | - BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | + Настройка | Описание | + --------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | + Paxcounter е активиран | Activate people counting | + Интервал на актуализиране | How often to report counts | + WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) | + BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) | > 💡 **Tip:** Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. diff --git a/main/docs/bg-rBG/user/settings-radio-user.html b/main/docs/bg-rBG/user/settings-radio-user.html index 582583dd7e..2258ae7c4f 100644 --- a/main/docs/bg-rBG/user/settings-radio-user.html +++ b/main/docs/bg-rBG/user/settings-radio-user.html @@ -76,7 +76,7 @@ On **Settings → LoRa**. Регион | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) | Предварително зададени | Speed/range tradeoff | LongFast | Брой отскоци | Maximum retransmit hops | 3 | - Мощност на предаване | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | + Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) | Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | Използване на предварително зададени настройки | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset | diff --git a/main/docs/ca-rES/user/discovery.html b/main/docs/ca-rES/user/discovery.html index 15c6d16a48..fcc97b17be 100644 --- a/main/docs/ca-rES/user/discovery.html +++ b/main/docs/ca-rES/user/discovery.html @@ -161,7 +161,7 @@ The Neighbor Info module lets each node broadcast a list of the nodes it can **d 1. Navigate to **Settings → Module configuration → Neighbor Info**. 2. Enable the module. -3. Set **Update interval (seconds)**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. +3. Set **Update Interval**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. 4. Turn on **Transmit over LoRa**. Without it, your neighbor list goes only to MQTT and to this app, never over the air. Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. diff --git a/main/docs/ca-rES/user/mqtt.html b/main/docs/ca-rES/user/mqtt.html index a26d94c047..d09e4c21da 100644 --- a/main/docs/ca-rES/user/mqtt.html +++ b/main/docs/ca-rES/user/mqtt.html @@ -90,7 +90,7 @@ Configure your node to point to your private broker with appropriate credentials When **Map reporting** is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. -Turning it on opens a consent card. Turn on **I agree.** and choose a **Map reporting interval (seconds)** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. +Turning it on opens a consent card. Turn on **I agree.** and choose a **Map Publish Interval** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at [meshmap.net](https://meshmap.net) and similar community map services. diff --git a/main/docs/ca-rES/user/settings-module-admin.html b/main/docs/ca-rES/user/settings-module-admin.html index 0c11ce620e..a4febab289 100644 --- a/main/docs/ca-rES/user/settings-module-admin.html +++ b/main/docs/ca-rES/user/settings-module-admin.html @@ -51,11 +51,11 @@ Turning **Map reporting** on reveals a consent card headed _Consent to Share Une via MQTT_, with an **I agree.** switch under it. The rest of the card doesn't exist on screen until you agree: - Setting | Descripció | - --------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | - I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it | - Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units | - Map reporting interval (seconds) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | + Setting | Descripció | + ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | + I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it | + Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units | + Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | See [MQTT](mqtt) for a detailed usage guide including encryption, privacy, and broker setup. @@ -80,20 +80,20 @@ Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devi There are two independent triggers — an incoming **message**, and a received **bell** character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. - Setting | Descripció | - ------------------------------------------------- | --------------------------------------------------------------------------------------------------- | - External notification enabled | Master toggle for the module | - Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | - Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | - Output LED (GPIO) | Pin the LED is wired to | - Output LED active high | Whether the LED pin is active high or low | - Output buzzer (GPIO) | Pin the buzzer is wired to | - Output vibra (GPIO) | Pin the vibration motor is wired to | - Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | - Use I2S as buzzer | Send the alert through an I2S audio output instead | - Output duration (milliseconds) | How long a single alert lasts | - Nag timeout (seconds) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | - Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | + Setting | Descripció | + --------------------------------------- | --------------------------------------------------------------------------------------------------- | + External notification enabled | Master toggle for the module | + Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | + Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | + Output LED (GPIO) | Pin the LED is wired to | + Output LED active high | Whether the LED pin is active high or low | + Output buzzer (GPIO) | Pin the buzzer is wired to | + Output vibra (GPIO) | Pin the vibration motor is wired to | + Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | + Use I2S as buzzer | Send the alert through an I2S audio output instead | + GPIO Output Duration | How long a single alert lasts | + Nag Timeout | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | + Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | ### Store & Forward module @@ -122,7 +122,7 @@ Automated range testing tool for evaluating link quality between nodes. When ena Setting | Descripció | -------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- | Range test enabled | Activate range testing | - Sender message interval (seconds) | Time between test transmissions, chosen from a dropdown of fixed intervals | + Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals | Save .CSV in storage (ESP32 only) | Log received test data to the node's own filesystem. ESP32 hardware only | ### Telemetry module @@ -195,11 +195,11 @@ GPIO control over the mesh network. Allows a remote node to read or write GPIO p Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. - Setting | Descripció | - -------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | - Neighbor Info enabled | Activate neighbor broadcasting | - Update interval (seconds) | How often to broadcast neighbor list | - Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | + Setting | Descripció | + --------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | + Neighbor Info enabled | Activate neighbor broadcasting | + Update Interval | How often to broadcast neighbor list | + Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | See [Local Mesh Discovery](discovery) for how to use neighbor data for mesh topology exploration. @@ -217,27 +217,27 @@ Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. C Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. - Setting | Descripció | - ---------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | - Detection Sensor enabled | Activate detection sensor | - GPIO pin to monitor | GPIO pin connected to sensor | - Detection trigger type | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) | - Use INPUT_PULLUP mode | Enable the pin's internal pull-up resistor | - Minimum broadcast (seconds) | Minimum time between alert broadcasts | - State broadcast (seconds) | Periodic state broadcast interval | - Send bell with alert message | Include bell character in alerts | - Friendly name | Custom name for this sensor | + Setting | Descripció | + ------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------- | + Detection Sensor enabled | Activate detection sensor | + GPIO pin to monitor | GPIO pin connected to sensor | + Detection trigger type | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) | + Use INPUT_PULLUP mode | Enable the pin's internal pull-up resistor | + Minimum time between detection broadcasts | Minimum time between alert broadcasts | + State Broadcast Interval | Periodic state broadcast interval | + Send bell with alert message | Include bell character in alerts | + Friendly name | Custom name for this sensor | ### Paxcounter module People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. - Setting | Descripció | - -------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | - Paxcounter enabled | Activate people counting | - Update interval (seconds) | How often to report counts | - Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) | - BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | + Setting | Descripció | + --------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | + Paxcounter enabled | Activate people counting | + Update Interval | How often to report counts | + WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) | + BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) | > 💡 **Tip:** Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. diff --git a/main/docs/ca-rES/user/settings-radio-user.html b/main/docs/ca-rES/user/settings-radio-user.html index 51b6923cfc..642d31ea42 100644 --- a/main/docs/ca-rES/user/settings-radio-user.html +++ b/main/docs/ca-rES/user/settings-radio-user.html @@ -71,24 +71,24 @@ On **Settings → Device configuration → Device**. On **Settings → LoRa**. - Setting | Descripció | Default | - ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- | - Regió | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) | - Presets | Speed/range tradeoff | LongFast | - Number of Hops | Maximum retransmit hops | 3 | - Transmit Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | - Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | - Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | - Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset | - Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | - Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset | - Frequency Slot | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) | - Transmit Enabled | Turning this off makes the node receive-only | On | - Override Duty Cycle | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | - Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | - Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | - RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | - PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | + Setting | Descripció | Default | + --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- | + Regió | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) | + Presets | Speed/range tradeoff | LongFast | + Number of Hops | Maximum retransmit hops | 3 | + Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) | + Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | + Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | + Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset | + Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | + Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset | + Frequency Slot | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) | + Transmit Enabled | Turning this off makes the node receive-only | On | + Override Duty Cycle | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | + Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | + Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | + RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | + PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn't appear in another. Changing region can therefore leave your current preset diff --git a/main/docs/cs-rCZ/user/discovery.html b/main/docs/cs-rCZ/user/discovery.html index c379fd52a7..d04b1e7abf 100644 --- a/main/docs/cs-rCZ/user/discovery.html +++ b/main/docs/cs-rCZ/user/discovery.html @@ -161,7 +161,7 @@ The Neighbor Info module lets each node broadcast a list of the nodes it can **d 1. Navigate to **Settings → Module configuration → Neighbor Info**. 2. Enable the module. -3. Set **Update interval (seconds)**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. +3. Set **Update Interval**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. 4. Turn on **Transmit over LoRa**. Without it, your neighbor list goes only to MQTT and to this app, never over the air. Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. diff --git a/main/docs/cs-rCZ/user/mqtt.html b/main/docs/cs-rCZ/user/mqtt.html index 2efb785d8e..6787b80d31 100644 --- a/main/docs/cs-rCZ/user/mqtt.html +++ b/main/docs/cs-rCZ/user/mqtt.html @@ -90,7 +90,7 @@ Configure your node to point to your private broker with appropriate credentials When **Map reporting** is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. -Turning it on opens a consent card. Turn on **I agree.** and choose a **Map reporting interval (seconds)** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. +Turning it on opens a consent card. Turn on **I agree.** and choose a **Map Publish Interval** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at [meshmap.net](https://meshmap.net) and similar community map services. diff --git a/main/docs/cs-rCZ/user/settings-module-admin.html b/main/docs/cs-rCZ/user/settings-module-admin.html index c258e0c7a8..b57a79b58a 100644 --- a/main/docs/cs-rCZ/user/settings-module-admin.html +++ b/main/docs/cs-rCZ/user/settings-module-admin.html @@ -55,7 +55,7 @@ until you agree: -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | Souhlasím. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units | - Interval hlášení mapy | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | + Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | See [MQTT](mqtt) for a detailed usage guide including encryption, privacy, and broker setup. @@ -91,8 +91,8 @@ and each can drive the LED, the buzzer and the vibration motor separately, givin Výstupní pin vybračního motorku (GPIO) | Pin the vibration motor is wired to | Použít PWM bzučák | Drive the buzzer with PWM, which allows tones rather than a single pitch | Použít I2S jako bzučák | Send the alert through an I2S audio output instead | - Doba trvání výstupu (v milisekundách) | How long a single alert lasts | - Interval opakovaného zvonění | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | + GPIO Output Duration | How long a single alert lasts | + Nag Timeout | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | Vyzváněcí tón | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | ### Store & Forward module @@ -122,7 +122,7 @@ Automated range testing tool for evaluating link quality between nodes. When ena Nastavení | Popis | ------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------- | Test pokrytí povolen | Activate range testing | - Interval odesílání zpráv | Time between test transmissions, chosen from a dropdown of fixed intervals | + Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals | Uložit .CSV do úložiště (pouze ESP32) | Log received test data to the node's own filesystem. ESP32 hardware only | ### Telemetry module @@ -195,11 +195,11 @@ GPIO control over the mesh network. Allows a remote node to read or write GPIO p Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. - Nastavení | Popis | - ----------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | - Informace o sousedech povoleny | Activate neighbor broadcasting | - Interval aktualizace (v sekundách) | How often to broadcast neighbor list | - Přenos přes LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | + Nastavení | Popis | + ------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------ | + Informace o sousedech povoleny | Activate neighbor broadcasting | + Interval aktualizace GPS | How often to broadcast neighbor list | + Přenos přes LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | See [Local Mesh Discovery](discovery) for how to use neighbor data for mesh topology exploration. @@ -217,27 +217,27 @@ Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. C Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. - Nastavení | Popis | - ----------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | - Detekční senzor povolen | Activate detection sensor | - GPIO pin ke sledování | GPIO pin connected to sensor | - Typ spouštění detekce | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) | - Použít INPUT_PULLUP režim | Enable the pin's internal pull-up resistor | - Minimální vysílání (sekundy) | Minimum time between alert broadcasts | - Vysílání stavu (v sekundách) | Periodic state broadcast interval | - Poslat zvonek s výstražnou zprávou | Include bell character in alerts | - Přezdívka | Custom name for this sensor | + Nastavení | Popis | + ---------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | + Detekční senzor povolen | Activate detection sensor | + GPIO pin ke sledování | GPIO pin connected to sensor | + Typ spouštění detekce | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) | + Použít INPUT_PULLUP režim | Enable the pin's internal pull-up resistor | + Minimum time between detection broadcasts | Minimum time between alert broadcasts | + State Broadcast Interval | Periodic state broadcast interval | + Poslat zvonek s výstražnou zprávou | Include bell character in alerts | + Přezdívka | Custom name for this sensor | ### Paxcounter module People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. - Nastavení | Popis | - ----------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | - Paxcounter povolen | Activate people counting | - Interval aktualizace (v sekundách) | How often to report counts | - Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) | - BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | + Nastavení | Popis | + --------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | + Paxcounter povolen | Activate people counting | + Interval aktualizace GPS | How often to report counts | + WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) | + BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) | > 💡 **Tip:** Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. diff --git a/main/docs/cs-rCZ/user/settings-radio-user.html b/main/docs/cs-rCZ/user/settings-radio-user.html index 23c54a70b7..c2436bc766 100644 --- a/main/docs/cs-rCZ/user/settings-radio-user.html +++ b/main/docs/cs-rCZ/user/settings-radio-user.html @@ -76,7 +76,7 @@ On **Settings → LoRa**. Region | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) | Předvolby | Speed/range tradeoff | LongFast | Počet skoků | Maximum retransmit hops | 3 | - Vysílací výkon | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | + Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) | Ruční nastavení frekvence | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | Použít předvolbu | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset | diff --git a/main/docs/de-rDE/user/discovery.html b/main/docs/de-rDE/user/discovery.html index 6a26add8ef..177ac48614 100644 --- a/main/docs/de-rDE/user/discovery.html +++ b/main/docs/de-rDE/user/discovery.html @@ -161,7 +161,7 @@ The Neighbor Info module lets each node broadcast a list of the nodes it can **d 1. Navigate to **Settings → Module configuration → Neighbor Info**. 2. Enable the module. -3. Set **Update interval (seconds)**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. +3. Set **Update Interval**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. 4. Turn on **Transmit over LoRa**. Without it, your neighbor list goes only to MQTT and to this app, never over the air. Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. diff --git a/main/docs/de-rDE/user/mqtt.html b/main/docs/de-rDE/user/mqtt.html index 6e783abb65..db1b6100bd 100644 --- a/main/docs/de-rDE/user/mqtt.html +++ b/main/docs/de-rDE/user/mqtt.html @@ -90,7 +90,7 @@ Configure your node to point to your private broker with appropriate credentials When **Map reporting** is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. -Turning it on opens a consent card. Turn on **I agree.** and choose a **Map reporting interval (seconds)** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. +Turning it on opens a consent card. Turn on **I agree.** and choose a **Map Publish Interval** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at [meshmap.net](https://meshmap.net) and similar community map services. diff --git a/main/docs/de-rDE/user/settings-module-admin.html b/main/docs/de-rDE/user/settings-module-admin.html index e6279fd673..71f2de99b4 100644 --- a/main/docs/de-rDE/user/settings-module-admin.html +++ b/main/docs/de-rDE/user/settings-module-admin.html @@ -51,11 +51,11 @@ Turning **Map reporting** on reveals a consent card headed _Consent to Share Une via MQTT_, with an **I agree.** switch under it. The rest of the card doesn't exist on screen until you agree: - Einstellung | Beschreibung | - ----------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | - Ich stimme zu. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it | - Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units | - Kartenberichtsintervall (Sekunden) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | + Einstellung | Beschreibung | + ------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | + Ich stimme zu. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it | + Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units | + Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | See [MQTT](mqtt) for a detailed usage guide including encryption, privacy, and broker setup. @@ -80,20 +80,20 @@ Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devi There are two independent triggers — an incoming **message**, and a received **bell** character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. - Einstellung | Beschreibung | - ------------------------------------------------- | --------------------------------------------------------------------------------------------------- | - Externe Benachrichtigungen aktiviert | Master toggle for the module | - Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | - Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | - Ausgabe LED (GPIO) | Pin the LED is wired to | - Ausgabe LED aktiv hoch | Whether the LED pin is active high or low | - Ausgabe Summer (GPIO) | Pin the buzzer is wired to | - Ausgabe Vibration (GPIO) | Pin the vibration motor is wired to | - Benutze PWM Summer | Drive the buzzer with PWM, which allows tones rather than a single pitch | - I2S als Buzzer verwenden | Send the alert through an I2S audio output instead | - Ausgabedauer (GPIO) | How long a single alert lasts | - Nervige Verzögerung (Sekunden) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | - Klingelton | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | + Einstellung | Beschreibung | + ------------------------------------------- | --------------------------------------------------------------------------------------------------- | + Externe Benachrichtigungen aktiviert | Master toggle for the module | + Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | + Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | + Ausgabe LED (GPIO) | Pin the LED is wired to | + Ausgabe LED aktiv hoch | Whether the LED pin is active high or low | + Ausgabe Summer (GPIO) | Pin the buzzer is wired to | + Ausgabe Vibration (GPIO) | Pin the vibration motor is wired to | + Benutze PWM Summer | Drive the buzzer with PWM, which allows tones rather than a single pitch | + I2S als Buzzer verwenden | Send the alert through an I2S audio output instead | + GPIO Output Duration | How long a single alert lasts | + Nervige Verzögerung | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | + Klingelton | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | ### Store & Forward module @@ -122,7 +122,7 @@ Automated range testing tool for evaluating link quality between nodes. When ena Einstellung | Beschreibung | ------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- | Reichweitentest aktiviert | Activate range testing | - Sendernachrichtenintervall (Sekunden) | Time between test transmissions, chosen from a dropdown of fixed intervals | + Sendeintervall | Time between test transmissions, chosen from a dropdown of fixed intervals | Speichere .CSV im Speicher (nur ESP32) | Log received test data to the node's own filesystem. ESP32 hardware only | ### Telemetry module @@ -195,11 +195,11 @@ GPIO control over the mesh network. Allows a remote node to read or write GPIO p Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. - Einstellung | Beschreibung | - ------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------ | - Nachbarinformationen aktiviert | Activate neighbor broadcasting | - Aktualisierungsintervall (Sekunden) | How often to broadcast neighbor list | - Übertragen über LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | + Einstellung | Beschreibung | + ------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------ | + Nachbarinformationen aktiviert | Activate neighbor broadcasting | + GPS Abfrageintervall | How often to broadcast neighbor list | + Übertragen über LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | See [Local Mesh Discovery](discovery) for how to use neighbor data for mesh topology exploration. @@ -217,27 +217,27 @@ Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. C Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. - Einstellung | Beschreibung | - ------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | - Erkennungssensor aktiviert | Activate detection sensor | - Zu überwachender GPIO-Pin | GPIO pin connected to sensor | - Typ der Erkennungsauslösung | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) | - Eingang PULLUP Einstellung | Enable the pin's internal pull-up resistor | - Minimale Übertragungszeit (Sekunden) | Minimum time between alert broadcasts | - Statusübertragung (Sekunden) | Periodic state broadcast interval | - Glocke mit Warnmeldung senden | Include bell character in alerts | - Anzeigename | Custom name for this sensor | + Einstellung | Beschreibung | + ----------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | + Erkennungssensor aktiviert | Activate detection sensor | + Zu überwachender GPIO-Pin | GPIO pin connected to sensor | + Typ der Erkennungsauslösung | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) | + Eingang PULLUP Einstellung | Enable the pin's internal pull-up resistor | + Minimum time between detection broadcasts | Minimum time between alert broadcasts | + Übertragungsintervall | Periodic state broadcast interval | + Glocke mit Warnmeldung senden | Include bell character in alerts | + Anzeigename | Custom name for this sensor | ### Paxcounter module People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. - Einstellung | Beschreibung | - ------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------- | - Besucherzähler aktiviert | Activate people counting | - Aktualisierungsintervall (Sekunden) | How often to report counts | - Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) | - BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | + Einstellung | Beschreibung | + --------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | + Besucherzähler aktiviert | Activate people counting | + GPS Abfrageintervall | How often to report counts | + WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) | + BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) | > 💡 **Tip:** Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. diff --git a/main/docs/de-rDE/user/settings-radio-user.html b/main/docs/de-rDE/user/settings-radio-user.html index 96b53c4fe9..6fb68079a7 100644 --- a/main/docs/de-rDE/user/settings-radio-user.html +++ b/main/docs/de-rDE/user/settings-radio-user.html @@ -71,24 +71,24 @@ On **Settings → Device configuration → Device**. On **Settings → LoRa**. - Einstellung | Beschreibung | Standardwert | - -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- | - Region | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) | - Voreinstellungen | Speed/range tradeoff | LongFast | - Anzahl der Weiterleitungen | Maximum retransmit hops | 3 | - Sendeleistung | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | - Frequenz überschreiben | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | - Voreinstellung verwenden | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | - Spreizfaktor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset | - Fehlerkorrektur | Manual mode only: 5–8. More redundancy costs airtime | From preset | - Bandbreite | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset | - Frequenzschlitz | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) | - Senden aktiviert | Turning this off makes the node receive-only | On | - Duty-Cycle überschreiben | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Aus | - MQTT ignorieren | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | - OK für MQTT | Allow your packets to be forwarded to MQTT by gateways | Aus | - Empfangsverstärkung | Extra receive gain on SX126x radios; costs a little current | Aus | - PA Fan deaktiviert | Turn off the power-amplifier fan on hardware that has one | Aus | + Einstellung | Beschreibung | Standardwert | + --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- | + Region | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) | + Voreinstellungen | Speed/range tradeoff | LongFast | + Anzahl der Weiterleitungen | Maximum retransmit hops | 3 | + Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) | + Frequenz überschreiben | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | + Voreinstellung verwenden | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | + Spreizfaktor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset | + Fehlerkorrektur | Manual mode only: 5–8. More redundancy costs airtime | From preset | + Bandbreite | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset | + Frequenzschlitz | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) | + Senden aktiviert | Turning this off makes the node receive-only | On | + Duty-Cycle überschreiben | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Aus | + MQTT ignorieren | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | + OK für MQTT | Allow your packets to be forwarded to MQTT by gateways | Aus | + Empfangsverstärkung | Extra receive gain on SX126x radios; costs a little current | Aus | + PA Fan deaktiviert | Turn off the power-amplifier fan on hardware that has one | Aus | The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn't appear in another. Changing region can therefore leave your current preset diff --git a/main/docs/el-rGR/user/discovery.html b/main/docs/el-rGR/user/discovery.html index 0623919436..3e17870fbd 100644 --- a/main/docs/el-rGR/user/discovery.html +++ b/main/docs/el-rGR/user/discovery.html @@ -161,7 +161,7 @@ The Neighbor Info module lets each node broadcast a list of the nodes it can **d 1. Navigate to **Settings → Module configuration → Neighbor Info**. 2. Enable the module. -3. Set **Update interval (seconds)**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. +3. Set **Update Interval**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. 4. Turn on **Transmit over LoRa**. Without it, your neighbor list goes only to MQTT and to this app, never over the air. Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. diff --git a/main/docs/el-rGR/user/mqtt.html b/main/docs/el-rGR/user/mqtt.html index d5879a5d18..845a499a2c 100644 --- a/main/docs/el-rGR/user/mqtt.html +++ b/main/docs/el-rGR/user/mqtt.html @@ -90,7 +90,7 @@ Configure your node to point to your private broker with appropriate credentials When **Map reporting** is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. -Turning it on opens a consent card. Turn on **I agree.** and choose a **Map reporting interval (seconds)** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. +Turning it on opens a consent card. Turn on **I agree.** and choose a **Map Publish Interval** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at [meshmap.net](https://meshmap.net) and similar community map services. diff --git a/main/docs/el-rGR/user/settings-module-admin.html b/main/docs/el-rGR/user/settings-module-admin.html index 7011303d0f..8f98ae991d 100644 --- a/main/docs/el-rGR/user/settings-module-admin.html +++ b/main/docs/el-rGR/user/settings-module-admin.html @@ -51,11 +51,11 @@ Turning **Map reporting** on reveals a consent card headed _Consent to Share Une via MQTT_, with an **I agree.** switch under it. The rest of the card doesn't exist on screen until you agree: - Setting | Περιγραφή | - --------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | - I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it | - Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units | - Map reporting interval (seconds) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | + Setting | Περιγραφή | + ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | + I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it | + Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units | + Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | See [MQTT](mqtt) for a detailed usage guide including encryption, privacy, and broker setup. @@ -80,20 +80,20 @@ Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devi There are two independent triggers — an incoming **message**, and a received **bell** character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. - Setting | Περιγραφή | - ------------------------------------------------- | --------------------------------------------------------------------------------------------------- | - External notification enabled | Master toggle for the module | - Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | - Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | - Output LED (GPIO) | Pin the LED is wired to | - Output LED active high | Whether the LED pin is active high or low | - Output buzzer (GPIO) | Pin the buzzer is wired to | - Output vibra (GPIO) | Pin the vibration motor is wired to | - Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | - Use I2S as buzzer | Send the alert through an I2S audio output instead | - Output duration (milliseconds) | How long a single alert lasts | - Nag timeout (seconds) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | - Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | + Setting | Περιγραφή | + --------------------------------------- | --------------------------------------------------------------------------------------------------- | + External notification enabled | Master toggle for the module | + Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | + Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | + Output LED (GPIO) | Pin the LED is wired to | + Output LED active high | Whether the LED pin is active high or low | + Output buzzer (GPIO) | Pin the buzzer is wired to | + Output vibra (GPIO) | Pin the vibration motor is wired to | + Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | + Use I2S as buzzer | Send the alert through an I2S audio output instead | + GPIO Output Duration | How long a single alert lasts | + Nag Timeout | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | + Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | ### Store & Forward module @@ -122,7 +122,7 @@ Automated range testing tool for evaluating link quality between nodes. When ena Setting | Περιγραφή | -------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- | Range test enabled | Activate range testing | - Sender message interval (seconds) | Time between test transmissions, chosen from a dropdown of fixed intervals | + Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals | Save .CSV in storage (ESP32 only) | Log received test data to the node's own filesystem. ESP32 hardware only | ### Telemetry module @@ -195,11 +195,11 @@ GPIO control over the mesh network. Allows a remote node to read or write GPIO p Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. - Setting | Περιγραφή | - -------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | - Neighbor Info enabled | Activate neighbor broadcasting | - Update interval (seconds) | How often to broadcast neighbor list | - Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | + Setting | Περιγραφή | + --------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | + Neighbor Info enabled | Activate neighbor broadcasting | + Update Interval | How often to broadcast neighbor list | + Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | See [Local Mesh Discovery](discovery) for how to use neighbor data for mesh topology exploration. @@ -217,27 +217,27 @@ Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. C Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. - Setting | Περιγραφή | - ---------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | - Detection Sensor enabled | Activate detection sensor | - GPIO pin to monitor | GPIO pin connected to sensor | - Detection trigger type | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) | - Use INPUT_PULLUP mode | Enable the pin's internal pull-up resistor | - Minimum broadcast (seconds) | Minimum time between alert broadcasts | - State broadcast (seconds) | Periodic state broadcast interval | - Send bell with alert message | Include bell character in alerts | - Friendly name | Custom name for this sensor | + Setting | Περιγραφή | + ------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------- | + Detection Sensor enabled | Activate detection sensor | + GPIO pin to monitor | GPIO pin connected to sensor | + Detection trigger type | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) | + Use INPUT_PULLUP mode | Enable the pin's internal pull-up resistor | + Minimum time between detection broadcasts | Minimum time between alert broadcasts | + State Broadcast Interval | Periodic state broadcast interval | + Send bell with alert message | Include bell character in alerts | + Friendly name | Custom name for this sensor | ### Paxcounter module People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. - Setting | Περιγραφή | - -------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | - Paxcounter enabled | Activate people counting | - Update interval (seconds) | How often to report counts | - Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) | - BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | + Setting | Περιγραφή | + --------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | + Paxcounter enabled | Activate people counting | + Update Interval | How often to report counts | + WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) | + BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) | > 💡 **Tip:** Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. diff --git a/main/docs/el-rGR/user/settings-radio-user.html b/main/docs/el-rGR/user/settings-radio-user.html index 95e4994494..8a1c5690b2 100644 --- a/main/docs/el-rGR/user/settings-radio-user.html +++ b/main/docs/el-rGR/user/settings-radio-user.html @@ -71,24 +71,24 @@ On **Settings → Device configuration → Device**. On **Settings → LoRa**. - Setting | Περιγραφή | Default | - ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- | - Περιφέρεια | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) | - Presets | Speed/range tradeoff | LongFast | - Number of Hops | Maximum retransmit hops | 3 | - Transmit Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | - Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | - Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | - Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset | - Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | - Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset | - Frequency Slot | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) | - Transmit Enabled | Turning this off makes the node receive-only | On | - Override Duty Cycle | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | - Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | - Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | - RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | - PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | + Setting | Περιγραφή | Default | + --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- | + Περιφέρεια | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) | + Presets | Speed/range tradeoff | LongFast | + Number of Hops | Maximum retransmit hops | 3 | + Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) | + Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | + Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | + Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset | + Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | + Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset | + Frequency Slot | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) | + Transmit Enabled | Turning this off makes the node receive-only | On | + Override Duty Cycle | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | + Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | + Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | + RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | + PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn't appear in another. Changing region can therefore leave your current preset diff --git a/main/docs/es-rES/user/discovery.html b/main/docs/es-rES/user/discovery.html index 5e070340a5..72d89cf5c3 100644 --- a/main/docs/es-rES/user/discovery.html +++ b/main/docs/es-rES/user/discovery.html @@ -161,7 +161,7 @@ The Neighbor Info module lets each node broadcast a list of the nodes it can **d 1. Navigate to **Settings → Module configuration → Neighbor Info**. 2. Enable the module. -3. Set **Update interval (seconds)**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. +3. Set **Update Interval**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. 4. Turn on **Transmit over LoRa**. Without it, your neighbor list goes only to MQTT and to this app, never over the air. Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. diff --git a/main/docs/es-rES/user/mqtt.html b/main/docs/es-rES/user/mqtt.html index 2605c0ff6f..31c934e773 100644 --- a/main/docs/es-rES/user/mqtt.html +++ b/main/docs/es-rES/user/mqtt.html @@ -90,7 +90,7 @@ Configure your node to point to your private broker with appropriate credentials When **Map reporting** is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. -Turning it on opens a consent card. Turn on **I agree.** and choose a **Map reporting interval (seconds)** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. +Turning it on opens a consent card. Turn on **I agree.** and choose a **Map Publish Interval** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at [meshmap.net](https://meshmap.net) and similar community map services. diff --git a/main/docs/es-rES/user/settings-module-admin.html b/main/docs/es-rES/user/settings-module-admin.html index 9c8efa30b0..f492130c96 100644 --- a/main/docs/es-rES/user/settings-module-admin.html +++ b/main/docs/es-rES/user/settings-module-admin.html @@ -51,11 +51,11 @@ Turning **Map reporting** on reveals a consent card headed _Consent to Share Une via MQTT_, with an **I agree.** switch under it. The rest of the card doesn't exist on screen until you agree: - Setting | Descripción | - ------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | - Estoy de acuerdo. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it | - Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units | - Tiempo entre Reportes de Posición (en Segundos) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | + Setting | Descripción | + --------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | + Estoy de acuerdo. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it | + Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units | + Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | See [MQTT](mqtt) for a detailed usage guide including encryption, privacy, and broker setup. @@ -80,20 +80,20 @@ Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devi There are two independent triggers — an incoming **message**, and a received **bell** character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. - Setting | Descripción | - --------------------------------------------------------- | --------------------------------------------------------------------------------------------------- | - Notificaciones externas activadas | Master toggle for the module | - Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | - Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | - Salida LED (pin GPIO) | Pin the LED is wired to | - LED de salida activo en alto | Whether the LED pin is active high or low | - Salida buzzer (pin GPIO) | Pin the buzzer is wired to | - Salida vibratoria (pin GPIO) | Pin the vibration motor is wired to | - Utilizar buzzer PWM | Drive the buzzer with PWM, which allows tones rather than a single pitch | - Utilizar el Buzzer como uno I2S | Send the alert through an I2S audio output instead | - Duración en las salidas (milisegundos) | How long a single alert lasts | - | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | - Tono de notificación | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | + Setting | Descripción | + ----------------------------------------------- | --------------------------------------------------------------------------------------------------- | + Notificaciones externas activadas | Master toggle for the module | + Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | + Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | + Salida LED (pin GPIO) | Pin the LED is wired to | + LED de salida activo en alto | Whether the LED pin is active high or low | + Salida buzzer (pin GPIO) | Pin the buzzer is wired to | + Salida vibratoria (pin GPIO) | Pin the vibration motor is wired to | + Utilizar buzzer PWM | Drive the buzzer with PWM, which allows tones rather than a single pitch | + Utilizar el Buzzer como uno I2S | Send the alert through an I2S audio output instead | + GPIO Output Duration | How long a single alert lasts | + Nag Timeout | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | + Tono de notificación | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | ### Store & Forward module @@ -122,7 +122,7 @@ Automated range testing tool for evaluating link quality between nodes. When ena Setting | Descripción | ------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- | Test de alcance activado | Activate range testing | - Periodo entre los mensajes del transmisor (segundos) | Time between test transmissions, chosen from a dropdown of fixed intervals | + Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals | Guardar el .CSV en el almacenamiento (Esp32) | Log received test data to the node's own filesystem. ESP32 hardware only | ### Telemetry module @@ -195,11 +195,11 @@ GPIO control over the mesh network. Allows a remote node to read or write GPIO p Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. - Setting | Descripción | - --------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | - Información de Vecinos | Activate neighbor broadcasting | - Intervalo de refresco (segundos) | How often to broadcast neighbor list | - Transmitir en LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | + Setting | Descripción | + -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | + Información de Vecinos | Activate neighbor broadcasting | + Intervalo de actualización | How often to broadcast neighbor list | + Transmitir en LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | See [Local Mesh Discovery](discovery) for how to use neighbor data for mesh topology exploration. @@ -217,27 +217,27 @@ Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. C Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. - Setting | Descripción | - ----------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | - Sensor detector activado | Activate detection sensor | - Pin GPIO para monitorizar | GPIO pin connected to sensor | - Tipo de detección para activar | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) | - Utilizar el modo de entrada PULL_UP | Enable the pin's internal pull-up resistor | - Tiempo mínimo de transmisión (segundos) | Minimum time between alert broadcasts | - Periodo entre transmisión de estado (segundos) | Periodic state broadcast interval | - Mandar la campana con el mensaje de alerta | Include bell character in alerts | - Mote | Custom name for this sensor | + Setting | Descripción | + -------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | + Sensor detector activado | Activate detection sensor | + Pin GPIO para monitorizar | GPIO pin connected to sensor | + Tipo de detección para activar | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) | + Utilizar el modo de entrada PULL_UP | Enable the pin's internal pull-up resistor | + Minimum time between detection broadcasts | Minimum time between alert broadcasts | + State Broadcast Interval | Periodic state broadcast interval | + Mandar la campana con el mensaje de alerta | Include bell character in alerts | + Mote | Custom name for this sensor | ### Paxcounter module People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. - Setting | Descripción | - --------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | - Activar el Contador de Paquetes | Activate people counting | - Intervalo de refresco (segundos) | How often to report counts | - Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) | - BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | + Setting | Descripción | + --------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | + Activar el Contador de Paquetes | Activate people counting | + Intervalo de actualización | How often to report counts | + WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) | + BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) | > 💡 **Tip:** Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. diff --git a/main/docs/es-rES/user/settings-radio-user.html b/main/docs/es-rES/user/settings-radio-user.html index 2eb983d4db..c521325cf5 100644 --- a/main/docs/es-rES/user/settings-radio-user.html +++ b/main/docs/es-rES/user/settings-radio-user.html @@ -71,24 +71,24 @@ On **Settings → Device configuration → Device**. On **Settings → LoRa**. - Setting | Descripción | Por defecto | - ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- | - Región | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) | - Predefinidos | Speed/range tradeoff | LongFast | - Número de saltos | Maximum retransmit hops | 3 | - Potencia de transmisión | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | - Sobreescribir frecuencia | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | - Usar predefinido | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | - Factor de dispersión | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset | - Ratio de Codificación | Manual mode only: 5–8. More redundancy costs airtime | From preset | - Ancho de banda | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset | - Banda de Frecuencia | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) | - Transmisión habilitada | Turning this off makes the node receive-only | On | - Sobreescribir el Tiempo de Trabajo | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | - Ignorar Paquetes MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | - Permitir MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | - Aumentar ganancia de RX | Extra receive gain on SX126x radios; costs a little current | Off | - Ventilador del Amplificador apagado | Turn off the power-amplifier fan on hardware that has one | Off | + Setting | Descripción | Por defecto | + --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- | + Región | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) | + Predefinidos | Speed/range tradeoff | LongFast | + Número de saltos | Maximum retransmit hops | 3 | + Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) | + Sobreescribir frecuencia | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | + Usar predefinido | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | + Factor de dispersión | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset | + Ratio de Codificación | Manual mode only: 5–8. More redundancy costs airtime | From preset | + Ancho de banda | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset | + Banda de Frecuencia | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) | + Transmisión habilitada | Turning this off makes the node receive-only | On | + Sobreescribir el Tiempo de Trabajo | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | + Ignorar Paquetes MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | + Permitir MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | + Aumentar ganancia de RX | Extra receive gain on SX126x radios; costs a little current | Off | + Ventilador del Amplificador apagado | Turn off the power-amplifier fan on hardware that has one | Off | The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn't appear in another. Changing region can therefore leave your current preset diff --git a/main/docs/et-rEE/user/discovery.html b/main/docs/et-rEE/user/discovery.html index ff3382406a..7e16a8b86c 100644 --- a/main/docs/et-rEE/user/discovery.html +++ b/main/docs/et-rEE/user/discovery.html @@ -161,7 +161,7 @@ Naabriinfo moodul võimaldab igal sõlmel levitada nimekirja sõlmedest, mida se 1. Navigate to **Settings → Module configuration → Neighbor Info**. 2. Luba moodul. -3. Set **Update interval (seconds)**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. +3. Set **Update Interval**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. 4. Turn on **Transmit over LoRa**. Without it, your neighbor list goes only to MQTT and to this app, never over the air. Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Teised sõlmed, millel on naabriinfo lubatud, teevad sama. diff --git a/main/docs/et-rEE/user/mqtt.html b/main/docs/et-rEE/user/mqtt.html index f4c5793b28..b2ec2d1566 100644 --- a/main/docs/et-rEE/user/mqtt.html +++ b/main/docs/et-rEE/user/mqtt.html @@ -90,7 +90,7 @@ Konfigureeri oma sõlm nii, et see osutaks sinu privaatsele maaklerile sobivate When **Map reporting** is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. -Turning it on opens a consent card. Turn on **I agree.** and choose a **Map reporting interval (seconds)** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. +Turning it on opens a consent card. Turn on **I agree.** and choose a **Map Publish Interval** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at [meshmap.net](https://meshmap.net) and similar community map services. diff --git a/main/docs/et-rEE/user/settings-module-admin.html b/main/docs/et-rEE/user/settings-module-admin.html index 5b7885f09f..2d0135385c 100644 --- a/main/docs/et-rEE/user/settings-module-admin.html +++ b/main/docs/et-rEE/user/settings-module-admin.html @@ -51,11 +51,11 @@ Turning **Map reporting** on reveals a consent card headed _Consent to Share Une via MQTT_, with an **I agree.** switch under it. The rest of the card doesn't exist on screen until you agree: - Sätted | Kirjeldus | - -------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | - Nõustun. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it | - Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units | - Kaardi raporti sagedus (sekund) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | + Sätted | Kirjeldus | + ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | + Nõustun. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it | + Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units | + Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | Vaata [MQTT](mqtt) üksikasjalikumat kasutusjuhendit, mis sisaldab teavet krüpteerimise, privaatsuse ja vahendaja seadistamise kohta,. @@ -80,20 +80,20 @@ Controls buzzer, LED, or vibration alerts on your node hardware. Kasulik seadmet There are two independent triggers — an incoming **message**, and a received **bell** character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. - Sätted | Kirjeldus | - --------------------------------------------------- | --------------------------------------------------------------------------------------------------- | - Luba Välised teated | Master toggle for the module | - Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | - Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | - Väljund LED (GPIO) | Pin the LED is wired to | - Väljund LED aktiivne | Whether the LED pin is active high or low | - Väljund summer (GPIO) | Pin the buzzer is wired to | - Väljund värin (GPIO) | Pin the vibration motor is wired to | - Kasuta PWM summerit | Drive the buzzer with PWM, which allows tones rather than a single pitch | - Kasuta I2S summerina | Send the alert through an I2S audio output instead | - Väljundi kestvus (millisekundit) | How long a single alert lasts | - Häire ajalõpp (sekundit) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | - Helin | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | + Sätted | Kirjeldus | + ---------------------------------------- | --------------------------------------------------------------------------------------------------- | + Luba Välised teated | Master toggle for the module | + Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | + Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | + Väljund LED (GPIO) | Pin the LED is wired to | + Väljund LED aktiivne | Whether the LED pin is active high or low | + Väljund summer (GPIO) | Pin the buzzer is wired to | + Väljund värin (GPIO) | Pin the vibration motor is wired to | + Kasuta PWM summerit | Drive the buzzer with PWM, which allows tones rather than a single pitch | + Kasuta I2S summerina | Send the alert through an I2S audio output instead | + GPIO Output Duration | How long a single alert lasts | + Nag Timeout | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | + Helin | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | ### Store & Forward module @@ -122,7 +122,7 @@ Automatiseeritud vahemiku testimise tööriist sõlmede vahelise ühenduse kvali Sätted | Kirjeldus | --------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- | Ulatustest lubatud | Aktiveeri levi test | - Saatja sõnumi sagedus (sekundit) | Time between test transmissions, chosen from a dropdown of fixed intervals | + Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals | Salvesta .CSV faili (ainult ESP32) | Log received test data to the node's own filesystem. ESP32 hardware only | ### Telemetry module @@ -195,11 +195,11 @@ GPIO juhtimine kärgvõrgu kaudu. Võimaldab kaugsõlmel lugeda või kirjutada G Levitab teavet otse kuuldud naabrite kohta, võimaldades kärgvõrgu topoloogia kaardistamist. Iga lubatud sõlm jagab perioodiliselt nimekirja teistest sõlmedest, mida ta kuuleb ja nende signaali kvaliteedist. - Sätted | Kirjeldus | - ----------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- | - Naabruskonna teave lubatud | Aktiveeri naabrite leviring | - Uuenduste sagedus (sekundit) | Kui tihti naabrite nimekirja levitada | - Saada LoRa kaudu | Edasta naabriinfot ka LoRa kaudu, mitte ainult MQTT/telefoni kaudu. Vaikimisi võtit ja nime kasutavat kanalit pole saadaval | + Sätted | Kirjeldus | + -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- | + Naabruskonna teave lubatud | Aktiveeri naabrite leviring | + GPS-i küsimise intervall | Kui tihti naabrite nimekirja levitada | + Saada LoRa kaudu | Edasta naabriinfot ka LoRa kaudu, mitte ainult MQTT/telefoni kaudu. Vaikimisi võtit ja nime kasutavat kanalit pole saadaval | See [Local Mesh Discovery](discovery) for how to use neighbor data for mesh topology exploration. @@ -217,27 +217,27 @@ Juhib toetatud riistvaral NeoPixeli või muid adresseeritavaid RGB LEDe. Saab ka Muudab sõlme liikumis- või ukseanduri hoiatussüsteemiks. Kui GPIO sisend tuvastab oleku muutuse (liikumine tuvastatud, uks avatud), levitab sõlm kärgvõrgu kaudu hoiatusteate. - Sätted | Kirjeldus | - ------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------- | - Tuvastusandur lubatud | Aktiveeri tuvastusandur | - GPIO klemmi jälgimine | GPIO sisend on anduriga ühendatud | - Identifitseerimistüüp | Kuidas klemmi olek vastab tuvastussündmusele (nt aktiivne kõrge/madal, serva poolt käivitatav) | - Kasuta INPUT_PULLUP režiimi | Enable the pin's internal pull-up resistor | - Minimaalne edastusaeg (sekund) | Minimaalne aeg hoiatusteadete levitamisel | - Oleku edastus (sekund) | Perioodilise oleku levitamise intervall | - Saada kõll koos hoiatussõnumiga | Lisa märguannetesse hoiatuskella sümbol | - Kasutajasõbralik nimi | Selle anduri kohandatud nimi | + Sätted | Kirjeldus | + ------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------- | + Tuvastusandur lubatud | Aktiveeri tuvastusandur | + GPIO klemmi jälgimine | GPIO sisend on anduriga ühendatud | + Identifitseerimistüüp | Kuidas klemmi olek vastab tuvastussündmusele (nt aktiivne kõrge/madal, serva poolt käivitatav) | + Kasuta INPUT_PULLUP režiimi | Enable the pin's internal pull-up resistor | + Minimum time between detection broadcasts | Minimaalne aeg hoiatusteadete levitamisel | + State Broadcast Interval | Perioodilise oleku levitamise intervall | + Saada kõll koos hoiatussõnumiga | Lisa märguannetesse hoiatuskella sümbol | + Kasutajasõbralik nimi | Selle anduri kohandatud nimi | ### Paxcounter module People counter using Wi-Fi and BLE probe requests. Loendab lähedalasuvaid seadmeid, kuulates passiivselt sondimistaotlusi, mida telefonid ja sülearvutid võrkude skannimisel edastavad. Available only on ESP32 devices. - Sätted | Kirjeldus | - ----------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | - Paxcounter lubatud | Aktiveeri inimeste loendamine | - Uuenduste sagedus (sekundit) | Kui tihti loendeid esitada | - Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) | - BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | + Sätted | Kirjeldus | + --------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | + Paxcounter lubatud | Aktiveeri inimeste loendamine | + GPS-i küsimise intervall | Kui tihti loendeid esitada | + WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) | + BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) | > 💡 **Vihje:** Paxloendur on kasulik jalakäijate liikluse hindamiseks matkaradade alguses, ürituste toimumiskohtades või muudes kohtades. Arvud on ligikaudsed – üks inimene võib kaasas kanda mitut seadet. diff --git a/main/docs/et-rEE/user/settings-radio-user.html b/main/docs/et-rEE/user/settings-radio-user.html index 92c773f360..59580e40ba 100644 --- a/main/docs/et-rEE/user/settings-radio-user.html +++ b/main/docs/et-rEE/user/settings-radio-user.html @@ -71,24 +71,24 @@ On **Settings → Device configuration → Device**. On **Settings → LoRa**. - Sätted | Kirjeldus | Vaikimisi | - ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------- | - Regioon | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Määramata (tuleb seadistada) | - Eelseadistused | Speed/range tradeoff | LongFast | - Hüpete arv | Maks uuesti saadetud hüpet | 3 | - Saatevõimsus | Transmission power (dBm); 0 = max allowed for region | 0 (regiooni maks) | - Tühista sagedus | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | - Kasuta eelseadistust | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | - Levitustegur | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset | - Kodeerimiskiirus | Manual mode only: 5–8. More redundancy costs airtime | From preset | - Ribalaius | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset | - Sageduspesa | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) | - Edastus lubatud | Turning this off makes the node receive-only | On | - Töötsükli tühistamine | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Väljas | - Keela MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | - Ok MQTTi | Allow your packets to be forwarded to MQTT by gateways | Väljas | - RX võimendatud võimendus | Extra receive gain on SX126x radios; costs a little current | Väljas | - PA ventilaator keelatud | Turn off the power-amplifier fan on hardware that has one | Väljas | + Sätted | Kirjeldus | Vaikimisi | + --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------- | + Regioon | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Määramata (tuleb seadistada) | + Eelseadistused | Speed/range tradeoff | LongFast | + Hüpete arv | Maks uuesti saadetud hüpet | 3 | + Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (regiooni maks) | + Tühista sagedus | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | + Kasuta eelseadistust | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | + Levitustegur | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset | + Kodeerimiskiirus | Manual mode only: 5–8. More redundancy costs airtime | From preset | + Ribalaius | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset | + Sageduspesa | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) | + Edastus lubatud | Turning this off makes the node receive-only | On | + Töötsükli tühistamine | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Väljas | + Keela MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | + Ok MQTTi | Allow your packets to be forwarded to MQTT by gateways | Väljas | + RX võimendatud võimendus | Extra receive gain on SX126x radios; costs a little current | Väljas | + PA ventilaator keelatud | Turn off the power-amplifier fan on hardware that has one | Väljas | The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn't appear in another. Changing region can therefore leave your current preset diff --git a/main/docs/fi-rFI/user/discovery.html b/main/docs/fi-rFI/user/discovery.html index 605614b2fe..165e53e16d 100644 --- a/main/docs/fi-rFI/user/discovery.html +++ b/main/docs/fi-rFI/user/discovery.html @@ -161,7 +161,7 @@ Naapuritieto-moduuli antaa jokaisen radion lähettää listan radioista, jotka s 1. Navigate to **Settings → Module configuration → Neighbor Info**. 2. Ota moduuli käyttöön. -3. Set **Update interval (seconds)**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. +3. Set **Update Interval**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. 4. Turn on **Transmit over LoRa**. Without it, your neighbor list goes only to MQTT and to this app, never over the air. Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Myös muut radiot, joissa naapuritieto on käytössä, toimivat samalla tavalla. diff --git a/main/docs/fi-rFI/user/mqtt.html b/main/docs/fi-rFI/user/mqtt.html index c975eeeecb..754a1ab2dd 100644 --- a/main/docs/fi-rFI/user/mqtt.html +++ b/main/docs/fi-rFI/user/mqtt.html @@ -88,7 +88,7 @@ Määritä radiosi osoittamaan omaan välityspalvelimeesi oikeilla tunnistetiedo When **Map reporting** is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. -Turning it on opens a consent card. Turn on **I agree.** and choose a **Map reporting interval (seconds)** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. +Turning it on opens a consent card. Turn on **I agree.** and choose a **Map Publish Interval** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at [meshmap.net](https://meshmap.net) and similar community map services. diff --git a/main/docs/fi-rFI/user/settings-module-admin.html b/main/docs/fi-rFI/user/settings-module-admin.html index 3f00199d1a..60c2e50d57 100644 --- a/main/docs/fi-rFI/user/settings-module-admin.html +++ b/main/docs/fi-rFI/user/settings-module-admin.html @@ -51,11 +51,11 @@ Turning **Map reporting** on reveals a consent card headed _Consent to Share Une via MQTT_, with an **I agree.** switch under it. The rest of the card doesn't exist on screen until you agree: - Asetus | Kuvaus | - --------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | - Hyväksyn. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it | - Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units | - Karttaraportoinnin aikaväli (sekuntia) | Kuinka usein sijainti julkaistaan. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | + Asetus | Kuvaus | + ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | + Hyväksyn. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it | + Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units | + Map Publish Interval | Kuinka usein sijainti julkaistaan. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | Katso [MQTT](mqtt) saadaksesi yksityiskohtaisen käyttöoppaan, joka sisältää salauksen, tietosuojan ja välityspalvelimen määrityksen. @@ -90,8 +90,8 @@ Käynnistimiä on kaksi – saapuva **viesti** ja vastaanotettu **BEL**-ohjausme Ulostulon värinä (GPIO) | Värinämoottori on kytketty nastaan | Käytä PWM-äänimerkkiä | Ohjaa summeria PWM:llä, jolloin voidaan toistaa ääniä yhden kiinteän taajuuden sijaan | Käytä I2S protokollaa äänimerkille | Lähetä hälytys sen sijaan I2S-äänilähdön kautta | - Ulostulon kesto (millisekuntia) | Kuinka kauan yksittäinen hälytys kestää | - Hälytysaikakatkaisu (sekuntia) | Toista hälytystä tämän ajan, kunnes se kuitataan. 0 poistaa toistuvan muistutuksen käytöstä | + GPIO Output Duration | Kuinka kauan yksittäinen hälytys kestää | + Toistokehotuksen aikakatkaisu | Toista hälytystä tämän ajan, kunnes se kuitataan. 0 poistaa toistuvan muistutuksen käytöstä | Soittoääni | PWM-summerilla toistettava RTTTL-soittoääni. Voidaan tuoda tiedostosta | ### Store & Forward module @@ -121,7 +121,7 @@ Automaattinen kuuluvuustestityökalu radioiden välisen yhteyden laadun arvioint Asetus | Kuvaus | ------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- | Kuuluvuustesti käytössä | Ota kuuluvuustesti käyttöön | - Viestien lähetyksen aikaväli (sekuntia) | Time between test transmissions, chosen from a dropdown of fixed intervals | + Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals | Tallenna .CSV (ESP32 ainoastaan) | Log received test data to the node's own filesystem. ESP32 hardware only | ### Telemetry module @@ -193,11 +193,11 @@ GPIO-ohjaus mesh-verkon kautta. Mahdollistaa etäradion lukea tai kirjoittaa GPI Lähettää tietoa suoraan kuulluista naapureista mahdollistaen verkon topologian kartoituksen. Jokainen käyttöön otettu radio jakaa säännöllisesti luettelon muista radioista, jotka se kuulee, sekä niiden signaalin laadun. - Asetus | Kuvaus | - -------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | - Naapuritiedot käytössä | Ota naapuritiedon lähetys käyttöön | - Päivityksen aikaväli (sekuntia) | Kuinka usein naapuriluettelo lähetetään | - Lähetä LoRa:n kautta | Lähetä myös naapuritiedot LoRa:n kautta, ei pelkästään MQTT:n tai puhelimen kautta. Ei käytettävissä kanavalla, joka käyttää oletusavainta ja nimeä | + Asetus | Kuvaus | + ------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | + Naapuritiedot käytössä | Ota naapuritiedon lähetys käyttöön | + GPS-kyselyn aikaväli | Kuinka usein naapuriluettelo lähetetään | + Lähetä LoRa:n kautta | Lähetä myös naapuritiedot LoRa:n kautta, ei pelkästään MQTT:n tai puhelimen kautta. Ei käytettävissä kanavalla, joka käyttää oletusavainta ja nimeä | Katso [Paikallinen mesh-haku](discovery), miten naapuritietoja käytetään mesh-verkon rakenteen tutkimiseen. @@ -215,27 +215,27 @@ Ohjaa tuetuissa laitteissa olevaa NeoPixeliä tai muita osoitteellisia RGB-LEDej Muuttaa radiosi liike- tai ovitunnistimeen perustuvaksi hälytysjärjestelmäksi. Kun GPIO-pinni havaitsee tilamuutoksen (liike havaittu, ovi avattu), radio lähettää hälytysviestin verkkoon. - Asetus | Kuvaus | - ------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------- | - Tunnistinsensori käytössä | Ota tunnistusanturi käyttöön | - GPIO-pinni valvontaa varten | Anturiin kytketty GPIO-pinni | - Tunnistuksen tyyppi | Miten pinnin tila vastaa havaitsemistapahtumaa (esim. aktiivinen korkea/matala taso tai reunalaukaisu) | - Käytä INPUT_PULLUP tilaa | Ota pinnin sisäinen ylösvetovastus käyttöön | - Minimilähetys (sekuntia) | Hälytyslähetysten vähimmäisaika | - Tilatiedon lähetys (sekuntia) | Tilatiedon lähetysväli | - Lähetä äänimerkki hälytyssanoman kanssa | Sisällytä soittomerkkimerkki hälytyksiin | - Käyttäjäystävällinen nimi | Tälle anturille määritetty nimi | + Asetus | Kuvaus | + --------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- | + Tunnistinsensori käytössä | Ota tunnistusanturi käyttöön | + GPIO-pinni valvontaa varten | Anturiin kytketty GPIO-pinni | + Tunnistuksen tyyppi | Miten pinnin tila vastaa havaitsemistapahtumaa (esim. aktiivinen korkea/matala taso tai reunalaukaisu) | + Käytä INPUT_PULLUP tilaa | Ota pinnin sisäinen ylösvetovastus käyttöön | + Minimum time between detection broadcasts | Hälytyslähetysten vähimmäisaika | + State Broadcast Interval | Tilatiedon lähetysväli | + Lähetä äänimerkki hälytyssanoman kanssa | Sisällytä soittomerkkimerkki hälytyksiin | + Käyttäjäystävällinen nimi | Tälle anturille määritetty nimi | ### Paxcounter module Henkilöt, jotka lasketaan WiFi- ja BLE-hakukyselyiden perusteella. Laskee lähellä olevia laitteita kuuntelemalla passiivisesti koepyyntöjä, joita puhelimet ja kannettavat tietokoneet lähettävät etsiessään verkkoja. Saatavilla vain ESP32-laitteissa. - Asetus | Kuvaus | - -------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | - PAX-laskuri käytössä | Ota henkilölaskenta käyttöön | - Päivityksen aikaväli (sekuntia) | Kuinka usein laskentatiedot raportoidaan | - WiFi-signaalin RSSI-kynnys | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) | - BLE-signaalin RSSI-kynnys | Sama raja-arvo BLE-mainospaketeille (oletus: -80 dBm) | + Asetus | Kuvaus | + --------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | + PAX-laskuri käytössä | Ota henkilölaskenta käyttöön | + GPS-kyselyn aikaväli | Kuinka usein laskentatiedot raportoidaan | + WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) | + BLE Threshold (dBm) | Sama raja-arvo BLE-mainospaketeille (oletus: -80 dBm) | > 💡 **Vinkki:** PAX-laskuri on hyödyllinen jalankulkijamäärien arviointiin retkeilyreittien lähtöpisteissä, tapahtumapaikoilla tai muissa kohteissa. Laskentatulokset ovat arvioita — yhdellä henkilöllä voi olla useita laitteita mukana. diff --git a/main/docs/fi-rFI/user/settings-radio-user.html b/main/docs/fi-rFI/user/settings-radio-user.html index 4f9942b210..911d842f45 100644 --- a/main/docs/fi-rFI/user/settings-radio-user.html +++ b/main/docs/fi-rFI/user/settings-radio-user.html @@ -75,7 +75,7 @@ On **Settings → LoRa**. Alue | Taajuusalueen sääntelyalue. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Ei asetettu (on määritettävä) | Esiasetukset | Nopeuden ja kantaman välinen kompromissi | LongFast | Hyppyjen määrä | Suurin hyppyjen määrä | 3 | - Lähetysteho | Lähetysteho (dBm): 0 = alueen sallima enimmäisteho | 0 (alueen enimmäisteho) | + Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (alueen enimmäisteho) | Taajuuden ohitus | Ohittaa lasketun käyttötaajuuden (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (käytä laskettua arvoa) | Käytä esiasetusta | Oletusarvoisesti käytössä. Poista tämä käytöstä, jos haluat määrittää hajotuskerroin-, koodausnopeus- ja kaistanleveysasetukset käsin modeemiesiasetuksen sijaan | Käytössä | Levennyskerroin (Spread Factor) | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | Esiasetuksesta | diff --git a/main/docs/fr-rCA/user/discovery.html b/main/docs/fr-rCA/user/discovery.html index f8df5560a0..c35165fc23 100644 --- a/main/docs/fr-rCA/user/discovery.html +++ b/main/docs/fr-rCA/user/discovery.html @@ -161,7 +161,7 @@ The Neighbor Info module lets each node broadcast a list of the nodes it can **d 1. Navigate to **Settings → Module configuration → Neighbor Info**. 2. Enable the module. -3. Set **Update interval (seconds)**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. +3. Set **Update Interval**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. 4. Turn on **Transmit over LoRa**. Without it, your neighbor list goes only to MQTT and to this app, never over the air. Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. diff --git a/main/docs/fr-rCA/user/mqtt.html b/main/docs/fr-rCA/user/mqtt.html index 7d1927cf1e..8d45a3d300 100644 --- a/main/docs/fr-rCA/user/mqtt.html +++ b/main/docs/fr-rCA/user/mqtt.html @@ -90,7 +90,7 @@ Configure your node to point to your private broker with appropriate credentials When **Map reporting** is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. -Turning it on opens a consent card. Turn on **I agree.** and choose a **Map reporting interval (seconds)** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. +Turning it on opens a consent card. Turn on **I agree.** and choose a **Map Publish Interval** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at [meshmap.net](https://meshmap.net) and similar community map services. diff --git a/main/docs/fr-rCA/user/settings-module-admin.html b/main/docs/fr-rCA/user/settings-module-admin.html index 57517af437..d64b32cb11 100644 --- a/main/docs/fr-rCA/user/settings-module-admin.html +++ b/main/docs/fr-rCA/user/settings-module-admin.html @@ -51,11 +51,11 @@ Turning **Map reporting** on reveals a consent card headed _Consent to Share Une via MQTT_, with an **I agree.** switch under it. The rest of the card doesn't exist on screen until you agree: - Setting | Description | - ------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | - J'accepte. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it | - Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units | - Intervalle de rapport cartographique (secondes) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | + Setting | Description | + -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | + J'accepte. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it | + Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units | + Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | See [MQTT](mqtt) for a detailed usage guide including encryption, privacy, and broker setup. @@ -80,20 +80,20 @@ Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devi There are two independent triggers — an incoming **message**, and a received **bell** character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. - Setting | Description | - -------------------------------------------------------------- | --------------------------------------------------------------------------------------------------- | - Notifications externes activées | Master toggle for the module | - Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | - Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | - LED extérieure (GPIO) | Pin the LED is wired to | - Sortie LED active à l’état haut | Whether the LED pin is active high or low | - Buzzer extérieur (GPIO) | Pin the buzzer is wired to | - Sortie vibreur (GPIO) | Pin the vibration motor is wired to | - Utiliser le buzzer PWM | Drive the buzzer with PWM, which allows tones rather than a single pitch | - Utiliser l'I2S comme buzzer | Send the alert through an I2S audio output instead | - Durée de sortie (en millisecondes) | How long a single alert lasts | - Durée de répétition de la sortie (secondes) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | - Sonnerie | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | + Setting | Description | + ------------------------------------------ | --------------------------------------------------------------------------------------------------- | + Notifications externes activées | Master toggle for the module | + Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | + Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | + LED extérieure (GPIO) | Pin the LED is wired to | + Sortie LED active à l’état haut | Whether the LED pin is active high or low | + Buzzer extérieur (GPIO) | Pin the buzzer is wired to | + Sortie vibreur (GPIO) | Pin the vibration motor is wired to | + Utiliser le buzzer PWM | Drive the buzzer with PWM, which allows tones rather than a single pitch | + Utiliser l'I2S comme buzzer | Send the alert through an I2S audio output instead | + GPIO Output Duration | How long a single alert lasts | + Délai d'expiration du message | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | + Sonnerie | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | ### Store & Forward module @@ -122,7 +122,7 @@ Automated range testing tool for evaluating link quality between nodes. When ena Setting | Description | -------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- | Test de portée activé | Activate range testing | - Intervalle de message de l'expéditeur (secondes) | Time between test transmissions, chosen from a dropdown of fixed intervals | + Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals | Enregistrer .CSV dans le stockage (ESP32 seulement) | Log received test data to the node's own filesystem. ESP32 hardware only | ### Telemetry module @@ -195,11 +195,11 @@ GPIO control over the mesh network. Allows a remote node to read or write GPIO p Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. - Setting | Description | - ------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | - Infos de voisinage activées | Activate neighbor broadcasting | - Intervalle de mise à jour (secondes) | How often to broadcast neighbor list | - Transmettre par LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | + Setting | Description | + ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | + Infos de voisinage activées | Activate neighbor broadcasting | + Fréquence de récupération GPS | How often to broadcast neighbor list | + Transmettre par LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | See [Local Mesh Discovery](discovery) for how to use neighbor data for mesh topology exploration. @@ -223,8 +223,8 @@ Turns your node into a motion or door sensor alert system. When a GPIO pin detec Broche GPIO à surveiller | GPIO pin connected to sensor | Type du déclencheur de détection | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) | Utiliser le mode INPUT_PULLUP | Enable the pin's internal pull-up resistor | - Diffusion minimale (secondes) | Minimum time between alert broadcasts | - Diffusion de l'État (secondes) | Periodic state broadcast interval | + Minimum time between detection broadcasts | Minimum time between alert broadcasts | + State Broadcast Interval | Periodic state broadcast interval | Envoyer une sonnerie avec un message d'alerte | Include bell character in alerts | Nom convivial | Custom name for this sensor | @@ -232,12 +232,12 @@ Turns your node into a motion or door sensor alert system. When a GPIO pin detec People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. - Paramètre | Description | - ------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | - Paxcounter activé | Activate people counting | - Intervalle de mise à jour (secondes) | How often to report counts | - Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) | - BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | + Paramètre | Description | + --------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | + Paxcounter activé | Activate people counting | + Fréquence de récupération GPS | How often to report counts | + WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) | + BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) | > 💡 **Tip:** Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. diff --git a/main/docs/fr-rCA/user/settings-radio-user.html b/main/docs/fr-rCA/user/settings-radio-user.html index 1a8ed32aef..cfc3156710 100644 --- a/main/docs/fr-rCA/user/settings-radio-user.html +++ b/main/docs/fr-rCA/user/settings-radio-user.html @@ -76,7 +76,7 @@ On **Settings → LoRa**. Région | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) | Préréglages | Speed/range tradeoff | LongFast | Nombre de sauts | Maximum retransmit hops | 3 | - Puissance d'émission | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | + Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) | Remplacer la fréquence | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | Utiliser un préréglage | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | Facteur de propagation | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset | diff --git a/main/docs/fr-rFR/user/discovery.html b/main/docs/fr-rFR/user/discovery.html index f1501198fb..35febd63eb 100644 --- a/main/docs/fr-rFR/user/discovery.html +++ b/main/docs/fr-rFR/user/discovery.html @@ -161,7 +161,7 @@ The Neighbor Info module lets each node broadcast a list of the nodes it can **d 1. Navigate to **Settings → Module configuration → Neighbor Info**. 2. Enable the module. -3. Set **Update interval (seconds)**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. +3. Set **Update Interval**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. 4. Turn on **Transmit over LoRa**. Without it, your neighbor list goes only to MQTT and to this app, never over the air. Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. diff --git a/main/docs/fr-rFR/user/mqtt.html b/main/docs/fr-rFR/user/mqtt.html index 109ee85cc9..98abb3a4aa 100644 --- a/main/docs/fr-rFR/user/mqtt.html +++ b/main/docs/fr-rFR/user/mqtt.html @@ -90,7 +90,7 @@ Configure your node to point to your private broker with appropriate credentials When **Map reporting** is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. -Turning it on opens a consent card. Turn on **I agree.** and choose a **Map reporting interval (seconds)** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. +Turning it on opens a consent card. Turn on **I agree.** and choose a **Map Publish Interval** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at [meshmap.net](https://meshmap.net) and similar community map services. diff --git a/main/docs/fr-rFR/user/settings-module-admin.html b/main/docs/fr-rFR/user/settings-module-admin.html index f110ff6b8d..f456a253bd 100644 --- a/main/docs/fr-rFR/user/settings-module-admin.html +++ b/main/docs/fr-rFR/user/settings-module-admin.html @@ -51,11 +51,11 @@ Turning **Map reporting** on reveals a consent card headed _Consent to Share Une via MQTT_, with an **I agree.** switch under it. The rest of the card doesn't exist on screen until you agree: - Setting | Description | - ------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | - J'accepte. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it | - Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units | - Intervalle de rapport cartographique (secondes) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | + Setting | Description | + -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | + J'accepte. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it | + Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units | + Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | See [MQTT](mqtt) for a detailed usage guide including encryption, privacy, and broker setup. @@ -80,20 +80,20 @@ Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devi There are two independent triggers — an incoming **message**, and a received **bell** character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. - Setting | Description | - -------------------------------------------------------------- | --------------------------------------------------------------------------------------------------- | - Notifications externes activées | Master toggle for the module | - Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | - Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | - LED extérieure (GPIO) | Pin the LED is wired to | - Sortie LED active à l’état haut | Whether the LED pin is active high or low | - Buzzer extérieur (GPIO) | Pin the buzzer is wired to | - Sortie vibreur (GPIO) | Pin the vibration motor is wired to | - Utiliser le buzzer PWM | Drive the buzzer with PWM, which allows tones rather than a single pitch | - Utiliser l'I2S comme buzzer | Send the alert through an I2S audio output instead | - Durée de sortie (en millisecondes) | How long a single alert lasts | - Durée de répétition de la sortie (secondes) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | - Sonnerie | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | + Setting | Description | + ------------------------------------------ | --------------------------------------------------------------------------------------------------- | + Notifications externes activées | Master toggle for the module | + Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | + Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | + LED extérieure (GPIO) | Pin the LED is wired to | + Sortie LED active à l’état haut | Whether the LED pin is active high or low | + Buzzer extérieur (GPIO) | Pin the buzzer is wired to | + Sortie vibreur (GPIO) | Pin the vibration motor is wired to | + Utiliser le buzzer PWM | Drive the buzzer with PWM, which allows tones rather than a single pitch | + Utiliser l'I2S comme buzzer | Send the alert through an I2S audio output instead | + GPIO Output Duration | How long a single alert lasts | + Délai d'expiration du message | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | + Sonnerie | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | ### Store & Forward module @@ -122,7 +122,7 @@ Automated range testing tool for evaluating link quality between nodes. When ena Setting | Description | -------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- | Test de portée activé | Activate range testing | - Intervalle de message de l'expéditeur (secondes) | Time between test transmissions, chosen from a dropdown of fixed intervals | + Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals | Enregistrer .CSV dans le stockage (ESP32 seulement) | Log received test data to the node's own filesystem. ESP32 hardware only | ### Telemetry module @@ -195,11 +195,11 @@ GPIO control over the mesh network. Allows a remote node to read or write GPIO p Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. - Setting | Description | - ------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | - Infos de voisinage activées | Activate neighbor broadcasting | - Intervalle de mise à jour (secondes) | How often to broadcast neighbor list | - Transmettre par LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | + Setting | Description | + ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | + Infos de voisinage activées | Activate neighbor broadcasting | + Fréquence de récupération GPS | How often to broadcast neighbor list | + Transmettre par LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | See [Local Mesh Discovery](discovery) for how to use neighbor data for mesh topology exploration. @@ -223,8 +223,8 @@ Turns your node into a motion or door sensor alert system. When a GPIO pin detec Broche GPIO à surveiller | GPIO pin connected to sensor | Type du déclencheur de détection | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) | Utiliser le mode INPUT_PULLUP | Enable the pin's internal pull-up resistor | - Diffusion minimale (secondes) | Minimum time between alert broadcasts | - Diffusion de l'État (secondes) | Periodic state broadcast interval | + Minimum time between detection broadcasts | Minimum time between alert broadcasts | + State Broadcast Interval | Periodic state broadcast interval | Envoyer une sonnerie avec un message d'alerte | Include bell character in alerts | Nom convivial | Custom name for this sensor | @@ -232,12 +232,12 @@ Turns your node into a motion or door sensor alert system. When a GPIO pin detec People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. - Paramètre | Description | - ------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | - Paxcounter activé | Activate people counting | - Intervalle de mise à jour (secondes) | How often to report counts | - Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) | - BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | + Paramètre | Description | + --------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | + Paxcounter activé | Activate people counting | + Fréquence de récupération GPS | How often to report counts | + WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) | + BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) | > 💡 **Tip:** Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. diff --git a/main/docs/fr-rFR/user/settings-radio-user.html b/main/docs/fr-rFR/user/settings-radio-user.html index d019ca5a97..a382979181 100644 --- a/main/docs/fr-rFR/user/settings-radio-user.html +++ b/main/docs/fr-rFR/user/settings-radio-user.html @@ -76,7 +76,7 @@ On **Settings → LoRa**. Région | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) | Préréglages | Speed/range tradeoff | LongFast | Nombre de sauts | Maximum retransmit hops | 3 | - Puissance d'émission | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | + Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) | Remplacer la fréquence | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | Utiliser un préréglage | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | Facteur de propagation | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset | diff --git a/main/docs/ga-rIE/user/discovery.html b/main/docs/ga-rIE/user/discovery.html index 2aac340750..c042ee4e07 100644 --- a/main/docs/ga-rIE/user/discovery.html +++ b/main/docs/ga-rIE/user/discovery.html @@ -161,7 +161,7 @@ The Neighbor Info module lets each node broadcast a list of the nodes it can **d 1. Navigate to **Settings → Module configuration → Neighbor Info**. 2. Enable the module. -3. Set **Update interval (seconds)**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. +3. Set **Update Interval**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. 4. Turn on **Transmit over LoRa**. Without it, your neighbor list goes only to MQTT and to this app, never over the air. Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. diff --git a/main/docs/ga-rIE/user/mqtt.html b/main/docs/ga-rIE/user/mqtt.html index a185473015..c800312c00 100644 --- a/main/docs/ga-rIE/user/mqtt.html +++ b/main/docs/ga-rIE/user/mqtt.html @@ -90,7 +90,7 @@ Configure your node to point to your private broker with appropriate credentials When **Map reporting** is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. -Turning it on opens a consent card. Turn on **I agree.** and choose a **Map reporting interval (seconds)** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. +Turning it on opens a consent card. Turn on **I agree.** and choose a **Map Publish Interval** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at [meshmap.net](https://meshmap.net) and similar community map services. diff --git a/main/docs/ga-rIE/user/settings-module-admin.html b/main/docs/ga-rIE/user/settings-module-admin.html index 09f2fb2f0b..f796c05014 100644 --- a/main/docs/ga-rIE/user/settings-module-admin.html +++ b/main/docs/ga-rIE/user/settings-module-admin.html @@ -51,11 +51,11 @@ Turning **Map reporting** on reveals a consent card headed _Consent to Share Une via MQTT_, with an **I agree.** switch under it. The rest of the card doesn't exist on screen until you agree: - Setting | Cur síos | - --------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | - I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it | - Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units | - Map reporting interval (seconds) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | + Setting | Cur síos | + ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | + I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it | + Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units | + Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | See [MQTT](mqtt) for a detailed usage guide including encryption, privacy, and broker setup. @@ -80,20 +80,20 @@ Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devi There are two independent triggers — an incoming **message**, and a received **bell** character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. - Setting | Cur síos | - ------------------------------------------------- | --------------------------------------------------------------------------------------------------- | - External notification enabled | Master toggle for the module | - Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | - Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | - Output LED (GPIO) | Pin the LED is wired to | - Output LED active high | Whether the LED pin is active high or low | - Output buzzer (GPIO) | Pin the buzzer is wired to | - Output vibra (GPIO) | Pin the vibration motor is wired to | - Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | - Use I2S as buzzer | Send the alert through an I2S audio output instead | - Output duration (milliseconds) | How long a single alert lasts | - Nag timeout (seconds) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | - Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | + Setting | Cur síos | + --------------------------------------- | --------------------------------------------------------------------------------------------------- | + External notification enabled | Master toggle for the module | + Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | + Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | + Output LED (GPIO) | Pin the LED is wired to | + Output LED active high | Whether the LED pin is active high or low | + Output buzzer (GPIO) | Pin the buzzer is wired to | + Output vibra (GPIO) | Pin the vibration motor is wired to | + Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | + Use I2S as buzzer | Send the alert through an I2S audio output instead | + GPIO Output Duration | How long a single alert lasts | + Nag Timeout | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | + Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | ### Store & Forward module @@ -122,7 +122,7 @@ Automated range testing tool for evaluating link quality between nodes. When ena Setting | Cur síos | -------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- | Range test enabled | Activate range testing | - Sender message interval (seconds) | Time between test transmissions, chosen from a dropdown of fixed intervals | + Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals | Save .CSV in storage (ESP32 only) | Log received test data to the node's own filesystem. ESP32 hardware only | ### Telemetry module @@ -195,11 +195,11 @@ GPIO control over the mesh network. Allows a remote node to read or write GPIO p Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. - Setting | Cur síos | - -------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | - Neighbor Info enabled | Activate neighbor broadcasting | - Update interval (seconds) | How often to broadcast neighbor list | - Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | + Setting | Cur síos | + --------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | + Neighbor Info enabled | Activate neighbor broadcasting | + Update Interval | How often to broadcast neighbor list | + Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | See [Local Mesh Discovery](discovery) for how to use neighbor data for mesh topology exploration. @@ -217,27 +217,27 @@ Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. C Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. - Setting | Cur síos | - ---------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | - Detection Sensor enabled | Activate detection sensor | - GPIO pin to monitor | GPIO pin connected to sensor | - Detection trigger type | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) | - Use INPUT_PULLUP mode | Enable the pin's internal pull-up resistor | - Minimum broadcast (seconds) | Minimum time between alert broadcasts | - State broadcast (seconds) | Periodic state broadcast interval | - Send bell with alert message | Include bell character in alerts | - Friendly name | Custom name for this sensor | + Setting | Cur síos | + ------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------- | + Detection Sensor enabled | Activate detection sensor | + GPIO pin to monitor | GPIO pin connected to sensor | + Detection trigger type | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) | + Use INPUT_PULLUP mode | Enable the pin's internal pull-up resistor | + Minimum time between detection broadcasts | Minimum time between alert broadcasts | + State Broadcast Interval | Periodic state broadcast interval | + Send bell with alert message | Include bell character in alerts | + Friendly name | Custom name for this sensor | ### Paxcounter module People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. - Setting | Cur síos | - -------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | - Paxcounter enabled | Activate people counting | - Update interval (seconds) | How often to report counts | - Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) | - BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | + Setting | Cur síos | + --------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | + Paxcounter enabled | Activate people counting | + Update Interval | How often to report counts | + WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) | + BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) | > 💡 **Tip:** Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. diff --git a/main/docs/ga-rIE/user/settings-radio-user.html b/main/docs/ga-rIE/user/settings-radio-user.html index 7973f4e4dc..070f014d24 100644 --- a/main/docs/ga-rIE/user/settings-radio-user.html +++ b/main/docs/ga-rIE/user/settings-radio-user.html @@ -71,24 +71,24 @@ On **Settings → Device configuration → Device**. On **Settings → LoRa**. - Setting | Cur síos | Default | - ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- | - Réigiún | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) | - Presets | Speed/range tradeoff | LongFast | - Number of Hops | Maximum retransmit hops | 3 | - Transmit Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | - Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | - Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | - Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset | - Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | - Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset | - Frequency Slot | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) | - Transmit Enabled | Turning this off makes the node receive-only | On | - Override Duty Cycle | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | - Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | - Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | - RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | - PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | + Setting | Cur síos | Default | + --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- | + Réigiún | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) | + Presets | Speed/range tradeoff | LongFast | + Number of Hops | Maximum retransmit hops | 3 | + Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) | + Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | + Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | + Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset | + Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | + Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset | + Frequency Slot | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) | + Transmit Enabled | Turning this off makes the node receive-only | On | + Override Duty Cycle | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | + Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | + Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | + RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | + PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn't appear in another. Changing region can therefore leave your current preset diff --git a/main/docs/gl-rES/user/discovery.html b/main/docs/gl-rES/user/discovery.html index 5a448acbed..d3df9ee262 100644 --- a/main/docs/gl-rES/user/discovery.html +++ b/main/docs/gl-rES/user/discovery.html @@ -161,7 +161,7 @@ The Neighbor Info module lets each node broadcast a list of the nodes it can **d 1. Navigate to **Settings → Module configuration → Neighbor Info**. 2. Enable the module. -3. Set **Update interval (seconds)**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. +3. Set **Update Interval**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. 4. Turn on **Transmit over LoRa**. Without it, your neighbor list goes only to MQTT and to this app, never over the air. Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. diff --git a/main/docs/gl-rES/user/mqtt.html b/main/docs/gl-rES/user/mqtt.html index 34712a2470..0dcfc1a34b 100644 --- a/main/docs/gl-rES/user/mqtt.html +++ b/main/docs/gl-rES/user/mqtt.html @@ -90,7 +90,7 @@ Configure your node to point to your private broker with appropriate credentials When **Map reporting** is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. -Turning it on opens a consent card. Turn on **I agree.** and choose a **Map reporting interval (seconds)** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. +Turning it on opens a consent card. Turn on **I agree.** and choose a **Map Publish Interval** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at [meshmap.net](https://meshmap.net) and similar community map services. diff --git a/main/docs/gl-rES/user/settings-module-admin.html b/main/docs/gl-rES/user/settings-module-admin.html index 6fcbf304bc..17e932d72f 100644 --- a/main/docs/gl-rES/user/settings-module-admin.html +++ b/main/docs/gl-rES/user/settings-module-admin.html @@ -51,11 +51,11 @@ Turning **Map reporting** on reveals a consent card headed _Consent to Share Une via MQTT_, with an **I agree.** switch under it. The rest of the card doesn't exist on screen until you agree: - Setting | Descrición | - --------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | - I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it | - Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units | - Map reporting interval (seconds) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | + Setting | Descrición | + ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | + I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it | + Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units | + Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | See [MQTT](mqtt) for a detailed usage guide including encryption, privacy, and broker setup. @@ -80,20 +80,20 @@ Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devi There are two independent triggers — an incoming **message**, and a received **bell** character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. - Setting | Descrición | - ------------------------------------------------- | --------------------------------------------------------------------------------------------------- | - External notification enabled | Master toggle for the module | - Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | - Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | - Output LED (GPIO) | Pin the LED is wired to | - Output LED active high | Whether the LED pin is active high or low | - Output buzzer (GPIO) | Pin the buzzer is wired to | - Output vibra (GPIO) | Pin the vibration motor is wired to | - Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | - Use I2S as buzzer | Send the alert through an I2S audio output instead | - Output duration (milliseconds) | How long a single alert lasts | - Nag timeout (seconds) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | - Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | + Setting | Descrición | + --------------------------------------- | --------------------------------------------------------------------------------------------------- | + External notification enabled | Master toggle for the module | + Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | + Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | + Output LED (GPIO) | Pin the LED is wired to | + Output LED active high | Whether the LED pin is active high or low | + Output buzzer (GPIO) | Pin the buzzer is wired to | + Output vibra (GPIO) | Pin the vibration motor is wired to | + Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | + Use I2S as buzzer | Send the alert through an I2S audio output instead | + GPIO Output Duration | How long a single alert lasts | + Nag Timeout | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | + Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | ### Store & Forward module @@ -122,7 +122,7 @@ Automated range testing tool for evaluating link quality between nodes. When ena Setting | Descrición | -------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- | Range test enabled | Activate range testing | - Sender message interval (seconds) | Time between test transmissions, chosen from a dropdown of fixed intervals | + Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals | Save .CSV in storage (ESP32 only) | Log received test data to the node's own filesystem. ESP32 hardware only | ### Telemetry module @@ -195,11 +195,11 @@ GPIO control over the mesh network. Allows a remote node to read or write GPIO p Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. - Setting | Descrición | - -------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | - Neighbor Info enabled | Activate neighbor broadcasting | - Update interval (seconds) | How often to broadcast neighbor list | - Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | + Setting | Descrición | + --------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | + Neighbor Info enabled | Activate neighbor broadcasting | + Update Interval | How often to broadcast neighbor list | + Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | See [Local Mesh Discovery](discovery) for how to use neighbor data for mesh topology exploration. @@ -217,27 +217,27 @@ Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. C Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. - Setting | Descrición | - ---------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | - Detection Sensor enabled | Activate detection sensor | - GPIO pin to monitor | GPIO pin connected to sensor | - Detection trigger type | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) | - Use INPUT_PULLUP mode | Enable the pin's internal pull-up resistor | - Minimum broadcast (seconds) | Minimum time between alert broadcasts | - State broadcast (seconds) | Periodic state broadcast interval | - Send bell with alert message | Include bell character in alerts | - Friendly name | Custom name for this sensor | + Setting | Descrición | + ------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------- | + Detection Sensor enabled | Activate detection sensor | + GPIO pin to monitor | GPIO pin connected to sensor | + Detection trigger type | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) | + Use INPUT_PULLUP mode | Enable the pin's internal pull-up resistor | + Minimum time between detection broadcasts | Minimum time between alert broadcasts | + State Broadcast Interval | Periodic state broadcast interval | + Send bell with alert message | Include bell character in alerts | + Friendly name | Custom name for this sensor | ### Paxcounter module People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. - Setting | Descrición | - -------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | - Paxcounter enabled | Activate people counting | - Update interval (seconds) | How often to report counts | - Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) | - BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | + Setting | Descrición | + --------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | + Paxcounter enabled | Activate people counting | + Update Interval | How often to report counts | + WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) | + BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) | > 💡 **Tip:** Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. diff --git a/main/docs/gl-rES/user/settings-radio-user.html b/main/docs/gl-rES/user/settings-radio-user.html index 602ee6bd05..757a9b6219 100644 --- a/main/docs/gl-rES/user/settings-radio-user.html +++ b/main/docs/gl-rES/user/settings-radio-user.html @@ -71,24 +71,24 @@ On **Settings → Device configuration → Device**. On **Settings → LoRa**. - Setting | Descrición | Default | - ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- | - Rexión | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) | - Presets | Speed/range tradeoff | LongFast | - Number of Hops | Maximum retransmit hops | 3 | - Transmit Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | - Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | - Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | - Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset | - Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | - Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset | - Frequency Slot | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) | - Transmit Enabled | Turning this off makes the node receive-only | On | - Override Duty Cycle | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | - Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | - Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | - RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | - PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | + Setting | Descrición | Default | + --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- | + Rexión | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) | + Presets | Speed/range tradeoff | LongFast | + Number of Hops | Maximum retransmit hops | 3 | + Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) | + Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | + Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | + Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset | + Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | + Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset | + Frequency Slot | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) | + Transmit Enabled | Turning this off makes the node receive-only | On | + Override Duty Cycle | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | + Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | + Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | + RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | + PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn't appear in another. Changing region can therefore leave your current preset diff --git a/main/docs/hr-rHR/user/discovery.html b/main/docs/hr-rHR/user/discovery.html index 1be8e47d0c..464db4ed75 100644 --- a/main/docs/hr-rHR/user/discovery.html +++ b/main/docs/hr-rHR/user/discovery.html @@ -161,7 +161,7 @@ The Neighbor Info module lets each node broadcast a list of the nodes it can **d 1. Navigate to **Settings → Module configuration → Neighbor Info**. 2. Enable the module. -3. Set **Update interval (seconds)**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. +3. Set **Update Interval**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. 4. Turn on **Transmit over LoRa**. Without it, your neighbor list goes only to MQTT and to this app, never over the air. Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. diff --git a/main/docs/hr-rHR/user/mqtt.html b/main/docs/hr-rHR/user/mqtt.html index 8131d64b8c..79f7b951e4 100644 --- a/main/docs/hr-rHR/user/mqtt.html +++ b/main/docs/hr-rHR/user/mqtt.html @@ -90,7 +90,7 @@ Configure your node to point to your private broker with appropriate credentials When **Map reporting** is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. -Turning it on opens a consent card. Turn on **I agree.** and choose a **Map reporting interval (seconds)** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. +Turning it on opens a consent card. Turn on **I agree.** and choose a **Map Publish Interval** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at [meshmap.net](https://meshmap.net) and similar community map services. diff --git a/main/docs/hr-rHR/user/settings-module-admin.html b/main/docs/hr-rHR/user/settings-module-admin.html index 02ff060f97..995a186bd9 100644 --- a/main/docs/hr-rHR/user/settings-module-admin.html +++ b/main/docs/hr-rHR/user/settings-module-admin.html @@ -51,11 +51,11 @@ Turning **Map reporting** on reveals a consent card headed _Consent to Share Une via MQTT_, with an **I agree.** switch under it. The rest of the card doesn't exist on screen until you agree: - Setting | Opis | - --------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | - I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it | - Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units | - Map reporting interval (seconds) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | + Setting | Opis | + ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | + I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it | + Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units | + Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | See [MQTT](mqtt) for a detailed usage guide including encryption, privacy, and broker setup. @@ -80,20 +80,20 @@ Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devi There are two independent triggers — an incoming **message**, and a received **bell** character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. - Setting | Opis | - ------------------------------------------------- | --------------------------------------------------------------------------------------------------- | - External notification enabled | Master toggle for the module | - Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | - Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | - Output LED (GPIO) | Pin the LED is wired to | - Output LED active high | Whether the LED pin is active high or low | - Output buzzer (GPIO) | Pin the buzzer is wired to | - Output vibra (GPIO) | Pin the vibration motor is wired to | - Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | - Use I2S as buzzer | Send the alert through an I2S audio output instead | - Output duration (milliseconds) | How long a single alert lasts | - Nag timeout (seconds) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | - Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | + Setting | Opis | + --------------------------------------- | --------------------------------------------------------------------------------------------------- | + External notification enabled | Master toggle for the module | + Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | + Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | + Output LED (GPIO) | Pin the LED is wired to | + Output LED active high | Whether the LED pin is active high or low | + Output buzzer (GPIO) | Pin the buzzer is wired to | + Output vibra (GPIO) | Pin the vibration motor is wired to | + Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | + Use I2S as buzzer | Send the alert through an I2S audio output instead | + GPIO Output Duration | How long a single alert lasts | + Nag Timeout | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | + Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | ### Store & Forward module @@ -122,7 +122,7 @@ Automated range testing tool for evaluating link quality between nodes. When ena Setting | Opis | -------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- | Range test enabled | Activate range testing | - Sender message interval (seconds) | Time between test transmissions, chosen from a dropdown of fixed intervals | + Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals | Save .CSV in storage (ESP32 only) | Log received test data to the node's own filesystem. ESP32 hardware only | ### Telemetry module @@ -195,11 +195,11 @@ GPIO control over the mesh network. Allows a remote node to read or write GPIO p Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. - Setting | Opis | - -------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | - Neighbor Info enabled | Activate neighbor broadcasting | - Update interval (seconds) | How often to broadcast neighbor list | - Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | + Setting | Opis | + --------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | + Neighbor Info enabled | Activate neighbor broadcasting | + Update Interval | How often to broadcast neighbor list | + Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | See [Local Mesh Discovery](discovery) for how to use neighbor data for mesh topology exploration. @@ -217,27 +217,27 @@ Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. C Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. - Setting | Opis | - ---------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | - Detection Sensor enabled | Activate detection sensor | - GPIO pin to monitor | GPIO pin connected to sensor | - Detection trigger type | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) | - Use INPUT_PULLUP mode | Enable the pin's internal pull-up resistor | - Minimum broadcast (seconds) | Minimum time between alert broadcasts | - State broadcast (seconds) | Periodic state broadcast interval | - Send bell with alert message | Include bell character in alerts | - Friendly name | Custom name for this sensor | + Setting | Opis | + ------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------- | + Detection Sensor enabled | Activate detection sensor | + GPIO pin to monitor | GPIO pin connected to sensor | + Detection trigger type | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) | + Use INPUT_PULLUP mode | Enable the pin's internal pull-up resistor | + Minimum time between detection broadcasts | Minimum time between alert broadcasts | + State Broadcast Interval | Periodic state broadcast interval | + Send bell with alert message | Include bell character in alerts | + Friendly name | Custom name for this sensor | ### Paxcounter module People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. - Setting | Opis | - -------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | - Paxcounter enabled | Activate people counting | - Update interval (seconds) | How often to report counts | - Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) | - BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | + Setting | Opis | + --------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | + Paxcounter enabled | Activate people counting | + Update Interval | How often to report counts | + WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) | + BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) | > 💡 **Tip:** Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. diff --git a/main/docs/hr-rHR/user/settings-radio-user.html b/main/docs/hr-rHR/user/settings-radio-user.html index 75fdbd853b..e73b695306 100644 --- a/main/docs/hr-rHR/user/settings-radio-user.html +++ b/main/docs/hr-rHR/user/settings-radio-user.html @@ -71,24 +71,24 @@ On **Settings → Device configuration → Device**. On **Settings → LoRa**. - Setting | Opis | Zadano | - ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- | - Regija | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) | - Presets | Speed/range tradeoff | LongFast | - Number of Hops | Maximum retransmit hops | 3 | - Transmit Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | - Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | - Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | - Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset | - Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | - Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset | - Frequency Slot | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) | - Transmit Enabled | Turning this off makes the node receive-only | On | - Override Duty Cycle | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | - Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | - Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | - RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | - PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | + Setting | Opis | Zadano | + --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- | + Regija | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) | + Presets | Speed/range tradeoff | LongFast | + Number of Hops | Maximum retransmit hops | 3 | + Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) | + Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | + Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | + Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset | + Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | + Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset | + Frequency Slot | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) | + Transmit Enabled | Turning this off makes the node receive-only | On | + Override Duty Cycle | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | + Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | + Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | + RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | + PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn't appear in another. Changing region can therefore leave your current preset diff --git a/main/docs/ht-rHT/user/discovery.html b/main/docs/ht-rHT/user/discovery.html index 00b4651309..34a6991de1 100644 --- a/main/docs/ht-rHT/user/discovery.html +++ b/main/docs/ht-rHT/user/discovery.html @@ -161,7 +161,7 @@ The Neighbor Info module lets each node broadcast a list of the nodes it can **d 1. Navigate to **Settings → Module configuration → Neighbor Info**. 2. Enable the module. -3. Set **Update interval (seconds)**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. +3. Set **Update Interval**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. 4. Turn on **Transmit over LoRa**. Without it, your neighbor list goes only to MQTT and to this app, never over the air. Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. diff --git a/main/docs/ht-rHT/user/mqtt.html b/main/docs/ht-rHT/user/mqtt.html index ea41467f13..2f5b08a625 100644 --- a/main/docs/ht-rHT/user/mqtt.html +++ b/main/docs/ht-rHT/user/mqtt.html @@ -90,7 +90,7 @@ Configure your node to point to your private broker with appropriate credentials When **Map reporting** is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. -Turning it on opens a consent card. Turn on **I agree.** and choose a **Map reporting interval (seconds)** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. +Turning it on opens a consent card. Turn on **I agree.** and choose a **Map Publish Interval** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at [meshmap.net](https://meshmap.net) and similar community map services. diff --git a/main/docs/ht-rHT/user/settings-module-admin.html b/main/docs/ht-rHT/user/settings-module-admin.html index 242a10b1aa..60afe1abc0 100644 --- a/main/docs/ht-rHT/user/settings-module-admin.html +++ b/main/docs/ht-rHT/user/settings-module-admin.html @@ -51,11 +51,11 @@ Turning **Map reporting** on reveals a consent card headed _Consent to Share Une via MQTT_, with an **I agree.** switch under it. The rest of the card doesn't exist on screen until you agree: - Setting | Deskripsyon | - --------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | - I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it | - Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units | - Map reporting interval (seconds) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | + Setting | Deskripsyon | + ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | + I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it | + Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units | + Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | See [MQTT](mqtt) for a detailed usage guide including encryption, privacy, and broker setup. @@ -80,20 +80,20 @@ Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devi There are two independent triggers — an incoming **message**, and a received **bell** character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. - Setting | Deskripsyon | - ------------------------------------------------- | --------------------------------------------------------------------------------------------------- | - External notification enabled | Master toggle for the module | - Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | - Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | - Output LED (GPIO) | Pin the LED is wired to | - Output LED active high | Whether the LED pin is active high or low | - Output buzzer (GPIO) | Pin the buzzer is wired to | - Output vibra (GPIO) | Pin the vibration motor is wired to | - Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | - Use I2S as buzzer | Send the alert through an I2S audio output instead | - Output duration (milliseconds) | How long a single alert lasts | - Nag timeout (seconds) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | - Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | + Setting | Deskripsyon | + --------------------------------------- | --------------------------------------------------------------------------------------------------- | + External notification enabled | Master toggle for the module | + Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | + Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | + Output LED (GPIO) | Pin the LED is wired to | + Output LED active high | Whether the LED pin is active high or low | + Output buzzer (GPIO) | Pin the buzzer is wired to | + Output vibra (GPIO) | Pin the vibration motor is wired to | + Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | + Use I2S as buzzer | Send the alert through an I2S audio output instead | + GPIO Output Duration | How long a single alert lasts | + Nag Timeout | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | + Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | ### Store & Forward module @@ -122,7 +122,7 @@ Automated range testing tool for evaluating link quality between nodes. When ena Setting | Deskripsyon | -------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- | Range test enabled | Activate range testing | - Sender message interval (seconds) | Time between test transmissions, chosen from a dropdown of fixed intervals | + Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals | Save .CSV in storage (ESP32 only) | Log received test data to the node's own filesystem. ESP32 hardware only | ### Telemetry module @@ -195,11 +195,11 @@ GPIO control over the mesh network. Allows a remote node to read or write GPIO p Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. - Setting | Deskripsyon | - -------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | - Neighbor Info enabled | Activate neighbor broadcasting | - Update interval (seconds) | How often to broadcast neighbor list | - Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | + Setting | Deskripsyon | + --------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | + Neighbor Info enabled | Activate neighbor broadcasting | + Update Interval | How often to broadcast neighbor list | + Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | See [Local Mesh Discovery](discovery) for how to use neighbor data for mesh topology exploration. @@ -217,27 +217,27 @@ Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. C Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. - Setting | Deskripsyon | - ---------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | - Detection Sensor enabled | Activate detection sensor | - GPIO pin to monitor | GPIO pin connected to sensor | - Detection trigger type | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) | - Use INPUT_PULLUP mode | Enable the pin's internal pull-up resistor | - Minimum broadcast (seconds) | Minimum time between alert broadcasts | - State broadcast (seconds) | Periodic state broadcast interval | - Send bell with alert message | Include bell character in alerts | - Friendly name | Custom name for this sensor | + Setting | Deskripsyon | + ------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------- | + Detection Sensor enabled | Activate detection sensor | + GPIO pin to monitor | GPIO pin connected to sensor | + Detection trigger type | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) | + Use INPUT_PULLUP mode | Enable the pin's internal pull-up resistor | + Minimum time between detection broadcasts | Minimum time between alert broadcasts | + State Broadcast Interval | Periodic state broadcast interval | + Send bell with alert message | Include bell character in alerts | + Friendly name | Custom name for this sensor | ### Paxcounter module People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. - Setting | Deskripsyon | - -------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | - Paxcounter enabled | Activate people counting | - Update interval (seconds) | How often to report counts | - Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) | - BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | + Setting | Deskripsyon | + --------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | + Paxcounter enabled | Activate people counting | + Update Interval | How often to report counts | + WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) | + BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) | > 💡 **Tip:** Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. diff --git a/main/docs/ht-rHT/user/settings-radio-user.html b/main/docs/ht-rHT/user/settings-radio-user.html index f42f9b5b61..4358ca4a66 100644 --- a/main/docs/ht-rHT/user/settings-radio-user.html +++ b/main/docs/ht-rHT/user/settings-radio-user.html @@ -71,24 +71,24 @@ On **Settings → Device configuration → Device**. On **Settings → LoRa**. - Setting | Deskripsyon | Default | - ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- | - Rejyon | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) | - Presets | Speed/range tradeoff | LongFast | - Number of Hops | Maximum retransmit hops | 3 | - Transmit Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | - Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | - Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | - Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset | - Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | - Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset | - Frequency Slot | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) | - Transmit Enabled | Turning this off makes the node receive-only | On | - Override Duty Cycle | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | - Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | - Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | - RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | - PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | + Setting | Deskripsyon | Default | + --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- | + Rejyon | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) | + Presets | Speed/range tradeoff | LongFast | + Number of Hops | Maximum retransmit hops | 3 | + Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) | + Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | + Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | + Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset | + Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | + Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset | + Frequency Slot | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) | + Transmit Enabled | Turning this off makes the node receive-only | On | + Override Duty Cycle | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | + Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | + Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | + RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | + PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn't appear in another. Changing region can therefore leave your current preset diff --git a/main/docs/hu-rHU/user/discovery.html b/main/docs/hu-rHU/user/discovery.html index 36a4e01c82..bc90e64a51 100644 --- a/main/docs/hu-rHU/user/discovery.html +++ b/main/docs/hu-rHU/user/discovery.html @@ -161,7 +161,7 @@ The Neighbor Info module lets each node broadcast a list of the nodes it can **d 1. Navigate to **Settings → Module configuration → Neighbor Info**. 2. Enable the module. -3. Set **Update interval (seconds)**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. +3. Set **Update Interval**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. 4. Turn on **Transmit over LoRa**. Without it, your neighbor list goes only to MQTT and to this app, never over the air. Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. diff --git a/main/docs/hu-rHU/user/mqtt.html b/main/docs/hu-rHU/user/mqtt.html index d446ab3ea2..d097cacfd3 100644 --- a/main/docs/hu-rHU/user/mqtt.html +++ b/main/docs/hu-rHU/user/mqtt.html @@ -90,7 +90,7 @@ Configure your node to point to your private broker with appropriate credentials When **Map reporting** is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. -Turning it on opens a consent card. Turn on **I agree.** and choose a **Map reporting interval (seconds)** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. +Turning it on opens a consent card. Turn on **I agree.** and choose a **Map Publish Interval** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at [meshmap.net](https://meshmap.net) and similar community map services. diff --git a/main/docs/hu-rHU/user/settings-module-admin.html b/main/docs/hu-rHU/user/settings-module-admin.html index 7964d4fb88..9cb7d7cc4e 100644 --- a/main/docs/hu-rHU/user/settings-module-admin.html +++ b/main/docs/hu-rHU/user/settings-module-admin.html @@ -51,11 +51,11 @@ Turning **Map reporting** on reveals a consent card headed _Consent to Share Une via MQTT_, with an **I agree.** switch under it. The rest of the card doesn't exist on screen until you agree: - Setting | Leírás | - --------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | - Elfogadom. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it | - Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units | - Térképadat-jelentés intervalluma (másodperc) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | + Setting | Leírás | + -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | + Elfogadom. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it | + Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units | + Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | See [MQTT](mqtt) for a detailed usage guide including encryption, privacy, and broker setup. @@ -80,20 +80,20 @@ Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devi There are two independent triggers — an incoming **message**, and a received **bell** character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. - Setting | Leírás | - --------------------------------------------------------- | --------------------------------------------------------------------------------------------------- | - Külső értesítés engedélyezve | Master toggle for the module | - Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | - Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | - Kimeneti LED (GPIO) | Pin the LED is wired to | - Kimeneti LED aktív magas szint | Whether the LED pin is active high or low | - Kimeneti csipogó (GPIO) | Pin the buzzer is wired to | - Kimeneti rezgő (GPIO) | Pin the vibration motor is wired to | - PWM csipogó használata | Drive the buzzer with PWM, which allows tones rather than a single pitch | - I2S használata csipogóként | Send the alert through an I2S audio output instead | - Kimeneti időtartam (ezredmásodperc) | How long a single alert lasts | - Ismétlő riasztás időkorlát (másodperc) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | - Csengőhang | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | + Setting | Leírás | + ------------------------------------------ | --------------------------------------------------------------------------------------------------- | + Külső értesítés engedélyezve | Master toggle for the module | + Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | + Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | + Kimeneti LED (GPIO) | Pin the LED is wired to | + Kimeneti LED aktív magas szint | Whether the LED pin is active high or low | + Kimeneti csipogó (GPIO) | Pin the buzzer is wired to | + Kimeneti rezgő (GPIO) | Pin the vibration motor is wired to | + PWM csipogó használata | Drive the buzzer with PWM, which allows tones rather than a single pitch | + I2S használata csipogóként | Send the alert through an I2S audio output instead | + GPIO Output Duration | How long a single alert lasts | + Nag Timeout | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | + Csengőhang | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | ### Store & Forward module @@ -122,7 +122,7 @@ Automated range testing tool for evaluating link quality between nodes. When ena Setting | Leírás | ------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------- | Hatótáv-teszt engedélyezve | Activate range testing | - Küldési üzenetintervallum (másodperc) | Time between test transmissions, chosen from a dropdown of fixed intervals | + Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals | .CSV mentése a tárhelyre (csak ESP32) | Log received test data to the node's own filesystem. ESP32 hardware only | ### Telemetry module @@ -195,11 +195,11 @@ GPIO control over the mesh network. Allows a remote node to read or write GPIO p Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. - Setting | Leírás | - ----------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | - Szomszéd-információ engedélyezve | Activate neighbor broadcasting | - Frissítési intervallum (másodperc) | How often to broadcast neighbor list | - Továbbítás LoRa-n keresztül | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | + Setting | Leírás | + -------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | + Szomszéd-információ engedélyezve | Activate neighbor broadcasting | + Frissítési időköz | How often to broadcast neighbor list | + Továbbítás LoRa-n keresztül | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | See [Local Mesh Discovery](discovery) for how to use neighbor data for mesh topology exploration. @@ -217,27 +217,27 @@ Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. C Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. - Setting | Leírás | - ------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------- | - Érzékelő szenzor engedélyezve | Activate detection sensor | - Figyelt GPIO láb | GPIO pin connected to sensor | - Érzékelési ravasztípus | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) | - INPUT_PULLUP mód használata | Enable the pin's internal pull-up resistor | - Minimális sugárzási idő (másodperc) | Minimum time between alert broadcasts | - Állapot-sugárzás (másodperc) | Periodic state broadcast interval | - Harangjel küldése riasztási üzenettel | Include bell character in alerts | - Barátságos név | Custom name for this sensor | + Setting | Leírás | + ------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------- | + Érzékelő szenzor engedélyezve | Activate detection sensor | + Figyelt GPIO láb | GPIO pin connected to sensor | + Érzékelési ravasztípus | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) | + INPUT_PULLUP mód használata | Enable the pin's internal pull-up resistor | + Minimum time between detection broadcasts | Minimum time between alert broadcasts | + State Broadcast Interval | Periodic state broadcast interval | + Harangjel küldése riasztási üzenettel | Include bell character in alerts | + Barátságos név | Custom name for this sensor | ### Paxcounter module People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. - Setting | Leírás | - ----------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | - Paxcounter engedélyezve | Activate people counting | - Frissítési intervallum (másodperc) | How often to report counts | - Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) | - BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | + Setting | Leírás | + --------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | + Paxcounter engedélyezve | Activate people counting | + Frissítési időköz | How often to report counts | + WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) | + BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) | > 💡 **Tip:** Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. diff --git a/main/docs/hu-rHU/user/settings-radio-user.html b/main/docs/hu-rHU/user/settings-radio-user.html index 2240e1a7cd..0faa7eeeca 100644 --- a/main/docs/hu-rHU/user/settings-radio-user.html +++ b/main/docs/hu-rHU/user/settings-radio-user.html @@ -71,24 +71,24 @@ On **Settings → Device configuration → Device**. On **Settings → LoRa**. - Setting | Leírás | Alapértelmezett | - ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- | - Régió | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) | - Előbeállítások | Speed/range tradeoff | LongFast | - Ugrások száma | Maximum retransmit hops | 3 | - Adásteljesítmény | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | - Frekvencia felülbírálása | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | - Előbeállítás használata | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | - Szórási Faktor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset | - Kódolási ráta | Manual mode only: 5–8. More redundancy costs airtime | From preset | - Sávszélesség | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset | - Frekvencia sáv | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) | - Adás engedélyezve | Turning this off makes the node receive-only | On | - Duty Cycle felülbírálása | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | - MQTT figyelmen kívül hagyása | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | - MQTT-re továbbítható | Allow your packets to be forwarded to MQTT by gateways | Off | - RX fokozott erősítés | Extra receive gain on SX126x radios; costs a little current | Off | - PA ventilátor letiltva | Turn off the power-amplifier fan on hardware that has one | Off | + Setting | Leírás | Alapértelmezett | + --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- | + Régió | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) | + Előbeállítások | Speed/range tradeoff | LongFast | + Ugrások száma | Maximum retransmit hops | 3 | + Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) | + Frekvencia felülbírálása | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | + Előbeállítás használata | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | + Szórási Faktor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset | + Kódolási ráta | Manual mode only: 5–8. More redundancy costs airtime | From preset | + Sávszélesség | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset | + Frekvencia sáv | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) | + Adás engedélyezve | Turning this off makes the node receive-only | On | + Duty Cycle felülbírálása | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | + MQTT figyelmen kívül hagyása | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | + MQTT-re továbbítható | Allow your packets to be forwarded to MQTT by gateways | Off | + RX fokozott erősítés | Extra receive gain on SX126x radios; costs a little current | Off | + PA ventilátor letiltva | Turn off the power-amplifier fan on hardware that has one | Off | The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn't appear in another. Changing region can therefore leave your current preset diff --git a/main/docs/is-rIS/user/discovery.html b/main/docs/is-rIS/user/discovery.html index f3df6b7641..4c265fc49e 100644 --- a/main/docs/is-rIS/user/discovery.html +++ b/main/docs/is-rIS/user/discovery.html @@ -161,7 +161,7 @@ The Neighbor Info module lets each node broadcast a list of the nodes it can **d 1. Navigate to **Settings → Module configuration → Neighbor Info**. 2. Enable the module. -3. Set **Update interval (seconds)**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. +3. Set **Update Interval**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. 4. Turn on **Transmit over LoRa**. Without it, your neighbor list goes only to MQTT and to this app, never over the air. Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. diff --git a/main/docs/is-rIS/user/mqtt.html b/main/docs/is-rIS/user/mqtt.html index 496f902b95..7f5025e105 100644 --- a/main/docs/is-rIS/user/mqtt.html +++ b/main/docs/is-rIS/user/mqtt.html @@ -90,7 +90,7 @@ Configure your node to point to your private broker with appropriate credentials When **Map reporting** is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. -Turning it on opens a consent card. Turn on **I agree.** and choose a **Map reporting interval (seconds)** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. +Turning it on opens a consent card. Turn on **I agree.** and choose a **Map Publish Interval** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at [meshmap.net](https://meshmap.net) and similar community map services. diff --git a/main/docs/is-rIS/user/settings-module-admin.html b/main/docs/is-rIS/user/settings-module-admin.html index 53e3c57c82..3cea55caec 100644 --- a/main/docs/is-rIS/user/settings-module-admin.html +++ b/main/docs/is-rIS/user/settings-module-admin.html @@ -51,11 +51,11 @@ Turning **Map reporting** on reveals a consent card headed _Consent to Share Une via MQTT_, with an **I agree.** switch under it. The rest of the card doesn't exist on screen until you agree: - Setting | Lýsing | - --------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | - I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it | - Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units | - Map reporting interval (seconds) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | + Setting | Lýsing | + ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | + I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it | + Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units | + Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | See [MQTT](mqtt) for a detailed usage guide including encryption, privacy, and broker setup. @@ -80,20 +80,20 @@ Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devi There are two independent triggers — an incoming **message**, and a received **bell** character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. - Setting | Lýsing | - ------------------------------------------------- | --------------------------------------------------------------------------------------------------- | - External notification enabled | Master toggle for the module | - Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | - Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | - Output LED (GPIO) | Pin the LED is wired to | - Output LED active high | Whether the LED pin is active high or low | - Output buzzer (GPIO) | Pin the buzzer is wired to | - Output vibra (GPIO) | Pin the vibration motor is wired to | - Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | - Use I2S as buzzer | Send the alert through an I2S audio output instead | - Output duration (milliseconds) | How long a single alert lasts | - Nag timeout (seconds) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | - Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | + Setting | Lýsing | + --------------------------------------- | --------------------------------------------------------------------------------------------------- | + External notification enabled | Master toggle for the module | + Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | + Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | + Output LED (GPIO) | Pin the LED is wired to | + Output LED active high | Whether the LED pin is active high or low | + Output buzzer (GPIO) | Pin the buzzer is wired to | + Output vibra (GPIO) | Pin the vibration motor is wired to | + Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | + Use I2S as buzzer | Send the alert through an I2S audio output instead | + GPIO Output Duration | How long a single alert lasts | + Nag Timeout | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | + Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | ### Store & Forward module @@ -122,7 +122,7 @@ Automated range testing tool for evaluating link quality between nodes. When ena Setting | Lýsing | -------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- | Range test enabled | Activate range testing | - Sender message interval (seconds) | Time between test transmissions, chosen from a dropdown of fixed intervals | + Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals | Save .CSV in storage (ESP32 only) | Log received test data to the node's own filesystem. ESP32 hardware only | ### Telemetry module @@ -195,11 +195,11 @@ GPIO control over the mesh network. Allows a remote node to read or write GPIO p Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. - Setting | Lýsing | - -------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | - Neighbor Info enabled | Activate neighbor broadcasting | - Update interval (seconds) | How often to broadcast neighbor list | - Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | + Setting | Lýsing | + --------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | + Neighbor Info enabled | Activate neighbor broadcasting | + Update Interval | How often to broadcast neighbor list | + Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | See [Local Mesh Discovery](discovery) for how to use neighbor data for mesh topology exploration. @@ -217,27 +217,27 @@ Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. C Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. - Setting | Lýsing | - ---------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | - Detection Sensor enabled | Activate detection sensor | - GPIO pin to monitor | GPIO pin connected to sensor | - Detection trigger type | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) | - Use INPUT_PULLUP mode | Enable the pin's internal pull-up resistor | - Minimum broadcast (seconds) | Minimum time between alert broadcasts | - State broadcast (seconds) | Periodic state broadcast interval | - Send bell with alert message | Include bell character in alerts | - Friendly name | Custom name for this sensor | + Setting | Lýsing | + ------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------- | + Detection Sensor enabled | Activate detection sensor | + GPIO pin to monitor | GPIO pin connected to sensor | + Detection trigger type | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) | + Use INPUT_PULLUP mode | Enable the pin's internal pull-up resistor | + Minimum time between detection broadcasts | Minimum time between alert broadcasts | + State Broadcast Interval | Periodic state broadcast interval | + Send bell with alert message | Include bell character in alerts | + Friendly name | Custom name for this sensor | ### Paxcounter module People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. - Setting | Lýsing | - -------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | - Paxcounter enabled | Activate people counting | - Update interval (seconds) | How often to report counts | - Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) | - BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | + Setting | Lýsing | + --------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | + Paxcounter enabled | Activate people counting | + Update Interval | How often to report counts | + WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) | + BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) | > 💡 **Tip:** Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. diff --git a/main/docs/is-rIS/user/settings-radio-user.html b/main/docs/is-rIS/user/settings-radio-user.html index f8e269c896..e0bbf2a792 100644 --- a/main/docs/is-rIS/user/settings-radio-user.html +++ b/main/docs/is-rIS/user/settings-radio-user.html @@ -71,24 +71,24 @@ On **Settings → Device configuration → Device**. On **Settings → LoRa**. - Setting | Lýsing | Default | - ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- | - Svæði | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) | - Presets | Speed/range tradeoff | LongFast | - Number of Hops | Maximum retransmit hops | 3 | - Transmit Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | - Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | - Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | - Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset | - Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | - Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset | - Frequency Slot | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) | - Transmit Enabled | Turning this off makes the node receive-only | On | - Override Duty Cycle | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | - Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | - Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | - RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | - PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | + Setting | Lýsing | Default | + --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- | + Svæði | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) | + Presets | Speed/range tradeoff | LongFast | + Number of Hops | Maximum retransmit hops | 3 | + Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) | + Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | + Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | + Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset | + Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | + Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset | + Frequency Slot | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) | + Transmit Enabled | Turning this off makes the node receive-only | On | + Override Duty Cycle | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | + Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | + Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | + RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | + PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn't appear in another. Changing region can therefore leave your current preset diff --git a/main/docs/it-rIT/user/discovery.html b/main/docs/it-rIT/user/discovery.html index e22e6fc76d..521842edc3 100644 --- a/main/docs/it-rIT/user/discovery.html +++ b/main/docs/it-rIT/user/discovery.html @@ -161,7 +161,7 @@ The Neighbor Info module lets each node broadcast a list of the nodes it can **d 1. Navigate to **Settings → Module configuration → Neighbor Info**. 2. Enable the module. -3. Set **Update interval (seconds)**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. +3. Set **Update Interval**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. 4. Turn on **Transmit over LoRa**. Without it, your neighbor list goes only to MQTT and to this app, never over the air. Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. diff --git a/main/docs/it-rIT/user/mqtt.html b/main/docs/it-rIT/user/mqtt.html index 4145aaf04b..b5d6ee3cf9 100644 --- a/main/docs/it-rIT/user/mqtt.html +++ b/main/docs/it-rIT/user/mqtt.html @@ -90,7 +90,7 @@ Configure your node to point to your private broker with appropriate credentials When **Map reporting** is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. -Turning it on opens a consent card. Turn on **I agree.** and choose a **Map reporting interval (seconds)** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. +Turning it on opens a consent card. Turn on **I agree.** and choose a **Map Publish Interval** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at [meshmap.net](https://meshmap.net) and similar community map services. diff --git a/main/docs/it-rIT/user/settings-module-admin.html b/main/docs/it-rIT/user/settings-module-admin.html index ca9672728c..acac7c261c 100644 --- a/main/docs/it-rIT/user/settings-module-admin.html +++ b/main/docs/it-rIT/user/settings-module-admin.html @@ -51,11 +51,11 @@ Turning **Map reporting** on reveals a consent card headed _Consent to Share Une via MQTT_, with an **I agree.** switch under it. The rest of the card doesn't exist on screen until you agree: - Impostazione | Descrizione | - ---------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | - Sono d’accordo. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it | - Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units | - Intervallo di segnalazione su mappa (secondi) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | + Impostazione | Descrizione | + ------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | + Sono d’accordo. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it | + Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units | + Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | See [MQTT](mqtt) for a detailed usage guide including encryption, privacy, and broker setup. @@ -80,20 +80,20 @@ Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devi There are two independent triggers — an incoming **message**, and a received **bell** character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. - Impostazione | Descrizione | - --------------------------------------------------- | --------------------------------------------------------------------------------------------------- | - Notifica esterna attivata | Master toggle for the module | - Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | - Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | - LED Output (GPIO) | Pin the LED is wired to | - Output per LED active high | Whether the LED pin is active high or low | - Output buzzer (GPIO) | Pin the buzzer is wired to | - Output vibrazione (GPIO) | Pin the vibration motor is wired to | - Usa buzzer PWM | Drive the buzzer with PWM, which allows tones rather than a single pitch | - Usa I2S come buzzer | Send the alert through an I2S audio output instead | - Durata output (millisecondi) | How long a single alert lasts | - Timeout chiusura popup (secondi) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | - Suoneria | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | + Impostazione | Descrizione | + ------------------------------------------- | --------------------------------------------------------------------------------------------------- | + Notifica esterna attivata | Master toggle for the module | + Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | + Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | + LED Output (GPIO) | Pin the LED is wired to | + Output per LED active high | Whether the LED pin is active high or low | + Output buzzer (GPIO) | Pin the buzzer is wired to | + Output vibrazione (GPIO) | Pin the vibration motor is wired to | + Usa buzzer PWM | Drive the buzzer with PWM, which allows tones rather than a single pitch | + Usa I2S come buzzer | Send the alert through an I2S audio output instead | + GPIO Output Duration | How long a single alert lasts | + Nag Timeout | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | + Suoneria | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | ### Store & Forward module @@ -122,7 +122,7 @@ Automated range testing tool for evaluating link quality between nodes. When ena Impostazione | Descrizione | ------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------- | Test distanza massima abilitato | Activate range testing | - Intervallo messaggio mittente (secondi) | Time between test transmissions, chosen from a dropdown of fixed intervals | + Intervallo Del Mittente | Time between test transmissions, chosen from a dropdown of fixed intervals | Salva .CSV nella memoria (solo ESP32) | Log received test data to the node's own filesystem. ESP32 hardware only | ### Telemetry module @@ -195,11 +195,11 @@ GPIO control over the mesh network. Allows a remote node to read or write GPIO p Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. - Impostazione | Descrizione | - -------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | - Info Nodi Vicini abilitato | Activate neighbor broadcasting | - Intervallo di aggiornamento (secondi) | How often to broadcast neighbor list | - Trasmettere su LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | + Impostazione | Descrizione | + ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | + Info Nodi Vicini abilitato | Activate neighbor broadcasting | + Intervallo Interrogazione GPS | How often to broadcast neighbor list | + Trasmettere su LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | See [Local Mesh Discovery](discovery) for how to use neighbor data for mesh topology exploration. @@ -217,27 +217,27 @@ Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. C Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. - Impostazione | Descrizione | - ------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------- | - Sensore Rilevamento attivo | Activate detection sensor | - Pin GPIO da monitorare | GPIO pin connected to sensor | - Tipo di trigger di rilevamento | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) | - Usa modalità INPUT_PULLUP | Enable the pin's internal pull-up resistor | - Trasmissione minima (secondi) | Minimum time between alert broadcasts | - Trasmissione stato (secondi) | Periodic state broadcast interval | - Invia campanella con messaggio di avviso | Include bell character in alerts | - Nome semplificato | Custom name for this sensor | + Impostazione | Descrizione | + ---------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | + Sensore Rilevamento attivo | Activate detection sensor | + Pin GPIO da monitorare | GPIO pin connected to sensor | + Tipo di trigger di rilevamento | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) | + Usa modalità INPUT_PULLUP | Enable the pin's internal pull-up resistor | + Minimum time between detection broadcasts | Minimum time between alert broadcasts | + Intervallo Di Trasmissione | Periodic state broadcast interval | + Invia campanella con messaggio di avviso | Include bell character in alerts | + Nome semplificato | Custom name for this sensor | ### Paxcounter module People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. - Impostazione | Descrizione | - -------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | - Paxcounter abilitato | Activate people counting | - Intervallo di aggiornamento (secondi) | How often to report counts | - Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) | - BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | + Impostazione | Descrizione | + --------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | + Paxcounter abilitato | Activate people counting | + Intervallo Interrogazione GPS | How often to report counts | + WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) | + BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) | > 💡 **Tip:** Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. diff --git a/main/docs/it-rIT/user/settings-radio-user.html b/main/docs/it-rIT/user/settings-radio-user.html index 2efa2d9a5f..c8e38be3d0 100644 --- a/main/docs/it-rIT/user/settings-radio-user.html +++ b/main/docs/it-rIT/user/settings-radio-user.html @@ -71,24 +71,24 @@ On **Settings → Device configuration → Device**. On **Settings → LoRa**. - Impostazione | Descrizione | Predefinito | - ------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- | - Regione | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) | - Preset | Speed/range tradeoff | LongFast | - Numero di Hop | Maximum retransmit hops | 3 | - Potenza di Trasmissione | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | - Sovrascrivi Frequenza | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | - Usa Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | - Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset | - Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | - Larghezza di banda | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset | - Slot di Frequenza | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) | - Trasmissione Abilitata | Turning this off makes the node receive-only | On | - Ignora limite di Duty Cycle | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Disattivato | - Ignora MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | - OK per MQTT | Allow your packets to be forwarded to MQTT by gateways | Disattivato | - Migliora guadagno in Ricezione | Extra receive gain on SX126x radios; costs a little current | Disattivato | - Ventola PA disabilitata | Turn off the power-amplifier fan on hardware that has one | Disattivato | + Impostazione | Descrizione | Predefinito | + --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- | + Regione | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) | + Preset | Speed/range tradeoff | LongFast | + Numero di Hop | Maximum retransmit hops | 3 | + Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) | + Sovrascrivi Frequenza | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | + Usa Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | + Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset | + Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | + Larghezza di banda | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset | + Slot di Frequenza | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) | + Trasmissione Abilitata | Turning this off makes the node receive-only | On | + Ignora limite di Duty Cycle | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Disattivato | + Ignora MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | + OK per MQTT | Allow your packets to be forwarded to MQTT by gateways | Disattivato | + Migliora guadagno in Ricezione | Extra receive gain on SX126x radios; costs a little current | Disattivato | + Ventola PA disabilitata | Turn off the power-amplifier fan on hardware that has one | Disattivato | The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn't appear in another. Changing region can therefore leave your current preset diff --git a/main/docs/iw-rIL/user/discovery.html b/main/docs/iw-rIL/user/discovery.html index f1db64183a..580cf984d5 100644 --- a/main/docs/iw-rIL/user/discovery.html +++ b/main/docs/iw-rIL/user/discovery.html @@ -161,7 +161,7 @@ The Neighbor Info module lets each node broadcast a list of the nodes it can **d 1. Navigate to **Settings → Module configuration → Neighbor Info**. 2. Enable the module. -3. Set **Update interval (seconds)**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. +3. Set **Update Interval**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. 4. Turn on **Transmit over LoRa**. Without it, your neighbor list goes only to MQTT and to this app, never over the air. Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. diff --git a/main/docs/iw-rIL/user/mqtt.html b/main/docs/iw-rIL/user/mqtt.html index ff52f5cfb1..bb43ad8b52 100644 --- a/main/docs/iw-rIL/user/mqtt.html +++ b/main/docs/iw-rIL/user/mqtt.html @@ -90,7 +90,7 @@ Configure your node to point to your private broker with appropriate credentials When **Map reporting** is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. -Turning it on opens a consent card. Turn on **I agree.** and choose a **Map reporting interval (seconds)** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. +Turning it on opens a consent card. Turn on **I agree.** and choose a **Map Publish Interval** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at [meshmap.net](https://meshmap.net) and similar community map services. diff --git a/main/docs/iw-rIL/user/settings-module-admin.html b/main/docs/iw-rIL/user/settings-module-admin.html index f149c4cf2e..30e9b992ec 100644 --- a/main/docs/iw-rIL/user/settings-module-admin.html +++ b/main/docs/iw-rIL/user/settings-module-admin.html @@ -51,11 +51,11 @@ Turning **Map reporting** on reveals a consent card headed _Consent to Share Une via MQTT_, with an **I agree.** switch under it. The rest of the card doesn't exist on screen until you agree: - Setting | תיאור | - --------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | - I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it | - Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units | - Map reporting interval (seconds) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | + Setting | תיאור | + ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | + I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it | + Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units | + Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | See [MQTT](mqtt) for a detailed usage guide including encryption, privacy, and broker setup. @@ -80,20 +80,20 @@ Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devi There are two independent triggers — an incoming **message**, and a received **bell** character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. - Setting | תיאור | - ------------------------------------------------- | --------------------------------------------------------------------------------------------------- | - External notification enabled | Master toggle for the module | - Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | - Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | - Output LED (GPIO) | Pin the LED is wired to | - Output LED active high | Whether the LED pin is active high or low | - Output buzzer (GPIO) | Pin the buzzer is wired to | - Output vibra (GPIO) | Pin the vibration motor is wired to | - Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | - Use I2S as buzzer | Send the alert through an I2S audio output instead | - Output duration (milliseconds) | How long a single alert lasts | - Nag timeout (seconds) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | - Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | + Setting | תיאור | + --------------------------------------- | --------------------------------------------------------------------------------------------------- | + External notification enabled | Master toggle for the module | + Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | + Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | + Output LED (GPIO) | Pin the LED is wired to | + Output LED active high | Whether the LED pin is active high or low | + Output buzzer (GPIO) | Pin the buzzer is wired to | + Output vibra (GPIO) | Pin the vibration motor is wired to | + Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | + Use I2S as buzzer | Send the alert through an I2S audio output instead | + GPIO Output Duration | How long a single alert lasts | + Nag Timeout | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | + Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | ### Store & Forward module @@ -122,7 +122,7 @@ Automated range testing tool for evaluating link quality between nodes. When ena Setting | תיאור | -------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- | Range test enabled | Activate range testing | - Sender message interval (seconds) | Time between test transmissions, chosen from a dropdown of fixed intervals | + Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals | Save .CSV in storage (ESP32 only) | Log received test data to the node's own filesystem. ESP32 hardware only | ### Telemetry module @@ -195,11 +195,11 @@ GPIO control over the mesh network. Allows a remote node to read or write GPIO p Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. - Setting | תיאור | - -------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | - Neighbor Info enabled | Activate neighbor broadcasting | - Update interval (seconds) | How often to broadcast neighbor list | - Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | + Setting | תיאור | + --------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | + Neighbor Info enabled | Activate neighbor broadcasting | + Update Interval | How often to broadcast neighbor list | + Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | See [Local Mesh Discovery](discovery) for how to use neighbor data for mesh topology exploration. @@ -217,27 +217,27 @@ Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. C Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. - Setting | תיאור | - ---------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | - Detection Sensor enabled | Activate detection sensor | - GPIO pin to monitor | GPIO pin connected to sensor | - Detection trigger type | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) | - Use INPUT_PULLUP mode | Enable the pin's internal pull-up resistor | - Minimum broadcast (seconds) | Minimum time between alert broadcasts | - State broadcast (seconds) | Periodic state broadcast interval | - Send bell with alert message | Include bell character in alerts | - Friendly name | Custom name for this sensor | + Setting | תיאור | + ------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------- | + Detection Sensor enabled | Activate detection sensor | + GPIO pin to monitor | GPIO pin connected to sensor | + Detection trigger type | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) | + Use INPUT_PULLUP mode | Enable the pin's internal pull-up resistor | + Minimum time between detection broadcasts | Minimum time between alert broadcasts | + State Broadcast Interval | Periodic state broadcast interval | + Send bell with alert message | Include bell character in alerts | + Friendly name | Custom name for this sensor | ### Paxcounter module People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. - Setting | תיאור | - -------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | - Paxcounter enabled | Activate people counting | - Update interval (seconds) | How often to report counts | - Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) | - BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | + Setting | תיאור | + --------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | + Paxcounter enabled | Activate people counting | + Update Interval | How often to report counts | + WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) | + BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) | > 💡 **Tip:** Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. diff --git a/main/docs/iw-rIL/user/settings-radio-user.html b/main/docs/iw-rIL/user/settings-radio-user.html index 8f18b3bc65..c06d8861fc 100644 --- a/main/docs/iw-rIL/user/settings-radio-user.html +++ b/main/docs/iw-rIL/user/settings-radio-user.html @@ -71,24 +71,24 @@ On **Settings → Device configuration → Device**. On **Settings → LoRa**. - Setting | תיאור | Default | - ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- | - אזור | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) | - Presets | Speed/range tradeoff | LongFast | - Number of Hops | Maximum retransmit hops | 3 | - Transmit Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | - Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | - Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | - Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset | - Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | - Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset | - Frequency Slot | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) | - Transmit Enabled | Turning this off makes the node receive-only | On | - Override Duty Cycle | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | - Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | - Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | - RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | - PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | + Setting | תיאור | Default | + --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- | + אזור | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) | + Presets | Speed/range tradeoff | LongFast | + Number of Hops | Maximum retransmit hops | 3 | + Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) | + Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | + Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | + Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset | + Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | + Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset | + Frequency Slot | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) | + Transmit Enabled | Turning this off makes the node receive-only | On | + Override Duty Cycle | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | + Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | + Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | + RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | + PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn't appear in another. Changing region can therefore leave your current preset diff --git a/main/docs/ja-rJP/user/discovery.html b/main/docs/ja-rJP/user/discovery.html index 4acc28728f..a303b4400f 100644 --- a/main/docs/ja-rJP/user/discovery.html +++ b/main/docs/ja-rJP/user/discovery.html @@ -161,7 +161,7 @@ Each `⇊` line between two nodes is one relay hop, and the SNR on that line is 1. Navigate to **Settings → Module configuration → Neighbor Info**. 2. モジュールを有効にします。 -3. Set **Update interval (seconds)**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. +3. Set **Update Interval**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. 4. Turn on **Transmit over LoRa**. Without it, your neighbor list goes only to MQTT and to this app, never over the air. Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. 隣接ノード情報を有効にしている他のノードも、同じことを行います。 diff --git a/main/docs/ja-rJP/user/mqtt.html b/main/docs/ja-rJP/user/mqtt.html index a1dc916669..ae39a87f75 100644 --- a/main/docs/ja-rJP/user/mqtt.html +++ b/main/docs/ja-rJP/user/mqtt.html @@ -90,7 +90,7 @@ When this phone relays MQTT for the radio, connections to that broker always use When **Map reporting** is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. -Turning it on opens a consent card. Turn on **I agree.** and choose a **Map reporting interval (seconds)** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. +Turning it on opens a consent card. Turn on **I agree.** and choose a **Map Publish Interval** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at [meshmap.net](https://meshmap.net) and similar community map services. diff --git a/main/docs/ja-rJP/user/settings-module-admin.html b/main/docs/ja-rJP/user/settings-module-admin.html index 1b17f8ec89..8333c0fafa 100644 --- a/main/docs/ja-rJP/user/settings-module-admin.html +++ b/main/docs/ja-rJP/user/settings-module-admin.html @@ -51,11 +51,11 @@ Turning **Map reporting** on reveals a consent card headed _Consent to Share Une via MQTT_, with an **I agree.** switch under it. The rest of the card doesn't exist on screen until you agree: - 設定項目 | 説明 | - --------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | - 同意します。 | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it | - Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units | - マップレポートの間隔 (秒) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | + 設定項目 | 説明 | + -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | + 同意します。 | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it | + Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units | + Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | 暗号化、プライバシー、サーバーの設定を含む詳しい使い方は、[MQTT](mqtt) を参照してください。 @@ -91,8 +91,8 @@ and each can drive the LED, the buzzer and the vibration motor separately, givin バイブレーション出力 (GPIO) | Pin the vibration motor is wired to | PWMブザーを使用 | Drive the buzzer with PWM, which allows tones rather than a single pitch | I2Sをブザーとして使用 | Send the alert through an I2S audio output instead | - 出力時間 (ミリ秒) | How long a single alert lasts | - 繰り返し通知間隔（秒） | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | + GPIO Output Duration | How long a single alert lasts | + Nag Timeout | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | 着信音 | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | ### Store & Forward module @@ -122,7 +122,7 @@ and each can drive the LED, the buzzer and the vibration motor separately, givin 設定項目 | 説明 | -------------------------------------------- | ---------------------------------------------------------------------------------------- | レンジテストを有効化 | レンジテストを有効化 | - 送信者のメッセージ間隔 (秒) | Time between test transmissions, chosen from a dropdown of fixed intervals | + Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals | ストレージにCSVファイルを保存(ESP32のみ) | Log received test data to the node's own filesystem. ESP32 hardware only | ### Telemetry module @@ -195,11 +195,11 @@ Pre-configured messages accessible from the node's physical buttons (for nodes w 直接受信した隣接ノードの情報をブロードキャストし、メッシュのトポロジーマッピングを可能にします。有効にした各ノードは、受信できる他のノードとその信号品質のリストを定期的に共有します。 - 設定項目 | 説明 | - --------------------------- | ------------------------------------------------------------------------------ | - 近隣ノード情報を有効化 | 隣接ノードのブロードキャストを有効化 | - 更新間隔 (秒) | 隣接ノードのリストをブロードキャストする頻度 | - LoRaで送信 | MQTT／スマートフォンだけでなく、LoRa 経由でも隣接ノード情報をブロードキャストします。デフォルトの鍵と名前を使用しているチャンネルでは利用できません | + 設定項目 | 説明 | + ----------- | ------------------------------------------------------------------------------ | + 近隣ノード情報を有効化 | 隣接ノードのブロードキャストを有効化 | + GPS ポーリング間隔 | 隣接ノードのリストをブロードキャストする頻度 | + LoRaで送信 | MQTT／スマートフォンだけでなく、LoRa 経由でも隣接ノード情報をブロードキャストします。デフォルトの鍵と名前を使用しているチャンネルでは利用できません | See [Local Mesh Discovery](discovery) for how to use neighbor data for mesh topology exploration. @@ -217,27 +217,27 @@ See [Local Mesh Discovery](discovery) for how to use neighbor data for mesh topo ノードを、動きやドアを検知するセンサーアラートシステムに変えます。 GPIO ピンが状態の変化（動きの検知、ドアの開放）を検出すると、ノードはメッシュ経由でアラートメッセージをブロードキャストします。 - 設定項目 | 説明 | - ---------------------------------------- | ------------------------------------------- | - 検出センサーを有効化 | 検知センサーを有効化 | - モニターのGPIOピン | センサーに接続された GPIO ピン | - 検出トリガーの種類 | ピンの状態を検知イベントにどう対応させるか（例：アクティブハイ／ロー、エッジトリガー） | - INPUT_PULLUP モードを使用 | ピンの内蔵プルアップ抵抗を有効にする | - 最小ブロードキャスト間隔(秒) | アラートのブロードキャスト間の最小時間 | - 状態のブロードキャスト間隔 (秒) | 定期的な状態ブロードキャストの間隔 | - アラートメッセージ付きのベルを送信 | アラートにベル文字を含める | - 名前 | このセンサーのカスタム名 | + 設定項目 | 説明 | + ----------------------------------------- | ------------------------------------------- | + 検出センサーを有効化 | 検知センサーを有効化 | + モニターのGPIOピン | センサーに接続された GPIO ピン | + 検出トリガーの種類 | ピンの状態を検知イベントにどう対応させるか（例：アクティブハイ／ロー、エッジトリガー） | + INPUT_PULLUP モードを使用 | ピンの内蔵プルアップ抵抗を有効にする | + Minimum time between detection broadcasts | アラートのブロードキャスト間の最小時間 | + State Broadcast Interval | 定期的な状態ブロードキャストの間隔 | + アラートメッセージ付きのベルを送信 | アラートにベル文字を含める | + 名前 | このセンサーのカスタム名 | ### Paxcounter module People counter using Wi-Fi and BLE probe requests. スマートフォンやノートパソコンがネットワークを探すときに発するプローブ要求を受動的に受信して、近くのデバイスを数えます。 ESP32 デバイスでのみ利用できます。 - 設定 | 説明 | - --------------------------- | ---------------------------------------------------------------------------------------------------------------- | - Paxcounter を有効化 | 人数カウントを有効化 | - 更新間隔 (秒) | カウントを報告する頻度 | - Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) | - BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | + 設定 | 説明 | + --------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | + Paxcounter を有効化 | 人数カウントを有効化 | + GPS ポーリング間隔 | カウントを報告する頻度 | + WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) | + BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) | > 💡 **ヒント：** Paxcounter は、登山口やイベント会場などの人出を推定するのに便利です。カウントはおおよその値です。1 人が複数のデバイスを持っていることがあります。 diff --git a/main/docs/ja-rJP/user/settings-radio-user.html b/main/docs/ja-rJP/user/settings-radio-user.html index fc64164daa..cddcfef07f 100644 --- a/main/docs/ja-rJP/user/settings-radio-user.html +++ b/main/docs/ja-rJP/user/settings-radio-user.html @@ -71,24 +71,24 @@ On **Settings → Device configuration → Device**. On **Settings → LoRa**. - 設定項目 | 説明 | デフォルト | - ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- | - リージョン | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | 未設定（要設定） | - プリセット | 速度と距離のトレードオフ | LongFast | - ホップ数 | 再送信の最大ホップ数 | 3 | - 送信出力 | 送信出力（dBm）。0 = リージョンで許可された最大値 | 0（リージョン最大） | - 周波数の上書き | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | - プリセットを使用 | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | - 拡散率 | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset | - 符号化レート | Manual mode only: 5–8. More redundancy costs airtime | From preset | - 帯域 | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset | - 周波数スロット | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) | - 送信を有効化 | Turning this off makes the node receive-only | On | - デューティサイクルを上書き | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | オフ | - MQTT を無視 | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | - MQTT への送信を許可 | Allow your packets to be forwarded to MQTT by gateways | オフ | - RX ブーストゲイン | Extra receive gain on SX126x radios; costs a little current | オフ | - PAファン無効 | Turn off the power-amplifier fan on hardware that has one | オフ | + 設定項目 | 説明 | デフォルト | + --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- | + リージョン | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | 未設定（要設定） | + プリセット | 速度と距離のトレードオフ | LongFast | + ホップ数 | 再送信の最大ホップ数 | 3 | + Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0（リージョン最大） | + 周波数の上書き | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | + プリセットを使用 | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | + 拡散率 | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset | + 符号化レート | Manual mode only: 5–8. More redundancy costs airtime | From preset | + 帯域 | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset | + 周波数スロット | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) | + 送信を有効化 | Turning this off makes the node receive-only | On | + デューティサイクルを上書き | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | オフ | + MQTT を無視 | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | + MQTT への送信を許可 | Allow your packets to be forwarded to MQTT by gateways | オフ | + RX ブーストゲイン | Extra receive gain on SX126x radios; costs a little current | オフ | + PAファン無効 | Turn off the power-amplifier fan on hardware that has one | オフ | The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn't appear in another. Changing region can therefore leave your current preset diff --git a/main/docs/ko-rKR/user/discovery.html b/main/docs/ko-rKR/user/discovery.html index 9d12d70859..7100ff1937 100644 --- a/main/docs/ko-rKR/user/discovery.html +++ b/main/docs/ko-rKR/user/discovery.html @@ -161,7 +161,7 @@ The Neighbor Info module lets each node broadcast a list of the nodes it can **d 1. Navigate to **Settings → Module configuration → Neighbor Info**. 2. Enable the module. -3. Set **Update interval (seconds)**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. +3. Set **Update Interval**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. 4. Turn on **Transmit over LoRa**. Without it, your neighbor list goes only to MQTT and to this app, never over the air. Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. diff --git a/main/docs/ko-rKR/user/mqtt.html b/main/docs/ko-rKR/user/mqtt.html index a2f43f7945..8737d5f0b4 100644 --- a/main/docs/ko-rKR/user/mqtt.html +++ b/main/docs/ko-rKR/user/mqtt.html @@ -90,7 +90,7 @@ Configure your node to point to your private broker with appropriate credentials When **Map reporting** is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. -Turning it on opens a consent card. Turn on **I agree.** and choose a **Map reporting interval (seconds)** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. +Turning it on opens a consent card. Turn on **I agree.** and choose a **Map Publish Interval** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at [meshmap.net](https://meshmap.net) and similar community map services. diff --git a/main/docs/ko-rKR/user/settings-module-admin.html b/main/docs/ko-rKR/user/settings-module-admin.html index 068580ad51..2771208168 100644 --- a/main/docs/ko-rKR/user/settings-module-admin.html +++ b/main/docs/ko-rKR/user/settings-module-admin.html @@ -51,11 +51,11 @@ Turning **Map reporting** on reveals a consent card headed _Consent to Share Une via MQTT_, with an **I agree.** switch under it. The rest of the card doesn't exist on screen until you agree: - Setting | 설명 | - ------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | - 동의합니다. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it | - Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units | - 맵 보고 간격 (초) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | + Setting | 설명 | + ---------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | + 동의합니다. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it | + Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units | + Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | See [MQTT](mqtt) for a detailed usage guide including encryption, privacy, and broker setup. @@ -91,8 +91,8 @@ and each can drive the LED, the buzzer and the vibration motor separately, givin 진동 출력 (GPIO) | Pin the vibration motor is wired to | PWM 부저 사용 | Drive the buzzer with PWM, which allows tones rather than a single pitch | I2S 부저 사용 | Send the alert through an I2S audio output instead | - 출력 지속시간 (밀리초) | How long a single alert lasts | - 반복 종료 시간 (초) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | + GPIO Output Duration | How long a single alert lasts | + Nag Timeout | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | 벨소리 | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | ### Store & Forward module @@ -122,7 +122,7 @@ Automated range testing tool for evaluating link quality between nodes. When ena Setting | 설명 | --------------------------------------------------------- | ---------------------------------------------------------------------------------------- | 거리 테스트 활성화 | Activate range testing | - 송신 장치 메시지 간격 (초) | Time between test transmissions, chosen from a dropdown of fixed intervals | + Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals | .CSV 파일 저장 (EPS32만 동작) | Log received test data to the node's own filesystem. ESP32 hardware only | ### Telemetry module @@ -195,11 +195,11 @@ GPIO control over the mesh network. Allows a remote node to read or write GPIO p Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. - Setting | 설명 | - ------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------ | - 이웃 정보 활성화 | Activate neighbor broadcasting | - 업데이트 간격 (초) | How often to broadcast neighbor list | - LoRa로 전송 | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | + Setting | 설명 | + --------------- | ------------------------------------------------------------------------------------------------------------------------------------ | + 이웃 정보 활성화 | Activate neighbor broadcasting | + Update Interval | How often to broadcast neighbor list | + LoRa로 전송 | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | See [Local Mesh Discovery](discovery) for how to use neighbor data for mesh topology exploration. @@ -217,27 +217,27 @@ Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. C Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. - Setting | 설명 | - --------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | - 감지 센서 활성화 | Activate detection sensor | - 상태 모니터링 GPIO 핀 | GPIO pin connected to sensor | - 디텍션 트리거 타입 | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) | - INPUT_PULLUP 모드 사용 | Enable the pin's internal pull-up resistor | - 최소 전송 간격 (초) | Minimum time between alert broadcasts | - 상태 전송 간격 (초) | Periodic state broadcast interval | - 알람 메시지와 벨 전송 | Include bell character in alerts | - 식별 이름 | Custom name for this sensor | + Setting | 설명 | + ----------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | + 감지 센서 활성화 | Activate detection sensor | + 상태 모니터링 GPIO 핀 | GPIO pin connected to sensor | + 디텍션 트리거 타입 | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) | + INPUT_PULLUP 모드 사용 | Enable the pin's internal pull-up resistor | + Minimum time between detection broadcasts | Minimum time between alert broadcasts | + State Broadcast Interval | Periodic state broadcast interval | + 알람 메시지와 벨 전송 | Include bell character in alerts | + 식별 이름 | Custom name for this sensor | ### Paxcounter module People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. - Setting | 설명 | - ------------------------------ | ---------------------------------------------------------------------------------------------------------------- | - 팍스카운터 활성화 | Activate people counting | - 업데이트 간격 (초) | How often to report counts | - Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) | - BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | + Setting | 설명 | + --------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | + 팍스카운터 활성화 | Activate people counting | + Update Interval | How often to report counts | + WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) | + BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) | > 💡 **Tip:** Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. diff --git a/main/docs/ko-rKR/user/settings-radio-user.html b/main/docs/ko-rKR/user/settings-radio-user.html index a639bd798e..4042ca0237 100644 --- a/main/docs/ko-rKR/user/settings-radio-user.html +++ b/main/docs/ko-rKR/user/settings-radio-user.html @@ -71,24 +71,24 @@ On **Settings → Device configuration → Device**. On **Settings → LoRa**. - Setting | 설명 | 기본값 | - ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- | - 지역 | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) | - Presets | Speed/range tradeoff | LongFast | - Number of Hops | Maximum retransmit hops | 3 | - 전송 출력 | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | - Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | - 프리셋 사용 | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | - Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset | - Coding rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | - 대역폭 | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset | - 주파수 슬롯 | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) | - 전송 활성화 | Turning this off makes the node receive-only | On | - Duty Cycle 무시 | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | - MQTT로 부터 수신 무시 | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | - Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | - RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | - PA fan 비활성화됨 | Turn off the power-amplifier fan on hardware that has one | Off | + Setting | 설명 | 기본값 | + --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- | + 지역 | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) | + Presets | Speed/range tradeoff | LongFast | + Number of Hops | Maximum retransmit hops | 3 | + Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) | + Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | + 프리셋 사용 | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | + Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset | + Coding rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | + 대역폭 | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset | + 주파수 슬롯 | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) | + 전송 활성화 | Turning this off makes the node receive-only | On | + Duty Cycle 무시 | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | + MQTT로 부터 수신 무시 | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | + Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | + RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | + PA fan 비활성화됨 | Turn off the power-amplifier fan on hardware that has one | Off | The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn't appear in another. Changing region can therefore leave your current preset diff --git a/main/docs/lt-rLT/user/discovery.html b/main/docs/lt-rLT/user/discovery.html index a2766b045e..03cf134ffd 100644 --- a/main/docs/lt-rLT/user/discovery.html +++ b/main/docs/lt-rLT/user/discovery.html @@ -161,7 +161,7 @@ The Neighbor Info module lets each node broadcast a list of the nodes it can **d 1. Navigate to **Settings → Module configuration → Neighbor Info**. 2. Enable the module. -3. Set **Update interval (seconds)**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. +3. Set **Update Interval**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. 4. Turn on **Transmit over LoRa**. Without it, your neighbor list goes only to MQTT and to this app, never over the air. Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. diff --git a/main/docs/lt-rLT/user/mqtt.html b/main/docs/lt-rLT/user/mqtt.html index 1ea030d1d5..f9dd414b54 100644 --- a/main/docs/lt-rLT/user/mqtt.html +++ b/main/docs/lt-rLT/user/mqtt.html @@ -90,7 +90,7 @@ Configure your node to point to your private broker with appropriate credentials When **Map reporting** is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. -Turning it on opens a consent card. Turn on **I agree.** and choose a **Map reporting interval (seconds)** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. +Turning it on opens a consent card. Turn on **I agree.** and choose a **Map Publish Interval** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at [meshmap.net](https://meshmap.net) and similar community map services. diff --git a/main/docs/lt-rLT/user/settings-module-admin.html b/main/docs/lt-rLT/user/settings-module-admin.html index 87fe3b3668..e5b869a885 100644 --- a/main/docs/lt-rLT/user/settings-module-admin.html +++ b/main/docs/lt-rLT/user/settings-module-admin.html @@ -51,11 +51,11 @@ Turning **Map reporting** on reveals a consent card headed _Consent to Share Une via MQTT_, with an **I agree.** switch under it. The rest of the card doesn't exist on screen until you agree: - Setting | Aprašymas | - --------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | - I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it | - Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units | - Map reporting interval (seconds) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | + Setting | Aprašymas | + ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | + I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it | + Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units | + Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | See [MQTT](mqtt) for a detailed usage guide including encryption, privacy, and broker setup. @@ -80,20 +80,20 @@ Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devi There are two independent triggers — an incoming **message**, and a received **bell** character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. - Setting | Aprašymas | - ------------------------------------------------- | --------------------------------------------------------------------------------------------------- | - External notification enabled | Master toggle for the module | - Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | - Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | - Output LED (GPIO) | Pin the LED is wired to | - Output LED active high | Whether the LED pin is active high or low | - Output buzzer (GPIO) | Pin the buzzer is wired to | - Output vibra (GPIO) | Pin the vibration motor is wired to | - Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | - Use I2S as buzzer | Send the alert through an I2S audio output instead | - Output duration (milliseconds) | How long a single alert lasts | - Nag timeout (seconds) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | - Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | + Setting | Aprašymas | + --------------------------------------- | --------------------------------------------------------------------------------------------------- | + External notification enabled | Master toggle for the module | + Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | + Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | + Output LED (GPIO) | Pin the LED is wired to | + Output LED active high | Whether the LED pin is active high or low | + Output buzzer (GPIO) | Pin the buzzer is wired to | + Output vibra (GPIO) | Pin the vibration motor is wired to | + Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | + Use I2S as buzzer | Send the alert through an I2S audio output instead | + GPIO Output Duration | How long a single alert lasts | + Nag Timeout | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | + Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | ### Store & Forward module @@ -122,7 +122,7 @@ Automated range testing tool for evaluating link quality between nodes. When ena Setting | Aprašymas | -------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- | Range test enabled | Activate range testing | - Sender message interval (seconds) | Time between test transmissions, chosen from a dropdown of fixed intervals | + Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals | Save .CSV in storage (ESP32 only) | Log received test data to the node's own filesystem. ESP32 hardware only | ### Telemetry module @@ -195,11 +195,11 @@ GPIO control over the mesh network. Allows a remote node to read or write GPIO p Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. - Setting | Aprašymas | - -------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | - Neighbor Info enabled | Activate neighbor broadcasting | - Update interval (seconds) | How often to broadcast neighbor list | - Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | + Setting | Aprašymas | + --------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | + Neighbor Info enabled | Activate neighbor broadcasting | + Update Interval | How often to broadcast neighbor list | + Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | See [Local Mesh Discovery](discovery) for how to use neighbor data for mesh topology exploration. @@ -217,27 +217,27 @@ Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. C Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. - Setting | Aprašymas | - ---------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | - Detection Sensor enabled | Activate detection sensor | - GPIO pin to monitor | GPIO pin connected to sensor | - Detection trigger type | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) | - Use INPUT_PULLUP mode | Enable the pin's internal pull-up resistor | - Minimum broadcast (seconds) | Minimum time between alert broadcasts | - State broadcast (seconds) | Periodic state broadcast interval | - Send bell with alert message | Include bell character in alerts | - Friendly name | Custom name for this sensor | + Setting | Aprašymas | + ------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------- | + Detection Sensor enabled | Activate detection sensor | + GPIO pin to monitor | GPIO pin connected to sensor | + Detection trigger type | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) | + Use INPUT_PULLUP mode | Enable the pin's internal pull-up resistor | + Minimum time between detection broadcasts | Minimum time between alert broadcasts | + State Broadcast Interval | Periodic state broadcast interval | + Send bell with alert message | Include bell character in alerts | + Friendly name | Custom name for this sensor | ### Paxcounter module People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. - Setting | Aprašymas | - -------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | - Paxcounter enabled | Activate people counting | - Update interval (seconds) | How often to report counts | - Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) | - BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | + Setting | Aprašymas | + --------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | + Paxcounter enabled | Activate people counting | + Update Interval | How often to report counts | + WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) | + BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) | > 💡 **Tip:** Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. diff --git a/main/docs/lt-rLT/user/settings-radio-user.html b/main/docs/lt-rLT/user/settings-radio-user.html index 296810e450..defcbd3e9e 100644 --- a/main/docs/lt-rLT/user/settings-radio-user.html +++ b/main/docs/lt-rLT/user/settings-radio-user.html @@ -71,24 +71,24 @@ On **Settings → Device configuration → Device**. On **Settings → LoRa**. - Setting | Aprašymas | Default | - ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- | - Regionas | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) | - Presets | Speed/range tradeoff | LongFast | - Number of Hops | Maximum retransmit hops | 3 | - Transmit Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | - Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | - Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | - Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset | - Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | - Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset | - Frequency Slot | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) | - Transmit Enabled | Turning this off makes the node receive-only | On | - Override Duty Cycle | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | - Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | - Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | - RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | - PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | + Setting | Aprašymas | Default | + --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- | + Regionas | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) | + Presets | Speed/range tradeoff | LongFast | + Number of Hops | Maximum retransmit hops | 3 | + Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) | + Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | + Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | + Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset | + Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | + Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset | + Frequency Slot | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) | + Transmit Enabled | Turning this off makes the node receive-only | On | + Override Duty Cycle | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | + Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | + Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | + RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | + PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn't appear in another. Changing region can therefore leave your current preset diff --git a/main/docs/nl-rNL/user/discovery.html b/main/docs/nl-rNL/user/discovery.html index a8bb593cd9..6efd196905 100644 --- a/main/docs/nl-rNL/user/discovery.html +++ b/main/docs/nl-rNL/user/discovery.html @@ -161,7 +161,7 @@ The Neighbor Info module lets each node broadcast a list of the nodes it can **d 1. Navigate to **Settings → Module configuration → Neighbor Info**. 2. Enable the module. -3. Set **Update interval (seconds)**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. +3. Set **Update Interval**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. 4. Turn on **Transmit over LoRa**. Without it, your neighbor list goes only to MQTT and to this app, never over the air. Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. diff --git a/main/docs/nl-rNL/user/mqtt.html b/main/docs/nl-rNL/user/mqtt.html index ef50f682b9..ba8c673be5 100644 --- a/main/docs/nl-rNL/user/mqtt.html +++ b/main/docs/nl-rNL/user/mqtt.html @@ -90,7 +90,7 @@ Configure your node to point to your private broker with appropriate credentials When **Map reporting** is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. -Turning it on opens a consent card. Turn on **I agree.** and choose a **Map reporting interval (seconds)** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. +Turning it on opens a consent card. Turn on **I agree.** and choose a **Map Publish Interval** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at [meshmap.net](https://meshmap.net) and similar community map services. diff --git a/main/docs/nl-rNL/user/settings-module-admin.html b/main/docs/nl-rNL/user/settings-module-admin.html index a790c0381f..125937b894 100644 --- a/main/docs/nl-rNL/user/settings-module-admin.html +++ b/main/docs/nl-rNL/user/settings-module-admin.html @@ -51,11 +51,11 @@ Turning **Map reporting** on reveals a consent card headed _Consent to Share Une via MQTT_, with an **I agree.** switch under it. The rest of the card doesn't exist on screen until you agree: - Setting | Beschrijving | - --------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | - I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it | - Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units | - Map reporting interval (seconds) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | + Setting | Beschrijving | + ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | + I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it | + Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units | + Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | See [MQTT](mqtt) for a detailed usage guide including encryption, privacy, and broker setup. @@ -80,20 +80,20 @@ Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devi There are two independent triggers — an incoming **message**, and a received **bell** character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. - Setting | Beschrijving | - ---------------------------------------------- | --------------------------------------------------------------------------------------------------- | - External notification enabled | Master toggle for the module | - Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | - Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | - Output LED (GPIO) | Pin the LED is wired to | - Output LED active high | Whether the LED pin is active high or low | - Output buzzer (GPIO) | Pin the buzzer is wired to | - Output vibra (GPIO) | Pin the vibration motor is wired to | - Gebruik PWM zoemer | Drive the buzzer with PWM, which allows tones rather than a single pitch | - Use I2S as buzzer | Send the alert through an I2S audio output instead | - Output duur (milliseconden) | How long a single alert lasts | - Nag timeout (seconds) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | - Beltoon | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | + Setting | Beschrijving | + --------------------------------------- | --------------------------------------------------------------------------------------------------- | + External notification enabled | Master toggle for the module | + Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | + Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | + Output LED (GPIO) | Pin the LED is wired to | + Output LED active high | Whether the LED pin is active high or low | + Output buzzer (GPIO) | Pin the buzzer is wired to | + Output vibra (GPIO) | Pin the vibration motor is wired to | + Gebruik PWM zoemer | Drive the buzzer with PWM, which allows tones rather than a single pitch | + Use I2S as buzzer | Send the alert through an I2S audio output instead | + GPIO Output Duration | How long a single alert lasts | + Nag Timeout | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | + Beltoon | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | ### Store & Forward module @@ -122,7 +122,7 @@ Automated range testing tool for evaluating link quality between nodes. When ena Setting | Beschrijving | -------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- | Range test enabled | Activate range testing | - Sender message interval (seconds) | Time between test transmissions, chosen from a dropdown of fixed intervals | + Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals | Save .CSV in storage (ESP32 only) | Log received test data to the node's own filesystem. ESP32 hardware only | ### Telemetry module @@ -195,11 +195,11 @@ GPIO control over the mesh network. Allows a remote node to read or write GPIO p Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. - Setting | Beschrijving | - --------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | - Neighbor Info enabled | Activate neighbor broadcasting | - Update-interval (seconden) | How often to broadcast neighbor list | - Zend over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | + Setting | Beschrijving | + --------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | + Neighbor Info enabled | Activate neighbor broadcasting | + Update Interval | How often to broadcast neighbor list | + Zend over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | See [Local Mesh Discovery](discovery) for how to use neighbor data for mesh topology exploration. @@ -217,27 +217,27 @@ Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. C Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. - Setting | Beschrijving | - ------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------- | - Bewegingssensor Ingeschakeld | Activate detection sensor | - GPIO pin om te monitoren | GPIO pin connected to sensor | - Detectie trigger type | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) | - Use INPUT_PULLUP mode | Enable the pin's internal pull-up resistor | - Minimale broadcast (seconden) | Minimum time between alert broadcasts | - State broadcast (seconds) | Periodic state broadcast interval | - Send bell with alert message | Include bell character in alerts | - Weergavenaam | Custom name for this sensor | + Setting | Beschrijving | + ------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------- | + Bewegingssensor Ingeschakeld | Activate detection sensor | + GPIO pin om te monitoren | GPIO pin connected to sensor | + Detectie trigger type | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) | + Use INPUT_PULLUP mode | Enable the pin's internal pull-up resistor | + Minimum time between detection broadcasts | Minimum time between alert broadcasts | + State Broadcast Interval | Periodic state broadcast interval | + Send bell with alert message | Include bell character in alerts | + Weergavenaam | Custom name for this sensor | ### Paxcounter module People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. - Setting | Beschrijving | - --------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | - Paxcounter ingeschakeld | Activate people counting | - Update-interval (seconden) | How often to report counts | - Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) | - BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | + Setting | Beschrijving | + --------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | + Paxcounter ingeschakeld | Activate people counting | + Update Interval | How often to report counts | + WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) | + BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) | > 💡 **Tip:** Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. diff --git a/main/docs/nl-rNL/user/settings-radio-user.html b/main/docs/nl-rNL/user/settings-radio-user.html index cec273ea16..da3a9ee23f 100644 --- a/main/docs/nl-rNL/user/settings-radio-user.html +++ b/main/docs/nl-rNL/user/settings-radio-user.html @@ -71,24 +71,24 @@ On **Settings → Device configuration → Device**. On **Settings → LoRa**. - Setting | Beschrijving | Standaard | - ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- | - Regio | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) | - Presets | Speed/range tradeoff | LongFast | - Number of Hops | Maximum retransmit hops | 3 | - Transmit Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | - Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | - Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | - Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset | - Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | - Bandbreedte | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset | - Frequency Slot | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) | - Transmit Enabled | Turning this off makes the node receive-only | On | - Overschrijf Duty Cycle | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | - Negeer MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | - Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | - RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | - PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | + Setting | Beschrijving | Standaard | + --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- | + Regio | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) | + Presets | Speed/range tradeoff | LongFast | + Number of Hops | Maximum retransmit hops | 3 | + Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) | + Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | + Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | + Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset | + Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | + Bandbreedte | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset | + Frequency Slot | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) | + Transmit Enabled | Turning this off makes the node receive-only | On | + Overschrijf Duty Cycle | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | + Negeer MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | + Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | + RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | + PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn't appear in another. Changing region can therefore leave your current preset diff --git a/main/docs/no-rNO/user/discovery.html b/main/docs/no-rNO/user/discovery.html index 2f1abbf9d6..d7b6a8fce1 100644 --- a/main/docs/no-rNO/user/discovery.html +++ b/main/docs/no-rNO/user/discovery.html @@ -161,7 +161,7 @@ The Neighbor Info module lets each node broadcast a list of the nodes it can **d 1. Navigate to **Settings → Module configuration → Neighbor Info**. 2. Enable the module. -3. Set **Update interval (seconds)**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. +3. Set **Update Interval**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. 4. Turn on **Transmit over LoRa**. Without it, your neighbor list goes only to MQTT and to this app, never over the air. Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. diff --git a/main/docs/no-rNO/user/mqtt.html b/main/docs/no-rNO/user/mqtt.html index 22f704ea1a..1823cb303f 100644 --- a/main/docs/no-rNO/user/mqtt.html +++ b/main/docs/no-rNO/user/mqtt.html @@ -90,7 +90,7 @@ Configure your node to point to your private broker with appropriate credentials When **Map reporting** is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. -Turning it on opens a consent card. Turn on **I agree.** and choose a **Map reporting interval (seconds)** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. +Turning it on opens a consent card. Turn on **I agree.** and choose a **Map Publish Interval** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at [meshmap.net](https://meshmap.net) and similar community map services. diff --git a/main/docs/no-rNO/user/settings-module-admin.html b/main/docs/no-rNO/user/settings-module-admin.html index 10ddce81b1..48b88fe911 100644 --- a/main/docs/no-rNO/user/settings-module-admin.html +++ b/main/docs/no-rNO/user/settings-module-admin.html @@ -51,11 +51,11 @@ Turning **Map reporting** on reveals a consent card headed _Consent to Share Une via MQTT_, with an **I agree.** switch under it. The rest of the card doesn't exist on screen until you agree: - Setting | Beskrivelse | - --------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | - I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it | - Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units | - Map reporting interval (seconds) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | + Setting | Beskrivelse | + ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | + I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it | + Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units | + Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | See [MQTT](mqtt) for a detailed usage guide including encryption, privacy, and broker setup. @@ -80,20 +80,20 @@ Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devi There are two independent triggers — an incoming **message**, and a received **bell** character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. - Setting | Beskrivelse | - ------------------------------------------------- | --------------------------------------------------------------------------------------------------- | - External notification enabled | Master toggle for the module | - Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | - Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | - Output LED (GPIO) | Pin the LED is wired to | - Output LED active high | Whether the LED pin is active high or low | - Output buzzer (GPIO) | Pin the buzzer is wired to | - Output vibra (GPIO) | Pin the vibration motor is wired to | - Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | - Use I2S as buzzer | Send the alert through an I2S audio output instead | - Output duration (milliseconds) | How long a single alert lasts | - Nag timeout (seconds) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | - Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | + Setting | Beskrivelse | + --------------------------------------- | --------------------------------------------------------------------------------------------------- | + External notification enabled | Master toggle for the module | + Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | + Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | + Output LED (GPIO) | Pin the LED is wired to | + Output LED active high | Whether the LED pin is active high or low | + Output buzzer (GPIO) | Pin the buzzer is wired to | + Output vibra (GPIO) | Pin the vibration motor is wired to | + Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | + Use I2S as buzzer | Send the alert through an I2S audio output instead | + GPIO Output Duration | How long a single alert lasts | + Nag Timeout | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | + Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | ### Store & Forward module @@ -122,7 +122,7 @@ Automated range testing tool for evaluating link quality between nodes. When ena Setting | Beskrivelse | -------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- | Range test enabled | Activate range testing | - Sender message interval (seconds) | Time between test transmissions, chosen from a dropdown of fixed intervals | + Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals | Save .CSV in storage (ESP32 only) | Log received test data to the node's own filesystem. ESP32 hardware only | ### Telemetry module @@ -195,11 +195,11 @@ GPIO control over the mesh network. Allows a remote node to read or write GPIO p Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. - Setting | Beskrivelse | - -------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | - Neighbor Info enabled | Activate neighbor broadcasting | - Update interval (seconds) | How often to broadcast neighbor list | - Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | + Setting | Beskrivelse | + --------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | + Neighbor Info enabled | Activate neighbor broadcasting | + Update Interval | How often to broadcast neighbor list | + Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | See [Local Mesh Discovery](discovery) for how to use neighbor data for mesh topology exploration. @@ -217,27 +217,27 @@ Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. C Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. - Setting | Beskrivelse | - ---------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | - Detection Sensor enabled | Activate detection sensor | - GPIO pin to monitor | GPIO pin connected to sensor | - Detection trigger type | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) | - Use INPUT_PULLUP mode | Enable the pin's internal pull-up resistor | - Minimum broadcast (seconds) | Minimum time between alert broadcasts | - State broadcast (seconds) | Periodic state broadcast interval | - Send bell with alert message | Include bell character in alerts | - Friendly name | Custom name for this sensor | + Setting | Beskrivelse | + ------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------- | + Detection Sensor enabled | Activate detection sensor | + GPIO pin to monitor | GPIO pin connected to sensor | + Detection trigger type | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) | + Use INPUT_PULLUP mode | Enable the pin's internal pull-up resistor | + Minimum time between detection broadcasts | Minimum time between alert broadcasts | + State Broadcast Interval | Periodic state broadcast interval | + Send bell with alert message | Include bell character in alerts | + Friendly name | Custom name for this sensor | ### Paxcounter module People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. - Setting | Beskrivelse | - -------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | - Paxcounter enabled | Activate people counting | - Update interval (seconds) | How often to report counts | - Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) | - BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | + Setting | Beskrivelse | + --------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | + Paxcounter enabled | Activate people counting | + Update Interval | How often to report counts | + WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) | + BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) | > 💡 **Tip:** Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. diff --git a/main/docs/no-rNO/user/settings-radio-user.html b/main/docs/no-rNO/user/settings-radio-user.html index e4593d66dd..536b880e28 100644 --- a/main/docs/no-rNO/user/settings-radio-user.html +++ b/main/docs/no-rNO/user/settings-radio-user.html @@ -71,24 +71,24 @@ On **Settings → Device configuration → Device**. On **Settings → LoRa**. - Setting | Beskrivelse | Default | - ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- | - Region | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) | - Presets | Speed/range tradeoff | LongFast | - Number of Hops | Maximum retransmit hops | 3 | - Transmit Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | - Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | - Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | - Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset | - Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | - Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset | - Frequency Slot | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) | - Transmit Enabled | Turning this off makes the node receive-only | On | - Override Duty Cycle | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | - Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | - Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | - RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | - PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | + Setting | Beskrivelse | Default | + --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- | + Region | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) | + Presets | Speed/range tradeoff | LongFast | + Number of Hops | Maximum retransmit hops | 3 | + Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) | + Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | + Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | + Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset | + Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | + Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset | + Frequency Slot | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) | + Transmit Enabled | Turning this off makes the node receive-only | On | + Override Duty Cycle | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | + Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | + Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | + RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | + PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn't appear in another. Changing region can therefore leave your current preset diff --git a/main/docs/pl-rPL/user/discovery.html b/main/docs/pl-rPL/user/discovery.html index a6e29880ca..5eb52b5666 100644 --- a/main/docs/pl-rPL/user/discovery.html +++ b/main/docs/pl-rPL/user/discovery.html @@ -161,7 +161,7 @@ The Neighbor Info module lets each node broadcast a list of the nodes it can **d 1. Navigate to **Settings → Module configuration → Neighbor Info**. 2. Enable the module. -3. Set **Update interval (seconds)**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. +3. Set **Update Interval**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. 4. Turn on **Transmit over LoRa**. Without it, your neighbor list goes only to MQTT and to this app, never over the air. Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. diff --git a/main/docs/pl-rPL/user/mqtt.html b/main/docs/pl-rPL/user/mqtt.html index 10594e4e15..6cab28f2be 100644 --- a/main/docs/pl-rPL/user/mqtt.html +++ b/main/docs/pl-rPL/user/mqtt.html @@ -90,7 +90,7 @@ Configure your node to point to your private broker with appropriate credentials When **Map reporting** is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. -Turning it on opens a consent card. Turn on **I agree.** and choose a **Map reporting interval (seconds)** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. +Turning it on opens a consent card. Turn on **I agree.** and choose a **Map Publish Interval** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at [meshmap.net](https://meshmap.net) and similar community map services. diff --git a/main/docs/pl-rPL/user/settings-module-admin.html b/main/docs/pl-rPL/user/settings-module-admin.html index ee1030e3a7..eeaecdf762 100644 --- a/main/docs/pl-rPL/user/settings-module-admin.html +++ b/main/docs/pl-rPL/user/settings-module-admin.html @@ -51,11 +51,11 @@ Turning **Map reporting** on reveals a consent card headed _Consent to Share Une via MQTT_, with an **I agree.** switch under it. The rest of the card doesn't exist on screen until you agree: - Setting | Opis | - ------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | - Zgadzam się. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it | - Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units | - Interwał raportowania map (sekundy) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | + Setting | Opis | + ---------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | + Zgadzam się. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it | + Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units | + Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | See [MQTT](mqtt) for a detailed usage guide including encryption, privacy, and broker setup. @@ -91,8 +91,8 @@ and each can drive the LED, the buzzer and the vibration motor separately, givin Wyjście silnika wibracyjnego (GPIO) | Pin the vibration motor is wired to | Użyj buzzer PWM | Drive the buzzer with PWM, which allows tones rather than a single pitch | Użyj I2S jako buzzer | Send the alert through an I2S audio output instead | - Czas trwania (w milisekundach) | How long a single alert lasts | - Nag timeout (seconds) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | + GPIO Output Duration | How long a single alert lasts | + Nag Czas przerwy | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | Dzwonek | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | ### Store & Forward module @@ -122,7 +122,7 @@ Automated range testing tool for evaluating link quality between nodes. When ena Setting | Opis | -------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- | Range test enabled | Activate range testing | - Sender message interval (seconds) | Time between test transmissions, chosen from a dropdown of fixed intervals | + Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals | Save .CSV in storage (ESP32 only) | Log received test data to the node's own filesystem. ESP32 hardware only | ### Telemetry module @@ -195,11 +195,11 @@ GPIO control over the mesh network. Allows a remote node to read or write GPIO p Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. - Setting | Opis | - ----------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | - Włącz informacje o sąsiedzie | Activate neighbor broadcasting | - Częstotliwość aktualizacji (w sekundach) | How often to broadcast neighbor list | - Nadaj przez LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | + Setting | Opis | + ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | + Włącz informacje o sąsiedzie | Activate neighbor broadcasting | + Częstotliwość aktualizacji | How often to broadcast neighbor list | + Nadaj przez LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | See [Local Mesh Discovery](discovery) for how to use neighbor data for mesh topology exploration. @@ -217,27 +217,27 @@ Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. C Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. - Setting | Opis | - ------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------- | - Czujnik detekcji włączony | Activate detection sensor | - Pin GPIO do monitorowania | GPIO pin connected to sensor | - Detection trigger type | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) | - Użyj trybu INPUT_PULLUP | Enable the pin's internal pull-up resistor | - Minimalny czas transmisji (sekundy) | Minimum time between alert broadcasts | - State broadcast (seconds) | Periodic state broadcast interval | - Send bell with alert message | Include bell character in alerts | - Przyjazna nazwa | Custom name for this sensor | + Setting | Opis | + -------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | + Czujnik detekcji włączony | Activate detection sensor | + Pin GPIO do monitorowania | GPIO pin connected to sensor | + Detection trigger type | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) | + Użyj trybu INPUT_PULLUP | Enable the pin's internal pull-up resistor | + Minimum time between detection broadcasts | Minimum time between alert broadcasts | + State Broadcast Interval | Periodic state broadcast interval | + Send bell with alert message | Include bell character in alerts | + Przyjazna nazwa | Custom name for this sensor | ### Paxcounter module People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. - Setting | Opis | - ----------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | - Paxcounter enabled | Activate people counting | - Częstotliwość aktualizacji (w sekundach) | How often to report counts | - Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) | - BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | + Setting | Opis | + --------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | + Paxcounter enabled | Activate people counting | + Częstotliwość aktualizacji | How often to report counts | + WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) | + BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) | > 💡 **Tip:** Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. diff --git a/main/docs/pl-rPL/user/settings-radio-user.html b/main/docs/pl-rPL/user/settings-radio-user.html index 2409640a7a..678a1fc400 100644 --- a/main/docs/pl-rPL/user/settings-radio-user.html +++ b/main/docs/pl-rPL/user/settings-radio-user.html @@ -71,24 +71,24 @@ On **Settings → Device configuration → Device**. On **Settings → LoRa**. - Setting | Opis | Domyślny | - ------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- | - Region | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) | - Presety | Speed/range tradeoff | LongFast | - Number of Hops | Maximum retransmit hops | 3 | - Moc nadawania | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | - Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | - Użyj predefiniowanych ustawień | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | - Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset | - Szybkość kodowania | Manual mode only: 5–8. More redundancy costs airtime | From preset | - Pasmo | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset | - Slot częstotliwości | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) | - Transmisja włączona | Turning this off makes the node receive-only | On | - Nadpisz cykl pracy | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Wyłączony | - Zignoruj MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | - Ok dla MQTT | Allow your packets to be forwarded to MQTT by gateways | Wyłączony | - RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Wyłączony | - PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Wyłączony | + Setting | Opis | Domyślny | + --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- | + Region | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) | + Presety | Speed/range tradeoff | LongFast | + Number of Hops | Maximum retransmit hops | 3 | + Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) | + Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | + Użyj predefiniowanych ustawień | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | + Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset | + Szybkość kodowania | Manual mode only: 5–8. More redundancy costs airtime | From preset | + Pasmo | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset | + Slot częstotliwości | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) | + Transmisja włączona | Turning this off makes the node receive-only | On | + Nadpisz cykl pracy | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Wyłączony | + Zignoruj MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | + Ok dla MQTT | Allow your packets to be forwarded to MQTT by gateways | Wyłączony | + RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Wyłączony | + PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Wyłączony | The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn't appear in another. Changing region can therefore leave your current preset diff --git a/main/docs/pt-rBR/user/discovery.html b/main/docs/pt-rBR/user/discovery.html index 4a8e714d1a..fe8a8877a3 100644 --- a/main/docs/pt-rBR/user/discovery.html +++ b/main/docs/pt-rBR/user/discovery.html @@ -161,7 +161,7 @@ The Neighbor Info module lets each node broadcast a list of the nodes it can **d 1. Navigate to **Settings → Module configuration → Neighbor Info**. 2. Enable the module. -3. Set **Update interval (seconds)**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. +3. Set **Update Interval**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. 4. Turn on **Transmit over LoRa**. Without it, your neighbor list goes only to MQTT and to this app, never over the air. Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. diff --git a/main/docs/pt-rBR/user/mqtt.html b/main/docs/pt-rBR/user/mqtt.html index 6fa9b174ac..0114a87dba 100644 --- a/main/docs/pt-rBR/user/mqtt.html +++ b/main/docs/pt-rBR/user/mqtt.html @@ -90,7 +90,7 @@ Configure your node to point to your private broker with appropriate credentials When **Map reporting** is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. -Turning it on opens a consent card. Turn on **I agree.** and choose a **Map reporting interval (seconds)** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. +Turning it on opens a consent card. Turn on **I agree.** and choose a **Map Publish Interval** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at [meshmap.net](https://meshmap.net) and similar community map services. diff --git a/main/docs/pt-rBR/user/settings-module-admin.html b/main/docs/pt-rBR/user/settings-module-admin.html index c0c5ec29bf..f791d63fff 100644 --- a/main/docs/pt-rBR/user/settings-module-admin.html +++ b/main/docs/pt-rBR/user/settings-module-admin.html @@ -51,11 +51,11 @@ Turning **Map reporting** on reveals a consent card headed _Consent to Share Une via MQTT_, with an **I agree.** switch under it. The rest of the card doesn't exist on screen until you agree: - Setting | Descrição | - ------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | - Eu concordo. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it | - Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units | - Intervalo de relatório de mapa (segundos) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | + Setting | Descrição | + ---------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | + Eu concordo. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it | + Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units | + Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | See [MQTT](mqtt) for a detailed usage guide including encryption, privacy, and broker setup. @@ -80,20 +80,20 @@ Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devi There are two independent triggers — an incoming **message**, and a received **bell** character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. - Setting | Descrição | - --------------------------------------------------- | --------------------------------------------------------------------------------------------------- | - Notificação Externa habilitada | Master toggle for the module | - Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | - Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | - LED de Saída (GPIO) | Pin the LED is wired to | - LED de saída habilitado alto | Whether the LED pin is active high or low | - Saída Campainha (GPIO) | Pin the buzzer is wired to | - Vibra de saída (GPIO) | Pin the vibration motor is wired to | - Usar uma campainha PWM | Drive the buzzer with PWM, which allows tones rather than a single pitch | - Usar I2S como campainha | Send the alert through an I2S audio output instead | - Duração da Saída (milissegundos) | How long a single alert lasts | - Tempo limite do Nag (segundos) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | - Toque | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | + Setting | Descrição | + ----------------------------------------- | --------------------------------------------------------------------------------------------------- | + Notificação Externa habilitada | Master toggle for the module | + Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | + Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | + LED de Saída (GPIO) | Pin the LED is wired to | + LED de saída habilitado alto | Whether the LED pin is active high or low | + Saída Campainha (GPIO) | Pin the buzzer is wired to | + Vibra de saída (GPIO) | Pin the vibration motor is wired to | + Usar uma campainha PWM | Drive the buzzer with PWM, which allows tones rather than a single pitch | + Usar I2S como campainha | Send the alert through an I2S audio output instead | + GPIO Output Duration | How long a single alert lasts | + Nag Timeout | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | + Toque | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | ### Store & Forward module @@ -122,7 +122,7 @@ Automated range testing tool for evaluating link quality between nodes. When ena Setting | Descrição | ------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------- | Teste de distância ativado | Activate range testing | - Intervalo de mensagem do remetente (segundos) | Time between test transmissions, chosen from a dropdown of fixed intervals | + Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals | Salvar .CSV no armazenamento (apenas ESP32) | Log received test data to the node's own filesystem. ESP32 hardware only | ### Telemetry module @@ -195,11 +195,11 @@ GPIO control over the mesh network. Allows a remote node to read or write GPIO p Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. - Setting | Descrição | - ------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------ | - Informações do Vizinho ativado | Activate neighbor broadcasting | - Intervalo de atualização (segundos) | How often to broadcast neighbor list | - Transmitir por LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | + Setting | Descrição | + ------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------ | + Informações do Vizinho ativado | Activate neighbor broadcasting | + Update Interval | How often to broadcast neighbor list | + Transmitir por LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | See [Local Mesh Discovery](discovery) for how to use neighbor data for mesh topology exploration. @@ -217,27 +217,27 @@ Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. C Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. - Setting | Descrição | - --------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | - Sensor de Detecção ativado | Activate detection sensor | - Pino GPIO para monitorar | GPIO pin connected to sensor | - Tipo de gatilho de deteção | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) | - Usar o modo INPUT_PULLUP | Enable the pin's internal pull-up resistor | - Transmissão mínima (segundos) | Minimum time between alert broadcasts | - Transmissão de estado (segundos) | Periodic state broadcast interval | - Enviar sino com mensagem de alerta | Include bell character in alerts | - Nome amigável | Custom name for this sensor | + Setting | Descrição | + --------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | + Sensor de Detecção ativado | Activate detection sensor | + Pino GPIO para monitorar | GPIO pin connected to sensor | + Tipo de gatilho de deteção | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) | + Usar o modo INPUT_PULLUP | Enable the pin's internal pull-up resistor | + Minimum time between detection broadcasts | Minimum time between alert broadcasts | + State Broadcast Interval | Periodic state broadcast interval | + Enviar sino com mensagem de alerta | Include bell character in alerts | + Nome amigável | Custom name for this sensor | ### Paxcounter module People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. - Setting | Descrição | - ------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------- | - Contador de Pessoas ativado | Activate people counting | - Intervalo de atualização (segundos) | How often to report counts | - Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) | - BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | + Setting | Descrição | + --------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | + Contador de Pessoas ativado | Activate people counting | + Update Interval | How often to report counts | + WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) | + BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) | > 💡 **Tip:** Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. diff --git a/main/docs/pt-rBR/user/settings-radio-user.html b/main/docs/pt-rBR/user/settings-radio-user.html index 9b682229e2..80d075d016 100644 --- a/main/docs/pt-rBR/user/settings-radio-user.html +++ b/main/docs/pt-rBR/user/settings-radio-user.html @@ -71,24 +71,24 @@ On **Settings → Device configuration → Device**. On **Settings → LoRa**. - Setting | Descrição | Padrão | - --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- | - Região | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) | - Presets | Speed/range tradeoff | LongFast | - Number of Hops | Maximum retransmit hops | 3 | - Transmit Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | - Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | - Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | - Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset | - Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | - Largura da banda | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset | - Frequency Slot | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) | - Transmit Enabled | Turning this off makes the node receive-only | On | - Ignorar ciclo de trabalho | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | - Ignorar MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | - Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | - RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | - Ventilador do PA desativado | Turn off the power-amplifier fan on hardware that has one | Off | + Setting | Descrição | Padrão | + --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- | + Região | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) | + Presets | Speed/range tradeoff | LongFast | + Number of Hops | Maximum retransmit hops | 3 | + Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) | + Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | + Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | + Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset | + Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | + Largura da banda | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset | + Frequency Slot | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) | + Transmit Enabled | Turning this off makes the node receive-only | On | + Ignorar ciclo de trabalho | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | + Ignorar MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | + Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | + RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | + Ventilador do PA desativado | Turn off the power-amplifier fan on hardware that has one | Off | The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn't appear in another. Changing region can therefore leave your current preset diff --git a/main/docs/pt-rPT/user/discovery.html b/main/docs/pt-rPT/user/discovery.html index 45247ef62e..f54cf60342 100644 --- a/main/docs/pt-rPT/user/discovery.html +++ b/main/docs/pt-rPT/user/discovery.html @@ -161,7 +161,7 @@ The Neighbor Info module lets each node broadcast a list of the nodes it can **d 1. Navigate to **Settings → Module configuration → Neighbor Info**. 2. Enable the module. -3. Set **Update interval (seconds)**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. +3. Set **Update Interval**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. 4. Turn on **Transmit over LoRa**. Without it, your neighbor list goes only to MQTT and to this app, never over the air. Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. diff --git a/main/docs/pt-rPT/user/mqtt.html b/main/docs/pt-rPT/user/mqtt.html index 7c9c959857..5d37dd9ee1 100644 --- a/main/docs/pt-rPT/user/mqtt.html +++ b/main/docs/pt-rPT/user/mqtt.html @@ -90,7 +90,7 @@ Configure your node to point to your private broker with appropriate credentials When **Map reporting** is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. -Turning it on opens a consent card. Turn on **I agree.** and choose a **Map reporting interval (seconds)** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. +Turning it on opens a consent card. Turn on **I agree.** and choose a **Map Publish Interval** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at [meshmap.net](https://meshmap.net) and similar community map services. diff --git a/main/docs/pt-rPT/user/settings-module-admin.html b/main/docs/pt-rPT/user/settings-module-admin.html index 15b0c1a2b7..e717612b76 100644 --- a/main/docs/pt-rPT/user/settings-module-admin.html +++ b/main/docs/pt-rPT/user/settings-module-admin.html @@ -51,11 +51,11 @@ Turning **Map reporting** on reveals a consent card headed _Consent to Share Une via MQTT_, with an **I agree.** switch under it. The rest of the card doesn't exist on screen until you agree: - Setting | Descrição | - ------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | - Estou de acordo. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it | - Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units | - Intervalo de envio (segundos) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | + Setting | Descrição | + -------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | + Estou de acordo. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it | + Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units | + Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | See [MQTT](mqtt) for a detailed usage guide including encryption, privacy, and broker setup. @@ -80,20 +80,20 @@ Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devi There are two independent triggers — an incoming **message**, and a received **bell** character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. - Setting | Descrição | - ------------------------------------------------------ | --------------------------------------------------------------------------------------------------- | - Ativar notificações externas | Master toggle for the module | - Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | - Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | - LED de Saída (GPIO) | Pin the LED is wired to | - LED de saída ativo alto | Whether the LED pin is active high or low | - Buzzer de saída (GPIO) | Pin the buzzer is wired to | - Vibra de saída (GPIO) | Pin the vibration motor is wired to | - Usar um buzzer PWM | Drive the buzzer with PWM, which allows tones rather than a single pitch | - Usar I2S como buzzer | Send the alert through an I2S audio output instead | - Duração da Saída (milissegundos) | How long a single alert lasts | - Tempo limite a incomodar (segundos) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | - Toque | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | + Setting | Descrição | + ----------------------------------------- | --------------------------------------------------------------------------------------------------- | + Ativar notificações externas | Master toggle for the module | + Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | + Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | + LED de Saída (GPIO) | Pin the LED is wired to | + LED de saída ativo alto | Whether the LED pin is active high or low | + Buzzer de saída (GPIO) | Pin the buzzer is wired to | + Vibra de saída (GPIO) | Pin the vibration motor is wired to | + Usar um buzzer PWM | Drive the buzzer with PWM, which allows tones rather than a single pitch | + Usar I2S como buzzer | Send the alert through an I2S audio output instead | + GPIO Output Duration | How long a single alert lasts | + Nag Timeout | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | + Toque | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | ### Store & Forward module @@ -122,7 +122,7 @@ Automated range testing tool for evaluating link quality between nodes. When ena Setting | Descrição | ------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- | Ativar Teste de alcance | Activate range testing | - Sender message interval (seconds) | Time between test transmissions, chosen from a dropdown of fixed intervals | + Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals | Guardar .CSV no armazenamento (apenas ESP32) | Log received test data to the node's own filesystem. ESP32 hardware only | ### Telemetry module @@ -195,11 +195,11 @@ GPIO control over the mesh network. Allows a remote node to read or write GPIO p Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. - Setting | Descrição | - ------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------ | - Enviar informações de vizinhos | Activate neighbor broadcasting | - Intervalo de atualização (segundos) | How often to broadcast neighbor list | - Enviar por LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | + Setting | Descrição | + ------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------ | + Enviar informações de vizinhos | Activate neighbor broadcasting | + Intervalo de Atualização | How often to broadcast neighbor list | + Enviar por LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | See [Local Mesh Discovery](discovery) for how to use neighbor data for mesh topology exploration. @@ -217,27 +217,27 @@ Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. C Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. - Setting | Descrição | - --------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | - Sensor de deteção ativado | Activate detection sensor | - Pin GPIO para monitorizar | GPIO pin connected to sensor | - Tipo de gatilho de deteção | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) | - Usar o modo INPUT_PULLUP | Enable the pin's internal pull-up resistor | - Transmissão mínima (segundos) | Minimum time between alert broadcasts | - Transmissão de estado (segundos) | Periodic state broadcast interval | - Enviar sino com mensagem de alerta | Include bell character in alerts | - Nome amigável | Custom name for this sensor | + Setting | Descrição | + --------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | + Sensor de deteção ativado | Activate detection sensor | + Pin GPIO para monitorizar | GPIO pin connected to sensor | + Tipo de gatilho de deteção | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) | + Usar o modo INPUT_PULLUP | Enable the pin's internal pull-up resistor | + Minimum time between detection broadcasts | Minimum time between alert broadcasts | + State Broadcast Interval | Periodic state broadcast interval | + Enviar sino com mensagem de alerta | Include bell character in alerts | + Nome amigável | Custom name for this sensor | ### Paxcounter module People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. - Setting | Descrição | - ------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------- | - Ativar contador de pessoas | Activate people counting | - Intervalo de atualização (segundos) | How often to report counts | - Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) | - BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | + Setting | Descrição | + --------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | + Ativar contador de pessoas | Activate people counting | + Intervalo de Atualização | How often to report counts | + WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) | + BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) | > 💡 **Tip:** Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. diff --git a/main/docs/pt-rPT/user/settings-radio-user.html b/main/docs/pt-rPT/user/settings-radio-user.html index 6df04a1628..1c421f9f3e 100644 --- a/main/docs/pt-rPT/user/settings-radio-user.html +++ b/main/docs/pt-rPT/user/settings-radio-user.html @@ -71,24 +71,24 @@ On **Settings → Device configuration → Device**. On **Settings → LoRa**. - Setting | Descrição | Predefinição | - ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- | - Região | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) | - Presets | Speed/range tradeoff | LongFast | - Number of Hops | Maximum retransmit hops | 3 | - Transmit Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | - Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | - Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | - Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset | - Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | - Largura de banda | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset | - Frequency Slot | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) | - Transmit Enabled | Turning this off makes the node receive-only | On | - Ignorar ciclo de trabalho | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | - Ignorar MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | - Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | - RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | - PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | + Setting | Descrição | Predefinição | + --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- | + Região | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) | + Presets | Speed/range tradeoff | LongFast | + Number of Hops | Maximum retransmit hops | 3 | + Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) | + Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | + Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | + Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset | + Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | + Largura de banda | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset | + Frequency Slot | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) | + Transmit Enabled | Turning this off makes the node receive-only | On | + Ignorar ciclo de trabalho | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | + Ignorar MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | + Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | + RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | + PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn't appear in another. Changing region can therefore leave your current preset diff --git a/main/docs/ro-rRO/user/discovery.html b/main/docs/ro-rRO/user/discovery.html index df541f88e0..1035ad1022 100644 --- a/main/docs/ro-rRO/user/discovery.html +++ b/main/docs/ro-rRO/user/discovery.html @@ -161,7 +161,7 @@ The Neighbor Info module lets each node broadcast a list of the nodes it can **d 1. Navigate to **Settings → Module configuration → Neighbor Info**. 2. Enable the module. -3. Set **Update interval (seconds)**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. +3. Set **Update Interval**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. 4. Turn on **Transmit over LoRa**. Without it, your neighbor list goes only to MQTT and to this app, never over the air. Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. diff --git a/main/docs/ro-rRO/user/mqtt.html b/main/docs/ro-rRO/user/mqtt.html index cd658a7b4e..c90c2c109f 100644 --- a/main/docs/ro-rRO/user/mqtt.html +++ b/main/docs/ro-rRO/user/mqtt.html @@ -90,7 +90,7 @@ Configure your node to point to your private broker with appropriate credentials When **Map reporting** is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. -Turning it on opens a consent card. Turn on **I agree.** and choose a **Map reporting interval (seconds)** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. +Turning it on opens a consent card. Turn on **I agree.** and choose a **Map Publish Interval** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at [meshmap.net](https://meshmap.net) and similar community map services. diff --git a/main/docs/ro-rRO/user/settings-module-admin.html b/main/docs/ro-rRO/user/settings-module-admin.html index 50f09429db..0f8445b1a1 100644 --- a/main/docs/ro-rRO/user/settings-module-admin.html +++ b/main/docs/ro-rRO/user/settings-module-admin.html @@ -51,11 +51,11 @@ Turning **Map reporting** on reveals a consent card headed _Consent to Share Une via MQTT_, with an **I agree.** switch under it. The rest of the card doesn't exist on screen until you agree: - Setting | Descriere | - ---------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | - Sunt de acord | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it | - Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units | - Intervalul de raportare hartă (secunde) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | + Setting | Descriere | + -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | + Sunt de acord | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it | + Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units | + Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | See [MQTT](mqtt) for a detailed usage guide including encryption, privacy, and broker setup. @@ -80,20 +80,20 @@ Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devi There are two independent triggers — an incoming **message**, and a received **bell** character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. - Setting | Descriere | - ---------------------------------------------- | --------------------------------------------------------------------------------------------------- | - Notificare externă activată | Master toggle for the module | - Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | - Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | - LED ieșire (GPIO) | Pin the LED is wired to | - LED de ieșire activ ridicat | Whether the LED pin is active high or low | - Buzzer ieșire (GPIO) | Pin the buzzer is wired to | - Ieșire vibrație (GPIO) | Pin the vibration motor is wired to | - Utilizează buzzer PWM | Drive the buzzer with PWM, which allows tones rather than a single pitch | - Utilizează I2S ca buzzer | Send the alert through an I2S audio output instead | - Durată ieșire (milisecunde) | How long a single alert lasts | - Durată notificare (secunde) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | - Sonerie | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | + Setting | Descriere | + ----------------------------------------- | --------------------------------------------------------------------------------------------------- | + Notificare externă activată | Master toggle for the module | + Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | + Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | + LED ieșire (GPIO) | Pin the LED is wired to | + LED de ieșire activ ridicat | Whether the LED pin is active high or low | + Buzzer ieșire (GPIO) | Pin the buzzer is wired to | + Ieșire vibrație (GPIO) | Pin the vibration motor is wired to | + Utilizează buzzer PWM | Drive the buzzer with PWM, which allows tones rather than a single pitch | + Utilizează I2S ca buzzer | Send the alert through an I2S audio output instead | + GPIO Output Duration | How long a single alert lasts | + Nag Timeout | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | + Sonerie | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | ### Store & Forward module @@ -122,7 +122,7 @@ Automated range testing tool for evaluating link quality between nodes. When ena Setting | Descriere | ----------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- | Testul de gamă activat | Activate range testing | - Interval mesaj expeditor (secunde) | Time between test transmissions, chosen from a dropdown of fixed intervals | + Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals | Salvați .CSV doar în memorie (ESP32) | Log received test data to the node's own filesystem. ESP32 hardware only | ### Telemetry module @@ -195,11 +195,11 @@ GPIO control over the mesh network. Allows a remote node to read or write GPIO p Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. - Setting | Descriere | - ---------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | - Info vecin activat | Activate neighbor broadcasting | - Interval de actualizare (secunde) | How often to broadcast neighbor list | - Transmite peste LoRA | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | + Setting | Descriere | + --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | + Info vecin activat | Activate neighbor broadcasting | + Interval de actualizare GPS | How often to broadcast neighbor list | + Transmite peste LoRA | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | See [Local Mesh Discovery](discovery) for how to use neighbor data for mesh topology exploration. @@ -223,8 +223,8 @@ Turns your node into a motion or door sensor alert system. When a GPIO pin detec Pin GPIO de monitorizat | GPIO pin connected to sensor | Tip declanșator detectare | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) | Folosește modul INPUT_PULLUP | Enable the pin's internal pull-up resistor | - Difuzare minimă (secunde) | Minimum time between alert broadcasts | - Difuzare stare (secunde) | Periodic state broadcast interval | + Minimum time between detection broadcasts | Minimum time between alert broadcasts | + State Broadcast Interval | Periodic state broadcast interval | Trimite clopoțelul cu mesaj de alertă | Include bell character in alerts | Nume comun | Custom name for this sensor | @@ -232,12 +232,12 @@ Turns your node into a motion or door sensor alert system. When a GPIO pin detec People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. - Setting | Descriere | - ---------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | - Paxcounter activat | Activate people counting | - Interval de actualizare (secunde) | How often to report counts | - Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) | - BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | + Setting | Descriere | + --------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | + Paxcounter activat | Activate people counting | + Interval de actualizare GPS | How often to report counts | + WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) | + BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) | > 💡 **Tip:** Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. diff --git a/main/docs/ro-rRO/user/settings-radio-user.html b/main/docs/ro-rRO/user/settings-radio-user.html index 868b711aa8..336b183fb1 100644 --- a/main/docs/ro-rRO/user/settings-radio-user.html +++ b/main/docs/ro-rRO/user/settings-radio-user.html @@ -71,24 +71,24 @@ On **Settings → Device configuration → Device**. On **Settings → LoRa**. - Setting | Descriere | Prestabilit | - ------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- | - Regiune | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) | - Presetări | Speed/range tradeoff | LongFast | - Numărul de Hops | Maximum retransmit hops | 3 | - Putere transmisie | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | - Suprascriere frecvență | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | - Utilizare presetare | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | - Factor de răspândire | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset | - Rata de codificare | Manual mode only: 5–8. More redundancy costs airtime | From preset | - Lățime bandă | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset | - Slot pentru frecvenţă | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) | - Transmisie activată | Turning this off makes the node receive-only | On | - Suprascrie ciclul de obligații | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | - Ignoră MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | - Acceptă MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | - Amplificare RX amplificată | Extra receive gain on SX126x radios; costs a little current | Off | - Ventilator PA dezactivat | Turn off the power-amplifier fan on hardware that has one | Off | + Setting | Descriere | Prestabilit | + --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- | + Regiune | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) | + Presetări | Speed/range tradeoff | LongFast | + Numărul de Hops | Maximum retransmit hops | 3 | + Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) | + Suprascriere frecvență | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | + Utilizare presetare | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | + Factor de răspândire | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset | + Rata de codificare | Manual mode only: 5–8. More redundancy costs airtime | From preset | + Lățime bandă | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset | + Slot pentru frecvenţă | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) | + Transmisie activată | Turning this off makes the node receive-only | On | + Suprascrie ciclul de obligații | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | + Ignoră MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | + Acceptă MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | + Amplificare RX amplificată | Extra receive gain on SX126x radios; costs a little current | Off | + Ventilator PA dezactivat | Turn off the power-amplifier fan on hardware that has one | Off | The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn't appear in another. Changing region can therefore leave your current preset diff --git a/main/docs/ru-rRU/user/discovery.html b/main/docs/ru-rRU/user/discovery.html index 833dcbd5fe..efb02fc66f 100644 --- a/main/docs/ru-rRU/user/discovery.html +++ b/main/docs/ru-rRU/user/discovery.html @@ -161,7 +161,7 @@ Each `⇊` line between two nodes is one relay hop, and the SNR on that line is 1. Navigate to **Settings → Module configuration → Neighbor Info**. 2. Включение модуля -3. Set **Update interval (seconds)**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. +3. Set **Update Interval**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. 4. Turn on **Transmit over LoRa**. Without it, your neighbor list goes only to MQTT and to this app, never over the air. Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Другие ноды с включённым модулем информации о соседях делают то же самое. diff --git a/main/docs/ru-rRU/user/mqtt.html b/main/docs/ru-rRU/user/mqtt.html index 6b0dfdbed5..3b02b0c44d 100644 --- a/main/docs/ru-rRU/user/mqtt.html +++ b/main/docs/ru-rRU/user/mqtt.html @@ -90,7 +90,7 @@ When this phone relays MQTT for the radio, connections to that broker always use When **Map reporting** is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. -Turning it on opens a consent card. Turn on **I agree.** and choose a **Map reporting interval (seconds)** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. +Turning it on opens a consent card. Turn on **I agree.** and choose a **Map Publish Interval** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at [meshmap.net](https://meshmap.net) and similar community map services. diff --git a/main/docs/ru-rRU/user/settings-module-admin.html b/main/docs/ru-rRU/user/settings-module-admin.html index c5c5a8fa16..fdececc704 100644 --- a/main/docs/ru-rRU/user/settings-module-admin.html +++ b/main/docs/ru-rRU/user/settings-module-admin.html @@ -51,11 +51,11 @@ Turning **Map reporting** on reveals a consent card headed _Consent to Share Une via MQTT_, with an **I agree.** switch under it. The rest of the card doesn't exist on screen until you agree: - Настройка | Описание | - ----------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | - Я согласен. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it | - Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units | - Интервал отчета карты (в секундах) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | + Настройка | Описание | + --------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | + Я согласен. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it | + Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units | + Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | См. [MQTT](mqtt) для подробного руководства по использованию, включая шифрование, конфиденциальность и настройку брокера. @@ -80,20 +80,20 @@ Controls buzzer, LED, or vibration alerts on your node hardware. Полезно There are two independent triggers — an incoming **message**, and a received **bell** character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. - Настройка | Описание | - ---------------------------------------------------------- | --------------------------------------------------------------------------------------------------- | - Внешние уведомления включены | Master toggle for the module | - Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | - Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | - Выход LED (GPIO) | Pin the LED is wired to | - Вывод светодиода активный высокий | Whether the LED pin is active high or low | - Выход Буззера (GPIO) | Pin the buzzer is wired to | - Вибросигнал (GPIO) | Pin the vibration motor is wired to | - Использовать PWM-звукоизлучатель | Drive the buzzer with PWM, which allows tones rather than a single pitch | - Использовать I2S как буззер | Send the alert through an I2S audio output instead | - Продолжительность вывода (миллисекунды) | How long a single alert lasts | - Таймаут Nag (в секундах) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | - Рингтон | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | + Настройка | Описание | + --------------------------------------- | --------------------------------------------------------------------------------------------------- | + Внешние уведомления включены | Master toggle for the module | + Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | + Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | + Выход LED (GPIO) | Pin the LED is wired to | + Вывод светодиода активный высокий | Whether the LED pin is active high or low | + Выход Буззера (GPIO) | Pin the buzzer is wired to | + Вибросигнал (GPIO) | Pin the vibration motor is wired to | + Использовать PWM-звукоизлучатель | Drive the buzzer with PWM, which allows tones rather than a single pitch | + Использовать I2S как буззер | Send the alert through an I2S audio output instead | + GPIO Output Duration | How long a single alert lasts | + Интервал повтора | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | + Рингтон | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | ### Store & Forward module @@ -122,7 +122,7 @@ and each can drive the LED, the buzzer and the vibration motor separately, givin Настройка | Описание | ---------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- | Проверка дальности включена | Активировать проверку дальности | - Интервал сообщений отправителя (в секундах) | Time between test transmissions, chosen from a dropdown of fixed intervals | + Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals | Сохранить .CSV в хранилище (только ESP32) | Log received test data to the node's own filesystem. ESP32 hardware only | ### Telemetry module @@ -195,11 +195,11 @@ Pre-configured messages accessible from the node's physical buttons (for nodes w Транслирует информацию о доступных услышанных соседей, включив ячейку сеточной топологии. Каждый включенный узел периодически делится списком других узлов которые он может слышать и их качество сигнала. - Настройка | Описание | - --------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | - Информация о соседях включена | Включить трансляцию соседей | - Интервал обновления (в секундах) | Как часто транслировать список соседей | - Передать через LoRa | Также транслировать информацию соседей по LoRa, а не только MQTT/телефон. Недоступно на канале используя ключ по умолчанию и имя | + Настройка | Описание | + ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | + Информация о соседях включена | Включить трансляцию соседей | + Интервал опроса GPS | Как часто транслировать список соседей | + Передать через LoRa | Также транслировать информацию соседей по LoRa, а не только MQTT/телефон. Недоступно на канале используя ключ по умолчанию и имя | See [Local Mesh Discovery](discovery) for how to use neighbor data for mesh topology exploration. @@ -217,27 +217,27 @@ See [Local Mesh Discovery](discovery) for how to use neighbor data for mesh topo Превращает ваш узел в систему сигнализации на основе датчика движения или открытия двери. При обнаружении изменения состояния на выводе GPIO (например, сработал датчик движения или открылась дверь) узел отправляет по меш-сети оповещение. - Настройка | Описание | - ------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------- | - Датчик определения включен | Активировать датчик обнаружения | - GPIO контакт для мониторинга | Пин GPIO, подключенный к датчику | - Тип триггера обнаружения | Как состояние пина интерпретируется как событие обнаружения (например, активный высокий/низкий уровень, срабатывание по фронту) | - Использовать режим INPUT_PULLUP | Включить внутренний подтягивающий резистор пина | - Минимальная трансляция (в секундах) | Минимальный интервал между оповещениями | - Трансляция состояния (в секундах) | Интервал периодической отправки состояния | - Отправить колокол с уведомлением | Включать символ колокола в оповещения | - Понятное имя | Пользовательское имя для этого датчика | + Настройка | Описание | + ---------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- | + Датчик определения включен | Активировать датчик обнаружения | + GPIO контакт для мониторинга | Пин GPIO, подключенный к датчику | + Тип триггера обнаружения | Как состояние пина интерпретируется как событие обнаружения (например, активный высокий/низкий уровень, срабатывание по фронту) | + Использовать режим INPUT_PULLUP | Включить внутренний подтягивающий резистор пина | + Minimum time between detection broadcasts | Минимальный интервал между оповещениями | + State Broadcast Interval | Интервал периодической отправки состояния | + Отправить колокол с уведомлением | Включать символ колокола в оповещения | + Понятное имя | Пользовательское имя для этого датчика | ### Paxcounter module People counter using Wi-Fi and BLE probe requests. Засчитывает ближайшие устройства, пассивно прослушивая зондирующие запросы, чтобы телефоны и ноутбуки излучали при сканировании сетей. Доступно только на устройствах ESP32. - Настройка | Описание | - --------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | - Paxcounter включен | Активировать подсчет людей | - Интервал обновления (в секундах) | Как часто сообщать подсчитывания | - Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) | - BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | + Настройка | Описание | + --------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | + Paxcounter включен | Активировать подсчет людей | + Интервал опроса GPS | Как часто сообщать подсчитывания | + WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) | + BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) | > 💡 **Совет:** Paxcounter полезен для приблизительной оценки пешеходного потока в местах начала маршрутов, на мероприятийных площадках или в других локациях. Счетчики приблизительны — один человек может иметь несколько устройств. diff --git a/main/docs/ru-rRU/user/settings-radio-user.html b/main/docs/ru-rRU/user/settings-radio-user.html index 2fad5a1d4b..59f9e6c865 100644 --- a/main/docs/ru-rRU/user/settings-radio-user.html +++ b/main/docs/ru-rRU/user/settings-radio-user.html @@ -71,24 +71,24 @@ On **Settings → Device configuration → Device**. On **Settings → LoRa**. - Настройка | Описание | По умолчанию | - --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------- | - Регион / Страна | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Не установлено (необходимо настроить) | - Шаблоны | Компромисс между скоростью и дальностью | LongFast | - Количество прыжков | Максимальное количество ретрансляций | 3 | - Мощность передатчика | Мощность передачи (дБм); 0 = максимально разрешённая для региона | 0 (максимум региона) | - Переопределить частоту | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | - Использовать шаблон | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | - Коэффициент распространения | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset | - Частота кодирования | Manual mode only: 5–8. More redundancy costs airtime | From preset | - Ширина канала | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset | - Частота слота | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) | - Передача включена | Turning this off makes the node receive-only | On | - Переопределить рабочий цикл | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Выкл | - Игнорировать MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | - ОК в MQTT | Allow your packets to be forwarded to MQTT by gateways | Выкл | - Усиление RX | Extra receive gain on SX126x radios; costs a little current | Выкл | - PA вентилятор выключен | Turn off the power-amplifier fan on hardware that has one | Выкл | + Настройка | Описание | По умолчанию | + --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------- | + Регион / Страна | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Не установлено (необходимо настроить) | + Шаблоны | Компромисс между скоростью и дальностью | LongFast | + Количество прыжков | Максимальное количество ретрансляций | 3 | + Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (максимум региона) | + Переопределить частоту | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | + Использовать шаблон | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | + Коэффициент распространения | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset | + Частота кодирования | Manual mode only: 5–8. More redundancy costs airtime | From preset | + Ширина канала | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset | + Частота слота | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) | + Передача включена | Turning this off makes the node receive-only | On | + Переопределить рабочий цикл | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Выкл | + Игнорировать MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | + ОК в MQTT | Allow your packets to be forwarded to MQTT by gateways | Выкл | + Усиление RX | Extra receive gain on SX126x radios; costs a little current | Выкл | + PA вентилятор выключен | Turn off the power-amplifier fan on hardware that has one | Выкл | The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn't appear in another. Changing region can therefore leave your current preset diff --git a/main/docs/sk-rSK/user/discovery.html b/main/docs/sk-rSK/user/discovery.html index cfb675b345..e90cea6449 100644 --- a/main/docs/sk-rSK/user/discovery.html +++ b/main/docs/sk-rSK/user/discovery.html @@ -161,7 +161,7 @@ The Neighbor Info module lets each node broadcast a list of the nodes it can **d 1. Navigate to **Settings → Module configuration → Neighbor Info**. 2. Enable the module. -3. Set **Update interval (seconds)**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. +3. Set **Update Interval**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. 4. Turn on **Transmit over LoRa**. Without it, your neighbor list goes only to MQTT and to this app, never over the air. Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. diff --git a/main/docs/sk-rSK/user/mqtt.html b/main/docs/sk-rSK/user/mqtt.html index eee2664010..79bc0391e8 100644 --- a/main/docs/sk-rSK/user/mqtt.html +++ b/main/docs/sk-rSK/user/mqtt.html @@ -90,7 +90,7 @@ Configure your node to point to your private broker with appropriate credentials When **Map reporting** is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. -Turning it on opens a consent card. Turn on **I agree.** and choose a **Map reporting interval (seconds)** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. +Turning it on opens a consent card. Turn on **I agree.** and choose a **Map Publish Interval** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at [meshmap.net](https://meshmap.net) and similar community map services. diff --git a/main/docs/sk-rSK/user/settings-module-admin.html b/main/docs/sk-rSK/user/settings-module-admin.html index 2a62f2fec4..8d0e0d5b49 100644 --- a/main/docs/sk-rSK/user/settings-module-admin.html +++ b/main/docs/sk-rSK/user/settings-module-admin.html @@ -51,11 +51,11 @@ Turning **Map reporting** on reveals a consent card headed _Consent to Share Une via MQTT_, with an **I agree.** switch under it. The rest of the card doesn't exist on screen until you agree: - Setting | Popis | - --------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | - I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it | - Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units | - Map reporting interval (seconds) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | + Setting | Popis | + ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | + I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it | + Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units | + Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | See [MQTT](mqtt) for a detailed usage guide including encryption, privacy, and broker setup. @@ -80,20 +80,20 @@ Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devi There are two independent triggers — an incoming **message**, and a received **bell** character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. - Setting | Popis | - ------------------------------------------------- | --------------------------------------------------------------------------------------------------- | - External notification enabled | Master toggle for the module | - Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | - Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | - Output LED (GPIO) | Pin the LED is wired to | - Output LED active high | Whether the LED pin is active high or low | - Output buzzer (GPIO) | Pin the buzzer is wired to | - Output vibra (GPIO) | Pin the vibration motor is wired to | - Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | - Use I2S as buzzer | Send the alert through an I2S audio output instead | - Output duration (milliseconds) | How long a single alert lasts | - Nag timeout (seconds) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | - Zvonenie | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | + Setting | Popis | + --------------------------------------- | --------------------------------------------------------------------------------------------------- | + External notification enabled | Master toggle for the module | + Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | + Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | + Output LED (GPIO) | Pin the LED is wired to | + Output LED active high | Whether the LED pin is active high or low | + Output buzzer (GPIO) | Pin the buzzer is wired to | + Output vibra (GPIO) | Pin the vibration motor is wired to | + Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | + Use I2S as buzzer | Send the alert through an I2S audio output instead | + GPIO Output Duration | How long a single alert lasts | + Nag Timeout | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | + Zvonenie | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | ### Store & Forward module @@ -122,7 +122,7 @@ Automated range testing tool for evaluating link quality between nodes. When ena Setting | Popis | -------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- | Range test enabled | Activate range testing | - Sender message interval (seconds) | Time between test transmissions, chosen from a dropdown of fixed intervals | + Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals | Save .CSV in storage (ESP32 only) | Log received test data to the node's own filesystem. ESP32 hardware only | ### Telemetry module @@ -195,11 +195,11 @@ GPIO control over the mesh network. Allows a remote node to read or write GPIO p Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. - Setting | Popis | - -------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | - Neighbor Info enabled | Activate neighbor broadcasting | - Update interval (seconds) | How often to broadcast neighbor list | - Vysielať cez sieť LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | + Setting | Popis | + ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | + Neighbor Info enabled | Activate neighbor broadcasting | + Aktualizačný interval | How often to broadcast neighbor list | + Vysielať cez sieť LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | See [Local Mesh Discovery](discovery) for how to use neighbor data for mesh topology exploration. @@ -217,27 +217,27 @@ Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. C Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. - Setting | Popis | - ---------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | - Detection Sensor enabled | Activate detection sensor | - GPIO pin to monitor | GPIO pin connected to sensor | - Detection trigger type | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) | - Use INPUT_PULLUP mode | Enable the pin's internal pull-up resistor | - Minimum broadcast (seconds) | Minimum time between alert broadcasts | - State broadcast (seconds) | Periodic state broadcast interval | - Send bell with alert message | Include bell character in alerts | - Friendly name | Custom name for this sensor | + Setting | Popis | + ------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------- | + Detection Sensor enabled | Activate detection sensor | + GPIO pin to monitor | GPIO pin connected to sensor | + Detection trigger type | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) | + Use INPUT_PULLUP mode | Enable the pin's internal pull-up resistor | + Minimum time between detection broadcasts | Minimum time between alert broadcasts | + State Broadcast Interval | Periodic state broadcast interval | + Send bell with alert message | Include bell character in alerts | + Friendly name | Custom name for this sensor | ### Paxcounter module People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. - Setting | Popis | - -------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | - Paxcounter enabled | Activate people counting | - Update interval (seconds) | How often to report counts | - Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) | - BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | + Setting | Popis | + --------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | + Paxcounter enabled | Activate people counting | + Aktualizačný interval | How often to report counts | + WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) | + BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) | > 💡 **Tip:** Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. diff --git a/main/docs/sk-rSK/user/settings-radio-user.html b/main/docs/sk-rSK/user/settings-radio-user.html index 3a27163dcc..864d9970d0 100644 --- a/main/docs/sk-rSK/user/settings-radio-user.html +++ b/main/docs/sk-rSK/user/settings-radio-user.html @@ -71,24 +71,24 @@ On **Settings → Device configuration → Device**. On **Settings → LoRa**. - Setting | Popis | Predvolené | - ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- | - Región | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) | - Presets | Speed/range tradeoff | LongFast | - Number of Hops | Maximum retransmit hops | 3 | - Transmit Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | - Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | - Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | - Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset | - Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | - Šírka pásma | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset | - Frequency Slot | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) | - Transmit Enabled | Turning this off makes the node receive-only | On | - Override Duty Cycle | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | - Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | - Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | - RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | - PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | + Setting | Popis | Predvolené | + --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- | + Región | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) | + Presets | Speed/range tradeoff | LongFast | + Number of Hops | Maximum retransmit hops | 3 | + Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) | + Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | + Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | + Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset | + Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | + Šírka pásma | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset | + Frequency Slot | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) | + Transmit Enabled | Turning this off makes the node receive-only | On | + Override Duty Cycle | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | + Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | + Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | + RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | + PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn't appear in another. Changing region can therefore leave your current preset diff --git a/main/docs/sl-rSI/user/discovery.html b/main/docs/sl-rSI/user/discovery.html index d15849b1eb..da3bbd5259 100644 --- a/main/docs/sl-rSI/user/discovery.html +++ b/main/docs/sl-rSI/user/discovery.html @@ -161,7 +161,7 @@ The Neighbor Info module lets each node broadcast a list of the nodes it can **d 1. Navigate to **Settings → Module configuration → Neighbor Info**. 2. Enable the module. -3. Set **Update interval (seconds)**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. +3. Set **Update Interval**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. 4. Turn on **Transmit over LoRa**. Without it, your neighbor list goes only to MQTT and to this app, never over the air. Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. diff --git a/main/docs/sl-rSI/user/mqtt.html b/main/docs/sl-rSI/user/mqtt.html index aadabf17d2..327c6e2ea9 100644 --- a/main/docs/sl-rSI/user/mqtt.html +++ b/main/docs/sl-rSI/user/mqtt.html @@ -90,7 +90,7 @@ Configure your node to point to your private broker with appropriate credentials When **Map reporting** is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. -Turning it on opens a consent card. Turn on **I agree.** and choose a **Map reporting interval (seconds)** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. +Turning it on opens a consent card. Turn on **I agree.** and choose a **Map Publish Interval** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at [meshmap.net](https://meshmap.net) and similar community map services. diff --git a/main/docs/sl-rSI/user/settings-module-admin.html b/main/docs/sl-rSI/user/settings-module-admin.html index 1b44486851..b01e1b7bfb 100644 --- a/main/docs/sl-rSI/user/settings-module-admin.html +++ b/main/docs/sl-rSI/user/settings-module-admin.html @@ -51,11 +51,11 @@ Turning **Map reporting** on reveals a consent card headed _Consent to Share Une via MQTT_, with an **I agree.** switch under it. The rest of the card doesn't exist on screen until you agree: - Setting | Opis | - --------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | - I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it | - Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units | - Map reporting interval (seconds) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | + Setting | Opis | + ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | + I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it | + Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units | + Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | See [MQTT](mqtt) for a detailed usage guide including encryption, privacy, and broker setup. @@ -80,20 +80,20 @@ Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devi There are two independent triggers — an incoming **message**, and a received **bell** character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. - Setting | Opis | - ------------------------------------------------- | --------------------------------------------------------------------------------------------------- | - External notification enabled | Master toggle for the module | - Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | - Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | - Output LED (GPIO) | Pin the LED is wired to | - Output LED active high | Whether the LED pin is active high or low | - Output buzzer (GPIO) | Pin the buzzer is wired to | - Output vibra (GPIO) | Pin the vibration motor is wired to | - Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | - Use I2S as buzzer | Send the alert through an I2S audio output instead | - Output duration (milliseconds) | How long a single alert lasts | - Nag timeout (seconds) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | - Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | + Setting | Opis | + --------------------------------------- | --------------------------------------------------------------------------------------------------- | + External notification enabled | Master toggle for the module | + Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | + Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | + Output LED (GPIO) | Pin the LED is wired to | + Output LED active high | Whether the LED pin is active high or low | + Output buzzer (GPIO) | Pin the buzzer is wired to | + Output vibra (GPIO) | Pin the vibration motor is wired to | + Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | + Use I2S as buzzer | Send the alert through an I2S audio output instead | + GPIO Output Duration | How long a single alert lasts | + Nag Timeout | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | + Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | ### Store & Forward module @@ -122,7 +122,7 @@ Automated range testing tool for evaluating link quality between nodes. When ena Setting | Opis | -------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- | Range test enabled | Activate range testing | - Sender message interval (seconds) | Time between test transmissions, chosen from a dropdown of fixed intervals | + Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals | Save .CSV in storage (ESP32 only) | Log received test data to the node's own filesystem. ESP32 hardware only | ### Telemetry module @@ -195,11 +195,11 @@ GPIO control over the mesh network. Allows a remote node to read or write GPIO p Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. - Setting | Opis | - -------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | - Neighbor Info enabled | Activate neighbor broadcasting | - Update interval (seconds) | How often to broadcast neighbor list | - Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | + Setting | Opis | + --------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | + Neighbor Info enabled | Activate neighbor broadcasting | + Update Interval | How often to broadcast neighbor list | + Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | See [Local Mesh Discovery](discovery) for how to use neighbor data for mesh topology exploration. @@ -217,27 +217,27 @@ Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. C Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. - Setting | Opis | - ---------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | - Detection Sensor enabled | Activate detection sensor | - GPIO pin to monitor | GPIO pin connected to sensor | - Detection trigger type | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) | - Use INPUT_PULLUP mode | Enable the pin's internal pull-up resistor | - Minimum broadcast (seconds) | Minimum time between alert broadcasts | - State broadcast (seconds) | Periodic state broadcast interval | - Send bell with alert message | Include bell character in alerts | - Friendly name | Custom name for this sensor | + Setting | Opis | + ------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------- | + Detection Sensor enabled | Activate detection sensor | + GPIO pin to monitor | GPIO pin connected to sensor | + Detection trigger type | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) | + Use INPUT_PULLUP mode | Enable the pin's internal pull-up resistor | + Minimum time between detection broadcasts | Minimum time between alert broadcasts | + State Broadcast Interval | Periodic state broadcast interval | + Send bell with alert message | Include bell character in alerts | + Friendly name | Custom name for this sensor | ### Paxcounter module People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. - Setting | Opis | - -------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | - Paxcounter enabled | Activate people counting | - Update interval (seconds) | How often to report counts | - Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) | - BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | + Setting | Opis | + --------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | + Paxcounter enabled | Activate people counting | + Update Interval | How often to report counts | + WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) | + BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) | > 💡 **Tip:** Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. diff --git a/main/docs/sl-rSI/user/settings-radio-user.html b/main/docs/sl-rSI/user/settings-radio-user.html index 0441015770..d315db34aa 100644 --- a/main/docs/sl-rSI/user/settings-radio-user.html +++ b/main/docs/sl-rSI/user/settings-radio-user.html @@ -71,24 +71,24 @@ On **Settings → Device configuration → Device**. On **Settings → LoRa**. - Setting | Opis | Default | - ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- | - Regija | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) | - Presets | Speed/range tradeoff | LongFast | - Number of Hops | Maximum retransmit hops | 3 | - Transmit Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | - Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | - Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | - Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset | - Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | - Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset | - Frequency Slot | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) | - Transmit Enabled | Turning this off makes the node receive-only | On | - Override Duty Cycle | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | - Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | - Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | - RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | - PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | + Setting | Opis | Default | + --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- | + Regija | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) | + Presets | Speed/range tradeoff | LongFast | + Number of Hops | Maximum retransmit hops | 3 | + Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) | + Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | + Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | + Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset | + Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | + Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset | + Frequency Slot | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) | + Transmit Enabled | Turning this off makes the node receive-only | On | + Override Duty Cycle | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | + Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | + Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | + RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | + PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn't appear in another. Changing region can therefore leave your current preset diff --git a/main/docs/sq-rAL/user/discovery.html b/main/docs/sq-rAL/user/discovery.html index 18fa52759f..3a86140167 100644 --- a/main/docs/sq-rAL/user/discovery.html +++ b/main/docs/sq-rAL/user/discovery.html @@ -161,7 +161,7 @@ The Neighbor Info module lets each node broadcast a list of the nodes it can **d 1. Navigate to **Settings → Module configuration → Neighbor Info**. 2. Enable the module. -3. Set **Update interval (seconds)**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. +3. Set **Update Interval**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. 4. Turn on **Transmit over LoRa**. Without it, your neighbor list goes only to MQTT and to this app, never over the air. Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. diff --git a/main/docs/sq-rAL/user/mqtt.html b/main/docs/sq-rAL/user/mqtt.html index 752d033a81..54317e932f 100644 --- a/main/docs/sq-rAL/user/mqtt.html +++ b/main/docs/sq-rAL/user/mqtt.html @@ -90,7 +90,7 @@ Configure your node to point to your private broker with appropriate credentials When **Map reporting** is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. -Turning it on opens a consent card. Turn on **I agree.** and choose a **Map reporting interval (seconds)** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. +Turning it on opens a consent card. Turn on **I agree.** and choose a **Map Publish Interval** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at [meshmap.net](https://meshmap.net) and similar community map services. diff --git a/main/docs/sq-rAL/user/settings-module-admin.html b/main/docs/sq-rAL/user/settings-module-admin.html index c924d5a882..e5075caf55 100644 --- a/main/docs/sq-rAL/user/settings-module-admin.html +++ b/main/docs/sq-rAL/user/settings-module-admin.html @@ -51,11 +51,11 @@ Turning **Map reporting** on reveals a consent card headed _Consent to Share Une via MQTT_, with an **I agree.** switch under it. The rest of the card doesn't exist on screen until you agree: - Setting | Përshkrimi | - --------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | - I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it | - Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units | - Map reporting interval (seconds) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | + Setting | Përshkrimi | + ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | + I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it | + Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units | + Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | See [MQTT](mqtt) for a detailed usage guide including encryption, privacy, and broker setup. @@ -80,20 +80,20 @@ Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devi There are two independent triggers — an incoming **message**, and a received **bell** character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. - Setting | Përshkrimi | - ------------------------------------------------- | --------------------------------------------------------------------------------------------------- | - External notification enabled | Master toggle for the module | - Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | - Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | - Output LED (GPIO) | Pin the LED is wired to | - Output LED active high | Whether the LED pin is active high or low | - Output buzzer (GPIO) | Pin the buzzer is wired to | - Output vibra (GPIO) | Pin the vibration motor is wired to | - Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | - Use I2S as buzzer | Send the alert through an I2S audio output instead | - Output duration (milliseconds) | How long a single alert lasts | - Nag timeout (seconds) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | - Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | + Setting | Përshkrimi | + --------------------------------------- | --------------------------------------------------------------------------------------------------- | + External notification enabled | Master toggle for the module | + Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | + Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | + Output LED (GPIO) | Pin the LED is wired to | + Output LED active high | Whether the LED pin is active high or low | + Output buzzer (GPIO) | Pin the buzzer is wired to | + Output vibra (GPIO) | Pin the vibration motor is wired to | + Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | + Use I2S as buzzer | Send the alert through an I2S audio output instead | + GPIO Output Duration | How long a single alert lasts | + Nag Timeout | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | + Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | ### Store & Forward module @@ -122,7 +122,7 @@ Automated range testing tool for evaluating link quality between nodes. When ena Setting | Përshkrimi | -------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- | Range test enabled | Activate range testing | - Sender message interval (seconds) | Time between test transmissions, chosen from a dropdown of fixed intervals | + Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals | Save .CSV in storage (ESP32 only) | Log received test data to the node's own filesystem. ESP32 hardware only | ### Telemetry module @@ -195,11 +195,11 @@ GPIO control over the mesh network. Allows a remote node to read or write GPIO p Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. - Setting | Përshkrimi | - -------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | - Neighbor Info enabled | Activate neighbor broadcasting | - Update interval (seconds) | How often to broadcast neighbor list | - Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | + Setting | Përshkrimi | + --------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | + Neighbor Info enabled | Activate neighbor broadcasting | + Update Interval | How often to broadcast neighbor list | + Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | See [Local Mesh Discovery](discovery) for how to use neighbor data for mesh topology exploration. @@ -217,27 +217,27 @@ Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. C Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. - Setting | Përshkrimi | - ---------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | - Detection Sensor enabled | Activate detection sensor | - GPIO pin to monitor | GPIO pin connected to sensor | - Detection trigger type | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) | - Use INPUT_PULLUP mode | Enable the pin's internal pull-up resistor | - Minimum broadcast (seconds) | Minimum time between alert broadcasts | - State broadcast (seconds) | Periodic state broadcast interval | - Send bell with alert message | Include bell character in alerts | - Friendly name | Custom name for this sensor | + Setting | Përshkrimi | + ------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------- | + Detection Sensor enabled | Activate detection sensor | + GPIO pin to monitor | GPIO pin connected to sensor | + Detection trigger type | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) | + Use INPUT_PULLUP mode | Enable the pin's internal pull-up resistor | + Minimum time between detection broadcasts | Minimum time between alert broadcasts | + State Broadcast Interval | Periodic state broadcast interval | + Send bell with alert message | Include bell character in alerts | + Friendly name | Custom name for this sensor | ### Paxcounter module People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. - Setting | Përshkrimi | - -------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | - Paxcounter enabled | Activate people counting | - Update interval (seconds) | How often to report counts | - Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) | - BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | + Setting | Përshkrimi | + --------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | + Paxcounter enabled | Activate people counting | + Update Interval | How often to report counts | + WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) | + BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) | > 💡 **Tip:** Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. diff --git a/main/docs/sq-rAL/user/settings-radio-user.html b/main/docs/sq-rAL/user/settings-radio-user.html index 1f565e1217..8ad98016e4 100644 --- a/main/docs/sq-rAL/user/settings-radio-user.html +++ b/main/docs/sq-rAL/user/settings-radio-user.html @@ -71,24 +71,24 @@ On **Settings → Device configuration → Device**. On **Settings → LoRa**. - Setting | Përshkrimi | Default | - ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- | - Rajon | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) | - Presets | Speed/range tradeoff | LongFast | - Number of Hops | Maximum retransmit hops | 3 | - Transmit Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | - Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | - Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | - Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset | - Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | - Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset | - Frequency Slot | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) | - Transmit Enabled | Turning this off makes the node receive-only | On | - Override Duty Cycle | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | - Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | - Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | - RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | - PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | + Setting | Përshkrimi | Default | + --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- | + Rajon | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) | + Presets | Speed/range tradeoff | LongFast | + Number of Hops | Maximum retransmit hops | 3 | + Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) | + Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | + Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | + Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset | + Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | + Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset | + Frequency Slot | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) | + Transmit Enabled | Turning this off makes the node receive-only | On | + Override Duty Cycle | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | + Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | + Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | + RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | + PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn't appear in another. Changing region can therefore leave your current preset diff --git a/main/docs/srp/user/discovery.html b/main/docs/srp/user/discovery.html index 11c372ee86..b906745e86 100644 --- a/main/docs/srp/user/discovery.html +++ b/main/docs/srp/user/discovery.html @@ -161,7 +161,7 @@ The Neighbor Info module lets each node broadcast a list of the nodes it can **d 1. Navigate to **Settings → Module configuration → Neighbor Info**. 2. Enable the module. -3. Set **Update interval (seconds)**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. +3. Set **Update Interval**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. 4. Turn on **Transmit over LoRa**. Without it, your neighbor list goes only to MQTT and to this app, never over the air. Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. diff --git a/main/docs/srp/user/mqtt.html b/main/docs/srp/user/mqtt.html index 1ef031f1e6..d1d7071990 100644 --- a/main/docs/srp/user/mqtt.html +++ b/main/docs/srp/user/mqtt.html @@ -90,7 +90,7 @@ Configure your node to point to your private broker with appropriate credentials When **Map reporting** is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. -Turning it on opens a consent card. Turn on **I agree.** and choose a **Map reporting interval (seconds)** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. +Turning it on opens a consent card. Turn on **I agree.** and choose a **Map Publish Interval** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at [meshmap.net](https://meshmap.net) and similar community map services. diff --git a/main/docs/srp/user/settings-module-admin.html b/main/docs/srp/user/settings-module-admin.html index a26c0a796a..7edfc82736 100644 --- a/main/docs/srp/user/settings-module-admin.html +++ b/main/docs/srp/user/settings-module-admin.html @@ -51,11 +51,11 @@ Turning **Map reporting** on reveals a consent card headed _Consent to Share Une via MQTT_, with an **I agree.** switch under it. The rest of the card doesn't exist on screen until you agree: - Setting | Опис | - --------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | - I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it | - Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units | - Map reporting interval (seconds) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | + Setting | Опис | + ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | + I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it | + Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units | + Интервал објављивања мапе | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | See [MQTT](mqtt) for a detailed usage guide including encryption, privacy, and broker setup. @@ -80,20 +80,20 @@ Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devi There are two independent triggers — an incoming **message**, and a received **bell** character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. - Setting | Опис | - ------------------------------------------------- | --------------------------------------------------------------------------------------------------- | - External notification enabled | Master toggle for the module | - Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | - Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | - Output LED (GPIO) | Pin the LED is wired to | - Output LED active high | Whether the LED pin is active high or low | - Output buzzer (GPIO) | Pin the buzzer is wired to | - Output vibra (GPIO) | Pin the vibration motor is wired to | - Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | - Use I2S as buzzer | Send the alert through an I2S audio output instead | - Output duration (milliseconds) | How long a single alert lasts | - Nag timeout (seconds) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | - Мелодија звона | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | + Setting | Опис | + --------------------------------------- | --------------------------------------------------------------------------------------------------- | + External notification enabled | Master toggle for the module | + Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | + Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | + Output LED (GPIO) | Pin the LED is wired to | + Output LED active high | Whether the LED pin is active high or low | + Output buzzer (GPIO) | Pin the buzzer is wired to | + Output vibra (GPIO) | Pin the vibration motor is wired to | + Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | + Use I2S as buzzer | Send the alert through an I2S audio output instead | + Трајање GPIO излаза | How long a single alert lasts | + Nag Timeout | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | + Мелодија звона | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | ### Store & Forward module @@ -122,7 +122,7 @@ Automated range testing tool for evaluating link quality between nodes. When ena Setting | Опис | -------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- | Range test enabled | Activate range testing | - Sender message interval (seconds) | Time between test transmissions, chosen from a dropdown of fixed intervals | + Инерварл пошиљаоца | Time between test transmissions, chosen from a dropdown of fixed intervals | Save .CSV in storage (ESP32 only) | Log received test data to the node's own filesystem. ESP32 hardware only | ### Telemetry module @@ -195,11 +195,11 @@ GPIO control over the mesh network. Allows a remote node to read or write GPIO p Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. - Setting | Опис | - -------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | - Neighbor Info enabled | Activate neighbor broadcasting | - Update interval (seconds) | How often to broadcast neighbor list | - Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | + Setting | Опис | + --------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | + Neighbor Info enabled | Activate neighbor broadcasting | + Интервал ажурирања | How often to broadcast neighbor list | + Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | See [Local Mesh Discovery](discovery) for how to use neighbor data for mesh topology exploration. @@ -217,27 +217,27 @@ Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. C Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. - Setting | Опис | - ---------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | - Detection Sensor enabled | Activate detection sensor | - GPIO pin to monitor | GPIO pin connected to sensor | - Detection trigger type | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) | - Use INPUT_PULLUP mode | Enable the pin's internal pull-up resistor | - Minimum broadcast (seconds) | Minimum time between alert broadcasts | - State broadcast (seconds) | Periodic state broadcast interval | - Send bell with alert message | Include bell character in alerts | - Пријатељски назив | Custom name for this sensor | + Setting | Опис | + ------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------- | + Detection Sensor enabled | Activate detection sensor | + GPIO pin to monitor | GPIO pin connected to sensor | + Detection trigger type | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) | + Use INPUT_PULLUP mode | Enable the pin's internal pull-up resistor | + Минимално време између емитовања детекције | Minimum time between alert broadcasts | + Интервал емитовања стања | Periodic state broadcast interval | + Send bell with alert message | Include bell character in alerts | + Пријатељски назив | Custom name for this sensor | ### Paxcounter module People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. - Setting | Опис | - -------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | - Paxcounter enabled | Activate people counting | - Update interval (seconds) | How often to report counts | - Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) | - BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | + Setting | Опис | + --------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | + Paxcounter enabled | Activate people counting | + Интервал ажурирања | How often to report counts | + WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) | + BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) | > 💡 **Tip:** Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. diff --git a/main/docs/srp/user/settings-radio-user.html b/main/docs/srp/user/settings-radio-user.html index 8b5a4a3df7..aef5e13116 100644 --- a/main/docs/srp/user/settings-radio-user.html +++ b/main/docs/srp/user/settings-radio-user.html @@ -71,24 +71,24 @@ On **Settings → Device configuration → Device**. On **Settings → LoRa**. - Setting | Опис | Подразумевано | - -------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- | - Регион | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) | - Унапред подешено | Speed/range tradeoff | LongFast | - Number of Hops | Maximum retransmit hops | 3 | - Transmit Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | - Измена фреквенције | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | - Користи предефинисано подешавање | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | - Фактор ширења | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset | - Стопа кодирања | Manual mode only: 5–8. More redundancy costs airtime | From preset | - Проток | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset | - Фреквенцијски слот | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) | - Трансмитер укључен | Turning this off makes the node receive-only | On | - Override Duty Cycle | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Искључен | - Игнориши MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | - Позитиван за MQTT | Allow your packets to be forwarded to MQTT by gateways | Искључен | - Појачање пријемника | Extra receive gain on SX126x radios; costs a little current | Искључен | - PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Искључен | + Setting | Опис | Подразумевано | + --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- | + Регион | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) | + Унапред подешено | Speed/range tradeoff | LongFast | + Number of Hops | Maximum retransmit hops | 3 | + Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) | + Измена фреквенције | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | + Користи предефинисано подешавање | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | + Фактор ширења | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset | + Стопа кодирања | Manual mode only: 5–8. More redundancy costs airtime | From preset | + Проток | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset | + Фреквенцијски слот | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) | + Трансмитер укључен | Turning this off makes the node receive-only | On | + Override Duty Cycle | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Искључен | + Игнориши MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | + Позитиван за MQTT | Allow your packets to be forwarded to MQTT by gateways | Искључен | + Појачање пријемника | Extra receive gain on SX126x radios; costs a little current | Искључен | + PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Искључен | The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn't appear in another. Changing region can therefore leave your current preset diff --git a/main/docs/sv-rSE/user/discovery.html b/main/docs/sv-rSE/user/discovery.html index 351c825f62..8831eb77ed 100644 --- a/main/docs/sv-rSE/user/discovery.html +++ b/main/docs/sv-rSE/user/discovery.html @@ -161,7 +161,7 @@ The Neighbor Info module lets each node broadcast a list of the nodes it can **d 1. Navigate to **Settings → Module configuration → Neighbor Info**. 2. Enable the module. -3. Set **Update interval (seconds)**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. +3. Set **Update Interval**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. 4. Turn on **Transmit over LoRa**. Without it, your neighbor list goes only to MQTT and to this app, never over the air. Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. diff --git a/main/docs/sv-rSE/user/mqtt.html b/main/docs/sv-rSE/user/mqtt.html index 3d8c220ebf..019d860293 100644 --- a/main/docs/sv-rSE/user/mqtt.html +++ b/main/docs/sv-rSE/user/mqtt.html @@ -90,7 +90,7 @@ Configure your node to point to your private broker with appropriate credentials When **Map reporting** is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. -Turning it on opens a consent card. Turn on **I agree.** and choose a **Map reporting interval (seconds)** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. +Turning it on opens a consent card. Turn on **I agree.** and choose a **Map Publish Interval** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at [meshmap.net](https://meshmap.net) and similar community map services. diff --git a/main/docs/sv-rSE/user/settings-module-admin.html b/main/docs/sv-rSE/user/settings-module-admin.html index 897fb21d55..251528e3c9 100644 --- a/main/docs/sv-rSE/user/settings-module-admin.html +++ b/main/docs/sv-rSE/user/settings-module-admin.html @@ -51,11 +51,11 @@ Turning **Map reporting** on reveals a consent card headed _Consent to Share Une via MQTT_, with an **I agree.** switch under it. The rest of the card doesn't exist on screen until you agree: - Setting | Beskrivning | - --------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | - Jag godkänner. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it | - Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units | - Map reporting interval (seconds) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | + Setting | Beskrivning | + ------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | + Jag godkänner. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it | + Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units | + Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | See [MQTT](mqtt) for a detailed usage guide including encryption, privacy, and broker setup. @@ -80,20 +80,20 @@ Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devi There are two independent triggers — an incoming **message**, and a received **bell** character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. - Setting | Beskrivning | - ------------------------------------------------ | --------------------------------------------------------------------------------------------------- | - Externa aviseringar aktiverad | Master toggle for the module | - Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | - Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | - Utmatning LED (GPIO) | Pin the LED is wired to | - Utmatnings-LED aktiv hög | Whether the LED pin is active high or low | - Utmatning summer (GPIO) | Pin the buzzer is wired to | - Utmatning vibration (GPIO) | Pin the vibration motor is wired to | - Använd PWM-summern | Drive the buzzer with PWM, which allows tones rather than a single pitch | - Använd I2S som summer | Send the alert through an I2S audio output instead | - Utmatningstid (millisekunder) | How long a single alert lasts | - Sluta tjata efter (sekunder) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | - Ringsignal | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | + Setting | Beskrivning | + --------------------------------------------- | --------------------------------------------------------------------------------------------------- | + Externa aviseringar aktiverad | Master toggle for the module | + Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | + Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | + Utmatning LED (GPIO) | Pin the LED is wired to | + Utmatnings-LED aktiv hög | Whether the LED pin is active high or low | + Utmatning summer (GPIO) | Pin the buzzer is wired to | + Utmatning vibration (GPIO) | Pin the vibration motor is wired to | + Använd PWM-summern | Drive the buzzer with PWM, which allows tones rather than a single pitch | + Använd I2S som summer | Send the alert through an I2S audio output instead | + GPIO Output Duration | How long a single alert lasts | + Time-out för påminnelse | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | + Ringsignal | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | ### Store & Forward module @@ -122,7 +122,7 @@ Automated range testing tool for evaluating link quality between nodes. When ena Setting | Beskrivning | ---------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- | Räckvidstest aktiverat | Activate range testing | - Avsändarens meddelandeintervall (sekunder) | Time between test transmissions, chosen from a dropdown of fixed intervals | + Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals | Spara .CSV i enheten (endast ESP32) | Log received test data to the node's own filesystem. ESP32 hardware only | ### Telemetry module @@ -195,11 +195,11 @@ GPIO control over the mesh network. Allows a remote node to read or write GPIO p Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. - Setting | Beskrivning | - --------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | - Grannskapsinformation aktiverat | Activate neighbor broadcasting | - Uppdateringsintervall (sekunder) | How often to broadcast neighbor list | - Skicka över LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | + Setting | Beskrivning | + -------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | + Grannskapsinformation aktiverat | Activate neighbor broadcasting | + Intervall för hämtning av GPS-position | How often to broadcast neighbor list | + Skicka över LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | See [Local Mesh Discovery](discovery) for how to use neighbor data for mesh topology exploration. @@ -217,27 +217,27 @@ Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. C Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. - Setting | Beskrivning | - ------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | - Detektionssensor aktiverad | Activate detection sensor | - GPIO-pin att övervaka | GPIO pin connected to sensor | - Detection trigger type | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) | - Använd INPUT_PULLUP-läge | Enable the pin's internal pull-up resistor | - Minsta sändningsintervall (sekunder) | Minimum time between alert broadcasts | - Statussändningsintervall (sekunder) | Periodic state broadcast interval | - Skicka ljudavisering med larmmeddelande | Include bell character in alerts | - Visningsnamn | Custom name for this sensor | + Setting | Beskrivning | + --------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | + Detektionssensor aktiverad | Activate detection sensor | + GPIO-pin att övervaka | GPIO pin connected to sensor | + Detection trigger type | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) | + Använd INPUT_PULLUP-läge | Enable the pin's internal pull-up resistor | + Minimum time between detection broadcasts | Minimum time between alert broadcasts | + State Broadcast Interval | Periodic state broadcast interval | + Skicka ljudavisering med larmmeddelande | Include bell character in alerts | + Visningsnamn | Custom name for this sensor | ### Paxcounter module People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. - Setting | Beskrivning | - --------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | - PAX-räknare aktiverad | Activate people counting | - Uppdateringsintervall (sekunder) | How often to report counts | - Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) | - BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | + Setting | Beskrivning | + --------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | + PAX-räknare aktiverad | Activate people counting | + Intervall för hämtning av GPS-position | How often to report counts | + WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) | + BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) | > 💡 **Tip:** Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. diff --git a/main/docs/sv-rSE/user/settings-radio-user.html b/main/docs/sv-rSE/user/settings-radio-user.html index 544f9079cc..f6150c3038 100644 --- a/main/docs/sv-rSE/user/settings-radio-user.html +++ b/main/docs/sv-rSE/user/settings-radio-user.html @@ -71,24 +71,24 @@ On **Settings → Device configuration → Device**. On **Settings → LoRa**. - Setting | Beskrivning | Förvald | - ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- | - Region | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) | - Förval | Speed/range tradeoff | LongFast | - Antal hopp | Maximum retransmit hops | 3 | - Sändningseffekt | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | - Åsidosätt | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | - Använd förinställning | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | - Spridningsfaktor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset | - Kodningshastighet | Manual mode only: 5–8. More redundancy costs airtime | From preset | - Bandbredd | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset | - Frekvens-slot | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) | - Sändning aktiverad | Turning this off makes the node receive-only | On | - Ersätt gräns för driftsperiod | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Av | - Ignorera MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | - Ok till MQTT | Allow your packets to be forwarded to MQTT by gateways | Av | - RX förstärkt gain | Extra receive gain on SX126x radios; costs a little current | Av | - PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Av | + Setting | Beskrivning | Förvald | + --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- | + Region | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) | + Förval | Speed/range tradeoff | LongFast | + Antal hopp | Maximum retransmit hops | 3 | + Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) | + Åsidosätt | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | + Använd förinställning | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | + Spridningsfaktor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset | + Kodningshastighet | Manual mode only: 5–8. More redundancy costs airtime | From preset | + Bandbredd | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset | + Frekvens-slot | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) | + Sändning aktiverad | Turning this off makes the node receive-only | On | + Ersätt gräns för driftsperiod | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Av | + Ignorera MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | + Ok till MQTT | Allow your packets to be forwarded to MQTT by gateways | Av | + RX förstärkt gain | Extra receive gain on SX126x radios; costs a little current | Av | + PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Av | The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn't appear in another. Changing region can therefore leave your current preset diff --git a/main/docs/tr-rTR/user/discovery.html b/main/docs/tr-rTR/user/discovery.html index 629f8fc2cb..aa6a7d2733 100644 --- a/main/docs/tr-rTR/user/discovery.html +++ b/main/docs/tr-rTR/user/discovery.html @@ -161,7 +161,7 @@ The Neighbor Info module lets each node broadcast a list of the nodes it can **d 1. Navigate to **Settings → Module configuration → Neighbor Info**. 2. Enable the module. -3. Set **Update interval (seconds)**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. +3. Set **Update Interval**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. 4. Turn on **Transmit over LoRa**. Without it, your neighbor list goes only to MQTT and to this app, never over the air. Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. diff --git a/main/docs/tr-rTR/user/mqtt.html b/main/docs/tr-rTR/user/mqtt.html index 6375c2a4e6..a4beec6251 100644 --- a/main/docs/tr-rTR/user/mqtt.html +++ b/main/docs/tr-rTR/user/mqtt.html @@ -90,7 +90,7 @@ Configure your node to point to your private broker with appropriate credentials When **Map reporting** is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. -Turning it on opens a consent card. Turn on **I agree.** and choose a **Map reporting interval (seconds)** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. +Turning it on opens a consent card. Turn on **I agree.** and choose a **Map Publish Interval** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at [meshmap.net](https://meshmap.net) and similar community map services. diff --git a/main/docs/tr-rTR/user/settings-module-admin.html b/main/docs/tr-rTR/user/settings-module-admin.html index a3a954fca4..4355b2b55f 100644 --- a/main/docs/tr-rTR/user/settings-module-admin.html +++ b/main/docs/tr-rTR/user/settings-module-admin.html @@ -51,11 +51,11 @@ Turning **Map reporting** on reveals a consent card headed _Consent to Share Une via MQTT_, with an **I agree.** switch under it. The rest of the card doesn't exist on screen until you agree: - Setting | Açıklaması | - ---------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | - Katılıyorum. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it | - Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units | - Harita raporlama aralığı (saniye) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | + Setting | Açıklaması | + ---------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | + Katılıyorum. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it | + Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units | + Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | See [MQTT](mqtt) for a detailed usage guide including encryption, privacy, and broker setup. @@ -80,20 +80,20 @@ Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devi There are two independent triggers — an incoming **message**, and a received **bell** character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. - Setting | Açıklaması | - -------------------------------------------- | --------------------------------------------------------------------------------------------------- | - Harici bildirim etkin | Master toggle for the module | - Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | - Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | - Çıktı LED (GPIO) | Pin the LED is wired to | - Çıktı LED aktif yüksek | Whether the LED pin is active high or low | - Çıktı zırnı (GPIO) | Pin the buzzer is wired to | - Çıktı titreşim (GPIO) | Pin the vibration motor is wired to | - PWM zırnı kullan | Drive the buzzer with PWM, which allows tones rather than a single pitch | - I2S'yi zırnı olarak kullan | Send the alert through an I2S audio output instead | - Çıktı süresi (milisaniye) | How long a single alert lasts | - Nag zaman aşımı (saniye) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | - Zil tipi | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | + Setting | Açıklaması | + ---------------------------------------- | --------------------------------------------------------------------------------------------------- | + Harici bildirim etkin | Master toggle for the module | + Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | + Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | + Çıktı LED (GPIO) | Pin the LED is wired to | + Çıktı LED aktif yüksek | Whether the LED pin is active high or low | + Çıktı zırnı (GPIO) | Pin the buzzer is wired to | + Çıktı titreşim (GPIO) | Pin the vibration motor is wired to | + PWM zırnı kullan | Drive the buzzer with PWM, which allows tones rather than a single pitch | + I2S'yi zırnı olarak kullan | Send the alert through an I2S audio output instead | + GPIO Output Duration | How long a single alert lasts | + Nag Timeout | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | + Zil tipi | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | ### Store & Forward module @@ -122,7 +122,7 @@ Automated range testing tool for evaluating link quality between nodes. When ena Setting | Açıklaması | --------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- | Menzi testi etkin | Activate range testing | - Gönderen mesaj aralığı (saniye) | Time between test transmissions, chosen from a dropdown of fixed intervals | + Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals | .CSV'yi depolamada kaydet (sadece ESP32) | Log received test data to the node's own filesystem. ESP32 hardware only | ### Telemetry module @@ -195,11 +195,11 @@ GPIO control over the mesh network. Allows a remote node to read or write GPIO p Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. - Setting | Açıklaması | - ---------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | - Komşu Bilgisi etkin | Activate neighbor broadcasting | - Güncelleme aralığı (saniye) | How often to broadcast neighbor list | - LoRa üzerinden ilet | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | + Setting | Açıklaması | + ------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | + Komşu Bilgisi etkin | Activate neighbor broadcasting | + Update Interval | How often to broadcast neighbor list | + LoRa üzerinden ilet | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | See [Local Mesh Discovery](discovery) for how to use neighbor data for mesh topology exploration. @@ -223,8 +223,8 @@ Turns your node into a motion or door sensor alert system. When a GPIO pin detec İzlenecek GPIO pini | GPIO pin connected to sensor | Algılama tetikleme türü | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) | INPUT_PULLUP modu kullan | Enable the pin's internal pull-up resistor | - Minimum yayın (saniye) | Minimum time between alert broadcasts | - Durum yayını (saniye) | Periodic state broadcast interval | + Minimum time between detection broadcasts | Minimum time between alert broadcasts | + State Broadcast Interval | Periodic state broadcast interval | Uyarı mesajı ile zil gönder | Include bell character in alerts | Arkadaşça isim | Custom name for this sensor | @@ -232,12 +232,12 @@ Turns your node into a motion or door sensor alert system. When a GPIO pin detec People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. - Setting | Açıklaması | - ---------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | - Pax sayacı etkin | Activate people counting | - Güncelleme aralığı (saniye) | How often to report counts | - Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) | - BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | + Setting | Açıklaması | + --------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | + Pax sayacı etkin | Activate people counting | + Update Interval | How often to report counts | + WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) | + BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) | > 💡 **Tip:** Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. diff --git a/main/docs/tr-rTR/user/settings-radio-user.html b/main/docs/tr-rTR/user/settings-radio-user.html index 0881900e1b..518205e015 100644 --- a/main/docs/tr-rTR/user/settings-radio-user.html +++ b/main/docs/tr-rTR/user/settings-radio-user.html @@ -71,24 +71,24 @@ On **Settings → Device configuration → Device**. On **Settings → LoRa**. - Setting | Açıklaması | Varsayılan | - ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- | - Bölge | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) | - Presets | Speed/range tradeoff | LongFast | - Number of Hops | Maximum retransmit hops | 3 | - Transmit Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | - Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | - Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | - Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset | - Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | - Bant genişliği | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset | - Frequency Slot | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) | - Transmit Enabled | Turning this off makes the node receive-only | On | - Görev Döngüsünü Geçersiz Kıl | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | - MQTT'yi Yoksay | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | - Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | - RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | - PA fanı devre dışı | Turn off the power-amplifier fan on hardware that has one | Off | + Setting | Açıklaması | Varsayılan | + --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- | + Bölge | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) | + Presets | Speed/range tradeoff | LongFast | + Number of Hops | Maximum retransmit hops | 3 | + Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) | + Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | + Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | + Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset | + Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | + Bant genişliği | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset | + Frequency Slot | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) | + Transmit Enabled | Turning this off makes the node receive-only | On | + Görev Döngüsünü Geçersiz Kıl | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | + MQTT'yi Yoksay | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | + Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | + RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | + PA fanı devre dışı | Turn off the power-amplifier fan on hardware that has one | Off | The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn't appear in another. Changing region can therefore leave your current preset diff --git a/main/docs/uk-rUA/user/discovery.html b/main/docs/uk-rUA/user/discovery.html index e4661ddd45..49d2d35d14 100644 --- a/main/docs/uk-rUA/user/discovery.html +++ b/main/docs/uk-rUA/user/discovery.html @@ -161,7 +161,7 @@ The Neighbor Info module lets each node broadcast a list of the nodes it can **d 1. Navigate to **Settings → Module configuration → Neighbor Info**. 2. Enable the module. -3. Set **Update interval (seconds)**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. +3. Set **Update Interval**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. 4. Turn on **Transmit over LoRa**. Without it, your neighbor list goes only to MQTT and to this app, never over the air. Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. diff --git a/main/docs/uk-rUA/user/mqtt.html b/main/docs/uk-rUA/user/mqtt.html index 91708e215d..7c837b187b 100644 --- a/main/docs/uk-rUA/user/mqtt.html +++ b/main/docs/uk-rUA/user/mqtt.html @@ -90,7 +90,7 @@ Configure your node to point to your private broker with appropriate credentials When **Map reporting** is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. -Turning it on opens a consent card. Turn on **I agree.** and choose a **Map reporting interval (seconds)** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. +Turning it on opens a consent card. Turn on **I agree.** and choose a **Map Publish Interval** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at [meshmap.net](https://meshmap.net) and similar community map services. diff --git a/main/docs/uk-rUA/user/settings-module-admin.html b/main/docs/uk-rUA/user/settings-module-admin.html index 1f92a63794..d9c6adc73f 100644 --- a/main/docs/uk-rUA/user/settings-module-admin.html +++ b/main/docs/uk-rUA/user/settings-module-admin.html @@ -51,11 +51,11 @@ Turning **Map reporting** on reveals a consent card headed _Consent to Share Une via MQTT_, with an **I agree.** switch under it. The rest of the card doesn't exist on screen until you agree: - Setting | Опис | - -------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | - Погоджуюся. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it | - Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units | - Інтервал звітування на мапі (секунди) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | + Setting | Опис | + --------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | + Погоджуюся. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it | + Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units | + Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | See [MQTT](mqtt) for a detailed usage guide including encryption, privacy, and broker setup. @@ -80,20 +80,20 @@ Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devi There are two independent triggers — an incoming **message**, and a received **bell** character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. - Setting | Опис | - ------------------------------------------------- | --------------------------------------------------------------------------------------------------- | - Зовнішні сповіщення увімкнено | Master toggle for the module | - Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | - Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | - Вихідний LED (GPIO) | Pin the LED is wired to | - Активний високий рівень світлодіода | Whether the LED pin is active high or low | - Вихідний гудок (GPIO) | Pin the buzzer is wired to | - Вихід вібросигналу (GPIO) | Pin the vibration motor is wired to | - Використовувати зумер із ШІМ-керуванням | Drive the buzzer with PWM, which allows tones rather than a single pitch | - Використовувати I2S як гудок | Send the alert through an I2S audio output instead | - Тривалість виводу (мілісекунд) | How long a single alert lasts | - Інтервал нагадувань (секунди) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | - Мелодія | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | + Setting | Опис | + -------------------------------------------- | --------------------------------------------------------------------------------------------------- | + Зовнішні сповіщення увімкнено | Master toggle for the module | + Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | + Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | + Вихідний LED (GPIO) | Pin the LED is wired to | + Активний високий рівень світлодіода | Whether the LED pin is active high or low | + Вихідний гудок (GPIO) | Pin the buzzer is wired to | + Вихід вібросигналу (GPIO) | Pin the vibration motor is wired to | + Використовувати зумер із ШІМ-керуванням | Drive the buzzer with PWM, which allows tones rather than a single pitch | + Використовувати I2S як гудок | Send the alert through an I2S audio output instead | + GPIO Output Duration | How long a single alert lasts | + Nag Timeout | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | + Мелодія | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | ### Store & Forward module @@ -122,7 +122,7 @@ Automated range testing tool for evaluating link quality between nodes. When ena Setting | Опис | ----------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- | Тест на відстань увімкнений | Activate range testing | - Інтервал надсилання повідомлень (секунди) | Time between test transmissions, chosen from a dropdown of fixed intervals | + Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals | Зберегти .CSV у сховищі (лише ESP32) | Log received test data to the node's own filesystem. ESP32 hardware only | ### Telemetry module @@ -195,11 +195,11 @@ GPIO control over the mesh network. Allows a remote node to read or write GPIO p Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. - Setting | Опис | - ---------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | - Інформацію про сусідів увімкнено | Activate neighbor broadcasting | - Інтервал оновлення (секунд) | How often to broadcast neighbor list | - Передавати через LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | + Setting | Опис | + -------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | + Інформацію про сусідів увімкнено | Activate neighbor broadcasting | + Інтервал опитування GPS | How often to broadcast neighbor list | + Передавати через LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | See [Local Mesh Discovery](discovery) for how to use neighbor data for mesh topology exploration. @@ -217,27 +217,27 @@ Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. C Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. - Setting | Опис | - -------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | - Датчик виявлення увімкнено | Activate detection sensor | - GPIO контакт для моніторингу | GPIO pin connected to sensor | - Тип тригера виявлення | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) | - Використовувати режим INPUT_PULLUP | Enable the pin's internal pull-up resistor | - Мінімальний період розсилки (секунди) | Minimum time between alert broadcasts | - Інтервал трансляції стану (секунди) | Periodic state broadcast interval | - Надсилати дзвіночок з тривожним повідомленням | Include bell character in alerts | - Дружня назва | Custom name for this sensor | + Setting | Опис | + ------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | + Датчик виявлення увімкнено | Activate detection sensor | + GPIO контакт для моніторингу | GPIO pin connected to sensor | + Тип тригера виявлення | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) | + Використовувати режим INPUT_PULLUP | Enable the pin's internal pull-up resistor | + Minimum time between detection broadcasts | Minimum time between alert broadcasts | + State Broadcast Interval | Periodic state broadcast interval | + Надсилати дзвіночок з тривожним повідомленням | Include bell character in alerts | + Дружня назва | Custom name for this sensor | ### Paxcounter module People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. - Setting | Опис | - ---------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | - Лічильник пристроїв активований | Activate people counting | - Інтервал оновлення (секунд) | How often to report counts | - Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) | - BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | + Setting | Опис | + --------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | + Лічильник пристроїв активований | Activate people counting | + Інтервал опитування GPS | How often to report counts | + WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) | + BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) | > 💡 **Tip:** Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. diff --git a/main/docs/uk-rUA/user/settings-radio-user.html b/main/docs/uk-rUA/user/settings-radio-user.html index 219ff480e0..1c5fcb3139 100644 --- a/main/docs/uk-rUA/user/settings-radio-user.html +++ b/main/docs/uk-rUA/user/settings-radio-user.html @@ -76,7 +76,7 @@ On **Settings → LoRa**. Регіон | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) | Пресети | Speed/range tradeoff | LongFast | К-ть стрибків | Maximum retransmit hops | 3 | - Потужність передачі | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | + Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) | Перевизначити частоту | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | Використовувати пресет | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | Показник розширення сигналу | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset | diff --git a/main/docs/zh-rCN/user/discovery.html b/main/docs/zh-rCN/user/discovery.html index 1bc0e78368..9af9f81133 100644 --- a/main/docs/zh-rCN/user/discovery.html +++ b/main/docs/zh-rCN/user/discovery.html @@ -161,7 +161,7 @@ The Neighbor Info module lets each node broadcast a list of the nodes it can **d 1. Navigate to **Settings → Module configuration → Neighbor Info**. 2. Enable the module. -3. Set **Update interval (seconds)**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. +3. Set **Update Interval**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. 4. Turn on **Transmit over LoRa**. Without it, your neighbor list goes only to MQTT and to this app, never over the air. Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. diff --git a/main/docs/zh-rCN/user/mqtt.html b/main/docs/zh-rCN/user/mqtt.html index 162dd33041..a6f031167e 100644 --- a/main/docs/zh-rCN/user/mqtt.html +++ b/main/docs/zh-rCN/user/mqtt.html @@ -90,7 +90,7 @@ Configure your node to point to your private broker with appropriate credentials When **Map reporting** is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. -Turning it on opens a consent card. Turn on **I agree.** and choose a **Map reporting interval (seconds)** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. +Turning it on opens a consent card. Turn on **I agree.** and choose a **Map Publish Interval** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at [meshmap.net](https://meshmap.net) and similar community map services. diff --git a/main/docs/zh-rCN/user/settings-module-admin.html b/main/docs/zh-rCN/user/settings-module-admin.html index 231dd0a586..e82242e8a7 100644 --- a/main/docs/zh-rCN/user/settings-module-admin.html +++ b/main/docs/zh-rCN/user/settings-module-admin.html @@ -51,11 +51,11 @@ Turning **Map reporting** on reveals a consent card headed _Consent to Share Une via MQTT_, with an **I agree.** switch under it. The rest of the card doesn't exist on screen until you agree: - Setting | 说明 | - ----------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | - 我同意。 | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it | - Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units | - 地图报告间隔 (秒) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | + Setting | 说明 | + ---------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | + 我同意。 | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it | + Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units | + 地图发布间隔 | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | See [MQTT](mqtt) for a detailed usage guide including encryption, privacy, and broker setup. @@ -91,8 +91,8 @@ and each can drive the LED, the buzzer and the vibration motor separately, givin 输出振动 (GPIO) | Pin the vibration motor is wired to | 使用 PWM 蜂鸣器 | Drive the buzzer with PWM, which allows tones rather than a single pitch | 使用 I2S 作为蜂鸣器 | Send the alert through an I2S audio output instead | - 输出持续时间 (毫秒) | How long a single alert lasts | - 屏幕超时(秒) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | + GPIO Output Duration | How long a single alert lasts | + 超时提醒 | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | 铃声 | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | ### Store & Forward module @@ -122,7 +122,7 @@ Automated range testing tool for evaluating link quality between nodes. When ena Setting | 说明 | -------------------------------------- | ---------------------------------------------------------------------------------------- | 启用范围测试 | Activate range testing | - 发件人消息间隔(秒) | Time between test transmissions, chosen from a dropdown of fixed intervals | + 发送间隔 | Time between test transmissions, chosen from a dropdown of fixed intervals | 保存 CSV 到存储 (仅ESP32) | Log received test data to the node's own filesystem. ESP32 hardware only | ### Telemetry module @@ -198,7 +198,7 @@ Broadcasts information about directly heard neighbors, enabling mesh topology ma Setting | 说明 | ---------- | ------------------------------------------------------------------------------------------------------------------------------------ | 启用邻居信息 | Activate neighbor broadcasting | - 更新间隔（秒） | How often to broadcast neighbor list | + GPS 轮询间隔 | How often to broadcast neighbor list | 通过 LoRa 传输 | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | See [Local Mesh Discovery](discovery) for how to use neighbor data for mesh topology exploration. @@ -217,27 +217,27 @@ Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. C Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. - Setting | 说明 | - ---------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | - 启用检测传感器 | Activate detection sensor | - 显示器的 GPIO 引脚 | GPIO pin connected to sensor | - 检测触发器类型 | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) | - 使用 输入上拉 模式 | Enable the pin's internal pull-up resistor | - 最小广播时间(秒) | Minimum time between alert broadcasts | - 状态广播(秒) | Periodic state broadcast interval | - 发送带有警报消息的响铃声 | Include bell character in alerts | - 友好名称 | Custom name for this sensor | + Setting | 说明 | + ----------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | + 启用检测传感器 | Activate detection sensor | + 显示器的 GPIO 引脚 | GPIO pin connected to sensor | + 检测触发器类型 | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) | + 使用 输入上拉 模式 | Enable the pin's internal pull-up resistor | + Minimum time between detection broadcasts | Minimum time between alert broadcasts | + State Broadcast Interval | Periodic state broadcast interval | + 发送带有警报消息的响铃声 | Include bell character in alerts | + 友好名称 | Custom name for this sensor | ### Paxcounter module People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. - Setting | 说明 | - -------------------- | ---------------------------------------------------------------------------------------------------------------- | - 启用 Paxcount | Activate people counting | - 更新间隔（秒） | How often to report counts | - Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) | - BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | + Setting | 说明 | + --------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | + 启用 Paxcount | Activate people counting | + GPS 轮询间隔 | How often to report counts | + WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) | + BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) | > 💡 **Tip:** Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. diff --git a/main/docs/zh-rCN/user/settings-radio-user.html b/main/docs/zh-rCN/user/settings-radio-user.html index 3fb37b79b5..d5c9240624 100644 --- a/main/docs/zh-rCN/user/settings-radio-user.html +++ b/main/docs/zh-rCN/user/settings-radio-user.html @@ -71,24 +71,24 @@ On **Settings → Device configuration → Device**. On **Settings → LoRa**. - Setting | 说明 | 默认 | - ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- | - 区域 | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) | - 预设 | Speed/range tradeoff | LongFast | - 节点数 | Maximum retransmit hops | 3 | - 发送强度 | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | - 频率覆盖 | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | - 使用预设 | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | - 扩散因子 | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset | - 编码率 | Manual mode only: 5–8. More redundancy costs airtime | From preset | - 带宽 | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset | - 频率时隙 | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) | - 启用传输 | Turning this off makes the node receive-only | On | - 覆盖占空比 | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | 关闭 | - 忽略 MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | - 使用MQTT | Allow your packets to be forwarded to MQTT by gateways | 关闭 | - RX 增益 | Extra receive gain on SX126x radios; costs a little current | 关闭 | - PA风扇已禁用 | Turn off the power-amplifier fan on hardware that has one | 关闭 | + Setting | 说明 | 默认 | + --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- | + 区域 | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) | + 预设 | Speed/range tradeoff | LongFast | + 节点数 | Maximum retransmit hops | 3 | + Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) | + 频率覆盖 | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | + 使用预设 | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | + 扩散因子 | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset | + 编码率 | Manual mode only: 5–8. More redundancy costs airtime | From preset | + 带宽 | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset | + 频率时隙 | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) | + 启用传输 | Turning this off makes the node receive-only | On | + 覆盖占空比 | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | 关闭 | + 忽略 MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | + 使用MQTT | Allow your packets to be forwarded to MQTT by gateways | 关闭 | + RX 增益 | Extra receive gain on SX126x radios; costs a little current | 关闭 | + PA风扇已禁用 | Turn off the power-amplifier fan on hardware that has one | 关闭 | The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn't appear in another. Changing region can therefore leave your current preset diff --git a/main/docs/zh-rTW/user/discovery.html b/main/docs/zh-rTW/user/discovery.html index 9383e83cb2..ec63deb009 100644 --- a/main/docs/zh-rTW/user/discovery.html +++ b/main/docs/zh-rTW/user/discovery.html @@ -161,7 +161,7 @@ Each `⇊` line between two nodes is one relay hop, and the SNR on that line is 1. Navigate to **Settings → Module configuration → Neighbor Info**. 2. 啟用此模組。 -3. Set **Update interval (seconds)**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. +3. Set **Update Interval**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. 4. Turn on **Transmit over LoRa**. Without it, your neighbor list goes only to MQTT and to this app, never over the air. Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. 其他已啟用鄰近節點資訊的節點也會執行相同動作。 diff --git a/main/docs/zh-rTW/user/mqtt.html b/main/docs/zh-rTW/user/mqtt.html index 8a932a64f6..68e3fa64d8 100644 --- a/main/docs/zh-rTW/user/mqtt.html +++ b/main/docs/zh-rTW/user/mqtt.html @@ -90,7 +90,7 @@ When this phone relays MQTT for the radio, connections to that broker always use When **Map reporting** is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. -Turning it on opens a consent card. Turn on **I agree.** and choose a **Map reporting interval (seconds)** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. +Turning it on opens a consent card. Turn on **I agree.** and choose a **Map Publish Interval** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at [meshmap.net](https://meshmap.net) and similar community map services. diff --git a/main/docs/zh-rTW/user/settings-module-admin.html b/main/docs/zh-rTW/user/settings-module-admin.html index 83ed09c2ea..c12fb464df 100644 --- a/main/docs/zh-rTW/user/settings-module-admin.html +++ b/main/docs/zh-rTW/user/settings-module-admin.html @@ -51,11 +51,11 @@ Turning **Map reporting** on reveals a consent card headed _Consent to Share Une via MQTT_, with an **I agree.** switch under it. The rest of the card doesn't exist on screen until you agree: - 設定 | 描述說明 | - ---------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | - 我同意。 | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it | - Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units | - 地圖報告間隔（秒） | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | + 設定 | 描述說明 | + -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | + 我同意。 | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it | + Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units | + Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | See [MQTT](mqtt) for a detailed usage guide including encryption, privacy, and broker setup. @@ -91,8 +91,8 @@ and each can drive the LED, the buzzer and the vibration motor separately, givin 輸出振動（GPIO） | Pin the vibration motor is wired to | 使用PWM調製的蜂鳴 | Drive the buzzer with PWM, which allows tones rather than a single pitch | 使用 I2S 控制蜂鳴器 | Send the alert through an I2S audio output instead | - 輸出持續時間（毫秒） | How long a single alert lasts | - 通知逾時時間（秒） | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | + GPIO Output Duration | How long a single alert lasts | + 持續提醒逾時 | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | 鈴聲 | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | ### Store & Forward module @@ -122,7 +122,7 @@ Automated range testing tool for evaluating link quality between nodes. When ena 設定 | 描述說明 | ------------------------------------------------------------ | ---------------------------------------------------------------------------------------- | 啟用範圍測試 | Activate range testing | - 訊息發送間隔(秒) | Time between test transmissions, chosen from a dropdown of fixed intervals | + 傳送間隔 | Time between test transmissions, chosen from a dropdown of fixed intervals | 將 .CSV 保存到內部儲存空間(僅限ESP32) | Log received test data to the node's own filesystem. ESP32 hardware only | ### Telemetry module @@ -198,7 +198,7 @@ Broadcasts information about directly heard neighbors, enabling mesh topology ma 設定 | 描述說明 | ----------- | ------------------------------------------------------------------------------------------------------------------------------------ | 啟用鄰居資訊 | Activate neighbor broadcasting | - 更新間隔（秒） | How often to broadcast neighbor list | + GPS 輪詢間隔 | How often to broadcast neighbor list | 通過Lora無線電傳輸 | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | See [Local Mesh Discovery](discovery) for how to use neighbor data for mesh topology exploration. @@ -217,27 +217,27 @@ Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. C Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. - 設定 | 描述說明 | - ----------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | - 啟用偵測感測器 | Activate detection sensor | - 螢幕的 GPIO 腳位 | GPIO pin connected to sensor | - 偵測觸發類型 | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) | - 使用輸入上拉模式 | Enable the pin's internal pull-up resistor | - 最短廣播間隔 (秒) | Minimum time between alert broadcasts | - 狀態廣播間隔 (秒) | Periodic state broadcast interval | - 告警訊息發送提示音 | Include bell character in alerts | - 顯示名稱 | Custom name for this sensor | + 設定 | 描述說明 | + ----------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | + 啟用偵測感測器 | Activate detection sensor | + 螢幕的 GPIO 腳位 | GPIO pin connected to sensor | + 偵測觸發類型 | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) | + 使用輸入上拉模式 | Enable the pin's internal pull-up resistor | + Minimum time between detection broadcasts | Minimum time between alert broadcasts | + 狀態廣播間隔 | Periodic state broadcast interval | + 告警訊息發送提示音 | Include bell character in alerts | + 顯示名稱 | Custom name for this sensor | ### Paxcounter module People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. - 設定 | 描述說明 | - -------------------- | ---------------------------------------------------------------------------------------------------------------- | - 已啟用人流計數（Paxcount） | Activate people counting | - 更新間隔（秒） | How often to report counts | - Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) | - BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | + 設定 | 描述說明 | + --------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | + 已啟用人流計數（Paxcount） | Activate people counting | + GPS 輪詢間隔 | How often to report counts | + WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) | + BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) | > 💡 **Tip:** Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. diff --git a/main/docs/zh-rTW/user/settings-radio-user.html b/main/docs/zh-rTW/user/settings-radio-user.html index 2a30a74e61..c830416ba7 100644 --- a/main/docs/zh-rTW/user/settings-radio-user.html +++ b/main/docs/zh-rTW/user/settings-radio-user.html @@ -71,24 +71,24 @@ On **Settings → Device configuration → Device**. On **Settings → LoRa**. - 設定 | 描述說明 | 默認 | - ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- | - 地區 | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) | - 預設配置 | Speed/range tradeoff | LongFast | - 中繼次數 | Maximum retransmit hops | 3 | - 傳輸功率 | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | - 手動設定頻率 | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | - 使用預設值 | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | - 擴頻因子 | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset | - 編碼率 | Manual mode only: 5–8. More redundancy costs airtime | From preset | - 頻寬 | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset | - 頻率槽 | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) | - 已啟用發射 | Turning this off makes the node receive-only | On | - 覆蓋工作週期/佔空比 | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | - 忽略 MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | - 允許轉發至 MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | - 接收增益提升 | Extra receive gain on SX126x radios; costs a little current | Off | - 停用PA風扇 | Turn off the power-amplifier fan on hardware that has one | Off | + 設定 | 描述說明 | 默認 | + --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- | + 地區 | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) | + 預設配置 | Speed/range tradeoff | LongFast | + 中繼次數 | Maximum retransmit hops | 3 | + Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) | + 手動設定頻率 | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | + 使用預設值 | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | + 擴頻因子 | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset | + 編碼率 | Manual mode only: 5–8. More redundancy costs airtime | From preset | + 頻寬 | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset | + 頻率槽 | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) | + 已啟用發射 | Turning this off makes the node receive-only | On | + 覆蓋工作週期/佔空比 | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | + 忽略 MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | + 允許轉發至 MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | + 接收增益提升 | Extra receive gain on SX126x radios; costs a little current | Off | + 停用PA風扇 | Turn off the power-amplifier fan on hardware that has one | Off | The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn't appear in another. Changing region can therefore leave your current preset diff --git a/main/el-rGR/user/discovery.html b/main/el-rGR/user/discovery.html index fa016dbd61..d3895fb7d8 100644 --- a/main/el-rGR/user/discovery.html +++ b/main/el-rGR/user/discovery.html @@ -5,4 +5,4 @@ ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) -

Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:.

What to look for What it means
All hops show Good SNR (green) Healthy path — messages flow reliably
One hop shows a poor SNR (orange or red) Weak link — this relay segment is fragile
Many hops (4+) Long path — consider repositioning a node to shorten it
Different path on retry Mesh is adapting — multiple routes exist (this is good!)

💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network.

Troubleshooting with Traceroute

  • No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key.
  • Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa.
  • Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position.
  • Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric.

Neighbor Info

The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh.

Enabling Neighbor Info

  1. Navigate to Settings → Module configuration → Neighbor Info.
  2. Enable the module.
  3. Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
  4. Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air.

Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.

Viewing neighbor data

  • Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors.
  • Each neighbor entry shows the node that was directly heard and its signal quality.
  • Combine neighbor data from multiple nodes to understand the full mesh topology.

ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further.

Node list as a discovery tool

The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively.

Finding new nodes

  • Sort by Last heard to see the most recently active nodes at the top.
  • Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes.

Assessing connectivity

  • Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed.
  • Sort by Distance to find nearby nodes and verify they’re reachable.
  • Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge).

Infrastructure audit

  • Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes.
  • Check their signal quality and last-heard times to verify your infrastructure nodes are healthy.

See Nodes for full details on filtering and sorting options.

Tips for Mesh exploration

  • Start with traceroute — it gives you immediate, actionable information about a specific path.
  • Enable Neighbor Info on key nodes — especially routers and repeaters, to build a picture of the backbone.
  • Check the map — node positions on the Map combined with signal data help you understand why some links are strong and others are weak.
  • Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly.
+

Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:.

What to look for What it means
All hops show Good SNR (green) Healthy path — messages flow reliably
One hop shows a poor SNR (orange or red) Weak link — this relay segment is fragile
Many hops (4+) Long path — consider repositioning a node to shorten it
Different path on retry Mesh is adapting — multiple routes exist (this is good!)

💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network.

Troubleshooting with Traceroute

  • No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key.
  • Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa.
  • Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position.
  • Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric.

Neighbor Info

The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh.

Enabling Neighbor Info

  1. Navigate to Settings → Module configuration → Neighbor Info.
  2. Enable the module.
  3. Set Update Interval. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
  4. Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air.

Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.

Viewing neighbor data

  • Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors.
  • Each neighbor entry shows the node that was directly heard and its signal quality.
  • Combine neighbor data from multiple nodes to understand the full mesh topology.

ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further.

Node list as a discovery tool

The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively.

Finding new nodes

  • Sort by Last heard to see the most recently active nodes at the top.
  • Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes.

Assessing connectivity

  • Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed.
  • Sort by Distance to find nearby nodes and verify they’re reachable.
  • Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge).

Infrastructure audit

  • Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes.
  • Check their signal quality and last-heard times to verify your infrastructure nodes are healthy.

See Nodes for full details on filtering and sorting options.

Tips for Mesh exploration

  • Start with traceroute — it gives you immediate, actionable information about a specific path.
  • Enable Neighbor Info on key nodes — especially routers and repeaters, to build a picture of the backbone.
  • Check the map — node positions on the Map combined with signal data help you understand why some links are strong and others are weak.
  • Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly.
diff --git a/main/el-rGR/user/mqtt.html b/main/el-rGR/user/mqtt.html index 4f5b726fec..4900298437 100644 --- a/main/el-rGR/user/mqtt.html +++ b/main/el-rGR/user/mqtt.html @@ -1,2 +1,2 @@ MQTT | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Ελληνικά
Meshtastic Docs ↗

🌐 Ελληνικά — Community translation View in English

MQTT

MQTT bridges your Meshtastic mesh network to the internet, enabling long-range communication beyond radio range.

Overview

The MQTT module connects your node to an MQTT broker, allowing:

  • Messages to reach nodes on different physical meshes via the internet
  • Integration with home automation and monitoring systems
  • Publishing node positions to the public Meshtastic map
  • Custom data pipelines for logging and alerting

How It Works 

[Your Node] → Radio → [Gateway Node with Wi-Fi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node]
-

A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh.

Configuration

Enabling MQTT

  1. Navigate to Settings → Module configuration → MQTT.
  2. Enable the MQTT module.
  3. Configure the broker connection:
Setting Περιγραφή Default
Address MQTT broker hostname mqtt.meshtastic.org
Username Broker authentication meshdev
Password Broker authentication large4cats
Root topic Base topic for messages msh, which the radio rewrites to msh/<REGION> once you set a region
Encryption enabled Encrypt MQTT payload Enabled
JSON output enabled Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it Disabled
TLS enabled Secure connection to broker Disabled
Map reporting Report position to public map Disabled
Proxy to client enabled Relay MQTT through the connected phone Disabled

Connection Status and Test Connection

The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here.

Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason.

MQTT Proxy on This Phone

If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection.

ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them.

The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration.

Default Meshtastic Broker

The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing.

When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without).

🔒 Privacy: Messages on the public broker are readable by anyone subscribed. Always use channel encryption for private communications.

Private Broker

For better privacy and control, you can run your own MQTT broker:

  • Mosquitto (lightweight, open-source)
  • HiveMQ
  • EMQX

Configure your node to point to your private broker with appropriate credentials.

Map Reporting

When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.

Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.

Reports appear at meshmap.net and similar community map services.

🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published.

Direction Περιγραφή
Uplink Messages from mesh → MQTT broker
Downlink Messages from MQTT broker → mesh

Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on.

Message Formats

MQTT carries two payload formats:

Format Περιγραφή Use case
Protobuf Binary Meshtastic protobuf encoding Node-to-node mesh bridging
JSON Human-readable JSON on the /2/json/ topic Consumers outside the mesh (dashboards, home automation)

ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads.

Encryption & Privacy

Understanding the layered encryption model:

  1. Channel encryption happens on the mesh before MQTT. If your channel has a PSK, the MQTT payload is already encrypted — the broker and any subscribers see only the ciphertext.
  2. Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard.
  3. TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping.

🔒 Security: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications.

Best Practices

  • Use channel-level encryption (PSK) on channels that bridge to MQTT
  • Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes memory)
  • Use a private broker for sensitive deployments
  • Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh
  • Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back

Troubleshooting

MQTT Not Connecting

  • Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself.
  • Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces.
  • Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443).
  • DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly.

Messages Not Bridging

  • Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway.
  • Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage.
  • Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root.
  • Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway.
  • Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in.
+

A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh.

Configuration

Enabling MQTT

  1. Navigate to Settings → Module configuration → MQTT.
  2. Enable the MQTT module.
  3. Configure the broker connection:
Setting Περιγραφή Default
Address MQTT broker hostname mqtt.meshtastic.org
Username Broker authentication meshdev
Password Broker authentication large4cats
Root topic Base topic for messages msh, which the radio rewrites to msh/<REGION> once you set a region
Encryption enabled Encrypt MQTT payload Enabled
JSON output enabled Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it Disabled
TLS enabled Secure connection to broker Disabled
Map reporting Report position to public map Disabled
Proxy to client enabled Relay MQTT through the connected phone Disabled

Connection Status and Test Connection

The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here.

Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason.

MQTT Proxy on This Phone

If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection.

ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them.

The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration.

Default Meshtastic Broker

The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing.

When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without).

🔒 Privacy: Messages on the public broker are readable by anyone subscribed. Always use channel encryption for private communications.

Private Broker

For better privacy and control, you can run your own MQTT broker:

  • Mosquitto (lightweight, open-source)
  • HiveMQ
  • EMQX

Configure your node to point to your private broker with appropriate credentials.

Map Reporting

When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.

Turning it on opens a consent card. Turn on I agree. and choose a Map Publish Interval of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.

Reports appear at meshmap.net and similar community map services.

🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published.

Direction Περιγραφή
Uplink Messages from mesh → MQTT broker
Downlink Messages from MQTT broker → mesh

Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on.

Message Formats

MQTT carries two payload formats:

Format Περιγραφή Use case
Protobuf Binary Meshtastic protobuf encoding Node-to-node mesh bridging
JSON Human-readable JSON on the /2/json/ topic Consumers outside the mesh (dashboards, home automation)

ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads.

Encryption & Privacy

Understanding the layered encryption model:

  1. Channel encryption happens on the mesh before MQTT. If your channel has a PSK, the MQTT payload is already encrypted — the broker and any subscribers see only the ciphertext.
  2. Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard.
  3. TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping.

🔒 Security: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications.

Best Practices

  • Use channel-level encryption (PSK) on channels that bridge to MQTT
  • Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes memory)
  • Use a private broker for sensitive deployments
  • Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh
  • Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back

Troubleshooting

MQTT Not Connecting

  • Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself.
  • Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces.
  • Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443).
  • DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly.

Messages Not Bridging

  • Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway.
  • Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage.
  • Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root.
  • Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway.
  • Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in.
diff --git a/main/el-rGR/user/settings-module-admin.html b/main/el-rGR/user/settings-module-admin.html index d6ce74f89a..c3b9db5b26 100644 --- a/main/el-rGR/user/settings-module-admin.html +++ b/main/el-rGR/user/settings-module-admin.html @@ -1 +1 @@ - Settings — Modules & Admin | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Ελληνικά
Meshtastic Docs ↗

🌐 Ελληνικά — Community translation View in English

Settings — Modules & Admin

Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.

💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.

Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:

A toggle setting in the on position

A dropdown setting, expanded to show its list of options

A text field setting with a value entered

A module settings card with its title and grouped controls

Ρυθμίσεις πρόσθετου

Every module lives under Settings → Module configuration.

⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes.

MQTT module

Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.

Setting Περιγραφή
MQTT enabled Toggle MQTT bridge
Διεύθυνση MQTT broker address
Όνομα χρήστη Authentication username
Κωδικός πρόσβασης Authentication password
Encryption enabled Encrypt MQTT payloads
JSON output enabled Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS enabled Use secure connection
Root topic Base MQTT topic path
Proxy to client enabled Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy on this phone The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT
Map reporting Publish position to the public map — see the Map reporting group that follows

Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:

Setting Περιγραφή
I agree. Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map reporting interval (seconds) How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered

See MQTT for a detailed usage guide including encryption, privacy, and broker setup.

Serial module

Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.

Setting Περιγραφή
Serial enabled Activate serial communication
Echo enabled Echo received serial data back
Serial mode Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX GPIO pins for the serial connection
Serial baud rate Port speed
Λήξη χρονικού ορίου How long to wait before considering an incoming message complete
Override console serial port Take over the port the debug console normally uses

External Notification module

Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.

There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.

Setting Περιγραφή
External notification enabled Master toggle for the module
Alert message LED / buzzer / vibra Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra Which outputs fire on a received bell character
Output LED (GPIO) Pin the LED is wired to
Output LED active high Whether the LED pin is active high or low
Output buzzer (GPIO) Pin the buzzer is wired to
Output vibra (GPIO) Pin the vibration motor is wired to
Use PWM buzzer Drive the buzzer with PWM, which allows tones rather than a single pitch
Use I2S as buzzer Send the alert through an I2S audio output instead
Output duration (milliseconds) How long a single alert lasts
Nag timeout (seconds) Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Ringtone The tone played on a PWM buzzer, in RTTTL. Can be imported from a file

Store & Forward module

Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.

Setting Περιγραφή
Store & Forward enabled Activate store and forward
Heartbeat Periodically announce this node’s store-and-forward capability
Number of records Maximum stored messages
History return max Max messages to replay
History return window Time window for replay
Server Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)

💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.

Range Test module

⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.

Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.

Setting Περιγραφή
Range test enabled Activate range testing
Sender message interval (seconds) Time between test transmissions, chosen from a dropdown of fixed intervals
Save .CSV in storage (ESP32 only) Log received test data to the node’s own filesystem. ESP32 hardware only

Telemetry module

Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).

Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.

Setting Περιγραφή
Send Device Telemetry Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval How often to report battery, uptime and channel utilization
Environment metrics module enabled Report the attached environment sensors
Environment metrics update interval How often to report them
Environment metrics on-screen enabled Also show these readings on the device’s own display
Environment metrics use Fahrenheit Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Air quality metrics module enabled Report particulate and CO₂ sensor data
Air quality metrics update interval How often to report them
Power metrics module enabled Report the per-channel voltage and current readings
Power metrics update interval How often to report them
Power metrics on-screen enabled Also show power readings on the device’s display

See Telemetry & Sensors for supported sensors and configuration recommendations.

Canned Message module

Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.

Setting Περιγραφή
Canned message enabled ⚠️ Deprecated in the protobuf schema
Μηνύματα Newline-separated list of messages
Send bell Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Rotary encoder #1 enabled Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port The three pins the encoder is wired to
Generate input event on Press / CW / CCW Which key event each encoder action produces
Up/Down/Select input enabled A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source ⚠️ Deprecated in the protobuf schema

Audio module

Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.

Setting Περιγραφή
CODEC 2 enabled Activate audio module
CODEC2 sample rate Audio quality/bandwidth tradeoff
PTT pin GPIO pin for the push-to-talk button
I2S word select GPIO pin for I2S WS
I2S data in GPIO pin for I2S DIN
I2S data out GPIO pin for I2S DOUT
I2S clock GPIO pin for the I2S bit clock

ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.

Remote Hardware module

GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.

⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.

Setting Περιγραφή
Remote Hardware enabled Activate remote GPIO access
Allow undefined pin access Allow access to any GPIO pin (security risk)
Available pins Up to 4 GPIO pins this node exposes for remote read/write

Neighbor Info module

Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.

Setting Περιγραφή
Neighbor Info enabled Activate neighbor broadcasting
Update interval (seconds) How often to broadcast neighbor list
Transmit over LoRa Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name

See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.

Ambient Lighting module

Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.

Setting Περιγραφή
LED state Turn the LED on or off
Current LED current limit (0–31)
Red / Green / Blue Individual color channel values (0–255)

Detection Sensor module

Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.

Setting Περιγραφή
Detection Sensor enabled Activate detection sensor
GPIO pin to monitor GPIO pin connected to sensor
Detection trigger type How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Use INPUT_PULLUP mode Enable the pin’s internal pull-up resistor
Minimum broadcast (seconds) Minimum time between alert broadcasts
State broadcast (seconds) Periodic state broadcast interval
Send bell with alert message Include bell character in alerts
Friendly name Custom name for this sensor

Paxcounter module

People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.

Setting Περιγραφή
Paxcounter enabled Activate people counting
Update interval (seconds) How often to report counts
Wi-Fi RSSI threshold Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE RSSI threshold The same cut-off for BLE advertisements (defaults to −80 dBm)

💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.

Status Message module

The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.

Mesh Beacon module

Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.

TAK module

Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.

Διαχείριση

Απομακρυσμένη Διαχείριση

Remotely configure nodes that share your admin key:

  1. Select the target node in the node list.
  2. Navigate to Settings for that node.
  3. Modify configuration.
  4. Tap Save — changes are sent over the mesh.

⚠️ Important: Requires an admin key configured on both your node and the target node.

Device Actions

Settings → Administration holds five one-shot actions, each behind a confirmation dialog:

Action What it does
Set time Sends your phone’s clock to the node
Επανεκκίνηση Restarts the node
Τερματισμός λειτουργίας Powers the node down
Επαναφορά εργοστασιακών ρυθμίσεων Returns every setting to its factory default
NodeDB reset Clears the node database. This dialog carries a Preserve Favorites? switch

⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.

Backup & Restore

Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.

Advanced

Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.

Clean Node Database

Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.

  • Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
  • Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.

The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.

Πίνακας αποσφαλμάτωσης

Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.

App Settings

The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:

Privacy

  • Allow analytics and crash reporting — opt in or out of diagnostics.
  • Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
  • Homoglyph encoding — how look-alike characters in names are handled.

Appearance

  • Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
  • Theme and Language.
  • Show full message timestamps.

Persistence

  • A cache limit for how much history is kept.
  • Export rangetest packets, Export all packets and Export node database.

On their own

  • Node Layout — how much detail each row of the node list shows.
  • Wi-Fi Provisioning for mPWRD-OS — see Connections.
  • Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
  • System AI — appears only where app functions are available; see App Functions.

A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.

Σχετικά

Settings → About carries the app’s own identity rather than the node’s:

Three sections:

  • What is Meshtastic? — a short description of the project.
  • Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
  • Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.

The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.

Acknowledgements

Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.

Troubleshooting remote admin

  • “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
  • Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
  • Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
+ Settings — Modules & Admin | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Ελληνικά
Meshtastic Docs ↗

🌐 Ελληνικά — Community translation View in English

Settings — Modules & Admin

Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.

💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.

Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:

A toggle setting in the on position

A dropdown setting, expanded to show its list of options

A text field setting with a value entered

A module settings card with its title and grouped controls

Ρυθμίσεις πρόσθετου

Every module lives under Settings → Module configuration.

⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes.

MQTT module

Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.

Setting Περιγραφή
MQTT enabled Toggle MQTT bridge
Διεύθυνση MQTT broker address
Όνομα χρήστη Authentication username
Κωδικός πρόσβασης Authentication password
Encryption enabled Encrypt MQTT payloads
JSON output enabled Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS enabled Use secure connection
Root topic Base MQTT topic path
Proxy to client enabled Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy on this phone The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT
Map reporting Publish position to the public map — see the Map reporting group that follows

Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:

Setting Περιγραφή
I agree. Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered

See MQTT for a detailed usage guide including encryption, privacy, and broker setup.

Serial module

Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.

Setting Περιγραφή
Serial enabled Activate serial communication
Echo enabled Echo received serial data back
Serial mode Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX GPIO pins for the serial connection
Serial baud rate Port speed
Λήξη χρονικού ορίου How long to wait before considering an incoming message complete
Override console serial port Take over the port the debug console normally uses

External Notification module

Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.

There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.

Setting Περιγραφή
External notification enabled Master toggle for the module
Alert message LED / buzzer / vibra Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra Which outputs fire on a received bell character
Output LED (GPIO) Pin the LED is wired to
Output LED active high Whether the LED pin is active high or low
Output buzzer (GPIO) Pin the buzzer is wired to
Output vibra (GPIO) Pin the vibration motor is wired to
Use PWM buzzer Drive the buzzer with PWM, which allows tones rather than a single pitch
Use I2S as buzzer Send the alert through an I2S audio output instead
GPIO Output Duration How long a single alert lasts
Nag Timeout Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Ringtone The tone played on a PWM buzzer, in RTTTL. Can be imported from a file

Store & Forward module

Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.

Setting Περιγραφή
Store & Forward enabled Activate store and forward
Heartbeat Periodically announce this node’s store-and-forward capability
Number of records Maximum stored messages
History return max Max messages to replay
History return window Time window for replay
Server Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)

💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.

Range Test module

⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.

Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.

Setting Περιγραφή
Range test enabled Activate range testing
Sender Interval Time between test transmissions, chosen from a dropdown of fixed intervals
Save .CSV in storage (ESP32 only) Log received test data to the node’s own filesystem. ESP32 hardware only

Telemetry module

Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).

Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.

Setting Περιγραφή
Send Device Telemetry Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval How often to report battery, uptime and channel utilization
Environment metrics module enabled Report the attached environment sensors
Environment metrics update interval How often to report them
Environment metrics on-screen enabled Also show these readings on the device’s own display
Environment metrics use Fahrenheit Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Air quality metrics module enabled Report particulate and CO₂ sensor data
Air quality metrics update interval How often to report them
Power metrics module enabled Report the per-channel voltage and current readings
Power metrics update interval How often to report them
Power metrics on-screen enabled Also show power readings on the device’s display

See Telemetry & Sensors for supported sensors and configuration recommendations.

Canned Message module

Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.

Setting Περιγραφή
Canned message enabled ⚠️ Deprecated in the protobuf schema
Μηνύματα Newline-separated list of messages
Send bell Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Rotary encoder #1 enabled Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port The three pins the encoder is wired to
Generate input event on Press / CW / CCW Which key event each encoder action produces
Up/Down/Select input enabled A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source ⚠️ Deprecated in the protobuf schema

Audio module

Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.

Setting Περιγραφή
CODEC 2 enabled Activate audio module
CODEC2 sample rate Audio quality/bandwidth tradeoff
PTT pin GPIO pin for the push-to-talk button
I2S word select GPIO pin for I2S WS
I2S data in GPIO pin for I2S DIN
I2S data out GPIO pin for I2S DOUT
I2S clock GPIO pin for the I2S bit clock

ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.

Remote Hardware module

GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.

⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.

Setting Περιγραφή
Remote Hardware enabled Activate remote GPIO access
Allow undefined pin access Allow access to any GPIO pin (security risk)
Available pins Up to 4 GPIO pins this node exposes for remote read/write

Neighbor Info module

Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.

Setting Περιγραφή
Neighbor Info enabled Activate neighbor broadcasting
Update Interval How often to broadcast neighbor list
Transmit over LoRa Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name

See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.

Ambient Lighting module

Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.

Setting Περιγραφή
LED state Turn the LED on or off
Current LED current limit (0–31)
Red / Green / Blue Individual color channel values (0–255)

Detection Sensor module

Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.

Setting Περιγραφή
Detection Sensor enabled Activate detection sensor
GPIO pin to monitor GPIO pin connected to sensor
Detection trigger type How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Use INPUT_PULLUP mode Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts Minimum time between alert broadcasts
State Broadcast Interval Periodic state broadcast interval
Send bell with alert message Include bell character in alerts
Friendly name Custom name for this sensor

Paxcounter module

People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.

Setting Περιγραφή
Paxcounter enabled Activate people counting
Update Interval How often to report counts
WiFi Threshold (dBm) Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm) The same cut-off for BLE advertisements (defaults to −80 dBm)

💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.

Status Message module

The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.

Mesh Beacon module

Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.

TAK module

Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.

Διαχείριση

Απομακρυσμένη Διαχείριση

Remotely configure nodes that share your admin key:

  1. Select the target node in the node list.
  2. Navigate to Settings for that node.
  3. Modify configuration.
  4. Tap Save — changes are sent over the mesh.

⚠️ Important: Requires an admin key configured on both your node and the target node.

Device Actions

Settings → Administration holds five one-shot actions, each behind a confirmation dialog:

Action What it does
Set time Sends your phone’s clock to the node
Επανεκκίνηση Restarts the node
Τερματισμός λειτουργίας Powers the node down
Επαναφορά εργοστασιακών ρυθμίσεων Returns every setting to its factory default
NodeDB reset Clears the node database. This dialog carries a Preserve Favorites? switch

⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.

Backup & Restore

Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.

Advanced

Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.

Clean Node Database

Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.

  • Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
  • Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.

The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.

Πίνακας αποσφαλμάτωσης

Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.

App Settings

The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:

Privacy

  • Allow analytics and crash reporting — opt in or out of diagnostics.
  • Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
  • Homoglyph encoding — how look-alike characters in names are handled.

Appearance

  • Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
  • Theme and Language.
  • Show full message timestamps.

Persistence

  • A cache limit for how much history is kept.
  • Export rangetest packets, Export all packets and Export node database.

On their own

  • Node Layout — how much detail each row of the node list shows.
  • Wi-Fi Provisioning for mPWRD-OS — see Connections.
  • Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
  • System AI — appears only where app functions are available; see App Functions.

A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.

Σχετικά

Settings → About carries the app’s own identity rather than the node’s:

Three sections:

  • What is Meshtastic? — a short description of the project.
  • Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
  • Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.

The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.

Acknowledgements

Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.

Troubleshooting remote admin

  • “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
  • Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
  • Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
diff --git a/main/el-rGR/user/settings-radio-user.html b/main/el-rGR/user/settings-radio-user.html index 58dee0a420..2a48edee57 100644 --- a/main/el-rGR/user/settings-radio-user.html +++ b/main/el-rGR/user/settings-radio-user.html @@ -1 +1 @@ - Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Ελληνικά
Meshtastic Docs ↗

🌐 Ελληνικά — Community translation View in English

Settings — Radio & User

Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How these screens work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Περιγραφή
Long Name Your display name (up to 39 characters)
Short Name 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Unmessageable Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur node (Ham) Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in.

Configuration

Device Config

On Settings → Device configuration → Device.

Setting Περιγραφή Default
Device Role Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Rebroadcast Mode How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Node Info Broadcast Interval How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Double Tap as Button Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Enabled
LED Heartbeat Blink the status LED periodically Enabled
Time Zone POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it —
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to —

LoRa Config

On Settings → LoRa.

Setting Περιγραφή Default
Περιφέρεια Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number Unset (must configure)
Presets Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Transmit Power Transmission power (dBm); 0 = max allowed for region 0 (region max)
Frequency Override Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Use Preset On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead From preset
Coding Rate Manual mode only: 5–8. More redundancy costs airtime From preset
Bandwidth Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Frequency Slot Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmit Enabled Turning this off makes the node receive-only On
Override Duty Cycle Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
Ignore MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok to MQTT Allow your packets to be forwarded to MQTT by gateways Off
RX Boosted Gain Extra receive gain on SX126x radios; costs a little current Off
PA fan disabled Turn off the power-amplifier fan on hardware that has one Off

The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set.

Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Speed SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a modem preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Display Config

On Settings → Device configuration → Display. These control the node’s own screen, not the app’s.

Setting Περιγραφή
Screen on for How long the display stays lit before sleeping
Carousel interval How often the node cycles between screens on its own
Display mode Screen layout/density used by the firmware
Display units Metric or Imperial on the node’s screen
Use 12h clock format Show the node’s clock as 12-hour rather than 24-hour
Bold Heading Draw the screen’s heading text in bold
Flip screen Rotate the display 180° for an inverted mounting
OLED type Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED
Wake on tap or motion Light the screen when the node is tapped or moved
Compass orientation Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each
Always point north Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Position Config

On Settings → Device configuration → Position.

Setting Περιγραφή
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the node asks its GPS for a fix
Broadcast Interval How often the position is shared with the mesh
Smart Position Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Fixed Position Use a manually entered latitude, longitude and altitude instead of the GPS
Position Flags A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Power Config

On Settings → Device configuration → Power.

Setting Περιγραφή
Enable power saving mode Let the node sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the node stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC multiplier override ratio The correction factor itself, used only when the override is on
Battery INA_2XX I2C address Address of an external INA-series power sensor, if fitted

Network Config

On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node.

Setting Περιγραφή
Wi-Fi enabled Enable the Wi-Fi node (ESP32 nodes)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Κωδικός πρόσβασης Network password
Ethernet enabled Use a wired connection on hardware that has one
IPv4 mode DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP server Time synchronization server
rsyslog server Remote logging server

Network Config with a static IPv4 address entered

Ρυθμίσεις Bluetooth

On Settings → Device configuration → Bluetooth, on nodes with Bluetooth.

Setting Περιγραφή
Bluetooth enabled Enable/disable BLE radio
Pairing mode Fixed PIN, Random PIN, or No PIN
Fixed PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Security Config

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

Setting Περιγραφή
Δημόσιο Κλειδί Your node’s public key (read-only)
Admin Key Keys permitted to administer this node remotely — up to three
Ιδιωτικό Κλειδί Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it
Regenerate Private Key Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Serial console Serial console over the Stream API
Debug log API enabled Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth
Managed Mode Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.

+ Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Ελληνικά
Meshtastic Docs ↗

🌐 Ελληνικά — Community translation View in English

Settings — Radio & User

Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How these screens work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Περιγραφή
Long Name Your display name (up to 39 characters)
Short Name 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Unmessageable Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur node (Ham) Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in.

Configuration

Device Config

On Settings → Device configuration → Device.

Setting Περιγραφή Default
Device Role Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Rebroadcast Mode How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Node Info Broadcast Interval How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Double Tap as Button Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Enabled
LED Heartbeat Blink the status LED periodically Enabled
Time Zone POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it —
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to —

LoRa Config

On Settings → LoRa.

Setting Περιγραφή Default
Περιφέρεια Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number Unset (must configure)
Presets Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Transmit Power (dBm) Transmission power; 0 = max allowed for region 0 (region max)
Frequency Override Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Use Preset On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead From preset
Coding Rate Manual mode only: 5–8. More redundancy costs airtime From preset
Bandwidth Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Frequency Slot Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmit Enabled Turning this off makes the node receive-only On
Override Duty Cycle Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
Ignore MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok to MQTT Allow your packets to be forwarded to MQTT by gateways Off
RX Boosted Gain Extra receive gain on SX126x radios; costs a little current Off
PA fan disabled Turn off the power-amplifier fan on hardware that has one Off

The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set.

Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Speed SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a modem preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Display Config

On Settings → Device configuration → Display. These control the node’s own screen, not the app’s.

Setting Περιγραφή
Screen on for How long the display stays lit before sleeping
Carousel interval How often the node cycles between screens on its own
Display mode Screen layout/density used by the firmware
Display units Metric or Imperial on the node’s screen
Use 12h clock format Show the node’s clock as 12-hour rather than 24-hour
Bold Heading Draw the screen’s heading text in bold
Flip screen Rotate the display 180° for an inverted mounting
OLED type Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED
Wake on tap or motion Light the screen when the node is tapped or moved
Compass orientation Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each
Always point north Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Position Config

On Settings → Device configuration → Position.

Setting Περιγραφή
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the node asks its GPS for a fix
Broadcast Interval How often the position is shared with the mesh
Smart Position Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Fixed Position Use a manually entered latitude, longitude and altitude instead of the GPS
Position Flags A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Power Config

On Settings → Device configuration → Power.

Setting Περιγραφή
Enable power saving mode Let the node sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the node stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC multiplier override ratio The correction factor itself, used only when the override is on
Battery INA_2XX I2C address Address of an external INA-series power sensor, if fitted

Network Config

On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node.

Setting Περιγραφή
Wi-Fi enabled Enable the Wi-Fi node (ESP32 nodes)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Κωδικός πρόσβασης Network password
Ethernet enabled Use a wired connection on hardware that has one
IPv4 mode DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP server Time synchronization server
rsyslog server Remote logging server

Network Config with a static IPv4 address entered

Ρυθμίσεις Bluetooth

On Settings → Device configuration → Bluetooth, on nodes with Bluetooth.

Setting Περιγραφή
Bluetooth enabled Enable/disable BLE radio
Pairing mode Fixed PIN, Random PIN, or No PIN
Fixed PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Security Config

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

Setting Περιγραφή
Δημόσιο Κλειδί Your node’s public key (read-only)
Admin Key Keys permitted to administer this node remotely — up to three
Ιδιωτικό Κλειδί Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it
Regenerate Private Key Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Serial console Serial console over the Stream API
Debug log API enabled Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth
Managed Mode Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.

diff --git a/main/es-rES/user/discovery.html b/main/es-rES/user/discovery.html index f9af55a7fa..1438d4acdd 100644 --- a/main/es-rES/user/discovery.html +++ b/main/es-rES/user/discovery.html @@ -5,4 +5,4 @@ ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) -

Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:.

What to look for What it means
All hops show Good SNR (green) Healthy path — messages flow reliably
One hop shows a poor SNR (orange or red) Weak link — this relay segment is fragile
Many hops (4+) Long path — consider repositioning a node to shorten it
Different path on retry Mesh is adapting — multiple routes exist (this is good!)

💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network.

Troubleshooting with Traceroute

  • No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key.
  • Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa.
  • Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position.
  • Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric.

Información de Vecinos

The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh.

Enabling Neighbor Info

  1. Navigate to Settings → Module configuration → Neighbor Info.
  2. Enable the module.
  3. Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
  4. Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air.

Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.

Viewing neighbor data

  • Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors.
  • Each neighbor entry shows the node that was directly heard and its signal quality.
  • Combine neighbor data from multiple nodes to understand the full mesh topology.

ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further.

Node list as a discovery tool

The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively.

Finding new nodes

  • Sort by Last heard to see the most recently active nodes at the top.
  • Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes.

Assessing connectivity

  • Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed.
  • Sort by Distance to find nearby nodes and verify they’re reachable.
  • Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge).

Infrastructure audit

  • Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes.
  • Check their signal quality and last-heard times to verify your infrastructure nodes are healthy.

See Nodes for full details on filtering and sorting options.

Tips for Mesh exploration

  • Start with traceroute — it gives you immediate, actionable information about a specific path.
  • Enable Neighbor Info on key nodes — especially routers and repeaters, to build a picture of the backbone.
  • Check the map — node positions on the Map combined with signal data help you understand why some links are strong and others are weak.
  • Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly.
+

Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:.

What to look for What it means
All hops show Good SNR (green) Healthy path — messages flow reliably
One hop shows a poor SNR (orange or red) Weak link — this relay segment is fragile
Many hops (4+) Long path — consider repositioning a node to shorten it
Different path on retry Mesh is adapting — multiple routes exist (this is good!)

💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network.

Troubleshooting with Traceroute

  • No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key.
  • Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa.
  • Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position.
  • Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric.

Información de Vecinos

The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh.

Enabling Neighbor Info

  1. Navigate to Settings → Module configuration → Neighbor Info.
  2. Enable the module.
  3. Set Update Interval. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
  4. Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air.

Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.

Viewing neighbor data

  • Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors.
  • Each neighbor entry shows the node that was directly heard and its signal quality.
  • Combine neighbor data from multiple nodes to understand the full mesh topology.

ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further.

Node list as a discovery tool

The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively.

Finding new nodes

  • Sort by Last heard to see the most recently active nodes at the top.
  • Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes.

Assessing connectivity

  • Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed.
  • Sort by Distance to find nearby nodes and verify they’re reachable.
  • Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge).

Infrastructure audit

  • Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes.
  • Check their signal quality and last-heard times to verify your infrastructure nodes are healthy.

See Nodes for full details on filtering and sorting options.

Tips for Mesh exploration

  • Start with traceroute — it gives you immediate, actionable information about a specific path.
  • Enable Neighbor Info on key nodes — especially routers and repeaters, to build a picture of the backbone.
  • Check the map — node positions on the Map combined with signal data help you understand why some links are strong and others are weak.
  • Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly.
diff --git a/main/es-rES/user/mqtt.html b/main/es-rES/user/mqtt.html index 54e082dc2a..a2af43d72b 100644 --- a/main/es-rES/user/mqtt.html +++ b/main/es-rES/user/mqtt.html @@ -1,2 +1,2 @@ MQTT | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Español
Meshtastic Docs ↗

🌐 Español — Community translation View in English

MQTT

MQTT bridges your Meshtastic mesh network to the internet, enabling long-range communication beyond radio range.

Visión general

The MQTT module connects your node to an MQTT broker, allowing:

  • Messages to reach nodes on different physical meshes via the internet
  • Integration with home automation and monitoring systems
  • Publishing node positions to the public Meshtastic map
  • Custom data pipelines for logging and alerting

How It Works 

[Your Node] → Radio → [Gateway Node with Wi-Fi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node]
-

A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh.

Configuración

Enabling MQTT

  1. Navigate to Settings → Module configuration → MQTT.
  2. Enable the MQTT module.
  3. Configure the broker connection:
Setting Descripción Por defecto
Address MQTT broker hostname mqtt.meshtastic.org
Username Broker authentication meshdev
Password Broker authentication large4cats
Root topic Base topic for messages msh, which the radio rewrites to msh/<REGION> once you set a region
Encryption enabled Encrypt MQTT payload Habilitado
JSON output enabled Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it Disabled
TLS enabled Secure connection to broker Disabled
Map reporting Report position to public map Disabled
Proxy to client enabled Relay MQTT through the connected phone Disabled

Connection Status and Test Connection

The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here.

Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason.

MQTT Proxy on This Phone

If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection.

ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them.

The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration.

Default Meshtastic Broker

The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing.

When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without).

🔒 Privacy: Messages on the public broker are readable by anyone subscribed. Always use channel encryption for private communications.

Private Broker

For better privacy and control, you can run your own MQTT broker:

  • Mosquitto (lightweight, open-source)
  • HiveMQ
  • EMQX

Configure your node to point to your private broker with appropriate credentials.

Map Reporting

When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.

Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.

Reports appear at meshmap.net and similar community map services.

🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published.

Direction Descripción
Uplink Messages from mesh → MQTT broker
Downlink Messages from MQTT broker → mesh

Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on.

Message Formats

MQTT carries two payload formats:

Format Descripción Use case
Protobuf Binary Meshtastic protobuf encoding Node-to-node mesh bridging
JSON Human-readable JSON on the /2/json/ topic Consumers outside the mesh (dashboards, home automation)

ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads.

Encryption & Privacy

Understanding the layered encryption model:

  1. Channel encryption happens on the mesh before MQTT. If your channel has a PSK, the MQTT payload is already encrypted — the broker and any subscribers see only the ciphertext.
  2. Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard.
  3. TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping.

🔒 Security: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications.

Best Practices

  • Use channel-level encryption (PSK) on channels that bridge to MQTT
  • Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes memory)
  • Use a private broker for sensitive deployments
  • Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh
  • Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back

Troubleshooting

MQTT Not Connecting

  • Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself.
  • Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces.
  • Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443).
  • DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly.

Messages Not Bridging

  • Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway.
  • Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage.
  • Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root.
  • Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway.
  • Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in.
+

A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh.

Configuración

Enabling MQTT

  1. Navigate to Settings → Module configuration → MQTT.
  2. Enable the MQTT module.
  3. Configure the broker connection:
Setting Descripción Por defecto
Address MQTT broker hostname mqtt.meshtastic.org
Username Broker authentication meshdev
Password Broker authentication large4cats
Root topic Base topic for messages msh, which the radio rewrites to msh/<REGION> once you set a region
Encryption enabled Encrypt MQTT payload Habilitado
JSON output enabled Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it Disabled
TLS enabled Secure connection to broker Disabled
Map reporting Report position to public map Disabled
Proxy to client enabled Relay MQTT through the connected phone Disabled

Connection Status and Test Connection

The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here.

Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason.

MQTT Proxy on This Phone

If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection.

ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them.

The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration.

Default Meshtastic Broker

The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing.

When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without).

🔒 Privacy: Messages on the public broker are readable by anyone subscribed. Always use channel encryption for private communications.

Private Broker

For better privacy and control, you can run your own MQTT broker:

  • Mosquitto (lightweight, open-source)
  • HiveMQ
  • EMQX

Configure your node to point to your private broker with appropriate credentials.

Map Reporting

When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.

Turning it on opens a consent card. Turn on I agree. and choose a Map Publish Interval of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.

Reports appear at meshmap.net and similar community map services.

🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published.

Direction Descripción
Uplink Messages from mesh → MQTT broker
Downlink Messages from MQTT broker → mesh

Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on.

Message Formats

MQTT carries two payload formats:

Format Descripción Use case
Protobuf Binary Meshtastic protobuf encoding Node-to-node mesh bridging
JSON Human-readable JSON on the /2/json/ topic Consumers outside the mesh (dashboards, home automation)

ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads.

Encryption & Privacy

Understanding the layered encryption model:

  1. Channel encryption happens on the mesh before MQTT. If your channel has a PSK, the MQTT payload is already encrypted — the broker and any subscribers see only the ciphertext.
  2. Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard.
  3. TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping.

🔒 Security: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications.

Best Practices

  • Use channel-level encryption (PSK) on channels that bridge to MQTT
  • Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes memory)
  • Use a private broker for sensitive deployments
  • Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh
  • Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back

Troubleshooting

MQTT Not Connecting

  • Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself.
  • Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces.
  • Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443).
  • DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly.

Messages Not Bridging

  • Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway.
  • Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage.
  • Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root.
  • Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway.
  • Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in.
diff --git a/main/es-rES/user/settings-module-admin.html b/main/es-rES/user/settings-module-admin.html index 93578ba68d..4eed8b1df9 100644 --- a/main/es-rES/user/settings-module-admin.html +++ b/main/es-rES/user/settings-module-admin.html @@ -1 +1 @@ - Settings — Modules & Admin | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Español
Meshtastic Docs ↗

🌐 Español — Community translation View in English

Settings — Modules & Admin

Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.

💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.

Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:

A toggle setting in the on position

A dropdown setting, expanded to show its list of options

A text field setting with a value entered

A module settings card with its title and grouped controls

Configuración de módulo

Every module lives under Settings → Module configuration.

⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes.

MQTT module

Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.

Setting Descripción
Activar el MQTT Toggle MQTT bridge
Dirección del Servidor MQTT MQTT broker address
Usuario Authentication username
Contraseña Authentication password
Permitir Encripción Encrypt MQTT payloads
Salida JSON activada Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS activado Use secure connection
Tema raíz Base MQTT topic path
Compartir Internet a la Radio Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy on this phone The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT
Reportar Posición Publish position to the public map — see the Map reporting group that follows

Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:

Setting Descripción
Estoy de acuerdo. Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Tiempo entre Reportes de Posición (en Segundos) How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered

See MQTT for a detailed usage guide including encryption, privacy, and broker setup.

Serial module

Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.

Setting Descripción
Comunicación serial activada Activate serial communication
Eco activado Echo received serial data back
Modo serial Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX GPIO pins for the serial connection
Tasa de baudios por segundo Port speed
Tiempo agotado How long to wait before considering an incoming message complete
Sobreescribir el puerto serie de la consola Take over the port the debug console normally uses

External Notification module

Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.

There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.

Setting Descripción
Notificaciones externas activadas Master toggle for the module
Alert message LED / buzzer / vibra Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra Which outputs fire on a received bell character
Salida LED (pin GPIO) Pin the LED is wired to
LED de salida activo en alto Whether the LED pin is active high or low
Salida buzzer (pin GPIO) Pin the buzzer is wired to
Salida vibratoria (pin GPIO) Pin the vibration motor is wired to
Utilizar buzzer PWM Drive the buzzer with PWM, which allows tones rather than a single pitch
Utilizar el Buzzer como uno I2S Send the alert through an I2S audio output instead
Duración en las salidas (milisegundos) How long a single alert lasts
  Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Tono de notificación The tone played on a PWM buzzer, in RTTTL. Can be imported from a file

Store & Forward module

Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.

Setting Descripción
Descargar y reenviar activado Activate store and forward
Pulso de vida Periodically announce this node’s store-and-forward capability
Número de registros Maximum stored messages
Historial máximo devuelto Max messages to replay
History return window Time window for replay
Servidor Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)

💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.

Range Test module

⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.

Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.

Setting Descripción
Test de alcance activado Activate range testing
Periodo entre los mensajes del transmisor (segundos) Time between test transmissions, chosen from a dropdown of fixed intervals
Guardar el .CSV en el almacenamiento (Esp32) Log received test data to the node’s own filesystem. ESP32 hardware only

Telemetry module

Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).

Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.

Setting Descripción
Enviar telemetría del dispositivo Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Intervalo actualización de métricas del dispositivo How often to report battery, uptime and channel utilization
Módulo para las medidas del entorno activado Report the attached environment sensors
Intervalo actualización de métricas del entorno How often to report them
Mostrar las medidas del entorno en la Also show these readings on the device’s own display
Grados Fahrenheit para la temperatura ambiente Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Módulo para la medición de la calidad del aire activado Report particulate and CO₂ sensor data
Intervalo actualización de métricas calidad del aire How often to report them
Módulo de medidas eléctricas activado Report the per-channel voltage and current readings
Intervalo de actualización de métricas de energía How often to report them
Medidas eléctricas en pantalla Also show power readings on the device’s display

See Telemetry & Sensors for supported sensors and configuration recommendations.

Canned Message module

Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.

Setting Descripción
Canned message enabled ⚠️ Deprecated in the protobuf schema
Mensajes Newline-separated list of messages
Mandar campana 🔔 Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Encoder Número 1 Activado Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port The three pins the encoder is wired to
Generate input event on Press / CW / CCW Which key event each encoder action produces
Arriba/Abajo/Seleccionar Activado A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source ⚠️ Deprecated in the protobuf schema

Audio module

Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.

Setting Descripción
CODEC 2 activado Activate audio module
Frecuencia de Muestreo CODEC2 Audio quality/bandwidth tradeoff
Pin PTT GPIO pin for the push-to-talk button
Selecionar palabras I2S GPIO pin for I2S WS
Entrada de datos I2S GPIO pin for I2S DIN
Salida de datos I2S GPIO pin for I2S DOUT
Reloj del I2S GPIO pin for the I2S bit clock

ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.

Remote Hardware module

GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.

⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.

Setting Descripción
Hardware remoto activado Activate remote GPIO access
Permitir el acceso sin un pin definido Allow access to any GPIO pin (security risk)
Pines disponibles Up to 4 GPIO pins this node exposes for remote read/write

Neighbor Info module

Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.

Setting Descripción
Información de Vecinos Activate neighbor broadcasting
Intervalo de refresco (segundos) How often to broadcast neighbor list
Transmitir en LoRa Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name

See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.

Ambient Lighting module

Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.

Setting Descripción
Estado de led Turn the LED on or off
Intensidad LED current limit (0–31)
Red / Green / Blue Individual color channel values (0–255)

Detection Sensor module

Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.

Setting Descripción
Sensor detector activado Activate detection sensor
Pin GPIO para monitorizar GPIO pin connected to sensor
Tipo de detección para activar How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Utilizar el modo de entrada PULL_UP Enable the pin’s internal pull-up resistor
Tiempo mínimo de transmisión (segundos) Minimum time between alert broadcasts
Periodo entre transmisión de estado (segundos) Periodic state broadcast interval
Mandar la campana con el mensaje de alerta Include bell character in alerts
Mote Custom name for this sensor

Paxcounter module

People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.

Setting Descripción
Activar el Contador de Paquetes Activate people counting
Intervalo de refresco (segundos) How often to report counts
Wi-Fi RSSI threshold Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE RSSI threshold The same cut-off for BLE advertisements (defaults to −80 dBm)

💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.

Status Message module

The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.

Mesh Beacon module

Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.

TAK module

Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.

Administración

Administración remota

Remotely configure nodes that share your admin key:

  1. Select the target node in the node list.
  2. Navigate to Settings for that node.
  3. Modify configuration.
  4. Tap Save — changes are sent over the mesh.

⚠️ Important: Requires an admin key configured on both your node and the target node.

Device Actions

Settings → Administration holds five one-shot actions, each behind a confirmation dialog:

Action What it does
Set time Sends your phone’s clock to the node
Reiniciar Restarts the node
Apagar Powers the node down
Restablecer los valores de fábrica Returns every setting to its factory default
Reinicio de NodeDB Clears the node database. This dialog carries a Preserve Favorites? switch

⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.

Hacer copia de seguridad y restaurar

Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.

Avanzado

Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.

Limpiar nodos de la base de datos

Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.

  • Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
  • Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.

The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.

Panel de depuración

Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.

App Settings

The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:

Privacy

  • Allow analytics and crash reporting — opt in or out of diagnostics.
  • Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
  • Homoglyph encoding — how look-alike characters in names are handled.

Appearance

  • Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
  • Theme and Language.
  • Show full message timestamps.

Persistence

  • A cache limit for how much history is kept.
  • Export rangetest packets, Export all packets and Export node database.

On their own

  • Node Layout — how much detail each row of the node list shows.
  • Wi-Fi Provisioning for mPWRD-OS — see Connections.
  • Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
  • System AI — appears only where app functions are available; see App Functions.

A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.

Acerca de

Settings → About carries the app’s own identity rather than the node’s:

Three sections:

  • What is Meshtastic? — a short description of the project.
  • Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
  • Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.

The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.

Agradecimientos

Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.

Troubleshooting remote admin

  • “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
  • Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
  • Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
+ Settings — Modules & Admin | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Español
Meshtastic Docs ↗

🌐 Español — Community translation View in English

Settings — Modules & Admin

Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.

💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.

Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:

A toggle setting in the on position

A dropdown setting, expanded to show its list of options

A text field setting with a value entered

A module settings card with its title and grouped controls

Configuración de módulo

Every module lives under Settings → Module configuration.

⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes.

MQTT module

Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.

Setting Descripción
Activar el MQTT Toggle MQTT bridge
Dirección del Servidor MQTT MQTT broker address
Usuario Authentication username
Contraseña Authentication password
Permitir Encripción Encrypt MQTT payloads
Salida JSON activada Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS activado Use secure connection
Tema raíz Base MQTT topic path
Compartir Internet a la Radio Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy on this phone The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT
Reportar Posición Publish position to the public map — see the Map reporting group that follows

Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:

Setting Descripción
Estoy de acuerdo. Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered

See MQTT for a detailed usage guide including encryption, privacy, and broker setup.

Serial module

Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.

Setting Descripción
Comunicación serial activada Activate serial communication
Eco activado Echo received serial data back
Modo serial Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX GPIO pins for the serial connection
Tasa de baudios por segundo Port speed
Tiempo agotado How long to wait before considering an incoming message complete
Sobreescribir el puerto serie de la consola Take over the port the debug console normally uses

External Notification module

Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.

There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.

Setting Descripción
Notificaciones externas activadas Master toggle for the module
Alert message LED / buzzer / vibra Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra Which outputs fire on a received bell character
Salida LED (pin GPIO) Pin the LED is wired to
LED de salida activo en alto Whether the LED pin is active high or low
Salida buzzer (pin GPIO) Pin the buzzer is wired to
Salida vibratoria (pin GPIO) Pin the vibration motor is wired to
Utilizar buzzer PWM Drive the buzzer with PWM, which allows tones rather than a single pitch
Utilizar el Buzzer como uno I2S Send the alert through an I2S audio output instead
GPIO Output Duration How long a single alert lasts
Nag Timeout Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Tono de notificación The tone played on a PWM buzzer, in RTTTL. Can be imported from a file

Store & Forward module

Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.

Setting Descripción
Descargar y reenviar activado Activate store and forward
Pulso de vida Periodically announce this node’s store-and-forward capability
Número de registros Maximum stored messages
Historial máximo devuelto Max messages to replay
History return window Time window for replay
Servidor Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)

💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.

Range Test module

⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.

Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.

Setting Descripción
Test de alcance activado Activate range testing
Sender Interval Time between test transmissions, chosen from a dropdown of fixed intervals
Guardar el .CSV en el almacenamiento (Esp32) Log received test data to the node’s own filesystem. ESP32 hardware only

Telemetry module

Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).

Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.

Setting Descripción
Enviar telemetría del dispositivo Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Intervalo actualización de métricas del dispositivo How often to report battery, uptime and channel utilization
Módulo para las medidas del entorno activado Report the attached environment sensors
Intervalo actualización de métricas del entorno How often to report them
Mostrar las medidas del entorno en la Also show these readings on the device’s own display
Grados Fahrenheit para la temperatura ambiente Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Módulo para la medición de la calidad del aire activado Report particulate and CO₂ sensor data
Intervalo actualización de métricas calidad del aire How often to report them
Módulo de medidas eléctricas activado Report the per-channel voltage and current readings
Intervalo de actualización de métricas de energía How often to report them
Medidas eléctricas en pantalla Also show power readings on the device’s display

See Telemetry & Sensors for supported sensors and configuration recommendations.

Canned Message module

Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.

Setting Descripción
Canned message enabled ⚠️ Deprecated in the protobuf schema
Mensajes Newline-separated list of messages
Mandar campana 🔔 Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Encoder Número 1 Activado Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port The three pins the encoder is wired to
Generate input event on Press / CW / CCW Which key event each encoder action produces
Arriba/Abajo/Seleccionar Activado A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source ⚠️ Deprecated in the protobuf schema

Audio module

Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.

Setting Descripción
CODEC 2 activado Activate audio module
Frecuencia de Muestreo CODEC2 Audio quality/bandwidth tradeoff
Pin PTT GPIO pin for the push-to-talk button
Selecionar palabras I2S GPIO pin for I2S WS
Entrada de datos I2S GPIO pin for I2S DIN
Salida de datos I2S GPIO pin for I2S DOUT
Reloj del I2S GPIO pin for the I2S bit clock

ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.

Remote Hardware module

GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.

⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.

Setting Descripción
Hardware remoto activado Activate remote GPIO access
Permitir el acceso sin un pin definido Allow access to any GPIO pin (security risk)
Pines disponibles Up to 4 GPIO pins this node exposes for remote read/write

Neighbor Info module

Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.

Setting Descripción
Información de Vecinos Activate neighbor broadcasting
Intervalo de actualización How often to broadcast neighbor list
Transmitir en LoRa Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name

See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.

Ambient Lighting module

Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.

Setting Descripción
Estado de led Turn the LED on or off
Intensidad LED current limit (0–31)
Red / Green / Blue Individual color channel values (0–255)

Detection Sensor module

Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.

Setting Descripción
Sensor detector activado Activate detection sensor
Pin GPIO para monitorizar GPIO pin connected to sensor
Tipo de detección para activar How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Utilizar el modo de entrada PULL_UP Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts Minimum time between alert broadcasts
State Broadcast Interval Periodic state broadcast interval
Mandar la campana con el mensaje de alerta Include bell character in alerts
Mote Custom name for this sensor

Paxcounter module

People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.

Setting Descripción
Activar el Contador de Paquetes Activate people counting
Intervalo de actualización How often to report counts
WiFi Threshold (dBm) Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm) The same cut-off for BLE advertisements (defaults to −80 dBm)

💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.

Status Message module

The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.

Mesh Beacon module

Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.

TAK module

Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.

Administración

Administración remota

Remotely configure nodes that share your admin key:

  1. Select the target node in the node list.
  2. Navigate to Settings for that node.
  3. Modify configuration.
  4. Tap Save — changes are sent over the mesh.

⚠️ Important: Requires an admin key configured on both your node and the target node.

Device Actions

Settings → Administration holds five one-shot actions, each behind a confirmation dialog:

Action What it does
Set time Sends your phone’s clock to the node
Reiniciar Restarts the node
Apagar Powers the node down
Restablecer los valores de fábrica Returns every setting to its factory default
Reinicio de NodeDB Clears the node database. This dialog carries a Preserve Favorites? switch

⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.

Hacer copia de seguridad y restaurar

Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.

Avanzado

Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.

Limpiar nodos de la base de datos

Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.

  • Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
  • Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.

The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.

Panel de depuración

Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.

App Settings

The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:

Privacy

  • Allow analytics and crash reporting — opt in or out of diagnostics.
  • Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
  • Homoglyph encoding — how look-alike characters in names are handled.

Appearance

  • Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
  • Theme and Language.
  • Show full message timestamps.

Persistence

  • A cache limit for how much history is kept.
  • Export rangetest packets, Export all packets and Export node database.

On their own

  • Node Layout — how much detail each row of the node list shows.
  • Wi-Fi Provisioning for mPWRD-OS — see Connections.
  • Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
  • System AI — appears only where app functions are available; see App Functions.

A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.

Acerca de

Settings → About carries the app’s own identity rather than the node’s:

Three sections:

  • What is Meshtastic? — a short description of the project.
  • Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
  • Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.

The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.

Agradecimientos

Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.

Troubleshooting remote admin

  • “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
  • Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
  • Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
diff --git a/main/es-rES/user/settings-radio-user.html b/main/es-rES/user/settings-radio-user.html index 04d310c56c..3dd29151c0 100644 --- a/main/es-rES/user/settings-radio-user.html +++ b/main/es-rES/user/settings-radio-user.html @@ -1 +1 @@ - Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Español
Meshtastic Docs ↗

🌐 Español — Community translation View in English

Settings — Radio & User

Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How these screens work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Descripción
Nombre largo Your display name (up to 39 characters)
Nombre Corto 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
No se puede enviar mensajes Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur node (Ham) Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in.

Configuración

Configuración del dispositivo

On Settings → Device configuration → Device.

Setting Descripción Por defecto
Rol del dispositivo Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Modo de retransmisión How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Intervalo de transmisión de información del nodo How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Doble pulsación como botón Treat a double tap as a button press Disabled
Triple pulsación para enviar un ping Send an ad-hoc position ping on a triple click Habilitado
Latido LED Blink the status LED periodically Habilitado
Zona horaria POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it —
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to —

Configuración LoRa

On Settings → LoRa.

Setting Descripción Por defecto
Región Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number Unset (must configure)
Predefinidos Speed/range tradeoff LongFast
Número de saltos Maximum retransmit hops 3
Potencia de transmisión Transmission power (dBm); 0 = max allowed for region 0 (region max)
Sobreescribir frecuencia Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Usar predefinido On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Factor de dispersión Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead From preset
Ratio de Codificación Manual mode only: 5–8. More redundancy costs airtime From preset
Ancho de banda Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Banda de Frecuencia Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmisión habilitada Turning this off makes the node receive-only On
Sobreescribir el Tiempo de Trabajo Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
Ignorar Paquetes MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Permitir MQTT Allow your packets to be forwarded to MQTT by gateways Off
Aumentar ganancia de RX Extra receive gain on SX126x radios; costs a little current Off
Ventilador del Amplificador apagado Turn off the power-amplifier fan on hardware that has one Off

The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set.

Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Velocidad SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a modem preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Configuración de pantalla

On Settings → Device configuration → Display. These control the node’s own screen, not the app’s.

Setting Descripción
Pantalla activa durante How long the display stays lit before sleeping
Intervalo de carrusel How often the node cycles between screens on its own
Modo de la pantalla Screen layout/density used by the firmware
Unidades en pantalla Metric or Imperial on the node’s screen
Utilizar el formato de 12h para el reloj Show the node’s clock as 12-hour rather than 24-hour
Encabezado en negrita Draw the screen’s heading text in bold
Girar la pantalla 180º Rotate the display 180° for an inverted mounting
Tipo de OLED Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED
Despertar al tocar o al mover Light the screen when the node is tapped or moved
Orientación de la brújula Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each
Siempre apuntar al norte Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Configuración de la posición

On Settings → Device configuration → Position.

Setting Descripción
Modo GPS (dispositivo físico) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the node asks its GPS for a fix
Intervalo de Difusión How often the position is shared with the mesh
Ubicación inteligente Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Posición fija Use a manually entered latitude, longitude and altitude instead of the GPS
Marcas de posición A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Configuración de elecenergía

On Settings → Device configuration → Power.

Setting Descripción
Activar el modo ahorro de energía Let the node sleep aggressively between activity
Apagar al perder energía Power the device down after external power disappears
Duración del sueño súper profundo How long the deepest sleep state lasts
Minimum wake time The shortest time the node stays awake once woken
Esperar Bluetooth durante How long to wait for a phone to connect before sleeping
Sobreescribir multiplicador ADC Turn on a manual correction for battery-voltage readings
Sobreescribir relación del multiplicador ADC The correction factor itself, used only when the override is on
Dirección I2C del INA_2xx para la batería Address of an external INA-series power sensor, if fitted

Configuración de la red

On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node.

Setting Descripción
Wi-Fi enabled Enable the Wi-Fi node (ESP32 nodes)
SSID (Nombre la Red) Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Contraseña Contraseña de red
Ethernet del Nodo Activado Use a wired connection on hardware that has one
Modo IPv4 DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
Servidor NTP Time synchronization server
Servidor rsyslog Remote logging server

Network Config with a static IPv4 address entered

Configuración Bluetooth

On Settings → Device configuration → Bluetooth, on nodes with Bluetooth.

Setting Descripción
Bluetooth activado Enable/disable BLE radio
Modo de emparejamiento Fixed PIN, Random PIN, or No PIN
Pin fijo PIN code for pairing. Must be exactly six digits — the field rejects anything else

Configuración de la seguridad

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

Setting Descripción
Clave Pública Your node’s public key (read-only)
Contraseña de administrador Keys permitted to administer this node remotely — up to three
Clave privada Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it
Regenerar clave privada Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Consola serial Serial console over the Stream API
API de registro de depuración habilitada Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth
Modo “ya terminado de configurar” Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.

+ Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Español
Meshtastic Docs ↗

🌐 Español — Community translation View in English

Settings — Radio & User

Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How these screens work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Descripción
Nombre largo Your display name (up to 39 characters)
Nombre Corto 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
No se puede enviar mensajes Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur node (Ham) Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in.

Configuración

Configuración del dispositivo

On Settings → Device configuration → Device.

Setting Descripción Por defecto
Rol del dispositivo Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Modo de retransmisión How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Intervalo de transmisión de información del nodo How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Doble pulsación como botón Treat a double tap as a button press Disabled
Triple pulsación para enviar un ping Send an ad-hoc position ping on a triple click Habilitado
Latido LED Blink the status LED periodically Habilitado
Zona horaria POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it —
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to —

Configuración LoRa

On Settings → LoRa.

Setting Descripción Por defecto
Región Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number Unset (must configure)
Predefinidos Speed/range tradeoff LongFast
Número de saltos Maximum retransmit hops 3
Transmit Power (dBm) Transmission power; 0 = max allowed for region 0 (region max)
Sobreescribir frecuencia Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Usar predefinido On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Factor de dispersión Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead From preset
Ratio de Codificación Manual mode only: 5–8. More redundancy costs airtime From preset
Ancho de banda Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Banda de Frecuencia Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmisión habilitada Turning this off makes the node receive-only On
Sobreescribir el Tiempo de Trabajo Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
Ignorar Paquetes MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Permitir MQTT Allow your packets to be forwarded to MQTT by gateways Off
Aumentar ganancia de RX Extra receive gain on SX126x radios; costs a little current Off
Ventilador del Amplificador apagado Turn off the power-amplifier fan on hardware that has one Off

The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set.

Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Velocidad SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a modem preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Configuración de pantalla

On Settings → Device configuration → Display. These control the node’s own screen, not the app’s.

Setting Descripción
Pantalla activa durante How long the display stays lit before sleeping
Intervalo de carrusel How often the node cycles between screens on its own
Modo de la pantalla Screen layout/density used by the firmware
Unidades en pantalla Metric or Imperial on the node’s screen
Utilizar el formato de 12h para el reloj Show the node’s clock as 12-hour rather than 24-hour
Encabezado en negrita Draw the screen’s heading text in bold
Girar la pantalla 180º Rotate the display 180° for an inverted mounting
Tipo de OLED Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED
Despertar al tocar o al mover Light the screen when the node is tapped or moved
Orientación de la brújula Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each
Siempre apuntar al norte Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Configuración de la posición

On Settings → Device configuration → Position.

Setting Descripción
Modo GPS (dispositivo físico) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the node asks its GPS for a fix
Intervalo de Difusión How often the position is shared with the mesh
Ubicación inteligente Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Posición fija Use a manually entered latitude, longitude and altitude instead of the GPS
Marcas de posición A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Configuración de elecenergía

On Settings → Device configuration → Power.

Setting Descripción
Activar el modo ahorro de energía Let the node sleep aggressively between activity
Apagar al perder energía Power the device down after external power disappears
Duración del sueño súper profundo How long the deepest sleep state lasts
Minimum wake time The shortest time the node stays awake once woken
Esperar Bluetooth durante How long to wait for a phone to connect before sleeping
Sobreescribir multiplicador ADC Turn on a manual correction for battery-voltage readings
Sobreescribir relación del multiplicador ADC The correction factor itself, used only when the override is on
Dirección I2C del INA_2xx para la batería Address of an external INA-series power sensor, if fitted

Configuración de la red

On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node.

Setting Descripción
Wi-Fi enabled Enable the Wi-Fi node (ESP32 nodes)
SSID (Nombre la Red) Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Contraseña Contraseña de red
Ethernet del Nodo Activado Use a wired connection on hardware that has one
Modo IPv4 DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
Servidor NTP Time synchronization server
Servidor rsyslog Remote logging server

Network Config with a static IPv4 address entered

Configuración Bluetooth

On Settings → Device configuration → Bluetooth, on nodes with Bluetooth.

Setting Descripción
Bluetooth activado Enable/disable BLE radio
Modo de emparejamiento Fixed PIN, Random PIN, or No PIN
Pin fijo PIN code for pairing. Must be exactly six digits — the field rejects anything else

Configuración de la seguridad

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

Setting Descripción
Clave Pública Your node’s public key (read-only)
Contraseña de administrador Keys permitted to administer this node remotely — up to three
Clave privada Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it
Regenerar clave privada Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Consola serial Serial console over the Stream API
API de registro de depuración habilitada Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth
Modo “ya terminado de configurar” Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.

diff --git a/main/et-rEE/user/discovery.html b/main/et-rEE/user/discovery.html index 94f2f37952..efb58af8ed 100644 --- a/main/et-rEE/user/discovery.html +++ b/main/et-rEE/user/discovery.html @@ -5,4 +5,4 @@ ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) -

Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:.

What to look for What it means
All hops show Good SNR (green) Healthy path — messages flow reliably
One hop shows a poor SNR (orange or red) Kehv ühendus – see releesegment on habras
Mitu hüppet (4+) Pikk tee – kaalu sõlme ümberpaigutamist selle lühendamiseks
Different path on retry Mesh is adapting — multiple routes exist (this is good!)

💡 Vihje: Käivita traceroute’i mitu korda mõne minuti tagant. If the path changes, your mesh has redundant routes — a sign of a well-connected network.

Veaotsing koos Traceroute

  • No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Kontrolli, et mõlemad sõlmed jagaksid vähemalt ühte kanalit sama krüpteerimisvõtmega.
  • Traceroute aegus — Tee võib olla liiga pikk (ületab hüppete limiidi) või on vahendussõlm ülekoormatud. Try increasing the hop limit in Settings → LoRa.
  • Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position.
  • Asümmeetrilised teed – Jälgimismarsruut teelt A→B võib minna teist teed kui teelt B→A. This is normal — radio propagation isn’t always symmetric.

Naabruse teave

Naabriinfo moodul võimaldab igal sõlmel levitada nimekirja sõlmedest, mida see otse kuuleb (üksik-hüpe). Kui mitu sõlme jagavad oma naaberloendeid, saate kokku panna kogu võrgu topoloogiakaardi.

Naabriinfo lubamine

  1. Navigate to Settings → Module configuration → Neighbor Info.
  2. Luba moodul.
  3. Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
  4. Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air.

Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Teised sõlmed, millel on naabriinfo lubatud, teevad sama.

Viewing neighbor data

  • Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors.
  • Iga naabri-kirje näitab otse kuuldud sõlme ja selle signaali kvaliteeti.
  • Kogu kärgvõrgu topoloogia mõistmiseks kombineerige mitme sõlme naaberandmeid.

ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further.

Node list as a discovery tool

Sõlmede loend ise on võimas avastusvahend, kui kasutada selle filtreerimis- ja sortimisfunktsioone tõhusalt.

Finding new nodes

  • Sorteeri Viimati kuuldud järgi, et näha kõige hiljutisemaid aktiivseid sõlmi ülaosas.
  • Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes.

Assessing connectivity

  • Sorteeri Hüpete arvu järgi, et näha, millised sõlmed on otse kättesaadavad (0 hüpet) ja millised vahendatavate sõlmedega.
  • Sort by Distance to find nearby nodes and verify they’re reachable.
  • Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge).

Infrastructure audit

  • Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes.
  • Kontrolli nende signaali kvaliteeti ja viimase kuulmise aegu, et veenduda oma infrastruktuuri sõlmede töökorras olekus.

Filtreerimis- ja sortimisvalikute kohta leiate lisateavet jaotisest Nodes.

Tips for Mesh exploration

  • Alusta traceroute’ist — see annab sulle kohest ja praktilist teavet konkreetse tee kohta.
  • Luba naabriinfo funktsioon võtmesõlmedes – eriti ruuterites ja repiiterites, et saada ülevaade magistraalvõrgust.
  • Kontrolli kaarti — sõlmede asukohad [Kaart] (map-and-waypoints) koos signaaliandmetega aitavad sul mõista, miks mõned ühendused on tugevad ja teised nõrgad.
  • Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly.

Seotud teemad

+

Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:.

What to look for What it means
All hops show Good SNR (green) Healthy path — messages flow reliably
One hop shows a poor SNR (orange or red) Kehv ühendus – see releesegment on habras
Mitu hüppet (4+) Pikk tee – kaalu sõlme ümberpaigutamist selle lühendamiseks
Different path on retry Mesh is adapting — multiple routes exist (this is good!)

💡 Vihje: Käivita traceroute’i mitu korda mõne minuti tagant. If the path changes, your mesh has redundant routes — a sign of a well-connected network.

Veaotsing koos Traceroute

  • No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Kontrolli, et mõlemad sõlmed jagaksid vähemalt ühte kanalit sama krüpteerimisvõtmega.
  • Traceroute aegus — Tee võib olla liiga pikk (ületab hüppete limiidi) või on vahendussõlm ülekoormatud. Try increasing the hop limit in Settings → LoRa.
  • Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position.
  • Asümmeetrilised teed – Jälgimismarsruut teelt A→B võib minna teist teed kui teelt B→A. This is normal — radio propagation isn’t always symmetric.

Naabruse teave

Naabriinfo moodul võimaldab igal sõlmel levitada nimekirja sõlmedest, mida see otse kuuleb (üksik-hüpe). Kui mitu sõlme jagavad oma naaberloendeid, saate kokku panna kogu võrgu topoloogiakaardi.

Naabriinfo lubamine

  1. Navigate to Settings → Module configuration → Neighbor Info.
  2. Luba moodul.
  3. Set Update Interval. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
  4. Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air.

Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Teised sõlmed, millel on naabriinfo lubatud, teevad sama.

Viewing neighbor data

  • Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors.
  • Iga naabri-kirje näitab otse kuuldud sõlme ja selle signaali kvaliteeti.
  • Kogu kärgvõrgu topoloogia mõistmiseks kombineerige mitme sõlme naaberandmeid.

ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further.

Node list as a discovery tool

Sõlmede loend ise on võimas avastusvahend, kui kasutada selle filtreerimis- ja sortimisfunktsioone tõhusalt.

Finding new nodes

  • Sorteeri Viimati kuuldud järgi, et näha kõige hiljutisemaid aktiivseid sõlmi ülaosas.
  • Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes.

Assessing connectivity

  • Sorteeri Hüpete arvu järgi, et näha, millised sõlmed on otse kättesaadavad (0 hüpet) ja millised vahendatavate sõlmedega.
  • Sort by Distance to find nearby nodes and verify they’re reachable.
  • Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge).

Infrastructure audit

  • Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes.
  • Kontrolli nende signaali kvaliteeti ja viimase kuulmise aegu, et veenduda oma infrastruktuuri sõlmede töökorras olekus.

Filtreerimis- ja sortimisvalikute kohta leiate lisateavet jaotisest Nodes.

Tips for Mesh exploration

  • Alusta traceroute’ist — see annab sulle kohest ja praktilist teavet konkreetse tee kohta.
  • Luba naabriinfo funktsioon võtmesõlmedes – eriti ruuterites ja repiiterites, et saada ülevaade magistraalvõrgust.
  • Kontrolli kaarti — sõlmede asukohad [Kaart] (map-and-waypoints) koos signaaliandmetega aitavad sul mõista, miks mõned ühendused on tugevad ja teised nõrgad.
  • Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly.

Seotud teemad

diff --git a/main/et-rEE/user/mqtt.html b/main/et-rEE/user/mqtt.html index 533e5b0467..49517ef644 100644 --- a/main/et-rEE/user/mqtt.html +++ b/main/et-rEE/user/mqtt.html @@ -1,2 +1,2 @@ MQTT | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Eesti
Meshtastic Docs ↗

🌐 Eesti — Community translation View in English

MQTT

MQTT ühendab Meshtastic võrgu internetiga, võimaldades raadiolevi ulatusest kaugemale ulatuvat pikamaasidet.

Ülevaade

MQTT moodul ühendab sinu sõlme MQTT vahendajaga, võimaldades:

  • Sõnumid interneti kaudu erinevate füüsiliste võrkude sõlmedeni jõudmiseks
  • Integration with home automation and monitoring systems
  • Sõlmede asukoha avaldamine avalikul Meshtastic kaardil
  • Custom data pipelines for logging and alerting

Kuidas see toimib 

[Your Node] → Radio → [Gateway Node with Wi-Fi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node]
-

A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Sama teemaga liitunud kauglüüsid sisestavad need sõnumid oma kohalikku kärgvõrku.

Sätted

Luba MQTT

  1. Navigate to Settings → Module configuration → MQTT.
  2. Luba MQTT moodul.
  3. Configure the broker connection:
Sätted Kirjeldus Vaikimisi
Address MQTT vahendaja hostinimi mqtt.meshtastic.org
Username Broker authentication meshdev
Password Broker authentication large4cats
Root topic Base topic for messages msh, which the radio rewrites to msh/<REGION> once you set a region
Encryption enabled Krüpteeri MQTT liiklus Lubatud
JSON output enabled Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it Keelatud
TLS enabled Secure connection to broker Keelatud
Map reporting Teavita asukoht avalikul kaardil Keelatud
Proxy to client enabled Relay MQTT through the connected phone Keelatud

Connection Status and Test Connection

The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here.

Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason.

MQTT puhverserver sellel telefonil

If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection.

ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them.

The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration.

Meshtastic vaikemaakler

Kogukond haldab avaliku vahendajat aadressil mqtt.meshtastic.org. This is intended for general use and testing.

When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without).

🔒 Privaatsus: Avaliku vahendaja sõnumeid saavad lugeda kõik tellijad. Privaatse suhtluse jaoks kasuta alati kanali krüpteerimist.

Private Broker

Parema privaatsuse ja kontrolli tagamiseks saad hallata oma MQTT maaklerit:

  • Mosquitto (kerge, avatud lähtekoodiga)
  • HiveMQ
  • EMQX

Konfigureeri oma sõlm nii, et see osutaks sinu privaatsele maaklerile sobivate volitustega.

Kaardiaruannete koostamine

When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.

Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.

Reports appear at meshmap.net and similar community map services.

🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published.

Suund Kirjeldus
Üleslink Sõnumid kärgvõrgust → MQTT maakler
Allalink Sõnumid MQTT maaklerist → kärgvõrk

Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on.

Sõnumivormingud

MQTT carries two payload formats:

Vorming Kirjeldus Kasutusjuhtum
Protobuf Binaarne Meshtastic protobuf kodeering Node-to-node mesh bridging
JSON Human-readable JSON on the /2/json/ topic Consumers outside the mesh (dashboards, home automation)

ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads.

Encryption & Privacy

Understanding the layered encryption model:

  1. Kanali krüptimine toimub kärgvõrgus enne MQTT. Kui kanalil on PSK, on ​​MQTT liiklus juba krüptitud – maakler ja kõik tellijad näevad ainult šifriteksti.
  2. Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard.
  3. TLS krüpteerib TCP ühenduse vahendaja endaga, takistades võrgutasandil pealtkuulamist.

🔒 Security: The default public channel has a well-known key. MQTT kaudu saadetud vaikekanalil olevad sõnumid on sisuliselt krüpteerimata – igaüks saab neid dekodeerida. Always use a custom PSK for private communications.

Parimad tavad

  • Kasuta kanali krüptimist (PSK), kanalitel mis on sillatud MQTT-ga
  • Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes memory)
  • Use a private broker for sensitive deployments
  • MQTT sõnumite allalaadimisel arvesta eetriaja kuluga – iga allalingitud sõnum tarbib sinu kohalikus võrgus raadioeetriaega
  • Kaalu ainult üleslingi lubamist, kui sul on vaja oma kärgvõrku eemalt jälgida ilma sõnumeid tagasi tõmbamata

Veaotsing

MQTT ei ühendu

  • Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT ei tööta LoRa raadiolingi enda kaudu.
  • Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces.
  • Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443).
  • DNS-i lahendamine – kui kasutad kohandatud maakleri hostinime, veenduge, et sõlm suudab seda lahendada. Try the broker’s IP address directly.

Messages Not Bridging

  • Kontrolli üleslingi/allalingi seadeid — kui lubatud on ainult üleslink, liiguvad sõnumid võrgust MQTT-sse, aga mitte tagasi. Luba vastuvõtval lüüsil allalink.
  • Kanali mittevastavus – mõlemad lüüsid peavad jagama sama kanalit sama PSK-ga. Vastuolu tähendab, et sõnumid on krüpteeritud erinevate võtmetega ja kuvatakse prügina.
  • Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root.
  • Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway.
  • Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in.

Seotud teemad

+

A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Sama teemaga liitunud kauglüüsid sisestavad need sõnumid oma kohalikku kärgvõrku.

Sätted

Luba MQTT

  1. Navigate to Settings → Module configuration → MQTT.
  2. Luba MQTT moodul.
  3. Configure the broker connection:
Sätted Kirjeldus Vaikimisi
Address MQTT vahendaja hostinimi mqtt.meshtastic.org
Username Broker authentication meshdev
Password Broker authentication large4cats
Root topic Base topic for messages msh, which the radio rewrites to msh/<REGION> once you set a region
Encryption enabled Krüpteeri MQTT liiklus Lubatud
JSON output enabled Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it Keelatud
TLS enabled Secure connection to broker Keelatud
Map reporting Teavita asukoht avalikul kaardil Keelatud
Proxy to client enabled Relay MQTT through the connected phone Keelatud

Connection Status and Test Connection

The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here.

Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason.

MQTT puhverserver sellel telefonil

If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection.

ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them.

The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration.

Meshtastic vaikemaakler

Kogukond haldab avaliku vahendajat aadressil mqtt.meshtastic.org. This is intended for general use and testing.

When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without).

🔒 Privaatsus: Avaliku vahendaja sõnumeid saavad lugeda kõik tellijad. Privaatse suhtluse jaoks kasuta alati kanali krüpteerimist.

Private Broker

Parema privaatsuse ja kontrolli tagamiseks saad hallata oma MQTT maaklerit:

  • Mosquitto (kerge, avatud lähtekoodiga)
  • HiveMQ
  • EMQX

Konfigureeri oma sõlm nii, et see osutaks sinu privaatsele maaklerile sobivate volitustega.

Kaardiaruannete koostamine

When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.

Turning it on opens a consent card. Turn on I agree. and choose a Map Publish Interval of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.

Reports appear at meshmap.net and similar community map services.

🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published.

Suund Kirjeldus
Üleslink Sõnumid kärgvõrgust → MQTT maakler
Allalink Sõnumid MQTT maaklerist → kärgvõrk

Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on.

Sõnumivormingud

MQTT carries two payload formats:

Vorming Kirjeldus Kasutusjuhtum
Protobuf Binaarne Meshtastic protobuf kodeering Node-to-node mesh bridging
JSON Human-readable JSON on the /2/json/ topic Consumers outside the mesh (dashboards, home automation)

ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads.

Encryption & Privacy

Understanding the layered encryption model:

  1. Kanali krüptimine toimub kärgvõrgus enne MQTT. Kui kanalil on PSK, on ​​MQTT liiklus juba krüptitud – maakler ja kõik tellijad näevad ainult šifriteksti.
  2. Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard.
  3. TLS krüpteerib TCP ühenduse vahendaja endaga, takistades võrgutasandil pealtkuulamist.

🔒 Security: The default public channel has a well-known key. MQTT kaudu saadetud vaikekanalil olevad sõnumid on sisuliselt krüpteerimata – igaüks saab neid dekodeerida. Always use a custom PSK for private communications.

Parimad tavad

  • Kasuta kanali krüptimist (PSK), kanalitel mis on sillatud MQTT-ga
  • Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes memory)
  • Use a private broker for sensitive deployments
  • MQTT sõnumite allalaadimisel arvesta eetriaja kuluga – iga allalingitud sõnum tarbib sinu kohalikus võrgus raadioeetriaega
  • Kaalu ainult üleslingi lubamist, kui sul on vaja oma kärgvõrku eemalt jälgida ilma sõnumeid tagasi tõmbamata

Veaotsing

MQTT ei ühendu

  • Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT ei tööta LoRa raadiolingi enda kaudu.
  • Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces.
  • Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443).
  • DNS-i lahendamine – kui kasutad kohandatud maakleri hostinime, veenduge, et sõlm suudab seda lahendada. Try the broker’s IP address directly.

Messages Not Bridging

  • Kontrolli üleslingi/allalingi seadeid — kui lubatud on ainult üleslink, liiguvad sõnumid võrgust MQTT-sse, aga mitte tagasi. Luba vastuvõtval lüüsil allalink.
  • Kanali mittevastavus – mõlemad lüüsid peavad jagama sama kanalit sama PSK-ga. Vastuolu tähendab, et sõnumid on krüpteeritud erinevate võtmetega ja kuvatakse prügina.
  • Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root.
  • Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway.
  • Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in.

Seotud teemad

diff --git a/main/et-rEE/user/settings-module-admin.html b/main/et-rEE/user/settings-module-admin.html index 36d89ed760..0dc8275dc6 100644 --- a/main/et-rEE/user/settings-module-admin.html +++ b/main/et-rEE/user/settings-module-admin.html @@ -1 +1 @@ - Sätted - moodulid & admin | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Eesti
Meshtastic Docs ↗

🌐 Eesti — Community translation View in English

Sätted - moodulid & admin

Konfi valikulisi funktsioonimooduleid ja teosta seadme haldamist. Moodulid laiendavad Meshtasticut spetsiaalsete võimalustega – igaüht saab eraldi lubada või keelata.

💡 Vihje: Pead lubama ainult need moodulid, mida sa tegelikult kasutad. Kasutamata moodulite keelamine vähendab eetriaega, säästab akut ja lihtsustab seadistamist. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.

Mooduli seaded kasutavad kaardipõhist paigutust koos lülitite, rippmenüüde, tekstiväljade ja liuguritega:

A toggle setting in the on position

A dropdown setting, expanded to show its list of options

A text field setting with a value entered

A module settings card with its title and grouped controls

Mooduli sätted

Every module lives under Settings → Module configuration.

⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes.

MQTT module

Sildab võrgusõnumeid MQTT vahendajasse ja sealt internetiühenduse loomiseks. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.

Sätted Kirjeldus
MQTT lubatud Lükka MQTT sild sisse
Aadress MQTT vahendaja aadress
Kasutajatunnus Authentication username
Parool Authentication password
Krüpteerimine lubatud Krüpteeri MQTT kasutus
JSON väljund lubatud Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS lubatud Use secure connection
Juurteema Baas MQTT teema teekond
Kliendi proksi lubatud Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself
Selle telefoni MQTT puhverserver The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT
Kaardi raport Publish position to the public map — see the Map reporting group that follows

Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:

Sätted Kirjeldus
Nõustun. Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Kaardi raporti sagedus (sekund) How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered

Vaata MQTT üksikasjalikumat kasutusjuhendit, mis sisaldab teavet krüpteerimise, privaatsuse ja vahendaja seadistamise kohta,.

Serial module

Võimaldab jadapordi sidet väliste seadmete integreerimiseks (GPS-moodulid, andurid või kohandatud riistvara). Kui lubatud, saab sõlme jadaühendus saata ja vastu võtta protobuf- või tekstiandmeid, võimaldades välistel mikrokontrolleritel või arvutitel võrguga suhelda.

Sätted Kirjeldus
Jadaport lubatud Aktiveeri jadapordi ühendus
Kaja lubatud Kaja sai jadaandmed tagasi
Jadapordi režiim Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX GPIO pins for the serial connection
Jadapordi kiirus Port speed
Aegunud How long to wait before considering an incoming message complete
Konsooli jadapordi alistamine Take over the port the debug console normally uses

External Notification module

Controls buzzer, LED, or vibration alerts on your node hardware. Kasulik seadmetele, mis peavad sõnumi saabumisest füüsiliselt märku andma – eriti kasulik järelevalveta või välistingimustes paigaldamise korral.

There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.

Sätted Kirjeldus
Luba Välised teated Master toggle for the module
Alert message LED / buzzer / vibra Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra Which outputs fire on a received bell character
Väljund LED (GPIO) Pin the LED is wired to
Väljund LED aktiivne Whether the LED pin is active high or low
Väljund summer (GPIO) Pin the buzzer is wired to
Väljund värin (GPIO) Pin the vibration motor is wired to
Kasuta PWM summerit Drive the buzzer with PWM, which allows tones rather than a single pitch
Kasuta I2S summerina Send the alert through an I2S audio output instead
Väljundi kestvus (millisekundit) How long a single alert lasts
Häire ajalõpp (sekundit) Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Helin The tone played on a PWM buzzer, in RTTTL. Can be imported from a file

Store & Forward module

Puhverdab ajutiselt võrguühenduseta olnud sõlmede sõnumeid ja esitab need uuesti, kui need sõlmed taasühenduvad. Hädavajalik kärgvõrgu jaoks, kus sõlmed regulaarselt levialasse lähevad ja levialast välja lähevad — tagab, et lühikeste katkestuste ajal sõnumid kaotsi ei lähe.

Sätted Kirjeldus
Salvesta & Edasta lubatud Aktiveeri salvesta ja saada
Südamelöögid Periodically announce this node’s store-and-forward capability
Kirjete arv Maximum stored messages
Ajalookirjete maksimaalne arv Max messages to replay
Ajalookirjete aken Time window for replay
Server Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)

💡 Vihje: Salvesta ja edasta töötab kõige paremini rohke mäluga sõlmedes (ESP32 koos PSRAM-iga). Router nodes are ideal candidates since they’re typically always-on.

Range Test module

⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.

Automatiseeritud vahemiku testimise tööriist sõlmede vahelise ühenduse kvaliteedi hindamiseks. Kui lubatud, edastab sõlm perioodiliselt testsõnumeid kasvavate loenduritega. Vastuvõtusõlm logib need sõnumid, võimaldades kõndida või minema sõita ning hiljem analüüsida, millisel kaugusel sõnumite saabumine lakkas.

Sätted Kirjeldus
Ulatustest lubatud Aktiveeri levi test
Saatja sõnumi sagedus (sekundit) Time between test transmissions, chosen from a dropdown of fixed intervals
Salvesta .CSV faili (ainult ESP32) Log received test data to the node’s own filesystem. ESP32 hardware only

Telemetry module

Juhib, milliseid telemeetriaandmeid sõlm võrguga jagab. Telemeetria sisaldab seadme tervist (aku, tööaeg) ja keskkonnaandurite andmeid (temperatuur, niiskus, rõhk).

Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.

Sätted Kirjeldus
Saada seadme telemeetria Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Seadme mõõdikute värskendamise intervall How often to report battery, uptime and channel utilization
Keskkonnamõõdikute lubamine Report the attached environment sensors
Keskkonnamõõdikute värskendamise intervall How often to report them
Keskkonnamõõdikute ekraanil kuvamine lubatud Also show these readings on the device’s own display
Keskkonnamõõdikud kasutavad Fahrenheiti Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Õhukvaliteedi moodul on lubatud Report particulate and CO₂ sensor data
Õhukvaliteedi näidikute värskendamise intervall How often to report them
Toitemõõdiku moodul on lubatud Report the per-channel voltage and current readings
Toitemõõdikute värskendamise intervall How often to report them
Toitemõõdiku ekraanil kuvamine lubatud Also show power readings on the device’s display

Vaata Telemeetria & Sensorid toetatud andurite ja sätete soovituste kohta.

Canned Message module

Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Määra nimekiri kiirsõnumitest, mida saab edastada ilma telefoni ühendamata – ideaalne välitöödeks.

Sätted Kirjeldus
Canned message enabled ⚠️ Deprecated in the protobuf schema
Sõnumid Reavahetusega eraldatud sõnumite loend
Saada Kõll Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Pöördvalik #1 lubatud Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port The three pins the encoder is wired to
Generate input event on Press / CW / CCW Which key event each encoder action produces
Üles/Alla/Vali sisend lubatud A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source ⚠️ Deprecated in the protobuf schema

Audio module

Codec2 audio support for low-bandwidth voice communication over the mesh. See on eksperimentaalne funktsioon, mis kodeerib hääle Codec2 koodeki abil väga väikesteks andmepakettideks.

Sätted Kirjeldus
CODEC 2 lubatud Aktiveeri audio moodul
CODEC2 test sagedus Audio quality/bandwidth tradeoff
PTT klemm GPIO pin for the push-to-talk button
I2S sõna valik GPIO sisend I2S WS jaoks
I2S info sisse GPIO sisend I2S DIN jaoks
I2S info välja GPIO sisend I2S DOUT jaoks
I2S kell GPIO pin for the I2S bit clock

ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.

Remote Hardware module

GPIO juhtimine kärgvõrgu kaudu. Võimaldab kaugsõlmel lugeda või kirjutada GPIO sisendkontakte teisel sõlmel – kasulik releede aktiveerimiseks, lülitite lugemiseks või välise riistvara kaugjuhtimiseks.

⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.

Sätted Kirjeldus
Kaug riistvara lubatud Aktiveeri kaugjuurdepääs GPIO-le
Luba määratlemata klemmi juurdepääs Luba juurdepääs mis tahes GPIO sisendile (turvarisk)
Saadaval klemmid Kuni 4 GPIO sisendit, mida see sõlm kauglugemiseks/-kirjutamiseks avab

Neighbor Info module

Levitab teavet otse kuuldud naabrite kohta, võimaldades kärgvõrgu topoloogia kaardistamist. Iga lubatud sõlm jagab perioodiliselt nimekirja teistest sõlmedest, mida ta kuuleb ja nende signaali kvaliteedist.

Sätted Kirjeldus
Naabruskonna teave lubatud Aktiveeri naabrite leviring
Uuenduste sagedus (sekundit) Kui tihti naabrite nimekirja levitada
Saada LoRa kaudu Edasta naabriinfot ka LoRa kaudu, mitte ainult MQTT/telefoni kaudu. Vaikimisi võtit ja nime kasutavat kanalit pole saadaval

See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.

Ambient Lighting module

Juhib toetatud riistvaral NeoPixeli või muid adresseeritavaid RGB LEDe. Saab kasutada visuaalsete olekuindikaatorite, märgutulede või dekoratiivsete efektide jaoks.

Sätted Kirjeldus
LED olek Turn the LED on or off
Pinge LED current limit (0–31)
Punane / Roheline / Sinine Individuaalsete värvikanalite väärtused (0–255)

Detection Sensor module

Muudab sõlme liikumis- või ukseanduri hoiatussüsteemiks. Kui GPIO sisend tuvastab oleku muutuse (liikumine tuvastatud, uks avatud), levitab sõlm kärgvõrgu kaudu hoiatusteate.

Sätted Kirjeldus
Tuvastusandur lubatud Aktiveeri tuvastusandur
GPIO klemmi jälgimine GPIO sisend on anduriga ühendatud
Identifitseerimistüüp Kuidas klemmi olek vastab tuvastussündmusele (nt aktiivne kõrge/madal, serva poolt käivitatav)
Kasuta INPUT_PULLUP režiimi Enable the pin’s internal pull-up resistor
Minimaalne edastusaeg (sekund) Minimaalne aeg hoiatusteadete levitamisel
Oleku edastus (sekund) Perioodilise oleku levitamise intervall
Saada kõll koos hoiatussõnumiga Lisa märguannetesse hoiatuskella sümbol
Kasutajasõbralik nimi Selle anduri kohandatud nimi

Paxcounter module

People counter using Wi-Fi and BLE probe requests. Loendab lähedalasuvaid seadmeid, kuulates passiivselt sondimistaotlusi, mida telefonid ja sülearvutid võrkude skannimisel edastavad. Available only on ESP32 devices.

Sätted Kirjeldus
Paxcounter lubatud Aktiveeri inimeste loendamine
Uuenduste sagedus (sekundit) Kui tihti loendeid esitada
Wi-Fi RSSI threshold Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE RSSI threshold The same cut-off for BLE advertisements (defaults to −80 dBm)

💡 Vihje: Paxloendur on kasulik jalakäijate liikluse hindamiseks matkaradade alguses, ürituste toimumiskohtades või muudes kohtades. Arvud on ligikaudsed – üks inimene võib kaasas kanda mitut seadet.

Status Message module

The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.

Mesh Beacon module

Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.

TAK module

Meeskonna teadlikkuse komplekti integratsioon ATAKi ja WinTAKi koostalitlusvõime tagamiseks. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. Vaata TAK Integration täpsema seadistamise ja kasutamise kohta.

Haldus

Kaughaldus

Administraatori võtit jagavate sõlmede kaugkonfigureerimine:

  1. Vali sõlmede loendist sihtsõlm.
  2. Mine selle sõlme Seadetesse.
  3. Muuda seadistust.
  4. Puuduta Salvesta – muudatused saadetakse kärgvõrgu kaudu.

⚠️ Important: Requires an admin key configured on both your node and the target node.

Device Actions

Settings → Administration holds five one-shot actions, each behind a confirmation dialog:

Action What it does
Määra aeg Sends your phone’s clock to the node
Taaskäivita Restarts the node
Lülita välja Powers the node down
Tehasesätted Returns every setting to its factory default
NodeDB lähtestamine Clears the node database. This dialog carries a Preserve Favorites? switch

⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.

Varunda ja taasta

Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.

Täpsem

Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.

Tühjenda sõlmede andmebaas

Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.

  • Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
  • Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.

The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.

Arendaja paneel

Avab vahekaardid Paketid ja Rakenduse logid diagnostilise väljundi vaatamiseks, filtreerimiseks ja eksportimiseks. See Debug Logs for the full walkthrough.

App Settings

The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:

Privacy

  • Allow analytics and crash reporting — opt in or out of diagnostics.
  • Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
  • Homoglyph encoding — how look-alike characters in names are handled.

Appearance

  • Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
  • Theme and Language.
  • Show full message timestamps.

Persistence

  • A cache limit for how much history is kept.
  • Export rangetest packets, Export all packets and Export node database.

On their own

  • Node Layout — how much detail each row of the node list shows.
  • Wi-Fi Provisioning for mPWRD-OS — see Connections.
  • Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
  • System AI — appears only where app functions are available; see App Functions.

A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.

Teave

Settings → About carries the app’s own identity rather than the node’s:

Three sections:

  • What is Meshtastic? — a short description of the project.
  • Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
  • Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.

The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.

Tänusõnad

Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.

Troubleshooting remote admin

  • “Sihtsõlmelt ei ole vastust” — sihtsõlm võib olla leviulatusest väljas, võrguühenduseta või sellel võib olla sobimatu administraatori võti. Veendu, et administraatori võti sobiks mõlemas sõlmele.
  • Muudatused ei rakendu — mõnede sätete jõustumiseks on vaja taaskäivitada. Pärast salvestamist proovi taaskäivitust.
  • Ei näe kaugseadeid — veendu, et sõlmel oleks sihtsõlme administraatori võti ja et administraatori kanal oleks turbekonfiguratsioonis lubatud. Administraatori kanal seadistatakse automaatselt, kui administraatori võti on määratud.

Seotud teemad

+ Sätted - moodulid & admin | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Eesti
Meshtastic Docs ↗

🌐 Eesti — Community translation View in English

Sätted - moodulid & admin

Konfi valikulisi funktsioonimooduleid ja teosta seadme haldamist. Moodulid laiendavad Meshtasticut spetsiaalsete võimalustega – igaüht saab eraldi lubada või keelata.

💡 Vihje: Pead lubama ainult need moodulid, mida sa tegelikult kasutad. Kasutamata moodulite keelamine vähendab eetriaega, säästab akut ja lihtsustab seadistamist. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.

Mooduli seaded kasutavad kaardipõhist paigutust koos lülitite, rippmenüüde, tekstiväljade ja liuguritega:

A toggle setting in the on position

A dropdown setting, expanded to show its list of options

A text field setting with a value entered

A module settings card with its title and grouped controls

Mooduli sätted

Every module lives under Settings → Module configuration.

⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes.

MQTT module

Sildab võrgusõnumeid MQTT vahendajasse ja sealt internetiühenduse loomiseks. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.

Sätted Kirjeldus
MQTT lubatud Lükka MQTT sild sisse
Aadress MQTT vahendaja aadress
Kasutajatunnus Authentication username
Parool Authentication password
Krüpteerimine lubatud Krüpteeri MQTT kasutus
JSON väljund lubatud Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS lubatud Use secure connection
Juurteema Baas MQTT teema teekond
Kliendi proksi lubatud Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself
Selle telefoni MQTT puhverserver The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT
Kaardi raport Publish position to the public map — see the Map reporting group that follows

Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:

Sätted Kirjeldus
Nõustun. Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered

Vaata MQTT üksikasjalikumat kasutusjuhendit, mis sisaldab teavet krüpteerimise, privaatsuse ja vahendaja seadistamise kohta,.

Serial module

Võimaldab jadapordi sidet väliste seadmete integreerimiseks (GPS-moodulid, andurid või kohandatud riistvara). Kui lubatud, saab sõlme jadaühendus saata ja vastu võtta protobuf- või tekstiandmeid, võimaldades välistel mikrokontrolleritel või arvutitel võrguga suhelda.

Sätted Kirjeldus
Jadaport lubatud Aktiveeri jadapordi ühendus
Kaja lubatud Kaja sai jadaandmed tagasi
Jadapordi režiim Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX GPIO pins for the serial connection
Jadapordi kiirus Port speed
Aegunud How long to wait before considering an incoming message complete
Konsooli jadapordi alistamine Take over the port the debug console normally uses

External Notification module

Controls buzzer, LED, or vibration alerts on your node hardware. Kasulik seadmetele, mis peavad sõnumi saabumisest füüsiliselt märku andma – eriti kasulik järelevalveta või välistingimustes paigaldamise korral.

There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.

Sätted Kirjeldus
Luba Välised teated Master toggle for the module
Alert message LED / buzzer / vibra Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra Which outputs fire on a received bell character
Väljund LED (GPIO) Pin the LED is wired to
Väljund LED aktiivne Whether the LED pin is active high or low
Väljund summer (GPIO) Pin the buzzer is wired to
Väljund värin (GPIO) Pin the vibration motor is wired to
Kasuta PWM summerit Drive the buzzer with PWM, which allows tones rather than a single pitch
Kasuta I2S summerina Send the alert through an I2S audio output instead
GPIO Output Duration How long a single alert lasts
Nag Timeout Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Helin The tone played on a PWM buzzer, in RTTTL. Can be imported from a file

Store & Forward module

Puhverdab ajutiselt võrguühenduseta olnud sõlmede sõnumeid ja esitab need uuesti, kui need sõlmed taasühenduvad. Hädavajalik kärgvõrgu jaoks, kus sõlmed regulaarselt levialasse lähevad ja levialast välja lähevad — tagab, et lühikeste katkestuste ajal sõnumid kaotsi ei lähe.

Sätted Kirjeldus
Salvesta & Edasta lubatud Aktiveeri salvesta ja saada
Südamelöögid Periodically announce this node’s store-and-forward capability
Kirjete arv Maximum stored messages
Ajalookirjete maksimaalne arv Max messages to replay
Ajalookirjete aken Time window for replay
Server Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)

💡 Vihje: Salvesta ja edasta töötab kõige paremini rohke mäluga sõlmedes (ESP32 koos PSRAM-iga). Router nodes are ideal candidates since they’re typically always-on.

Range Test module

⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.

Automatiseeritud vahemiku testimise tööriist sõlmede vahelise ühenduse kvaliteedi hindamiseks. Kui lubatud, edastab sõlm perioodiliselt testsõnumeid kasvavate loenduritega. Vastuvõtusõlm logib need sõnumid, võimaldades kõndida või minema sõita ning hiljem analüüsida, millisel kaugusel sõnumite saabumine lakkas.

Sätted Kirjeldus
Ulatustest lubatud Aktiveeri levi test
Sender Interval Time between test transmissions, chosen from a dropdown of fixed intervals
Salvesta .CSV faili (ainult ESP32) Log received test data to the node’s own filesystem. ESP32 hardware only

Telemetry module

Juhib, milliseid telemeetriaandmeid sõlm võrguga jagab. Telemeetria sisaldab seadme tervist (aku, tööaeg) ja keskkonnaandurite andmeid (temperatuur, niiskus, rõhk).

Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.

Sätted Kirjeldus
Saada seadme telemeetria Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Seadme mõõdikute värskendamise intervall How often to report battery, uptime and channel utilization
Keskkonnamõõdikute lubamine Report the attached environment sensors
Keskkonnamõõdikute värskendamise intervall How often to report them
Keskkonnamõõdikute ekraanil kuvamine lubatud Also show these readings on the device’s own display
Keskkonnamõõdikud kasutavad Fahrenheiti Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Õhukvaliteedi moodul on lubatud Report particulate and CO₂ sensor data
Õhukvaliteedi näidikute värskendamise intervall How often to report them
Toitemõõdiku moodul on lubatud Report the per-channel voltage and current readings
Toitemõõdikute värskendamise intervall How often to report them
Toitemõõdiku ekraanil kuvamine lubatud Also show power readings on the device’s display

Vaata Telemeetria & Sensorid toetatud andurite ja sätete soovituste kohta.

Canned Message module

Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Määra nimekiri kiirsõnumitest, mida saab edastada ilma telefoni ühendamata – ideaalne välitöödeks.

Sätted Kirjeldus
Canned message enabled ⚠️ Deprecated in the protobuf schema
Sõnumid Reavahetusega eraldatud sõnumite loend
Saada Kõll Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Pöördvalik #1 lubatud Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port The three pins the encoder is wired to
Generate input event on Press / CW / CCW Which key event each encoder action produces
Üles/Alla/Vali sisend lubatud A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source ⚠️ Deprecated in the protobuf schema

Audio module

Codec2 audio support for low-bandwidth voice communication over the mesh. See on eksperimentaalne funktsioon, mis kodeerib hääle Codec2 koodeki abil väga väikesteks andmepakettideks.

Sätted Kirjeldus
CODEC 2 lubatud Aktiveeri audio moodul
CODEC2 test sagedus Audio quality/bandwidth tradeoff
PTT klemm GPIO pin for the push-to-talk button
I2S sõna valik GPIO sisend I2S WS jaoks
I2S info sisse GPIO sisend I2S DIN jaoks
I2S info välja GPIO sisend I2S DOUT jaoks
I2S kell GPIO pin for the I2S bit clock

ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.

Remote Hardware module

GPIO juhtimine kärgvõrgu kaudu. Võimaldab kaugsõlmel lugeda või kirjutada GPIO sisendkontakte teisel sõlmel – kasulik releede aktiveerimiseks, lülitite lugemiseks või välise riistvara kaugjuhtimiseks.

⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.

Sätted Kirjeldus
Kaug riistvara lubatud Aktiveeri kaugjuurdepääs GPIO-le
Luba määratlemata klemmi juurdepääs Luba juurdepääs mis tahes GPIO sisendile (turvarisk)
Saadaval klemmid Kuni 4 GPIO sisendit, mida see sõlm kauglugemiseks/-kirjutamiseks avab

Neighbor Info module

Levitab teavet otse kuuldud naabrite kohta, võimaldades kärgvõrgu topoloogia kaardistamist. Iga lubatud sõlm jagab perioodiliselt nimekirja teistest sõlmedest, mida ta kuuleb ja nende signaali kvaliteedist.

Sätted Kirjeldus
Naabruskonna teave lubatud Aktiveeri naabrite leviring
GPS-i küsimise intervall Kui tihti naabrite nimekirja levitada
Saada LoRa kaudu Edasta naabriinfot ka LoRa kaudu, mitte ainult MQTT/telefoni kaudu. Vaikimisi võtit ja nime kasutavat kanalit pole saadaval

See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.

Ambient Lighting module

Juhib toetatud riistvaral NeoPixeli või muid adresseeritavaid RGB LEDe. Saab kasutada visuaalsete olekuindikaatorite, märgutulede või dekoratiivsete efektide jaoks.

Sätted Kirjeldus
LED olek Turn the LED on or off
Pinge LED current limit (0–31)
Punane / Roheline / Sinine Individuaalsete värvikanalite väärtused (0–255)

Detection Sensor module

Muudab sõlme liikumis- või ukseanduri hoiatussüsteemiks. Kui GPIO sisend tuvastab oleku muutuse (liikumine tuvastatud, uks avatud), levitab sõlm kärgvõrgu kaudu hoiatusteate.

Sätted Kirjeldus
Tuvastusandur lubatud Aktiveeri tuvastusandur
GPIO klemmi jälgimine GPIO sisend on anduriga ühendatud
Identifitseerimistüüp Kuidas klemmi olek vastab tuvastussündmusele (nt aktiivne kõrge/madal, serva poolt käivitatav)
Kasuta INPUT_PULLUP režiimi Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts Minimaalne aeg hoiatusteadete levitamisel
State Broadcast Interval Perioodilise oleku levitamise intervall
Saada kõll koos hoiatussõnumiga Lisa märguannetesse hoiatuskella sümbol
Kasutajasõbralik nimi Selle anduri kohandatud nimi

Paxcounter module

People counter using Wi-Fi and BLE probe requests. Loendab lähedalasuvaid seadmeid, kuulates passiivselt sondimistaotlusi, mida telefonid ja sülearvutid võrkude skannimisel edastavad. Available only on ESP32 devices.

Sätted Kirjeldus
Paxcounter lubatud Aktiveeri inimeste loendamine
GPS-i küsimise intervall Kui tihti loendeid esitada
WiFi Threshold (dBm) Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm) The same cut-off for BLE advertisements (defaults to −80 dBm)

💡 Vihje: Paxloendur on kasulik jalakäijate liikluse hindamiseks matkaradade alguses, ürituste toimumiskohtades või muudes kohtades. Arvud on ligikaudsed – üks inimene võib kaasas kanda mitut seadet.

Status Message module

The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.

Mesh Beacon module

Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.

TAK module

Meeskonna teadlikkuse komplekti integratsioon ATAKi ja WinTAKi koostalitlusvõime tagamiseks. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. Vaata TAK Integration täpsema seadistamise ja kasutamise kohta.

Haldus

Kaughaldus

Administraatori võtit jagavate sõlmede kaugkonfigureerimine:

  1. Vali sõlmede loendist sihtsõlm.
  2. Mine selle sõlme Seadetesse.
  3. Muuda seadistust.
  4. Puuduta Salvesta – muudatused saadetakse kärgvõrgu kaudu.

⚠️ Important: Requires an admin key configured on both your node and the target node.

Device Actions

Settings → Administration holds five one-shot actions, each behind a confirmation dialog:

Action What it does
Määra aeg Sends your phone’s clock to the node
Taaskäivita Restarts the node
Lülita välja Powers the node down
Tehasesätted Returns every setting to its factory default
NodeDB lähtestamine Clears the node database. This dialog carries a Preserve Favorites? switch

⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.

Varunda ja taasta

Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.

Täpsem

Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.

Tühjenda sõlmede andmebaas

Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.

  • Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
  • Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.

The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.

Arendaja paneel

Avab vahekaardid Paketid ja Rakenduse logid diagnostilise väljundi vaatamiseks, filtreerimiseks ja eksportimiseks. See Debug Logs for the full walkthrough.

App Settings

The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:

Privacy

  • Allow analytics and crash reporting — opt in or out of diagnostics.
  • Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
  • Homoglyph encoding — how look-alike characters in names are handled.

Appearance

  • Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
  • Theme and Language.
  • Show full message timestamps.

Persistence

  • A cache limit for how much history is kept.
  • Export rangetest packets, Export all packets and Export node database.

On their own

  • Node Layout — how much detail each row of the node list shows.
  • Wi-Fi Provisioning for mPWRD-OS — see Connections.
  • Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
  • System AI — appears only where app functions are available; see App Functions.

A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.

Teave

Settings → About carries the app’s own identity rather than the node’s:

Three sections:

  • What is Meshtastic? — a short description of the project.
  • Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
  • Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.

The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.

Tänusõnad

Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.

Troubleshooting remote admin

  • “Sihtsõlmelt ei ole vastust” — sihtsõlm võib olla leviulatusest väljas, võrguühenduseta või sellel võib olla sobimatu administraatori võti. Veendu, et administraatori võti sobiks mõlemas sõlmele.
  • Muudatused ei rakendu — mõnede sätete jõustumiseks on vaja taaskäivitada. Pärast salvestamist proovi taaskäivitust.
  • Ei näe kaugseadeid — veendu, et sõlmel oleks sihtsõlme administraatori võti ja et administraatori kanal oleks turbekonfiguratsioonis lubatud. Administraatori kanal seadistatakse automaatselt, kui administraatori võti on määratud.

Seotud teemad

diff --git a/main/et-rEE/user/settings-radio-user.html b/main/et-rEE/user/settings-radio-user.html index adf96f5630..a3c0e4025a 100644 --- a/main/et-rEE/user/settings-radio-user.html +++ b/main/et-rEE/user/settings-radio-user.html @@ -1 +1 @@ - Seaded — raadio ja kasutaja | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Eesti
Meshtastic Docs ↗

🌐 Eesti — Community translation View in English

Seaded — raadio ja kasutaja

Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How these screens work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth.

Seaded kasutavad standardseid eelistuste juhtelemente – rippmenüüsid, lülitid ja liugurid:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

Kasutaja seaded

Kasutajaprofiil

On Settings → User.

Sätted Kirjeldus
Täis nimi Your display name (up to 39 characters)
Lühi nimi 4-character abbreviated name
Oleku teavitus A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Ei võta sõnumeid vastu Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur node (Ham) Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in.

Sätted

Seadme sätted

On Settings → Device configuration → Device.

Sätted Kirjeldus Vaikimisi
Seadme roll Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Kordusülekannete režiim How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Sõlme teabe edastamise intervall How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Topeltpuudutus nupuna Treat a double tap as a button press Keelatud
Kolmekordne klõps Ad Hoc Ping Send an ad-hoc position ping on a triple click Lubatud
Südamelöögi LED Blink the status LED periodically Lubatud
Ajavöönd POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it —
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to —

LoRa sätted

On Settings → LoRa.

Sätted Kirjeldus Vaikimisi
Regioon Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number Määramata (tuleb seadistada)
Eelseadistused Speed/range tradeoff LongFast
Hüpete arv Maks uuesti saadetud hüpet 3
Saatevõimsus Transmission power (dBm); 0 = max allowed for region 0 (regiooni maks)
Tühista sagedus Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Kasuta eelseadistust On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Levitustegur Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead From preset
Kodeerimiskiirus Manual mode only: 5–8. More redundancy costs airtime From preset
Ribalaius Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Sageduspesa Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Edastus lubatud Turning this off makes the node receive-only On
Töötsükli tühistamine Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Väljas
Keela MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok MQTTi Allow your packets to be forwarded to MQTT by gateways Väljas
RX võimendatud võimendus Extra receive gain on SX126x radios; costs a little current Väljas
PA ventilaator keelatud Turn off the power-amplifier fan on hardware that has one Väljas

The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set.

Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. Lisateabe saamiseks vaadake regiooni seadistamise juhendit aadressil meshtastic.org.

Modem presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes.

💡 Vihje: SNR-i piirväärtused on meelega negatiivsed. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Kiirus SNR limiit Parim
Short Turbo ~1 km 21,9 kbps −7,5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10,9 kbps −7,5 dB Linnaosad; hooned mõne kvartali raadiuses
Short Slow ~5 km 6.25 kbps −10 dB Äärelinna lühimaa; mõõdukas hoonestustihedus
Medium Fast ~5 km 3.52 kbps −12,5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17,5 dB Sarnane ulatus kui Pikk Kauge, aga 500 kHz ribalaiusega; kiirem läbilaskevõime
Long Fast ~10 km 1,1 kbps −17,5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0,34 kbps −17,5 dB Maapiirkond, mõningase maastikuga; aeg-ajalt kasutatav
Lite Fast ~5 km 1.76 kbps −12,5 dB EL 866 MHz SRD sagedusala (125 kHz ribalaius); võrreldav Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EL 866 MHz SRD sagedusala (125 kHz ribalaius); võrreldav Long Fast
Narrow Fast ~5 km 2.28 kbps −7,5 dB EL 868 MHz sagedusala (62,5 kHz sagedusriba); väldib häireid teiste seadmetega
Narrow Slow ~10 km 1.30 kbps −10 dB EL 868 MHz sagedusala (62,5 kHz ribalaius); võrreldav Long Fast
Medium Turbo ~5 km 7.0 kbps −12,5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7,5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements
Long Slow ~30 km 0,18 kbps −20 dB ⚠️ Vananenud — endiselt valitav, kuid võidakse tulevases püsivara versioonis eemaldada
Very Long Slow ~40+ km 0,09 kbps −20 dB ⚠️ Vananenud — endiselt valitav, kuid võidakse tulevases püsivara versioonis eemaldada

ℹ️ Märkus: Selles tabelis kasutatakse üldlevinud lühinimesid. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a modem preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). See tähendab pikemat ulatust, aga vähem baite sekundis.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Linnavõrk (palju sõlmi, lühikesed vahemaad): Kasutage valikut Long Fast (vaikimisi) või Short Fast. Suurem kiirus tähendab väiksemat eetriaega, kui kanalit jagavad paljud sõlmed.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • Vastavus EL 866/868 MHz regulatsioonidele: Kasuta Lite Fast, Lite Slow, Narrow Fast või Narrow Slow – need on optimeeritud kitsama ribalaiusega EL SRD/868 MHz sagedusaladele.
  • Fikseeritud taristuühendused: Kasutage Short Turbo või Long Turbo spetsiaalsete punkt-punkti ühenduste jaoks, millel on head antennid ja otsenähtavus.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Kõrguse eelis (mäetipp, katus) suurendab märgatavalt efektiivset ulatust. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Ekraani sätted

On Settings → Device configuration → Display. These control the node’s own screen, not the app’s.

Sätted Kirjeldus
Ekraan sisse lülitatud How long the display stays lit before sleeping
Karusselli intervall How often the node cycles between screens on its own
Ekraani režiim Screen layout/density used by the firmware
Ekraani ühikud Metric or Imperial on the node’s screen
Kasuta 12 tunni formaati Show the node’s clock as 12-hour rather than 24-hour
Paks pealkiri Draw the screen’s heading text in bold
Keera ekraani Rotate the display 180° for an inverted mounting
OLED tüüp Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED
Ärata puudutusega või liigutusega Light the screen when the node is tapped or moved
Kompassi suund Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each
Suund alati põhi Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Asukoha sätted

On Settings → Device configuration → Position.

Sätted Kirjeldus
GPS-režiim (riistvara) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS-i küsimise intervall How often the node asks its GPS for a fix
Levitamise inteintervall How often the position is shared with the mesh
Nutikas asukoht Broadcast based on movement rather than purely on the clock
Nutikas intervall With Smart Position on, the shortest gap between broadcasts
Nutikas kaugus With Smart Position on, how far you must move before broadcasting
Määratud asukoht Use a manually entered latitude, longitude and altitude instead of the GPS
Asukoha lipp A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Toite sätted

On Settings → Device configuration → Power.

Sätted Kirjeldus
Luba energiasäästurežiim Let the node sleep aggressively between activity
Väljalülitamine voolukatkestuse korral Power the device down after external power disappears
Super sügava une kestus How long the deepest sleep state lasts
Minimaalne ärkveloleku aeg The shortest time the node stays awake once woken
Oota Bluetoothi ​​kestust How long to wait for a phone to connect before sleeping
ADC kordaja tühistamine Turn on a manual correction for battery-voltage readings
Asenda ADC kordistaja suhe The correction factor itself, used only when the override is on
Aku INA_2XX I2C aadress Address of an external INA-series power sensor, if fitted

Võrgu sätted

On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node.

Sätted Kirjeldus
Wi-Fi enabled Enable the Wi-Fi node (ESP32 nodes)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Parool Network password
Ethernet lubatud Use a wired connection on hardware that has one
IPv4 režiim DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP levitamine Share mesh traffic with other nodes over the local network
NTP server Time synchronization server
rsyslog server Kauglogimise server

Network Config with a static IPv4 address entered

Sinihamba sätted

On Settings → Device configuration → Bluetooth, on nodes with Bluetooth.

Sätted Kirjeldus
Sinihammas lubatud Enable/disable BLE radio
Sidumine Määratud PIN kood, juhuslik PIN kood või PIN koodi pole
Fikseeritud PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Turva sätted

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

Sätted Kirjeldus
Avalik võti Sinu sõlme avalik võti (kirjutuskaitstud)
Administraatori võti Keys permitted to administer this node remotely — up to three
Salajane võti Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it
Loo uus privaatvõti Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin kanal lubatud ⚠️ Eemaldatud — nüüd seadistatakse automaatselt, kui administraatori võti on määratud
Jadapordi konsool Serial console over the Stream API
Silumislogi API lubatud Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth
Hallatud režiim Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set
Taastevõtmed Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Taasta võtmed Kirjuta varundatud võtmed tagasi sõlme (saadaval siis, kui varukoopia on olemas)
Kustuta taastevõtmed Remove the stored key backup from this phone
Kaitsetase How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Käivitusi alles How many device boots the unlocked state survives
Tunde kuni kehtivusaja lõpuni Wall-clock lifetime of the unlocked state
Seansi limiit (minutid) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.

Seotud teemad

+ Seaded — raadio ja kasutaja | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Eesti
Meshtastic Docs ↗

🌐 Eesti — Community translation View in English

Seaded — raadio ja kasutaja

Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How these screens work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth.

Seaded kasutavad standardseid eelistuste juhtelemente – rippmenüüsid, lülitid ja liugurid:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

Kasutaja seaded

Kasutajaprofiil

On Settings → User.

Sätted Kirjeldus
Täis nimi Your display name (up to 39 characters)
Lühi nimi 4-character abbreviated name
Oleku teavitus A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Ei võta sõnumeid vastu Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur node (Ham) Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in.

Sätted

Seadme sätted

On Settings → Device configuration → Device.

Sätted Kirjeldus Vaikimisi
Seadme roll Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Kordusülekannete režiim How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Sõlme teabe edastamise intervall How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Topeltpuudutus nupuna Treat a double tap as a button press Keelatud
Kolmekordne klõps Ad Hoc Ping Send an ad-hoc position ping on a triple click Lubatud
Südamelöögi LED Blink the status LED periodically Lubatud
Ajavöönd POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it —
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to —

LoRa sätted

On Settings → LoRa.

Sätted Kirjeldus Vaikimisi
Regioon Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number Määramata (tuleb seadistada)
Eelseadistused Speed/range tradeoff LongFast
Hüpete arv Maks uuesti saadetud hüpet 3
Transmit Power (dBm) Transmission power; 0 = max allowed for region 0 (regiooni maks)
Tühista sagedus Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Kasuta eelseadistust On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Levitustegur Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead From preset
Kodeerimiskiirus Manual mode only: 5–8. More redundancy costs airtime From preset
Ribalaius Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Sageduspesa Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Edastus lubatud Turning this off makes the node receive-only On
Töötsükli tühistamine Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Väljas
Keela MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok MQTTi Allow your packets to be forwarded to MQTT by gateways Väljas
RX võimendatud võimendus Extra receive gain on SX126x radios; costs a little current Väljas
PA ventilaator keelatud Turn off the power-amplifier fan on hardware that has one Väljas

The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set.

Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. Lisateabe saamiseks vaadake regiooni seadistamise juhendit aadressil meshtastic.org.

Modem presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes.

💡 Vihje: SNR-i piirväärtused on meelega negatiivsed. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Kiirus SNR limiit Parim
Short Turbo ~1 km 21,9 kbps −7,5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10,9 kbps −7,5 dB Linnaosad; hooned mõne kvartali raadiuses
Short Slow ~5 km 6.25 kbps −10 dB Äärelinna lühimaa; mõõdukas hoonestustihedus
Medium Fast ~5 km 3.52 kbps −12,5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17,5 dB Sarnane ulatus kui Pikk Kauge, aga 500 kHz ribalaiusega; kiirem läbilaskevõime
Long Fast ~10 km 1,1 kbps −17,5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0,34 kbps −17,5 dB Maapiirkond, mõningase maastikuga; aeg-ajalt kasutatav
Lite Fast ~5 km 1.76 kbps −12,5 dB EL 866 MHz SRD sagedusala (125 kHz ribalaius); võrreldav Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EL 866 MHz SRD sagedusala (125 kHz ribalaius); võrreldav Long Fast
Narrow Fast ~5 km 2.28 kbps −7,5 dB EL 868 MHz sagedusala (62,5 kHz sagedusriba); väldib häireid teiste seadmetega
Narrow Slow ~10 km 1.30 kbps −10 dB EL 868 MHz sagedusala (62,5 kHz ribalaius); võrreldav Long Fast
Medium Turbo ~5 km 7.0 kbps −12,5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7,5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements
Long Slow ~30 km 0,18 kbps −20 dB ⚠️ Vananenud — endiselt valitav, kuid võidakse tulevases püsivara versioonis eemaldada
Very Long Slow ~40+ km 0,09 kbps −20 dB ⚠️ Vananenud — endiselt valitav, kuid võidakse tulevases püsivara versioonis eemaldada

ℹ️ Märkus: Selles tabelis kasutatakse üldlevinud lühinimesid. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a modem preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). See tähendab pikemat ulatust, aga vähem baite sekundis.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Linnavõrk (palju sõlmi, lühikesed vahemaad): Kasutage valikut Long Fast (vaikimisi) või Short Fast. Suurem kiirus tähendab väiksemat eetriaega, kui kanalit jagavad paljud sõlmed.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • Vastavus EL 866/868 MHz regulatsioonidele: Kasuta Lite Fast, Lite Slow, Narrow Fast või Narrow Slow – need on optimeeritud kitsama ribalaiusega EL SRD/868 MHz sagedusaladele.
  • Fikseeritud taristuühendused: Kasutage Short Turbo või Long Turbo spetsiaalsete punkt-punkti ühenduste jaoks, millel on head antennid ja otsenähtavus.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Kõrguse eelis (mäetipp, katus) suurendab märgatavalt efektiivset ulatust. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Ekraani sätted

On Settings → Device configuration → Display. These control the node’s own screen, not the app’s.

Sätted Kirjeldus
Ekraan sisse lülitatud How long the display stays lit before sleeping
Karusselli intervall How often the node cycles between screens on its own
Ekraani režiim Screen layout/density used by the firmware
Ekraani ühikud Metric or Imperial on the node’s screen
Kasuta 12 tunni formaati Show the node’s clock as 12-hour rather than 24-hour
Paks pealkiri Draw the screen’s heading text in bold
Keera ekraani Rotate the display 180° for an inverted mounting
OLED tüüp Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED
Ärata puudutusega või liigutusega Light the screen when the node is tapped or moved
Kompassi suund Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each
Suund alati põhi Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Asukoha sätted

On Settings → Device configuration → Position.

Sätted Kirjeldus
GPS-režiim (riistvara) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS-i küsimise intervall How often the node asks its GPS for a fix
Levitamise inteintervall How often the position is shared with the mesh
Nutikas asukoht Broadcast based on movement rather than purely on the clock
Nutikas intervall With Smart Position on, the shortest gap between broadcasts
Nutikas kaugus With Smart Position on, how far you must move before broadcasting
Määratud asukoht Use a manually entered latitude, longitude and altitude instead of the GPS
Asukoha lipp A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Toite sätted

On Settings → Device configuration → Power.

Sätted Kirjeldus
Luba energiasäästurežiim Let the node sleep aggressively between activity
Väljalülitamine voolukatkestuse korral Power the device down after external power disappears
Super sügava une kestus How long the deepest sleep state lasts
Minimaalne ärkveloleku aeg The shortest time the node stays awake once woken
Oota Bluetoothi ​​kestust How long to wait for a phone to connect before sleeping
ADC kordaja tühistamine Turn on a manual correction for battery-voltage readings
Asenda ADC kordistaja suhe The correction factor itself, used only when the override is on
Aku INA_2XX I2C aadress Address of an external INA-series power sensor, if fitted

Võrgu sätted

On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node.

Sätted Kirjeldus
Wi-Fi enabled Enable the Wi-Fi node (ESP32 nodes)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Parool Network password
Ethernet lubatud Use a wired connection on hardware that has one
IPv4 režiim DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP levitamine Share mesh traffic with other nodes over the local network
NTP server Time synchronization server
rsyslog server Kauglogimise server

Network Config with a static IPv4 address entered

Sinihamba sätted

On Settings → Device configuration → Bluetooth, on nodes with Bluetooth.

Sätted Kirjeldus
Sinihammas lubatud Enable/disable BLE radio
Sidumine Määratud PIN kood, juhuslik PIN kood või PIN koodi pole
Fikseeritud PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Turva sätted

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

Sätted Kirjeldus
Avalik võti Sinu sõlme avalik võti (kirjutuskaitstud)
Administraatori võti Keys permitted to administer this node remotely — up to three
Salajane võti Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it
Loo uus privaatvõti Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin kanal lubatud ⚠️ Eemaldatud — nüüd seadistatakse automaatselt, kui administraatori võti on määratud
Jadapordi konsool Serial console over the Stream API
Silumislogi API lubatud Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth
Hallatud režiim Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set
Taastevõtmed Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Taasta võtmed Kirjuta varundatud võtmed tagasi sõlme (saadaval siis, kui varukoopia on olemas)
Kustuta taastevõtmed Remove the stored key backup from this phone
Kaitsetase How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Käivitusi alles How many device boots the unlocked state survives
Tunde kuni kehtivusaja lõpuni Wall-clock lifetime of the unlocked state
Seansi limiit (minutid) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.

Seotud teemad

diff --git a/main/fi-rFI/user/discovery.html b/main/fi-rFI/user/discovery.html index cde35de94b..b708b10680 100644 --- a/main/fi-rFI/user/discovery.html +++ b/main/fi-rFI/user/discovery.html @@ -5,4 +5,4 @@ ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) -

Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:.

Mitä kannattaa tarkkailla Mitä se tarkoittaa
All hops show Good SNR (green) Hyvä reitti — viestit kulkevat luotettavasti
One hop shows a poor SNR (orange or red) Heikko yhteys — tämä välityssegmentti on haavoittuva
Useita hyppyjä (4+) Pitkä reitti — harkitse radion siirtämistä sen lyhentämiseksi
Eri reitti uudelleenyrityksellä Verkko mukautuu — useita reittejä on olemassa (tämä on hyvä!)

Vinkki: Aja reitinselvitys useita kertoja muutaman minuutin aikana. Jos reitti muuttuu, verkossasi on varareittejä — merkki hyvin kytketystä verkosta.

Reitinselvityksen vianmääritys

  • No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Varmista, että molemmat radiot jakavat vähintään yhden kanavan samalla salausavaimella.
  • Reitinselvitys aikakatkaistu — reitti voi olla liian pitkä (ylittää hyppymäärärajan) tai välittäjä-radio on ruuhkautunut. Try increasing the hop limit in Settings → LoRa.
  • Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position.
  • Epäsymmetriset reitit — reitinselvitys A→B voi kulkea eri reittiä kuin B→A. This is normal — radio propagation isn’t always symmetric.

Naapuritieto

Naapuritieto-moduuli antaa jokaisen radion lähettää listan radioista, jotka se voi kuulla suoraan (yhden hypyn päässä). Kun useat radiot jakavat naapurilistansa, voit muodostaa koko verkon topologian kartan.

Naapuritiedon käyttöönotto

  1. Navigate to Settings → Module configuration → Neighbor Info.
  2. Ota moduuli käyttöön.
  3. Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
  4. Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air.

Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Myös muut radiot, joissa naapuritieto on käytössä, toimivat samalla tavalla.

Viewing neighbor data

  • Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors.
  • Jokainen naapurimerkintä näyttää radion, joka on kuultu suoraan, sekä sen signaalilaadun.
  • Yhdistä naapuritiedot useista radioista ymmärtääksesi koko mesh-verkon topologian.

ℹ️ Huomautus: Naapuritieto lisää lähetysaikaa, koska jokainen toiminnon ottanut radio lähettää säännöllisesti naapuriluettelonsa. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further.

Node list as a discovery tool

Radiolista on itsessään tehokas hakutyökalu, kun käytät sen suodatus- ja lajitteluominaisuuksia oikein.

Finding new nodes

  • Lajittele Viimeksi kuultu nähdäksesi viimeksi aktiiviset radiot ylimpänä.
  • Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes.

Assessing connectivity

  • Lajittele Hyppyjen määrä nähdäksesi mitkä radiot ovat suoraan tavoitettavissa (0 hyppyä) ja mitkä välitettyinä.
  • Lajittele Etäisyys löytääksesi lähellä olevat radiot ja varmistaaksesi niiden tavoitettavuuden.
  • Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge).

Infrastructure audit

  • Poista Jätä infrastruktuuri pois käytöstä, jos haluat nähdä Router-, Router Late- ja Client Base -radiot.
  • Tarkista niiden signaalin laatu ja viimeksi kuultu -ajat varmistaaksesi, että infrastruktuuriradiot ovat kunnossa.

Katso Radiot saadaksesi lisätietoa suodatus- ja lajitteluasetuksista.

Tips for Mesh exploration

  • Aloita reitinselvityksellä — se antaa välittömän ja käytännöllisen tiedon yksittäisestä reitistä.
  • Ota naapuritieto käyttöön keskeisissä radioissa — erityisesti reitittimissä ja toistimissa, jotta saat näkyvyyden runkoverkkoon.
  • Tarkista kartta — Kartta yhdessä signaalitiedon kanssa auttaa ymmärtämään, miksi jotkin yhteydet ovat vahvoja ja toiset heikkoja.
  • Seuraa signaalin muutoksia ajan kuluessa — käytä Signaalimittari -opasta tulkitaksesi SNR- ja RSSI-arvot oikein.

Aiheeseen liittyvät aiheet

+

Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:.

Mitä kannattaa tarkkailla Mitä se tarkoittaa
All hops show Good SNR (green) Hyvä reitti — viestit kulkevat luotettavasti
One hop shows a poor SNR (orange or red) Heikko yhteys — tämä välityssegmentti on haavoittuva
Useita hyppyjä (4+) Pitkä reitti — harkitse radion siirtämistä sen lyhentämiseksi
Eri reitti uudelleenyrityksellä Verkko mukautuu — useita reittejä on olemassa (tämä on hyvä!)

Vinkki: Aja reitinselvitys useita kertoja muutaman minuutin aikana. Jos reitti muuttuu, verkossasi on varareittejä — merkki hyvin kytketystä verkosta.

Reitinselvityksen vianmääritys

  • No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Varmista, että molemmat radiot jakavat vähintään yhden kanavan samalla salausavaimella.
  • Reitinselvitys aikakatkaistu — reitti voi olla liian pitkä (ylittää hyppymäärärajan) tai välittäjä-radio on ruuhkautunut. Try increasing the hop limit in Settings → LoRa.
  • Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position.
  • Epäsymmetriset reitit — reitinselvitys A→B voi kulkea eri reittiä kuin B→A. This is normal — radio propagation isn’t always symmetric.

Naapuritieto

Naapuritieto-moduuli antaa jokaisen radion lähettää listan radioista, jotka se voi kuulla suoraan (yhden hypyn päässä). Kun useat radiot jakavat naapurilistansa, voit muodostaa koko verkon topologian kartan.

Naapuritiedon käyttöönotto

  1. Navigate to Settings → Module configuration → Neighbor Info.
  2. Ota moduuli käyttöön.
  3. Set Update Interval. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
  4. Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air.

Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Myös muut radiot, joissa naapuritieto on käytössä, toimivat samalla tavalla.

Viewing neighbor data

  • Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors.
  • Jokainen naapurimerkintä näyttää radion, joka on kuultu suoraan, sekä sen signaalilaadun.
  • Yhdistä naapuritiedot useista radioista ymmärtääksesi koko mesh-verkon topologian.

ℹ️ Huomautus: Naapuritieto lisää lähetysaikaa, koska jokainen toiminnon ottanut radio lähettää säännöllisesti naapuriluettelonsa. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further.

Node list as a discovery tool

Radiolista on itsessään tehokas hakutyökalu, kun käytät sen suodatus- ja lajitteluominaisuuksia oikein.

Finding new nodes

  • Lajittele Viimeksi kuultu nähdäksesi viimeksi aktiiviset radiot ylimpänä.
  • Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes.

Assessing connectivity

  • Lajittele Hyppyjen määrä nähdäksesi mitkä radiot ovat suoraan tavoitettavissa (0 hyppyä) ja mitkä välitettyinä.
  • Lajittele Etäisyys löytääksesi lähellä olevat radiot ja varmistaaksesi niiden tavoitettavuuden.
  • Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge).

Infrastructure audit

  • Poista Jätä infrastruktuuri pois käytöstä, jos haluat nähdä Router-, Router Late- ja Client Base -radiot.
  • Tarkista niiden signaalin laatu ja viimeksi kuultu -ajat varmistaaksesi, että infrastruktuuriradiot ovat kunnossa.

Katso Radiot saadaksesi lisätietoa suodatus- ja lajitteluasetuksista.

Tips for Mesh exploration

  • Aloita reitinselvityksellä — se antaa välittömän ja käytännöllisen tiedon yksittäisestä reitistä.
  • Ota naapuritieto käyttöön keskeisissä radioissa — erityisesti reitittimissä ja toistimissa, jotta saat näkyvyyden runkoverkkoon.
  • Tarkista kartta — Kartta yhdessä signaalitiedon kanssa auttaa ymmärtämään, miksi jotkin yhteydet ovat vahvoja ja toiset heikkoja.
  • Seuraa signaalin muutoksia ajan kuluessa — käytä Signaalimittari -opasta tulkitaksesi SNR- ja RSSI-arvot oikein.

Aiheeseen liittyvät aiheet

diff --git a/main/fi-rFI/user/mqtt.html b/main/fi-rFI/user/mqtt.html index 5de4533b73..af08db566e 100644 --- a/main/fi-rFI/user/mqtt.html +++ b/main/fi-rFI/user/mqtt.html @@ -1,2 +1,2 @@ MQTT | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Suomi
Meshtastic Docs ↗

🌐 Suomi — Community translation View in English

MQTT

MQTT yhdistää Meshtastic-mesh-verkkosi internetiin ja mahdollistaa pitkän kantaman viestinnän radioalueen ulkopuolella.

Yleiskatsaus

MQTT-moduuli yhdistää radion MQTT-välityspalvelimeen, mahdollistaen:

  • Viestien välittymisen eri fyysisten mesh-verkkojen välillä internetin kautta
  • Integraation kotiautomaatio- ja valvontajärjestelmiin
  • Radioiden sijaintien julkaisemisen julkiseen Meshtastic-karttaan
  • Mukautetut dataputket tiedonkeruuta ja hälytyksiä varten

Kuinka se toimii 

[Oma radio] → Radio → [Yhdyskäytäväradio, jossa WiFi] → MQTT-välityspalvelin → [Etäyhdyskäytävä] → Radio → [Etäradio]
-

Internet-yhteydellä varustettu yhdyskäytäväradio (WiFi tai Ethernet) julkaisee mesh-verkon viestejä MQTT-aiheeseen. Etä-yhdyskäytävät, jotka ovat tilanneet saman aiheen, syöttävät viestit omaan paikalliseen mesh-verkkoonsa.

Asetukset

MQTT:n käyttöönotto

  1. Navigate to Settings → Module configuration → MQTT.
  2. Ota MQTT-moduuli käyttöön.
  3. Määritä välityspalvelimen yhteys:
Asetus Kuvaus Oletus
Address MQTT-välityspalvelimen osoite mqtt.meshtastic.org
Username Välityspalvelimen tunnistautuminen meshdev
Password Välityspalvelimen tunnistautuminen large4cats
Root topic Viestien perusaihe msh, which the radio rewrites to msh/<REGION> once you set a region
Encryption enabled MQTT-viestisisällön salaus Käytössä
JSON output enabled Julkaise ja vastaanota myös /2/json/-aihetta. Merkitty protobuf-rakenteessa vanhentuneeksi, mutta tämä on edelleen ainoa asetus tähän toimintaan — ja sovelluksen oma välityspalvelin käyttää sitä Ei käytössä
TLS enabled Yhteyden suojaaminen välityspalvelimeen Ei käytössä
Map reporting Sijainnin julkaisu julkiselle kartalle Ei käytössä
Proxy to client enabled Relay MQTT through the connected phone Ei käytössä

Yhteyden tila ja testaa yhteys

The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here.

Testaa yhteys tarkistaa välityspalvelimen ennen asetusten tallentamista radioon ja erottaa eri virhetilanteet: palvelinnimen selvitys epäonnistui, TCP-yhteys hylättiin, TLS epäonnistui, yritys aikakatkaistiin tai välityspalvelin hylkäsi tunnistetietosi syyn kera.

MQTT-välityspalvelin tässä puhelimessa

Jos radiollasi ei ole omaa internetyhteyttä, se voi käyttää yhdistettyä puhelinta MQTT-yhdyskäytävänään: ota moduulin asetuksista käyttöön MQTT ja Välityspalvelin käytössä, jolloin sovellus välittää MQTT-liikenteen radion ja välityspalvelimen välillä puhelimesi internetyhteyden kautta.

ℹ️ Huomautus: MQTT-välitys toimii vain mobiilisovelluksessa. Työpöytäsovelluksessa MQTT-asetukset ovat käytettävissä, mutta niiden taustalla ei ole välityspalvelua.

MQTT-asetusten yläreunassa oleva MQTT-välityspalvelin tällä puhelimella -kytkin näyttää, onko tämä välitys käytössä, ja sen avulla voit pysäyttää sen (tai käynnistää sen uudelleen) heti ilman, että radion MQTT-asetuksia tarvitsee muokata tai tallentaa uudelleen.

Oletus Meshtastic-välityspalvelin

Yhteisö ylläpitää julkista välityspalvelinta osoitteessa mqtt.meshtastic.org. Tämä on tarkoitettu yleiseen käyttöön ja testaukseen.

When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without).

🔒 Tietosuoja: Julkisen välityspalvelimen viestit ovat kaikkien tilaajien luettavissa. Käytä aina kanavasalausta yksityiseen viestintään.

Oma välityspalvelin

Parempaa yksityisyyttä ja hallintaa varten voit käyttää omaa MQTT-välityspalvelinta:

  • Mosquitto (kevyt, avoimen lähdekoodin)
  • HiveMQ
  • EMQX

Määritä radiosi osoittamaan omaan välityspalvelimeesi oikeilla tunnistetiedoilla.

Karttaraportointi

When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.

Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.

Reports appear at meshmap.net and similar community map services.

🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published.

Lähetys vs vastaanotto

Suunta Kuvaus
Lähetys Viestit mesh-verkosta → MQTT-välityspalvelimeen
Vastaanotto Viestit MQTT-välityspalvelimesta → mesh-verkkoon

Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on.

Viestiformaatit

MQTT käyttää kahta viestisisällön muotoa:

Muoto Kuvaus Käyttötarkoitus
Protobuf Binäärinen Meshtastic protobuf -enkoodaus Radioiden välinen mesh-siltaus
JSON Ihmisen luettavissa oleva JSON /2/json/-aiheessa Mesh-verkon ulkopuolisille sovelluksille (hallintapaneelit, kotiautomaatio)

ℹ️ Huomautus: json_enabled on merkitty protobuf-rakenteessa vanhentuneeksi, mutta sitä ei ole korvattu eikä sitä ohiteta. Kun tämä on käytössä, sovelluksen oma MQTT-välityspalvelin tilaa /2/json/-aiheen ja purkaa sen viestisisällöt.

Salaus ja yksityisyys

Kerrostetun salausmallin ymmärtäminen:

  1. Kanavasalaus tapahtuu meshissä ennen MQTT:tä. Jos kanavallasi on PSK, MQTT-viestisisältö on jo salattu — välityspalvelin ja tilaajat näkevät vain salatun datan.
  2. Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard.
  3. TLS salaa TCP-yhteyden itse välityspalvelimeen estäen verkkotason salakuuntelun.

🔒 Tietoturva: Oletusjulkisella kanavalla on tunnettu avain. Oletuskanavan MQTT:n kautta lähetetyt viestit ovat käytännössä salaamattomia — kuka tahansa tilaaja voi purkaa ne. Käytä aina omaa PSK-avainta yksityiseen viestintään.

Parhaat käytännöt

  • Käytä kanavatasoista salausta (PSK) kanavissa, jotka yhdistetään MQTT:hen
  • Älä ota MQTT:tä käyttöön radioissa, joilla ei ole internetyhteyttä (radio puskuroi lähettämättä jääneet viestit ja tuhlaa muistia)
  • Käytä yksityistä välityspalvelinta arkaluonteisissa käyttöönotossa
  • Ole tarkkana lähetysajan (downlink) käyttämisessä ruuhkaisissa MQTT-aiheissa — jokainen viesti kuluttaa radio-aikaa paikallisessa meshissä
  • Harkitse lähetyssuunnan vaihtamista (uplink), jos haluat vain seurata verkkoa etänä ilman viestien lähettämistä verkkoon

Vianetsintä

MQTT ei yhdistä

  • Tarkista WiFi — yhdyskäytäväradiolla on oltava toimiva internetyhteys (WiFi tai Ethernet). MQTT ei toimi LoRa-radiolinkin kautta.
  • Tarkista tunnistetiedot — virheellisillä tunnistetiedoilla useimmat välityspalvelimet epäonnistuvat ilman virheilmoitusta — tarkista erityisesti lopussa olevat välilyönnit.
  • Palomuuri — portin 1883 (MQTT) tai 8883 (MQTT TLS:n kautta) on oltava saavutettavissa. Joissakin verkoissa sallitaan vain verkkoliikenne (portit 80 ja 443).
  • DNS-ratkaisu – jos käytät omaa välityspalvelimen isäntänimeä, varmista että laite pystyy ratkaisemaan sen. Kokeile välityspalvelimen IP-osoitetta suoraan.

Viestit eivät välity

  • Tarkista lähetys ja vastaanotto-asetukset – jos vain lähetys on käytössä, viestit kulkevat meshistä MQTT:hen mutta eivät takaisin. Ota vastaanotto käyttöön vastaanottavassa yhdyskäytävän laitteessa.
  • Kanava ei täsmää – molempien gateway-laitteiden täytyy käyttää samaa kanavaa ja samaa PSK-avainta. Eroavaisuus tarkoittaa, että viestit on salattu eri avaimilla ja näyttävät roskalta.
  • Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root.
  • Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway.
  • Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in.

Aiheeseen liittyvät aiheet

+

Internet-yhteydellä varustettu yhdyskäytäväradio (WiFi tai Ethernet) julkaisee mesh-verkon viestejä MQTT-aiheeseen. Etä-yhdyskäytävät, jotka ovat tilanneet saman aiheen, syöttävät viestit omaan paikalliseen mesh-verkkoonsa.

Asetukset

MQTT:n käyttöönotto

  1. Navigate to Settings → Module configuration → MQTT.
  2. Ota MQTT-moduuli käyttöön.
  3. Määritä välityspalvelimen yhteys:
Asetus Kuvaus Oletus
Address MQTT-välityspalvelimen osoite mqtt.meshtastic.org
Username Välityspalvelimen tunnistautuminen meshdev
Password Välityspalvelimen tunnistautuminen large4cats
Root topic Viestien perusaihe msh, which the radio rewrites to msh/<REGION> once you set a region
Encryption enabled MQTT-viestisisällön salaus Käytössä
JSON output enabled Julkaise ja vastaanota myös /2/json/-aihetta. Merkitty protobuf-rakenteessa vanhentuneeksi, mutta tämä on edelleen ainoa asetus tähän toimintaan — ja sovelluksen oma välityspalvelin käyttää sitä Ei käytössä
TLS enabled Yhteyden suojaaminen välityspalvelimeen Ei käytössä
Map reporting Sijainnin julkaisu julkiselle kartalle Ei käytössä
Proxy to client enabled Relay MQTT through the connected phone Ei käytössä

Yhteyden tila ja testaa yhteys

The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here.

Testaa yhteys tarkistaa välityspalvelimen ennen asetusten tallentamista radioon ja erottaa eri virhetilanteet: palvelinnimen selvitys epäonnistui, TCP-yhteys hylättiin, TLS epäonnistui, yritys aikakatkaistiin tai välityspalvelin hylkäsi tunnistetietosi syyn kera.

MQTT-välityspalvelin tässä puhelimessa

Jos radiollasi ei ole omaa internetyhteyttä, se voi käyttää yhdistettyä puhelinta MQTT-yhdyskäytävänään: ota moduulin asetuksista käyttöön MQTT ja Välityspalvelin käytössä, jolloin sovellus välittää MQTT-liikenteen radion ja välityspalvelimen välillä puhelimesi internetyhteyden kautta.

ℹ️ Huomautus: MQTT-välitys toimii vain mobiilisovelluksessa. Työpöytäsovelluksessa MQTT-asetukset ovat käytettävissä, mutta niiden taustalla ei ole välityspalvelua.

MQTT-asetusten yläreunassa oleva MQTT-välityspalvelin tällä puhelimella -kytkin näyttää, onko tämä välitys käytössä, ja sen avulla voit pysäyttää sen (tai käynnistää sen uudelleen) heti ilman, että radion MQTT-asetuksia tarvitsee muokata tai tallentaa uudelleen.

Oletus Meshtastic-välityspalvelin

Yhteisö ylläpitää julkista välityspalvelinta osoitteessa mqtt.meshtastic.org. Tämä on tarkoitettu yleiseen käyttöön ja testaukseen.

When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without).

🔒 Tietosuoja: Julkisen välityspalvelimen viestit ovat kaikkien tilaajien luettavissa. Käytä aina kanavasalausta yksityiseen viestintään.

Oma välityspalvelin

Parempaa yksityisyyttä ja hallintaa varten voit käyttää omaa MQTT-välityspalvelinta:

  • Mosquitto (kevyt, avoimen lähdekoodin)
  • HiveMQ
  • EMQX

Määritä radiosi osoittamaan omaan välityspalvelimeesi oikeilla tunnistetiedoilla.

Karttaraportointi

When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.

Turning it on opens a consent card. Turn on I agree. and choose a Map Publish Interval of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.

Reports appear at meshmap.net and similar community map services.

🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published.

Lähetys vs vastaanotto

Suunta Kuvaus
Lähetys Viestit mesh-verkosta → MQTT-välityspalvelimeen
Vastaanotto Viestit MQTT-välityspalvelimesta → mesh-verkkoon

Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on.

Viestiformaatit

MQTT käyttää kahta viestisisällön muotoa:

Muoto Kuvaus Käyttötarkoitus
Protobuf Binäärinen Meshtastic protobuf -enkoodaus Radioiden välinen mesh-siltaus
JSON Ihmisen luettavissa oleva JSON /2/json/-aiheessa Mesh-verkon ulkopuolisille sovelluksille (hallintapaneelit, kotiautomaatio)

ℹ️ Huomautus: json_enabled on merkitty protobuf-rakenteessa vanhentuneeksi, mutta sitä ei ole korvattu eikä sitä ohiteta. Kun tämä on käytössä, sovelluksen oma MQTT-välityspalvelin tilaa /2/json/-aiheen ja purkaa sen viestisisällöt.

Salaus ja yksityisyys

Kerrostetun salausmallin ymmärtäminen:

  1. Kanavasalaus tapahtuu meshissä ennen MQTT:tä. Jos kanavallasi on PSK, MQTT-viestisisältö on jo salattu — välityspalvelin ja tilaajat näkevät vain salatun datan.
  2. Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard.
  3. TLS salaa TCP-yhteyden itse välityspalvelimeen estäen verkkotason salakuuntelun.

🔒 Tietoturva: Oletusjulkisella kanavalla on tunnettu avain. Oletuskanavan MQTT:n kautta lähetetyt viestit ovat käytännössä salaamattomia — kuka tahansa tilaaja voi purkaa ne. Käytä aina omaa PSK-avainta yksityiseen viestintään.

Parhaat käytännöt

  • Käytä kanavatasoista salausta (PSK) kanavissa, jotka yhdistetään MQTT:hen
  • Älä ota MQTT:tä käyttöön radioissa, joilla ei ole internetyhteyttä (radio puskuroi lähettämättä jääneet viestit ja tuhlaa muistia)
  • Käytä yksityistä välityspalvelinta arkaluonteisissa käyttöönotossa
  • Ole tarkkana lähetysajan (downlink) käyttämisessä ruuhkaisissa MQTT-aiheissa — jokainen viesti kuluttaa radio-aikaa paikallisessa meshissä
  • Harkitse lähetyssuunnan vaihtamista (uplink), jos haluat vain seurata verkkoa etänä ilman viestien lähettämistä verkkoon

Vianetsintä

MQTT ei yhdistä

  • Tarkista WiFi — yhdyskäytäväradiolla on oltava toimiva internetyhteys (WiFi tai Ethernet). MQTT ei toimi LoRa-radiolinkin kautta.
  • Tarkista tunnistetiedot — virheellisillä tunnistetiedoilla useimmat välityspalvelimet epäonnistuvat ilman virheilmoitusta — tarkista erityisesti lopussa olevat välilyönnit.
  • Palomuuri — portin 1883 (MQTT) tai 8883 (MQTT TLS:n kautta) on oltava saavutettavissa. Joissakin verkoissa sallitaan vain verkkoliikenne (portit 80 ja 443).
  • DNS-ratkaisu – jos käytät omaa välityspalvelimen isäntänimeä, varmista että laite pystyy ratkaisemaan sen. Kokeile välityspalvelimen IP-osoitetta suoraan.

Viestit eivät välity

  • Tarkista lähetys ja vastaanotto-asetukset – jos vain lähetys on käytössä, viestit kulkevat meshistä MQTT:hen mutta eivät takaisin. Ota vastaanotto käyttöön vastaanottavassa yhdyskäytävän laitteessa.
  • Kanava ei täsmää – molempien gateway-laitteiden täytyy käyttää samaa kanavaa ja samaa PSK-avainta. Eroavaisuus tarkoittaa, että viestit on salattu eri avaimilla ja näyttävät roskalta.
  • Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root.
  • Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway.
  • Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in.

Aiheeseen liittyvät aiheet

diff --git a/main/fi-rFI/user/settings-module-admin.html b/main/fi-rFI/user/settings-module-admin.html index 992b5ad0dc..7d061d0781 100644 --- a/main/fi-rFI/user/settings-module-admin.html +++ b/main/fi-rFI/user/settings-module-admin.html @@ -1 +1 @@ - Asetukset — Moduulit ja ylläpito | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Suomi
Meshtastic Docs ↗

🌐 Suomi — Community translation View in English

Asetukset — Moduulit ja ylläpito

Määritä valinnaiset ominaisuusmoduulit ja suorita laitteen ylläpitotoimia. Moduulit laajentavat Meshtasticia erikoisominaisuuksilla — jokainen voidaan ottaa käyttöön tai poistaa käytöstä erikseen.

💡 Vinkki: Ota käyttöön vain ne moduulit, joita todella käytät. Käyttämättömien moduulien poistaminen käytöstä vähentää lähetyksen käyttöastetta, säästää akkua ja yksinkertaistaa määrityksiä. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.

Moduuliasetukset käyttävät korttipohjaista asettelua, jossa on kytkimiä, pudotusvalikoita, tekstikenttiä ja liukusäätimiä:

Kytkinasetus käytössä-asennossa

Pudotusvalikkoasetus avattuna näyttämään vaihtoehtoluettelonsa

A text field setting with a value entered

A module settings card with its title and grouped controls

Moduulin asetukset

Every module lives under Settings → Module configuration.

⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes.

MQTT module

Yhdistää verkon viestejä MQTT-välityspalvelimeen ja sieltä takaisin internet-yhteyksiä varten. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.

Asetus Kuvaus
MQTT käytössä Ota MQTT-välityspalvelin käyttöön
Osoite MQTT-välityspalvelimen osoite
Käyttäjänimi Todennuksen käyttäjätunnus
Salasana Todennuksen salasana
Salaus käytössä Salaa MQTT-viestisisällöt
JSON ulostulo käytössä Julkaise ja vastaanota MQTT-viestejä JSON-muodossa. Merkitty protobuf-rakenteessa vanhentuneeksi, mutta tämä on edelleen ainoa asetus tähän toimintaan, ja laiteohjelmisto käyttää sitä yhä
TLS käytössä Käytä suojattua yhteyttä
Palvelimen osoite (root topic) MQTT:n perusaihepolku
Välityspalvelin käytössä Anna yhdistetyn puhelimen välittää radion MQTT-liikenne sen sijaan, että radio muodostaisi itse yhteyden välityspalvelimeen
MQTT-välityspalvelin tällä puhelimella Yllä olevan Välitys asiakkaalle käytössä -asetuksen puhelinpään osuus: käyttääkö tämä puhelin kyseistä välitystä. Katso MQTT
Karttaraportointi Publish position to the public map — see the Map reporting group that follows

Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:

Asetus Kuvaus
Hyväksyn. Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Karttaraportoinnin aikaväli (sekuntia) Kuinka usein sijainti julkaistaan. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered

Katso MQTT saadaksesi yksityiskohtaisen käyttöoppaan, joka sisältää salauksen, tietosuojan ja välityspalvelimen määrityksen.

Serial module

Mahdollistaa sarjaporttiviestinnän ulkoisten laiteintegraatioiden kanssa (GPS-moduulit, anturit tai mukautettu laitteisto). Kun tämä on käytössä, radion sarjaportti voi lähettää ja vastaanottaa protobuf- tai tekstimuotoista dataa, jolloin ulkoiset mikrokontrollerit tai tietokoneet voivat olla vuorovaikutuksessa verkon kanssa.

Asetus Kuvaus
Sarjaportti käytössä Ota sarjaporttiviestintä käyttöön
Palautus päällä Toista vastaanotettu sarjaporttidata takaisin
Sarjaportin tila Portin käyttämä protokolla – Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, YE.Direct, MeshSolar config, Log tai Log (vain teksti)
Vastaanotto / lähetys Sarjayhteyden GPIO-nastat
Sarjaportin nopeus Portin nopeus
Aikakatkaisu Kuinka kauan odotetaan ennen kuin saapuva viesti katsotaan kokonaiseksi
Korvaa konsolin sarjaportti Ota käyttöön portti, jota virheenkorjauskonsoli normaalisti käyttää

External Notification module

Controls buzzer, LED, or vibration alerts on your node hardware. Hyödyllinen laitteille, joiden täytyy ilmoittaa fyysisesti viestin saapumisesta — erityisen hyödyllinen valvomattomissa tai ulkokäyttöön asennetuissa laitteissa.

Käynnistimiä on kaksi – saapuva viesti ja vastaanotettu BEL-ohjausmerkki – ja kumpikin voi ohjata LED-valoa, summeria ja värinämoottoria erikseen, joten käytettävissä on kuusi kytkintä.

Asetus Kuvaus
Ulkoiset ilmoitukset käytössä Moduulin pääkytkin
Hälytysviesti: LED / summeri / värinä Mitkä lähdöt aktivoituvat saapuvasta viestistä
Hälytysmerkki: LED / summeri / värinä Mitkä lähdöt aktivoituvat vastaanotetusta BEL-ohjausmerkistä
Ulostulon LED (GPIO) LED on kytketty nastaan
Ulostulon LED aktiivinen Onko LED-nasta aktiivinen korkealla vai matalalla tasolla
Ulostulon äänimerkki (GPIO) Summeri on kytketty nastaan
Ulostulon värinä (GPIO) Värinämoottori on kytketty nastaan
Käytä PWM-äänimerkkiä Ohjaa summeria PWM:llä, jolloin voidaan toistaa ääniä yhden kiinteän taajuuden sijaan
Käytä I2S protokollaa äänimerkille Lähetä hälytys sen sijaan I2S-äänilähdön kautta
Ulostulon kesto (millisekuntia) Kuinka kauan yksittäinen hälytys kestää
Hälytysaikakatkaisu (sekuntia) Toista hälytystä tämän ajan, kunnes se kuitataan. 0 poistaa toistuvan muistutuksen käytöstä
Soittoääni PWM-summerilla toistettava RTTTL-soittoääni. Voidaan tuoda tiedostosta

Store & Forward module

Puskuroi viestejä radioille, jotka ovat tilapäisesti poissa verkosta, ja toimittaa ne, kun nämä radiot yhdistyvät uudelleen. Välttämätön verkoissa, joissa radiot siirtyvät säännöllisesti kuuluvuusalueelle ja sen ulkopuolelle — varmistaa, etteivät viestit katoa lyhyiden yhteyskatkosten aikana.

Asetus Kuvaus
Tallenna ja lähetä edelleen Ota Varastoi & välitä käyttöön
Valvontasignaali Ilmoita tämän radion varastoi & välitä -ominaisuudesta säännöllisesti
Kirjausten määrä Tallennettujen viestien enimmäismäärä
Historian maksimimäärä Toistettavien viestien enimmäismäärä
Historian aikamäärä Aikaikkuna viestien toistolle
Palvelin Toimi mesh-verkon varastoi & välitä -palvelimena (edellyttää riittävästi muistia, esimerkiksi ESP32 PSRAM:lla)

💡 Vinkki: Varastoi & välitä toimii parhaiten radioissa, joissa on runsaasti muistia (ESP32 ja PSRAM). Router-roolin radiot ovat ihanteellisia ehdokkaita, koska ne ovat yleensä jatkuvasti käynnissä.

Range Test module

⚠️ Varoitus: Kuuluvuustesti toimii vain suojatulla ensisijaisella kanavalla. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.

Automaattinen kuuluvuustestityökalu radioiden välisen yhteyden laadun arviointiin. Kun toiminto on käytössä, radio lähettää säännöllisesti testiviestejä kasvavilla laskuriarvoilla. Vastaanottava radio kirjaa nämä viestit, jolloin voit myöhemmin kävellä tai ajaa pois ja analysoida, millä etäisyydellä viestien saapuminen loppui.

Asetus Kuvaus
Kuuluvuustesti käytössä Ota kuuluvuustesti käyttöön
Viestien lähetyksen aikaväli (sekuntia) Time between test transmissions, chosen from a dropdown of fixed intervals
Tallenna .CSV (ESP32 ainoastaan) Log received test data to the node’s own filesystem. ESP32 hardware only

Telemetry module

Määrittää, mitä telemetriatietoja radiosi jakaa verkkoon. Telemetria sisältää laitteen kuntoon liittyviä tietoja (akun varaustaso, käyttöaika) sekä ympäristöanturien tietoja (lämpötila, kosteus, ilmanpaine).

Jokaisella neljällä mittausryhmällä on oma käyttöönottokytkin ja oma mittausväli, joten esimerkiksi akun tila voidaan raportoida usein ja anturitiedot harvemmin.

Asetus Kuvaus
Lähetä laitteen telemetriatiedot Laitemittausten pääkytkin. Näkyy vain laiteohjelmistoversiossa 2.7.12 ja uudemmissa
Laitemittareiden päivitysväli How often to report battery, uptime and channel utilization
Ympäristötietojen moduuli käytössä Raportoi liitettyjen ympäristöanturien tiedot
Ympäristömittareiden päivitysväli Kuinka usein tiedot raportoidaan
Näytä ympäristötiedot näytöllä Näytä nämä tiedot myös radion omalla näytöllä
Käytä Fahrenheit yksikköä Käytä radion näytössä Fahrenheit-asteita. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Ilmanlaadun tietojen moduuli käytössä Raportoi hiukkas- ja CO₂-anturin tiedot
Ilmanlaatumittareiden päivitysväli Kuinka usein tiedot raportoidaan
Virrankulutuksen moduuli käytössä Raportoi kanavakohtaiset jännite- ja virtamittaukset
Virtamittareiden päivitysväli Kuinka usein tiedot raportoidaan
Virrankulutuksen näyttö käytössä Näytä virtamittaukset myös radion omalla näytöllä

Katso Telemetria ja anturit saadaksesi tietoa tuetuista antureista ja määrityssuosituksista.

Canned Message module

Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Määritä luettelo pikaviesteistä, jotka voidaan lähettää ilman yhdistettyä puhelinta — ihanteellinen kenttäkäyttöön.

Asetus Kuvaus
Valmisviesti käytössä ⚠️ Vanhentunut protobuf-rakenteessa
Viestit Rivinvaihdoilla eroteltu viestiluettelo
Lähetä äänimerkki Lähetä viestin mukana BEL-ohjausmerkki, jotta vastaanottavan radion Ulkoiset ilmoitukset -moduuli voi antaa hälytyksen
Kiertovalitsin #1 käytössä Käytä kiertokoodainta syöttölaitteena
GPIO pin for rotary encoder A / B / Press port Kolme nastaa, joihin kiertokoodain on kytketty
Generate input event on Press / CW / CCW Minkä näppäintapahtuman kukin kiertokoodaimen toiminto tuottaa
Ylös/Alas/Valitse syöte käytössä Erillinen, yksinkertaisempi syöttötapa, jossa käytetään ylös-/alas-/valitse-painikkeita kiertokoodaimen sijaan
Salli syöttölähde ⚠️ Vanhentunut protobuf-rakenteessa

Audio module

Codec2-äänituki matalan kaistanleveyden puheviestintään verkossa. Tämä on kokeellinen ominaisuus, joka koodaa puheen erittäin pieniksi datapaketeiksi käyttäen Codec2-koodekkia.

Asetus Kuvaus
CODEC 2 käytössä Ota äänimoduuli käyttöön
CODEC2 näytteenottotaajuus Äänenlaadun ja kaistanleveyden välinen kompromissi
PTT-pinni PTT-painikkeen GPIO-nasta
I2S-sanan valinta GPIO-pinni I2S WS:lle
I2S-datatulo GPIO-nasta I2S DIN:lle
I2S-datalähtö GPIO-pinni I2S DOUT:lle
I2S-kello I2S-bittikellon GPIO-nasta

ℹ️ Huomautus: Ääniominaisuus edellyttää yhteensopivaa laitteistoa (I2S-mikrofoni ja -kaiutin). Äänenlaatu on hyvin matalakaistainen — ajattele “ymmärrettävää radiopuhetta”, ei puhelinlaatua.

Remote Hardware module

GPIO-ohjaus mesh-verkon kautta. Mahdollistaa etäradion lukea tai kirjoittaa GPIO-nastoja toisessa radiossa — hyödyllinen releiden aktivointiin, kytkimien lukemiseen tai ulkoisen laitteiston ohjaamiseen etäältä.

⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.

Asetus Kuvaus
Etälaitteen ohjaus käytössä Ota etä-GPIO-käyttö käyttöön
Salli määrittämättömän pinnin käyttö Salli pääsy mihin tahansa GPIO-nastaan (tietoturvariski)
Käytettävissä olevat pinnit Enintään 4 tämän radion etälukuun tai kirjoitukseen tarjoamaa GPIO-pinniä

Neighbor Info module

Lähettää tietoa suoraan kuulluista naapureista mahdollistaen verkon topologian kartoituksen. Jokainen käyttöön otettu radio jakaa säännöllisesti luettelon muista radioista, jotka se kuulee, sekä niiden signaalin laadun.

Asetus Kuvaus
Naapuritiedot käytössä Ota naapuritiedon lähetys käyttöön
Päivityksen aikaväli (sekuntia) Kuinka usein naapuriluettelo lähetetään
Lähetä LoRa:n kautta Lähetä myös naapuritiedot LoRa:n kautta, ei pelkästään MQTT:n tai puhelimen kautta. Ei käytettävissä kanavalla, joka käyttää oletusavainta ja nimeä

Katso Paikallinen mesh-haku, miten naapuritietoja käytetään mesh-verkon rakenteen tutkimiseen.

Ambient Lighting module

Ohjaa tuetuissa laitteissa olevaa NeoPixeliä tai muita osoitteellisia RGB-LEDejä. Voidaan käyttää visuaalisina tilailmaisimina, ilmoitusvaloina tai koriste-efekteinä.

Asetus Kuvaus
LED-tila Kytke LED päälle tai pois päältä
Virta LED-virran rajoitus (0–31)
Punainen / vihreä / sininen Yksittäisten värikanavien arvot (0–255)

Detection Sensor module

Muuttaa radiosi liike- tai ovitunnistimeen perustuvaksi hälytysjärjestelmäksi. Kun GPIO-pinni havaitsee tilamuutoksen (liike havaittu, ovi avattu), radio lähettää hälytysviestin verkkoon.

Asetus Kuvaus
Tunnistinsensori käytössä Ota tunnistusanturi käyttöön
GPIO-pinni valvontaa varten Anturiin kytketty GPIO-pinni
Tunnistuksen tyyppi Miten pinnin tila vastaa havaitsemistapahtumaa (esim. aktiivinen korkea/matala taso tai reunalaukaisu)
Käytä INPUT_PULLUP tilaa Ota pinnin sisäinen ylösvetovastus käyttöön
Minimilähetys (sekuntia) Hälytyslähetysten vähimmäisaika
Tilatiedon lähetys (sekuntia) Tilatiedon lähetysväli
Lähetä äänimerkki hälytyssanoman kanssa Sisällytä soittomerkkimerkki hälytyksiin
Käyttäjäystävällinen nimi Tälle anturille määritetty nimi

Paxcounter module

Henkilöt, jotka lasketaan WiFi- ja BLE-hakukyselyiden perusteella. Laskee lähellä olevia laitteita kuuntelemalla passiivisesti koepyyntöjä, joita puhelimet ja kannettavat tietokoneet lähettävät etsiessään verkkoja. Saatavilla vain ESP32-laitteissa.

Asetus Kuvaus
PAX-laskuri käytössä Ota henkilölaskenta käyttöön
Päivityksen aikaväli (sekuntia) Kuinka usein laskentatiedot raportoidaan
WiFi-signaalin RSSI-kynnys Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE-signaalin RSSI-kynnys Sama raja-arvo BLE-mainospaketeille (oletus: -80 dBm)

💡 Vinkki: PAX-laskuri on hyödyllinen jalankulkijamäärien arviointiin retkeilyreittien lähtöpisteissä, tapahtumapaikoilla tai muissa kohteissa. Laskentatulokset ovat arvioita — yhdellä henkilöllä voi olla useita laitteita mukana.

Status Message module

Tilaviestillä ei ole omaa moduulinäkymää. Sitä muokataan yhdessä muiden radion tunnistetietojen kanssa kohdassa Asetukset → Radio ja käyttäjä.

Mesh Beacon module

Lähettää kutsun mesh-verkkoosi ja vastaanottaa muiden lähettämiä kutsuja. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.

TAK module

Team Awareness Kit -integraatio yhteensopivuutta varten ATAK- ja WinTAK-järjestelmien kanssa. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. Katso TAK-integraatio saadaksesi tarkemmat määritys- ja käyttöohjeet.

Ylläpito

Etähallinta

Määritä etänä radiot, jotka jakavat saman ylläpitoavaimen:

  1. Valitse kohderadio radioluettelosta.
  2. Siirry kyseisen radion Asetukset-kohtaan.
  3. Muokkaa määrityksiä.
  4. Napauta Tallenna — muutokset lähetetään verkon kautta.

⚠️ Tärkeää: Edellyttää, että järjestelmänvalvojan avain on määritetty sekä omassa radiossasi että kohderadiossa.

Device Actions

Settings → Administration holds five one-shot actions, each behind a confirmation dialog:

Toiminto Mitä se tekee
Aseta aika Sends your phone’s clock to the node
Käynnistä uudelleen Restarts the node
Sammuta Powers the node down
Palauta tehdasasetukset Returns every setting to its factory default
Tyhjennä NodeDB-tietokanta Clears the node database. This dialog carries a Preserve Favorites? switch

⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.

Varmuuskopiointi ja palautus

Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.

Lisäasetukset

Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.

Tyhjennä NodeDB-tietokanta

Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.

  • Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
  • Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.

The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.

Vianetsintäpaneeli

Avaa Paketit- ja Sovelluslokit-välilehdet diagnostiikkatietojen tarkastelua, suodatusta ja vientiä varten. Katso Virheenjäljityslokit, jossa on täydellinen käyttöohje.

App Settings

The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:

Privacy

  • Allow analytics and crash reporting — opt in or out of diagnostics.
  • Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
  • Homoglyph encoding — how look-alike characters in names are handled.

Appearance

  • Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
  • Theme and Language.
  • Show full message timestamps.

Persistence

  • A cache limit for how much history is kept.
  • Export rangetest packets, Export all packets and Export node database.

On their own

  • Node Layout — how much detail each row of the node list shows.
  • Wi-Fi Provisioning for mPWRD-OS — see Connections.
  • Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
  • System AI — appears only where app functions are available; see App Functions.

A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.

Tietoja

Settings → About carries the app’s own identity rather than the node’s:

Kolme osiota:

  • Mikä on Meshtastic? – lyhyt kuvaus projektista.
  • Sovellukset — avaa Tarvitsetko laitteiston? -näkymän, jossa on suosittujen laitteiden karuselli ja linkit niiden ostopaikkoihin. Siellä näytetään myös GitHub-tietovarasto, käytössä oleva sovellusversio ja Tekijätiedot (katso seuraava osio).
  • Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.

The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.

Kiitokset

Tietoja-kohdasta avattava näkymä, jossa luetellaan kaikki sovelluksen käyttämät avoimen lähdekoodin kirjastot lisensseineen. Luettelo luodaan käännöshetkellä AboutLibraries-kirjastolla. Tätä kutsuttiin aiemmin lisenssinäkymäksi.

Troubleshooting remote admin

  • Ei vastausta kohderadiolta — kohderadio voi olla kuuluvuusalueen ulkopuolella, poissa verkosta tai siinä voi olla eri ylläpitoavain. Varmista, että ylläpitoavain on sama molemmissa radioissa.
  • Muutokset eivät tule voimaan — jotkin asetukset edellyttävät uudelleenkäynnistystä ennen kuin ne astuvat voimaan. Kokeile Uudelleenkäynnistystä tallennuksen jälkeen.
  • Et näe etäasetuksia — varmista, että radiossasi on kohderadion ylläpitoavain. Ylläpitokanava määritetään automaattisesti, kun ylläpitoavain on asetettu.

Aiheeseen liittyvät aiheet

+ Asetukset — Moduulit ja ylläpito | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Suomi
Meshtastic Docs ↗

🌐 Suomi — Community translation View in English

Asetukset — Moduulit ja ylläpito

Määritä valinnaiset ominaisuusmoduulit ja suorita laitteen ylläpitotoimia. Moduulit laajentavat Meshtasticia erikoisominaisuuksilla — jokainen voidaan ottaa käyttöön tai poistaa käytöstä erikseen.

💡 Vinkki: Ota käyttöön vain ne moduulit, joita todella käytät. Käyttämättömien moduulien poistaminen käytöstä vähentää lähetyksen käyttöastetta, säästää akkua ja yksinkertaistaa määrityksiä. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.

Moduuliasetukset käyttävät korttipohjaista asettelua, jossa on kytkimiä, pudotusvalikoita, tekstikenttiä ja liukusäätimiä:

Kytkinasetus käytössä-asennossa

Pudotusvalikkoasetus avattuna näyttämään vaihtoehtoluettelonsa

A text field setting with a value entered

A module settings card with its title and grouped controls

Moduulin asetukset

Every module lives under Settings → Module configuration.

⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes.

MQTT module

Yhdistää verkon viestejä MQTT-välityspalvelimeen ja sieltä takaisin internet-yhteyksiä varten. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.

Asetus Kuvaus
MQTT käytössä Ota MQTT-välityspalvelin käyttöön
Osoite MQTT-välityspalvelimen osoite
Käyttäjänimi Todennuksen käyttäjätunnus
Salasana Todennuksen salasana
Salaus käytössä Salaa MQTT-viestisisällöt
JSON ulostulo käytössä Julkaise ja vastaanota MQTT-viestejä JSON-muodossa. Merkitty protobuf-rakenteessa vanhentuneeksi, mutta tämä on edelleen ainoa asetus tähän toimintaan, ja laiteohjelmisto käyttää sitä yhä
TLS käytössä Käytä suojattua yhteyttä
Palvelimen osoite (root topic) MQTT:n perusaihepolku
Välityspalvelin käytössä Anna yhdistetyn puhelimen välittää radion MQTT-liikenne sen sijaan, että radio muodostaisi itse yhteyden välityspalvelimeen
MQTT-välityspalvelin tällä puhelimella Yllä olevan Välitys asiakkaalle käytössä -asetuksen puhelinpään osuus: käyttääkö tämä puhelin kyseistä välitystä. Katso MQTT
Karttaraportointi Publish position to the public map — see the Map reporting group that follows

Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:

Asetus Kuvaus
Hyväksyn. Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval Kuinka usein sijainti julkaistaan. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered

Katso MQTT saadaksesi yksityiskohtaisen käyttöoppaan, joka sisältää salauksen, tietosuojan ja välityspalvelimen määrityksen.

Serial module

Mahdollistaa sarjaporttiviestinnän ulkoisten laiteintegraatioiden kanssa (GPS-moduulit, anturit tai mukautettu laitteisto). Kun tämä on käytössä, radion sarjaportti voi lähettää ja vastaanottaa protobuf- tai tekstimuotoista dataa, jolloin ulkoiset mikrokontrollerit tai tietokoneet voivat olla vuorovaikutuksessa verkon kanssa.

Asetus Kuvaus
Sarjaportti käytössä Ota sarjaporttiviestintä käyttöön
Palautus päällä Toista vastaanotettu sarjaporttidata takaisin
Sarjaportin tila Portin käyttämä protokolla – Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, YE.Direct, MeshSolar config, Log tai Log (vain teksti)
Vastaanotto / lähetys Sarjayhteyden GPIO-nastat
Sarjaportin nopeus Portin nopeus
Aikakatkaisu Kuinka kauan odotetaan ennen kuin saapuva viesti katsotaan kokonaiseksi
Korvaa konsolin sarjaportti Ota käyttöön portti, jota virheenkorjauskonsoli normaalisti käyttää

External Notification module

Controls buzzer, LED, or vibration alerts on your node hardware. Hyödyllinen laitteille, joiden täytyy ilmoittaa fyysisesti viestin saapumisesta — erityisen hyödyllinen valvomattomissa tai ulkokäyttöön asennetuissa laitteissa.

Käynnistimiä on kaksi – saapuva viesti ja vastaanotettu BEL-ohjausmerkki – ja kumpikin voi ohjata LED-valoa, summeria ja värinämoottoria erikseen, joten käytettävissä on kuusi kytkintä.

Asetus Kuvaus
Ulkoiset ilmoitukset käytössä Moduulin pääkytkin
Hälytysviesti: LED / summeri / värinä Mitkä lähdöt aktivoituvat saapuvasta viestistä
Hälytysmerkki: LED / summeri / värinä Mitkä lähdöt aktivoituvat vastaanotetusta BEL-ohjausmerkistä
Ulostulon LED (GPIO) LED on kytketty nastaan
Ulostulon LED aktiivinen Onko LED-nasta aktiivinen korkealla vai matalalla tasolla
Ulostulon äänimerkki (GPIO) Summeri on kytketty nastaan
Ulostulon värinä (GPIO) Värinämoottori on kytketty nastaan
Käytä PWM-äänimerkkiä Ohjaa summeria PWM:llä, jolloin voidaan toistaa ääniä yhden kiinteän taajuuden sijaan
Käytä I2S protokollaa äänimerkille Lähetä hälytys sen sijaan I2S-äänilähdön kautta
GPIO Output Duration Kuinka kauan yksittäinen hälytys kestää
Toistokehotuksen aikakatkaisu Toista hälytystä tämän ajan, kunnes se kuitataan. 0 poistaa toistuvan muistutuksen käytöstä
Soittoääni PWM-summerilla toistettava RTTTL-soittoääni. Voidaan tuoda tiedostosta

Store & Forward module

Puskuroi viestejä radioille, jotka ovat tilapäisesti poissa verkosta, ja toimittaa ne, kun nämä radiot yhdistyvät uudelleen. Välttämätön verkoissa, joissa radiot siirtyvät säännöllisesti kuuluvuusalueelle ja sen ulkopuolelle — varmistaa, etteivät viestit katoa lyhyiden yhteyskatkosten aikana.

Asetus Kuvaus
Tallenna ja lähetä edelleen Ota Varastoi & välitä käyttöön
Valvontasignaali Ilmoita tämän radion varastoi & välitä -ominaisuudesta säännöllisesti
Kirjausten määrä Tallennettujen viestien enimmäismäärä
Historian maksimimäärä Toistettavien viestien enimmäismäärä
Historian aikamäärä Aikaikkuna viestien toistolle
Palvelin Toimi mesh-verkon varastoi & välitä -palvelimena (edellyttää riittävästi muistia, esimerkiksi ESP32 PSRAM:lla)

💡 Vinkki: Varastoi & välitä toimii parhaiten radioissa, joissa on runsaasti muistia (ESP32 ja PSRAM). Router-roolin radiot ovat ihanteellisia ehdokkaita, koska ne ovat yleensä jatkuvasti käynnissä.

Range Test module

⚠️ Varoitus: Kuuluvuustesti toimii vain suojatulla ensisijaisella kanavalla. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.

Automaattinen kuuluvuustestityökalu radioiden välisen yhteyden laadun arviointiin. Kun toiminto on käytössä, radio lähettää säännöllisesti testiviestejä kasvavilla laskuriarvoilla. Vastaanottava radio kirjaa nämä viestit, jolloin voit myöhemmin kävellä tai ajaa pois ja analysoida, millä etäisyydellä viestien saapuminen loppui.

Asetus Kuvaus
Kuuluvuustesti käytössä Ota kuuluvuustesti käyttöön
Sender Interval Time between test transmissions, chosen from a dropdown of fixed intervals
Tallenna .CSV (ESP32 ainoastaan) Log received test data to the node’s own filesystem. ESP32 hardware only

Telemetry module

Määrittää, mitä telemetriatietoja radiosi jakaa verkkoon. Telemetria sisältää laitteen kuntoon liittyviä tietoja (akun varaustaso, käyttöaika) sekä ympäristöanturien tietoja (lämpötila, kosteus, ilmanpaine).

Jokaisella neljällä mittausryhmällä on oma käyttöönottokytkin ja oma mittausväli, joten esimerkiksi akun tila voidaan raportoida usein ja anturitiedot harvemmin.

Asetus Kuvaus
Lähetä laitteen telemetriatiedot Laitemittausten pääkytkin. Näkyy vain laiteohjelmistoversiossa 2.7.12 ja uudemmissa
Laitemittareiden päivitysväli How often to report battery, uptime and channel utilization
Ympäristötietojen moduuli käytössä Raportoi liitettyjen ympäristöanturien tiedot
Ympäristömittareiden päivitysväli Kuinka usein tiedot raportoidaan
Näytä ympäristötiedot näytöllä Näytä nämä tiedot myös radion omalla näytöllä
Käytä Fahrenheit yksikköä Käytä radion näytössä Fahrenheit-asteita. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Ilmanlaadun tietojen moduuli käytössä Raportoi hiukkas- ja CO₂-anturin tiedot
Ilmanlaatumittareiden päivitysväli Kuinka usein tiedot raportoidaan
Virrankulutuksen moduuli käytössä Raportoi kanavakohtaiset jännite- ja virtamittaukset
Virtamittareiden päivitysväli Kuinka usein tiedot raportoidaan
Virrankulutuksen näyttö käytössä Näytä virtamittaukset myös radion omalla näytöllä

Katso Telemetria ja anturit saadaksesi tietoa tuetuista antureista ja määrityssuosituksista.

Canned Message module

Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Määritä luettelo pikaviesteistä, jotka voidaan lähettää ilman yhdistettyä puhelinta — ihanteellinen kenttäkäyttöön.

Asetus Kuvaus
Valmisviesti käytössä ⚠️ Vanhentunut protobuf-rakenteessa
Viestit Rivinvaihdoilla eroteltu viestiluettelo
Lähetä äänimerkki Lähetä viestin mukana BEL-ohjausmerkki, jotta vastaanottavan radion Ulkoiset ilmoitukset -moduuli voi antaa hälytyksen
Kiertovalitsin #1 käytössä Käytä kiertokoodainta syöttölaitteena
GPIO pin for rotary encoder A / B / Press port Kolme nastaa, joihin kiertokoodain on kytketty
Generate input event on Press / CW / CCW Minkä näppäintapahtuman kukin kiertokoodaimen toiminto tuottaa
Ylös/Alas/Valitse syöte käytössä Erillinen, yksinkertaisempi syöttötapa, jossa käytetään ylös-/alas-/valitse-painikkeita kiertokoodaimen sijaan
Salli syöttölähde ⚠️ Vanhentunut protobuf-rakenteessa

Audio module

Codec2-äänituki matalan kaistanleveyden puheviestintään verkossa. Tämä on kokeellinen ominaisuus, joka koodaa puheen erittäin pieniksi datapaketeiksi käyttäen Codec2-koodekkia.

Asetus Kuvaus
CODEC 2 käytössä Ota äänimoduuli käyttöön
CODEC2 näytteenottotaajuus Äänenlaadun ja kaistanleveyden välinen kompromissi
PTT-pinni PTT-painikkeen GPIO-nasta
I2S-sanan valinta GPIO-pinni I2S WS:lle
I2S-datatulo GPIO-nasta I2S DIN:lle
I2S-datalähtö GPIO-pinni I2S DOUT:lle
I2S-kello I2S-bittikellon GPIO-nasta

ℹ️ Huomautus: Ääniominaisuus edellyttää yhteensopivaa laitteistoa (I2S-mikrofoni ja -kaiutin). Äänenlaatu on hyvin matalakaistainen — ajattele “ymmärrettävää radiopuhetta”, ei puhelinlaatua.

Remote Hardware module

GPIO-ohjaus mesh-verkon kautta. Mahdollistaa etäradion lukea tai kirjoittaa GPIO-nastoja toisessa radiossa — hyödyllinen releiden aktivointiin, kytkimien lukemiseen tai ulkoisen laitteiston ohjaamiseen etäältä.

⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.

Asetus Kuvaus
Etälaitteen ohjaus käytössä Ota etä-GPIO-käyttö käyttöön
Salli määrittämättömän pinnin käyttö Salli pääsy mihin tahansa GPIO-nastaan (tietoturvariski)
Käytettävissä olevat pinnit Enintään 4 tämän radion etälukuun tai kirjoitukseen tarjoamaa GPIO-pinniä

Neighbor Info module

Lähettää tietoa suoraan kuulluista naapureista mahdollistaen verkon topologian kartoituksen. Jokainen käyttöön otettu radio jakaa säännöllisesti luettelon muista radioista, jotka se kuulee, sekä niiden signaalin laadun.

Asetus Kuvaus
Naapuritiedot käytössä Ota naapuritiedon lähetys käyttöön
GPS-kyselyn aikaväli Kuinka usein naapuriluettelo lähetetään
Lähetä LoRa:n kautta Lähetä myös naapuritiedot LoRa:n kautta, ei pelkästään MQTT:n tai puhelimen kautta. Ei käytettävissä kanavalla, joka käyttää oletusavainta ja nimeä

Katso Paikallinen mesh-haku, miten naapuritietoja käytetään mesh-verkon rakenteen tutkimiseen.

Ambient Lighting module

Ohjaa tuetuissa laitteissa olevaa NeoPixeliä tai muita osoitteellisia RGB-LEDejä. Voidaan käyttää visuaalisina tilailmaisimina, ilmoitusvaloina tai koriste-efekteinä.

Asetus Kuvaus
LED-tila Kytke LED päälle tai pois päältä
Virta LED-virran rajoitus (0–31)
Punainen / vihreä / sininen Yksittäisten värikanavien arvot (0–255)

Detection Sensor module

Muuttaa radiosi liike- tai ovitunnistimeen perustuvaksi hälytysjärjestelmäksi. Kun GPIO-pinni havaitsee tilamuutoksen (liike havaittu, ovi avattu), radio lähettää hälytysviestin verkkoon.

Asetus Kuvaus
Tunnistinsensori käytössä Ota tunnistusanturi käyttöön
GPIO-pinni valvontaa varten Anturiin kytketty GPIO-pinni
Tunnistuksen tyyppi Miten pinnin tila vastaa havaitsemistapahtumaa (esim. aktiivinen korkea/matala taso tai reunalaukaisu)
Käytä INPUT_PULLUP tilaa Ota pinnin sisäinen ylösvetovastus käyttöön
Minimum time between detection broadcasts Hälytyslähetysten vähimmäisaika
State Broadcast Interval Tilatiedon lähetysväli
Lähetä äänimerkki hälytyssanoman kanssa Sisällytä soittomerkkimerkki hälytyksiin
Käyttäjäystävällinen nimi Tälle anturille määritetty nimi

Paxcounter module

Henkilöt, jotka lasketaan WiFi- ja BLE-hakukyselyiden perusteella. Laskee lähellä olevia laitteita kuuntelemalla passiivisesti koepyyntöjä, joita puhelimet ja kannettavat tietokoneet lähettävät etsiessään verkkoja. Saatavilla vain ESP32-laitteissa.

Asetus Kuvaus
PAX-laskuri käytössä Ota henkilölaskenta käyttöön
GPS-kyselyn aikaväli Kuinka usein laskentatiedot raportoidaan
WiFi Threshold (dBm) Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm) Sama raja-arvo BLE-mainospaketeille (oletus: -80 dBm)

💡 Vinkki: PAX-laskuri on hyödyllinen jalankulkijamäärien arviointiin retkeilyreittien lähtöpisteissä, tapahtumapaikoilla tai muissa kohteissa. Laskentatulokset ovat arvioita — yhdellä henkilöllä voi olla useita laitteita mukana.

Status Message module

Tilaviestillä ei ole omaa moduulinäkymää. Sitä muokataan yhdessä muiden radion tunnistetietojen kanssa kohdassa Asetukset → Radio ja käyttäjä.

Mesh Beacon module

Lähettää kutsun mesh-verkkoosi ja vastaanottaa muiden lähettämiä kutsuja. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.

TAK module

Team Awareness Kit -integraatio yhteensopivuutta varten ATAK- ja WinTAK-järjestelmien kanssa. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. Katso TAK-integraatio saadaksesi tarkemmat määritys- ja käyttöohjeet.

Ylläpito

Etähallinta

Määritä etänä radiot, jotka jakavat saman ylläpitoavaimen:

  1. Valitse kohderadio radioluettelosta.
  2. Siirry kyseisen radion Asetukset-kohtaan.
  3. Muokkaa määrityksiä.
  4. Napauta Tallenna — muutokset lähetetään verkon kautta.

⚠️ Tärkeää: Edellyttää, että järjestelmänvalvojan avain on määritetty sekä omassa radiossasi että kohderadiossa.

Device Actions

Settings → Administration holds five one-shot actions, each behind a confirmation dialog:

Toiminto Mitä se tekee
Aseta aika Sends your phone’s clock to the node
Käynnistä uudelleen Restarts the node
Sammuta Powers the node down
Palauta tehdasasetukset Returns every setting to its factory default
Tyhjennä NodeDB-tietokanta Clears the node database. This dialog carries a Preserve Favorites? switch

⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.

Varmuuskopiointi ja palautus

Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.

Lisäasetukset

Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.

Tyhjennä NodeDB-tietokanta

Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.

  • Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
  • Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.

The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.

Vianetsintäpaneeli

Avaa Paketit- ja Sovelluslokit-välilehdet diagnostiikkatietojen tarkastelua, suodatusta ja vientiä varten. Katso Virheenjäljityslokit, jossa on täydellinen käyttöohje.

App Settings

The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:

Privacy

  • Allow analytics and crash reporting — opt in or out of diagnostics.
  • Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
  • Homoglyph encoding — how look-alike characters in names are handled.

Appearance

  • Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
  • Theme and Language.
  • Show full message timestamps.

Persistence

  • A cache limit for how much history is kept.
  • Export rangetest packets, Export all packets and Export node database.

On their own

  • Node Layout — how much detail each row of the node list shows.
  • Wi-Fi Provisioning for mPWRD-OS — see Connections.
  • Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
  • System AI — appears only where app functions are available; see App Functions.

A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.

Tietoja

Settings → About carries the app’s own identity rather than the node’s:

Kolme osiota:

  • Mikä on Meshtastic? – lyhyt kuvaus projektista.
  • Sovellukset — avaa Tarvitsetko laitteiston? -näkymän, jossa on suosittujen laitteiden karuselli ja linkit niiden ostopaikkoihin. Siellä näytetään myös GitHub-tietovarasto, käytössä oleva sovellusversio ja Tekijätiedot (katso seuraava osio).
  • Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.

The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.

Kiitokset

Tietoja-kohdasta avattava näkymä, jossa luetellaan kaikki sovelluksen käyttämät avoimen lähdekoodin kirjastot lisensseineen. Luettelo luodaan käännöshetkellä AboutLibraries-kirjastolla. Tätä kutsuttiin aiemmin lisenssinäkymäksi.

Troubleshooting remote admin

  • Ei vastausta kohderadiolta — kohderadio voi olla kuuluvuusalueen ulkopuolella, poissa verkosta tai siinä voi olla eri ylläpitoavain. Varmista, että ylläpitoavain on sama molemmissa radioissa.
  • Muutokset eivät tule voimaan — jotkin asetukset edellyttävät uudelleenkäynnistystä ennen kuin ne astuvat voimaan. Kokeile Uudelleenkäynnistystä tallennuksen jälkeen.
  • Et näe etäasetuksia — varmista, että radiossasi on kohderadion ylläpitoavain. Ylläpitokanava määritetään automaattisesti, kun ylläpitoavain on asetettu.

Aiheeseen liittyvät aiheet

diff --git a/main/fi-rFI/user/settings-radio-user.html b/main/fi-rFI/user/settings-radio-user.html index 4311681783..beaca17e7d 100644 --- a/main/fi-rFI/user/settings-radio-user.html +++ b/main/fi-rFI/user/settings-radio-user.html @@ -1 +1 @@ - Asetukset — Radio ja käyttäjä | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Suomi
Meshtastic Docs ↗

🌐 Suomi — Community translation View in English

Asetukset — Radio ja käyttäjä

Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How these screens work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth.

Asetukset käyttävät tavallisia asetussäätimiä — pudotusvalikoita, kytkimiä ja liukusäätimiä:

Säädin Kuvakaappaus
Pudotusvalikko Pudotusvalikkoasetus avattuna näyttämään vaihtoehtoluettelonsa
Kytkin Kytkinasetus käytössä-asennossa
Liukusäädin Liukusäädinasetus nykyinen numeerinen arvo näkyvissä

Käyttäjäasetukset

Käyttäjäprofiili

On Settings → User.

Asetus Kuvaus
Pitkä nimi Näyttönimesi (enintään 39 merkkiä)
Lyhytnimi 4-merkkinen lyhytnimi
Tilaviesti A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Edellyttää laiteohjelmistoversiota 2.8 tai uudempaa. Muussa tapauksessa tätä ei näytetä
Ei vastaanota viestejä Merkitsee radion sellaiseksi, jolle kenenkään ei pitäisi yrittää lähettää viestejä – tarkoitettu valvomattomalle tai infrastruktuuriradiolle. Muut sovellukset piilottavat sen yhteystietoluettelosta. Edellyttää yhteensopivaa laiteohjelmistoa
Licensed amateur node (Ham) Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

Tilaviesti tallennetaan samalla Tallenna-painikkeella, mutta se ei koskaan käynnistä radiota uudelleen. Kuten muitakin tämän näkymän asetuksia, sitä voidaan muokata etähallittavassa radiossa. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in.

Asetukset

Laitteen asetukset

On Settings → Device configuration → Device.

Asetus Kuvaus Oletus
Laitteen rooli Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Uudelleenlähetyksen tila How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Laitteen tietojen lähetyksen aikaväli How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Kaksoisnapautus painikkeena Käsittele kaksoisnapautus painikkeen painalluksena Ei käytössä
Kolmoisklikkaus Ad Hoc -pingille Lähetä kertaluonteinen sijaintipyyntö kolminkertaisella painalluksella Käytössä
Ledin valvontasignaali Vilkuta tilan merkkilediä säännöllisesti Käytössä
Aikavyöhyke Laitteen kellon POSIX-aikavyöhyke. Painikkeilla voit kopioida puhelimesi aikavyöhykkeen tai tyhjentää kentän —
Painikkeen / summerin GPIO Lisäasetukset: GPIO-nastat, joihin painike ja summeri on kytketty —

LoRa:n asetukset

On Settings → LoRa.

Asetus Kuvaus Oletus
Alue Taajuusalueen sääntelyalue. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number Ei asetettu (on määritettävä)
Esiasetukset Nopeuden ja kantaman välinen kompromissi LongFast
Hyppyjen määrä Suurin hyppyjen määrä 3
Lähetysteho Lähetysteho (dBm): 0 = alueen sallima enimmäisteho 0 (alueen enimmäisteho)
Taajuuden ohitus Ohittaa lasketun käyttötaajuuden (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (käytä laskettua arvoa)
Käytä esiasetusta Oletusarvoisesti käytössä. Poista tämä käytöstä, jos haluat määrittää hajotuskerroin-, koodausnopeus- ja kaistanleveysasetukset käsin modeemiesiasetuksen sijaan Käytössä
Levennyskerroin (Spread Factor) Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead Esiasetuksesta
Koodausnopeus Vain manuaalitilassa: 5–8. Suurempi virheenkorjaus lisää lähetysaikaa Esiasetuksesta
Kaistanleveys Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one Esiasetuksesta
Taajuuspaikka Määrittää, mitä alueen taajuusväliä käytetään. 0 muodostetaan ensisijaisen kanavan nimestä 0 (automaattinen)
Lähetys käytössä Tämän poistaminen käytöstä tekee radiosta vain vastaanottavan Käytössä
Ohita käyttöaste (Duty Cycle) Ohittaa alueen lähetysajan käyttörajoituksen. Laitonta useimmilla alueilla. Ota käyttöön vain, jos radioamatöörilupasi sallii sen Pois
Ohita MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
MQTT päällä Salli yhdyskäytävien välittää pakettisi MQTT:hen Pois
RX tehostettu vahvistus Lisävastaanottovahvistus SX126x-radioille. Kuluttaa hieman enemmän virtaa Pois
PA tuuletin pois käytöstä Poista päätevahvistimen tuuletin käytöstä laitteissa, joissa sellainen on Pois

The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set.

Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Tärkeää: Käyttö väärällä alueasetuksella voi rikkoa paikallisia radiomääräyksiä. Katso alueasetusten määritysopas meshtastic.org-sivustolta saadaksesi lisätietoja.

Modem presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes.

💡 Vinkki: SNR-raja-arvot ovat tarkoituksella negatiivisia. LoRa pystyy purkamaan signaaleja kohinatason alapuolelta, joten negatiivisempi raja tarkoittaa, että esiasetus sietää heikomman ja kohinaisemman signaalin (suurempi kantama). Katso Miten signaalimittari toimii saadaksesi täydellisen selityksen.

Esiasetus Kantama Nopeus SNR-raja Paras käyttöön
Short Turbo ~1 km 21.9 kbps −7.5 dB Tiheä kaupunkiympäristö suoralla näköyhteydellä; paljon dataa siirtävät sovellukset
Short Fast ~3 km 10.9 kbps −7.5 dB Kaupunkialueet, rakennuksia muutaman korttelin säteellä
Short Slow ~5 km 6.25 kbps −10 dB Lyhyen kantaman esikaupunkialueet; kohtalainen rakennustiheys
Medium Fast ~5 km 3.52 kbps −12.5 dB Esikaupunkialueet; kohtalainen rakennustiheys
Medium Slow ~8 km 1.95 kbps −15 dB Esikaupunki-/maaseutualueet; kohtalainen kantama ja hitaampi nopeus
Long Turbo ~10 km 1.34 kbps −17.5 dB Samankaltainen kantama kuin Long Fast -asetuksella, mutta 500 kHz:n kaistanleveydellä; suurempi tiedonsiirtonopeus
Long Fast ~10 km 1.1 kbps −17.5 dB Yleiskäyttö (oletus) — tasapaino kantaman ja nopeuden välillä
Long Moderate ~20 km 0.34 kbps −17.5 dB Maaseutualueet, joissa on jonkin verran maastonmuotoja; satunnainen käyttö
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD -alue (125 kHz BW); verrattavissa Medium Fast -asetukseen
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD -alue (125 kHz BW); verrattavissa Long Fast -asetukseen
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz -alue (62,5 kHz BW); välttää häiriöitä muiden laitteiden kanssa
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz -alue (62,5 kHz BW); verrattavissa Long Fast -asetukseen
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Vanhentunut — edelleen valittavissa, mutta voidaan poistaa tulevassa laiteohjelmistoversiossa
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Vanhentunut — edelleen valittavissa, mutta voidaan poistaa tulevassa laiteohjelmistoversiossa

ℹ️ Huomautus: Tässä taulukossa käytetään yleisesti käytössä olevia lyhyitä nimiä. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a modem preset

Modeemiesiasetus määrittää tärkeimmän kompromissin kantaman ja tiedonsiirtonopeuden välillä:

  • Hitaammat esiasetukset käyttävät enemmän hajautusta, jolloin signaali voidaan purkaa heikommilla signaalitasoilla (alempi SNR-raja). Tämä tarkoittaa pidempää kantamaa, mutta vähemmän tavuja sekunnissa.
  • Nopeammat esiasetukset siirtävät enemmän dataa, mutta vaativat vahvemman signaalin purkamista varten.

Käytännön ohje:

  • Kaupunkiverkko (paljon radioita, lyhyet etäisyydet): Käytä Long Fast -asetusta (oletus) tai Short Fast -asetusta. Suurempi nopeus tarkoittaa vähemmän käyttöasteruuhkaa, kun monet radiot jakavat saman kanavan.
  • Maaseutu tai harva verkko (vähän radioita, pitkät etäisyydet): Käytä Long Moderate -asetusta. Kantama on tärkeämpi kuin nopeus, kun radiot ovat kaukana toisistaan.
  • EU 866/868 MHz -alueen säädösten noudattaminen: Käytä Lite Fast, Lite Slow, Narrow Fast tai Narrow Slow -asetuksia — ne on optimoitu EU:n SRD/868 MHz -alueille kapeammilla kaistanleveyksillä.
  • Kiinteät infrastruktuurilinkit: Käytä Short Turbo- tai Long Turbo -asetusta erillisille pisteestä pisteeseen -linkeille, joissa on hyvät antennit ja suora näköyhteys.
  • Sekaverkot: Pysy Long Fast -asetuksessa — se on yhteisön oletusasetus ja varmistaa yhteensopivuuden alueesi muiden käyttäjien kanssa.

Kaikkien samalla kanavalla olevien radioiden on käytettävä samaa modeemiesiasetusta. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key.

Modeemiesiasetukset-taulukon kantama-arviot perustuvat tasaiseen maastoon ja vaatimattomiin antenneihin. Korkeuseroetu (mäki, rakennuksen katto) kasvattaa käytännön kantamaa huomattavasti. Hyvin sijoitettu Long Fast -asetusta käyttävä Router voi usein toimia paremmin kuin maan tasalla oleva Long Slow -asetusta käyttävä radio.

Näytön asetukset

On Settings → Device configuration → Display. These control the node’s own screen, not the app’s.

Asetus Kuvaus
Näytön päälläoloaika Kuinka kauan näyttö pysyy päällä ennen siirtymistä lepotilaan
Karusellin aikaväli How often the node cycles between screens on its own
Näyttötila Laiteohjelmiston käyttämä näytön asettelu/tiheys
Näyttöyksiköt Metric or Imperial on the node’s screen
Käytä 12 tunnin kelloa Show the node’s clock as 12-hour rather than 24-hour
Lihavoitu otsikko Näytä näytön otsikkoteksti lihavoituna
Käännä näyttö Kierrä näyttö 180° ylösalaisin asennusta varten
OLED-tyyppi Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED
Herätä napautuksesta tai liikkeestä Light the screen when the node is tapped or moved
Kompassin suuntaus Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each
Osoita aina pohjoiseen Lukitsee kompassinäytön näyttämään pohjoiseen sen sijaan, että se kääntyisi kulkusuunnan mukaan. Riippumaton kompassin suunnasta — kumpikaan ei korvaa toista

Sijainnin asetukset

On Settings → Device configuration → Position.

Asetus Kuvaus
GPS-tila (fyysinen laitteisto) Kolmitilainen: GPS käytössä, poistettu käytöstä tai ei käytettävissä. Ei pelkkä käytössä / poistettu käytöstä -asetus
GPS-kyselyn aikaväli How often the node asks its GPS for a fix
Lähetyksen aikaväli Kuinka usein sijainti jaetaan mesh-verkkoon
Älykäs sijainti Lähettää sijainnin liikkeen perusteella pelkän aikavälin sijaan
Älykäs aikaväli Älykäs sijainti -toiminnon ollessa käytössä lyhin sallittu aika sijaintilähetysten välillä
Älykäs etäisyys Älykäs sijainti -toiminnon ollessa käytössä, kuinka pitkän matkan on liikuttava ennen sijainnin lähettämistä
Kiinteä sijainti Käytä käsin syötettyä leveyspiiriä, pituuspiiriä ja korkeutta GPS:n sijaan
Sijaintimerkinnät Asetusryhmä, jolla valitaan, mitkä tiedot liitetään sijaintiin — kuten korkeus, viitekehys, tarkkuus, näkyvissä olevat satelliitit, aikaleima ja muut tiedot
GPS EN / Vastaanotto / Lähetys GPIO Lisäasetukset: nastat, joihin GPS-moduuli on kytketty

Virran asetukset

On Settings → Device configuration → Power.

Asetus Kuvaus
Ota virransäästötila käyttöön Let the node sleep aggressively between activity
Sammuta virran katketessa Sammuta laite, kun ulkoinen virta katkeaa
Super-syväunen kesto Kuinka kauan syvin lepotila kestää
Vähimmäisherätyksen kesto The shortest time the node stays awake once woken
Bluetoothin odotusaika Kuinka kauan odotetaan puhelimen yhteyden muodostumista ennen lepotilaan siirtymistä
ADC-kertoimen ohitus Ota akun jännitemittauksille käyttöön manuaalinen korjaus
Korvaava AD-muuntimen kerroin Korjauskerroin, käytössä vain kun manuaalinen korjaus on käytössä
INA_2XX-akun valvontapiirin I2C-osoite Ulkoisen INA-sarjan tehoanturin osoite, jos sellainen on asennettu

Verkon asetukset

On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node.

Asetus Kuvaus
WiFi käytössä Enable the Wi-Fi node (ESP32 nodes)
SSID Verkon nimi, johon yhdistetään. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Salasana Verkon salasana
Ethernet käytössä Käytä langallista yhteyttä sitä tukevalla laitteistolla
IPv4-tila DHCP, or a static address configured with the four fields that follow
WiFi IP / Aliverkko / Yhdyskäytävä / DNS Kiinteä IP-osoite, käytössä vain kun IPv4-tila on kiinteä
UDP-lähetys Jaa mesh-verkon liikenne muiden radioiden kanssa lähiverkon kautta
NTP palvelin Ajan synkronointipalvelin (NTP-palvelin)
rsyslog-palvelin Etätietojen palvelin

Verkkoasetukset, joissa on määritetty kiinteä IPv4-osoite

Bluetooth asetukset

On Settings → Device configuration → Bluetooth, on nodes with Bluetooth.

Asetus Kuvaus
Bluetooth käytössä Ota Bluetooth-radio käyttöön tai poista käytöstä
Paritustila Kiinteä PIN-koodi, satunnainen PIN-koodi tai ei PIN-koodia
Kiinteä PIN-koodi Pariliitoksen PIN-koodi. Siinä on oltava täsmälleen kuusi numeroa — kenttä hylkää kaikki muut arvot

Turvallisuusasetukset

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

Asetus Kuvaus
Julkinen avain Radiosi julkinen avain (vain luku)
Ylläpitäjän avain Avaimet, joilla tätä radiota voidaan hallita etänä – enintään kolme
Yksityinen avain Radiosi yksityinen avain (säilytä turvallisesti). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it
Luo uusi yksityinen avain Luo tälle radiolle uuden avainparin vahvistuksen jälkeen. Kaikkien vanhan avaimesi tunteneiden vertaisradioiden on opittava uusi avain
Ylläpitokanava käytössä ⚠️ Poistettu — määritetään nyt automaattisesti, kun ylläpitoavain asetetaan
Sarjaporttikonsoli Serial console over the Stream API
Vianetsintälokirajapinta käytössä Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth
Hallintatila Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Voidaan valita vasta, kun järjestelmänvalvojan avain on määritetty
Varmuuskopioi avaimet Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Palauta avaimet Kirjoita varmuuskopioidut avaimet takaisin radioon (käytettävissä, kun varmuuskopio on olemassa)
Poista avaimen varmuuskopio Remove the stored key backup from this phone
Suojaustaso How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lukitustila

Lukitustila salaa laitteen tallennustilan ja edellyttää tunnuslausetta jokaiselle yhteydelle. It needs supporting firmware; the row doesn’t appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device.

Tunnuslauseen lisäksi määrität rajat, joiden täyttyessä istunto päättyy automaattisesti:

Kenttä Mitä se tekee
Jäljellä olevat käynnistykset Kuinka monen käynnistyksen ajan avattu tila säilyy
Tuntia vanhenemiseen saakka Avatun tilan enimmäiskesto
Istunnon enimmäiskesto (minuuttia) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Kun lukitustila on käytössä, tässä lukee Aktiivinen – tallennustila salattu, tämä yhteys todennettu, kun yhteys on avattu, tai Aktiivinen – avaa tämä yhteys antamalla tunnuslause, kun sitä ei ole avattu. Lukitse nyt päättää nykyisen istunnon välittömästi. Toistuvat virheelliset tunnuslauseet rajoitetaan odotusajalla, ennen kuin voit yrittää uudelleen.

⚠️ Varoitus: Tunnuslausetta ei voi palauttaa. Jos kadotat sen, laite on tyhjennettävä sen palauttamiseksi, jolloin sen avaimet, kanavat ja asetukset poistuvat.

Aiheeseen liittyvät aiheet

+ Asetukset — Radio ja käyttäjä | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Suomi
Meshtastic Docs ↗

🌐 Suomi — Community translation View in English

Asetukset — Radio ja käyttäjä

Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How these screens work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth.

Asetukset käyttävät tavallisia asetussäätimiä — pudotusvalikoita, kytkimiä ja liukusäätimiä:

Säädin Kuvakaappaus
Pudotusvalikko Pudotusvalikkoasetus avattuna näyttämään vaihtoehtoluettelonsa
Kytkin Kytkinasetus käytössä-asennossa
Liukusäädin Liukusäädinasetus nykyinen numeerinen arvo näkyvissä

Käyttäjäasetukset

Käyttäjäprofiili

On Settings → User.

Asetus Kuvaus
Pitkä nimi Näyttönimesi (enintään 39 merkkiä)
Lyhytnimi 4-merkkinen lyhytnimi
Tilaviesti A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Edellyttää laiteohjelmistoversiota 2.8 tai uudempaa. Muussa tapauksessa tätä ei näytetä
Ei vastaanota viestejä Merkitsee radion sellaiseksi, jolle kenenkään ei pitäisi yrittää lähettää viestejä – tarkoitettu valvomattomalle tai infrastruktuuriradiolle. Muut sovellukset piilottavat sen yhteystietoluettelosta. Edellyttää yhteensopivaa laiteohjelmistoa
Licensed amateur node (Ham) Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

Tilaviesti tallennetaan samalla Tallenna-painikkeella, mutta se ei koskaan käynnistä radiota uudelleen. Kuten muitakin tämän näkymän asetuksia, sitä voidaan muokata etähallittavassa radiossa. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in.

Asetukset

Laitteen asetukset

On Settings → Device configuration → Device.

Asetus Kuvaus Oletus
Laitteen rooli Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Uudelleenlähetyksen tila How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Laitteen tietojen lähetyksen aikaväli How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Kaksoisnapautus painikkeena Käsittele kaksoisnapautus painikkeen painalluksena Ei käytössä
Kolmoisklikkaus Ad Hoc -pingille Lähetä kertaluonteinen sijaintipyyntö kolminkertaisella painalluksella Käytössä
Ledin valvontasignaali Vilkuta tilan merkkilediä säännöllisesti Käytössä
Aikavyöhyke Laitteen kellon POSIX-aikavyöhyke. Painikkeilla voit kopioida puhelimesi aikavyöhykkeen tai tyhjentää kentän —
Painikkeen / summerin GPIO Lisäasetukset: GPIO-nastat, joihin painike ja summeri on kytketty —

LoRa:n asetukset

On Settings → LoRa.

Asetus Kuvaus Oletus
Alue Taajuusalueen sääntelyalue. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number Ei asetettu (on määritettävä)
Esiasetukset Nopeuden ja kantaman välinen kompromissi LongFast
Hyppyjen määrä Suurin hyppyjen määrä 3
Transmit Power (dBm) Transmission power; 0 = max allowed for region 0 (alueen enimmäisteho)
Taajuuden ohitus Ohittaa lasketun käyttötaajuuden (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (käytä laskettua arvoa)
Käytä esiasetusta Oletusarvoisesti käytössä. Poista tämä käytöstä, jos haluat määrittää hajotuskerroin-, koodausnopeus- ja kaistanleveysasetukset käsin modeemiesiasetuksen sijaan Käytössä
Levennyskerroin (Spread Factor) Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead Esiasetuksesta
Koodausnopeus Vain manuaalitilassa: 5–8. Suurempi virheenkorjaus lisää lähetysaikaa Esiasetuksesta
Kaistanleveys Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one Esiasetuksesta
Taajuuspaikka Määrittää, mitä alueen taajuusväliä käytetään. 0 muodostetaan ensisijaisen kanavan nimestä 0 (automaattinen)
Lähetys käytössä Tämän poistaminen käytöstä tekee radiosta vain vastaanottavan Käytössä
Ohita käyttöaste (Duty Cycle) Ohittaa alueen lähetysajan käyttörajoituksen. Laitonta useimmilla alueilla. Ota käyttöön vain, jos radioamatöörilupasi sallii sen Pois
Ohita MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
MQTT päällä Salli yhdyskäytävien välittää pakettisi MQTT:hen Pois
RX tehostettu vahvistus Lisävastaanottovahvistus SX126x-radioille. Kuluttaa hieman enemmän virtaa Pois
PA tuuletin pois käytöstä Poista päätevahvistimen tuuletin käytöstä laitteissa, joissa sellainen on Pois

The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set.

Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Tärkeää: Käyttö väärällä alueasetuksella voi rikkoa paikallisia radiomääräyksiä. Katso alueasetusten määritysopas meshtastic.org-sivustolta saadaksesi lisätietoja.

Modem presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes.

💡 Vinkki: SNR-raja-arvot ovat tarkoituksella negatiivisia. LoRa pystyy purkamaan signaaleja kohinatason alapuolelta, joten negatiivisempi raja tarkoittaa, että esiasetus sietää heikomman ja kohinaisemman signaalin (suurempi kantama). Katso Miten signaalimittari toimii saadaksesi täydellisen selityksen.

Esiasetus Kantama Nopeus SNR-raja Paras käyttöön
Short Turbo ~1 km 21.9 kbps −7.5 dB Tiheä kaupunkiympäristö suoralla näköyhteydellä; paljon dataa siirtävät sovellukset
Short Fast ~3 km 10.9 kbps −7.5 dB Kaupunkialueet, rakennuksia muutaman korttelin säteellä
Short Slow ~5 km 6.25 kbps −10 dB Lyhyen kantaman esikaupunkialueet; kohtalainen rakennustiheys
Medium Fast ~5 km 3.52 kbps −12.5 dB Esikaupunkialueet; kohtalainen rakennustiheys
Medium Slow ~8 km 1.95 kbps −15 dB Esikaupunki-/maaseutualueet; kohtalainen kantama ja hitaampi nopeus
Long Turbo ~10 km 1.34 kbps −17.5 dB Samankaltainen kantama kuin Long Fast -asetuksella, mutta 500 kHz:n kaistanleveydellä; suurempi tiedonsiirtonopeus
Long Fast ~10 km 1.1 kbps −17.5 dB Yleiskäyttö (oletus) — tasapaino kantaman ja nopeuden välillä
Long Moderate ~20 km 0.34 kbps −17.5 dB Maaseutualueet, joissa on jonkin verran maastonmuotoja; satunnainen käyttö
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD -alue (125 kHz BW); verrattavissa Medium Fast -asetukseen
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD -alue (125 kHz BW); verrattavissa Long Fast -asetukseen
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz -alue (62,5 kHz BW); välttää häiriöitä muiden laitteiden kanssa
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz -alue (62,5 kHz BW); verrattavissa Long Fast -asetukseen
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Vanhentunut — edelleen valittavissa, mutta voidaan poistaa tulevassa laiteohjelmistoversiossa
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Vanhentunut — edelleen valittavissa, mutta voidaan poistaa tulevassa laiteohjelmistoversiossa

ℹ️ Huomautus: Tässä taulukossa käytetään yleisesti käytössä olevia lyhyitä nimiä. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a modem preset

Modeemiesiasetus määrittää tärkeimmän kompromissin kantaman ja tiedonsiirtonopeuden välillä:

  • Hitaammat esiasetukset käyttävät enemmän hajautusta, jolloin signaali voidaan purkaa heikommilla signaalitasoilla (alempi SNR-raja). Tämä tarkoittaa pidempää kantamaa, mutta vähemmän tavuja sekunnissa.
  • Nopeammat esiasetukset siirtävät enemmän dataa, mutta vaativat vahvemman signaalin purkamista varten.

Käytännön ohje:

  • Kaupunkiverkko (paljon radioita, lyhyet etäisyydet): Käytä Long Fast -asetusta (oletus) tai Short Fast -asetusta. Suurempi nopeus tarkoittaa vähemmän käyttöasteruuhkaa, kun monet radiot jakavat saman kanavan.
  • Maaseutu tai harva verkko (vähän radioita, pitkät etäisyydet): Käytä Long Moderate -asetusta. Kantama on tärkeämpi kuin nopeus, kun radiot ovat kaukana toisistaan.
  • EU 866/868 MHz -alueen säädösten noudattaminen: Käytä Lite Fast, Lite Slow, Narrow Fast tai Narrow Slow -asetuksia — ne on optimoitu EU:n SRD/868 MHz -alueille kapeammilla kaistanleveyksillä.
  • Kiinteät infrastruktuurilinkit: Käytä Short Turbo- tai Long Turbo -asetusta erillisille pisteestä pisteeseen -linkeille, joissa on hyvät antennit ja suora näköyhteys.
  • Sekaverkot: Pysy Long Fast -asetuksessa — se on yhteisön oletusasetus ja varmistaa yhteensopivuuden alueesi muiden käyttäjien kanssa.

Kaikkien samalla kanavalla olevien radioiden on käytettävä samaa modeemiesiasetusta. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key.

Modeemiesiasetukset-taulukon kantama-arviot perustuvat tasaiseen maastoon ja vaatimattomiin antenneihin. Korkeuseroetu (mäki, rakennuksen katto) kasvattaa käytännön kantamaa huomattavasti. Hyvin sijoitettu Long Fast -asetusta käyttävä Router voi usein toimia paremmin kuin maan tasalla oleva Long Slow -asetusta käyttävä radio.

Näytön asetukset

On Settings → Device configuration → Display. These control the node’s own screen, not the app’s.

Asetus Kuvaus
Näytön päälläoloaika Kuinka kauan näyttö pysyy päällä ennen siirtymistä lepotilaan
Karusellin aikaväli How often the node cycles between screens on its own
Näyttötila Laiteohjelmiston käyttämä näytön asettelu/tiheys
Näyttöyksiköt Metric or Imperial on the node’s screen
Käytä 12 tunnin kelloa Show the node’s clock as 12-hour rather than 24-hour
Lihavoitu otsikko Näytä näytön otsikkoteksti lihavoituna
Käännä näyttö Kierrä näyttö 180° ylösalaisin asennusta varten
OLED-tyyppi Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED
Herätä napautuksesta tai liikkeestä Light the screen when the node is tapped or moved
Kompassin suuntaus Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each
Osoita aina pohjoiseen Lukitsee kompassinäytön näyttämään pohjoiseen sen sijaan, että se kääntyisi kulkusuunnan mukaan. Riippumaton kompassin suunnasta — kumpikaan ei korvaa toista

Sijainnin asetukset

On Settings → Device configuration → Position.

Asetus Kuvaus
GPS-tila (fyysinen laitteisto) Kolmitilainen: GPS käytössä, poistettu käytöstä tai ei käytettävissä. Ei pelkkä käytössä / poistettu käytöstä -asetus
GPS-kyselyn aikaväli How often the node asks its GPS for a fix
Lähetyksen aikaväli Kuinka usein sijainti jaetaan mesh-verkkoon
Älykäs sijainti Lähettää sijainnin liikkeen perusteella pelkän aikavälin sijaan
Älykäs aikaväli Älykäs sijainti -toiminnon ollessa käytössä lyhin sallittu aika sijaintilähetysten välillä
Älykäs etäisyys Älykäs sijainti -toiminnon ollessa käytössä, kuinka pitkän matkan on liikuttava ennen sijainnin lähettämistä
Kiinteä sijainti Käytä käsin syötettyä leveyspiiriä, pituuspiiriä ja korkeutta GPS:n sijaan
Sijaintimerkinnät Asetusryhmä, jolla valitaan, mitkä tiedot liitetään sijaintiin — kuten korkeus, viitekehys, tarkkuus, näkyvissä olevat satelliitit, aikaleima ja muut tiedot
GPS EN / Vastaanotto / Lähetys GPIO Lisäasetukset: nastat, joihin GPS-moduuli on kytketty

Virran asetukset

On Settings → Device configuration → Power.

Asetus Kuvaus
Ota virransäästötila käyttöön Let the node sleep aggressively between activity
Sammuta virran katketessa Sammuta laite, kun ulkoinen virta katkeaa
Super-syväunen kesto Kuinka kauan syvin lepotila kestää
Vähimmäisherätyksen kesto The shortest time the node stays awake once woken
Bluetoothin odotusaika Kuinka kauan odotetaan puhelimen yhteyden muodostumista ennen lepotilaan siirtymistä
ADC-kertoimen ohitus Ota akun jännitemittauksille käyttöön manuaalinen korjaus
Korvaava AD-muuntimen kerroin Korjauskerroin, käytössä vain kun manuaalinen korjaus on käytössä
INA_2XX-akun valvontapiirin I2C-osoite Ulkoisen INA-sarjan tehoanturin osoite, jos sellainen on asennettu

Verkon asetukset

On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node.

Asetus Kuvaus
WiFi käytössä Enable the Wi-Fi node (ESP32 nodes)
SSID Verkon nimi, johon yhdistetään. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Salasana Verkon salasana
Ethernet käytössä Käytä langallista yhteyttä sitä tukevalla laitteistolla
IPv4-tila DHCP, or a static address configured with the four fields that follow
WiFi IP / Aliverkko / Yhdyskäytävä / DNS Kiinteä IP-osoite, käytössä vain kun IPv4-tila on kiinteä
UDP-lähetys Jaa mesh-verkon liikenne muiden radioiden kanssa lähiverkon kautta
NTP palvelin Ajan synkronointipalvelin (NTP-palvelin)
rsyslog-palvelin Etätietojen palvelin

Verkkoasetukset, joissa on määritetty kiinteä IPv4-osoite

Bluetooth asetukset

On Settings → Device configuration → Bluetooth, on nodes with Bluetooth.

Asetus Kuvaus
Bluetooth käytössä Ota Bluetooth-radio käyttöön tai poista käytöstä
Paritustila Kiinteä PIN-koodi, satunnainen PIN-koodi tai ei PIN-koodia
Kiinteä PIN-koodi Pariliitoksen PIN-koodi. Siinä on oltava täsmälleen kuusi numeroa — kenttä hylkää kaikki muut arvot

Turvallisuusasetukset

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

Asetus Kuvaus
Julkinen avain Radiosi julkinen avain (vain luku)
Ylläpitäjän avain Avaimet, joilla tätä radiota voidaan hallita etänä – enintään kolme
Yksityinen avain Radiosi yksityinen avain (säilytä turvallisesti). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it
Luo uusi yksityinen avain Luo tälle radiolle uuden avainparin vahvistuksen jälkeen. Kaikkien vanhan avaimesi tunteneiden vertaisradioiden on opittava uusi avain
Ylläpitokanava käytössä ⚠️ Poistettu — määritetään nyt automaattisesti, kun ylläpitoavain asetetaan
Sarjaporttikonsoli Serial console over the Stream API
Vianetsintälokirajapinta käytössä Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth
Hallintatila Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Voidaan valita vasta, kun järjestelmänvalvojan avain on määritetty
Varmuuskopioi avaimet Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Palauta avaimet Kirjoita varmuuskopioidut avaimet takaisin radioon (käytettävissä, kun varmuuskopio on olemassa)
Poista avaimen varmuuskopio Remove the stored key backup from this phone
Suojaustaso How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lukitustila

Lukitustila salaa laitteen tallennustilan ja edellyttää tunnuslausetta jokaiselle yhteydelle. It needs supporting firmware; the row doesn’t appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device.

Tunnuslauseen lisäksi määrität rajat, joiden täyttyessä istunto päättyy automaattisesti:

Kenttä Mitä se tekee
Jäljellä olevat käynnistykset Kuinka monen käynnistyksen ajan avattu tila säilyy
Tuntia vanhenemiseen saakka Avatun tilan enimmäiskesto
Istunnon enimmäiskesto (minuuttia) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Kun lukitustila on käytössä, tässä lukee Aktiivinen – tallennustila salattu, tämä yhteys todennettu, kun yhteys on avattu, tai Aktiivinen – avaa tämä yhteys antamalla tunnuslause, kun sitä ei ole avattu. Lukitse nyt päättää nykyisen istunnon välittömästi. Toistuvat virheelliset tunnuslauseet rajoitetaan odotusajalla, ennen kuin voit yrittää uudelleen.

⚠️ Varoitus: Tunnuslausetta ei voi palauttaa. Jos kadotat sen, laite on tyhjennettävä sen palauttamiseksi, jolloin sen avaimet, kanavat ja asetukset poistuvat.

Aiheeseen liittyvät aiheet

diff --git a/main/fr-rCA/user/discovery.html b/main/fr-rCA/user/discovery.html index 580ff43a32..6f889442da 100644 --- a/main/fr-rCA/user/discovery.html +++ b/main/fr-rCA/user/discovery.html @@ -266,7 +266,7 @@
  1. Navigate to Settings → Module configuration → Neighbor Info.
  2. Enable the module.
    3. -
  3. Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
    4. +
  4. Set Update Interval. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
  5. Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air.
diff --git a/main/fr-rCA/user/mqtt.html b/main/fr-rCA/user/mqtt.html index 7d5f49f14d..0814aa1381 100644 --- a/main/fr-rCA/user/mqtt.html +++ b/main/fr-rCA/user/mqtt.html @@ -135,7 +135,7 @@ TLS failing, the attempt timing out, or the broker rejecting your credentials wi

When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.

-

Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.

+

Turning it on opens a consent card. Turn on I agree. and choose a Map Publish Interval of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.

Reports appear at meshmap.net and similar community map services.

diff --git a/main/fr-rCA/user/settings-module-admin.html b/main/fr-rCA/user/settings-module-admin.html index a4386a40ae..7dd275ee5b 100644 --- a/main/fr-rCA/user/settings-module-admin.html +++ b/main/fr-rCA/user/settings-module-admin.html @@ -104,7 +104,7 @@ until you agree:

The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units - Intervalle de rapport cartographique (secondes) + Map Publish Interval How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered @@ -207,11 +207,11 @@ and each can drive the LED, the buzzer and the vibration motor separately, givin Send the alert through an I2S audio output instead - Durée de sortie (en millisecondes) + GPIO Output Duration How long a single alert lasts - Durée de répétition de la sortie (secondes) + Délai d’expiration du message Keep repeating the alert for this long until it is acknowledged. 0 disables nagging @@ -288,7 +288,7 @@ reverted to public.

Activate range testing - Intervalle de message de l’expéditeur (secondes) + Sender Interval Time between test transmissions, chosen from a dropdown of fixed intervals @@ -504,7 +504,7 @@ battery health often and sensors rarely.

Activate neighbor broadcasting - Intervalle de mise à jour (secondes) + Fréquence de récupération GPS How often to broadcast neighbor list @@ -572,11 +572,11 @@ battery health often and sensors rarely.

Enable the pin’s internal pull-up resistor - Diffusion minimale (secondes) + Minimum time between detection broadcasts Minimum time between alert broadcasts - Diffusion de l’État (secondes) + State Broadcast Interval Periodic state broadcast interval @@ -607,15 +607,15 @@ battery health often and sensors rarely.

Activate people counting - Intervalle de mise à jour (secondes) + Fréquence de récupération GPS How often to report counts - Wi-Fi RSSI threshold + WiFi Threshold (dBm) Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) - BLE RSSI threshold + BLE Threshold (dBm) The same cut-off for BLE advertisements (defaults to −80 dBm) diff --git a/main/fr-rCA/user/settings-radio-user.html b/main/fr-rCA/user/settings-radio-user.html index 4766b25771..fa6165ab9d 100644 --- a/main/fr-rCA/user/settings-radio-user.html +++ b/main/fr-rCA/user/settings-radio-user.html @@ -168,8 +168,8 @@ still the way in.

3 - Puissance d’émission - Transmission power (dBm); 0 = max allowed for region + Transmit Power (dBm) + Transmission power; 0 = max allowed for region 0 (region max) diff --git a/main/fr-rFR/user/discovery.html b/main/fr-rFR/user/discovery.html index 500cbc8ab8..e1b917e3c7 100644 --- a/main/fr-rFR/user/discovery.html +++ b/main/fr-rFR/user/discovery.html @@ -5,4 +5,4 @@ ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) -

Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:.

What to look for What it means
All hops show Good SNR (green) Healthy path — messages flow reliably
One hop shows a poor SNR (orange or red) Weak link — this relay segment is fragile
Many hops (4+) Long path — consider repositioning a node to shorten it
Different path on retry Mesh is adapting — multiple routes exist (this is good!)

💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network.

Troubleshooting with Traceroute

  • No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key.
  • Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa.
  • Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position.
  • Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric.

Informations sur les voisins

The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh.

Enabling Neighbor Info

  1. Navigate to Settings → Module configuration → Neighbor Info.
  2. Enable the module.
  3. Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
  4. Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air.

Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.

Viewing neighbor data

  • Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors.
  • Each neighbor entry shows the node that was directly heard and its signal quality.
  • Combine neighbor data from multiple nodes to understand the full mesh topology.

ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further.

Node list as a discovery tool

The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively.

Finding new nodes

  • Sort by Last heard to see the most recently active nodes at the top.
  • Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes.

Assessing connectivity

  • Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed.
  • Sort by Distance to find nearby nodes and verify they’re reachable.
  • Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge).

Infrastructure audit

  • Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes.
  • Check their signal quality and last-heard times to verify your infrastructure nodes are healthy.

See Nodes for full details on filtering and sorting options.

Tips for Mesh exploration

  • Start with traceroute — it gives you immediate, actionable information about a specific path.
  • Enable Neighbor Info on key nodes — especially routers and repeaters, to build a picture of the backbone.
  • Check the map — node positions on the Map combined with signal data help you understand why some links are strong and others are weak.
  • Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly.
+

Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:.

What to look for What it means
All hops show Good SNR (green) Healthy path — messages flow reliably
One hop shows a poor SNR (orange or red) Weak link — this relay segment is fragile
Many hops (4+) Long path — consider repositioning a node to shorten it
Different path on retry Mesh is adapting — multiple routes exist (this is good!)

💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network.

Troubleshooting with Traceroute

  • No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key.
  • Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa.
  • Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position.
  • Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric.

Informations sur les voisins

The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh.

Enabling Neighbor Info

  1. Navigate to Settings → Module configuration → Neighbor Info.
  2. Enable the module.
  3. Set Update Interval. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
  4. Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air.

Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.

Viewing neighbor data

  • Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors.
  • Each neighbor entry shows the node that was directly heard and its signal quality.
  • Combine neighbor data from multiple nodes to understand the full mesh topology.

ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further.

Node list as a discovery tool

The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively.

Finding new nodes

  • Sort by Last heard to see the most recently active nodes at the top.
  • Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes.

Assessing connectivity

  • Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed.
  • Sort by Distance to find nearby nodes and verify they’re reachable.
  • Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge).

Infrastructure audit

  • Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes.
  • Check their signal quality and last-heard times to verify your infrastructure nodes are healthy.

See Nodes for full details on filtering and sorting options.

Tips for Mesh exploration

  • Start with traceroute — it gives you immediate, actionable information about a specific path.
  • Enable Neighbor Info on key nodes — especially routers and repeaters, to build a picture of the backbone.
  • Check the map — node positions on the Map combined with signal data help you understand why some links are strong and others are weak.
  • Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly.
diff --git a/main/fr-rFR/user/mqtt.html b/main/fr-rFR/user/mqtt.html index 43c1301fb8..7fd905adf0 100644 --- a/main/fr-rFR/user/mqtt.html +++ b/main/fr-rFR/user/mqtt.html @@ -1,2 +1,2 @@ MQTT | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Français
Meshtastic Docs ↗

🌐 Français — Community translation View in English

MQTT

MQTT bridges your Meshtastic mesh network to the internet, enabling long-range communication beyond radio range.

Overview

The MQTT module connects your node to an MQTT broker, allowing:

  • Messages to reach nodes on different physical meshes via the internet
  • Integration with home automation and monitoring systems
  • Publishing node positions to the public Meshtastic map
  • Custom data pipelines for logging and alerting

How It Works 

[Your Node] → Radio → [Gateway Node with Wi-Fi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node]
-

A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh.

Configuration

Enabling MQTT

  1. Navigate to Settings → Module configuration → MQTT.
  2. Enable the MQTT module.
  3. Configure the broker connection:
Setting Description Par défaut
Address MQTT broker hostname mqtt.meshtastic.org
Username Broker authentication meshdev
Password Broker authentication large4cats
Root topic Base topic for messages msh, which the radio rewrites to msh/<REGION> once you set a region
Encryption enabled Encrypt MQTT payload Activé
JSON output enabled Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it Désactivé
TLS enabled Secure connection to broker Désactivé
Map reporting Report position to public map Désactivé
Proxy to client enabled Relay MQTT through the connected phone Désactivé

Connection Status and Test Connection

The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here.

Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason.

MQTT Proxy on This Phone

If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection.

ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them.

The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration.

Default Meshtastic Broker

The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing.

When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without).

🔒 Privacy: Messages on the public broker are readable by anyone subscribed. Always use channel encryption for private communications.

Private Broker

For better privacy and control, you can run your own MQTT broker:

  • Mosquitto (lightweight, open-source)
  • HiveMQ
  • EMQX

Configure your node to point to your private broker with appropriate credentials.

Map Reporting

When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.

Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.

Reports appear at meshmap.net and similar community map services.

🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published.

Direction Description
Uplink Messages from mesh → MQTT broker
Downlink Messages from MQTT broker → mesh

Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on.

Message Formats

MQTT carries two payload formats:

Format Description Use case
Protobuf Binary Meshtastic protobuf encoding Node-to-node mesh bridging
JSON Human-readable JSON on the /2/json/ topic Consumers outside the mesh (dashboards, home automation)

ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads.

Encryption & Privacy

Understanding the layered encryption model:

  1. Channel encryption happens on the mesh before MQTT. If your channel has a PSK, the MQTT payload is already encrypted — the broker and any subscribers see only the ciphertext.
  2. Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard.
  3. TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping.

🔒 Security: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications.

Best Practices

  • Use channel-level encryption (PSK) on channels that bridge to MQTT
  • Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes memory)
  • Use a private broker for sensitive deployments
  • Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh
  • Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back

Troubleshooting

MQTT Not Connecting

  • Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself.
  • Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces.
  • Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443).
  • DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly.

Messages Not Bridging

  • Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway.
  • Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage.
  • Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root.
  • Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway.
  • Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in.
+

A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh.

Configuration

Enabling MQTT

  1. Navigate to Settings → Module configuration → MQTT.
  2. Enable the MQTT module.
  3. Configure the broker connection:
Setting Description Par défaut
Address MQTT broker hostname mqtt.meshtastic.org
Username Broker authentication meshdev
Password Broker authentication large4cats
Root topic Base topic for messages msh, which the radio rewrites to msh/<REGION> once you set a region
Encryption enabled Encrypt MQTT payload Activé
JSON output enabled Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it Désactivé
TLS enabled Secure connection to broker Désactivé
Map reporting Report position to public map Désactivé
Proxy to client enabled Relay MQTT through the connected phone Désactivé

Connection Status and Test Connection

The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here.

Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason.

MQTT Proxy on This Phone

If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection.

ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them.

The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration.

Default Meshtastic Broker

The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing.

When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without).

🔒 Privacy: Messages on the public broker are readable by anyone subscribed. Always use channel encryption for private communications.

Private Broker

For better privacy and control, you can run your own MQTT broker:

  • Mosquitto (lightweight, open-source)
  • HiveMQ
  • EMQX

Configure your node to point to your private broker with appropriate credentials.

Map Reporting

When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.

Turning it on opens a consent card. Turn on I agree. and choose a Map Publish Interval of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.

Reports appear at meshmap.net and similar community map services.

🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published.

Direction Description
Uplink Messages from mesh → MQTT broker
Downlink Messages from MQTT broker → mesh

Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on.

Message Formats

MQTT carries two payload formats:

Format Description Use case
Protobuf Binary Meshtastic protobuf encoding Node-to-node mesh bridging
JSON Human-readable JSON on the /2/json/ topic Consumers outside the mesh (dashboards, home automation)

ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads.

Encryption & Privacy

Understanding the layered encryption model:

  1. Channel encryption happens on the mesh before MQTT. If your channel has a PSK, the MQTT payload is already encrypted — the broker and any subscribers see only the ciphertext.
  2. Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard.
  3. TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping.

🔒 Security: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications.

Best Practices

  • Use channel-level encryption (PSK) on channels that bridge to MQTT
  • Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes memory)
  • Use a private broker for sensitive deployments
  • Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh
  • Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back

Troubleshooting

MQTT Not Connecting

  • Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself.
  • Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces.
  • Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443).
  • DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly.

Messages Not Bridging

  • Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway.
  • Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage.
  • Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root.
  • Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway.
  • Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in.
diff --git a/main/fr-rFR/user/settings-module-admin.html b/main/fr-rFR/user/settings-module-admin.html index 8d5f40e13e..5c0b9274fe 100644 --- a/main/fr-rFR/user/settings-module-admin.html +++ b/main/fr-rFR/user/settings-module-admin.html @@ -1 +1 @@ - Settings — Modules & Admin | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Français
Meshtastic Docs ↗

🌐 Français — Community translation View in English

Settings — Modules & Admin

Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.

💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.

Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:

A toggle setting in the on position

A dropdown setting, expanded to show its list of options

A text field setting with a value entered

A module settings card with its title and grouped controls

Réglages du module

Every module lives under Settings → Module configuration.

⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes.

MQTT module

Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.

Setting Description
MQTT activé Toggle MQTT bridge
Adresse MQTT broker address
Nom d’utilisateur Authentication username
Mot de passe Authentication password
Chiffrement activé Encrypt MQTT payloads
Sortie JSON activée Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS activé Use secure connection
Sujet principal Base MQTT topic path
Proxy pour le client activé Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy on this phone The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT
Rapport cartographique Publish position to the public map — see the Map reporting group that follows

Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:

Setting Description
J’accepte. Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Intervalle de rapport cartographique (secondes) How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered

See MQTT for a detailed usage guide including encryption, privacy, and broker setup.

Serial module

Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.

Setting Description
Série activée Activate serial communication
Écho activé Echo received serial data back
Mode série Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX GPIO pins for the serial connection
Vitesse de transmission série Port speed
Délai d’expiration How long to wait before considering an incoming message complete
Outrepasser le port série de la console Take over the port the debug console normally uses

External Notification module

Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.

There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.

Setting Description
Notifications externes activées Master toggle for the module
Alert message LED / buzzer / vibra Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra Which outputs fire on a received bell character
LED extérieure (GPIO) Pin the LED is wired to
Sortie LED active à l’état haut Whether the LED pin is active high or low
Buzzer extérieur (GPIO) Pin the buzzer is wired to
Sortie vibreur (GPIO) Pin the vibration motor is wired to
Utiliser le buzzer PWM Drive the buzzer with PWM, which allows tones rather than a single pitch
Utiliser l’I2S comme buzzer Send the alert through an I2S audio output instead
Durée de sortie (en millisecondes) How long a single alert lasts
Durée de répétition de la sortie (secondes) Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Sonnerie The tone played on a PWM buzzer, in RTTTL. Can be imported from a file

Store & Forward module

Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.

Setting Description
Stocker & Transférer activé Activate store and forward
Battement de cœur (heartbeat) Periodically announce this node’s store-and-forward capability
Nombre d’enregistrements Maximum stored messages
Limite d’historique renvoyé Max messages to replay
Fenêtre de retour d’historique Time window for replay
Serveur Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)

💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.

Range Test module

⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.

Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.

Setting Description
Test de portée activé Activate range testing
Intervalle de message de l’expéditeur (secondes) Time between test transmissions, chosen from a dropdown of fixed intervals
Enregistrer .CSV dans le stockage (ESP32 seulement) Log received test data to the node’s own filesystem. ESP32 hardware only

Telemetry module

Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).

Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.

Setting Description
Envoyer la télémétrie de l’appareil Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Intervalle de mise à jour des mesures How often to report battery, uptime and channel utilization
Module de métriques de l’environnement activé Report the attached environment sensors
Intervalle de mise à jour des mesures d’environnement How often to report them
Mesures d’environnement à l’écran activées Also show these readings on the device’s own display
Les mesures environnementales utilisent Fahrenheit Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Module de mesure de la qualité de l’air activé Report particulate and CO₂ sensor data
Intervalle de mise à jour des mesures de qualité d’air How often to report them
Module de mesure de puissance activé Report the per-channel voltage and current readings
Intervalle de mise à jour des mesures d’alimentation How often to report them
Indicateurs d’alimentation à l’écran activés Also show power readings on the device’s display

See Telemetry & Sensors for supported sensors and configuration recommendations.

Canned Message module

Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.

Setting Description
Canned message enabled ⚠️ Deprecated in the protobuf schema
Messages Newline-separated list of messages
Envoyer une sonnerie Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Encodeur rotatif #1 activé Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port The three pins the encoder is wired to
Generate input event on Press / CW / CCW Which key event each encoder action produces
Entrée Haut/Bas/Select activée A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source ⚠️ Deprecated in the protobuf schema

Audio module

Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.

Setting Description
CODEC 2 activé Activate audio module
Taux d’échantillonnage CODEC2 Audio quality/bandwidth tradeoff
Broche PTT GPIO pin for the push-to-talk button
Selection de mot I2S GPIO pin for I2S WS
Données d’entrée I2S GPIO pin for I2S DIN
Données de sortie I2S GPIO pin for I2S DOUT
Horloge I2C GPIO pin for the I2S bit clock

ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.

Remote Hardware module

GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.

⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.

Setting Description
Matériel distant activé Activate remote GPIO access
Autoriser l’accès non défini aux broches Allow access to any GPIO pin (security risk)
Broches disponibles Up to 4 GPIO pins this node exposes for remote read/write

Neighbor Info module

Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.

Setting Description
Infos de voisinage activées Activate neighbor broadcasting
Intervalle de mise à jour (secondes) How often to broadcast neighbor list
Transmettre par LoRa Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name

See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.

Ambient Lighting module

Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.

Setting Description
État de la LED Turn the LED on or off
Actif LED current limit (0–31)
Red / Green / Blue Individual color channel values (0–255)

Detection Sensor module

Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.

Setting Description
Capteur de détection activé Activate detection sensor
Broche GPIO à surveiller GPIO pin connected to sensor
Type du déclencheur de détection How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Utiliser le mode INPUT_PULLUP Enable the pin’s internal pull-up resistor
Diffusion minimale (secondes) Minimum time between alert broadcasts
Diffusion de l’État (secondes) Periodic state broadcast interval
Envoyer une sonnerie avec un message d’alerte Include bell character in alerts
Nom convivial Custom name for this sensor

Paxcounter module

People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.

Paramètre Description
Paxcounter activé Activate people counting
Intervalle de mise à jour (secondes) How often to report counts
Wi-Fi RSSI threshold Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE RSSI threshold The same cut-off for BLE advertisements (defaults to −80 dBm)

💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.

Status Message module

The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.

Mesh Beacon module

Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.

TAK module

Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.

Administration

Administration à distance

Remotely configure nodes that share your admin key:

  1. Select the target node in the node list.
  2. Navigate to Settings for that node.
  3. Modify configuration.
  4. Tap Save — changes are sent over the mesh.

⚠️ Important: Requires an admin key configured on both your node and the target node.

Device Actions

Settings → Administration holds five one-shot actions, each behind a confirmation dialog:

Action What it does
Set time Sends your phone’s clock to the node
Redémarrer Restarts the node
Éteindre Powers the node down
Réinitialisation d’usine Returns every setting to its factory default
Reconfiguration de NodeDB Clears the node database. This dialog carries a Preserve Favorites? switch

⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.

Sauvegarder & Restaurer

Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.

Avancé

Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.

Nettoyer la base de données des nœuds

Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.

  • Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
  • Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.

The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.

Panneau de débogage

Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.

App Settings

The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:

Privacy

  • Allow analytics and crash reporting — opt in or out of diagnostics.
  • Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
  • Homoglyph encoding — how look-alike characters in names are handled.

Appearance

  • Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
  • Theme and Language.
  • Show full message timestamps.

Persistence

  • A cache limit for how much history is kept.
  • Export rangetest packets, Export all packets and Export node database.

On their own

  • Node Layout — how much detail each row of the node list shows.
  • Wi-Fi Provisioning for mPWRD-OS — see Connections.
  • Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
  • System AI — appears only where app functions are available; see App Functions.

A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.

A propros

Settings → About carries the app’s own identity rather than the node’s:

Three sections:

  • What is Meshtastic? — a short description of the project.
  • Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
  • Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.

The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.

Remerciements

Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.

Troubleshooting remote admin

  • “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
  • Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
  • Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
+ Settings — Modules & Admin | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Français
Meshtastic Docs ↗

🌐 Français — Community translation View in English

Settings — Modules & Admin

Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.

💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.

Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:

A toggle setting in the on position

A dropdown setting, expanded to show its list of options

A text field setting with a value entered

A module settings card with its title and grouped controls

Réglages du module

Every module lives under Settings → Module configuration.

⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes.

MQTT module

Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.

Setting Description
MQTT activé Toggle MQTT bridge
Adresse MQTT broker address
Nom d’utilisateur Authentication username
Mot de passe Authentication password
Chiffrement activé Encrypt MQTT payloads
Sortie JSON activée Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS activé Use secure connection
Sujet principal Base MQTT topic path
Proxy pour le client activé Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy on this phone The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT
Rapport cartographique Publish position to the public map — see the Map reporting group that follows

Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:

Setting Description
J’accepte. Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered

See MQTT for a detailed usage guide including encryption, privacy, and broker setup.

Serial module

Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.

Setting Description
Série activée Activate serial communication
Écho activé Echo received serial data back
Mode série Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX GPIO pins for the serial connection
Vitesse de transmission série Port speed
Délai d’expiration How long to wait before considering an incoming message complete
Outrepasser le port série de la console Take over the port the debug console normally uses

External Notification module

Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.

There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.

Setting Description
Notifications externes activées Master toggle for the module
Alert message LED / buzzer / vibra Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra Which outputs fire on a received bell character
LED extérieure (GPIO) Pin the LED is wired to
Sortie LED active à l’état haut Whether the LED pin is active high or low
Buzzer extérieur (GPIO) Pin the buzzer is wired to
Sortie vibreur (GPIO) Pin the vibration motor is wired to
Utiliser le buzzer PWM Drive the buzzer with PWM, which allows tones rather than a single pitch
Utiliser l’I2S comme buzzer Send the alert through an I2S audio output instead
GPIO Output Duration How long a single alert lasts
Délai d’expiration du message Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Sonnerie The tone played on a PWM buzzer, in RTTTL. Can be imported from a file

Store & Forward module

Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.

Setting Description
Stocker & Transférer activé Activate store and forward
Battement de cœur (heartbeat) Periodically announce this node’s store-and-forward capability
Nombre d’enregistrements Maximum stored messages
Limite d’historique renvoyé Max messages to replay
Fenêtre de retour d’historique Time window for replay
Serveur Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)

💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.

Range Test module

⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.

Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.

Setting Description
Test de portée activé Activate range testing
Sender Interval Time between test transmissions, chosen from a dropdown of fixed intervals
Enregistrer .CSV dans le stockage (ESP32 seulement) Log received test data to the node’s own filesystem. ESP32 hardware only

Telemetry module

Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).

Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.

Setting Description
Envoyer la télémétrie de l’appareil Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Intervalle de mise à jour des mesures How often to report battery, uptime and channel utilization
Module de métriques de l’environnement activé Report the attached environment sensors
Intervalle de mise à jour des mesures d’environnement How often to report them
Mesures d’environnement à l’écran activées Also show these readings on the device’s own display
Les mesures environnementales utilisent Fahrenheit Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Module de mesure de la qualité de l’air activé Report particulate and CO₂ sensor data
Intervalle de mise à jour des mesures de qualité d’air How often to report them
Module de mesure de puissance activé Report the per-channel voltage and current readings
Intervalle de mise à jour des mesures d’alimentation How often to report them
Indicateurs d’alimentation à l’écran activés Also show power readings on the device’s display

See Telemetry & Sensors for supported sensors and configuration recommendations.

Canned Message module

Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.

Setting Description
Canned message enabled ⚠️ Deprecated in the protobuf schema
Messages Newline-separated list of messages
Envoyer une sonnerie Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Encodeur rotatif #1 activé Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port The three pins the encoder is wired to
Generate input event on Press / CW / CCW Which key event each encoder action produces
Entrée Haut/Bas/Select activée A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source ⚠️ Deprecated in the protobuf schema

Audio module

Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.

Setting Description
CODEC 2 activé Activate audio module
Taux d’échantillonnage CODEC2 Audio quality/bandwidth tradeoff
Broche PTT GPIO pin for the push-to-talk button
Selection de mot I2S GPIO pin for I2S WS
Données d’entrée I2S GPIO pin for I2S DIN
Données de sortie I2S GPIO pin for I2S DOUT
Horloge I2C GPIO pin for the I2S bit clock

ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.

Remote Hardware module

GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.

⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.

Setting Description
Matériel distant activé Activate remote GPIO access
Autoriser l’accès non défini aux broches Allow access to any GPIO pin (security risk)
Broches disponibles Up to 4 GPIO pins this node exposes for remote read/write

Neighbor Info module

Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.

Setting Description
Infos de voisinage activées Activate neighbor broadcasting
Fréquence de récupération GPS How often to broadcast neighbor list
Transmettre par LoRa Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name

See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.

Ambient Lighting module

Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.

Setting Description
État de la LED Turn the LED on or off
Actif LED current limit (0–31)
Red / Green / Blue Individual color channel values (0–255)

Detection Sensor module

Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.

Setting Description
Capteur de détection activé Activate detection sensor
Broche GPIO à surveiller GPIO pin connected to sensor
Type du déclencheur de détection How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Utiliser le mode INPUT_PULLUP Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts Minimum time between alert broadcasts
State Broadcast Interval Periodic state broadcast interval
Envoyer une sonnerie avec un message d’alerte Include bell character in alerts
Nom convivial Custom name for this sensor

Paxcounter module

People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.

Paramètre Description
Paxcounter activé Activate people counting
Fréquence de récupération GPS How often to report counts
WiFi Threshold (dBm) Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm) The same cut-off for BLE advertisements (defaults to −80 dBm)

💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.

Status Message module

The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.

Mesh Beacon module

Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.

TAK module

Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.

Administration

Administration à distance

Remotely configure nodes that share your admin key:

  1. Select the target node in the node list.
  2. Navigate to Settings for that node.
  3. Modify configuration.
  4. Tap Save — changes are sent over the mesh.

⚠️ Important: Requires an admin key configured on both your node and the target node.

Device Actions

Settings → Administration holds five one-shot actions, each behind a confirmation dialog:

Action What it does
Set time Sends your phone’s clock to the node
Redémarrer Restarts the node
Éteindre Powers the node down
Réinitialisation d’usine Returns every setting to its factory default
Reconfiguration de NodeDB Clears the node database. This dialog carries a Preserve Favorites? switch

⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.

Sauvegarder & Restaurer

Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.

Avancé

Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.

Nettoyer la base de données des nœuds

Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.

  • Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
  • Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.

The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.

Panneau de débogage

Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.

App Settings

The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:

Privacy

  • Allow analytics and crash reporting — opt in or out of diagnostics.
  • Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
  • Homoglyph encoding — how look-alike characters in names are handled.

Appearance

  • Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
  • Theme and Language.
  • Show full message timestamps.

Persistence

  • A cache limit for how much history is kept.
  • Export rangetest packets, Export all packets and Export node database.

On their own

  • Node Layout — how much detail each row of the node list shows.
  • Wi-Fi Provisioning for mPWRD-OS — see Connections.
  • Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
  • System AI — appears only where app functions are available; see App Functions.

A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.

A propros

Settings → About carries the app’s own identity rather than the node’s:

Three sections:

  • What is Meshtastic? — a short description of the project.
  • Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
  • Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.

The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.

Remerciements

Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.

Troubleshooting remote admin

  • “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
  • Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
  • Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
diff --git a/main/fr-rFR/user/settings-radio-user.html b/main/fr-rFR/user/settings-radio-user.html index 5cef87cd7e..812b2dada0 100644 --- a/main/fr-rFR/user/settings-radio-user.html +++ b/main/fr-rFR/user/settings-radio-user.html @@ -1 +1 @@ - Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Français
Meshtastic Docs ↗

🌐 Français — Community translation View in English

Settings — Radio & User

Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How these screens work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

Paramètres utilisateur

User Profile

On Settings → User.

Setting Description
Nom long Your display name (up to 39 characters)
Nom court 4-character abbreviated name
Statut du message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Non joignable par message Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur node (Ham) Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in.

Configuration

Configuration de l’appareil

On Settings → Device configuration → Device.

Setting Description Par défaut
Rôle de l’appareil Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Mode de réémission How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Intervalle de diffusion des infos nœud How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Double clic comme appui sur le bouton Treat a double tap as a button press Désactivé
Triple clic pour faire un ping Ad Hoc Send an ad-hoc position ping on a triple click Activé
LED de vérification de fonctionnement (heartbeat) Blink the status LED periodically Activé
Fuseau horaire POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it —
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to —

Configuration LoRa

On Settings → LoRa.

Setting Description Par défaut
Région Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number Unset (must configure)
Préréglages Speed/range tradeoff LongFast
Nombre de sauts Maximum retransmit hops 3
Puissance d’émission Transmission power (dBm); 0 = max allowed for region 0 (region max)
Remplacer la fréquence Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Utiliser un préréglage On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Facteur de propagation Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead From preset
Taux de codage Manual mode only: 5–8. More redundancy costs airtime From preset
Bande Passante Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Slot de fréquence Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmission activée Turning this off makes the node receive-only On
Autoriser le dépassement du temps d’émission autorisé par heure Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Éteint
Ignorer MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Transmission des paquets vers MQTT Allow your packets to be forwarded to MQTT by gateways Éteint
Gain RX Boosté Extra receive gain on SX126x radios; costs a little current Éteint
Ventilateur PA désactivé Turn off the power-amplifier fan on hardware that has one Éteint

The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set.

Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Vitesse SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a modem preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Configuration de l’écran

On Settings → Device configuration → Display. These control the node’s own screen, not the app’s.

Setting Description
Écran allumé pour How long the display stays lit before sleeping
Intervalle du carrousel How often the node cycles between screens on its own
Mode d’affichage Screen layout/density used by the firmware
Unités d’affichage Metric or Imperial on the node’s screen
Utiliser le format horaire 12h Show the node’s clock as 12-hour rather than 24-hour
Titre en gras Draw the screen’s heading text in bold
Inverser l’écran Rotate the display 180° for an inverted mounting
Type d’OLED Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED
Réveil par appui ou mouvement Light the screen when the node is tapped or moved
Orientation de la boussole Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each
Toujours pointer vers le nord Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Configuration de la position

On Settings → Device configuration → Position.

Setting Description
Mode GPS (matériel physique) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
Fréquence de récupération GPS How often the node asks its GPS for a fix
Intervalle de diffusion How often the position is shared with the mesh
Position Intelligente Broadcast based on movement rather than purely on the clock
Intervalle intelligent With Smart Position on, the shortest gap between broadcasts
Distance intelligente With Smart Position on, how far you must move before broadcasting
Position fixe Use a manually entered latitude, longitude and altitude instead of the GPS
Champs de position A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Configuration de l’alimentation

On Settings → Device configuration → Power.

Setting Description
Activer le mode économie d’énergie Let the node sleep aggressively between activity
Arrêt en cas de perte d’alimentation Power the device down after external power disappears
Durée du sommeil extra profond How long the deepest sleep state lasts
Durée minimale de réveil The shortest time the node stays awake once woken
Durée d’attente max du Bluetooth How long to wait for a phone to connect before sleeping
Remplacer le multiplicateur ADC Turn on a manual correction for battery-voltage readings
Facteur de remplacement du multiplicateur ADC The correction factor itself, used only when the override is on
Adresse I2C de la batterie INA_2XX Address of an external INA-series power sensor, if fitted

Configuration du réseau

On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node.

Setting Description
Wi-Fi enabled Enable the Wi-Fi node (ESP32 nodes)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Mot de passe Mot de passe du réseau
Ethernet activé Use a wired connection on hardware that has one
Mode IPv4 DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
Serveur NTP Time synchronization server
Serveur Rsyslog Remote logging server

Network Config with a static IPv4 address entered

Configuration Bluetooth

On Settings → Device configuration → Bluetooth, on nodes with Bluetooth.

Setting Description
Bluetooth activé Enable/disable BLE radio
Mode d’appariement Fixed PIN, Random PIN, or No PIN
Code PIN fixe PIN code for pairing. Must be exactly six digits — the field rejects anything else

Configuration de sécurité

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

Setting Description
Clé publique Your node’s public key (read-only)
Clé Admin Keys permitted to administer this node remotely — up to three
Clé privée Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it
Régénérer la clé privée Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Console série Serial console over the Stream API
API de journalisation de débogage activée Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth
Mode géré Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set
Sauvegarder les clés Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Heures jusqu’à expiration Wall-clock lifetime of the unlocked state
Limite de sessions (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.

+ Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Français
Meshtastic Docs ↗

🌐 Français — Community translation View in English

Settings — Radio & User

Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How these screens work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

Paramètres utilisateur

User Profile

On Settings → User.

Setting Description
Nom long Your display name (up to 39 characters)
Nom court 4-character abbreviated name
Statut du message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Non joignable par message Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur node (Ham) Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in.

Configuration

Configuration de l’appareil

On Settings → Device configuration → Device.

Setting Description Par défaut
Rôle de l’appareil Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Mode de réémission How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Intervalle de diffusion des infos nœud How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Double clic comme appui sur le bouton Treat a double tap as a button press Désactivé
Triple clic pour faire un ping Ad Hoc Send an ad-hoc position ping on a triple click Activé
LED de vérification de fonctionnement (heartbeat) Blink the status LED periodically Activé
Fuseau horaire POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it —
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to —

Configuration LoRa

On Settings → LoRa.

Setting Description Par défaut
Région Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number Unset (must configure)
Préréglages Speed/range tradeoff LongFast
Nombre de sauts Maximum retransmit hops 3
Transmit Power (dBm) Transmission power; 0 = max allowed for region 0 (region max)
Remplacer la fréquence Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Utiliser un préréglage On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Facteur de propagation Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead From preset
Taux de codage Manual mode only: 5–8. More redundancy costs airtime From preset
Bande Passante Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Slot de fréquence Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmission activée Turning this off makes the node receive-only On
Autoriser le dépassement du temps d’émission autorisé par heure Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Éteint
Ignorer MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Transmission des paquets vers MQTT Allow your packets to be forwarded to MQTT by gateways Éteint
Gain RX Boosté Extra receive gain on SX126x radios; costs a little current Éteint
Ventilateur PA désactivé Turn off the power-amplifier fan on hardware that has one Éteint

The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set.

Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Vitesse SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a modem preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Configuration de l’écran

On Settings → Device configuration → Display. These control the node’s own screen, not the app’s.

Setting Description
Écran allumé pour How long the display stays lit before sleeping
Intervalle du carrousel How often the node cycles between screens on its own
Mode d’affichage Screen layout/density used by the firmware
Unités d’affichage Metric or Imperial on the node’s screen
Utiliser le format horaire 12h Show the node’s clock as 12-hour rather than 24-hour
Titre en gras Draw the screen’s heading text in bold
Inverser l’écran Rotate the display 180° for an inverted mounting
Type d’OLED Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED
Réveil par appui ou mouvement Light the screen when the node is tapped or moved
Orientation de la boussole Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each
Toujours pointer vers le nord Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Configuration de la position

On Settings → Device configuration → Position.

Setting Description
Mode GPS (matériel physique) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
Fréquence de récupération GPS How often the node asks its GPS for a fix
Intervalle de diffusion How often the position is shared with the mesh
Position Intelligente Broadcast based on movement rather than purely on the clock
Intervalle intelligent With Smart Position on, the shortest gap between broadcasts
Distance intelligente With Smart Position on, how far you must move before broadcasting
Position fixe Use a manually entered latitude, longitude and altitude instead of the GPS
Champs de position A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Configuration de l’alimentation

On Settings → Device configuration → Power.

Setting Description
Activer le mode économie d’énergie Let the node sleep aggressively between activity
Arrêt en cas de perte d’alimentation Power the device down after external power disappears
Durée du sommeil extra profond How long the deepest sleep state lasts
Durée minimale de réveil The shortest time the node stays awake once woken
Durée d’attente max du Bluetooth How long to wait for a phone to connect before sleeping
Remplacer le multiplicateur ADC Turn on a manual correction for battery-voltage readings
Facteur de remplacement du multiplicateur ADC The correction factor itself, used only when the override is on
Adresse I2C de la batterie INA_2XX Address of an external INA-series power sensor, if fitted

Configuration du réseau

On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node.

Setting Description
Wi-Fi enabled Enable the Wi-Fi node (ESP32 nodes)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Mot de passe Mot de passe du réseau
Ethernet activé Use a wired connection on hardware that has one
Mode IPv4 DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
Serveur NTP Time synchronization server
Serveur Rsyslog Remote logging server

Network Config with a static IPv4 address entered

Configuration Bluetooth

On Settings → Device configuration → Bluetooth, on nodes with Bluetooth.

Setting Description
Bluetooth activé Enable/disable BLE radio
Mode d’appariement Fixed PIN, Random PIN, or No PIN
Code PIN fixe PIN code for pairing. Must be exactly six digits — the field rejects anything else

Configuration de sécurité

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

Setting Description
Clé publique Your node’s public key (read-only)
Clé Admin Keys permitted to administer this node remotely — up to three
Clé privée Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it
Régénérer la clé privée Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Console série Serial console over the Stream API
API de journalisation de débogage activée Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth
Mode géré Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set
Sauvegarder les clés Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Heures jusqu’à expiration Wall-clock lifetime of the unlocked state
Limite de sessions (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.

diff --git a/main/ga-rIE/user/discovery.html b/main/ga-rIE/user/discovery.html index a917cb686e..8c79e9786b 100644 --- a/main/ga-rIE/user/discovery.html +++ b/main/ga-rIE/user/discovery.html @@ -5,4 +5,4 @@ ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) -

Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:.

What to look for What it means
All hops show Good SNR (green) Healthy path — messages flow reliably
One hop shows a poor SNR (orange or red) Weak link — this relay segment is fragile
Many hops (4+) Long path — consider repositioning a node to shorten it
Different path on retry Mesh is adapting — multiple routes exist (this is good!)

💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network.

Troubleshooting with Traceroute

  • No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key.
  • Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa.
  • Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position.
  • Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric.

Neighbor Info

The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh.

Enabling Neighbor Info

  1. Navigate to Settings → Module configuration → Neighbor Info.
  2. Enable the module.
  3. Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
  4. Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air.

Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.

Viewing neighbor data

  • Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors.
  • Each neighbor entry shows the node that was directly heard and its signal quality.
  • Combine neighbor data from multiple nodes to understand the full mesh topology.

ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further.

Node list as a discovery tool

The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively.

Finding new nodes

  • Sort by Last heard to see the most recently active nodes at the top.
  • Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes.

Assessing connectivity

  • Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed.
  • Sort by Distance to find nearby nodes and verify they’re reachable.
  • Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge).

Infrastructure audit

  • Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes.
  • Check their signal quality and last-heard times to verify your infrastructure nodes are healthy.

See Nodes for full details on filtering and sorting options.

Tips for Mesh exploration

  • Start with traceroute — it gives you immediate, actionable information about a specific path.
  • Enable Neighbor Info on key nodes — especially routers and repeaters, to build a picture of the backbone.
  • Check the map — node positions on the Map combined with signal data help you understand why some links are strong and others are weak.
  • Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly.
+

Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:.

What to look for What it means
All hops show Good SNR (green) Healthy path — messages flow reliably
One hop shows a poor SNR (orange or red) Weak link — this relay segment is fragile
Many hops (4+) Long path — consider repositioning a node to shorten it
Different path on retry Mesh is adapting — multiple routes exist (this is good!)

💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network.

Troubleshooting with Traceroute

  • No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key.
  • Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa.
  • Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position.
  • Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric.

Neighbor Info

The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh.

Enabling Neighbor Info

  1. Navigate to Settings → Module configuration → Neighbor Info.
  2. Enable the module.
  3. Set Update Interval. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
  4. Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air.

Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.

Viewing neighbor data

  • Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors.
  • Each neighbor entry shows the node that was directly heard and its signal quality.
  • Combine neighbor data from multiple nodes to understand the full mesh topology.

ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further.

Node list as a discovery tool

The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively.

Finding new nodes

  • Sort by Last heard to see the most recently active nodes at the top.
  • Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes.

Assessing connectivity

  • Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed.
  • Sort by Distance to find nearby nodes and verify they’re reachable.
  • Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge).

Infrastructure audit

  • Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes.
  • Check their signal quality and last-heard times to verify your infrastructure nodes are healthy.

See Nodes for full details on filtering and sorting options.

Tips for Mesh exploration

  • Start with traceroute — it gives you immediate, actionable information about a specific path.
  • Enable Neighbor Info on key nodes — especially routers and repeaters, to build a picture of the backbone.
  • Check the map — node positions on the Map combined with signal data help you understand why some links are strong and others are weak.
  • Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly.
diff --git a/main/ga-rIE/user/mqtt.html b/main/ga-rIE/user/mqtt.html index 4cc3336ed3..8e12f19421 100644 --- a/main/ga-rIE/user/mqtt.html +++ b/main/ga-rIE/user/mqtt.html @@ -1,2 +1,2 @@ MQTT | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Gaeilge
Meshtastic Docs ↗

🌐 Gaeilge — Community translation View in English

MQTT

MQTT bridges your Meshtastic mesh network to the internet, enabling long-range communication beyond radio range.

Overview

The MQTT module connects your node to an MQTT broker, allowing:

  • Messages to reach nodes on different physical meshes via the internet
  • Integration with home automation and monitoring systems
  • Publishing node positions to the public Meshtastic map
  • Custom data pipelines for logging and alerting

How It Works 

[Your Node] → Radio → [Gateway Node with Wi-Fi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node]
-

A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh.

Configuration

Enabling MQTT

  1. Navigate to Settings → Module configuration → MQTT.
  2. Enable the MQTT module.
  3. Configure the broker connection:
Setting Cur síos Default
Address MQTT broker hostname mqtt.meshtastic.org
Username Broker authentication meshdev
Password Broker authentication large4cats
Root topic Base topic for messages msh, which the radio rewrites to msh/<REGION> once you set a region
Encryption enabled Encrypt MQTT payload Enabled
JSON output enabled Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it Disabled
TLS enabled Secure connection to broker Disabled
Map reporting Report position to public map Disabled
Proxy to client enabled Relay MQTT through the connected phone Disabled

Connection Status and Test Connection

The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here.

Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason.

MQTT Proxy on This Phone

If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection.

ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them.

The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration.

Default Meshtastic Broker

The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing.

When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without).

🔒 Privacy: Messages on the public broker are readable by anyone subscribed. Always use channel encryption for private communications.

Private Broker

For better privacy and control, you can run your own MQTT broker:

  • Mosquitto (lightweight, open-source)
  • HiveMQ
  • EMQX

Configure your node to point to your private broker with appropriate credentials.

Map Reporting

When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.

Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.

Reports appear at meshmap.net and similar community map services.

🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published.

Direction Cur síos
Uplink Messages from mesh → MQTT broker
Downlink Messages from MQTT broker → mesh

Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on.

Message Formats

MQTT carries two payload formats:

Format Cur síos Use case
Protobuf Binary Meshtastic protobuf encoding Node-to-node mesh bridging
JSON Human-readable JSON on the /2/json/ topic Consumers outside the mesh (dashboards, home automation)

ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads.

Encryption & Privacy

Understanding the layered encryption model:

  1. Channel encryption happens on the mesh before MQTT. If your channel has a PSK, the MQTT payload is already encrypted — the broker and any subscribers see only the ciphertext.
  2. Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard.
  3. TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping.

🔒 Security: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications.

Best Practices

  • Use channel-level encryption (PSK) on channels that bridge to MQTT
  • Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes memory)
  • Use a private broker for sensitive deployments
  • Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh
  • Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back

Troubleshooting

MQTT Not Connecting

  • Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself.
  • Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces.
  • Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443).
  • DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly.

Messages Not Bridging

  • Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway.
  • Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage.
  • Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root.
  • Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway.
  • Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in.
+

A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh.

Configuration

Enabling MQTT

  1. Navigate to Settings → Module configuration → MQTT.
  2. Enable the MQTT module.
  3. Configure the broker connection:
Setting Cur síos Default
Address MQTT broker hostname mqtt.meshtastic.org
Username Broker authentication meshdev
Password Broker authentication large4cats
Root topic Base topic for messages msh, which the radio rewrites to msh/<REGION> once you set a region
Encryption enabled Encrypt MQTT payload Enabled
JSON output enabled Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it Disabled
TLS enabled Secure connection to broker Disabled
Map reporting Report position to public map Disabled
Proxy to client enabled Relay MQTT through the connected phone Disabled

Connection Status and Test Connection

The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here.

Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason.

MQTT Proxy on This Phone

If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection.

ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them.

The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration.

Default Meshtastic Broker

The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing.

When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without).

🔒 Privacy: Messages on the public broker are readable by anyone subscribed. Always use channel encryption for private communications.

Private Broker

For better privacy and control, you can run your own MQTT broker:

  • Mosquitto (lightweight, open-source)
  • HiveMQ
  • EMQX

Configure your node to point to your private broker with appropriate credentials.

Map Reporting

When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.

Turning it on opens a consent card. Turn on I agree. and choose a Map Publish Interval of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.

Reports appear at meshmap.net and similar community map services.

🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published.

Direction Cur síos
Uplink Messages from mesh → MQTT broker
Downlink Messages from MQTT broker → mesh

Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on.

Message Formats

MQTT carries two payload formats:

Format Cur síos Use case
Protobuf Binary Meshtastic protobuf encoding Node-to-node mesh bridging
JSON Human-readable JSON on the /2/json/ topic Consumers outside the mesh (dashboards, home automation)

ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads.

Encryption & Privacy

Understanding the layered encryption model:

  1. Channel encryption happens on the mesh before MQTT. If your channel has a PSK, the MQTT payload is already encrypted — the broker and any subscribers see only the ciphertext.
  2. Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard.
  3. TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping.

🔒 Security: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications.

Best Practices

  • Use channel-level encryption (PSK) on channels that bridge to MQTT
  • Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes memory)
  • Use a private broker for sensitive deployments
  • Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh
  • Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back

Troubleshooting

MQTT Not Connecting

  • Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself.
  • Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces.
  • Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443).
  • DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly.

Messages Not Bridging

  • Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway.
  • Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage.
  • Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root.
  • Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway.
  • Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in.
diff --git a/main/ga-rIE/user/settings-module-admin.html b/main/ga-rIE/user/settings-module-admin.html index 27b0594f31..b27183f321 100644 --- a/main/ga-rIE/user/settings-module-admin.html +++ b/main/ga-rIE/user/settings-module-admin.html @@ -1 +1 @@ - Settings — Modules & Admin | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Gaeilge
Meshtastic Docs ↗

🌐 Gaeilge — Community translation View in English

Settings — Modules & Admin

Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.

💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.

Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:

A toggle setting in the on position

A dropdown setting, expanded to show its list of options

A text field setting with a value entered

A module settings card with its title and grouped controls

Cumraíocht an mhódule

Every module lives under Settings → Module configuration.

⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes.

MQTT module

Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.

Setting Cur síos
MQTT enabled Toggle MQTT bridge
Address MQTT broker address
Username Authentication username
Password Authentication password
Encryption enabled Encrypt MQTT payloads
JSON output enabled Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS enabled Use secure connection
Root topic Base MQTT topic path
Proxy to client enabled Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy on this phone The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT
Map reporting Publish position to the public map — see the Map reporting group that follows

Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:

Setting Cur síos
I agree. Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map reporting interval (seconds) How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered

See MQTT for a detailed usage guide including encryption, privacy, and broker setup.

Serial module

Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.

Setting Cur síos
Serial enabled Activate serial communication
Echo enabled Echo received serial data back
Serial mode Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX GPIO pins for the serial connection
Serial baud rate Port speed
Am tráth How long to wait before considering an incoming message complete
Override console serial port Take over the port the debug console normally uses

External Notification module

Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.

There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.

Setting Cur síos
External notification enabled Master toggle for the module
Alert message LED / buzzer / vibra Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra Which outputs fire on a received bell character
Output LED (GPIO) Pin the LED is wired to
Output LED active high Whether the LED pin is active high or low
Output buzzer (GPIO) Pin the buzzer is wired to
Output vibra (GPIO) Pin the vibration motor is wired to
Use PWM buzzer Drive the buzzer with PWM, which allows tones rather than a single pitch
Use I2S as buzzer Send the alert through an I2S audio output instead
Output duration (milliseconds) How long a single alert lasts
Nag timeout (seconds) Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Ringtone The tone played on a PWM buzzer, in RTTTL. Can be imported from a file

Store & Forward module

Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.

Setting Cur síos
Store & Forward enabled Activate store and forward
Heartbeat Periodically announce this node’s store-and-forward capability
Number of records Maximum stored messages
History return max Max messages to replay
History return window Time window for replay
Server Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)

💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.

Range Test module

⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.

Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.

Setting Cur síos
Range test enabled Activate range testing
Sender message interval (seconds) Time between test transmissions, chosen from a dropdown of fixed intervals
Save .CSV in storage (ESP32 only) Log received test data to the node’s own filesystem. ESP32 hardware only

Telemetry module

Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).

Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.

Setting Cur síos
Send Device Telemetry Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval How often to report battery, uptime and channel utilization
Environment metrics module enabled Report the attached environment sensors
Environment metrics update interval How often to report them
Environment metrics on-screen enabled Also show these readings on the device’s own display
Environment metrics use Fahrenheit Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Air quality metrics module enabled Report particulate and CO₂ sensor data
Air quality metrics update interval How often to report them
Power metrics module enabled Report the per-channel voltage and current readings
Power metrics update interval How often to report them
Power metrics on-screen enabled Also show power readings on the device’s display

See Telemetry & Sensors for supported sensors and configuration recommendations.

Canned Message module

Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.

Setting Cur síos
Canned message enabled ⚠️ Deprecated in the protobuf schema
Messages Newline-separated list of messages
Send bell Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Rotary encoder #1 enabled Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port The three pins the encoder is wired to
Generate input event on Press / CW / CCW Which key event each encoder action produces
Up/Down/Select input enabled A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source ⚠️ Deprecated in the protobuf schema

Audio module

Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.

Setting Cur síos
CODEC 2 enabled Activate audio module
CODEC2 sample rate Audio quality/bandwidth tradeoff
PTT pin GPIO pin for the push-to-talk button
I2S word select GPIO pin for I2S WS
I2S data in GPIO pin for I2S DIN
I2S data out GPIO pin for I2S DOUT
I2S clock GPIO pin for the I2S bit clock

ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.

Remote Hardware module

GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.

⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.

Setting Cur síos
Remote Hardware enabled Activate remote GPIO access
Allow undefined pin access Allow access to any GPIO pin (security risk)
Available pins Up to 4 GPIO pins this node exposes for remote read/write

Neighbor Info module

Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.

Setting Cur síos
Neighbor Info enabled Activate neighbor broadcasting
Update interval (seconds) How often to broadcast neighbor list
Transmit over LoRa Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name

See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.

Ambient Lighting module

Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.

Setting Cur síos
LED state Turn the LED on or off
Current LED current limit (0–31)
Red / Green / Blue Individual color channel values (0–255)

Detection Sensor module

Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.

Setting Cur síos
Detection Sensor enabled Activate detection sensor
GPIO pin to monitor GPIO pin connected to sensor
Detection trigger type How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Use INPUT_PULLUP mode Enable the pin’s internal pull-up resistor
Minimum broadcast (seconds) Minimum time between alert broadcasts
State broadcast (seconds) Periodic state broadcast interval
Send bell with alert message Include bell character in alerts
Friendly name Custom name for this sensor

Paxcounter module

People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.

Setting Cur síos
Paxcounter enabled Activate people counting
Update interval (seconds) How often to report counts
Wi-Fi RSSI threshold Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE RSSI threshold The same cut-off for BLE advertisements (defaults to −80 dBm)

💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.

Status Message module

The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.

Mesh Beacon module

Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.

TAK module

Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.

Rialachas

Rialú iargúlta

Remotely configure nodes that share your admin key:

  1. Select the target node in the node list.
  2. Navigate to Settings for that node.
  3. Modify configuration.
  4. Tap Save — changes are sent over the mesh.

⚠️ Important: Requires an admin key configured on both your node and the target node.

Device Actions

Settings → Administration holds five one-shot actions, each behind a confirmation dialog:

Action What it does
Set time Sends your phone’s clock to the node
Athmhaoinigh Restarts the node
Dún Powers the node down
Athshocraigh an fhactaraí Returns every setting to its factory default
Athshocraigh NodeDB Clears the node database. This dialog carries a Preserve Favorites? switch

⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.

Backup & Restore

Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.

Advanced

Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.

Clean Node Database

Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.

  • Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
  • Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.

The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.

Painéal Laige

Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.

App Settings

The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:

Privacy

  • Allow analytics and crash reporting — opt in or out of diagnostics.
  • Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
  • Homoglyph encoding — how look-alike characters in names are handled.

Appearance

  • Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
  • Theme and Language.
  • Show full message timestamps.

Persistence

  • A cache limit for how much history is kept.
  • Export rangetest packets, Export all packets and Export node database.

On their own

  • Node Layout — how much detail each row of the node list shows.
  • Wi-Fi Provisioning for mPWRD-OS — see Connections.
  • Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
  • System AI — appears only where app functions are available; see App Functions.

A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.

Maidir le

Settings → About carries the app’s own identity rather than the node’s:

Three sections:

  • What is Meshtastic? — a short description of the project.
  • Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
  • Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.

The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.

Acknowledgements

Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.

Troubleshooting remote admin

  • “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
  • Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
  • Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
+ Settings — Modules & Admin | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Gaeilge
Meshtastic Docs ↗

🌐 Gaeilge — Community translation View in English

Settings — Modules & Admin

Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.

💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.

Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:

A toggle setting in the on position

A dropdown setting, expanded to show its list of options

A text field setting with a value entered

A module settings card with its title and grouped controls

Cumraíocht an mhódule

Every module lives under Settings → Module configuration.

⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes.

MQTT module

Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.

Setting Cur síos
MQTT enabled Toggle MQTT bridge
Address MQTT broker address
Username Authentication username
Password Authentication password
Encryption enabled Encrypt MQTT payloads
JSON output enabled Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS enabled Use secure connection
Root topic Base MQTT topic path
Proxy to client enabled Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy on this phone The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT
Map reporting Publish position to the public map — see the Map reporting group that follows

Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:

Setting Cur síos
I agree. Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered

See MQTT for a detailed usage guide including encryption, privacy, and broker setup.

Serial module

Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.

Setting Cur síos
Serial enabled Activate serial communication
Echo enabled Echo received serial data back
Serial mode Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX GPIO pins for the serial connection
Serial baud rate Port speed
Am tráth How long to wait before considering an incoming message complete
Override console serial port Take over the port the debug console normally uses

External Notification module

Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.

There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.

Setting Cur síos
External notification enabled Master toggle for the module
Alert message LED / buzzer / vibra Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra Which outputs fire on a received bell character
Output LED (GPIO) Pin the LED is wired to
Output LED active high Whether the LED pin is active high or low
Output buzzer (GPIO) Pin the buzzer is wired to
Output vibra (GPIO) Pin the vibration motor is wired to
Use PWM buzzer Drive the buzzer with PWM, which allows tones rather than a single pitch
Use I2S as buzzer Send the alert through an I2S audio output instead
GPIO Output Duration How long a single alert lasts
Nag Timeout Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Ringtone The tone played on a PWM buzzer, in RTTTL. Can be imported from a file

Store & Forward module

Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.

Setting Cur síos
Store & Forward enabled Activate store and forward
Heartbeat Periodically announce this node’s store-and-forward capability
Number of records Maximum stored messages
History return max Max messages to replay
History return window Time window for replay
Server Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)

💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.

Range Test module

⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.

Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.

Setting Cur síos
Range test enabled Activate range testing
Sender Interval Time between test transmissions, chosen from a dropdown of fixed intervals
Save .CSV in storage (ESP32 only) Log received test data to the node’s own filesystem. ESP32 hardware only

Telemetry module

Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).

Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.

Setting Cur síos
Send Device Telemetry Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval How often to report battery, uptime and channel utilization
Environment metrics module enabled Report the attached environment sensors
Environment metrics update interval How often to report them
Environment metrics on-screen enabled Also show these readings on the device’s own display
Environment metrics use Fahrenheit Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Air quality metrics module enabled Report particulate and CO₂ sensor data
Air quality metrics update interval How often to report them
Power metrics module enabled Report the per-channel voltage and current readings
Power metrics update interval How often to report them
Power metrics on-screen enabled Also show power readings on the device’s display

See Telemetry & Sensors for supported sensors and configuration recommendations.

Canned Message module

Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.

Setting Cur síos
Canned message enabled ⚠️ Deprecated in the protobuf schema
Messages Newline-separated list of messages
Send bell Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Rotary encoder #1 enabled Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port The three pins the encoder is wired to
Generate input event on Press / CW / CCW Which key event each encoder action produces
Up/Down/Select input enabled A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source ⚠️ Deprecated in the protobuf schema

Audio module

Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.

Setting Cur síos
CODEC 2 enabled Activate audio module
CODEC2 sample rate Audio quality/bandwidth tradeoff
PTT pin GPIO pin for the push-to-talk button
I2S word select GPIO pin for I2S WS
I2S data in GPIO pin for I2S DIN
I2S data out GPIO pin for I2S DOUT
I2S clock GPIO pin for the I2S bit clock

ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.

Remote Hardware module

GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.

⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.

Setting Cur síos
Remote Hardware enabled Activate remote GPIO access
Allow undefined pin access Allow access to any GPIO pin (security risk)
Available pins Up to 4 GPIO pins this node exposes for remote read/write

Neighbor Info module

Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.

Setting Cur síos
Neighbor Info enabled Activate neighbor broadcasting
Update Interval How often to broadcast neighbor list
Transmit over LoRa Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name

See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.

Ambient Lighting module

Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.

Setting Cur síos
LED state Turn the LED on or off
Current LED current limit (0–31)
Red / Green / Blue Individual color channel values (0–255)

Detection Sensor module

Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.

Setting Cur síos
Detection Sensor enabled Activate detection sensor
GPIO pin to monitor GPIO pin connected to sensor
Detection trigger type How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Use INPUT_PULLUP mode Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts Minimum time between alert broadcasts
State Broadcast Interval Periodic state broadcast interval
Send bell with alert message Include bell character in alerts
Friendly name Custom name for this sensor

Paxcounter module

People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.

Setting Cur síos
Paxcounter enabled Activate people counting
Update Interval How often to report counts
WiFi Threshold (dBm) Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm) The same cut-off for BLE advertisements (defaults to −80 dBm)

💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.

Status Message module

The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.

Mesh Beacon module

Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.

TAK module

Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.

Rialachas

Rialú iargúlta

Remotely configure nodes that share your admin key:

  1. Select the target node in the node list.
  2. Navigate to Settings for that node.
  3. Modify configuration.
  4. Tap Save — changes are sent over the mesh.

⚠️ Important: Requires an admin key configured on both your node and the target node.

Device Actions

Settings → Administration holds five one-shot actions, each behind a confirmation dialog:

Action What it does
Set time Sends your phone’s clock to the node
Athmhaoinigh Restarts the node
Dún Powers the node down
Athshocraigh an fhactaraí Returns every setting to its factory default
Athshocraigh NodeDB Clears the node database. This dialog carries a Preserve Favorites? switch

⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.

Backup & Restore

Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.

Advanced

Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.

Clean Node Database

Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.

  • Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
  • Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.

The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.

Painéal Laige

Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.

App Settings

The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:

Privacy

  • Allow analytics and crash reporting — opt in or out of diagnostics.
  • Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
  • Homoglyph encoding — how look-alike characters in names are handled.

Appearance

  • Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
  • Theme and Language.
  • Show full message timestamps.

Persistence

  • A cache limit for how much history is kept.
  • Export rangetest packets, Export all packets and Export node database.

On their own

  • Node Layout — how much detail each row of the node list shows.
  • Wi-Fi Provisioning for mPWRD-OS — see Connections.
  • Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
  • System AI — appears only where app functions are available; see App Functions.

A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.

Maidir le

Settings → About carries the app’s own identity rather than the node’s:

Three sections:

  • What is Meshtastic? — a short description of the project.
  • Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
  • Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.

The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.

Acknowledgements

Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.

Troubleshooting remote admin

  • “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
  • Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
  • Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
diff --git a/main/ga-rIE/user/settings-radio-user.html b/main/ga-rIE/user/settings-radio-user.html index 2c791a79dd..be8c2ce0fc 100644 --- a/main/ga-rIE/user/settings-radio-user.html +++ b/main/ga-rIE/user/settings-radio-user.html @@ -1 +1 @@ - Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Gaeilge
Meshtastic Docs ↗

🌐 Gaeilge — Community translation View in English

Settings — Radio & User

Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How these screens work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Cur síos
Long Name Your display name (up to 39 characters)
Short Name 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Unmessageable Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur node (Ham) Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in.

Configuration

Device Config

On Settings → Device configuration → Device.

Setting Cur síos Default
Device Role Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Rebroadcast Mode How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Node Info Broadcast Interval How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Double Tap as Button Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Enabled
LED Heartbeat Blink the status LED periodically Enabled
Time Zone POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it —
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to —

LoRa Config

On Settings → LoRa.

Setting Cur síos Default
Réigiún Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number Unset (must configure)
Presets Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Transmit Power Transmission power (dBm); 0 = max allowed for region 0 (region max)
Frequency Override Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Use Preset On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead From preset
Coding Rate Manual mode only: 5–8. More redundancy costs airtime From preset
Bandwidth Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Frequency Slot Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmit Enabled Turning this off makes the node receive-only On
Override Duty Cycle Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
Ignore MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok to MQTT Allow your packets to be forwarded to MQTT by gateways Off
RX Boosted Gain Extra receive gain on SX126x radios; costs a little current Off
PA fan disabled Turn off the power-amplifier fan on hardware that has one Off

The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set.

Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Speed SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a modem preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Display Config

On Settings → Device configuration → Display. These control the node’s own screen, not the app’s.

Setting Cur síos
Screen on for How long the display stays lit before sleeping
Carousel interval How often the node cycles between screens on its own
Display mode Screen layout/density used by the firmware
Display units Metric or Imperial on the node’s screen
Use 12h clock format Show the node’s clock as 12-hour rather than 24-hour
Bold Heading Draw the screen’s heading text in bold
Flip screen Rotate the display 180° for an inverted mounting
OLED type Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED
Wake on tap or motion Light the screen when the node is tapped or moved
Compass orientation Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each
Always point north Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Position Config

On Settings → Device configuration → Position.

Setting Cur síos
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the node asks its GPS for a fix
Broadcast Interval How often the position is shared with the mesh
Smart Position Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Fixed Position Use a manually entered latitude, longitude and altitude instead of the GPS
Position Flags A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Power Config

On Settings → Device configuration → Power.

Setting Cur síos
Enable power saving mode Let the node sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the node stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC multiplier override ratio The correction factor itself, used only when the override is on
Battery INA_2XX I2C address Address of an external INA-series power sensor, if fitted

Network Config

On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node.

Setting Cur síos
Wi-Fi enabled Enable the Wi-Fi node (ESP32 nodes)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Password Network password
Ethernet enabled Use a wired connection on hardware that has one
IPv4 mode DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP server Time synchronization server
rsyslog server Remote logging server

Network Config with a static IPv4 address entered

Bluetooth Config

On Settings → Device configuration → Bluetooth, on nodes with Bluetooth.

Setting Cur síos
Bluetooth enabled Enable/disable BLE radio
Pairing mode Fixed PIN, Random PIN, or No PIN
Fixed PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Security Config

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

Setting Cur síos
Public Key Your node’s public key (read-only)
Admin Key Keys permitted to administer this node remotely — up to three
Private Key Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it
Regenerate Private Key Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Serial console Serial console over the Stream API
Debug log API enabled Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth
Managed Mode Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.

+ Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Gaeilge
Meshtastic Docs ↗

🌐 Gaeilge — Community translation View in English

Settings — Radio & User

Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How these screens work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Cur síos
Long Name Your display name (up to 39 characters)
Short Name 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Unmessageable Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur node (Ham) Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in.

Configuration

Device Config

On Settings → Device configuration → Device.

Setting Cur síos Default
Device Role Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Rebroadcast Mode How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Node Info Broadcast Interval How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Double Tap as Button Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Enabled
LED Heartbeat Blink the status LED periodically Enabled
Time Zone POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it —
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to —

LoRa Config

On Settings → LoRa.

Setting Cur síos Default
Réigiún Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number Unset (must configure)
Presets Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Transmit Power (dBm) Transmission power; 0 = max allowed for region 0 (region max)
Frequency Override Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Use Preset On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead From preset
Coding Rate Manual mode only: 5–8. More redundancy costs airtime From preset
Bandwidth Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Frequency Slot Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmit Enabled Turning this off makes the node receive-only On
Override Duty Cycle Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
Ignore MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok to MQTT Allow your packets to be forwarded to MQTT by gateways Off
RX Boosted Gain Extra receive gain on SX126x radios; costs a little current Off
PA fan disabled Turn off the power-amplifier fan on hardware that has one Off

The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set.

Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Speed SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a modem preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Display Config

On Settings → Device configuration → Display. These control the node’s own screen, not the app’s.

Setting Cur síos
Screen on for How long the display stays lit before sleeping
Carousel interval How often the node cycles between screens on its own
Display mode Screen layout/density used by the firmware
Display units Metric or Imperial on the node’s screen
Use 12h clock format Show the node’s clock as 12-hour rather than 24-hour
Bold Heading Draw the screen’s heading text in bold
Flip screen Rotate the display 180° for an inverted mounting
OLED type Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED
Wake on tap or motion Light the screen when the node is tapped or moved
Compass orientation Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each
Always point north Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Position Config

On Settings → Device configuration → Position.

Setting Cur síos
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the node asks its GPS for a fix
Broadcast Interval How often the position is shared with the mesh
Smart Position Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Fixed Position Use a manually entered latitude, longitude and altitude instead of the GPS
Position Flags A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Power Config

On Settings → Device configuration → Power.

Setting Cur síos
Enable power saving mode Let the node sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the node stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC multiplier override ratio The correction factor itself, used only when the override is on
Battery INA_2XX I2C address Address of an external INA-series power sensor, if fitted

Network Config

On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node.

Setting Cur síos
Wi-Fi enabled Enable the Wi-Fi node (ESP32 nodes)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Password Network password
Ethernet enabled Use a wired connection on hardware that has one
IPv4 mode DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP server Time synchronization server
rsyslog server Remote logging server

Network Config with a static IPv4 address entered

Bluetooth Config

On Settings → Device configuration → Bluetooth, on nodes with Bluetooth.

Setting Cur síos
Bluetooth enabled Enable/disable BLE radio
Pairing mode Fixed PIN, Random PIN, or No PIN
Fixed PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Security Config

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

Setting Cur síos
Public Key Your node’s public key (read-only)
Admin Key Keys permitted to administer this node remotely — up to three
Private Key Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it
Regenerate Private Key Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Serial console Serial console over the Stream API
Debug log API enabled Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth
Managed Mode Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.

diff --git a/main/gl-rES/user/discovery.html b/main/gl-rES/user/discovery.html index 242395d74c..86bbf27c8a 100644 --- a/main/gl-rES/user/discovery.html +++ b/main/gl-rES/user/discovery.html @@ -5,4 +5,4 @@ ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) -

Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:.

What to look for What it means
All hops show Good SNR (green) Healthy path — messages flow reliably
One hop shows a poor SNR (orange or red) Weak link — this relay segment is fragile
Many hops (4+) Long path — consider repositioning a node to shorten it
Different path on retry Mesh is adapting — multiple routes exist (this is good!)

💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network.

Troubleshooting with Traceroute

  • No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key.
  • Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa.
  • Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position.
  • Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric.

Neighbor Info

The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh.

Enabling Neighbor Info

  1. Navigate to Settings → Module configuration → Neighbor Info.
  2. Enable the module.
  3. Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
  4. Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air.

Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.

Viewing neighbor data

  • Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors.
  • Each neighbor entry shows the node that was directly heard and its signal quality.
  • Combine neighbor data from multiple nodes to understand the full mesh topology.

ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further.

Node list as a discovery tool

The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively.

Finding new nodes

  • Sort by Last heard to see the most recently active nodes at the top.
  • Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes.

Assessing connectivity

  • Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed.
  • Sort by Distance to find nearby nodes and verify they’re reachable.
  • Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge).

Infrastructure audit

  • Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes.
  • Check their signal quality and last-heard times to verify your infrastructure nodes are healthy.

See Nodes for full details on filtering and sorting options.

Tips for Mesh exploration

  • Start with traceroute — it gives you immediate, actionable information about a specific path.
  • Enable Neighbor Info on key nodes — especially routers and repeaters, to build a picture of the backbone.
  • Check the map — node positions on the Map combined with signal data help you understand why some links are strong and others are weak.
  • Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly.
+

Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:.

What to look for What it means
All hops show Good SNR (green) Healthy path — messages flow reliably
One hop shows a poor SNR (orange or red) Weak link — this relay segment is fragile
Many hops (4+) Long path — consider repositioning a node to shorten it
Different path on retry Mesh is adapting — multiple routes exist (this is good!)

💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network.

Troubleshooting with Traceroute

  • No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key.
  • Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa.
  • Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position.
  • Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric.

Neighbor Info

The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh.

Enabling Neighbor Info

  1. Navigate to Settings → Module configuration → Neighbor Info.
  2. Enable the module.
  3. Set Update Interval. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
  4. Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air.

Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.

Viewing neighbor data

  • Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors.
  • Each neighbor entry shows the node that was directly heard and its signal quality.
  • Combine neighbor data from multiple nodes to understand the full mesh topology.

ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further.

Node list as a discovery tool

The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively.

Finding new nodes

  • Sort by Last heard to see the most recently active nodes at the top.
  • Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes.

Assessing connectivity

  • Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed.
  • Sort by Distance to find nearby nodes and verify they’re reachable.
  • Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge).

Infrastructure audit

  • Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes.
  • Check their signal quality and last-heard times to verify your infrastructure nodes are healthy.

See Nodes for full details on filtering and sorting options.

Tips for Mesh exploration

  • Start with traceroute — it gives you immediate, actionable information about a specific path.
  • Enable Neighbor Info on key nodes — especially routers and repeaters, to build a picture of the backbone.
  • Check the map — node positions on the Map combined with signal data help you understand why some links are strong and others are weak.
  • Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly.
diff --git a/main/gl-rES/user/mqtt.html b/main/gl-rES/user/mqtt.html index 5d74212134..f26c2d2fe0 100644 --- a/main/gl-rES/user/mqtt.html +++ b/main/gl-rES/user/mqtt.html @@ -1,2 +1,2 @@ MQTT | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Galego
Meshtastic Docs ↗

🌐 Galego — Community translation View in English

MQTT

MQTT bridges your Meshtastic mesh network to the internet, enabling long-range communication beyond radio range.

Overview

The MQTT module connects your node to an MQTT broker, allowing:

  • Messages to reach nodes on different physical meshes via the internet
  • Integration with home automation and monitoring systems
  • Publishing node positions to the public Meshtastic map
  • Custom data pipelines for logging and alerting

How It Works 

[Your Node] → Radio → [Gateway Node with Wi-Fi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node]
-

A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh.

Configuration

Enabling MQTT

  1. Navigate to Settings → Module configuration → MQTT.
  2. Enable the MQTT module.
  3. Configure the broker connection:
Setting Descrición Default
Address MQTT broker hostname mqtt.meshtastic.org
Username Broker authentication meshdev
Password Broker authentication large4cats
Root topic Base topic for messages msh, which the radio rewrites to msh/<REGION> once you set a region
Encryption enabled Encrypt MQTT payload Enabled
JSON output enabled Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it Disabled
TLS enabled Secure connection to broker Disabled
Map reporting Report position to public map Disabled
Proxy to client enabled Relay MQTT through the connected phone Disabled

Connection Status and Test Connection

The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here.

Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason.

MQTT Proxy on This Phone

If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection.

ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them.

The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration.

Default Meshtastic Broker

The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing.

When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without).

🔒 Privacy: Messages on the public broker are readable by anyone subscribed. Always use channel encryption for private communications.

Private Broker

For better privacy and control, you can run your own MQTT broker:

  • Mosquitto (lightweight, open-source)
  • HiveMQ
  • EMQX

Configure your node to point to your private broker with appropriate credentials.

Map Reporting

When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.

Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.

Reports appear at meshmap.net and similar community map services.

🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published.

Direction Descrición
Uplink Messages from mesh → MQTT broker
Downlink Messages from MQTT broker → mesh

Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on.

Message Formats

MQTT carries two payload formats:

Format Descrición Use case
Protobuf Binary Meshtastic protobuf encoding Node-to-node mesh bridging
JSON Human-readable JSON on the /2/json/ topic Consumers outside the mesh (dashboards, home automation)

ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads.

Encryption & Privacy

Understanding the layered encryption model:

  1. Channel encryption happens on the mesh before MQTT. If your channel has a PSK, the MQTT payload is already encrypted — the broker and any subscribers see only the ciphertext.
  2. Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard.
  3. TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping.

🔒 Security: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications.

Best Practices

  • Use channel-level encryption (PSK) on channels that bridge to MQTT
  • Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes memory)
  • Use a private broker for sensitive deployments
  • Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh
  • Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back

Troubleshooting

MQTT Not Connecting

  • Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself.
  • Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces.
  • Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443).
  • DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly.

Messages Not Bridging

  • Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway.
  • Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage.
  • Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root.
  • Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway.
  • Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in.
+

A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh.

Configuration

Enabling MQTT

  1. Navigate to Settings → Module configuration → MQTT.
  2. Enable the MQTT module.
  3. Configure the broker connection:
Setting Descrición Default
Address MQTT broker hostname mqtt.meshtastic.org
Username Broker authentication meshdev
Password Broker authentication large4cats
Root topic Base topic for messages msh, which the radio rewrites to msh/<REGION> once you set a region
Encryption enabled Encrypt MQTT payload Enabled
JSON output enabled Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it Disabled
TLS enabled Secure connection to broker Disabled
Map reporting Report position to public map Disabled
Proxy to client enabled Relay MQTT through the connected phone Disabled

Connection Status and Test Connection

The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here.

Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason.

MQTT Proxy on This Phone

If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection.

ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them.

The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration.

Default Meshtastic Broker

The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing.

When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without).

🔒 Privacy: Messages on the public broker are readable by anyone subscribed. Always use channel encryption for private communications.

Private Broker

For better privacy and control, you can run your own MQTT broker:

  • Mosquitto (lightweight, open-source)
  • HiveMQ
  • EMQX

Configure your node to point to your private broker with appropriate credentials.

Map Reporting

When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.

Turning it on opens a consent card. Turn on I agree. and choose a Map Publish Interval of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.

Reports appear at meshmap.net and similar community map services.

🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published.

Direction Descrición
Uplink Messages from mesh → MQTT broker
Downlink Messages from MQTT broker → mesh

Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on.

Message Formats

MQTT carries two payload formats:

Format Descrición Use case
Protobuf Binary Meshtastic protobuf encoding Node-to-node mesh bridging
JSON Human-readable JSON on the /2/json/ topic Consumers outside the mesh (dashboards, home automation)

ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads.

Encryption & Privacy

Understanding the layered encryption model:

  1. Channel encryption happens on the mesh before MQTT. If your channel has a PSK, the MQTT payload is already encrypted — the broker and any subscribers see only the ciphertext.
  2. Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard.
  3. TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping.

🔒 Security: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications.

Best Practices

  • Use channel-level encryption (PSK) on channels that bridge to MQTT
  • Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes memory)
  • Use a private broker for sensitive deployments
  • Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh
  • Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back

Troubleshooting

MQTT Not Connecting

  • Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself.
  • Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces.
  • Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443).
  • DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly.

Messages Not Bridging

  • Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway.
  • Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage.
  • Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root.
  • Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway.
  • Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in.
diff --git a/main/gl-rES/user/settings-module-admin.html b/main/gl-rES/user/settings-module-admin.html index fbd1ec6eb5..9b45baf3c9 100644 --- a/main/gl-rES/user/settings-module-admin.html +++ b/main/gl-rES/user/settings-module-admin.html @@ -1 +1 @@ - Settings — Modules & Admin | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Galego
Meshtastic Docs ↗

🌐 Galego — Community translation View in English

Settings — Modules & Admin

Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.

💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.

Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:

A toggle setting in the on position

A dropdown setting, expanded to show its list of options

A text field setting with a value entered

A module settings card with its title and grouped controls

Configuración de módulo

Every module lives under Settings → Module configuration.

⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes.

MQTT module

Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.

Setting Descrición
MQTT enabled Toggle MQTT bridge
Address MQTT broker address
Username Authentication username
Password Authentication password
Encryption enabled Encrypt MQTT payloads
JSON output enabled Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS enabled Use secure connection
Root topic Base MQTT topic path
Proxy to client enabled Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy on this phone The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT
Map reporting Publish position to the public map — see the Map reporting group that follows

Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:

Setting Descrición
I agree. Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map reporting interval (seconds) How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered

See MQTT for a detailed usage guide including encryption, privacy, and broker setup.

Serial module

Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.

Setting Descrición
Serial enabled Activate serial communication
Echo enabled Echo received serial data back
Serial mode Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX GPIO pins for the serial connection
Serial baud rate Port speed
Timeout How long to wait before considering an incoming message complete
Override console serial port Take over the port the debug console normally uses

External Notification module

Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.

There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.

Setting Descrición
External notification enabled Master toggle for the module
Alert message LED / buzzer / vibra Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra Which outputs fire on a received bell character
Output LED (GPIO) Pin the LED is wired to
Output LED active high Whether the LED pin is active high or low
Output buzzer (GPIO) Pin the buzzer is wired to
Output vibra (GPIO) Pin the vibration motor is wired to
Use PWM buzzer Drive the buzzer with PWM, which allows tones rather than a single pitch
Use I2S as buzzer Send the alert through an I2S audio output instead
Output duration (milliseconds) How long a single alert lasts
Nag timeout (seconds) Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Ringtone The tone played on a PWM buzzer, in RTTTL. Can be imported from a file

Store & Forward module

Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.

Setting Descrición
Store & Forward enabled Activate store and forward
Heartbeat Periodically announce this node’s store-and-forward capability
Number of records Maximum stored messages
History return max Max messages to replay
History return window Time window for replay
Server Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)

💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.

Range Test module

⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.

Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.

Setting Descrición
Range test enabled Activate range testing
Sender message interval (seconds) Time between test transmissions, chosen from a dropdown of fixed intervals
Save .CSV in storage (ESP32 only) Log received test data to the node’s own filesystem. ESP32 hardware only

Telemetry module

Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).

Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.

Setting Descrición
Send Device Telemetry Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval How often to report battery, uptime and channel utilization
Environment metrics module enabled Report the attached environment sensors
Environment metrics update interval How often to report them
Environment metrics on-screen enabled Also show these readings on the device’s own display
Environment metrics use Fahrenheit Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Air quality metrics module enabled Report particulate and CO₂ sensor data
Air quality metrics update interval How often to report them
Power metrics module enabled Report the per-channel voltage and current readings
Power metrics update interval How often to report them
Power metrics on-screen enabled Also show power readings on the device’s display

See Telemetry & Sensors for supported sensors and configuration recommendations.

Canned Message module

Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.

Setting Descrición
Canned message enabled ⚠️ Deprecated in the protobuf schema
Messages Newline-separated list of messages
Send bell Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Rotary encoder #1 enabled Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port The three pins the encoder is wired to
Generate input event on Press / CW / CCW Which key event each encoder action produces
Up/Down/Select input enabled A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source ⚠️ Deprecated in the protobuf schema

Audio module

Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.

Setting Descrición
CODEC 2 enabled Activate audio module
CODEC2 sample rate Audio quality/bandwidth tradeoff
PTT pin GPIO pin for the push-to-talk button
I2S word select GPIO pin for I2S WS
I2S data in GPIO pin for I2S DIN
I2S data out GPIO pin for I2S DOUT
I2S clock GPIO pin for the I2S bit clock

ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.

Remote Hardware module

GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.

⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.

Setting Descrición
Remote Hardware enabled Activate remote GPIO access
Allow undefined pin access Allow access to any GPIO pin (security risk)
Available pins Up to 4 GPIO pins this node exposes for remote read/write

Neighbor Info module

Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.

Setting Descrición
Neighbor Info enabled Activate neighbor broadcasting
Update interval (seconds) How often to broadcast neighbor list
Transmit over LoRa Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name

See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.

Ambient Lighting module

Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.

Setting Descrición
LED state Turn the LED on or off
Current LED current limit (0–31)
Red / Green / Blue Individual color channel values (0–255)

Detection Sensor module

Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.

Setting Descrición
Detection Sensor enabled Activate detection sensor
GPIO pin to monitor GPIO pin connected to sensor
Detection trigger type How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Use INPUT_PULLUP mode Enable the pin’s internal pull-up resistor
Minimum broadcast (seconds) Minimum time between alert broadcasts
State broadcast (seconds) Periodic state broadcast interval
Send bell with alert message Include bell character in alerts
Friendly name Custom name for this sensor

Paxcounter module

People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.

Setting Descrición
Paxcounter enabled Activate people counting
Update interval (seconds) How often to report counts
Wi-Fi RSSI threshold Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE RSSI threshold The same cut-off for BLE advertisements (defaults to −80 dBm)

💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.

Status Message module

The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.

Mesh Beacon module

Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.

TAK module

Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.

Administration

Remote Administration

Remotely configure nodes that share your admin key:

  1. Select the target node in the node list.
  2. Navigate to Settings for that node.
  3. Modify configuration.
  4. Tap Save — changes are sent over the mesh.

⚠️ Important: Requires an admin key configured on both your node and the target node.

Device Actions

Settings → Administration holds five one-shot actions, each behind a confirmation dialog:

Action What it does
Set time Sends your phone’s clock to the node
Reiniciar Restarts the node
Apagar Powers the node down
Restablecemento de fábrica Returns every setting to its factory default
Restablecer NodeDB Clears the node database. This dialog carries a Preserve Favorites? switch

⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.

Backup & Restore

Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.

Advanced

Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.

Clean Node Database

Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.

  • Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
  • Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.

The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.

Panel de depuración

Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.

App Settings

The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:

Privacy

  • Allow analytics and crash reporting — opt in or out of diagnostics.
  • Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
  • Homoglyph encoding — how look-alike characters in names are handled.

Appearance

  • Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
  • Theme and Language.
  • Show full message timestamps.

Persistence

  • A cache limit for how much history is kept.
  • Export rangetest packets, Export all packets and Export node database.

On their own

  • Node Layout — how much detail each row of the node list shows.
  • Wi-Fi Provisioning for mPWRD-OS — see Connections.
  • Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
  • System AI — appears only where app functions are available; see App Functions.

A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.

Acerca de

Settings → About carries the app’s own identity rather than the node’s:

Three sections:

  • What is Meshtastic? — a short description of the project.
  • Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
  • Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.

The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.

Acknowledgements

Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.

Troubleshooting remote admin

  • “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
  • Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
  • Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
+ Settings — Modules & Admin | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Galego
Meshtastic Docs ↗

🌐 Galego — Community translation View in English

Settings — Modules & Admin

Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.

💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.

Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:

A toggle setting in the on position

A dropdown setting, expanded to show its list of options

A text field setting with a value entered

A module settings card with its title and grouped controls

Configuración de módulo

Every module lives under Settings → Module configuration.

⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes.

MQTT module

Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.

Setting Descrición
MQTT enabled Toggle MQTT bridge
Address MQTT broker address
Username Authentication username
Password Authentication password
Encryption enabled Encrypt MQTT payloads
JSON output enabled Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS enabled Use secure connection
Root topic Base MQTT topic path
Proxy to client enabled Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy on this phone The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT
Map reporting Publish position to the public map — see the Map reporting group that follows

Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:

Setting Descrición
I agree. Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered

See MQTT for a detailed usage guide including encryption, privacy, and broker setup.

Serial module

Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.

Setting Descrición
Serial enabled Activate serial communication
Echo enabled Echo received serial data back
Serial mode Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX GPIO pins for the serial connection
Serial baud rate Port speed
Timeout How long to wait before considering an incoming message complete
Override console serial port Take over the port the debug console normally uses

External Notification module

Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.

There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.

Setting Descrición
External notification enabled Master toggle for the module
Alert message LED / buzzer / vibra Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra Which outputs fire on a received bell character
Output LED (GPIO) Pin the LED is wired to
Output LED active high Whether the LED pin is active high or low
Output buzzer (GPIO) Pin the buzzer is wired to
Output vibra (GPIO) Pin the vibration motor is wired to
Use PWM buzzer Drive the buzzer with PWM, which allows tones rather than a single pitch
Use I2S as buzzer Send the alert through an I2S audio output instead
GPIO Output Duration How long a single alert lasts
Nag Timeout Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Ringtone The tone played on a PWM buzzer, in RTTTL. Can be imported from a file

Store & Forward module

Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.

Setting Descrición
Store & Forward enabled Activate store and forward
Heartbeat Periodically announce this node’s store-and-forward capability
Number of records Maximum stored messages
History return max Max messages to replay
History return window Time window for replay
Server Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)

💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.

Range Test module

⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.

Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.

Setting Descrición
Range test enabled Activate range testing
Sender Interval Time between test transmissions, chosen from a dropdown of fixed intervals
Save .CSV in storage (ESP32 only) Log received test data to the node’s own filesystem. ESP32 hardware only

Telemetry module

Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).

Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.

Setting Descrición
Send Device Telemetry Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval How often to report battery, uptime and channel utilization
Environment metrics module enabled Report the attached environment sensors
Environment metrics update interval How often to report them
Environment metrics on-screen enabled Also show these readings on the device’s own display
Environment metrics use Fahrenheit Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Air quality metrics module enabled Report particulate and CO₂ sensor data
Air quality metrics update interval How often to report them
Power metrics module enabled Report the per-channel voltage and current readings
Power metrics update interval How often to report them
Power metrics on-screen enabled Also show power readings on the device’s display

See Telemetry & Sensors for supported sensors and configuration recommendations.

Canned Message module

Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.

Setting Descrición
Canned message enabled ⚠️ Deprecated in the protobuf schema
Messages Newline-separated list of messages
Send bell Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Rotary encoder #1 enabled Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port The three pins the encoder is wired to
Generate input event on Press / CW / CCW Which key event each encoder action produces
Up/Down/Select input enabled A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source ⚠️ Deprecated in the protobuf schema

Audio module

Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.

Setting Descrición
CODEC 2 enabled Activate audio module
CODEC2 sample rate Audio quality/bandwidth tradeoff
PTT pin GPIO pin for the push-to-talk button
I2S word select GPIO pin for I2S WS
I2S data in GPIO pin for I2S DIN
I2S data out GPIO pin for I2S DOUT
I2S clock GPIO pin for the I2S bit clock

ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.

Remote Hardware module

GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.

⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.

Setting Descrición
Remote Hardware enabled Activate remote GPIO access
Allow undefined pin access Allow access to any GPIO pin (security risk)
Available pins Up to 4 GPIO pins this node exposes for remote read/write

Neighbor Info module

Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.

Setting Descrición
Neighbor Info enabled Activate neighbor broadcasting
Update Interval How often to broadcast neighbor list
Transmit over LoRa Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name

See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.

Ambient Lighting module

Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.

Setting Descrición
LED state Turn the LED on or off
Current LED current limit (0–31)
Red / Green / Blue Individual color channel values (0–255)

Detection Sensor module

Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.

Setting Descrición
Detection Sensor enabled Activate detection sensor
GPIO pin to monitor GPIO pin connected to sensor
Detection trigger type How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Use INPUT_PULLUP mode Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts Minimum time between alert broadcasts
State Broadcast Interval Periodic state broadcast interval
Send bell with alert message Include bell character in alerts
Friendly name Custom name for this sensor

Paxcounter module

People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.

Setting Descrición
Paxcounter enabled Activate people counting
Update Interval How often to report counts
WiFi Threshold (dBm) Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm) The same cut-off for BLE advertisements (defaults to −80 dBm)

💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.

Status Message module

The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.

Mesh Beacon module

Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.

TAK module

Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.

Administration

Remote Administration

Remotely configure nodes that share your admin key:

  1. Select the target node in the node list.
  2. Navigate to Settings for that node.
  3. Modify configuration.
  4. Tap Save — changes are sent over the mesh.

⚠️ Important: Requires an admin key configured on both your node and the target node.

Device Actions

Settings → Administration holds five one-shot actions, each behind a confirmation dialog:

Action What it does
Set time Sends your phone’s clock to the node
Reiniciar Restarts the node
Apagar Powers the node down
Restablecemento de fábrica Returns every setting to its factory default
Restablecer NodeDB Clears the node database. This dialog carries a Preserve Favorites? switch

⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.

Backup & Restore

Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.

Advanced

Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.

Clean Node Database

Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.

  • Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
  • Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.

The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.

Panel de depuración

Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.

App Settings

The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:

Privacy

  • Allow analytics and crash reporting — opt in or out of diagnostics.
  • Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
  • Homoglyph encoding — how look-alike characters in names are handled.

Appearance

  • Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
  • Theme and Language.
  • Show full message timestamps.

Persistence

  • A cache limit for how much history is kept.
  • Export rangetest packets, Export all packets and Export node database.

On their own

  • Node Layout — how much detail each row of the node list shows.
  • Wi-Fi Provisioning for mPWRD-OS — see Connections.
  • Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
  • System AI — appears only where app functions are available; see App Functions.

A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.

Acerca de

Settings → About carries the app’s own identity rather than the node’s:

Three sections:

  • What is Meshtastic? — a short description of the project.
  • Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
  • Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.

The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.

Acknowledgements

Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.

Troubleshooting remote admin

  • “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
  • Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
  • Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
diff --git a/main/gl-rES/user/settings-radio-user.html b/main/gl-rES/user/settings-radio-user.html index d8a258a11d..498850d099 100644 --- a/main/gl-rES/user/settings-radio-user.html +++ b/main/gl-rES/user/settings-radio-user.html @@ -1 +1 @@ - Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Galego
Meshtastic Docs ↗

🌐 Galego — Community translation View in English

Settings — Radio & User

Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How these screens work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Descrición
Long Name Your display name (up to 39 characters)
Short Name 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Unmessageable Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur node (Ham) Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in.

Configuration

Device Config

On Settings → Device configuration → Device.

Setting Descrición Default
Device Role Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Rebroadcast Mode How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Node Info Broadcast Interval How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Double Tap as Button Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Enabled
LED Heartbeat Blink the status LED periodically Enabled
Time Zone POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it —
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to —

LoRa Config

On Settings → LoRa.

Setting Descrición Default
Rexión Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number Unset (must configure)
Presets Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Transmit Power Transmission power (dBm); 0 = max allowed for region 0 (region max)
Frequency Override Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Use Preset On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead From preset
Coding Rate Manual mode only: 5–8. More redundancy costs airtime From preset
Bandwidth Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Frequency Slot Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmit Enabled Turning this off makes the node receive-only On
Override Duty Cycle Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
Ignore MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok to MQTT Allow your packets to be forwarded to MQTT by gateways Off
RX Boosted Gain Extra receive gain on SX126x radios; costs a little current Off
PA fan disabled Turn off the power-amplifier fan on hardware that has one Off

The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set.

Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Speed SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a modem preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Display Config

On Settings → Device configuration → Display. These control the node’s own screen, not the app’s.

Setting Descrición
Screen on for How long the display stays lit before sleeping
Carousel interval How often the node cycles between screens on its own
Display mode Screen layout/density used by the firmware
Display units Metric or Imperial on the node’s screen
Use 12h clock format Show the node’s clock as 12-hour rather than 24-hour
Bold Heading Draw the screen’s heading text in bold
Flip screen Rotate the display 180° for an inverted mounting
OLED type Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED
Wake on tap or motion Light the screen when the node is tapped or moved
Compass orientation Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each
Always point north Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Position Config

On Settings → Device configuration → Position.

Setting Descrición
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the node asks its GPS for a fix
Broadcast Interval How often the position is shared with the mesh
Smart Position Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Fixed Position Use a manually entered latitude, longitude and altitude instead of the GPS
Position Flags A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Power Config

On Settings → Device configuration → Power.

Setting Descrición
Enable power saving mode Let the node sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the node stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC multiplier override ratio The correction factor itself, used only when the override is on
Battery INA_2XX I2C address Address of an external INA-series power sensor, if fitted

Network Config

On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node.

Setting Descrición
Wi-Fi enabled Enable the Wi-Fi node (ESP32 nodes)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Password Network password
Ethernet enabled Use a wired connection on hardware that has one
IPv4 mode DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP server Time synchronization server
rsyslog server Remote logging server

Network Config with a static IPv4 address entered

Bluetooth Config

On Settings → Device configuration → Bluetooth, on nodes with Bluetooth.

Setting Descrición
Bluetooth enabled Enable/disable BLE radio
Pairing mode Fixed PIN, Random PIN, or No PIN
Fixed PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Security Config

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

Setting Descrición
Public Key Your node’s public key (read-only)
Admin Key Keys permitted to administer this node remotely — up to three
Private Key Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it
Regenerate Private Key Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Serial console Serial console over the Stream API
Debug log API enabled Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth
Managed Mode Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.

+ Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Galego
Meshtastic Docs ↗

🌐 Galego — Community translation View in English

Settings — Radio & User

Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How these screens work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Descrición
Long Name Your display name (up to 39 characters)
Short Name 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Unmessageable Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur node (Ham) Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in.

Configuration

Device Config

On Settings → Device configuration → Device.

Setting Descrición Default
Device Role Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Rebroadcast Mode How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Node Info Broadcast Interval How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Double Tap as Button Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Enabled
LED Heartbeat Blink the status LED periodically Enabled
Time Zone POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it —
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to —

LoRa Config

On Settings → LoRa.

Setting Descrición Default
Rexión Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number Unset (must configure)
Presets Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Transmit Power (dBm) Transmission power; 0 = max allowed for region 0 (region max)
Frequency Override Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Use Preset On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead From preset
Coding Rate Manual mode only: 5–8. More redundancy costs airtime From preset
Bandwidth Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Frequency Slot Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmit Enabled Turning this off makes the node receive-only On
Override Duty Cycle Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
Ignore MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok to MQTT Allow your packets to be forwarded to MQTT by gateways Off
RX Boosted Gain Extra receive gain on SX126x radios; costs a little current Off
PA fan disabled Turn off the power-amplifier fan on hardware that has one Off

The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set.

Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Speed SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a modem preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Display Config

On Settings → Device configuration → Display. These control the node’s own screen, not the app’s.

Setting Descrición
Screen on for How long the display stays lit before sleeping
Carousel interval How often the node cycles between screens on its own
Display mode Screen layout/density used by the firmware
Display units Metric or Imperial on the node’s screen
Use 12h clock format Show the node’s clock as 12-hour rather than 24-hour
Bold Heading Draw the screen’s heading text in bold
Flip screen Rotate the display 180° for an inverted mounting
OLED type Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED
Wake on tap or motion Light the screen when the node is tapped or moved
Compass orientation Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each
Always point north Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Position Config

On Settings → Device configuration → Position.

Setting Descrición
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the node asks its GPS for a fix
Broadcast Interval How often the position is shared with the mesh
Smart Position Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Fixed Position Use a manually entered latitude, longitude and altitude instead of the GPS
Position Flags A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Power Config

On Settings → Device configuration → Power.

Setting Descrición
Enable power saving mode Let the node sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the node stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC multiplier override ratio The correction factor itself, used only when the override is on
Battery INA_2XX I2C address Address of an external INA-series power sensor, if fitted

Network Config

On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node.

Setting Descrición
Wi-Fi enabled Enable the Wi-Fi node (ESP32 nodes)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Password Network password
Ethernet enabled Use a wired connection on hardware that has one
IPv4 mode DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP server Time synchronization server
rsyslog server Remote logging server

Network Config with a static IPv4 address entered

Bluetooth Config

On Settings → Device configuration → Bluetooth, on nodes with Bluetooth.

Setting Descrición
Bluetooth enabled Enable/disable BLE radio
Pairing mode Fixed PIN, Random PIN, or No PIN
Fixed PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Security Config

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

Setting Descrición
Public Key Your node’s public key (read-only)
Admin Key Keys permitted to administer this node remotely — up to three
Private Key Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it
Regenerate Private Key Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Serial console Serial console over the Stream API
Debug log API enabled Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth
Managed Mode Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.

diff --git a/main/hr-rHR/user/discovery.html b/main/hr-rHR/user/discovery.html index deccf5d043..2996f1e160 100644 --- a/main/hr-rHR/user/discovery.html +++ b/main/hr-rHR/user/discovery.html @@ -5,4 +5,4 @@ ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) -

Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:.

What to look for What it means
All hops show Good SNR (green) Healthy path — messages flow reliably
One hop shows a poor SNR (orange or red) Weak link — this relay segment is fragile
Many hops (4+) Long path — consider repositioning a node to shorten it
Different path on retry Mesh is adapting — multiple routes exist (this is good!)

💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network.

Troubleshooting with Traceroute

  • No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key.
  • Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa.
  • Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position.
  • Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric.

Neighbor Info

The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh.

Enabling Neighbor Info

  1. Navigate to Settings → Module configuration → Neighbor Info.
  2. Enable the module.
  3. Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
  4. Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air.

Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.

Viewing neighbor data

  • Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors.
  • Each neighbor entry shows the node that was directly heard and its signal quality.
  • Combine neighbor data from multiple nodes to understand the full mesh topology.

ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further.

Node list as a discovery tool

The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively.

Finding new nodes

  • Sort by Last heard to see the most recently active nodes at the top.
  • Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes.

Assessing connectivity

  • Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed.
  • Sort by Distance to find nearby nodes and verify they’re reachable.
  • Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge).

Infrastructure audit

  • Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes.
  • Check their signal quality and last-heard times to verify your infrastructure nodes are healthy.

See Nodes for full details on filtering and sorting options.

Tips for Mesh exploration

  • Start with traceroute — it gives you immediate, actionable information about a specific path.
  • Enable Neighbor Info on key nodes — especially routers and repeaters, to build a picture of the backbone.
  • Check the map — node positions on the Map combined with signal data help you understand why some links are strong and others are weak.
  • Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly.
+

Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:.

What to look for What it means
All hops show Good SNR (green) Healthy path — messages flow reliably
One hop shows a poor SNR (orange or red) Weak link — this relay segment is fragile
Many hops (4+) Long path — consider repositioning a node to shorten it
Different path on retry Mesh is adapting — multiple routes exist (this is good!)

💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network.

Troubleshooting with Traceroute

  • No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key.
  • Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa.
  • Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position.
  • Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric.

Neighbor Info

The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh.

Enabling Neighbor Info

  1. Navigate to Settings → Module configuration → Neighbor Info.
  2. Enable the module.
  3. Set Update Interval. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
  4. Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air.

Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.

Viewing neighbor data

  • Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors.
  • Each neighbor entry shows the node that was directly heard and its signal quality.
  • Combine neighbor data from multiple nodes to understand the full mesh topology.

ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further.

Node list as a discovery tool

The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively.

Finding new nodes

  • Sort by Last heard to see the most recently active nodes at the top.
  • Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes.

Assessing connectivity

  • Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed.
  • Sort by Distance to find nearby nodes and verify they’re reachable.
  • Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge).

Infrastructure audit

  • Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes.
  • Check their signal quality and last-heard times to verify your infrastructure nodes are healthy.

See Nodes for full details on filtering and sorting options.

Tips for Mesh exploration

  • Start with traceroute — it gives you immediate, actionable information about a specific path.
  • Enable Neighbor Info on key nodes — especially routers and repeaters, to build a picture of the backbone.
  • Check the map — node positions on the Map combined with signal data help you understand why some links are strong and others are weak.
  • Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly.
diff --git a/main/hr-rHR/user/mqtt.html b/main/hr-rHR/user/mqtt.html index 5302e46345..6a311534c6 100644 --- a/main/hr-rHR/user/mqtt.html +++ b/main/hr-rHR/user/mqtt.html @@ -1,2 +1,2 @@ MQTT | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Hrvatski
Meshtastic Docs ↗

🌐 Hrvatski — Community translation View in English

MQTT

MQTT bridges your Meshtastic mesh network to the internet, enabling long-range communication beyond radio range.

Overview

The MQTT module connects your node to an MQTT broker, allowing:

  • Messages to reach nodes on different physical meshes via the internet
  • Integration with home automation and monitoring systems
  • Publishing node positions to the public Meshtastic map
  • Custom data pipelines for logging and alerting

How It Works 

[Your Node] → Radio → [Gateway Node with Wi-Fi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node]
-

A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh.

Configuration

Enabling MQTT

  1. Navigate to Settings → Module configuration → MQTT.
  2. Enable the MQTT module.
  3. Configure the broker connection:
Setting Opis Zadano
Address MQTT broker hostname mqtt.meshtastic.org
Username Broker authentication meshdev
Password Broker authentication large4cats
Root topic Base topic for messages msh, which the radio rewrites to msh/<REGION> once you set a region
Encryption enabled Encrypt MQTT payload Enabled
JSON output enabled Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it Disabled
TLS enabled Secure connection to broker Disabled
Map reporting Report position to public map Disabled
Proxy to client enabled Relay MQTT through the connected phone Disabled

Connection Status and Test Connection

The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here.

Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason.

MQTT Proxy on This Phone

If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection.

ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them.

The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration.

Default Meshtastic Broker

The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing.

When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without).

🔒 Privacy: Messages on the public broker are readable by anyone subscribed. Always use channel encryption for private communications.

Private Broker

For better privacy and control, you can run your own MQTT broker:

  • Mosquitto (lightweight, open-source)
  • HiveMQ
  • EMQX

Configure your node to point to your private broker with appropriate credentials.

Map Reporting

When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.

Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.

Reports appear at meshmap.net and similar community map services.

🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published.

Direction Opis
Uplink Messages from mesh → MQTT broker
Downlink Messages from MQTT broker → mesh

Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on.

Message Formats

MQTT carries two payload formats:

Format Opis Use case
Protobuf Binary Meshtastic protobuf encoding Node-to-node mesh bridging
JSON Human-readable JSON on the /2/json/ topic Consumers outside the mesh (dashboards, home automation)

ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads.

Encryption & Privacy

Understanding the layered encryption model:

  1. Channel encryption happens on the mesh before MQTT. If your channel has a PSK, the MQTT payload is already encrypted — the broker and any subscribers see only the ciphertext.
  2. Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard.
  3. TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping.

🔒 Security: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications.

Best Practices

  • Use channel-level encryption (PSK) on channels that bridge to MQTT
  • Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes memory)
  • Use a private broker for sensitive deployments
  • Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh
  • Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back

Troubleshooting

MQTT Not Connecting

  • Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself.
  • Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces.
  • Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443).
  • DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly.

Messages Not Bridging

  • Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway.
  • Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage.
  • Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root.
  • Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway.
  • Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in.
+

A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh.

Configuration

Enabling MQTT

  1. Navigate to Settings → Module configuration → MQTT.
  2. Enable the MQTT module.
  3. Configure the broker connection:
Setting Opis Zadano
Address MQTT broker hostname mqtt.meshtastic.org
Username Broker authentication meshdev
Password Broker authentication large4cats
Root topic Base topic for messages msh, which the radio rewrites to msh/<REGION> once you set a region
Encryption enabled Encrypt MQTT payload Enabled
JSON output enabled Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it Disabled
TLS enabled Secure connection to broker Disabled
Map reporting Report position to public map Disabled
Proxy to client enabled Relay MQTT through the connected phone Disabled

Connection Status and Test Connection

The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here.

Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason.

MQTT Proxy on This Phone

If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection.

ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them.

The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration.

Default Meshtastic Broker

The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing.

When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without).

🔒 Privacy: Messages on the public broker are readable by anyone subscribed. Always use channel encryption for private communications.

Private Broker

For better privacy and control, you can run your own MQTT broker:

  • Mosquitto (lightweight, open-source)
  • HiveMQ
  • EMQX

Configure your node to point to your private broker with appropriate credentials.

Map Reporting

When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.

Turning it on opens a consent card. Turn on I agree. and choose a Map Publish Interval of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.

Reports appear at meshmap.net and similar community map services.

🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published.

Direction Opis
Uplink Messages from mesh → MQTT broker
Downlink Messages from MQTT broker → mesh

Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on.

Message Formats

MQTT carries two payload formats:

Format Opis Use case
Protobuf Binary Meshtastic protobuf encoding Node-to-node mesh bridging
JSON Human-readable JSON on the /2/json/ topic Consumers outside the mesh (dashboards, home automation)

ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads.

Encryption & Privacy

Understanding the layered encryption model:

  1. Channel encryption happens on the mesh before MQTT. If your channel has a PSK, the MQTT payload is already encrypted — the broker and any subscribers see only the ciphertext.
  2. Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard.
  3. TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping.

🔒 Security: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications.

Best Practices

  • Use channel-level encryption (PSK) on channels that bridge to MQTT
  • Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes memory)
  • Use a private broker for sensitive deployments
  • Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh
  • Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back

Troubleshooting

MQTT Not Connecting

  • Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself.
  • Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces.
  • Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443).
  • DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly.

Messages Not Bridging

  • Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway.
  • Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage.
  • Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root.
  • Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway.
  • Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in.
diff --git a/main/hr-rHR/user/settings-module-admin.html b/main/hr-rHR/user/settings-module-admin.html index 9f173fc42f..fe401cbb38 100644 --- a/main/hr-rHR/user/settings-module-admin.html +++ b/main/hr-rHR/user/settings-module-admin.html @@ -1 +1 @@ - Settings — Modules & Admin | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Hrvatski
Meshtastic Docs ↗

🌐 Hrvatski — Community translation View in English

Settings — Modules & Admin

Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.

💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.

Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:

A toggle setting in the on position

A dropdown setting, expanded to show its list of options

A text field setting with a value entered

A module settings card with its title and grouped controls

Konfiguracija modula

Every module lives under Settings → Module configuration.

⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes.

MQTT module

Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.

Setting Opis
MQTT enabled Toggle MQTT bridge
Address MQTT broker address
Username Authentication username
Password Authentication password
Encryption enabled Encrypt MQTT payloads
JSON output enabled Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS enabled Use secure connection
Root topic Base MQTT topic path
Proxy to client enabled Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy on this phone The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT
Map reporting Publish position to the public map — see the Map reporting group that follows

Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:

Setting Opis
I agree. Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map reporting interval (seconds) How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered

See MQTT for a detailed usage guide including encryption, privacy, and broker setup.

Serial module

Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.

Setting Opis
Serial enabled Activate serial communication
Echo enabled Echo received serial data back
Serial mode Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX GPIO pins for the serial connection
Serial baud rate Port speed
Timeout How long to wait before considering an incoming message complete
Override console serial port Take over the port the debug console normally uses

External Notification module

Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.

There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.

Setting Opis
External notification enabled Master toggle for the module
Alert message LED / buzzer / vibra Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra Which outputs fire on a received bell character
Output LED (GPIO) Pin the LED is wired to
Output LED active high Whether the LED pin is active high or low
Output buzzer (GPIO) Pin the buzzer is wired to
Output vibra (GPIO) Pin the vibration motor is wired to
Use PWM buzzer Drive the buzzer with PWM, which allows tones rather than a single pitch
Use I2S as buzzer Send the alert through an I2S audio output instead
Output duration (milliseconds) How long a single alert lasts
Nag timeout (seconds) Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Ringtone The tone played on a PWM buzzer, in RTTTL. Can be imported from a file

Store & Forward module

Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.

Setting Opis
Store & Forward enabled Activate store and forward
Heartbeat Periodically announce this node’s store-and-forward capability
Number of records Maximum stored messages
History return max Max messages to replay
History return window Time window for replay
Server Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)

💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.

Range Test module

⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.

Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.

Setting Opis
Range test enabled Activate range testing
Sender message interval (seconds) Time between test transmissions, chosen from a dropdown of fixed intervals
Save .CSV in storage (ESP32 only) Log received test data to the node’s own filesystem. ESP32 hardware only

Telemetry module

Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).

Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.

Setting Opis
Send Device Telemetry Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval How often to report battery, uptime and channel utilization
Environment metrics module enabled Report the attached environment sensors
Environment metrics update interval How often to report them
Environment metrics on-screen enabled Also show these readings on the device’s own display
Environment metrics use Fahrenheit Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Air quality metrics module enabled Report particulate and CO₂ sensor data
Air quality metrics update interval How often to report them
Power metrics module enabled Report the per-channel voltage and current readings
Power metrics update interval How often to report them
Power metrics on-screen enabled Also show power readings on the device’s display

See Telemetry & Sensors for supported sensors and configuration recommendations.

Canned Message module

Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.

Setting Opis
Canned message enabled ⚠️ Deprecated in the protobuf schema
Messages Newline-separated list of messages
Send bell Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Rotary encoder #1 enabled Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port The three pins the encoder is wired to
Generate input event on Press / CW / CCW Which key event each encoder action produces
Up/Down/Select input enabled A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source ⚠️ Deprecated in the protobuf schema

Audio module

Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.

Setting Opis
CODEC 2 enabled Activate audio module
CODEC2 sample rate Audio quality/bandwidth tradeoff
PTT pin GPIO pin for the push-to-talk button
I2S word select GPIO pin for I2S WS
I2S data in GPIO pin for I2S DIN
I2S data out GPIO pin for I2S DOUT
I2S clock GPIO pin for the I2S bit clock

ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.

Remote Hardware module

GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.

⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.

Setting Opis
Remote Hardware enabled Activate remote GPIO access
Allow undefined pin access Allow access to any GPIO pin (security risk)
Available pins Up to 4 GPIO pins this node exposes for remote read/write

Neighbor Info module

Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.

Setting Opis
Neighbor Info enabled Activate neighbor broadcasting
Update interval (seconds) How often to broadcast neighbor list
Transmit over LoRa Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name

See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.

Ambient Lighting module

Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.

Setting Opis
LED state Turn the LED on or off
Current LED current limit (0–31)
Red / Green / Blue Individual color channel values (0–255)

Detection Sensor module

Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.

Setting Opis
Detection Sensor enabled Activate detection sensor
GPIO pin to monitor GPIO pin connected to sensor
Detection trigger type How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Use INPUT_PULLUP mode Enable the pin’s internal pull-up resistor
Minimum broadcast (seconds) Minimum time between alert broadcasts
State broadcast (seconds) Periodic state broadcast interval
Send bell with alert message Include bell character in alerts
Friendly name Custom name for this sensor

Paxcounter module

People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.

Setting Opis
Paxcounter enabled Activate people counting
Update interval (seconds) How often to report counts
Wi-Fi RSSI threshold Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE RSSI threshold The same cut-off for BLE advertisements (defaults to −80 dBm)

💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.

Status Message module

The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.

Mesh Beacon module

Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.

TAK module

Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.

Administration

Remote Administration

Remotely configure nodes that share your admin key:

  1. Select the target node in the node list.
  2. Navigate to Settings for that node.
  3. Modify configuration.
  4. Tap Save — changes are sent over the mesh.

⚠️ Important: Requires an admin key configured on both your node and the target node.

Device Actions

Settings → Administration holds five one-shot actions, each behind a confirmation dialog:

Action What it does
Set time Sends your phone’s clock to the node
Ponovno pokreni Restarts the node
Isključi Powers the node down
Vraćanje na tvorničke postavke Returns every setting to its factory default
Resetiraj NodeDB bazu Clears the node database. This dialog carries a Preserve Favorites? switch

⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.

Backup & Restore

Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.

Advanced

Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.

Clean Node Database

Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.

  • Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
  • Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.

The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.

Otklanjanje pogrešaka

Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.

App Settings

The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:

Privacy

  • Allow analytics and crash reporting — opt in or out of diagnostics.
  • Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
  • Homoglyph encoding — how look-alike characters in names are handled.

Appearance

  • Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
  • Theme and Language.
  • Show full message timestamps.

Persistence

  • A cache limit for how much history is kept.
  • Export rangetest packets, Export all packets and Export node database.

On their own

  • Node Layout — how much detail each row of the node list shows.
  • Wi-Fi Provisioning for mPWRD-OS — see Connections.
  • Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
  • System AI — appears only where app functions are available; see App Functions.

A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.

O programu

Settings → About carries the app’s own identity rather than the node’s:

Three sections:

  • What is Meshtastic? — a short description of the project.
  • Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
  • Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.

The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.

Acknowledgements

Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.

Troubleshooting remote admin

  • “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
  • Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
  • Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
+ Settings — Modules & Admin | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Hrvatski
Meshtastic Docs ↗

🌐 Hrvatski — Community translation View in English

Settings — Modules & Admin

Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.

💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.

Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:

A toggle setting in the on position

A dropdown setting, expanded to show its list of options

A text field setting with a value entered

A module settings card with its title and grouped controls

Konfiguracija modula

Every module lives under Settings → Module configuration.

⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes.

MQTT module

Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.

Setting Opis
MQTT enabled Toggle MQTT bridge
Address MQTT broker address
Username Authentication username
Password Authentication password
Encryption enabled Encrypt MQTT payloads
JSON output enabled Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS enabled Use secure connection
Root topic Base MQTT topic path
Proxy to client enabled Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy on this phone The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT
Map reporting Publish position to the public map — see the Map reporting group that follows

Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:

Setting Opis
I agree. Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered

See MQTT for a detailed usage guide including encryption, privacy, and broker setup.

Serial module

Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.

Setting Opis
Serial enabled Activate serial communication
Echo enabled Echo received serial data back
Serial mode Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX GPIO pins for the serial connection
Serial baud rate Port speed
Timeout How long to wait before considering an incoming message complete
Override console serial port Take over the port the debug console normally uses

External Notification module

Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.

There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.

Setting Opis
External notification enabled Master toggle for the module
Alert message LED / buzzer / vibra Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra Which outputs fire on a received bell character
Output LED (GPIO) Pin the LED is wired to
Output LED active high Whether the LED pin is active high or low
Output buzzer (GPIO) Pin the buzzer is wired to
Output vibra (GPIO) Pin the vibration motor is wired to
Use PWM buzzer Drive the buzzer with PWM, which allows tones rather than a single pitch
Use I2S as buzzer Send the alert through an I2S audio output instead
GPIO Output Duration How long a single alert lasts
Nag Timeout Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Ringtone The tone played on a PWM buzzer, in RTTTL. Can be imported from a file

Store & Forward module

Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.

Setting Opis
Store & Forward enabled Activate store and forward
Heartbeat Periodically announce this node’s store-and-forward capability
Number of records Maximum stored messages
History return max Max messages to replay
History return window Time window for replay
Server Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)

💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.

Range Test module

⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.

Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.

Setting Opis
Range test enabled Activate range testing
Sender Interval Time between test transmissions, chosen from a dropdown of fixed intervals
Save .CSV in storage (ESP32 only) Log received test data to the node’s own filesystem. ESP32 hardware only

Telemetry module

Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).

Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.

Setting Opis
Send Device Telemetry Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval How often to report battery, uptime and channel utilization
Environment metrics module enabled Report the attached environment sensors
Environment metrics update interval How often to report them
Environment metrics on-screen enabled Also show these readings on the device’s own display
Environment metrics use Fahrenheit Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Air quality metrics module enabled Report particulate and CO₂ sensor data
Air quality metrics update interval How often to report them
Power metrics module enabled Report the per-channel voltage and current readings
Power metrics update interval How often to report them
Power metrics on-screen enabled Also show power readings on the device’s display

See Telemetry & Sensors for supported sensors and configuration recommendations.

Canned Message module

Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.

Setting Opis
Canned message enabled ⚠️ Deprecated in the protobuf schema
Messages Newline-separated list of messages
Send bell Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Rotary encoder #1 enabled Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port The three pins the encoder is wired to
Generate input event on Press / CW / CCW Which key event each encoder action produces
Up/Down/Select input enabled A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source ⚠️ Deprecated in the protobuf schema

Audio module

Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.

Setting Opis
CODEC 2 enabled Activate audio module
CODEC2 sample rate Audio quality/bandwidth tradeoff
PTT pin GPIO pin for the push-to-talk button
I2S word select GPIO pin for I2S WS
I2S data in GPIO pin for I2S DIN
I2S data out GPIO pin for I2S DOUT
I2S clock GPIO pin for the I2S bit clock

ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.

Remote Hardware module

GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.

⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.

Setting Opis
Remote Hardware enabled Activate remote GPIO access
Allow undefined pin access Allow access to any GPIO pin (security risk)
Available pins Up to 4 GPIO pins this node exposes for remote read/write

Neighbor Info module

Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.

Setting Opis
Neighbor Info enabled Activate neighbor broadcasting
Update Interval How often to broadcast neighbor list
Transmit over LoRa Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name

See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.

Ambient Lighting module

Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.

Setting Opis
LED state Turn the LED on or off
Current LED current limit (0–31)
Red / Green / Blue Individual color channel values (0–255)

Detection Sensor module

Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.

Setting Opis
Detection Sensor enabled Activate detection sensor
GPIO pin to monitor GPIO pin connected to sensor
Detection trigger type How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Use INPUT_PULLUP mode Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts Minimum time between alert broadcasts
State Broadcast Interval Periodic state broadcast interval
Send bell with alert message Include bell character in alerts
Friendly name Custom name for this sensor

Paxcounter module

People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.

Setting Opis
Paxcounter enabled Activate people counting
Update Interval How often to report counts
WiFi Threshold (dBm) Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm) The same cut-off for BLE advertisements (defaults to −80 dBm)

💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.

Status Message module

The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.

Mesh Beacon module

Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.

TAK module

Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.

Administration

Remote Administration

Remotely configure nodes that share your admin key:

  1. Select the target node in the node list.
  2. Navigate to Settings for that node.
  3. Modify configuration.
  4. Tap Save — changes are sent over the mesh.

⚠️ Important: Requires an admin key configured on both your node and the target node.

Device Actions

Settings → Administration holds five one-shot actions, each behind a confirmation dialog:

Action What it does
Set time Sends your phone’s clock to the node
Ponovno pokreni Restarts the node
Isključi Powers the node down
Vraćanje na tvorničke postavke Returns every setting to its factory default
Resetiraj NodeDB bazu Clears the node database. This dialog carries a Preserve Favorites? switch

⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.

Backup & Restore

Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.

Advanced

Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.

Clean Node Database

Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.

  • Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
  • Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.

The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.

Otklanjanje pogrešaka

Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.

App Settings

The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:

Privacy

  • Allow analytics and crash reporting — opt in or out of diagnostics.
  • Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
  • Homoglyph encoding — how look-alike characters in names are handled.

Appearance

  • Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
  • Theme and Language.
  • Show full message timestamps.

Persistence

  • A cache limit for how much history is kept.
  • Export rangetest packets, Export all packets and Export node database.

On their own

  • Node Layout — how much detail each row of the node list shows.
  • Wi-Fi Provisioning for mPWRD-OS — see Connections.
  • Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
  • System AI — appears only where app functions are available; see App Functions.

A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.

O programu

Settings → About carries the app’s own identity rather than the node’s:

Three sections:

  • What is Meshtastic? — a short description of the project.
  • Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
  • Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.

The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.

Acknowledgements

Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.

Troubleshooting remote admin

  • “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
  • Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
  • Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
diff --git a/main/hr-rHR/user/settings-radio-user.html b/main/hr-rHR/user/settings-radio-user.html index 43d8492f21..c67da75124 100644 --- a/main/hr-rHR/user/settings-radio-user.html +++ b/main/hr-rHR/user/settings-radio-user.html @@ -1 +1 @@ - Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Hrvatski
Meshtastic Docs ↗

🌐 Hrvatski — Community translation View in English

Settings — Radio & User

Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How these screens work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Opis
Long Name Your display name (up to 39 characters)
Short Name 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Unmessageable Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur node (Ham) Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in.

Configuration

Device Config

On Settings → Device configuration → Device.

Setting Opis Zadano
Device Role Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Rebroadcast Mode How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Node Info Broadcast Interval How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Double Tap as Button Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Enabled
LED Heartbeat Blink the status LED periodically Enabled
Time Zone POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it —
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to —

LoRa Config

On Settings → LoRa.

Setting Opis Zadano
Regija Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number Unset (must configure)
Presets Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Transmit Power Transmission power (dBm); 0 = max allowed for region 0 (region max)
Frequency Override Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Use Preset On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead From preset
Coding Rate Manual mode only: 5–8. More redundancy costs airtime From preset
Bandwidth Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Frequency Slot Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmit Enabled Turning this off makes the node receive-only On
Override Duty Cycle Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
Ignore MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok to MQTT Allow your packets to be forwarded to MQTT by gateways Off
RX Boosted Gain Extra receive gain on SX126x radios; costs a little current Off
PA fan disabled Turn off the power-amplifier fan on hardware that has one Off

The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set.

Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Speed SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a modem preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Display Config

On Settings → Device configuration → Display. These control the node’s own screen, not the app’s.

Setting Opis
Screen on for How long the display stays lit before sleeping
Carousel interval How often the node cycles between screens on its own
Display mode Screen layout/density used by the firmware
Display units Metric or Imperial on the node’s screen
Use 12h clock format Show the node’s clock as 12-hour rather than 24-hour
Bold Heading Draw the screen’s heading text in bold
Flip screen Rotate the display 180° for an inverted mounting
OLED type Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED
Wake on tap or motion Light the screen when the node is tapped or moved
Compass orientation Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each
Always point north Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Position Config

On Settings → Device configuration → Position.

Setting Opis
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the node asks its GPS for a fix
Broadcast Interval How often the position is shared with the mesh
Smart Position Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Fixed Position Use a manually entered latitude, longitude and altitude instead of the GPS
Position Flags A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Power Config

On Settings → Device configuration → Power.

Setting Opis
Enable power saving mode Let the node sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the node stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC multiplier override ratio The correction factor itself, used only when the override is on
Battery INA_2XX I2C address Address of an external INA-series power sensor, if fitted

Network Config

On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node.

Setting Opis
Wi-Fi enabled Enable the Wi-Fi node (ESP32 nodes)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Password Network password
Ethernet enabled Use a wired connection on hardware that has one
IPv4 mode DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP server Time synchronization server
rsyslog server Remote logging server

Network Config with a static IPv4 address entered

Postavke Bluetootha

On Settings → Device configuration → Bluetooth, on nodes with Bluetooth.

Setting Opis
Bluetooth enabled Enable/disable BLE radio
Pairing mode Fixed PIN, Random PIN, or No PIN
Fixed PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Security Config

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

Setting Opis
Public Key Your node’s public key (read-only)
Admin Key Keys permitted to administer this node remotely — up to three
Private Key Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it
Regenerate Private Key Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Serial console Serial console over the Stream API
Debug log API enabled Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth
Managed Mode Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.

+ Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Hrvatski
Meshtastic Docs ↗

🌐 Hrvatski — Community translation View in English

Settings — Radio & User

Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How these screens work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Opis
Long Name Your display name (up to 39 characters)
Short Name 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Unmessageable Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur node (Ham) Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in.

Configuration

Device Config

On Settings → Device configuration → Device.

Setting Opis Zadano
Device Role Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Rebroadcast Mode How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Node Info Broadcast Interval How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Double Tap as Button Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Enabled
LED Heartbeat Blink the status LED periodically Enabled
Time Zone POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it —
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to —

LoRa Config

On Settings → LoRa.

Setting Opis Zadano
Regija Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number Unset (must configure)
Presets Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Transmit Power (dBm) Transmission power; 0 = max allowed for region 0 (region max)
Frequency Override Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Use Preset On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead From preset
Coding Rate Manual mode only: 5–8. More redundancy costs airtime From preset
Bandwidth Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Frequency Slot Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmit Enabled Turning this off makes the node receive-only On
Override Duty Cycle Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
Ignore MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok to MQTT Allow your packets to be forwarded to MQTT by gateways Off
RX Boosted Gain Extra receive gain on SX126x radios; costs a little current Off
PA fan disabled Turn off the power-amplifier fan on hardware that has one Off

The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set.

Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Speed SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a modem preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Display Config

On Settings → Device configuration → Display. These control the node’s own screen, not the app’s.

Setting Opis
Screen on for How long the display stays lit before sleeping
Carousel interval How often the node cycles between screens on its own
Display mode Screen layout/density used by the firmware
Display units Metric or Imperial on the node’s screen
Use 12h clock format Show the node’s clock as 12-hour rather than 24-hour
Bold Heading Draw the screen’s heading text in bold
Flip screen Rotate the display 180° for an inverted mounting
OLED type Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED
Wake on tap or motion Light the screen when the node is tapped or moved
Compass orientation Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each
Always point north Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Position Config

On Settings → Device configuration → Position.

Setting Opis
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the node asks its GPS for a fix
Broadcast Interval How often the position is shared with the mesh
Smart Position Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Fixed Position Use a manually entered latitude, longitude and altitude instead of the GPS
Position Flags A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Power Config

On Settings → Device configuration → Power.

Setting Opis
Enable power saving mode Let the node sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the node stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC multiplier override ratio The correction factor itself, used only when the override is on
Battery INA_2XX I2C address Address of an external INA-series power sensor, if fitted

Network Config

On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node.

Setting Opis
Wi-Fi enabled Enable the Wi-Fi node (ESP32 nodes)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Password Network password
Ethernet enabled Use a wired connection on hardware that has one
IPv4 mode DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP server Time synchronization server
rsyslog server Remote logging server

Network Config with a static IPv4 address entered

Postavke Bluetootha

On Settings → Device configuration → Bluetooth, on nodes with Bluetooth.

Setting Opis
Bluetooth enabled Enable/disable BLE radio
Pairing mode Fixed PIN, Random PIN, or No PIN
Fixed PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Security Config

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

Setting Opis
Public Key Your node’s public key (read-only)
Admin Key Keys permitted to administer this node remotely — up to three
Private Key Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it
Regenerate Private Key Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Serial console Serial console over the Stream API
Debug log API enabled Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth
Managed Mode Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.

diff --git a/main/ht-rHT/user/discovery.html b/main/ht-rHT/user/discovery.html index 6a65343d3d..ad3867624d 100644 --- a/main/ht-rHT/user/discovery.html +++ b/main/ht-rHT/user/discovery.html @@ -5,4 +5,4 @@ ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) -

Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:.

What to look for What it means
All hops show Good SNR (green) Healthy path — messages flow reliably
One hop shows a poor SNR (orange or red) Weak link — this relay segment is fragile
Many hops (4+) Long path — consider repositioning a node to shorten it
Different path on retry Mesh is adapting — multiple routes exist (this is good!)

💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network.

Troubleshooting with Traceroute

  • No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key.
  • Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa.
  • Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position.
  • Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric.

Neighbor Info

The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh.

Enabling Neighbor Info

  1. Navigate to Settings → Module configuration → Neighbor Info.
  2. Enable the module.
  3. Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
  4. Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air.

Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.

Viewing neighbor data

  • Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors.
  • Each neighbor entry shows the node that was directly heard and its signal quality.
  • Combine neighbor data from multiple nodes to understand the full mesh topology.

ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further.

Node list as a discovery tool

The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively.

Finding new nodes

  • Sort by Last heard to see the most recently active nodes at the top.
  • Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes.

Assessing connectivity

  • Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed.
  • Sort by Distance to find nearby nodes and verify they’re reachable.
  • Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge).

Infrastructure audit

  • Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes.
  • Check their signal quality and last-heard times to verify your infrastructure nodes are healthy.

See Nodes for full details on filtering and sorting options.

Tips for Mesh exploration

  • Start with traceroute — it gives you immediate, actionable information about a specific path.
  • Enable Neighbor Info on key nodes — especially routers and repeaters, to build a picture of the backbone.
  • Check the map — node positions on the Map combined with signal data help you understand why some links are strong and others are weak.
  • Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly.
+

Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:.

What to look for What it means
All hops show Good SNR (green) Healthy path — messages flow reliably
One hop shows a poor SNR (orange or red) Weak link — this relay segment is fragile
Many hops (4+) Long path — consider repositioning a node to shorten it
Different path on retry Mesh is adapting — multiple routes exist (this is good!)

💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network.

Troubleshooting with Traceroute

  • No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key.
  • Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa.
  • Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position.
  • Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric.

Neighbor Info

The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh.

Enabling Neighbor Info

  1. Navigate to Settings → Module configuration → Neighbor Info.
  2. Enable the module.
  3. Set Update Interval. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
  4. Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air.

Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.

Viewing neighbor data

  • Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors.
  • Each neighbor entry shows the node that was directly heard and its signal quality.
  • Combine neighbor data from multiple nodes to understand the full mesh topology.

ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further.

Node list as a discovery tool

The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively.

Finding new nodes

  • Sort by Last heard to see the most recently active nodes at the top.
  • Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes.

Assessing connectivity

  • Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed.
  • Sort by Distance to find nearby nodes and verify they’re reachable.
  • Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge).

Infrastructure audit

  • Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes.
  • Check their signal quality and last-heard times to verify your infrastructure nodes are healthy.

See Nodes for full details on filtering and sorting options.

Tips for Mesh exploration

  • Start with traceroute — it gives you immediate, actionable information about a specific path.
  • Enable Neighbor Info on key nodes — especially routers and repeaters, to build a picture of the backbone.
  • Check the map — node positions on the Map combined with signal data help you understand why some links are strong and others are weak.
  • Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly.
diff --git a/main/ht-rHT/user/mqtt.html b/main/ht-rHT/user/mqtt.html index ab60a260fc..177264871a 100644 --- a/main/ht-rHT/user/mqtt.html +++ b/main/ht-rHT/user/mqtt.html @@ -1,2 +1,2 @@ MQTT | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Kreyòl Ayisyen
Meshtastic Docs ↗

🌐 Kreyòl Ayisyen — Community translation View in English

MQTT

MQTT bridges your Meshtastic mesh network to the internet, enabling long-range communication beyond radio range.

Overview

The MQTT module connects your node to an MQTT broker, allowing:

  • Messages to reach nodes on different physical meshes via the internet
  • Integration with home automation and monitoring systems
  • Publishing node positions to the public Meshtastic map
  • Custom data pipelines for logging and alerting

How It Works 

[Your Node] → Radio → [Gateway Node with Wi-Fi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node]
-

A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh.

Configuration

Enabling MQTT

  1. Navigate to Settings → Module configuration → MQTT.
  2. Enable the MQTT module.
  3. Configure the broker connection:
Setting Deskripsyon Default
Address MQTT broker hostname mqtt.meshtastic.org
Username Broker authentication meshdev
Password Broker authentication large4cats
Root topic Base topic for messages msh, which the radio rewrites to msh/<REGION> once you set a region
Encryption enabled Encrypt MQTT payload Enabled
JSON output enabled Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it Disabled
TLS enabled Secure connection to broker Disabled
Map reporting Report position to public map Disabled
Proxy to client enabled Relay MQTT through the connected phone Disabled

Connection Status and Test Connection

The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here.

Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason.

MQTT Proxy on This Phone

If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection.

ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them.

The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration.

Default Meshtastic Broker

The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing.

When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without).

🔒 Privacy: Messages on the public broker are readable by anyone subscribed. Always use channel encryption for private communications.

Private Broker

For better privacy and control, you can run your own MQTT broker:

  • Mosquitto (lightweight, open-source)
  • HiveMQ
  • EMQX

Configure your node to point to your private broker with appropriate credentials.

Map Reporting

When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.

Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.

Reports appear at meshmap.net and similar community map services.

🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published.

Direction Deskripsyon
Uplink Messages from mesh → MQTT broker
Downlink Messages from MQTT broker → mesh

Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on.

Message Formats

MQTT carries two payload formats:

Format Deskripsyon Use case
Protobuf Binary Meshtastic protobuf encoding Node-to-node mesh bridging
JSON Human-readable JSON on the /2/json/ topic Consumers outside the mesh (dashboards, home automation)

ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads.

Encryption & Privacy

Understanding the layered encryption model:

  1. Channel encryption happens on the mesh before MQTT. If your channel has a PSK, the MQTT payload is already encrypted — the broker and any subscribers see only the ciphertext.
  2. Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard.
  3. TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping.

🔒 Security: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications.

Best Practices

  • Use channel-level encryption (PSK) on channels that bridge to MQTT
  • Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes memory)
  • Use a private broker for sensitive deployments
  • Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh
  • Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back

Troubleshooting

MQTT Not Connecting

  • Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself.
  • Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces.
  • Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443).
  • DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly.

Messages Not Bridging

  • Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway.
  • Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage.
  • Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root.
  • Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway.
  • Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in.
+

A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh.

Configuration

Enabling MQTT

  1. Navigate to Settings → Module configuration → MQTT.
  2. Enable the MQTT module.
  3. Configure the broker connection:
Setting Deskripsyon Default
Address MQTT broker hostname mqtt.meshtastic.org
Username Broker authentication meshdev
Password Broker authentication large4cats
Root topic Base topic for messages msh, which the radio rewrites to msh/<REGION> once you set a region
Encryption enabled Encrypt MQTT payload Enabled
JSON output enabled Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it Disabled
TLS enabled Secure connection to broker Disabled
Map reporting Report position to public map Disabled
Proxy to client enabled Relay MQTT through the connected phone Disabled

Connection Status and Test Connection

The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here.

Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason.

MQTT Proxy on This Phone

If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection.

ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them.

The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration.

Default Meshtastic Broker

The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing.

When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without).

🔒 Privacy: Messages on the public broker are readable by anyone subscribed. Always use channel encryption for private communications.

Private Broker

For better privacy and control, you can run your own MQTT broker:

  • Mosquitto (lightweight, open-source)
  • HiveMQ
  • EMQX

Configure your node to point to your private broker with appropriate credentials.

Map Reporting

When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.

Turning it on opens a consent card. Turn on I agree. and choose a Map Publish Interval of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.

Reports appear at meshmap.net and similar community map services.

🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published.

Direction Deskripsyon
Uplink Messages from mesh → MQTT broker
Downlink Messages from MQTT broker → mesh

Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on.

Message Formats

MQTT carries two payload formats:

Format Deskripsyon Use case
Protobuf Binary Meshtastic protobuf encoding Node-to-node mesh bridging
JSON Human-readable JSON on the /2/json/ topic Consumers outside the mesh (dashboards, home automation)

ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads.

Encryption & Privacy

Understanding the layered encryption model:

  1. Channel encryption happens on the mesh before MQTT. If your channel has a PSK, the MQTT payload is already encrypted — the broker and any subscribers see only the ciphertext.
  2. Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard.
  3. TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping.

🔒 Security: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications.

Best Practices

  • Use channel-level encryption (PSK) on channels that bridge to MQTT
  • Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes memory)
  • Use a private broker for sensitive deployments
  • Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh
  • Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back

Troubleshooting

MQTT Not Connecting

  • Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself.
  • Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces.
  • Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443).
  • DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly.

Messages Not Bridging

  • Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway.
  • Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage.
  • Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root.
  • Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway.
  • Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in.
diff --git a/main/ht-rHT/user/settings-module-admin.html b/main/ht-rHT/user/settings-module-admin.html index 3eb9ac5adc..982ea749f2 100644 --- a/main/ht-rHT/user/settings-module-admin.html +++ b/main/ht-rHT/user/settings-module-admin.html @@ -1 +1 @@ - Settings — Modules & Admin | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Kreyòl Ayisyen
Meshtastic Docs ↗

🌐 Kreyòl Ayisyen — Community translation View in English

Settings — Modules & Admin

Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.

💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.

Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:

A toggle setting in the on position

A dropdown setting, expanded to show its list of options

A text field setting with a value entered

A module settings card with its title and grouped controls

Konfigirasyon modil

Every module lives under Settings → Module configuration.

⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes.

MQTT module

Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.

Setting Deskripsyon
MQTT enabled Toggle MQTT bridge
Address MQTT broker address
Username Authentication username
Password Authentication password
Encryption enabled Encrypt MQTT payloads
JSON output enabled Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS enabled Use secure connection
Root topic Base MQTT topic path
Proxy to client enabled Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy on this phone The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT
Map reporting Publish position to the public map — see the Map reporting group that follows

Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:

Setting Deskripsyon
I agree. Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map reporting interval (seconds) How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered

See MQTT for a detailed usage guide including encryption, privacy, and broker setup.

Serial module

Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.

Setting Deskripsyon
Serial enabled Activate serial communication
Echo enabled Echo received serial data back
Serial mode Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX GPIO pins for the serial connection
Serial baud rate Port speed
Tan pase How long to wait before considering an incoming message complete
Override console serial port Take over the port the debug console normally uses

External Notification module

Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.

There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.

Setting Deskripsyon
External notification enabled Master toggle for the module
Alert message LED / buzzer / vibra Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra Which outputs fire on a received bell character
Output LED (GPIO) Pin the LED is wired to
Output LED active high Whether the LED pin is active high or low
Output buzzer (GPIO) Pin the buzzer is wired to
Output vibra (GPIO) Pin the vibration motor is wired to
Use PWM buzzer Drive the buzzer with PWM, which allows tones rather than a single pitch
Use I2S as buzzer Send the alert through an I2S audio output instead
Output duration (milliseconds) How long a single alert lasts
Nag timeout (seconds) Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Ringtone The tone played on a PWM buzzer, in RTTTL. Can be imported from a file

Store & Forward module

Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.

Setting Deskripsyon
Store & Forward enabled Activate store and forward
Heartbeat Periodically announce this node’s store-and-forward capability
Number of records Maximum stored messages
History return max Max messages to replay
History return window Time window for replay
Server Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)

💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.

Range Test module

⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.

Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.

Setting Deskripsyon
Range test enabled Activate range testing
Sender message interval (seconds) Time between test transmissions, chosen from a dropdown of fixed intervals
Save .CSV in storage (ESP32 only) Log received test data to the node’s own filesystem. ESP32 hardware only

Telemetry module

Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).

Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.

Setting Deskripsyon
Send Device Telemetry Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval How often to report battery, uptime and channel utilization
Environment metrics module enabled Report the attached environment sensors
Environment metrics update interval How often to report them
Environment metrics on-screen enabled Also show these readings on the device’s own display
Environment metrics use Fahrenheit Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Air quality metrics module enabled Report particulate and CO₂ sensor data
Air quality metrics update interval How often to report them
Power metrics module enabled Report the per-channel voltage and current readings
Power metrics update interval How often to report them
Power metrics on-screen enabled Also show power readings on the device’s display

See Telemetry & Sensors for supported sensors and configuration recommendations.

Canned Message module

Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.

Setting Deskripsyon
Canned message enabled ⚠️ Deprecated in the protobuf schema
Messages Newline-separated list of messages
Send bell Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Rotary encoder #1 enabled Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port The three pins the encoder is wired to
Generate input event on Press / CW / CCW Which key event each encoder action produces
Up/Down/Select input enabled A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source ⚠️ Deprecated in the protobuf schema

Audio module

Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.

Setting Deskripsyon
CODEC 2 enabled Activate audio module
CODEC2 sample rate Audio quality/bandwidth tradeoff
PTT pin GPIO pin for the push-to-talk button
I2S word select GPIO pin for I2S WS
I2S data in GPIO pin for I2S DIN
I2S data out GPIO pin for I2S DOUT
I2S clock GPIO pin for the I2S bit clock

ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.

Remote Hardware module

GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.

⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.

Setting Deskripsyon
Remote Hardware enabled Activate remote GPIO access
Allow undefined pin access Allow access to any GPIO pin (security risk)
Available pins Up to 4 GPIO pins this node exposes for remote read/write

Neighbor Info module

Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.

Setting Deskripsyon
Neighbor Info enabled Activate neighbor broadcasting
Update interval (seconds) How often to broadcast neighbor list
Transmit over LoRa Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name

See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.

Ambient Lighting module

Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.

Setting Deskripsyon
LED state Turn the LED on or off
Current LED current limit (0–31)
Red / Green / Blue Individual color channel values (0–255)

Detection Sensor module

Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.

Setting Deskripsyon
Detection Sensor enabled Activate detection sensor
GPIO pin to monitor GPIO pin connected to sensor
Detection trigger type How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Use INPUT_PULLUP mode Enable the pin’s internal pull-up resistor
Minimum broadcast (seconds) Minimum time between alert broadcasts
State broadcast (seconds) Periodic state broadcast interval
Send bell with alert message Include bell character in alerts
Friendly name Custom name for this sensor

Paxcounter module

People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.

Setting Deskripsyon
Paxcounter enabled Activate people counting
Update interval (seconds) How often to report counts
Wi-Fi RSSI threshold Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE RSSI threshold The same cut-off for BLE advertisements (defaults to −80 dBm)

💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.

Status Message module

The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.

Mesh Beacon module

Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.

TAK module

Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.

Administrasyon

Administrasyon Remote

Remotely configure nodes that share your admin key:

  1. Select the target node in the node list.
  2. Navigate to Settings for that node.
  3. Modify configuration.
  4. Tap Save — changes are sent over the mesh.

⚠️ Important: Requires an admin key configured on both your node and the target node.

Device Actions

Settings → Administration holds five one-shot actions, each behind a confirmation dialog:

Action What it does
Set time Sends your phone’s clock to the node
Rekòmanse Restarts the node
Fèmen Powers the node down
Reyajiste nan faktori Returns every setting to its factory default
Reyajiste NodeDB Clears the node database. This dialog carries a Preserve Favorites? switch

⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.

Backup & Restore

Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.

Advanced

Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.

Clean Node Database

Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.

  • Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
  • Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.

The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.

Panno Debug

Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.

App Settings

The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:

Privacy

  • Allow analytics and crash reporting — opt in or out of diagnostics.
  • Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
  • Homoglyph encoding — how look-alike characters in names are handled.

Appearance

  • Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
  • Theme and Language.
  • Show full message timestamps.

Persistence

  • A cache limit for how much history is kept.
  • Export rangetest packets, Export all packets and Export node database.

On their own

  • Node Layout — how much detail each row of the node list shows.
  • Wi-Fi Provisioning for mPWRD-OS — see Connections.
  • Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
  • System AI — appears only where app functions are available; see App Functions.

A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.

Sou

Settings → About carries the app’s own identity rather than the node’s:

Three sections:

  • What is Meshtastic? — a short description of the project.
  • Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
  • Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.

The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.

Acknowledgements

Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.

Troubleshooting remote admin

  • “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
  • Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
  • Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
+ Settings — Modules & Admin | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Kreyòl Ayisyen
Meshtastic Docs ↗

🌐 Kreyòl Ayisyen — Community translation View in English

Settings — Modules & Admin

Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.

💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.

Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:

A toggle setting in the on position

A dropdown setting, expanded to show its list of options

A text field setting with a value entered

A module settings card with its title and grouped controls

Konfigirasyon modil

Every module lives under Settings → Module configuration.

⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes.

MQTT module

Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.

Setting Deskripsyon
MQTT enabled Toggle MQTT bridge
Address MQTT broker address
Username Authentication username
Password Authentication password
Encryption enabled Encrypt MQTT payloads
JSON output enabled Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS enabled Use secure connection
Root topic Base MQTT topic path
Proxy to client enabled Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy on this phone The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT
Map reporting Publish position to the public map — see the Map reporting group that follows

Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:

Setting Deskripsyon
I agree. Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered

See MQTT for a detailed usage guide including encryption, privacy, and broker setup.

Serial module

Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.

Setting Deskripsyon
Serial enabled Activate serial communication
Echo enabled Echo received serial data back
Serial mode Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX GPIO pins for the serial connection
Serial baud rate Port speed
Tan pase How long to wait before considering an incoming message complete
Override console serial port Take over the port the debug console normally uses

External Notification module

Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.

There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.

Setting Deskripsyon
External notification enabled Master toggle for the module
Alert message LED / buzzer / vibra Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra Which outputs fire on a received bell character
Output LED (GPIO) Pin the LED is wired to
Output LED active high Whether the LED pin is active high or low
Output buzzer (GPIO) Pin the buzzer is wired to
Output vibra (GPIO) Pin the vibration motor is wired to
Use PWM buzzer Drive the buzzer with PWM, which allows tones rather than a single pitch
Use I2S as buzzer Send the alert through an I2S audio output instead
GPIO Output Duration How long a single alert lasts
Nag Timeout Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Ringtone The tone played on a PWM buzzer, in RTTTL. Can be imported from a file

Store & Forward module

Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.

Setting Deskripsyon
Store & Forward enabled Activate store and forward
Heartbeat Periodically announce this node’s store-and-forward capability
Number of records Maximum stored messages
History return max Max messages to replay
History return window Time window for replay
Server Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)

💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.

Range Test module

⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.

Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.

Setting Deskripsyon
Range test enabled Activate range testing
Sender Interval Time between test transmissions, chosen from a dropdown of fixed intervals
Save .CSV in storage (ESP32 only) Log received test data to the node’s own filesystem. ESP32 hardware only

Telemetry module

Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).

Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.

Setting Deskripsyon
Send Device Telemetry Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval How often to report battery, uptime and channel utilization
Environment metrics module enabled Report the attached environment sensors
Environment metrics update interval How often to report them
Environment metrics on-screen enabled Also show these readings on the device’s own display
Environment metrics use Fahrenheit Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Air quality metrics module enabled Report particulate and CO₂ sensor data
Air quality metrics update interval How often to report them
Power metrics module enabled Report the per-channel voltage and current readings
Power metrics update interval How often to report them
Power metrics on-screen enabled Also show power readings on the device’s display

See Telemetry & Sensors for supported sensors and configuration recommendations.

Canned Message module

Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.

Setting Deskripsyon
Canned message enabled ⚠️ Deprecated in the protobuf schema
Messages Newline-separated list of messages
Send bell Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Rotary encoder #1 enabled Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port The three pins the encoder is wired to
Generate input event on Press / CW / CCW Which key event each encoder action produces
Up/Down/Select input enabled A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source ⚠️ Deprecated in the protobuf schema

Audio module

Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.

Setting Deskripsyon
CODEC 2 enabled Activate audio module
CODEC2 sample rate Audio quality/bandwidth tradeoff
PTT pin GPIO pin for the push-to-talk button
I2S word select GPIO pin for I2S WS
I2S data in GPIO pin for I2S DIN
I2S data out GPIO pin for I2S DOUT
I2S clock GPIO pin for the I2S bit clock

ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.

Remote Hardware module

GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.

⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.

Setting Deskripsyon
Remote Hardware enabled Activate remote GPIO access
Allow undefined pin access Allow access to any GPIO pin (security risk)
Available pins Up to 4 GPIO pins this node exposes for remote read/write

Neighbor Info module

Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.

Setting Deskripsyon
Neighbor Info enabled Activate neighbor broadcasting
Update Interval How often to broadcast neighbor list
Transmit over LoRa Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name

See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.

Ambient Lighting module

Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.

Setting Deskripsyon
LED state Turn the LED on or off
Current LED current limit (0–31)
Red / Green / Blue Individual color channel values (0–255)

Detection Sensor module

Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.

Setting Deskripsyon
Detection Sensor enabled Activate detection sensor
GPIO pin to monitor GPIO pin connected to sensor
Detection trigger type How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Use INPUT_PULLUP mode Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts Minimum time between alert broadcasts
State Broadcast Interval Periodic state broadcast interval
Send bell with alert message Include bell character in alerts
Friendly name Custom name for this sensor

Paxcounter module

People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.

Setting Deskripsyon
Paxcounter enabled Activate people counting
Update Interval How often to report counts
WiFi Threshold (dBm) Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm) The same cut-off for BLE advertisements (defaults to −80 dBm)

💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.

Status Message module

The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.

Mesh Beacon module

Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.

TAK module

Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.

Administrasyon

Administrasyon Remote

Remotely configure nodes that share your admin key:

  1. Select the target node in the node list.
  2. Navigate to Settings for that node.
  3. Modify configuration.
  4. Tap Save — changes are sent over the mesh.

⚠️ Important: Requires an admin key configured on both your node and the target node.

Device Actions

Settings → Administration holds five one-shot actions, each behind a confirmation dialog:

Action What it does
Set time Sends your phone’s clock to the node
Rekòmanse Restarts the node
Fèmen Powers the node down
Reyajiste nan faktori Returns every setting to its factory default
Reyajiste NodeDB Clears the node database. This dialog carries a Preserve Favorites? switch

⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.

Backup & Restore

Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.

Advanced

Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.

Clean Node Database

Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.

  • Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
  • Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.

The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.

Panno Debug

Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.

App Settings

The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:

Privacy

  • Allow analytics and crash reporting — opt in or out of diagnostics.
  • Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
  • Homoglyph encoding — how look-alike characters in names are handled.

Appearance

  • Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
  • Theme and Language.
  • Show full message timestamps.

Persistence

  • A cache limit for how much history is kept.
  • Export rangetest packets, Export all packets and Export node database.

On their own

  • Node Layout — how much detail each row of the node list shows.
  • Wi-Fi Provisioning for mPWRD-OS — see Connections.
  • Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
  • System AI — appears only where app functions are available; see App Functions.

A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.

Sou

Settings → About carries the app’s own identity rather than the node’s:

Three sections:

  • What is Meshtastic? — a short description of the project.
  • Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
  • Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.

The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.

Acknowledgements

Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.

Troubleshooting remote admin

  • “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
  • Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
  • Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
diff --git a/main/ht-rHT/user/settings-radio-user.html b/main/ht-rHT/user/settings-radio-user.html index 435d14b3be..97f7c80888 100644 --- a/main/ht-rHT/user/settings-radio-user.html +++ b/main/ht-rHT/user/settings-radio-user.html @@ -1 +1 @@ - Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Kreyòl Ayisyen
Meshtastic Docs ↗

🌐 Kreyòl Ayisyen — Community translation View in English

Settings — Radio & User

Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How these screens work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Deskripsyon
Long Name Your display name (up to 39 characters)
Short Name 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Unmessageable Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur node (Ham) Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in.

Configuration

Device Config

On Settings → Device configuration → Device.

Setting Deskripsyon Default
Device Role Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Rebroadcast Mode How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Node Info Broadcast Interval How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Double Tap as Button Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Enabled
LED Heartbeat Blink the status LED periodically Enabled
Time Zone POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it —
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to —

LoRa Config

On Settings → LoRa.

Setting Deskripsyon Default
Rejyon Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number Unset (must configure)
Presets Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Transmit Power Transmission power (dBm); 0 = max allowed for region 0 (region max)
Frequency Override Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Use Preset On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead From preset
Coding Rate Manual mode only: 5–8. More redundancy costs airtime From preset
Bandwidth Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Frequency Slot Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmit Enabled Turning this off makes the node receive-only On
Override Duty Cycle Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
Ignore MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok to MQTT Allow your packets to be forwarded to MQTT by gateways Off
RX Boosted Gain Extra receive gain on SX126x radios; costs a little current Off
PA fan disabled Turn off the power-amplifier fan on hardware that has one Off

The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set.

Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Speed SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a modem preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Display Config

On Settings → Device configuration → Display. These control the node’s own screen, not the app’s.

Setting Deskripsyon
Screen on for How long the display stays lit before sleeping
Carousel interval How often the node cycles between screens on its own
Display mode Screen layout/density used by the firmware
Display units Metric or Imperial on the node’s screen
Use 12h clock format Show the node’s clock as 12-hour rather than 24-hour
Bold Heading Draw the screen’s heading text in bold
Flip screen Rotate the display 180° for an inverted mounting
OLED type Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED
Wake on tap or motion Light the screen when the node is tapped or moved
Compass orientation Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each
Always point north Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Position Config

On Settings → Device configuration → Position.

Setting Deskripsyon
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the node asks its GPS for a fix
Broadcast Interval How often the position is shared with the mesh
Smart Position Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Fixed Position Use a manually entered latitude, longitude and altitude instead of the GPS
Position Flags A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Power Config

On Settings → Device configuration → Power.

Setting Deskripsyon
Enable power saving mode Let the node sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the node stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC multiplier override ratio The correction factor itself, used only when the override is on
Battery INA_2XX I2C address Address of an external INA-series power sensor, if fitted

Network Config

On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node.

Setting Deskripsyon
Wi-Fi enabled Enable the Wi-Fi node (ESP32 nodes)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Password Network password
Ethernet enabled Use a wired connection on hardware that has one
IPv4 mode DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP server Time synchronization server
rsyslog server Remote logging server

Network Config with a static IPv4 address entered

Bluetooth Config

On Settings → Device configuration → Bluetooth, on nodes with Bluetooth.

Setting Deskripsyon
Bluetooth enabled Enable/disable BLE radio
Pairing mode Fixed PIN, Random PIN, or No PIN
Fixed PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Security Config

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

Setting Deskripsyon
Public Key Your node’s public key (read-only)
Admin Key Keys permitted to administer this node remotely — up to three
Private Key Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it
Regenerate Private Key Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Serial console Serial console over the Stream API
Debug log API enabled Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth
Managed Mode Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.

+ Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Kreyòl Ayisyen
Meshtastic Docs ↗

🌐 Kreyòl Ayisyen — Community translation View in English

Settings — Radio & User

Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How these screens work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Deskripsyon
Long Name Your display name (up to 39 characters)
Short Name 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Unmessageable Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur node (Ham) Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in.

Configuration

Device Config

On Settings → Device configuration → Device.

Setting Deskripsyon Default
Device Role Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Rebroadcast Mode How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Node Info Broadcast Interval How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Double Tap as Button Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Enabled
LED Heartbeat Blink the status LED periodically Enabled
Time Zone POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it —
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to —

LoRa Config

On Settings → LoRa.

Setting Deskripsyon Default
Rejyon Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number Unset (must configure)
Presets Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Transmit Power (dBm) Transmission power; 0 = max allowed for region 0 (region max)
Frequency Override Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Use Preset On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead From preset
Coding Rate Manual mode only: 5–8. More redundancy costs airtime From preset
Bandwidth Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Frequency Slot Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmit Enabled Turning this off makes the node receive-only On
Override Duty Cycle Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
Ignore MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok to MQTT Allow your packets to be forwarded to MQTT by gateways Off
RX Boosted Gain Extra receive gain on SX126x radios; costs a little current Off
PA fan disabled Turn off the power-amplifier fan on hardware that has one Off

The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set.

Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Speed SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a modem preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Display Config

On Settings → Device configuration → Display. These control the node’s own screen, not the app’s.

Setting Deskripsyon
Screen on for How long the display stays lit before sleeping
Carousel interval How often the node cycles between screens on its own
Display mode Screen layout/density used by the firmware
Display units Metric or Imperial on the node’s screen
Use 12h clock format Show the node’s clock as 12-hour rather than 24-hour
Bold Heading Draw the screen’s heading text in bold
Flip screen Rotate the display 180° for an inverted mounting
OLED type Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED
Wake on tap or motion Light the screen when the node is tapped or moved
Compass orientation Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each
Always point north Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Position Config

On Settings → Device configuration → Position.

Setting Deskripsyon
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the node asks its GPS for a fix
Broadcast Interval How often the position is shared with the mesh
Smart Position Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Fixed Position Use a manually entered latitude, longitude and altitude instead of the GPS
Position Flags A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Power Config

On Settings → Device configuration → Power.

Setting Deskripsyon
Enable power saving mode Let the node sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the node stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC multiplier override ratio The correction factor itself, used only when the override is on
Battery INA_2XX I2C address Address of an external INA-series power sensor, if fitted

Network Config

On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node.

Setting Deskripsyon
Wi-Fi enabled Enable the Wi-Fi node (ESP32 nodes)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Password Network password
Ethernet enabled Use a wired connection on hardware that has one
IPv4 mode DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP server Time synchronization server
rsyslog server Remote logging server

Network Config with a static IPv4 address entered

Bluetooth Config

On Settings → Device configuration → Bluetooth, on nodes with Bluetooth.

Setting Deskripsyon
Bluetooth enabled Enable/disable BLE radio
Pairing mode Fixed PIN, Random PIN, or No PIN
Fixed PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Security Config

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

Setting Deskripsyon
Public Key Your node’s public key (read-only)
Admin Key Keys permitted to administer this node remotely — up to three
Private Key Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it
Regenerate Private Key Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Serial console Serial console over the Stream API
Debug log API enabled Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth
Managed Mode Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.

diff --git a/main/hu-rHU/user/discovery.html b/main/hu-rHU/user/discovery.html index 9135fb67aa..8f869523b3 100644 --- a/main/hu-rHU/user/discovery.html +++ b/main/hu-rHU/user/discovery.html @@ -5,4 +5,4 @@ ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) -

Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:.

What to look for What it means
All hops show Good SNR (green) Healthy path — messages flow reliably
One hop shows a poor SNR (orange or red) Weak link — this relay segment is fragile
Many hops (4+) Long path — consider repositioning a node to shorten it
Different path on retry Mesh is adapting — multiple routes exist (this is good!)

💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network.

Troubleshooting with Traceroute

  • No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key.
  • Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa.
  • Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position.
  • Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric.

Szomszéd-információ

The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh.

Enabling Neighbor Info

  1. Navigate to Settings → Module configuration → Neighbor Info.
  2. Enable the module.
  3. Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
  4. Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air.

Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.

Viewing neighbor data

  • Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors.
  • Each neighbor entry shows the node that was directly heard and its signal quality.
  • Combine neighbor data from multiple nodes to understand the full mesh topology.

ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further.

Node list as a discovery tool

The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively.

Finding new nodes

  • Sort by Last heard to see the most recently active nodes at the top.
  • Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes.

Assessing connectivity

  • Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed.
  • Sort by Distance to find nearby nodes and verify they’re reachable.
  • Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge).

Infrastructure audit

  • Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes.
  • Check their signal quality and last-heard times to verify your infrastructure nodes are healthy.

See Nodes for full details on filtering and sorting options.

Tips for Mesh exploration

  • Start with traceroute — it gives you immediate, actionable information about a specific path.
  • Enable Neighbor Info on key nodes — especially routers and repeaters, to build a picture of the backbone.
  • Check the map — node positions on the Map combined with signal data help you understand why some links are strong and others are weak.
  • Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly.
+

Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:.

What to look for What it means
All hops show Good SNR (green) Healthy path — messages flow reliably
One hop shows a poor SNR (orange or red) Weak link — this relay segment is fragile
Many hops (4+) Long path — consider repositioning a node to shorten it
Different path on retry Mesh is adapting — multiple routes exist (this is good!)

💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network.

Troubleshooting with Traceroute

  • No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key.
  • Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa.
  • Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position.
  • Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric.

Szomszéd-információ

The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh.

Enabling Neighbor Info

  1. Navigate to Settings → Module configuration → Neighbor Info.
  2. Enable the module.
  3. Set Update Interval. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
  4. Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air.

Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.

Viewing neighbor data

  • Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors.
  • Each neighbor entry shows the node that was directly heard and its signal quality.
  • Combine neighbor data from multiple nodes to understand the full mesh topology.

ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further.

Node list as a discovery tool

The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively.

Finding new nodes

  • Sort by Last heard to see the most recently active nodes at the top.
  • Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes.

Assessing connectivity

  • Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed.
  • Sort by Distance to find nearby nodes and verify they’re reachable.
  • Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge).

Infrastructure audit

  • Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes.
  • Check their signal quality and last-heard times to verify your infrastructure nodes are healthy.

See Nodes for full details on filtering and sorting options.

Tips for Mesh exploration

  • Start with traceroute — it gives you immediate, actionable information about a specific path.
  • Enable Neighbor Info on key nodes — especially routers and repeaters, to build a picture of the backbone.
  • Check the map — node positions on the Map combined with signal data help you understand why some links are strong and others are weak.
  • Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly.
diff --git a/main/hu-rHU/user/mqtt.html b/main/hu-rHU/user/mqtt.html index ce78da3e19..25472b7eeb 100644 --- a/main/hu-rHU/user/mqtt.html +++ b/main/hu-rHU/user/mqtt.html @@ -1,2 +1,2 @@ MQTT | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Magyar
Meshtastic Docs ↗

🌐 Magyar — Community translation View in English

MQTT

MQTT bridges your Meshtastic mesh network to the internet, enabling long-range communication beyond radio range.

Overview

The MQTT module connects your node to an MQTT broker, allowing:

  • Messages to reach nodes on different physical meshes via the internet
  • Integration with home automation and monitoring systems
  • Publishing node positions to the public Meshtastic map
  • Custom data pipelines for logging and alerting

How It Works 

[Your Node] → Radio → [Gateway Node with Wi-Fi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node]
-

A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh.

Configuration

Enabling MQTT

  1. Navigate to Settings → Module configuration → MQTT.
  2. Enable the MQTT module.
  3. Configure the broker connection:
Setting Leírás Alapértelmezett
Address MQTT broker hostname mqtt.meshtastic.org
Username Broker authentication meshdev
Password Broker authentication large4cats
Root topic Base topic for messages msh, which the radio rewrites to msh/<REGION> once you set a region
Encryption enabled Encrypt MQTT payload Engedélyezve
JSON output enabled Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it Disabled
TLS enabled Secure connection to broker Disabled
Map reporting Report position to public map Disabled
Proxy to client enabled Relay MQTT through the connected phone Disabled

Connection Status and Test Connection

The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here.

Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason.

MQTT Proxy on This Phone

If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection.

ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them.

The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration.

Default Meshtastic Broker

The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing.

When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without).

🔒 Privacy: Messages on the public broker are readable by anyone subscribed. Always use channel encryption for private communications.

Private Broker

For better privacy and control, you can run your own MQTT broker:

  • Mosquitto (lightweight, open-source)
  • HiveMQ
  • EMQX

Configure your node to point to your private broker with appropriate credentials.

Map Reporting

When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.

Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.

Reports appear at meshmap.net and similar community map services.

🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published.

Direction Leírás
Uplink Messages from mesh → MQTT broker
Downlink Messages from MQTT broker → mesh

Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on.

Message Formats

MQTT carries two payload formats:

Format Leírás Use case
Protobuf Binary Meshtastic protobuf encoding Node-to-node mesh bridging
JSON Human-readable JSON on the /2/json/ topic Consumers outside the mesh (dashboards, home automation)

ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads.

Encryption & Privacy

Understanding the layered encryption model:

  1. Channel encryption happens on the mesh before MQTT. If your channel has a PSK, the MQTT payload is already encrypted — the broker and any subscribers see only the ciphertext.
  2. Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard.
  3. TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping.

🔒 Security: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications.

Best Practices

  • Use channel-level encryption (PSK) on channels that bridge to MQTT
  • Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes memory)
  • Use a private broker for sensitive deployments
  • Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh
  • Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back

Troubleshooting

MQTT Not Connecting

  • Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself.
  • Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces.
  • Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443).
  • DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly.

Messages Not Bridging

  • Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway.
  • Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage.
  • Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root.
  • Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway.
  • Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in.
+

A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh.

Configuration

Enabling MQTT

  1. Navigate to Settings → Module configuration → MQTT.
  2. Enable the MQTT module.
  3. Configure the broker connection:
Setting Leírás Alapértelmezett
Address MQTT broker hostname mqtt.meshtastic.org
Username Broker authentication meshdev
Password Broker authentication large4cats
Root topic Base topic for messages msh, which the radio rewrites to msh/<REGION> once you set a region
Encryption enabled Encrypt MQTT payload Engedélyezve
JSON output enabled Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it Disabled
TLS enabled Secure connection to broker Disabled
Map reporting Report position to public map Disabled
Proxy to client enabled Relay MQTT through the connected phone Disabled

Connection Status and Test Connection

The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here.

Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason.

MQTT Proxy on This Phone

If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection.

ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them.

The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration.

Default Meshtastic Broker

The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing.

When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without).

🔒 Privacy: Messages on the public broker are readable by anyone subscribed. Always use channel encryption for private communications.

Private Broker

For better privacy and control, you can run your own MQTT broker:

  • Mosquitto (lightweight, open-source)
  • HiveMQ
  • EMQX

Configure your node to point to your private broker with appropriate credentials.

Map Reporting

When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.

Turning it on opens a consent card. Turn on I agree. and choose a Map Publish Interval of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.

Reports appear at meshmap.net and similar community map services.

🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published.

Direction Leírás
Uplink Messages from mesh → MQTT broker
Downlink Messages from MQTT broker → mesh

Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on.

Message Formats

MQTT carries two payload formats:

Format Leírás Use case
Protobuf Binary Meshtastic protobuf encoding Node-to-node mesh bridging
JSON Human-readable JSON on the /2/json/ topic Consumers outside the mesh (dashboards, home automation)

ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads.

Encryption & Privacy

Understanding the layered encryption model:

  1. Channel encryption happens on the mesh before MQTT. If your channel has a PSK, the MQTT payload is already encrypted — the broker and any subscribers see only the ciphertext.
  2. Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard.
  3. TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping.

🔒 Security: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications.

Best Practices

  • Use channel-level encryption (PSK) on channels that bridge to MQTT
  • Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes memory)
  • Use a private broker for sensitive deployments
  • Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh
  • Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back

Troubleshooting

MQTT Not Connecting

  • Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself.
  • Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces.
  • Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443).
  • DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly.

Messages Not Bridging

  • Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway.
  • Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage.
  • Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root.
  • Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway.
  • Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in.
diff --git a/main/hu-rHU/user/settings-module-admin.html b/main/hu-rHU/user/settings-module-admin.html index 6c7fcdbb35..d9541fafc8 100644 --- a/main/hu-rHU/user/settings-module-admin.html +++ b/main/hu-rHU/user/settings-module-admin.html @@ -1 +1 @@ - Settings — Modules & Admin | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Magyar
Meshtastic Docs ↗

🌐 Magyar — Community translation View in English

Settings — Modules & Admin

Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.

💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.

Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:

A toggle setting in the on position

A dropdown setting, expanded to show its list of options

A text field setting with a value entered

A module settings card with its title and grouped controls

Modul beállítások

Every module lives under Settings → Module configuration.

⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes.

MQTT module

Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.

Setting Leírás
MQTT engedélyezve Toggle MQTT bridge
Cím MQTT broker address
Felhasználónév Authentication username
Jelszó Authentication password
Titkosítás engedélyezve Encrypt MQTT payloads
JSON kimenet engedélyezve Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS engedélyezve Use secure connection
Gyökér téma Base MQTT topic path
Proxy kliens felé engedélyezve Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy on this phone The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT
Térképadat-jelentés Publish position to the public map — see the Map reporting group that follows

Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:

Setting Leírás
Elfogadom. Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Térképadat-jelentés intervalluma (másodperc) How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered

See MQTT for a detailed usage guide including encryption, privacy, and broker setup.

Serial module

Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.

Setting Leírás
Soros engedélyezve Activate serial communication
Echo engedélyezve Echo received serial data back
Soros mód Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX GPIO pins for the serial connection
Soros baud ráta Port speed
Időtúllépés How long to wait before considering an incoming message complete
Konzol soros port felülbírálása Take over the port the debug console normally uses

External Notification module

Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.

There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.

Setting Leírás
Külső értesítés engedélyezve Master toggle for the module
Alert message LED / buzzer / vibra Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra Which outputs fire on a received bell character
Kimeneti LED (GPIO) Pin the LED is wired to
Kimeneti LED aktív magas szint Whether the LED pin is active high or low
Kimeneti csipogó (GPIO) Pin the buzzer is wired to
Kimeneti rezgő (GPIO) Pin the vibration motor is wired to
PWM csipogó használata Drive the buzzer with PWM, which allows tones rather than a single pitch
I2S használata csipogóként Send the alert through an I2S audio output instead
Kimeneti időtartam (ezredmásodperc) How long a single alert lasts
Ismétlő riasztás időkorlát (másodperc) Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Csengőhang The tone played on a PWM buzzer, in RTTTL. Can be imported from a file

Store & Forward module

Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.

Setting Leírás
Tárolás és továbbítás engedélyezve Activate store and forward
Heartbeat jel Periodically announce this node’s store-and-forward capability
Rekordok száma Maximum stored messages
Előzmény-visszaadás maximum Max messages to replay
Előzmény-visszaadás időablak Time window for replay
Szerver Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)

💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.

Range Test module

⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.

Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.

Setting Leírás
Hatótáv-teszt engedélyezve Activate range testing
Küldési üzenetintervallum (másodperc) Time between test transmissions, chosen from a dropdown of fixed intervals
.CSV mentése a tárhelyre (csak ESP32) Log received test data to the node’s own filesystem. ESP32 hardware only

Telemetry module

Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).

Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.

Setting Leírás
Eszköztelemetria küldése Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Eszközmetrikák frissítési időköze How often to report battery, uptime and channel utilization
Környezeti metrika modul engedélyezve Report the attached environment sensors
Környezeti metrikák frissítési időköze How often to report them
Környezeti metrikák megjelenítése képernyőn Also show these readings on the device’s own display
Környezeti metrikák Fahrenheit-ben Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Levegőminőség-metrika modul engedélyezve Report particulate and CO₂ sensor data
Levegőminőségi metrikák frissítési időköze How often to report them
Energia-metrika modul engedélyezve Report the per-channel voltage and current readings
Tápellátási metrikák frissítési időköze How often to report them
Energia-metrikák megjelenítése képernyőn engedélyezve Also show power readings on the device’s display

See Telemetry & Sensors for supported sensors and configuration recommendations.

Canned Message module

Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.

Setting Leírás
Canned message enabled ⚠️ Deprecated in the protobuf schema
Üzenetek Newline-separated list of messages
Harangjel küldése Send a bell character alongside the message, so a receiving node’s External Notification module can sound
1. forgóenkóder engedélyezve Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port The three pins the encoder is wired to
Generate input event on Press / CW / CCW Which key event each encoder action produces
Fel/Le/Kiválaszt gomb engedélyezve A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source ⚠️ Deprecated in the protobuf schema

Audio module

Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.

Setting Leírás
CODEC 2 engedélyezve Activate audio module
CODEC2 mintavételi ráta Audio quality/bandwidth tradeoff
PTT pin GPIO pin for the push-to-talk button
I2S szóválasztás GPIO pin for I2S WS
I2S adat be GPIO pin for I2S DIN
I2S adat ki GPIO pin for I2S DOUT
I2S órajel GPIO pin for the I2S bit clock

ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.

Remote Hardware module

GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.

⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.

Setting Leírás
Távoli hardver engedélyezve Activate remote GPIO access
Nem definiált pinek elérésének engedélyezése Allow access to any GPIO pin (security risk)
Elérhető pinek Up to 4 GPIO pins this node exposes for remote read/write

Neighbor Info module

Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.

Setting Leírás
Szomszéd-információ engedélyezve Activate neighbor broadcasting
Frissítési intervallum (másodperc) How often to broadcast neighbor list
Továbbítás LoRa-n keresztül Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name

See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.

Ambient Lighting module

Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.

Setting Leírás
LED állapot Turn the LED on or off
Áramerősség LED current limit (0–31)
Red / Green / Blue Individual color channel values (0–255)

Detection Sensor module

Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.

Setting Leírás
Érzékelő szenzor engedélyezve Activate detection sensor
Figyelt GPIO láb GPIO pin connected to sensor
Érzékelési ravasztípus How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
INPUT_PULLUP mód használata Enable the pin’s internal pull-up resistor
Minimális sugárzási idő (másodperc) Minimum time between alert broadcasts
Állapot-sugárzás (másodperc) Periodic state broadcast interval
Harangjel küldése riasztási üzenettel Include bell character in alerts
Barátságos név Custom name for this sensor

Paxcounter module

People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.

Setting Leírás
Paxcounter engedélyezve Activate people counting
Frissítési intervallum (másodperc) How often to report counts
Wi-Fi RSSI threshold Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE RSSI threshold The same cut-off for BLE advertisements (defaults to −80 dBm)

💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.

Status Message module

The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.

Mesh Beacon module

Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.

TAK module

Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.

Adminisztráció

Távoli Adminisztráció

Remotely configure nodes that share your admin key:

  1. Select the target node in the node list.
  2. Navigate to Settings for that node.
  3. Modify configuration.
  4. Tap Save — changes are sent over the mesh.

⚠️ Important: Requires an admin key configured on both your node and the target node.

Device Actions

Settings → Administration holds five one-shot actions, each behind a confirmation dialog:

Action What it does
Set time Sends your phone’s clock to the node
Újraindítás Restarts the node
Leállítás Powers the node down
Gyári beállítások visszaállítása Returns every setting to its factory default
NodeDB törlése Clears the node database. This dialog carries a Preserve Favorites? switch

⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.

Biztonsági mentés és visszaállítás

Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.

Haladó

Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.

Csomópont-adatbázis tisztítása

Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.

  • Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
  • Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.

The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.

Hibakereső panel

Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.

App Settings

The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:

Privacy

  • Allow analytics and crash reporting — opt in or out of diagnostics.
  • Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
  • Homoglyph encoding — how look-alike characters in names are handled.

Appearance

  • Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
  • Theme and Language.
  • Show full message timestamps.

Persistence

  • A cache limit for how much history is kept.
  • Export rangetest packets, Export all packets and Export node database.

On their own

  • Node Layout — how much detail each row of the node list shows.
  • Wi-Fi Provisioning for mPWRD-OS — see Connections.
  • Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
  • System AI — appears only where app functions are available; see App Functions.

A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.

A programról

Settings → About carries the app’s own identity rather than the node’s:

Three sections:

  • What is Meshtastic? — a short description of the project.
  • Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
  • Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.

The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.

Visszaigazolások (ACK-ek)

Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.

Troubleshooting remote admin

  • “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
  • Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
  • Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
+ Settings — Modules & Admin | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Magyar
Meshtastic Docs ↗

🌐 Magyar — Community translation View in English

Settings — Modules & Admin

Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.

💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.

Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:

A toggle setting in the on position

A dropdown setting, expanded to show its list of options

A text field setting with a value entered

A module settings card with its title and grouped controls

Modul beállítások

Every module lives under Settings → Module configuration.

⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes.

MQTT module

Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.

Setting Leírás
MQTT engedélyezve Toggle MQTT bridge
Cím MQTT broker address
Felhasználónév Authentication username
Jelszó Authentication password
Titkosítás engedélyezve Encrypt MQTT payloads
JSON kimenet engedélyezve Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS engedélyezve Use secure connection
Gyökér téma Base MQTT topic path
Proxy kliens felé engedélyezve Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy on this phone The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT
Térképadat-jelentés Publish position to the public map — see the Map reporting group that follows

Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:

Setting Leírás
Elfogadom. Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered

See MQTT for a detailed usage guide including encryption, privacy, and broker setup.

Serial module

Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.

Setting Leírás
Soros engedélyezve Activate serial communication
Echo engedélyezve Echo received serial data back
Soros mód Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX GPIO pins for the serial connection
Soros baud ráta Port speed
Időtúllépés How long to wait before considering an incoming message complete
Konzol soros port felülbírálása Take over the port the debug console normally uses

External Notification module

Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.

There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.

Setting Leírás
Külső értesítés engedélyezve Master toggle for the module
Alert message LED / buzzer / vibra Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra Which outputs fire on a received bell character
Kimeneti LED (GPIO) Pin the LED is wired to
Kimeneti LED aktív magas szint Whether the LED pin is active high or low
Kimeneti csipogó (GPIO) Pin the buzzer is wired to
Kimeneti rezgő (GPIO) Pin the vibration motor is wired to
PWM csipogó használata Drive the buzzer with PWM, which allows tones rather than a single pitch
I2S használata csipogóként Send the alert through an I2S audio output instead
GPIO Output Duration How long a single alert lasts
Nag Timeout Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Csengőhang The tone played on a PWM buzzer, in RTTTL. Can be imported from a file

Store & Forward module

Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.

Setting Leírás
Tárolás és továbbítás engedélyezve Activate store and forward
Heartbeat jel Periodically announce this node’s store-and-forward capability
Rekordok száma Maximum stored messages
Előzmény-visszaadás maximum Max messages to replay
Előzmény-visszaadás időablak Time window for replay
Szerver Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)

💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.

Range Test module

⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.

Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.

Setting Leírás
Hatótáv-teszt engedélyezve Activate range testing
Sender Interval Time between test transmissions, chosen from a dropdown of fixed intervals
.CSV mentése a tárhelyre (csak ESP32) Log received test data to the node’s own filesystem. ESP32 hardware only

Telemetry module

Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).

Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.

Setting Leírás
Eszköztelemetria küldése Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Eszközmetrikák frissítési időköze How often to report battery, uptime and channel utilization
Környezeti metrika modul engedélyezve Report the attached environment sensors
Környezeti metrikák frissítési időköze How often to report them
Környezeti metrikák megjelenítése képernyőn Also show these readings on the device’s own display
Környezeti metrikák Fahrenheit-ben Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Levegőminőség-metrika modul engedélyezve Report particulate and CO₂ sensor data
Levegőminőségi metrikák frissítési időköze How often to report them
Energia-metrika modul engedélyezve Report the per-channel voltage and current readings
Tápellátási metrikák frissítési időköze How often to report them
Energia-metrikák megjelenítése képernyőn engedélyezve Also show power readings on the device’s display

See Telemetry & Sensors for supported sensors and configuration recommendations.

Canned Message module

Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.

Setting Leírás
Canned message enabled ⚠️ Deprecated in the protobuf schema
Üzenetek Newline-separated list of messages
Harangjel küldése Send a bell character alongside the message, so a receiving node’s External Notification module can sound
1. forgóenkóder engedélyezve Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port The three pins the encoder is wired to
Generate input event on Press / CW / CCW Which key event each encoder action produces
Fel/Le/Kiválaszt gomb engedélyezve A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source ⚠️ Deprecated in the protobuf schema

Audio module

Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.

Setting Leírás
CODEC 2 engedélyezve Activate audio module
CODEC2 mintavételi ráta Audio quality/bandwidth tradeoff
PTT pin GPIO pin for the push-to-talk button
I2S szóválasztás GPIO pin for I2S WS
I2S adat be GPIO pin for I2S DIN
I2S adat ki GPIO pin for I2S DOUT
I2S órajel GPIO pin for the I2S bit clock

ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.

Remote Hardware module

GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.

⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.

Setting Leírás
Távoli hardver engedélyezve Activate remote GPIO access
Nem definiált pinek elérésének engedélyezése Allow access to any GPIO pin (security risk)
Elérhető pinek Up to 4 GPIO pins this node exposes for remote read/write

Neighbor Info module

Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.

Setting Leírás
Szomszéd-információ engedélyezve Activate neighbor broadcasting
Frissítési időköz How often to broadcast neighbor list
Továbbítás LoRa-n keresztül Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name

See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.

Ambient Lighting module

Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.

Setting Leírás
LED állapot Turn the LED on or off
Áramerősség LED current limit (0–31)
Red / Green / Blue Individual color channel values (0–255)

Detection Sensor module

Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.

Setting Leírás
Érzékelő szenzor engedélyezve Activate detection sensor
Figyelt GPIO láb GPIO pin connected to sensor
Érzékelési ravasztípus How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
INPUT_PULLUP mód használata Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts Minimum time between alert broadcasts
State Broadcast Interval Periodic state broadcast interval
Harangjel küldése riasztási üzenettel Include bell character in alerts
Barátságos név Custom name for this sensor

Paxcounter module

People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.

Setting Leírás
Paxcounter engedélyezve Activate people counting
Frissítési időköz How often to report counts
WiFi Threshold (dBm) Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm) The same cut-off for BLE advertisements (defaults to −80 dBm)

💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.

Status Message module

The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.

Mesh Beacon module

Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.

TAK module

Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.

Adminisztráció

Távoli Adminisztráció

Remotely configure nodes that share your admin key:

  1. Select the target node in the node list.
  2. Navigate to Settings for that node.
  3. Modify configuration.
  4. Tap Save — changes are sent over the mesh.

⚠️ Important: Requires an admin key configured on both your node and the target node.

Device Actions

Settings → Administration holds five one-shot actions, each behind a confirmation dialog:

Action What it does
Set time Sends your phone’s clock to the node
Újraindítás Restarts the node
Leállítás Powers the node down
Gyári beállítások visszaállítása Returns every setting to its factory default
NodeDB törlése Clears the node database. This dialog carries a Preserve Favorites? switch

⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.

Biztonsági mentés és visszaállítás

Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.

Haladó

Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.

Csomópont-adatbázis tisztítása

Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.

  • Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
  • Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.

The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.

Hibakereső panel

Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.

App Settings

The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:

Privacy

  • Allow analytics and crash reporting — opt in or out of diagnostics.
  • Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
  • Homoglyph encoding — how look-alike characters in names are handled.

Appearance

  • Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
  • Theme and Language.
  • Show full message timestamps.

Persistence

  • A cache limit for how much history is kept.
  • Export rangetest packets, Export all packets and Export node database.

On their own

  • Node Layout — how much detail each row of the node list shows.
  • Wi-Fi Provisioning for mPWRD-OS — see Connections.
  • Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
  • System AI — appears only where app functions are available; see App Functions.

A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.

A programról

Settings → About carries the app’s own identity rather than the node’s:

Three sections:

  • What is Meshtastic? — a short description of the project.
  • Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
  • Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.

The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.

Visszaigazolások (ACK-ek)

Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.

Troubleshooting remote admin

  • “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
  • Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
  • Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
diff --git a/main/hu-rHU/user/settings-radio-user.html b/main/hu-rHU/user/settings-radio-user.html index 53e2b81f7b..849396d3c3 100644 --- a/main/hu-rHU/user/settings-radio-user.html +++ b/main/hu-rHU/user/settings-radio-user.html @@ -1 +1 @@ - Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Magyar
Meshtastic Docs ↗

🌐 Magyar — Community translation View in English

Settings — Radio & User

Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How these screens work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Leírás
Hosszú név Your display name (up to 39 characters)
Rövid név 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Nem üzenetképes Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur node (Ham) Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in.

Configuration

Eszközbeállítások

On Settings → Device configuration → Device.

Setting Leírás Alapértelmezett
Eszköz szerepköre Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Újrasugárzási mód How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Csomópont-információ sugárzási időköze How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Dupla koppintás mint gomb Treat a double tap as a button press Disabled
Háromszori kattintás – ad hoc ping Send an ad-hoc position ping on a triple click Engedélyezve
LED ütemjelzés Blink the status LED periodically Engedélyezve
Időzóna POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it —
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to —

LoRa beállítások

On Settings → LoRa.

Setting Leírás Alapértelmezett
Régió Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number Unset (must configure)
Előbeállítások Speed/range tradeoff LongFast
Ugrások száma Maximum retransmit hops 3
Adásteljesítmény Transmission power (dBm); 0 = max allowed for region 0 (region max)
Frekvencia felülbírálása Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Előbeállítás használata On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Szórási Faktor Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead From preset
Kódolási ráta Manual mode only: 5–8. More redundancy costs airtime From preset
Sávszélesség Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Frekvencia sáv Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Adás engedélyezve Turning this off makes the node receive-only On
Duty Cycle felülbírálása Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
MQTT figyelmen kívül hagyása Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
MQTT-re továbbítható Allow your packets to be forwarded to MQTT by gateways Off
RX fokozott erősítés Extra receive gain on SX126x radios; costs a little current Off
PA ventilátor letiltva Turn off the power-amplifier fan on hardware that has one Off

The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set.

Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Sebesség SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a modem preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Kijelző beállítások

On Settings → Device configuration → Display. These control the node’s own screen, not the app’s.

Setting Leírás
Kijelző bekapcsolva ennyi ideig How long the display stays lit before sleeping
Karusszel időköz How often the node cycles between screens on its own
Kijelző mód Screen layout/density used by the firmware
Mértékegységek megjelenítése Metric or Imperial on the node’s screen
12 órás időformátum használata Show the node’s clock as 12-hour rather than 24-hour
Félkövér címsor Draw the screen’s heading text in bold
Kijelző megfordítása Rotate the display 180° for an inverted mounting
OLED típus Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED
Érintésre vagy mozgásra ébresztés Light the screen when the node is tapped or moved
Iránytű tájolás Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each
Mindig észak felé mutasson Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Pozíció beállítások

On Settings → Device configuration → Position.

Setting Leírás
GPS mód (fizikai hardver) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the node asks its GPS for a fix
Sugárzási időköz How often the position is shared with the mesh
Intelligens pozíció Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Rögzített pozíció Use a manually entered latitude, longitude and altitude instead of the GPS
Pozíció jelzők (flags) A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Energia-beállítások

On Settings → Device configuration → Power.

Setting Leírás
Energiatakarékos mód engedélyezése Let the node sleep aggressively between activity
Leállítás áramszünet esetén Power the device down after external power disappears
Szuper mélyalvás időtartama How long the deepest sleep state lasts
Minimális ébrenléti idő The shortest time the node stays awake once woken
Bluetooth-várakozás időtartama How long to wait for a phone to connect before sleeping
ADC szorzó felülbírálása Turn on a manual correction for battery-voltage readings
ADC szorzó felülbírálási arány The correction factor itself, used only when the override is on
Akkumulátor INA_2XX I2C-cím Address of an external INA-series power sensor, if fitted

Hálózati beállítások

On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node.

Setting Leírás
Wi-Fi enabled Enable the Wi-Fi node (ESP32 nodes)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Jelszó Network password
Ethernet engedélyezve Use a wired connection on hardware that has one
IPv4 mód DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP szerver Time synchronization server
rsyslog szerver Remote logging server

Network Config with a static IPv4 address entered

Bluetooth beállítások

On Settings → Device configuration → Bluetooth, on nodes with Bluetooth.

Setting Leírás
Bluetooth engedélyezve Enable/disable BLE radio
Párosítási mód Fixed PIN, Random PIN, or No PIN
Rögzített PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Biztonsági beállítások

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

Setting Leírás
Nyilvános kulcs Your node’s public key (read-only)
Admin kulcs Keys permitted to administer this node remotely — up to three
Privát kulcs Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it
Privát kulcs újragenerálása Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Soros konzol Serial console over the Stream API
Hibakeresési napló API engedélyezve Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth
Felügyelt mód Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.

+ Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Magyar
Meshtastic Docs ↗

🌐 Magyar — Community translation View in English

Settings — Radio & User

Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How these screens work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Leírás
Hosszú név Your display name (up to 39 characters)
Rövid név 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Nem üzenetképes Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur node (Ham) Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in.

Configuration

Eszközbeállítások

On Settings → Device configuration → Device.

Setting Leírás Alapértelmezett
Eszköz szerepköre Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Újrasugárzási mód How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Csomópont-információ sugárzási időköze How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Dupla koppintás mint gomb Treat a double tap as a button press Disabled
Háromszori kattintás – ad hoc ping Send an ad-hoc position ping on a triple click Engedélyezve
LED ütemjelzés Blink the status LED periodically Engedélyezve
Időzóna POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it —
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to —

LoRa beállítások

On Settings → LoRa.

Setting Leírás Alapértelmezett
Régió Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number Unset (must configure)
Előbeállítások Speed/range tradeoff LongFast
Ugrások száma Maximum retransmit hops 3
Transmit Power (dBm) Transmission power; 0 = max allowed for region 0 (region max)
Frekvencia felülbírálása Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Előbeállítás használata On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Szórási Faktor Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead From preset
Kódolási ráta Manual mode only: 5–8. More redundancy costs airtime From preset
Sávszélesség Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Frekvencia sáv Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Adás engedélyezve Turning this off makes the node receive-only On
Duty Cycle felülbírálása Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
MQTT figyelmen kívül hagyása Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
MQTT-re továbbítható Allow your packets to be forwarded to MQTT by gateways Off
RX fokozott erősítés Extra receive gain on SX126x radios; costs a little current Off
PA ventilátor letiltva Turn off the power-amplifier fan on hardware that has one Off

The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set.

Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Sebesség SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a modem preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Kijelző beállítások

On Settings → Device configuration → Display. These control the node’s own screen, not the app’s.

Setting Leírás
Kijelző bekapcsolva ennyi ideig How long the display stays lit before sleeping
Karusszel időköz How often the node cycles between screens on its own
Kijelző mód Screen layout/density used by the firmware
Mértékegységek megjelenítése Metric or Imperial on the node’s screen
12 órás időformátum használata Show the node’s clock as 12-hour rather than 24-hour
Félkövér címsor Draw the screen’s heading text in bold
Kijelző megfordítása Rotate the display 180° for an inverted mounting
OLED típus Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED
Érintésre vagy mozgásra ébresztés Light the screen when the node is tapped or moved
Iránytű tájolás Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each
Mindig észak felé mutasson Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Pozíció beállítások

On Settings → Device configuration → Position.

Setting Leírás
GPS mód (fizikai hardver) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the node asks its GPS for a fix
Sugárzási időköz How often the position is shared with the mesh
Intelligens pozíció Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Rögzített pozíció Use a manually entered latitude, longitude and altitude instead of the GPS
Pozíció jelzők (flags) A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Energia-beállítások

On Settings → Device configuration → Power.

Setting Leírás
Energiatakarékos mód engedélyezése Let the node sleep aggressively between activity
Leállítás áramszünet esetén Power the device down after external power disappears
Szuper mélyalvás időtartama How long the deepest sleep state lasts
Minimális ébrenléti idő The shortest time the node stays awake once woken
Bluetooth-várakozás időtartama How long to wait for a phone to connect before sleeping
ADC szorzó felülbírálása Turn on a manual correction for battery-voltage readings
ADC szorzó felülbírálási arány The correction factor itself, used only when the override is on
Akkumulátor INA_2XX I2C-cím Address of an external INA-series power sensor, if fitted

Hálózati beállítások

On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node.

Setting Leírás
Wi-Fi enabled Enable the Wi-Fi node (ESP32 nodes)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Jelszó Network password
Ethernet engedélyezve Use a wired connection on hardware that has one
IPv4 mód DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP szerver Time synchronization server
rsyslog szerver Remote logging server

Network Config with a static IPv4 address entered

Bluetooth beállítások

On Settings → Device configuration → Bluetooth, on nodes with Bluetooth.

Setting Leírás
Bluetooth engedélyezve Enable/disable BLE radio
Párosítási mód Fixed PIN, Random PIN, or No PIN
Rögzített PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Biztonsági beállítások

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

Setting Leírás
Nyilvános kulcs Your node’s public key (read-only)
Admin kulcs Keys permitted to administer this node remotely — up to three
Privát kulcs Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it
Privát kulcs újragenerálása Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Soros konzol Serial console over the Stream API
Hibakeresési napló API engedélyezve Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth
Felügyelt mód Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.

diff --git a/main/index.json b/main/index.json index cbdf5323a2..6c3566a90d 100644 --- a/main/index.json +++ b/main/index.json @@ -35,17 +35,17 @@ {"id":"connections","title":"Connections","section":"user","locale":"ar-rSA","resourcePath":"docs/ar-rSA/user/connections.html","navOrder":2,"keywords":["connections", "bluetooth", "ble", "pairing", "radio", "connection", "status", "troubleshooting", "usb", "serial", "setup", "tcp", "network", "connecting", "over", "the", "when", "use", "provisioning", "for", "mpwrd", "after", "your", "first", "reconnection", "behavior", "desktop", "related", "topics"],"aliases":["bluetooth", "usb", "tcp", "pairing"],"charCount":11132}, {"id":"debug-logs","title":"Debug Logs","section":"user","locale":"ar-rSA","resourcePath":"docs/ar-rSA/user/debug-logs.html","navOrder":22,"keywords":["debug", "logs", "the", "two", "tabs", "viewing", "app", "exporting", "desktop", "related", "topics"],"aliases":["debug-logs", "logcat", "app-logs", "bug-report"],"charCount":3119}, {"id":"desktop","title":"Desktop App","section":"user","locale":"ar-rSA","resourcePath":"docs/ar-rSA/user/desktop.html","navOrder":14,"keywords":["desktop", "app", "installation", "linux", "macos", "windows", "connecting", "your", "radio", "usb", "serial", "primary", "tcp", "bluetooth", "ble", "feature", "parity", "differences", "keyboard", "shortcuts", "window", "system", "tray", "notification", "preferences", "built", "documentation", "browser", "building", "from"],"aliases":["desktop", "linux", "macos", "windows", "jvm"],"charCount":9955}, - {"id":"discovery","title":"Local Mesh Discovery","section":"user","locale":"ar-rSA","resourcePath":"docs/ar-rSA/user/discovery.html","navOrder":12,"keywords":["local", "mesh", "discovery", "scanner", "setting", "scan", "live", "progress", "reading", "the", "results", "beacon", "manual", "exploration", "traceroute", "neighbor", "info", "node", "list", "tool", "tips", "for", "related", "topics"],"aliases":["discovery", "local-mesh-discovery", "mesh-discovery", "local-discovery", "network-scan", "traceroute", "neighbor-info"],"charCount":18334}, + {"id":"discovery","title":"Local Mesh Discovery","section":"user","locale":"ar-rSA","resourcePath":"docs/ar-rSA/user/discovery.html","navOrder":12,"keywords":["local", "mesh", "discovery", "scanner", "setting", "scan", "live", "progress", "reading", "the", "results", "beacon", "manual", "exploration", "traceroute", "neighbor", "info", "node", "list", "tool", "tips", "for", "related", "topics"],"aliases":["discovery", "local-mesh-discovery", "mesh-discovery", "local-discovery", "network-scan", "traceroute", "neighbor-info"],"charCount":18324}, {"id":"firmware","title":"Firmware Updates","section":"user","locale":"ar-rSA","resourcePath":"docs/ar-rSA/user/firmware.html","navOrder":13,"keywords":["firmware", "updates", "checking", "for", "update", "methods", "ota", "over", "the", "air", "via", "bluetooth", "network", "connected", "esp32", "app", "usb", "factory", "erase", "and", "bootloader", "upgrade", "other", "flashing", "options", "version", "channels", "pre", "checklist", "post"],"aliases":["firmware", "update", "ota", "flash"],"charCount":11096}, {"id":"help-and-docs","title":"Help & In-App Docs","section":"user","locale":"ar-rSA","resourcePath":"docs/ar-rSA/user/help-and-docs.html","navOrder":21,"keywords":["help", "app", "docs", "browsing", "search", "chirpy", "the", "assistant", "related", "topics"],"aliases":["help", "docs-browser", "chirpy", "assistant"],"charCount":2306}, {"id":"map-and-waypoints","title":"Map & Waypoints","section":"user","locale":"ar-rSA","resourcePath":"docs/ar-rSA/user/map-and-waypoints.html","navOrder":6,"keywords":["map", "waypoints", "view", "node", "markers", "controls", "filtering", "the", "creating", "waypoint", "properties", "expiration", "geofences", "managing", "layers", "site", "planner", "position", "sharing", "enabling", "privacy", "considerations", "sources", "adding", "your", "own", "tile", "source", "offline", "terrain"],"aliases":["map", "waypoints", "gps", "location", "site-planner", "map-layers", "geojson", "kml"],"charCount":14884}, {"id":"messages-and-channels","title":"Messages & Channels","section":"user","locale":"ar-rSA","resourcePath":"docs/ar-rSA/user/messages-and-channels.html","navOrder":3,"keywords":["messages", "channels", "default", "channel", "security", "adding", "archived", "direct", "sending", "message", "managing", "the", "conversation", "list", "bubbles", "states", "delivery", "errors", "features", "quick", "chat", "searching", "text", "formatting", "mentions", "reactions", "replying", "day", "separators", "jump"],"aliases":["channels", "direct-messages", "messaging", "conversations"],"charCount":23867}, - {"id":"mqtt","title":"MQTT","section":"user","locale":"ar-rSA","resourcePath":"docs/ar-rSA/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "configuration", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12415}, + {"id":"mqtt","title":"MQTT","section":"user","locale":"ar-rSA","resourcePath":"docs/ar-rSA/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "configuration", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12403}, {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"ar-rSA","resourcePath":"docs/ar-rSA/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "device", "environment", "air", "quality", "signal", "reference", "power", "traceroute", "reading", "results", "neighbor", "info", "host", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12592}, {"id":"nodes","title":"Nodes","section":"user","locale":"ar-rSA","resourcePath":"docs/ar-rSA/user/nodes.html","navOrder":4,"keywords":["nodes", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "security", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "not", "heard", "your", "current", "settings", "sort", "options", "per"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":23249}, {"id":"onboarding","title":"Getting Started","section":"user","locale":"ar-rSA","resourcePath":"docs/ar-rSA/user/onboarding.html","navOrder":1,"keywords":["getting", "started", "first", "launch", "welcome", "screen", "permissions", "bluetooth", "permission", "location", "notifications", "critical", "alerts", "reviewing", "later", "after", "setup", "related", "topics"],"aliases":["first-launch", "setup", "intro"],"charCount":8461}, - {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"ar-rSA","resourcePath":"docs/ar-rSA/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "mqtt", "module", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon", "tak", "administration"],"aliases":["modules", "module-config", "administration"],"charCount":33319}, - {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"ar-rSA","resourcePath":"docs/ar-rSA/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "configuration", "device", "config", "lora", "modem", "presets", "display", "position", "power", "network", "bluetooth", "security", "related", "topics"],"aliases":["الإعدادات", "radio-config", "user-config", "lora"],"charCount":41642}, + {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"ar-rSA","resourcePath":"docs/ar-rSA/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "mqtt", "module", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon", "tak", "administration"],"aliases":["modules", "module-config", "administration"],"charCount":32973}, + {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"ar-rSA","resourcePath":"docs/ar-rSA/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "configuration", "device", "config", "lora", "modem", "presets", "display", "position", "power", "network", "bluetooth", "security", "related", "topics"],"aliases":["الإعدادات", "radio-config", "user-config", "lora"],"charCount":42002}, {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"ar-rSA","resourcePath":"docs/ar-rSA/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5245}, {"id":"tak","title":"TAK Integration","section":"user","locale":"ar-rSA","resourcePath":"docs/ar-rSA/user/tak.html","navOrder":10,"keywords":["tak", "integration", "overview", "setup", "prerequisites", "configuration", "local", "server", "roles", "cot", "cursor", "target", "format", "wire", "usage", "with", "atak", "troubleshooting", "security", "considerations", "related", "topics"],"aliases":["tak", "atak", "team-awareness-kit"],"charCount":10705}, {"id":"telemetry-and-sensors","title":"Telemetry and sensors","section":"user","locale":"ar-rSA","resourcePath":"docs/ar-rSA/user/telemetry-and-sensors.html","navOrder":999,"keywords":["telemetry", "and", "sensors", "device", "environment", "temperature", "humidity", "air", "quality", "soil", "light", "weather", "other", "readings", "power", "metrics", "configuring", "choosing", "interval", "viewing", "troubleshooting", "related", "topics"],"aliases":[],"charCount":12274}, @@ -56,17 +56,17 @@ {"id":"connections","title":"Connections","section":"user","locale":"be-rBY","resourcePath":"docs/be-rBY/user/connections.html","navOrder":2,"keywords":["connections", "bluetooth", "ble", "pairing", "radio", "connection", "status", "troubleshooting", "usb", "serial", "setup", "tcp", "network", "connecting", "over", "the", "when", "use", "provisioning", "for", "mpwrd", "after", "your", "first", "reconnection", "behavior", "desktop", "related", "topics"],"aliases":["bluetooth", "usb", "tcp", "pairing"],"charCount":11078}, {"id":"debug-logs","title":"Debug Logs","section":"user","locale":"be-rBY","resourcePath":"docs/be-rBY/user/debug-logs.html","navOrder":22,"keywords":["debug", "logs", "the", "two", "tabs", "viewing", "app", "exporting", "desktop", "related", "topics"],"aliases":["debug-logs", "logcat", "app-logs", "bug-report"],"charCount":3119}, {"id":"desktop","title":"Desktop App","section":"user","locale":"be-rBY","resourcePath":"docs/be-rBY/user/desktop.html","navOrder":14,"keywords":["desktop", "app", "linux", "macos", "windows", "connecting", "your", "radio", "usb", "serial", "primary", "tcp", "bluetooth", "ble", "feature", "parity", "differences", "keyboard", "shortcuts", "window", "system", "tray", "notification", "preferences", "built", "documentation", "browser", "building", "from", "source"],"aliases":["desktop", "linux", "macos", "windows", "jvm"],"charCount":9952}, - {"id":"discovery","title":"Local Mesh Discovery","section":"user","locale":"be-rBY","resourcePath":"docs/be-rBY/user/discovery.html","navOrder":12,"keywords":["local", "mesh", "discovery", "scanner", "setting", "scan", "live", "progress", "reading", "the", "results", "beacon", "manual", "exploration", "traceroute", "neighbor", "info", "node", "list", "tool", "tips", "for", "related", "topics"],"aliases":["discovery", "local-mesh-discovery", "mesh-discovery", "local-discovery", "network-scan", "traceroute", "neighbor-info"],"charCount":18334}, + {"id":"discovery","title":"Local Mesh Discovery","section":"user","locale":"be-rBY","resourcePath":"docs/be-rBY/user/discovery.html","navOrder":12,"keywords":["local", "mesh", "discovery", "scanner", "setting", "scan", "live", "progress", "reading", "the", "results", "beacon", "manual", "exploration", "traceroute", "neighbor", "info", "node", "list", "tool", "tips", "for", "related", "topics"],"aliases":["discovery", "local-mesh-discovery", "mesh-discovery", "local-discovery", "network-scan", "traceroute", "neighbor-info"],"charCount":18324}, {"id":"firmware","title":"Firmware Updates","section":"user","locale":"be-rBY","resourcePath":"docs/be-rBY/user/firmware.html","navOrder":13,"keywords":["firmware", "updates", "checking", "for", "update", "methods", "ota", "over", "the", "air", "via", "bluetooth", "network", "connected", "esp32", "app", "usb", "factory", "erase", "and", "bootloader", "upgrade", "other", "flashing", "options", "version", "channels", "pre", "checklist", "post"],"aliases":["firmware", "update", "ota", "flash"],"charCount":11096}, {"id":"help-and-docs","title":"Help & In-App Docs","section":"user","locale":"be-rBY","resourcePath":"docs/be-rBY/user/help-and-docs.html","navOrder":21,"keywords":["help", "app", "docs", "browsing", "chirpy", "the", "assistant", "related", "topics"],"aliases":["help", "docs-browser", "chirpy", "assistant"],"charCount":2305}, {"id":"map-and-waypoints","title":"Map & Waypoints","section":"user","locale":"be-rBY","resourcePath":"docs/be-rBY/user/map-and-waypoints.html","navOrder":6,"keywords":["map", "waypoints", "view", "node", "markers", "controls", "filtering", "the", "creating", "waypoint", "properties", "expiration", "geofences", "managing", "layers", "site", "planner", "position", "sharing", "enabling", "privacy", "considerations", "sources", "adding", "your", "own", "tile", "source", "offline", "terrain"],"aliases":["map", "waypoints", "gps", "location", "site-planner", "map-layers", "geojson", "kml"],"charCount":14884}, {"id":"messages-and-channels","title":"Messages & Channels","section":"user","locale":"be-rBY","resourcePath":"docs/be-rBY/user/messages-and-channels.html","navOrder":3,"keywords":["messages", "channels", "default", "channel", "security", "adding", "archived", "direct", "sending", "message", "managing", "the", "conversation", "list", "bubbles", "states", "delivery", "errors", "features", "quick", "chat", "searching", "text", "formatting", "mentions", "reactions", "replying", "day", "separators", "jump"],"aliases":["channels", "direct-messages", "messaging", "conversations"],"charCount":23866}, - {"id":"mqtt","title":"MQTT","section":"user","locale":"be-rBY","resourcePath":"docs/be-rBY/user/mqtt.html","navOrder":11,"keywords":["mqtt", "how", "works", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting", "messages", "bridging"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12411}, + {"id":"mqtt","title":"MQTT","section":"user","locale":"be-rBY","resourcePath":"docs/be-rBY/user/mqtt.html","navOrder":11,"keywords":["mqtt", "how", "works", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting", "messages", "bridging"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12399}, {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"be-rBY","resourcePath":"docs/be-rBY/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "device", "environment", "air", "quality", "signal", "reference", "power", "traceroute", "reading", "results", "neighbor", "info", "host", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12603}, {"id":"nodes","title":"Nodes","section":"user","locale":"be-rBY","resourcePath":"docs/be-rBY/user/nodes.html","navOrder":4,"keywords":["nodes", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "security", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "not", "heard", "your", "current", "settings", "sort", "options", "per"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":23272}, {"id":"onboarding","title":"Начало работы","section":"user","locale":"be-rBY","resourcePath":"docs/be-rBY/user/onboarding.html","navOrder":1,"keywords":["first", "launch", "welcome", "screen", "permissions", "bluetooth", "permission", "location", "notifications", "critical", "alerts", "reviewing", "later", "after", "setup", "related", "topics"],"aliases":["first-launch", "setup", "intro"],"charCount":8457}, - {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"be-rBY","resourcePath":"docs/be-rBY/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "module", "configuration", "mqtt", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon", "tak"],"aliases":["modules", "module-config", "administration"],"charCount":33337}, - {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"be-rBY","resourcePath":"docs/be-rBY/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "device", "config", "lora", "modem", "presets", "display", "position", "power", "network", "bluetooth", "security", "related", "topics"],"aliases":["settings", "radio-config", "user-config", "lora"],"charCount":41640}, + {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"be-rBY","resourcePath":"docs/be-rBY/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "module", "configuration", "mqtt", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon", "tak"],"aliases":["modules", "module-config", "administration"],"charCount":32991}, + {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"be-rBY","resourcePath":"docs/be-rBY/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "device", "config", "lora", "modem", "presets", "display", "position", "power", "network", "bluetooth", "security", "related", "topics"],"aliases":["settings", "radio-config", "user-config", "lora"],"charCount":42000}, {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"be-rBY","resourcePath":"docs/be-rBY/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5239}, {"id":"tak","title":"TAK Integration","section":"user","locale":"be-rBY","resourcePath":"docs/be-rBY/user/tak.html","navOrder":10,"keywords":["tak", "integration", "setup", "prerequisites", "local", "server", "roles", "cot", "cursor", "target", "format", "wire", "usage", "with", "atak", "troubleshooting", "security", "considerations", "related", "topics"],"aliases":["tak", "atak", "team-awareness-kit"],"charCount":10701}, {"id":"telemetry-and-sensors","title":"Telemetry and sensors","section":"user","locale":"be-rBY","resourcePath":"docs/be-rBY/user/telemetry-and-sensors.html","navOrder":999,"keywords":["telemetry", "and", "sensors", "device", "environment", "temperature", "humidity", "air", "quality", "soil", "light", "weather", "other", "readings", "power", "metrics", "configuring", "choosing", "interval", "viewing", "troubleshooting", "related", "topics"],"aliases":[],"charCount":12325}, @@ -77,16 +77,16 @@ {"id":"connections","title":"Връзки","section":"user","locale":"bg-rBG","resourcePath":"docs/bg-rBG/user/connections.html","navOrder":2,"keywords":["bluetooth", "ble", "pairing", "radio", "troubleshooting", "usb", "serial", "tcp", "network", "when", "use", "mpwrd", "after", "your", "first", "connection", "reconnection", "behavior", "desktop", "connections", "related", "topics"],"aliases":["bluetooth", "usb", "tcp", "pairing"],"charCount":11148}, {"id":"debug-logs","title":"Debug Logs","section":"user","locale":"bg-rBG","resourcePath":"docs/bg-rBG/user/debug-logs.html","navOrder":22,"keywords":["debug", "logs", "the", "two", "tabs", "viewing", "app", "exporting", "desktop", "related", "topics"],"aliases":["debug-logs", "logcat", "app-logs", "bug-report"],"charCount":3135}, {"id":"desktop","title":"Настолно приложение","section":"user","locale":"bg-rBG","resourcePath":"docs/bg-rBG/user/desktop.html","navOrder":14,"keywords":["linux", "macos", "windows", "connecting", "your", "radio", "usb", "serial", "primary", "tcp", "bluetooth", "ble", "feature", "parity", "differences", "window", "system", "tray", "notification", "preferences", "built", "documentation", "browser", "building", "from", "source"],"aliases":["desktop", "linux", "macos", "windows", "jvm"],"charCount":10004}, - {"id":"discovery","title":"Local Mesh Discovery","section":"user","locale":"bg-rBG","resourcePath":"docs/bg-rBG/user/discovery.html","navOrder":12,"keywords":["local", "mesh", "discovery", "scanner", "setting", "scan", "live", "progress", "reading", "the", "results", "beacon", "manual", "exploration", "neighbor", "info", "node", "list", "tool", "tips", "for"],"aliases":["discovery", "local-mesh-discovery", "mesh-discovery", "local-discovery", "network-scan", "traceroute", "neighbor-info"],"charCount":18366}, + {"id":"discovery","title":"Local Mesh Discovery","section":"user","locale":"bg-rBG","resourcePath":"docs/bg-rBG/user/discovery.html","navOrder":12,"keywords":["local", "mesh", "discovery", "scanner", "setting", "scan", "live", "progress", "reading", "the", "results", "beacon", "manual", "exploration", "neighbor", "info", "node", "list", "tool", "tips", "for"],"aliases":["discovery", "local-mesh-discovery", "mesh-discovery", "local-discovery", "network-scan", "traceroute", "neighbor-info"],"charCount":18356}, {"id":"firmware","title":"Актуализации на фърмуера","section":"user","locale":"bg-rBG","resourcePath":"docs/bg-rBG/user/firmware.html","navOrder":13,"keywords":["ota", "over", "the", "air", "bluetooth", "via", "network", "connected", "esp32", "app", "usb", "update", "factory", "erase", "and", "bootloader", "upgrade", "other", "flashing", "options", "stuck", "radio", "won", "boot", "after"],"aliases":["firmware", "update", "ota", "flash"],"charCount":11327}, {"id":"help-and-docs","title":"Help & In-App Docs","section":"user","locale":"bg-rBG","resourcePath":"docs/bg-rBG/user/help-and-docs.html","navOrder":21,"keywords":["help", "app", "docs", "browsing", "chirpy", "the", "assistant"],"aliases":["help", "docs-browser", "chirpy", "assistant"],"charCount":2324}, {"id":"map-and-waypoints","title":"Map & Waypoints","section":"user","locale":"bg-rBG","resourcePath":"docs/bg-rBG/user/map-and-waypoints.html","navOrder":6,"keywords":["map", "waypoints", "view", "node", "markers", "controls", "filtering", "the", "creating", "waypoint", "properties", "expiration", "geofences", "managing", "site", "planner", "position", "sharing", "enabling", "privacy", "considerations", "sources", "adding", "your", "own", "tile", "source", "offline", "terrain", "going"],"aliases":["map", "waypoints", "gps", "location", "site-planner", "map-layers", "geojson", "kml"],"charCount":14914}, {"id":"messages-and-channels","title":"Съобщения & Канали","section":"user","locale":"bg-rBG","resourcePath":"docs/bg-rBG/user/messages-and-channels.html","navOrder":3,"keywords":["default", "channel", "adding", "archived", "channels", "sending", "direct", "message", "managing", "the", "conversation", "list", "bubbles", "states", "delivery", "errors", "features", "quick", "chat", "searching", "messages", "text", "formatting", "mentions", "reactions", "replying", "day", "separators", "jump", "latest"],"aliases":["канали", "direct-messages", "messaging", "conversations"],"charCount":24058}, - {"id":"mqtt","title":"MQTT","section":"user","locale":"bg-rBG","resourcePath":"docs/bg-rBG/user/mqtt.html","navOrder":11,"keywords":["mqtt", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "not", "connecting", "messages", "bridging"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12464}, + {"id":"mqtt","title":"MQTT","section":"user","locale":"bg-rBG","resourcePath":"docs/bg-rBG/user/mqtt.html","navOrder":11,"keywords":["mqtt", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "not", "connecting", "messages", "bridging"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12452}, {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"bg-rBG","resourcePath":"docs/bg-rBG/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "air", "quality", "signal", "reference", "reading", "traceroute", "results", "neighbor", "info", "host", "pax"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12770}, {"id":"nodes","title":"Възли","section":"user","locale":"bg-rBG","resourcePath":"docs/bg-rBG/user/nodes.html","navOrder":4,"keywords":["node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "security", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "nodes", "not", "heard", "your", "current", "settings", "sort", "options", "per"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":23378}, {"id":"onboarding","title":"Първи стъпки","section":"user","locale":"bg-rBG","resourcePath":"docs/bg-rBG/user/onboarding.html","navOrder":1,"keywords":["first", "launch", "welcome", "screen", "permissions", "bluetooth", "permission", "location", "notifications", "critical", "alerts", "reviewing", "later", "after", "setup"],"aliases":["first-launch", "setup", "intro"],"charCount":8480}, - {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"bg-rBG","resourcePath":"docs/bg-rBG/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "mqtt", "module", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon", "tak", "device"],"aliases":["modules", "module-config", "administration"],"charCount":34359}, + {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"bg-rBG","resourcePath":"docs/bg-rBG/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "mqtt", "module", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon", "tak", "device"],"aliases":["modules", "module-config", "administration"],"charCount":33988}, {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"bg-rBG","resourcePath":"docs/bg-rBG/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "lora", "modem", "presets", "bluetooth", "related", "topics"],"aliases":["настройки", "radio-config", "user-config", "lora"],"charCount":42651}, {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"bg-rBG","resourcePath":"docs/bg-rBG/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5297}, {"id":"tak","title":"TAK Integration","section":"user","locale":"bg-rBG","resourcePath":"docs/bg-rBG/user/tak.html","navOrder":10,"keywords":["tak", "integration", "setup", "prerequisites", "local", "server", "roles", "cot", "cursor", "target", "format", "wire", "usage", "with", "atak", "security", "considerations", "related", "topics"],"aliases":["tak", "atak", "team-awareness-kit"],"charCount":10741}, @@ -98,17 +98,17 @@ {"id":"connections","title":"Connections","section":"user","locale":"ca-rES","resourcePath":"docs/ca-rES/user/connections.html","navOrder":2,"keywords":["connections", "bluetooth", "ble", "pairing", "radio", "connection", "status", "troubleshooting", "usb", "serial", "setup", "tcp", "network", "connecting", "over", "the", "when", "use", "provisioning", "for", "mpwrd", "after", "your", "first", "reconnection", "behavior", "desktop", "related", "topics"],"aliases":["bluetooth", "usb", "tcp", "pairing"],"charCount":11120}, {"id":"debug-logs","title":"Debug Logs","section":"user","locale":"ca-rES","resourcePath":"docs/ca-rES/user/debug-logs.html","navOrder":22,"keywords":["debug", "logs", "the", "two", "tabs", "viewing", "app", "exporting", "desktop", "related", "topics"],"aliases":["debug-logs", "logcat", "app-logs", "bug-report"],"charCount":3119}, {"id":"desktop","title":"Desktop App","section":"user","locale":"ca-rES","resourcePath":"docs/ca-rES/user/desktop.html","navOrder":14,"keywords":["desktop", "app", "installation", "linux", "macos", "windows", "connecting", "your", "radio", "usb", "serial", "primary", "tcp", "bluetooth", "ble", "feature", "parity", "differences", "keyboard", "shortcuts", "window", "system", "tray", "notification", "preferences", "built", "documentation", "browser", "building", "from"],"aliases":["desktop", "linux", "macos", "windows", "jvm"],"charCount":9955}, - {"id":"discovery","title":"Local Mesh Discovery","section":"user","locale":"ca-rES","resourcePath":"docs/ca-rES/user/discovery.html","navOrder":12,"keywords":["local", "mesh", "discovery", "scanner", "setting", "scan", "live", "progress", "reading", "the", "results", "beacon", "manual", "exploration", "tra", "ruta", "neighbor", "info", "node", "list", "tool", "tips", "for", "related", "topics"],"aliases":["discovery", "local-mesh-discovery", "mesh-discovery", "local-discovery", "network-scan", "traceroute", "neighbor-info"],"charCount":18335}, + {"id":"discovery","title":"Local Mesh Discovery","section":"user","locale":"ca-rES","resourcePath":"docs/ca-rES/user/discovery.html","navOrder":12,"keywords":["local", "mesh", "discovery", "scanner", "setting", "scan", "live", "progress", "reading", "the", "results", "beacon", "manual", "exploration", "tra", "ruta", "neighbor", "info", "node", "list", "tool", "tips", "for", "related", "topics"],"aliases":["discovery", "local-mesh-discovery", "mesh-discovery", "local-discovery", "network-scan", "traceroute", "neighbor-info"],"charCount":18325}, {"id":"firmware","title":"Firmware Updates","section":"user","locale":"ca-rES","resourcePath":"docs/ca-rES/user/firmware.html","navOrder":13,"keywords":["firmware", "updates", "checking", "for", "update", "methods", "ota", "over", "the", "air", "via", "bluetooth", "network", "connected", "esp32", "app", "usb", "factory", "erase", "and", "bootloader", "upgrade", "other", "flashing", "options", "version", "channels", "pre", "checklist", "post"],"aliases":["firmware", "update", "ota", "flash"],"charCount":11096}, {"id":"help-and-docs","title":"Help & In-App Docs","section":"user","locale":"ca-rES","resourcePath":"docs/ca-rES/user/help-and-docs.html","navOrder":21,"keywords":["help", "app", "docs", "browsing", "search", "chirpy", "the", "assistant", "related", "topics"],"aliases":["help", "docs-browser", "chirpy", "assistant"],"charCount":2306}, {"id":"map-and-waypoints","title":"Map & Waypoints","section":"user","locale":"ca-rES","resourcePath":"docs/ca-rES/user/map-and-waypoints.html","navOrder":6,"keywords":["map", "waypoints", "view", "node", "markers", "controls", "filtering", "the", "creating", "waypoint", "properties", "expiration", "geofences", "managing", "layers", "site", "planner", "position", "sharing", "enabling", "privacy", "considerations", "sources", "adding", "your", "own", "tile", "source", "offline", "terrain"],"aliases":["map", "waypoints", "gps", "location", "site-planner", "map-layers", "geojson", "kml"],"charCount":14884}, {"id":"messages-and-channels","title":"Messages & Channels","section":"user","locale":"ca-rES","resourcePath":"docs/ca-rES/user/messages-and-channels.html","navOrder":3,"keywords":["messages", "channels", "default", "channel", "security", "adding", "archived", "direct", "sending", "message", "managing", "the", "conversation", "list", "bubbles", "states", "delivery", "errors", "features", "quick", "chat", "searching", "text", "formatting", "mentions", "reactions", "replying", "day", "separators", "jump"],"aliases":["channels", "direct-messages", "messaging", "conversations"],"charCount":23868}, - {"id":"mqtt","title":"MQTT","section":"user","locale":"ca-rES","resourcePath":"docs/ca-rES/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "configuration", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12415}, + {"id":"mqtt","title":"MQTT","section":"user","locale":"ca-rES","resourcePath":"docs/ca-rES/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "configuration", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12403}, {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"ca-rES","resourcePath":"docs/ca-rES/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "device", "environment", "air", "quality", "signal", "reference", "power", "tra", "ruta", "reading", "traceroute", "results", "position", "log", "neighbor", "info", "host", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12543}, {"id":"nodes","title":"Nodes","section":"user","locale":"ca-rES","resourcePath":"docs/ca-rES/user/nodes.html","navOrder":4,"keywords":["nodes", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "security", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "not", "heard", "your", "current", "settings", "sort", "options", "per"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":23251}, {"id":"onboarding","title":"Getting Started","section":"user","locale":"ca-rES","resourcePath":"docs/ca-rES/user/onboarding.html","navOrder":1,"keywords":["getting", "started", "first", "launch", "welcome", "screen", "permissions", "bluetooth", "permission", "location", "notifications", "critical", "alerts", "reviewing", "later", "after", "setup", "related", "topics"],"aliases":["first-launch", "setup", "intro"],"charCount":8461}, - {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"ca-rES","resourcePath":"docs/ca-rES/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "configuraci", "dul", "mqtt", "module", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon"],"aliases":["modules", "module-config", "administration"],"charCount":33518}, - {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"ca-rES","resourcePath":"docs/ca-rES/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "configuration", "device", "config", "lora", "modem", "presets", "display", "position", "power", "network", "bluetooth", "security", "related", "topics"],"aliases":["settings", "radio-config", "user-config", "lora"],"charCount":41641}, + {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"ca-rES","resourcePath":"docs/ca-rES/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "configuraci", "dul", "mqtt", "module", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon"],"aliases":["modules", "module-config", "administration"],"charCount":33172}, + {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"ca-rES","resourcePath":"docs/ca-rES/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "configuration", "device", "config", "lora", "modem", "presets", "display", "position", "power", "network", "bluetooth", "security", "related", "topics"],"aliases":["settings", "radio-config", "user-config", "lora"],"charCount":42001}, {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"ca-rES","resourcePath":"docs/ca-rES/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5233}, {"id":"tak","title":"TAK Integration","section":"user","locale":"ca-rES","resourcePath":"docs/ca-rES/user/tak.html","navOrder":10,"keywords":["tak", "integration", "overview", "setup", "prerequisites", "configuration", "local", "server", "roles", "cot", "cursor", "target", "format", "wire", "usage", "with", "atak", "troubleshooting", "security", "considerations", "related", "topics"],"aliases":["tak", "atak", "team-awareness-kit"],"charCount":10705}, {"id":"telemetry-and-sensors","title":"Telemetry and sensors","section":"user","locale":"ca-rES","resourcePath":"docs/ca-rES/user/telemetry-and-sensors.html","navOrder":999,"keywords":["telemetry", "and", "sensors", "device", "environment", "temperature", "humidity", "air", "quality", "soil", "light", "weather", "other", "readings", "power", "metrics", "configuring", "choosing", "interval", "viewing", "troubleshooting", "related", "topics"],"aliases":[],"charCount":12297}, @@ -119,16 +119,16 @@ {"id":"connections","title":"Připojení","section":"user","locale":"cs-rCZ","resourcePath":"docs/cs-rCZ/user/connections.html","navOrder":2,"keywords":["ipojen", "bluetooth", "ble", "pairing", "radio", "connection", "status", "troubleshooting", "usb", "serial", "setup", "tcp", "network", "connecting", "over", "the", "when", "use", "nastaven", "pro", "mpwrd", "after", "your", "first", "reconnection", "behavior", "desktop", "connections", "related", "topics"],"aliases":["bluetooth", "usb", "tcp", "pairing"],"charCount":11065}, {"id":"debug-logs","title":"Debug Logs","section":"user","locale":"cs-rCZ","resourcePath":"docs/cs-rCZ/user/debug-logs.html","navOrder":22,"keywords":["debug", "logs", "the", "two", "tabs", "viewing", "app", "exporting", "desktop", "related", "topics"],"aliases":["debug-logs", "logcat", "app-logs", "bug-report"],"charCount":3129}, {"id":"desktop","title":"Desktop App","section":"user","locale":"cs-rCZ","resourcePath":"docs/cs-rCZ/user/desktop.html","navOrder":14,"keywords":["desktop", "app", "installation", "linux", "macos", "windows", "connecting", "your", "radio", "usb", "serial", "primary", "tcp", "bluetooth", "ble", "feature", "parity", "differences", "keyboard", "shortcuts", "window", "system", "tray", "notification", "preferences", "built", "documentation", "browser", "building", "from"],"aliases":["desktop", "linux", "macos", "windows", "jvm"],"charCount":9952}, - {"id":"discovery","title":"Vyhledávání zařízení v místní mesh síti","section":"user","locale":"cs-rCZ","resourcePath":"docs/cs-rCZ/user/discovery.html","navOrder":12,"keywords":["vyhled", "zen", "stn", "mesh", "local", "discovery", "scanner", "setting", "scan", "live", "progress", "reading", "the", "results", "maj", "manual", "exploration", "traceroute", "informace", "sousedech", "node", "list", "tool", "tips", "for", "related", "topics"],"aliases":["discovery", "local-mesh-discovery", "mesh-discovery", "local-discovery", "network-scan", "traceroute", "neighbor-info"],"charCount":18379}, + {"id":"discovery","title":"Vyhledávání zařízení v místní mesh síti","section":"user","locale":"cs-rCZ","resourcePath":"docs/cs-rCZ/user/discovery.html","navOrder":12,"keywords":["vyhled", "zen", "stn", "mesh", "local", "discovery", "scanner", "setting", "scan", "live", "progress", "reading", "the", "results", "maj", "manual", "exploration", "traceroute", "informace", "sousedech", "node", "list", "tool", "tips", "for", "related", "topics"],"aliases":["discovery", "local-mesh-discovery", "mesh-discovery", "local-discovery", "network-scan", "traceroute", "neighbor-info"],"charCount":18369}, {"id":"firmware","title":"Aktualizace firmware","section":"user","locale":"cs-rCZ","resourcePath":"docs/cs-rCZ/user/firmware.html","navOrder":13,"keywords":["aktualizace", "firmware", "checking", "for", "updates", "update", "methods", "ota", "over", "the", "air", "via", "bluetooth", "network", "connected", "esp32", "app", "usb", "factory", "erase", "and", "bootloader", "upgrade", "other", "flashing", "options", "version", "channels", "pre", "checklist"],"aliases":["firmware", "update", "ota", "flash"],"charCount":11146}, {"id":"help-and-docs","title":"Help & In-App Docs","section":"user","locale":"cs-rCZ","resourcePath":"docs/cs-rCZ/user/help-and-docs.html","navOrder":21,"keywords":["help", "app", "docs", "browsing", "search", "chirpy", "the", "assistant", "related", "topics"],"aliases":["help", "docs-browser", "chirpy", "assistant"],"charCount":2316}, {"id":"map-and-waypoints","title":"Map & Waypoints","section":"user","locale":"cs-rCZ","resourcePath":"docs/cs-rCZ/user/map-and-waypoints.html","navOrder":6,"keywords":["map", "waypoints", "view", "node", "markers", "controls", "filtering", "the", "creating", "waypoint", "properties", "expiration", "geofences", "managing", "mapov", "vrstvy", "site", "planner", "position", "sharing", "enabling", "privacy", "considerations", "sources", "adding", "your", "own", "tile", "source", "offline"],"aliases":["map", "waypoints", "gps", "location", "site-planner", "map-layers", "geojson", "kml"],"charCount":14887}, {"id":"messages-and-channels","title":"Messages & Channels","section":"user","locale":"cs-rCZ","resourcePath":"docs/cs-rCZ/user/messages-and-channels.html","navOrder":3,"keywords":["messages", "channels", "kan", "default", "channel", "zabezpe", "adding", "archived", "direct", "sending", "message", "managing", "the", "conversation", "list", "bubbles", "states", "delivery", "errors", "features", "quick", "chat", "searching", "text", "formatting", "mentions", "reactions", "replying", "day", "separators"],"aliases":["channels", "direct-messages", "messaging", "conversations"],"charCount":23987}, - {"id":"mqtt","title":"MQTT","section":"user","locale":"cs-rCZ","resourcePath":"docs/cs-rCZ/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "nastaven", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12411}, + {"id":"mqtt","title":"MQTT","section":"user","locale":"cs-rCZ","resourcePath":"docs/cs-rCZ/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "nastaven", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12399}, {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"cs-rCZ","resourcePath":"docs/cs-rCZ/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "metriky", "zen", "prost", "air", "quality", "kvalita", "sign", "signal", "reference", "nap", "jen", "traceroute", "reading", "results", "protokol", "pozic", "informace", "sousedech", "hostitele", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12568}, {"id":"nodes","title":"Uzly","section":"user","locale":"cs-rCZ","resourcePath":"docs/cs-rCZ/user/nodes.html","navOrder":4,"keywords":["uzly", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "role", "uzlu", "security", "rychl", "akce", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "nodes", "not", "heard", "your", "current", "settings", "sort", "options"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":23473}, {"id":"onboarding","title":"Getting Started","section":"user","locale":"cs-rCZ","resourcePath":"docs/cs-rCZ/user/onboarding.html","navOrder":1,"keywords":["getting", "started", "first", "launch", "welcome", "screen", "permissions", "bluetooth", "permission", "location", "notifications", "critical", "alerts", "reviewing", "later", "after", "setup", "related", "topics"],"aliases":["first-launch", "setup", "intro"],"charCount":8511}, - {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"cs-rCZ","resourcePath":"docs/cs-rCZ/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "nastaven", "modul", "mqtt", "module", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon"],"aliases":["modules", "module-config", "administration"],"charCount":33887}, + {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"cs-rCZ","resourcePath":"docs/cs-rCZ/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "nastaven", "modul", "mqtt", "module", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon"],"aliases":["modules", "module-config", "administration"],"charCount":33735}, {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"cs-rCZ","resourcePath":"docs/cs-rCZ/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "nastaven", "zen", "lora", "modem", "presets", "zobrazen", "pozice", "nap", "jen", "bluetooth", "zabezpe", "related", "topics"],"aliases":["nastavení", "radio-config", "user-config", "lora"],"charCount":42520}, {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"cs-rCZ","resourcePath":"docs/cs-rCZ/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5239}, {"id":"tak","title":"TAK Integration","section":"user","locale":"cs-rCZ","resourcePath":"docs/cs-rCZ/user/tak.html","navOrder":10,"keywords":["tak", "integration", "overview", "setup", "prerequisites", "nastaven", "local", "server", "roles", "cot", "cursor", "target", "format", "wire", "usage", "with", "atak", "troubleshooting", "security", "considerations", "related", "topics"],"aliases":["tak", "atak", "team-awareness-kit"],"charCount":10701}, @@ -140,17 +140,17 @@ {"id":"connections","title":"Verbindungen","section":"user","locale":"de-rDE","resourcePath":"docs/de-rDE/user/connections.html","navOrder":2,"keywords":["verbindungen", "bluetooth", "ble", "pairing", "radio", "connection", "status", "troubleshooting", "usb", "serial", "einstellungen", "tcp", "network", "connecting", "over", "the", "when", "use", "wlan", "unterst", "tzung", "mpwrd", "after", "your", "first", "reconnection", "behavior", "desktop", "connections", "related"],"aliases":["bluetooth", "usb", "tcp", "Kopplung"],"charCount":11169}, {"id":"debug-logs","title":"Fehlersuchprotokolle","section":"user","locale":"de-rDE","resourcePath":"docs/de-rDE/user/debug-logs.html","navOrder":22,"keywords":["fehlersuchprotokolle", "the", "two", "tabs", "viewing", "app", "logs", "exporting", "desktop", "related", "topics"],"aliases":["debug-logs", "logcat", "app-logs", "bug-report"],"charCount":3145}, {"id":"desktop","title":"Desktop App","section":"user","locale":"de-rDE","resourcePath":"docs/de-rDE/user/desktop.html","navOrder":14,"keywords":["desktop", "app", "installation", "linux", "macos", "windows", "connecting", "your", "radio", "usb", "serial", "primary", "tcp", "bluetooth", "ble", "feature", "parity", "differences", "tastaturk", "rzel", "window", "system", "tray", "notification", "preferences", "built", "documentation", "browser", "building", "from"],"aliases":["desktop", "linux", "macos", "windows", "jvm"],"charCount":9979}, - {"id":"discovery","title":"Local Mesh Discovery","section":"user","locale":"de-rDE","resourcePath":"docs/de-rDE/user/discovery.html","navOrder":12,"keywords":["local", "mesh", "discovery", "scanner", "setting", "scan", "live", "progress", "reading", "the", "results", "beacon", "manual", "exploration", "traceroute", "nachbarinformation", "node", "list", "tool", "tips", "for", "verwandte", "themen"],"aliases":["discovery", "local-mesh-discovery", "mesh-discovery", "local-discovery", "network-scan", "traceroute", "neighbor-info"],"charCount":18364}, + {"id":"discovery","title":"Local Mesh Discovery","section":"user","locale":"de-rDE","resourcePath":"docs/de-rDE/user/discovery.html","navOrder":12,"keywords":["local", "mesh", "discovery", "scanner", "setting", "scan", "live", "progress", "reading", "the", "results", "beacon", "manual", "exploration", "traceroute", "nachbarinformation", "node", "list", "tool", "tips", "for", "verwandte", "themen"],"aliases":["discovery", "local-mesh-discovery", "mesh-discovery", "local-discovery", "network-scan", "traceroute", "neighbor-info"],"charCount":18354}, {"id":"firmware","title":"Firmwareaktualisierungen","section":"user","locale":"de-rDE","resourcePath":"docs/de-rDE/user/firmware.html","navOrder":13,"keywords":["firmwareaktualisierungen", "checking", "for", "updates", "update", "methods", "ota", "over", "the", "air", "via", "bluetooth", "network", "connected", "esp32", "app", "usb", "factory", "erase", "and", "bootloader", "upgrade", "other", "flashing", "options", "version", "channels", "pre", "checklist", "post"],"aliases":["firmware", "update", "ota", "flash"],"charCount":11123}, {"id":"help-and-docs","title":"Help & In-App Docs","section":"user","locale":"de-rDE","resourcePath":"docs/de-rDE/user/help-and-docs.html","navOrder":21,"keywords":["help", "app", "docs", "browsing", "suchen", "chirpy", "the", "assistant", "related", "topics"],"aliases":["Hilfe", "docs-browser", "chirpy", "assistant"],"charCount":2313}, {"id":"map-and-waypoints","title":"Map & Waypoints","section":"user","locale":"de-rDE","resourcePath":"docs/de-rDE/user/map-and-waypoints.html","navOrder":6,"keywords":["map", "waypoints", "view", "node", "markers", "kartensteuerung", "filtering", "the", "creating", "waypoint", "properties", "expiration", "geofences", "managing", "kartenebenen", "site", "planner", "position", "sharing", "enabling", "privacy", "considerations", "sources", "adding", "your", "own", "tile", "source", "offline", "terrain"],"aliases":["map", "waypoints", "gps", "location", "site-planner", "map-layers", "geojson", "kml"],"charCount":14965}, {"id":"messages-and-channels","title":"Messages & Channels","section":"user","locale":"de-rDE","resourcePath":"docs/de-rDE/user/messages-and-channels.html","navOrder":3,"keywords":["messages", "channels", "kan", "default", "channel", "kanalsicherheit", "adding", "archived", "direktnachrichten", "sending", "direct", "message", "managing", "the", "conversation", "list", "bubbles", "states", "delivery", "errors", "features", "quick", "chat", "searching", "text", "formatting", "mentions", "reactions", "replying", "day"],"aliases":["channels", "direct-messages", "messaging", "conversations"],"charCount":24115}, - {"id":"mqtt","title":"MQTT","section":"user","locale":"de-rDE","resourcePath":"docs/de-rDE/user/mqtt.html","navOrder":11,"keywords":["mqtt", "bersicht", "funktioniert", "einstellungen", "aktivieren", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "bew", "hrte", "praktiken", "fehlerbehebung", "not", "connecting"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12426}, + {"id":"mqtt","title":"MQTT","section":"user","locale":"de-rDE","resourcePath":"docs/de-rDE/user/mqtt.html","navOrder":11,"keywords":["mqtt", "bersicht", "funktioniert", "einstellungen", "aktivieren", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "bew", "hrte", "praktiken", "fehlerbehebung", "not", "connecting"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12414}, {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"de-rDE","resourcePath":"docs/de-rDE/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "ger", "tedaten", "umweltdaten", "air", "quality", "signalqualit", "signal", "reference", "energiedaten", "traceroute", "reading", "results", "standortprotokoll", "nachbarinformation", "host", "kennzahlen", "benutzerz", "hlerdaten", "verwandte", "themen"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12976}, {"id":"nodes","title":"Knoten","section":"user","locale":"de-rDE","resourcePath":"docs/de-rDE/user/nodes.html","navOrder":4,"keywords":["knoten", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "security", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "nodes", "not", "heard", "your", "current", "settings", "sort", "options"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":23529}, {"id":"onboarding","title":"Erste Schritte","section":"user","locale":"de-rDE","resourcePath":"docs/de-rDE/user/onboarding.html","navOrder":1,"keywords":["erste", "schritte", "first", "launch", "welcome", "screen", "permissions", "bluetooth", "permission", "location", "notifications", "critical", "alerts", "reviewing", "later", "after", "setup", "verwandte", "themen"],"aliases":["first-launch", "setup", "intro"],"charCount":8565}, - {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"de-rDE","resourcePath":"docs/de-rDE/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "moduleinstellungen", "mqtt", "module", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon", "tak"],"aliases":["modules", "module-config", "administration"],"charCount":34128}, - {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"de-rDE","resourcePath":"docs/de-rDE/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "benutzereinstellungen", "profile", "applying", "changes", "einstellungen", "ger", "teeinstellungen", "lora", "modem", "presets", "anzeigeeinstellungen", "standorteinstellungen", "energie", "netzwerkeinstellungen", "bluetooth", "sicherheitseinstellungen", "related", "topics"],"aliases":["Einstellungen", "radio-config", "user-config", "lora"],"charCount":42529}, + {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"de-rDE","resourcePath":"docs/de-rDE/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "moduleinstellungen", "mqtt", "module", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon", "tak"],"aliases":["modules", "module-config", "administration"],"charCount":33693}, + {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"de-rDE","resourcePath":"docs/de-rDE/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "benutzereinstellungen", "profile", "applying", "changes", "einstellungen", "ger", "teeinstellungen", "lora", "modem", "presets", "anzeigeeinstellungen", "standorteinstellungen", "energie", "netzwerkeinstellungen", "bluetooth", "sicherheitseinstellungen", "related", "topics"],"aliases":["Einstellungen", "radio-config", "user-config", "lora"],"charCount":42763}, {"id":"signal-meter","title":"Wie das Meshtastic Signal Meter funktioniert","section":"user","locale":"de-rDE","resourcePath":"docs/de-rDE/user/signal-meter.html","navOrder":15,"keywords":["wie", "das", "meshtastic", "signal", "meter", "funktioniert", "rssi", "and", "snr", "decoding", "below", "the", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["Signal", "Signal-Meter", "snr", "rssi"],"charCount":5378}, {"id":"tak","title":"TAK Integration","section":"user","locale":"de-rDE","resourcePath":"docs/de-rDE/user/tak.html","navOrder":10,"keywords":["tak", "integration", "bersicht", "einstellungen", "voraussetzungen", "local", "server", "roles", "cot", "cursor", "target", "format", "wire", "usage", "with", "atak", "fehlerbehebung", "security", "considerations", "related", "topics"],"aliases":["tak", "atak", "team-awareness-kit"],"charCount":10727}, {"id":"telemetry-and-sensors","title":"Telemetry and sensors","section":"user","locale":"de-rDE","resourcePath":"docs/de-rDE/user/telemetry-and-sensors.html","navOrder":999,"keywords":["telemetry", "and", "sensors", "ger", "tetelemetrie", "environment", "temperature", "humidity", "air", "quality", "soil", "light", "weather", "other", "readings", "energiedaten", "configuring", "choosing", "interval", "metrics", "viewing", "fehlerbehebung", "related", "topics"],"aliases":[],"charCount":12385}, @@ -161,17 +161,17 @@ {"id":"connections","title":"Connections","section":"user","locale":"el-rGR","resourcePath":"docs/el-rGR/user/connections.html","navOrder":2,"keywords":["connections", "bluetooth", "ble", "pairing", "radio", "connection", "status", "troubleshooting", "usb", "serial", "setup", "tcp", "network", "connecting", "over", "the", "when", "use", "provisioning", "for", "mpwrd", "after", "your", "first", "reconnection", "behavior", "desktop", "related", "topics"],"aliases":["bluetooth", "usb", "tcp", "pairing"],"charCount":11102}, {"id":"debug-logs","title":"Debug Logs","section":"user","locale":"el-rGR","resourcePath":"docs/el-rGR/user/debug-logs.html","navOrder":22,"keywords":["debug", "logs", "the", "two", "tabs", "viewing", "app", "exporting", "desktop", "related", "topics"],"aliases":["debug-logs", "logcat", "app-logs", "bug-report"],"charCount":3119}, {"id":"desktop","title":"Desktop App","section":"user","locale":"el-rGR","resourcePath":"docs/el-rGR/user/desktop.html","navOrder":14,"keywords":["desktop", "app", "installation", "linux", "macos", "windows", "connecting", "your", "radio", "usb", "serial", "primary", "tcp", "bluetooth", "ble", "feature", "parity", "differences", "keyboard", "shortcuts", "window", "system", "tray", "notification", "preferences", "built", "documentation", "browser", "building", "from"],"aliases":["desktop", "linux", "macos", "windows", "jvm"],"charCount":9955}, - {"id":"discovery","title":"Local Mesh Discovery","section":"user","locale":"el-rGR","resourcePath":"docs/el-rGR/user/discovery.html","navOrder":12,"keywords":["local", "mesh", "discovery", "scanner", "setting", "scan", "live", "progress", "reading", "the", "results", "beacon", "manual", "exploration", "traceroute", "neighbor", "info", "node", "list", "tool", "tips", "for", "related", "topics"],"aliases":["discovery", "local-mesh-discovery", "mesh-discovery", "local-discovery", "network-scan", "traceroute", "neighbor-info"],"charCount":18334}, + {"id":"discovery","title":"Local Mesh Discovery","section":"user","locale":"el-rGR","resourcePath":"docs/el-rGR/user/discovery.html","navOrder":12,"keywords":["local", "mesh", "discovery", "scanner", "setting", "scan", "live", "progress", "reading", "the", "results", "beacon", "manual", "exploration", "traceroute", "neighbor", "info", "node", "list", "tool", "tips", "for", "related", "topics"],"aliases":["discovery", "local-mesh-discovery", "mesh-discovery", "local-discovery", "network-scan", "traceroute", "neighbor-info"],"charCount":18324}, {"id":"firmware","title":"Firmware Updates","section":"user","locale":"el-rGR","resourcePath":"docs/el-rGR/user/firmware.html","navOrder":13,"keywords":["firmware", "updates", "checking", "for", "update", "methods", "ota", "over", "the", "air", "via", "bluetooth", "network", "connected", "esp32", "app", "usb", "factory", "erase", "and", "bootloader", "upgrade", "other", "flashing", "options", "version", "channels", "pre", "checklist", "post"],"aliases":["firmware", "update", "ota", "flash"],"charCount":11096}, {"id":"help-and-docs","title":"Help & In-App Docs","section":"user","locale":"el-rGR","resourcePath":"docs/el-rGR/user/help-and-docs.html","navOrder":21,"keywords":["help", "app", "docs", "browsing", "search", "chirpy", "the", "assistant", "related", "topics"],"aliases":["help", "docs-browser", "chirpy", "assistant"],"charCount":2306}, {"id":"map-and-waypoints","title":"Map & Waypoints","section":"user","locale":"el-rGR","resourcePath":"docs/el-rGR/user/map-and-waypoints.html","navOrder":6,"keywords":["map", "waypoints", "view", "node", "markers", "controls", "filtering", "the", "creating", "waypoint", "properties", "expiration", "geofences", "managing", "layers", "site", "planner", "position", "sharing", "enabling", "privacy", "considerations", "sources", "adding", "your", "own", "tile", "source", "offline", "terrain"],"aliases":["map", "waypoints", "gps", "location", "site-planner", "map-layers", "geojson", "kml"],"charCount":14884}, {"id":"messages-and-channels","title":"Messages & Channels","section":"user","locale":"el-rGR","resourcePath":"docs/el-rGR/user/messages-and-channels.html","navOrder":3,"keywords":["messages", "channels", "default", "channel", "security", "adding", "archived", "direct", "sending", "message", "managing", "the", "conversation", "list", "bubbles", "states", "delivery", "errors", "features", "quick", "chat", "searching", "text", "formatting", "mentions", "reactions", "replying", "day", "separators", "jump"],"aliases":["channels", "direct-messages", "messaging", "conversations"],"charCount":23867}, - {"id":"mqtt","title":"MQTT","section":"user","locale":"el-rGR","resourcePath":"docs/el-rGR/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "configuration", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12415}, + {"id":"mqtt","title":"MQTT","section":"user","locale":"el-rGR","resourcePath":"docs/el-rGR/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "configuration", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12403}, {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"el-rGR","resourcePath":"docs/el-rGR/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "device", "environment", "air", "quality", "signal", "reference", "power", "traceroute", "reading", "results", "neighbor", "info", "host", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12558}, {"id":"nodes","title":"Nodes","section":"user","locale":"el-rGR","resourcePath":"docs/el-rGR/user/nodes.html","navOrder":4,"keywords":["nodes", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "security", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "not", "heard", "your", "current", "settings", "sort", "options", "per"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":23251}, {"id":"onboarding","title":"Getting Started","section":"user","locale":"el-rGR","resourcePath":"docs/el-rGR/user/onboarding.html","navOrder":1,"keywords":["getting", "started", "first", "launch", "welcome", "screen", "permissions", "bluetooth", "permission", "location", "notifications", "critical", "alerts", "reviewing", "later", "after", "setup", "related", "topics"],"aliases":["first-launch", "setup", "intro"],"charCount":8461}, - {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"el-rGR","resourcePath":"docs/el-rGR/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "mqtt", "module", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon", "tak", "device"],"aliases":["modules", "module-config", "administration"],"charCount":33485}, - {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"el-rGR","resourcePath":"docs/el-rGR/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "configuration", "device", "config", "lora", "modem", "presets", "display", "position", "power", "network", "bluetooth", "security", "related", "topics"],"aliases":["ρυθμίσεις", "radio-config", "user-config", "lora"],"charCount":41645}, + {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"el-rGR","resourcePath":"docs/el-rGR/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "mqtt", "module", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon", "tak", "device"],"aliases":["modules", "module-config", "administration"],"charCount":33139}, + {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"el-rGR","resourcePath":"docs/el-rGR/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "configuration", "device", "config", "lora", "modem", "presets", "display", "position", "power", "network", "bluetooth", "security", "related", "topics"],"aliases":["ρυθμίσεις", "radio-config", "user-config", "lora"],"charCount":42005}, {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"el-rGR","resourcePath":"docs/el-rGR/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5233}, {"id":"tak","title":"TAK Integration","section":"user","locale":"el-rGR","resourcePath":"docs/el-rGR/user/tak.html","navOrder":10,"keywords":["tak", "integration", "overview", "setup", "prerequisites", "configuration", "local", "server", "roles", "cot", "cursor", "target", "format", "wire", "usage", "with", "atak", "troubleshooting", "security", "considerations", "related", "topics"],"aliases":["tak", "atak", "team-awareness-kit"],"charCount":10705}, {"id":"telemetry-and-sensors","title":"Telemetry and sensors","section":"user","locale":"el-rGR","resourcePath":"docs/el-rGR/user/telemetry-and-sensors.html","navOrder":999,"keywords":["telemetry", "and", "sensors", "device", "environment", "temperature", "humidity", "air", "quality", "soil", "light", "weather", "other", "readings", "power", "metrics", "configuring", "choosing", "interval", "viewing", "troubleshooting", "related", "topics"],"aliases":[],"charCount":12290}, @@ -182,17 +182,17 @@ {"id":"connections","title":"Conexiones","section":"user","locale":"es-rES","resourcePath":"docs/es-rES/user/connections.html","navOrder":2,"keywords":["conexiones", "bluetooth", "ble", "pairing", "radio", "connection", "status", "troubleshooting", "usb", "serial", "setup", "tcp", "network", "connecting", "over", "the", "when", "use", "provisioning", "for", "mpwrd", "after", "your", "first", "reconnection", "behavior", "desktop", "connections", "related", "topics"],"aliases":["bluetooth", "usb", "tcp", "pairing"],"charCount":11124}, {"id":"debug-logs","title":"Debug Logs","section":"user","locale":"es-rES","resourcePath":"docs/es-rES/user/debug-logs.html","navOrder":22,"keywords":["debug", "logs", "the", "two", "tabs", "viewing", "app", "exporting", "desktop", "related", "topics"],"aliases":["debug-logs", "logcat", "app-logs", "bug-report"],"charCount":3119}, {"id":"desktop","title":"Desktop App","section":"user","locale":"es-rES","resourcePath":"docs/es-rES/user/desktop.html","navOrder":14,"keywords":["desktop", "app", "installation", "linux", "macos", "windows", "connecting", "your", "radio", "usb", "serial", "primary", "tcp", "bluetooth", "ble", "feature", "parity", "differences", "keyboard", "shortcuts", "window", "system", "tray", "notification", "preferences", "built", "documentation", "browser", "building", "from"],"aliases":["desktop", "linux", "macos", "windows", "jvm"],"charCount":9955}, - {"id":"discovery","title":"Local Mesh Discovery","section":"user","locale":"es-rES","resourcePath":"docs/es-rES/user/discovery.html","navOrder":12,"keywords":["local", "mesh", "discovery", "scanner", "setting", "scan", "live", "progress", "reading", "the", "results", "beacon", "manual", "exploration", "traceroute", "informaci", "vecinos", "node", "list", "tool", "tips", "for", "related", "topics"],"aliases":["discovery", "local-mesh-discovery", "mesh-discovery", "local-discovery", "network-scan", "traceroute", "neighbor-info"],"charCount":18343}, + {"id":"discovery","title":"Local Mesh Discovery","section":"user","locale":"es-rES","resourcePath":"docs/es-rES/user/discovery.html","navOrder":12,"keywords":["local", "mesh", "discovery", "scanner", "setting", "scan", "live", "progress", "reading", "the", "results", "beacon", "manual", "exploration", "traceroute", "informaci", "vecinos", "node", "list", "tool", "tips", "for", "related", "topics"],"aliases":["discovery", "local-mesh-discovery", "mesh-discovery", "local-discovery", "network-scan", "traceroute", "neighbor-info"],"charCount":18333}, {"id":"firmware","title":"Firmware Updates","section":"user","locale":"es-rES","resourcePath":"docs/es-rES/user/firmware.html","navOrder":13,"keywords":["firmware", "updates", "checking", "for", "update", "methods", "ota", "over", "the", "air", "via", "bluetooth", "network", "connected", "esp32", "app", "usb", "factory", "erase", "and", "bootloader", "upgrade", "other", "flashing", "options", "version", "channels", "pre", "checklist", "post"],"aliases":["firmware", "update", "ota", "flash"],"charCount":11096}, {"id":"help-and-docs","title":"Help & In-App Docs","section":"user","locale":"es-rES","resourcePath":"docs/es-rES/user/help-and-docs.html","navOrder":21,"keywords":["help", "app", "docs", "browsing", "search", "chirpy", "the", "assistant", "related", "topics"],"aliases":["help", "docs-browser", "chirpy", "assistant"],"charCount":2306}, {"id":"map-and-waypoints","title":"Map & Waypoints","section":"user","locale":"es-rES","resourcePath":"docs/es-rES/user/map-and-waypoints.html","navOrder":6,"keywords":["map", "waypoints", "view", "node", "markers", "controls", "filtering", "the", "creating", "waypoint", "properties", "expiration", "geofences", "managing", "capas", "del", "mapa", "site", "planner", "position", "sharing", "enabling", "privacy", "considerations", "sources", "adding", "your", "own", "tile", "source"],"aliases":["map", "waypoints", "gps", "location", "site-planner", "map-layers", "geojson", "kml"],"charCount":14896}, {"id":"messages-and-channels","title":"Messages & Channels","section":"user","locale":"es-rES","resourcePath":"docs/es-rES/user/messages-and-channels.html","navOrder":3,"keywords":["messages", "channels", "canales", "default", "channel", "seguridad", "del", "canal", "adding", "archived", "direct", "sending", "message", "managing", "the", "conversation", "list", "bubbles", "states", "delivery", "errors", "features", "quick", "chat", "searching", "text", "formatting", "mentions", "reactions", "replying"],"aliases":["channels", "direct-messages", "messaging", "conversations"],"charCount":23870}, - {"id":"mqtt","title":"MQTT","section":"user","locale":"es-rES","resourcePath":"docs/es-rES/user/mqtt.html","navOrder":11,"keywords":["mqtt", "visi", "general", "how", "works", "configuraci", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12421}, + {"id":"mqtt","title":"MQTT","section":"user","locale":"es-rES","resourcePath":"docs/es-rES/user/mqtt.html","navOrder":11,"keywords":["mqtt", "visi", "general", "how", "works", "configuraci", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12409}, {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"es-rES","resourcePath":"docs/es-rES/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "tricas", "dispositivo", "entorno", "air", "quality", "calidad", "signal", "reference", "energ", "traceroute", "reading", "results", "registro", "posiciones", "informaci", "vecinos", "del", "anfitri", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12616}, {"id":"nodes","title":"Nodos","section":"user","locale":"es-rES","resourcePath":"docs/es-rES/user/nodes.html","navOrder":4,"keywords":["nodos", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "security", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "nodes", "not", "heard", "your", "current", "settings", "sort", "options"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":23294}, {"id":"onboarding","title":"Primeros Pasos","section":"user","locale":"es-rES","resourcePath":"docs/es-rES/user/onboarding.html","navOrder":1,"keywords":["primeros", "pasos", "first", "launch", "welcome", "screen", "permissions", "bluetooth", "permission", "location", "notifications", "critical", "alerts", "reviewing", "later", "after", "setup", "related", "topics"],"aliases":["first-launch", "setup", "intro"],"charCount":8534}, - {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"es-rES","resourcePath":"docs/es-rES/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "configuraci", "dulo", "mqtt", "module", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon"],"aliases":["modules", "module-config", "administration"],"charCount":34558}, - {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"es-rES","resourcePath":"docs/es-rES/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "configuraci", "del", "dispositivo", "lora", "modem", "presets", "pantalla", "posici", "elecenerg", "red", "bluetooth", "seguridad", "related", "topics"],"aliases":["ajustes", "radio-config", "user-config", "lora"],"charCount":42931}, + {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"es-rES","resourcePath":"docs/es-rES/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "configuraci", "dulo", "mqtt", "module", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon"],"aliases":["modules", "module-config", "administration"],"charCount":34061}, + {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"es-rES","resourcePath":"docs/es-rES/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "configuraci", "del", "dispositivo", "lora", "modem", "presets", "pantalla", "posici", "elecenerg", "red", "bluetooth", "seguridad", "related", "topics"],"aliases":["ajustes", "radio-config", "user-config", "lora"],"charCount":43003}, {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"es-rES","resourcePath":"docs/es-rES/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5257}, {"id":"tak","title":"TAK Integration","section":"user","locale":"es-rES","resourcePath":"docs/es-rES/user/tak.html","navOrder":10,"keywords":["tak", "integration", "visi", "general", "setup", "prerequisites", "configuraci", "local", "server", "roles", "cot", "cursor", "target", "format", "wire", "usage", "with", "atak", "troubleshooting", "security", "considerations", "related", "topics"],"aliases":["tak", "atak", "team-awareness-kit"],"charCount":10711}, {"id":"telemetry-and-sensors","title":"Telemetry and sensors","section":"user","locale":"es-rES","resourcePath":"docs/es-rES/user/telemetry-and-sensors.html","navOrder":999,"keywords":["telemetry", "and", "sensors", "device", "environment", "temperature", "humidity", "air", "quality", "soil", "light", "weather", "other", "readings", "tricas", "energ", "configuring", "choosing", "interval", "metrics", "viewing", "troubleshooting", "related", "topics"],"aliases":[],"charCount":12425}, @@ -203,17 +203,17 @@ {"id":"connections","title":"Ühendus","section":"user","locale":"et-rEE","resourcePath":"docs/et-rEE/user/connections.html","navOrder":2,"keywords":["hendus", "sinihammas", "ble", "pairing", "radio", "henduse", "olek", "sinihamba", "veaotsing", "usb", "port", "seadistamine", "troubleshooting", "tcp", "connecting", "over", "the", "network", "millal", "kasutada", "wifi", "loomine", "mpwrd", "jaoks", "after", "your", "first", "connection", "reconnection", "behavior"],"aliases":["sinihammas", "usb", "tcp", "seon"],"charCount":11126}, {"id":"debug-logs","title":"Arendaja logid","section":"user","locale":"et-rEE","resourcePath":"docs/et-rEE/user/debug-logs.html","navOrder":22,"keywords":["arendaja", "logid", "the", "two", "tabs", "viewing", "app", "logs", "eksportimine", "laud", "seotud", "teemad"],"aliases":["arendaja-logid", "logcat", "app-logs", "bug-report"],"charCount":3259}, {"id":"desktop","title":"Desktop App","section":"user","locale":"et-rEE","resourcePath":"docs/et-rEE/user/desktop.html","navOrder":14,"keywords":["desktop", "app", "paigaldus", "linux", "macos", "windows", "connecting", "your", "radio", "usb", "port", "esmane", "tcp", "sinihammas", "ble", "feature", "parity", "differences", "kiirklahvid", "window", "system", "tray", "notification", "preferences", "sisseehitatud", "dokumentatsioonibrauser", "building", "from", "source", "known"],"aliases":["töölaud", "linux", "macos", "windows", "jvm"],"charCount":10023}, - {"id":"discovery","title":"Kohalik kärgvõrgu avastaja","section":"user","locale":"et-rEE","resourcePath":"docs/et-rEE/user/discovery.html","navOrder":12,"keywords":["kohalik", "rgv", "rgu", "avastaja", "skanner", "setting", "scan", "live", "progress", "reading", "the", "results", "majakas", "manual", "exploration", "marsruudi", "naabruse", "teave", "node", "list", "discovery", "tool", "tips", "for", "mesh", "seotud", "teemad"],"aliases":["discovery", "local-mesh-discovery", "kärgvõrgu-avastamine", "kohalik-avastamine", "võrguskannimine", "traceroute", "naabri-info"],"charCount":18391}, + {"id":"discovery","title":"Kohalik kärgvõrgu avastaja","section":"user","locale":"et-rEE","resourcePath":"docs/et-rEE/user/discovery.html","navOrder":12,"keywords":["kohalik", "rgv", "rgu", "avastaja", "skanner", "setting", "scan", "live", "progress", "reading", "the", "results", "majakas", "manual", "exploration", "marsruudi", "naabruse", "teave", "node", "list", "discovery", "tool", "tips", "for", "mesh", "seotud", "teemad"],"aliases":["discovery", "local-mesh-discovery", "kärgvõrgu-avastamine", "kohalik-avastamine", "võrguskannimine", "traceroute", "naabri-info"],"charCount":18381}, {"id":"firmware","title":"Püsivara värskendus","section":"user","locale":"et-rEE","resourcePath":"docs/et-rEE/user/firmware.html","navOrder":13,"keywords":["sivara", "rskendus", "kontrollin", "rskendust", "rskendamise", "meetod", "ota", "over", "the", "air", "sinihamba", "abil", "via", "network", "connected", "esp32", "rakendusesisene", "usb", "factory", "erase", "and", "bootloader", "upgrade", "muud", "sivarauuenduse", "valikud", "versioonikanalid", "eelv", "rskenduse", "kontrollnimekiri"],"aliases":["püsivara", "värskendus", "ota", "püsivarauuendus"],"charCount":11310}, {"id":"help-and-docs","title":"Help & In-App Docs","section":"user","locale":"et-rEE","resourcePath":"docs/et-rEE/user/help-and-docs.html","navOrder":21,"keywords":["help", "app", "docs", "browsing", "otsi", "chirpy", "assistent", "seotud", "teemad"],"aliases":["abi", "docs-browser", "chirpy", "assistent"],"charCount":2373}, {"id":"map-and-waypoints","title":"Kaart ja teekonnapunktid","section":"user","locale":"et-rEE","resourcePath":"docs/et-rEE/user/map-and-waypoints.html","navOrder":6,"keywords":["kaart", "teekonnapunktid", "kaardi", "vaade", "node", "markers", "juhtnupud", "filtering", "the", "map", "teekonnapunkt", "loo", "waypoint", "properties", "expiration", "teekonnapunktide", "geopiirded", "managing", "waypoints", "kaardikihid", "saidi", "planeerija", "position", "sharing", "enabling", "privacy", "considerations", "allikad", "adding", "your"],"aliases":["kaart", "teekonnapunkt", "gps", "asukoht", "saidi planeerija", "kaardi-kihid", "geojson", "kml"],"charCount":15075}, {"id":"messages-and-channels","title":"Sõnumid ja kanalid","section":"user","locale":"et-rEE","resourcePath":"docs/et-rEE/user/messages-and-channels.html","navOrder":3,"keywords":["numid", "kanalid", "kanal", "vaikekanal", "kanali", "turvalisus", "lisa", "archived", "channels", "otses", "sending", "direct", "message", "managing", "the", "conversation", "list", "bubbles", "numi", "olek", "delivery", "errors", "omadused", "kiirvestlus", "otsin", "numeid", "numimullid", "teksti", "vormindamine", "mainimine"],"aliases":["kanalid", "otsesõnumid", "messaging", "conversations"],"charCount":24043}, - {"id":"mqtt","title":"MQTT","section":"user","locale":"et-rEE","resourcePath":"docs/et-rEE/user/mqtt.html","navOrder":11,"keywords":["mqtt", "levaade", "kuidas", "see", "toimib", "tted", "luba", "connection", "status", "and", "test", "puhverserver", "sellel", "telefonil", "meshtastic", "vaikemaakler", "private", "broker", "kaardiaruannete", "koostamine", "leslink", "allalink", "numivormingud", "encryption", "privacy", "parimad", "tavad", "veaotsing", "hendu", "messages"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12446}, + {"id":"mqtt","title":"MQTT","section":"user","locale":"et-rEE","resourcePath":"docs/et-rEE/user/mqtt.html","navOrder":11,"keywords":["mqtt", "levaade", "kuidas", "see", "toimib", "tted", "luba", "connection", "status", "and", "test", "puhverserver", "sellel", "telefonil", "meshtastic", "vaikemaakler", "private", "broker", "kaardiaruannete", "koostamine", "leslink", "allalink", "numivormingud", "encryption", "privacy", "parimad", "tavad", "veaotsing", "hendu", "messages"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12434}, {"id":"node-metrics","title":"Sõlme mõõdikud","section":"user","locale":"et-rEE","resourcePath":"docs/et-rEE/user/node-metrics.html","navOrder":5,"keywords":["lme", "dikud", "viewing", "metrics", "seadme", "keskkonnam", "air", "quality", "levi", "kvaliteet", "signal", "reference", "imsusn", "itajad", "marsruudi", "traceroute", "tulemuste", "lugemine", "asukoha", "logi", "naabruse", "teave", "hosti", "dik", "pax", "diku", "seotud", "teemad"],"aliases":["meetriline", "telemeetria", "sõlme-mõõdikud", "signaal"],"charCount":12798}, {"id":"nodes","title":"Sõlmed","section":"user","locale":"et-rEE","resourcePath":"docs/et-rEE/user/nodes.html","navOrder":4,"keywords":["lmed", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "security", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "nodes", "not", "heard", "your", "current", "settings", "sort", "options"],"aliases":["sõlmede loend", "mesh-nodes", "eakaaslased", "hop-histogram"],"charCount":23754}, {"id":"onboarding","title":"Getting Started","section":"user","locale":"et-rEE","resourcePath":"docs/et-rEE/user/onboarding.html","navOrder":1,"keywords":["getting", "started", "first", "launch", "tervituskuva", "permissions", "sinihamba", "load", "asukoha", "luba", "rguannete", "critical", "alerts", "permission", "reviewing", "later", "peale", "seadistamist", "seotud", "teemad"],"aliases":["first-launch", "seadistamine", "sissejuhatus"],"charCount":8529}, - {"id":"settings-module-admin","title":"Sätted - moodulid & admin","section":"user","locale":"et-rEE","resourcePath":"docs/et-rEE/user/settings-module-admin.html","navOrder":8,"keywords":["tted", "moodulid", "admin", "mooduli", "mqtt", "module", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon", "tak"],"aliases":["moodul", "mooduli sätted", "administratsioon"],"charCount":34121}, - {"id":"settings-radio-user","title":"Seaded — raadio ja kasutaja","section":"user","locale":"et-rEE","resourcePath":"docs/et-rEE/user/settings-radio-user.html","navOrder":7,"keywords":["seaded", "raadio", "kasutaja", "how", "these", "screens", "work", "kasutajaprofiil", "applying", "changes", "tted", "seadme", "lora", "modem", "presets", "ekraani", "asukoha", "toite", "rgu", "sinihamba", "turva", "seotud", "teemad"],"aliases":["sätted", "raadio-sätted", "kasutaja-sätted", "lora"],"charCount":41980}, + {"id":"settings-module-admin","title":"Sätted - moodulid & admin","section":"user","locale":"et-rEE","resourcePath":"docs/et-rEE/user/settings-module-admin.html","navOrder":8,"keywords":["tted", "moodulid", "admin", "mooduli", "mqtt", "module", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon", "tak"],"aliases":["moodul", "mooduli sätted", "administratsioon"],"charCount":33788}, + {"id":"settings-radio-user","title":"Seaded — raadio ja kasutaja","section":"user","locale":"et-rEE","resourcePath":"docs/et-rEE/user/settings-radio-user.html","navOrder":7,"keywords":["seaded", "raadio", "kasutaja", "how", "these", "screens", "work", "kasutajaprofiil", "applying", "changes", "tted", "seadme", "lora", "modem", "presets", "ekraani", "asukoha", "toite", "rgu", "sinihamba", "turva", "seotud", "teemad"],"aliases":["sätted", "raadio-sätted", "kasutaja-sätted", "lora"],"charCount":42250}, {"id":"signal-meter","title":"Kuidas Meshtastic signaalimõõtur töötab","section":"user","locale":"et-rEE","resourcePath":"docs/et-rEE/user/signal-meter.html","navOrder":15,"keywords":["kuidas", "meshtastic", "signaalim", "tur", "tab", "rssi", "and", "snr", "decoding", "below", "the", "noise", "floor", "rating", "signal", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "seotud", "teemad"],"aliases":["signaal", "signaali-mõõtur", "snr", "rssi"],"charCount":5291}, {"id":"tak","title":"TAK integratsioon","section":"user","locale":"et-rEE","resourcePath":"docs/et-rEE/user/tak.html","navOrder":10,"keywords":["tak", "integratsioon", "levaade", "seadistamine", "prerequisites", "tted", "lokaalne", "server", "rollid", "cot", "cursor", "target", "vorming", "numivorming", "kasutamine", "koos", "atakiga", "veaotsing", "security", "considerations", "seotud", "teemad"],"aliases":["tak", "atak", "meeskonna teadlikkuse komplekt"],"charCount":11116}, {"id":"telemetry-and-sensors","title":"Telemetry and sensors","section":"user","locale":"et-rEE","resourcePath":"docs/et-rEE/user/telemetry-and-sensors.html","navOrder":999,"keywords":["telemetry", "and", "sensors", "telemeetria", "sensorid", "device", "environment", "temperature", "humidity", "air", "quality", "soil", "valgus", "weather", "other", "readings", "imsusn", "itajad", "configuring", "choosing", "interval", "metrics", "viewing", "veaotsing", "seotud", "teemad"],"aliases":[],"charCount":12183}, @@ -224,17 +224,17 @@ {"id":"connections","title":"Yhteydet","section":"user","locale":"fi-rFI","resourcePath":"docs/fi-rFI/user/connections.html","navOrder":2,"keywords":["yhteydet", "bluetooth", "ble", "radion", "pariliitt", "minen", "yhteyden", "tila", "bluetoothin", "vianm", "ritys", "usb", "sarjaporttiyhteys", "asetukset", "troubleshooting", "tcp", "verkko", "yhdist", "verkon", "kautta", "milloin", "yhteytt", "kannattaa", "ytt", "wifi", "mpwrd", "lle", "after", "your", "first"],"aliases":["bluetooth", "usb", "tcp", "pariliitos"],"charCount":11729}, {"id":"debug-logs","title":"Virheenjäljityslokitiedot","section":"user","locale":"fi-rFI","resourcePath":"docs/fi-rFI/user/debug-logs.html","navOrder":22,"keywords":["virheenj", "ljityslokitiedot", "kaksi", "lilehte", "sovelluslokitietojen", "tarkastelu", "lokien", "vienti", "aiheeseen", "liittyv", "aiheet"],"aliases":["debug-lokitiedot", "logcat", "sovelluslokitiedot", "vikailmoitus"],"charCount":3571}, {"id":"desktop","title":"Työpöytäsovellus","section":"user","locale":"fi-rFI","resourcePath":"docs/fi-rFI/user/desktop.html","navOrder":14,"keywords":["sovellus", "asennus", "linux", "macos", "windows", "radioon", "yhdist", "minen", "usb", "sarjaportti", "ensisijainen", "tcp", "bluetooth", "ble", "ominaisuuksien", "yhtenevyys", "ytt", "liittym", "erot", "pikan", "imet", "ikkuna", "rjestelm", "tarjotin", "ilmoitusasetukset", "sis", "nrakennettu", "dokumentaatioselain", "rakentaminen", "hdekoodista"],"aliases":["työpöytä", "linux", "macos", "windows", "jvm"],"charCount":10948}, - {"id":"discovery","title":"Paikallisen mesh-verkon skannaus","section":"user","locale":"fi-rFI","resourcePath":"docs/fi-rFI/user/discovery.html","navOrder":12,"keywords":["paikallisen", "mesh", "verkon", "skannaus", "paikallinen", "haku", "scanner", "setting", "scan", "live", "progress", "reading", "the", "results", "verkkokutsu", "manual", "exploration", "reitinselvitys", "naapuritieto", "node", "list", "discovery", "tool", "tips", "for", "aiheeseen", "liittyv", "aiheet"],"aliases":["haku", "paikallisen mesh-verkon haku", "mesh-verkon haku", "paikallinen haku", "verkkohaku", "reitinselvitys", "naapuritieto"],"charCount":19024}, + {"id":"discovery","title":"Paikallisen mesh-verkon skannaus","section":"user","locale":"fi-rFI","resourcePath":"docs/fi-rFI/user/discovery.html","navOrder":12,"keywords":["paikallisen", "mesh", "verkon", "skannaus", "paikallinen", "haku", "scanner", "setting", "scan", "live", "progress", "reading", "the", "results", "verkkokutsu", "manual", "exploration", "reitinselvitys", "naapuritieto", "node", "list", "discovery", "tool", "tips", "for", "aiheeseen", "liittyv", "aiheet"],"aliases":["haku", "paikallisen mesh-verkon haku", "mesh-verkon haku", "paikallinen haku", "verkkohaku", "reitinselvitys", "naapuritieto"],"charCount":19014}, {"id":"firmware","title":"Laiteohjelmiston päivitykset","section":"user","locale":"fi-rFI","resourcePath":"docs/fi-rFI/user/firmware.html","navOrder":13,"keywords":["laiteohjelmiston", "ivitykset", "ivitysten", "tarkistaminen", "ivitysmenetelm", "ota", "over", "the", "air", "bluetooth", "yhteyden", "kautta", "wifi", "verkkoon", "yhdistetty", "esp32", "usb", "ivitys", "sovelluksesta", "tyhjennys", "tehdasasetuksiin", "ynnistyslataimen", "muut", "ivitysvaihtoehdot", "versiokanavat", "ivityst", "edelt", "tarkistuslista", "ivityksen", "lkeen"],"aliases":["firmware", "päivitä", "ota", "ohjelmoi"],"charCount":12195}, {"id":"help-and-docs","title":"Ohjeet jasovelluksen sisäinen dokumentaatio","section":"user","locale":"fi-rFI","resourcePath":"docs/fi-rFI/user/help-and-docs.html","navOrder":21,"keywords":["ohjeet", "jasovelluksen", "sis", "inen", "dokumentaatio", "sovelluksen", "selaaminen", "haku", "chirpy", "teko", "lyn", "avustaja", "aiheeseen", "liittyv", "aiheet"],"aliases":["apua", "dokumenttiselain", "chirpy", "avustaja"],"charCount":2638}, {"id":"map-and-waypoints","title":"Kartta ja reittipisteet","section":"user","locale":"fi-rFI","resourcePath":"docs/fi-rFI/user/map-and-waypoints.html","navOrder":6,"keywords":["kartta", "reittipisteet", "karttan", "kym", "radioiden", "merkinn", "kartan", "hallinta", "filtering", "the", "map", "reittipisteen", "luominen", "ominaisuudet", "vanheneminen", "reittipisteiden", "aluerajaukset", "karttatasot", "site", "planner", "sijainnin", "jakaminen", "jakamisen", "ytt", "notto", "tietosuoja", "karttal", "hteet", "oman", "karttatiilipalvelun"],"aliases":["kartta", "reittipisteet", "gps", "sijainti", "site-planner", "karttatasot", "geojson", "kml"],"charCount":16104}, {"id":"messages-and-channels","title":"Viestit ja kanavat","section":"user","locale":"fi-rFI","resourcePath":"docs/fi-rFI/user/messages-and-channels.html","navOrder":3,"keywords":["viestit", "kanavat", "oletuskanava", "kanavan", "turvallisuus", "lis", "minen", "archived", "channels", "yksityisviestit", "yksityisviestin", "hett", "keskusteluluettelon", "hallinta", "keskustelukuplat", "viestin", "tilat", "toimitusvirheet", "viestiominaisuudet", "pikachatti", "viestien", "haku", "viestikuplat", "tekstin", "muotoilu", "maininnat", "reaktiot", "vastaaminen", "erottimet", "siirry"],"aliases":["kanavat", "yksityisviestit", "viestit", "keskustelut"],"charCount":25840}, - {"id":"mqtt","title":"MQTT","section":"user","locale":"fi-rFI","resourcePath":"docs/fi-rFI/user/mqtt.html","navOrder":11,"keywords":["mqtt", "yleiskatsaus", "kuinka", "toimii", "asetukset", "ytt", "notto", "yhteyden", "tila", "testaa", "yhteys", "lityspalvelin", "puhelimessa", "oletus", "meshtastic", "oma", "karttaraportointi", "hetys", "vastaanotto", "viestiformaatit", "salaus", "yksityisyys", "parhaat", "vianetsint", "yhdist", "viestit", "eiv", "lity", "aiheeseen", "liittyv"],"aliases":["mqtt", "internet-silta", "välityspalvelin"],"charCount":13534}, + {"id":"mqtt","title":"MQTT","section":"user","locale":"fi-rFI","resourcePath":"docs/fi-rFI/user/mqtt.html","navOrder":11,"keywords":["mqtt", "yleiskatsaus", "kuinka", "toimii", "asetukset", "ytt", "notto", "yhteyden", "tila", "testaa", "yhteys", "lityspalvelin", "puhelimessa", "oletus", "meshtastic", "oma", "karttaraportointi", "hetys", "vastaanotto", "viestiformaatit", "salaus", "yksityisyys", "parhaat", "vianetsint", "yhdist", "viestit", "eiv", "lity", "aiheeseen", "liittyv"],"aliases":["mqtt", "internet-silta", "välityspalvelin"],"charCount":13522}, {"id":"node-metrics","title":"Radion mittarit","section":"user","locale":"fi-rFI","resourcePath":"docs/fi-rFI/user/node-metrics.html","navOrder":5,"keywords":["radion", "mittarit", "mittareiden", "tarkastelu", "laitteen", "mittausloki", "ymp", "rist", "arvot", "ilmanlaatumittarit", "signaalin", "laatu", "laadun", "viitearvot", "virranhallinnan", "reitinselvitys", "reitinselvityksen", "tulosten", "lukeminen", "sijainnin", "loki", "naapuritieto", "mittausarvot", "pax", "aiheeseen", "liittyv", "aiheet"],"aliases":["mittarit", "telemetria", "laitteen mittarit", "signaali"],"charCount":14092}, {"id":"nodes","title":"Laitteet","section":"user","locale":"fi-rFI","resourcePath":"docs/fi-rFI/user/nodes.html","navOrder":4,"keywords":["laitteet", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "radioiden", "roolit", "role", "security", "pikatoiminnot", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "nodes", "not", "heard", "your", "current", "settings", "sort", "options"],"aliases":["radiolista", "mesh-radiot", "vertaisradiot", "Hyppymääräjakauma"],"charCount":24516}, {"id":"onboarding","title":"Aloittaminen","section":"user","locale":"fi-rFI","resourcePath":"docs/fi-rFI/user/onboarding.html","navOrder":1,"keywords":["aloittaminen", "ensimm", "inen", "ynnistys", "aloitusn", "kym", "ytt", "oikeudet", "bluetooth", "oikeus", "sijaintik", "ilmoitusk", "kriittisten", "lytysten", "oikeuksien", "tarkistaminen", "hemmin", "rityksen", "lkeen", "aiheeseen", "liittyv", "aiheet"],"aliases":["ensimmäinen käynnistys", "asetukset", "esittely"],"charCount":9481}, - {"id":"settings-module-admin","title":"Asetukset — Moduulit ja ylläpito","section":"user","locale":"fi-rFI","resourcePath":"docs/fi-rFI/user/settings-module-admin.html","navOrder":8,"keywords":["asetukset", "moduulit", "yll", "pito", "moduulin", "mqtt", "module", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon"],"aliases":["moduulit", "moduulin asetukset", "ylläpito"],"charCount":36068}, - {"id":"settings-radio-user","title":"Asetukset — Radio ja käyttäjä","section":"user","locale":"fi-rFI","resourcePath":"docs/fi-rFI/user/settings-radio-user.html","navOrder":7,"keywords":["asetukset", "radio", "ytt", "how", "these", "screens", "work", "profiili", "applying", "changes", "laitteen", "lora", "modem", "presets", "sijainnin", "virran", "verkon", "bluetooth", "turvallisuusasetukset", "aiheeseen", "liittyv", "aiheet"],"aliases":["asetukset", "radion asetukset", "käyttäjän asetukset", "lora"],"charCount":44324}, + {"id":"settings-module-admin","title":"Asetukset — Moduulit ja ylläpito","section":"user","locale":"fi-rFI","resourcePath":"docs/fi-rFI/user/settings-module-admin.html","navOrder":8,"keywords":["asetukset", "moduulit", "yll", "pito", "moduulin", "mqtt", "module", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon"],"aliases":["moduulit", "moduulin asetukset", "ylläpito"],"charCount":35856}, + {"id":"settings-radio-user","title":"Asetukset — Radio ja käyttäjä","section":"user","locale":"fi-rFI","resourcePath":"docs/fi-rFI/user/settings-radio-user.html","navOrder":7,"keywords":["asetukset", "radio", "ytt", "how", "these", "screens", "work", "profiili", "applying", "changes", "laitteen", "lora", "modem", "presets", "sijainnin", "virran", "verkon", "bluetooth", "turvallisuusasetukset", "aiheeseen", "liittyv", "aiheet"],"aliases":["asetukset", "radion asetukset", "käyttäjän asetukset", "lora"],"charCount":44340}, {"id":"signal-meter","title":"Kuinka Meshtastic-signaalimittari toimii","section":"user","locale":"fi-rFI","resourcePath":"docs/fi-rFI/user/signal-meter.html","navOrder":15,"keywords":["kuinka", "meshtastic", "signaalimittari", "toimii", "rssi", "snr", "vastaanotto", "kohinatason", "alapuolelta", "signaalin", "laadun", "arviointi", "paikallisten", "iri", "iden", "tunnistaminen", "miss", "signaalitieto", "kyy", "aiheeseen", "liittyv", "aiheet"],"aliases":["signaali", "signaalimittari", "snr", "rssi"],"charCount":5753}, {"id":"tak","title":"TAK-integraatio","section":"user","locale":"fi-rFI","resourcePath":"docs/fi-rFI/user/tak.html","navOrder":10,"keywords":["tak", "integraatio", "yleiskatsaus", "asetukset", "edellytykset", "paikallinen", "palvelin", "roolit", "cot", "cursor", "target", "muoto", "wire", "format", "ytt", "atak", "kanssa", "vianetsint", "tietoturvahuomiot", "aiheeseen", "liittyv", "aiheet"],"aliases":["tak", "atak", "team awareness kit"],"charCount":11743}, {"id":"telemetry-and-sensors","title":"Telemetry and sensors","section":"user","locale":"fi-rFI","resourcePath":"docs/fi-rFI/user/telemetry-and-sensors.html","navOrder":999,"keywords":["telemetry", "and", "sensors", "telemetria", "anturit", "laitteen", "telemetriatiedot", "ymp", "rist", "tila", "kosteus", "ilmanlaatu", "maaper", "valo", "weather", "other", "readings", "virranhallinnan", "arvot", "telemetrian", "ritt", "minen", "mittausv", "lin", "valitseminen", "ilmanlaatumittarit", "tarkastelu", "vianetsint", "aiheeseen", "liittyv"],"aliases":[],"charCount":12957}, @@ -245,16 +245,16 @@ {"id":"connections","title":"Connexions","section":"user","locale":"fr-rCA","resourcePath":"docs/fr-rCA/user/connections.html","navOrder":2,"keywords":["connexions", "bluetooth", "ble", "pairing", "radio", "connection", "status", "troubleshooting", "usb", "serial", "setup", "tcp", "network", "connecting", "over", "the", "when", "use", "approvisionnement", "pour", "mpwrd", "after", "your", "first", "reconnection", "behavior", "desktop", "connections", "related", "topics"],"aliases":["bluetooth", "usb", "tcp", "pairing"],"charCount":11112}, {"id":"debug-logs","title":"Debug Logs","section":"user","locale":"fr-rCA","resourcePath":"docs/fr-rCA/user/debug-logs.html","navOrder":22,"keywords":["debug", "logs", "the", "two", "tabs", "viewing", "app", "exporting", "desktop", "related", "topics"],"aliases":["debug-logs", "logcat", "app-logs", "bug-report"],"charCount":3131}, {"id":"desktop","title":"Desktop App","section":"user","locale":"fr-rCA","resourcePath":"docs/fr-rCA/user/desktop.html","navOrder":14,"keywords":["desktop", "app", "installation", "linux", "macos", "windows", "connecting", "your", "radio", "usb", "serial", "primary", "tcp", "bluetooth", "ble", "feature", "parity", "differences", "keyboard", "shortcuts", "window", "system", "tray", "notification", "preferences", "built", "documentation", "browser", "building", "from"],"aliases":["desktop", "linux", "macos", "windows", "jvm"],"charCount":9955}, - {"id":"discovery","title":"Découverte de maille locale","section":"user","locale":"fr-rCA","resourcePath":"docs/fr-rCA/user/discovery.html","navOrder":12,"keywords":["couverte", "maille", "locale", "local", "mesh", "discovery", "scanner", "setting", "scan", "live", "progress", "reading", "the", "results", "beacon", "manual", "exploration", "traceroute", "informations", "sur", "les", "voisins", "node", "list", "tool", "tips", "for", "related", "topics"],"aliases":["discovery", "local-mesh-discovery", "mesh-discovery", "local-discovery", "network-scan", "traceroute", "neighbor-info"],"charCount":18363}, + {"id":"discovery","title":"Découverte de maille locale","section":"user","locale":"fr-rCA","resourcePath":"docs/fr-rCA/user/discovery.html","navOrder":12,"keywords":["couverte", "maille", "locale", "local", "mesh", "discovery", "scanner", "setting", "scan", "live", "progress", "reading", "the", "results", "beacon", "manual", "exploration", "traceroute", "informations", "sur", "les", "voisins", "node", "list", "tool", "tips", "for", "related", "topics"],"aliases":["discovery", "local-mesh-discovery", "mesh-discovery", "local-discovery", "network-scan", "traceroute", "neighbor-info"],"charCount":18353}, {"id":"firmware","title":"Firmware Updates","section":"user","locale":"fr-rCA","resourcePath":"docs/fr-rCA/user/firmware.html","navOrder":13,"keywords":["firmware", "updates", "checking", "for", "update", "methods", "ota", "over", "the", "air", "via", "bluetooth", "network", "connected", "esp32", "app", "usb", "factory", "erase", "and", "bootloader", "upgrade", "other", "flashing", "options", "version", "channels", "pre", "checklist", "post"],"aliases":["firmware", "update", "ota", "flash"],"charCount":11111}, {"id":"help-and-docs","title":"Help & In-App Docs","section":"user","locale":"fr-rCA","resourcePath":"docs/fr-rCA/user/help-and-docs.html","navOrder":21,"keywords":["help", "app", "docs", "browsing", "search", "chirpy", "the", "assistant", "related", "topics"],"aliases":["help", "docs-browser", "chirpy", "assistant"],"charCount":2318}, {"id":"map-and-waypoints","title":"Map & Waypoints","section":"user","locale":"fr-rCA","resourcePath":"docs/fr-rCA/user/map-and-waypoints.html","navOrder":6,"keywords":["map", "waypoints", "view", "node", "markers", "controls", "filtering", "the", "creating", "waypoint", "properties", "expiration", "geofences", "managing", "couches", "cartographiques", "site", "planner", "position", "sharing", "enabling", "privacy", "considerations", "sources", "adding", "your", "own", "tile", "source", "offline"],"aliases":["map", "waypoints", "gps", "location", "site-planner", "map-layers", "geojson", "kml"],"charCount":14905}, {"id":"messages-and-channels","title":"Messages & Channels","section":"user","locale":"fr-rCA","resourcePath":"docs/fr-rCA/user/messages-and-channels.html","navOrder":3,"keywords":["messages", "channels", "canaux", "default", "channel", "curit", "canal", "adding", "archived", "directs", "sending", "direct", "message", "managing", "the", "conversation", "list", "bubbles", "states", "delivery", "errors", "features", "quick", "chat", "searching", "text", "formatting", "mentions", "reactions", "replying"],"aliases":["channels", "direct-messages", "messaging", "conversations"],"charCount":23868}, - {"id":"mqtt","title":"MQTT","section":"user","locale":"fr-rCA","resourcePath":"docs/fr-rCA/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "configuration", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12415}, + {"id":"mqtt","title":"MQTT","section":"user","locale":"fr-rCA","resourcePath":"docs/fr-rCA/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "configuration", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12403}, {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"fr-rCA","resourcePath":"docs/fr-rCA/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "triques", "appareil", "environnement", "air", "quality", "qualit", "signal", "reference", "alimentation", "traceroute", "reading", "results", "journal", "des", "positions", "informations", "sur", "les", "voisins", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12683}, {"id":"nodes","title":"Nœuds","section":"user","locale":"fr-rCA","resourcePath":"docs/fr-rCA/user/nodes.html","navOrder":4,"keywords":["uds", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "security", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "nodes", "not", "heard", "your", "current", "settings", "sort", "options"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":23310}, {"id":"onboarding","title":"Getting Started","section":"user","locale":"fr-rCA","resourcePath":"docs/fr-rCA/user/onboarding.html","navOrder":1,"keywords":["getting", "started", "first", "launch", "welcome", "screen", "permissions", "bluetooth", "permission", "location", "notifications", "critical", "alerts", "reviewing", "later", "after", "setup", "related", "topics"],"aliases":["first-launch", "setup", "intro"],"charCount":8571}, - {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"fr-rCA","resourcePath":"docs/fr-rCA/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "glages", "module", "mqtt", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon", "tak"],"aliases":["modules", "module-config", "administration"],"charCount":34509}, + {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"fr-rCA","resourcePath":"docs/fr-rCA/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "glages", "module", "mqtt", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon", "tak"],"aliases":["modules", "module-config", "administration"],"charCount":33917}, {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"fr-rCA","resourcePath":"docs/fr-rCA/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "param", "tres", "utilisateur", "profile", "applying", "changes", "configuration", "appareil", "lora", "modem", "presets", "cran", "position", "alimentation", "seau", "bluetooth", "curit", "related", "topics"],"aliases":["paramètres", "radio-config", "user-config", "lora"],"charCount":43385}, {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"fr-rCA","resourcePath":"docs/fr-rCA/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5251}, {"id":"tak","title":"TAK Integration","section":"user","locale":"fr-rCA","resourcePath":"docs/fr-rCA/user/tak.html","navOrder":10,"keywords":["tak", "integration", "overview", "setup", "prerequisites", "configuration", "local", "server", "roles", "cot", "cursor", "target", "format", "wire", "usage", "with", "atak", "troubleshooting", "security", "considerations", "related", "topics"],"aliases":["tak", "atak", "team-awareness-kit"],"charCount":10737}, @@ -266,16 +266,16 @@ {"id":"connections","title":"Connexions","section":"user","locale":"fr-rFR","resourcePath":"docs/fr-rFR/user/connections.html","navOrder":2,"keywords":["connexions", "bluetooth", "ble", "pairing", "radio", "connection", "status", "troubleshooting", "usb", "serial", "setup", "tcp", "network", "connecting", "over", "the", "when", "use", "approvisionnement", "pour", "mpwrd", "after", "your", "first", "reconnection", "behavior", "desktop", "connections", "related", "topics"],"aliases":["bluetooth", "usb", "tcp", "pairing"],"charCount":11112}, {"id":"debug-logs","title":"Debug Logs","section":"user","locale":"fr-rFR","resourcePath":"docs/fr-rFR/user/debug-logs.html","navOrder":22,"keywords":["debug", "logs", "the", "two", "tabs", "viewing", "app", "exporting", "desktop", "related", "topics"],"aliases":["debug-logs", "logcat", "app-logs", "bug-report"],"charCount":3131}, {"id":"desktop","title":"Desktop App","section":"user","locale":"fr-rFR","resourcePath":"docs/fr-rFR/user/desktop.html","navOrder":14,"keywords":["desktop", "app", "installation", "linux", "macos", "windows", "connecting", "your", "radio", "usb", "serial", "primary", "tcp", "bluetooth", "ble", "feature", "parity", "differences", "keyboard", "shortcuts", "window", "system", "tray", "notification", "preferences", "built", "documentation", "browser", "building", "from"],"aliases":["desktop", "linux", "macos", "windows", "jvm"],"charCount":9955}, - {"id":"discovery","title":"Découverte de maille locale","section":"user","locale":"fr-rFR","resourcePath":"docs/fr-rFR/user/discovery.html","navOrder":12,"keywords":["couverte", "maille", "locale", "local", "mesh", "discovery", "scanner", "setting", "scan", "live", "progress", "reading", "the", "results", "beacon", "manual", "exploration", "traceroute", "informations", "sur", "les", "voisins", "node", "list", "tool", "tips", "for", "related", "topics"],"aliases":["discovery", "local-mesh-discovery", "mesh-discovery", "local-discovery", "network-scan", "traceroute", "neighbor-info"],"charCount":18363}, + {"id":"discovery","title":"Découverte de maille locale","section":"user","locale":"fr-rFR","resourcePath":"docs/fr-rFR/user/discovery.html","navOrder":12,"keywords":["couverte", "maille", "locale", "local", "mesh", "discovery", "scanner", "setting", "scan", "live", "progress", "reading", "the", "results", "beacon", "manual", "exploration", "traceroute", "informations", "sur", "les", "voisins", "node", "list", "tool", "tips", "for", "related", "topics"],"aliases":["discovery", "local-mesh-discovery", "mesh-discovery", "local-discovery", "network-scan", "traceroute", "neighbor-info"],"charCount":18353}, {"id":"firmware","title":"Firmware Updates","section":"user","locale":"fr-rFR","resourcePath":"docs/fr-rFR/user/firmware.html","navOrder":13,"keywords":["firmware", "updates", "checking", "for", "update", "methods", "ota", "over", "the", "air", "via", "bluetooth", "network", "connected", "esp32", "app", "usb", "factory", "erase", "and", "bootloader", "upgrade", "other", "flashing", "options", "version", "channels", "pre", "checklist", "post"],"aliases":["firmware", "update", "ota", "flash"],"charCount":11111}, {"id":"help-and-docs","title":"Help & In-App Docs","section":"user","locale":"fr-rFR","resourcePath":"docs/fr-rFR/user/help-and-docs.html","navOrder":21,"keywords":["help", "app", "docs", "browsing", "search", "chirpy", "the", "assistant", "related", "topics"],"aliases":["help", "docs-browser", "chirpy", "assistant"],"charCount":2318}, {"id":"map-and-waypoints","title":"Map & Waypoints","section":"user","locale":"fr-rFR","resourcePath":"docs/fr-rFR/user/map-and-waypoints.html","navOrder":6,"keywords":["map", "waypoints", "view", "node", "markers", "controls", "filtering", "the", "creating", "waypoint", "properties", "expiration", "geofences", "managing", "couches", "cartographiques", "site", "planner", "position", "sharing", "enabling", "privacy", "considerations", "sources", "adding", "your", "own", "tile", "source", "offline"],"aliases":["map", "waypoints", "gps", "location", "site-planner", "map-layers", "geojson", "kml"],"charCount":14905}, {"id":"messages-and-channels","title":"Messages & Channels","section":"user","locale":"fr-rFR","resourcePath":"docs/fr-rFR/user/messages-and-channels.html","navOrder":3,"keywords":["messages", "channels", "canaux", "default", "channel", "curit", "canal", "adding", "archived", "directs", "sending", "direct", "message", "managing", "the", "conversation", "list", "bubbles", "states", "delivery", "errors", "features", "quick", "chat", "searching", "text", "formatting", "mentions", "reactions", "replying"],"aliases":["channels", "direct-messages", "messaging", "conversations"],"charCount":23868}, - {"id":"mqtt","title":"MQTT","section":"user","locale":"fr-rFR","resourcePath":"docs/fr-rFR/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "configuration", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12415}, + {"id":"mqtt","title":"MQTT","section":"user","locale":"fr-rFR","resourcePath":"docs/fr-rFR/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "configuration", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12403}, {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"fr-rFR","resourcePath":"docs/fr-rFR/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "triques", "appareil", "environnement", "air", "quality", "qualit", "signal", "reference", "alimentation", "traceroute", "reading", "results", "journal", "des", "positions", "informations", "sur", "les", "voisins", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12683}, {"id":"nodes","title":"Nœuds","section":"user","locale":"fr-rFR","resourcePath":"docs/fr-rFR/user/nodes.html","navOrder":4,"keywords":["uds", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "security", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "nodes", "not", "heard", "your", "current", "settings", "sort", "options"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":23310}, {"id":"onboarding","title":"Getting Started","section":"user","locale":"fr-rFR","resourcePath":"docs/fr-rFR/user/onboarding.html","navOrder":1,"keywords":["getting", "started", "first", "launch", "welcome", "screen", "permissions", "bluetooth", "permission", "location", "notifications", "critical", "alerts", "reviewing", "later", "after", "setup", "related", "topics"],"aliases":["first-launch", "setup", "intro"],"charCount":8571}, - {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"fr-rFR","resourcePath":"docs/fr-rFR/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "glages", "module", "mqtt", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon", "tak"],"aliases":["modules", "module-config", "administration"],"charCount":34509}, + {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"fr-rFR","resourcePath":"docs/fr-rFR/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "glages", "module", "mqtt", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon", "tak"],"aliases":["modules", "module-config", "administration"],"charCount":33917}, {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"fr-rFR","resourcePath":"docs/fr-rFR/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "param", "tres", "utilisateur", "profile", "applying", "changes", "configuration", "appareil", "lora", "modem", "presets", "cran", "position", "alimentation", "seau", "bluetooth", "curit", "related", "topics"],"aliases":["paramètres", "radio-config", "user-config", "lora"],"charCount":43385}, {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"fr-rFR","resourcePath":"docs/fr-rFR/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5251}, {"id":"tak","title":"TAK Integration","section":"user","locale":"fr-rFR","resourcePath":"docs/fr-rFR/user/tak.html","navOrder":10,"keywords":["tak", "integration", "overview", "setup", "prerequisites", "configuration", "local", "server", "roles", "cot", "cursor", "target", "format", "wire", "usage", "with", "atak", "troubleshooting", "security", "considerations", "related", "topics"],"aliases":["tak", "atak", "team-awareness-kit"],"charCount":10737}, @@ -287,17 +287,17 @@ {"id":"connections","title":"Connections","section":"user","locale":"ga-rIE","resourcePath":"docs/ga-rIE/user/connections.html","navOrder":2,"keywords":["connections", "bluetooth", "ble", "pairing", "radio", "connection", "status", "troubleshooting", "usb", "serial", "setup", "tcp", "network", "connecting", "over", "the", "when", "use", "provisioning", "for", "mpwrd", "after", "your", "first", "reconnection", "behavior", "desktop", "related", "topics"],"aliases":["bluetooth", "usb", "tcp", "pairing"],"charCount":11108}, {"id":"debug-logs","title":"Debug Logs","section":"user","locale":"ga-rIE","resourcePath":"docs/ga-rIE/user/debug-logs.html","navOrder":22,"keywords":["debug", "logs", "the", "two", "tabs", "viewing", "app", "exporting", "desktop", "related", "topics"],"aliases":["debug-logs", "logcat", "app-logs", "bug-report"],"charCount":3119}, {"id":"desktop","title":"Desktop App","section":"user","locale":"ga-rIE","resourcePath":"docs/ga-rIE/user/desktop.html","navOrder":14,"keywords":["desktop", "app", "installation", "linux", "macos", "windows", "connecting", "your", "radio", "usb", "serial", "primary", "tcp", "bluetooth", "ble", "feature", "parity", "differences", "keyboard", "shortcuts", "window", "system", "tray", "notification", "preferences", "built", "documentation", "browser", "building", "from"],"aliases":["desktop", "linux", "macos", "windows", "jvm"],"charCount":9955}, - {"id":"discovery","title":"Local Mesh Discovery","section":"user","locale":"ga-rIE","resourcePath":"docs/ga-rIE/user/discovery.html","navOrder":12,"keywords":["local", "mesh", "discovery", "scanner", "setting", "scan", "live", "progress", "reading", "the", "results", "beacon", "manual", "exploration", "rianad", "ireachta", "neighbor", "info", "node", "list", "tool", "tips", "for", "related", "topics"],"aliases":["discovery", "local-mesh-discovery", "mesh-discovery", "local-discovery", "network-scan", "traceroute", "neighbor-info"],"charCount":18344}, + {"id":"discovery","title":"Local Mesh Discovery","section":"user","locale":"ga-rIE","resourcePath":"docs/ga-rIE/user/discovery.html","navOrder":12,"keywords":["local", "mesh", "discovery", "scanner", "setting", "scan", "live", "progress", "reading", "the", "results", "beacon", "manual", "exploration", "rianad", "ireachta", "neighbor", "info", "node", "list", "tool", "tips", "for", "related", "topics"],"aliases":["discovery", "local-mesh-discovery", "mesh-discovery", "local-discovery", "network-scan", "traceroute", "neighbor-info"],"charCount":18334}, {"id":"firmware","title":"Firmware Updates","section":"user","locale":"ga-rIE","resourcePath":"docs/ga-rIE/user/firmware.html","navOrder":13,"keywords":["firmware", "updates", "checking", "for", "update", "methods", "ota", "over", "the", "air", "via", "bluetooth", "network", "connected", "esp32", "app", "usb", "factory", "erase", "and", "bootloader", "upgrade", "other", "flashing", "options", "version", "channels", "pre", "checklist", "post"],"aliases":["firmware", "update", "ota", "flash"],"charCount":11096}, {"id":"help-and-docs","title":"Help & In-App Docs","section":"user","locale":"ga-rIE","resourcePath":"docs/ga-rIE/user/help-and-docs.html","navOrder":21,"keywords":["help", "app", "docs", "browsing", "search", "chirpy", "the", "assistant", "related", "topics"],"aliases":["help", "docs-browser", "chirpy", "assistant"],"charCount":2306}, {"id":"map-and-waypoints","title":"Map & Waypoints","section":"user","locale":"ga-rIE","resourcePath":"docs/ga-rIE/user/map-and-waypoints.html","navOrder":6,"keywords":["map", "waypoints", "view", "node", "markers", "controls", "filtering", "the", "creating", "waypoint", "properties", "expiration", "geofences", "managing", "layers", "site", "planner", "position", "sharing", "enabling", "privacy", "considerations", "sources", "adding", "your", "own", "tile", "source", "offline", "terrain"],"aliases":["map", "waypoints", "gps", "location", "site-planner", "map-layers", "geojson", "kml"],"charCount":14884}, {"id":"messages-and-channels","title":"Messages & Channels","section":"user","locale":"ga-rIE","resourcePath":"docs/ga-rIE/user/messages-and-channels.html","navOrder":3,"keywords":["messages", "channels", "default", "channel", "security", "adding", "archived", "direct", "sending", "message", "managing", "the", "conversation", "list", "bubbles", "states", "delivery", "errors", "features", "quick", "chat", "searching", "text", "formatting", "mentions", "reactions", "replying", "day", "separators", "jump"],"aliases":["channels", "direct-messages", "messaging", "conversations"],"charCount":23868}, - {"id":"mqtt","title":"MQTT","section":"user","locale":"ga-rIE","resourcePath":"docs/ga-rIE/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "configuration", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12415}, + {"id":"mqtt","title":"MQTT","section":"user","locale":"ga-rIE","resourcePath":"docs/ga-rIE/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "configuration", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12403}, {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"ga-rIE","resourcePath":"docs/ga-rIE/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "device", "environment", "air", "quality", "ocht", "gneal", "signal", "reference", "power", "rianad", "ireachta", "reading", "traceroute", "results", "seirbh", "neighbor", "info", "host", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12615}, {"id":"nodes","title":"Nodes","section":"user","locale":"ga-rIE","resourcePath":"docs/ga-rIE/user/nodes.html","navOrder":4,"keywords":["nodes", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "security", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "not", "heard", "your", "current", "settings", "sort", "options", "per"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":23268}, {"id":"onboarding","title":"Getting Started","section":"user","locale":"ga-rIE","resourcePath":"docs/ga-rIE/user/onboarding.html","navOrder":1,"keywords":["getting", "started", "first", "launch", "welcome", "screen", "permissions", "bluetooth", "permission", "location", "notifications", "critical", "alerts", "reviewing", "later", "after", "setup", "related", "topics"],"aliases":["first-launch", "setup", "intro"],"charCount":8461}, - {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"ga-rIE","resourcePath":"docs/ga-rIE/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "cumra", "ocht", "dule", "mqtt", "module", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh"],"aliases":["modules", "module-config", "administration"],"charCount":33413}, - {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"ga-rIE","resourcePath":"docs/ga-rIE/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "configuration", "device", "config", "lora", "modem", "presets", "display", "position", "power", "network", "bluetooth", "security", "related", "topics"],"aliases":["settings", "radio-config", "user-config", "lora"],"charCount":41641}, + {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"ga-rIE","resourcePath":"docs/ga-rIE/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "cumra", "ocht", "dule", "mqtt", "module", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh"],"aliases":["modules", "module-config", "administration"],"charCount":33067}, + {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"ga-rIE","resourcePath":"docs/ga-rIE/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "configuration", "device", "config", "lora", "modem", "presets", "display", "position", "power", "network", "bluetooth", "security", "related", "topics"],"aliases":["settings", "radio-config", "user-config", "lora"],"charCount":42001}, {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"ga-rIE","resourcePath":"docs/ga-rIE/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5299}, {"id":"tak","title":"TAK Integration","section":"user","locale":"ga-rIE","resourcePath":"docs/ga-rIE/user/tak.html","navOrder":10,"keywords":["tak", "integration", "overview", "setup", "prerequisites", "configuration", "local", "server", "roles", "cot", "cursor", "target", "format", "wire", "usage", "with", "atak", "troubleshooting", "security", "considerations", "related", "topics"],"aliases":["tak", "atak", "team-awareness-kit"],"charCount":10705}, {"id":"telemetry-and-sensors","title":"Telemetry and sensors","section":"user","locale":"ga-rIE","resourcePath":"docs/ga-rIE/user/telemetry-and-sensors.html","navOrder":999,"keywords":["telemetry", "and", "sensors", "device", "environment", "temperature", "humidity", "air", "quality", "soil", "light", "weather", "other", "readings", "power", "metrics", "configuring", "choosing", "interval", "viewing", "troubleshooting", "related", "topics"],"aliases":[],"charCount":12241}, @@ -308,17 +308,17 @@ {"id":"connections","title":"Connections","section":"user","locale":"gl-rES","resourcePath":"docs/gl-rES/user/connections.html","navOrder":2,"keywords":["connections", "bluetooth", "ble", "pairing", "radio", "connection", "status", "troubleshooting", "usb", "serial", "setup", "tcp", "network", "connecting", "over", "the", "when", "use", "provisioning", "for", "mpwrd", "after", "your", "first", "reconnection", "behavior", "desktop", "related", "topics"],"aliases":["bluetooth", "usb", "tcp", "pairing"],"charCount":11120}, {"id":"debug-logs","title":"Debug Logs","section":"user","locale":"gl-rES","resourcePath":"docs/gl-rES/user/debug-logs.html","navOrder":22,"keywords":["debug", "logs", "the", "two", "tabs", "viewing", "app", "exporting", "desktop", "related", "topics"],"aliases":["debug-logs", "logcat", "app-logs", "bug-report"],"charCount":3119}, {"id":"desktop","title":"Desktop App","section":"user","locale":"gl-rES","resourcePath":"docs/gl-rES/user/desktop.html","navOrder":14,"keywords":["desktop", "app", "installation", "linux", "macos", "windows", "connecting", "your", "radio", "usb", "serial", "primary", "tcp", "bluetooth", "ble", "feature", "parity", "differences", "keyboard", "shortcuts", "window", "system", "tray", "notification", "preferences", "built", "documentation", "browser", "building", "from"],"aliases":["desktop", "linux", "macos", "windows", "jvm"],"charCount":9955}, - {"id":"discovery","title":"Local Mesh Discovery","section":"user","locale":"gl-rES","resourcePath":"docs/gl-rES/user/discovery.html","navOrder":12,"keywords":["local", "mesh", "discovery", "scanner", "setting", "scan", "live", "progress", "reading", "the", "results", "beacon", "manual", "exploration", "traza", "ruta", "neighbor", "info", "node", "list", "tool", "tips", "for", "related", "topics"],"aliases":["discovery", "local-mesh-discovery", "mesh-discovery", "local-discovery", "network-scan", "traceroute", "neighbor-info"],"charCount":18334}, + {"id":"discovery","title":"Local Mesh Discovery","section":"user","locale":"gl-rES","resourcePath":"docs/gl-rES/user/discovery.html","navOrder":12,"keywords":["local", "mesh", "discovery", "scanner", "setting", "scan", "live", "progress", "reading", "the", "results", "beacon", "manual", "exploration", "traza", "ruta", "neighbor", "info", "node", "list", "tool", "tips", "for", "related", "topics"],"aliases":["discovery", "local-mesh-discovery", "mesh-discovery", "local-discovery", "network-scan", "traceroute", "neighbor-info"],"charCount":18324}, {"id":"firmware","title":"Firmware Updates","section":"user","locale":"gl-rES","resourcePath":"docs/gl-rES/user/firmware.html","navOrder":13,"keywords":["firmware", "updates", "checking", "for", "update", "methods", "ota", "over", "the", "air", "via", "bluetooth", "network", "connected", "esp32", "app", "usb", "factory", "erase", "and", "bootloader", "upgrade", "other", "flashing", "options", "version", "channels", "pre", "checklist", "post"],"aliases":["firmware", "update", "ota", "flash"],"charCount":11096}, {"id":"help-and-docs","title":"Help & In-App Docs","section":"user","locale":"gl-rES","resourcePath":"docs/gl-rES/user/help-and-docs.html","navOrder":21,"keywords":["help", "app", "docs", "browsing", "search", "chirpy", "the", "assistant", "related", "topics"],"aliases":["help", "docs-browser", "chirpy", "assistant"],"charCount":2306}, {"id":"map-and-waypoints","title":"Map & Waypoints","section":"user","locale":"gl-rES","resourcePath":"docs/gl-rES/user/map-and-waypoints.html","navOrder":6,"keywords":["map", "waypoints", "view", "node", "markers", "controls", "filtering", "the", "creating", "waypoint", "properties", "expiration", "geofences", "managing", "layers", "site", "planner", "position", "sharing", "enabling", "privacy", "considerations", "sources", "adding", "your", "own", "tile", "source", "offline", "terrain"],"aliases":["map", "waypoints", "gps", "location", "site-planner", "map-layers", "geojson", "kml"],"charCount":14884}, {"id":"messages-and-channels","title":"Messages & Channels","section":"user","locale":"gl-rES","resourcePath":"docs/gl-rES/user/messages-and-channels.html","navOrder":3,"keywords":["messages", "channels", "default", "channel", "security", "adding", "archived", "direct", "sending", "message", "managing", "the", "conversation", "list", "bubbles", "states", "delivery", "errors", "features", "quick", "chat", "searching", "text", "formatting", "mentions", "reactions", "replying", "day", "separators", "jump"],"aliases":["channels", "direct-messages", "messaging", "conversations"],"charCount":23868}, - {"id":"mqtt","title":"MQTT","section":"user","locale":"gl-rES","resourcePath":"docs/gl-rES/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "configuration", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12415}, + {"id":"mqtt","title":"MQTT","section":"user","locale":"gl-rES","resourcePath":"docs/gl-rES/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "configuration", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12403}, {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"gl-rES","resourcePath":"docs/gl-rES/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "device", "environment", "air", "quality", "signal", "reference", "power", "traza", "ruta", "reading", "traceroute", "results", "position", "log", "neighbor", "info", "host", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12542}, {"id":"nodes","title":"Nodes","section":"user","locale":"gl-rES","resourcePath":"docs/gl-rES/user/nodes.html","navOrder":4,"keywords":["nodes", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "security", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "not", "heard", "your", "current", "settings", "sort", "options", "per"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":23251}, {"id":"onboarding","title":"Getting Started","section":"user","locale":"gl-rES","resourcePath":"docs/gl-rES/user/onboarding.html","navOrder":1,"keywords":["getting", "started", "first", "launch", "welcome", "screen", "permissions", "bluetooth", "permission", "location", "notifications", "critical", "alerts", "reviewing", "later", "after", "setup", "related", "topics"],"aliases":["first-launch", "setup", "intro"],"charCount":8461}, - {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"gl-rES","resourcePath":"docs/gl-rES/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "configuraci", "dulo", "mqtt", "module", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon"],"aliases":["modules", "module-config", "administration"],"charCount":33440}, - {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"gl-rES","resourcePath":"docs/gl-rES/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "configuration", "device", "config", "lora", "modem", "presets", "display", "position", "power", "network", "bluetooth", "security", "related", "topics"],"aliases":["settings", "radio-config", "user-config", "lora"],"charCount":41641}, + {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"gl-rES","resourcePath":"docs/gl-rES/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "configuraci", "dulo", "mqtt", "module", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon"],"aliases":["modules", "module-config", "administration"],"charCount":33094}, + {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"gl-rES","resourcePath":"docs/gl-rES/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "configuration", "device", "config", "lora", "modem", "presets", "display", "position", "power", "network", "bluetooth", "security", "related", "topics"],"aliases":["settings", "radio-config", "user-config", "lora"],"charCount":42001}, {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"gl-rES","resourcePath":"docs/gl-rES/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5233}, {"id":"tak","title":"TAK Integration","section":"user","locale":"gl-rES","resourcePath":"docs/gl-rES/user/tak.html","navOrder":10,"keywords":["tak", "integration", "overview", "setup", "prerequisites", "configuration", "local", "server", "roles", "cot", "cursor", "target", "format", "wire", "usage", "with", "atak", "troubleshooting", "security", "considerations", "related", "topics"],"aliases":["tak", "atak", "team-awareness-kit"],"charCount":10705}, {"id":"telemetry-and-sensors","title":"Telemetry and sensors","section":"user","locale":"gl-rES","resourcePath":"docs/gl-rES/user/telemetry-and-sensors.html","navOrder":999,"keywords":["telemetry", "and", "sensors", "device", "environment", "temperature", "humidity", "air", "quality", "soil", "light", "weather", "other", "readings", "power", "metrics", "configuring", "choosing", "interval", "viewing", "troubleshooting", "related", "topics"],"aliases":[],"charCount":12297}, @@ -329,17 +329,17 @@ {"id":"connections","title":"Connections","section":"user","locale":"hr-rHR","resourcePath":"docs/hr-rHR/user/connections.html","navOrder":2,"keywords":["connections", "bluetooth", "ble", "pairing", "radio", "connection", "status", "troubleshooting", "usb", "serial", "setup", "tcp", "network", "connecting", "over", "the", "when", "use", "provisioning", "for", "mpwrd", "after", "your", "first", "reconnection", "behavior", "desktop", "related", "topics"],"aliases":["bluetooth", "usb", "tcp", "pairing"],"charCount":11168}, {"id":"debug-logs","title":"Debug Logs","section":"user","locale":"hr-rHR","resourcePath":"docs/hr-rHR/user/debug-logs.html","navOrder":22,"keywords":["debug", "logs", "the", "two", "tabs", "viewing", "app", "exporting", "desktop", "related", "topics"],"aliases":["debug-logs", "logcat", "app-logs", "bug-report"],"charCount":3119}, {"id":"desktop","title":"Desktop App","section":"user","locale":"hr-rHR","resourcePath":"docs/hr-rHR/user/desktop.html","navOrder":14,"keywords":["desktop", "app", "installation", "linux", "macos", "windows", "connecting", "your", "radio", "usb", "serial", "primary", "tcp", "bluetooth", "ble", "feature", "parity", "differences", "keyboard", "shortcuts", "window", "system", "tray", "notification", "preferences", "built", "documentation", "browser", "building", "from"],"aliases":["desktop", "linux", "macos", "windows", "jvm"],"charCount":9955}, - {"id":"discovery","title":"Local Mesh Discovery","section":"user","locale":"hr-rHR","resourcePath":"docs/hr-rHR/user/discovery.html","navOrder":12,"keywords":["local", "mesh", "discovery", "scanner", "setting", "scan", "live", "progress", "reading", "the", "results", "beacon", "manual", "exploration", "traceroute", "neighbor", "info", "node", "list", "tool", "tips", "for", "related", "topics"],"aliases":["discovery", "local-mesh-discovery", "mesh-discovery", "local-discovery", "network-scan", "traceroute", "neighbor-info"],"charCount":18334}, + {"id":"discovery","title":"Local Mesh Discovery","section":"user","locale":"hr-rHR","resourcePath":"docs/hr-rHR/user/discovery.html","navOrder":12,"keywords":["local", "mesh", "discovery", "scanner", "setting", "scan", "live", "progress", "reading", "the", "results", "beacon", "manual", "exploration", "traceroute", "neighbor", "info", "node", "list", "tool", "tips", "for", "related", "topics"],"aliases":["discovery", "local-mesh-discovery", "mesh-discovery", "local-discovery", "network-scan", "traceroute", "neighbor-info"],"charCount":18324}, {"id":"firmware","title":"Firmware Updates","section":"user","locale":"hr-rHR","resourcePath":"docs/hr-rHR/user/firmware.html","navOrder":13,"keywords":["firmware", "updates", "checking", "for", "update", "methods", "ota", "over", "the", "air", "via", "bluetooth", "network", "connected", "esp32", "app", "usb", "factory", "erase", "and", "bootloader", "upgrade", "other", "flashing", "options", "version", "channels", "pre", "checklist", "post"],"aliases":["firmware", "update", "ota", "flash"],"charCount":11096}, {"id":"help-and-docs","title":"Help & In-App Docs","section":"user","locale":"hr-rHR","resourcePath":"docs/hr-rHR/user/help-and-docs.html","navOrder":21,"keywords":["help", "app", "docs", "browsing", "search", "chirpy", "the", "assistant", "related", "topics"],"aliases":["help", "docs-browser", "chirpy", "assistant"],"charCount":2306}, {"id":"map-and-waypoints","title":"Map & Waypoints","section":"user","locale":"hr-rHR","resourcePath":"docs/hr-rHR/user/map-and-waypoints.html","navOrder":6,"keywords":["map", "waypoints", "view", "node", "markers", "controls", "filtering", "the", "creating", "waypoint", "properties", "expiration", "geofences", "managing", "layers", "site", "planner", "position", "sharing", "enabling", "privacy", "considerations", "sources", "adding", "your", "own", "tile", "source", "offline", "terrain"],"aliases":["map", "waypoints", "gps", "location", "site-planner", "map-layers", "geojson", "kml"],"charCount":14884}, {"id":"messages-and-channels","title":"Messages & Channels","section":"user","locale":"hr-rHR","resourcePath":"docs/hr-rHR/user/messages-and-channels.html","navOrder":3,"keywords":["messages", "channels", "default", "channel", "security", "adding", "archived", "direct", "sending", "message", "managing", "the", "conversation", "list", "bubbles", "states", "delivery", "errors", "features", "quick", "chat", "searching", "text", "formatting", "mentions", "reactions", "replying", "day", "separators", "jump"],"aliases":["channels", "direct-messages", "messaging", "conversations"],"charCount":23868}, - {"id":"mqtt","title":"MQTT","section":"user","locale":"hr-rHR","resourcePath":"docs/hr-rHR/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "configuration", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12415}, + {"id":"mqtt","title":"MQTT","section":"user","locale":"hr-rHR","resourcePath":"docs/hr-rHR/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "configuration", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12403}, {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"hr-rHR","resourcePath":"docs/hr-rHR/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "device", "environment", "air", "quality", "signal", "reference", "power", "traceroute", "reading", "results", "position", "log", "neighbor", "info", "host", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12542}, {"id":"nodes","title":"Nodes","section":"user","locale":"hr-rHR","resourcePath":"docs/hr-rHR/user/nodes.html","navOrder":4,"keywords":["nodes", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "security", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "not", "heard", "your", "current", "settings", "sort", "options", "per"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":23249}, {"id":"onboarding","title":"Getting Started","section":"user","locale":"hr-rHR","resourcePath":"docs/hr-rHR/user/onboarding.html","navOrder":1,"keywords":["getting", "started", "first", "launch", "welcome", "screen", "permissions", "bluetooth", "permission", "location", "notifications", "critical", "alerts", "reviewing", "later", "after", "setup", "related", "topics"],"aliases":["first-launch", "setup", "intro"],"charCount":8461}, - {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"hr-rHR","resourcePath":"docs/hr-rHR/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "konfiguracija", "modula", "mqtt", "module", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon"],"aliases":["modules", "module-config", "administration"],"charCount":33468}, - {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"hr-rHR","resourcePath":"docs/hr-rHR/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "configuration", "device", "config", "lora", "modem", "presets", "display", "position", "power", "network", "postavke", "bluetootha", "security", "related", "topics"],"aliases":["settings", "radio-config", "user-config", "lora"],"charCount":41644}, + {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"hr-rHR","resourcePath":"docs/hr-rHR/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "konfiguracija", "modula", "mqtt", "module", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon"],"aliases":["modules", "module-config", "administration"],"charCount":33122}, + {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"hr-rHR","resourcePath":"docs/hr-rHR/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "configuration", "device", "config", "lora", "modem", "presets", "display", "position", "power", "network", "postavke", "bluetootha", "security", "related", "topics"],"aliases":["settings", "radio-config", "user-config", "lora"],"charCount":42004}, {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"hr-rHR","resourcePath":"docs/hr-rHR/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5233}, {"id":"tak","title":"TAK Integration","section":"user","locale":"hr-rHR","resourcePath":"docs/hr-rHR/user/tak.html","navOrder":10,"keywords":["tak", "integration", "overview", "setup", "prerequisites", "configuration", "local", "server", "roles", "cot", "cursor", "target", "format", "wire", "usage", "with", "atak", "troubleshooting", "security", "considerations", "related", "topics"],"aliases":["tak", "atak", "team-awareness-kit"],"charCount":10705}, {"id":"telemetry-and-sensors","title":"Telemetry and sensors","section":"user","locale":"hr-rHR","resourcePath":"docs/hr-rHR/user/telemetry-and-sensors.html","navOrder":999,"keywords":["telemetry", "and", "sensors", "device", "environment", "temperature", "humidity", "air", "quality", "soil", "light", "weather", "other", "readings", "power", "metrics", "configuring", "choosing", "interval", "viewing", "troubleshooting", "related", "topics"],"aliases":[],"charCount":12297}, @@ -350,17 +350,17 @@ {"id":"connections","title":"Connections","section":"user","locale":"ht-rHT","resourcePath":"docs/ht-rHT/user/connections.html","navOrder":2,"keywords":["connections", "bluetooth", "ble", "pairing", "radio", "connection", "status", "troubleshooting", "usb", "serial", "setup", "tcp", "network", "connecting", "over", "the", "when", "use", "provisioning", "for", "mpwrd", "after", "your", "first", "reconnection", "behavior", "desktop", "related", "topics"],"aliases":["bluetooth", "usb", "tcp", "pairing"],"charCount":11084}, {"id":"debug-logs","title":"Debug Logs","section":"user","locale":"ht-rHT","resourcePath":"docs/ht-rHT/user/debug-logs.html","navOrder":22,"keywords":["debug", "logs", "the", "two", "tabs", "viewing", "app", "exporting", "desktop", "related", "topics"],"aliases":["debug-logs", "logcat", "app-logs", "bug-report"],"charCount":3119}, {"id":"desktop","title":"Desktop App","section":"user","locale":"ht-rHT","resourcePath":"docs/ht-rHT/user/desktop.html","navOrder":14,"keywords":["desktop", "app", "installation", "linux", "macos", "windows", "connecting", "your", "radio", "usb", "serial", "primary", "tcp", "bluetooth", "ble", "feature", "parity", "differences", "keyboard", "shortcuts", "window", "system", "tray", "notification", "preferences", "built", "documentation", "browser", "building", "from"],"aliases":["desktop", "linux", "macos", "windows", "jvm"],"charCount":9955}, - {"id":"discovery","title":"Local Mesh Discovery","section":"user","locale":"ht-rHT","resourcePath":"docs/ht-rHT/user/discovery.html","navOrder":12,"keywords":["local", "mesh", "discovery", "scanner", "setting", "scan", "live", "progress", "reading", "the", "results", "beacon", "manual", "exploration", "traceroute", "neighbor", "info", "node", "list", "tool", "tips", "for", "related", "topics"],"aliases":["discovery", "local-mesh-discovery", "mesh-discovery", "local-discovery", "network-scan", "traceroute", "neighbor-info"],"charCount":18334}, + {"id":"discovery","title":"Local Mesh Discovery","section":"user","locale":"ht-rHT","resourcePath":"docs/ht-rHT/user/discovery.html","navOrder":12,"keywords":["local", "mesh", "discovery", "scanner", "setting", "scan", "live", "progress", "reading", "the", "results", "beacon", "manual", "exploration", "traceroute", "neighbor", "info", "node", "list", "tool", "tips", "for", "related", "topics"],"aliases":["discovery", "local-mesh-discovery", "mesh-discovery", "local-discovery", "network-scan", "traceroute", "neighbor-info"],"charCount":18324}, {"id":"firmware","title":"Firmware Updates","section":"user","locale":"ht-rHT","resourcePath":"docs/ht-rHT/user/firmware.html","navOrder":13,"keywords":["firmware", "updates", "checking", "for", "update", "methods", "ota", "over", "the", "air", "via", "bluetooth", "network", "connected", "esp32", "app", "usb", "factory", "erase", "and", "bootloader", "upgrade", "other", "flashing", "options", "version", "channels", "pre", "checklist", "post"],"aliases":["firmware", "update", "ota", "flash"],"charCount":11096}, {"id":"help-and-docs","title":"Help & In-App Docs","section":"user","locale":"ht-rHT","resourcePath":"docs/ht-rHT/user/help-and-docs.html","navOrder":21,"keywords":["help", "app", "docs", "browsing", "search", "chirpy", "the", "assistant", "related", "topics"],"aliases":["help", "docs-browser", "chirpy", "assistant"],"charCount":2306}, {"id":"map-and-waypoints","title":"Map & Waypoints","section":"user","locale":"ht-rHT","resourcePath":"docs/ht-rHT/user/map-and-waypoints.html","navOrder":6,"keywords":["map", "waypoints", "view", "node", "markers", "controls", "filtering", "the", "creating", "waypoint", "properties", "expiration", "geofences", "managing", "layers", "site", "planner", "position", "sharing", "enabling", "privacy", "considerations", "sources", "adding", "your", "own", "tile", "source", "offline", "terrain"],"aliases":["map", "waypoints", "gps", "location", "site-planner", "map-layers", "geojson", "kml"],"charCount":14892}, {"id":"messages-and-channels","title":"Messages & Channels","section":"user","locale":"ht-rHT","resourcePath":"docs/ht-rHT/user/messages-and-channels.html","navOrder":3,"keywords":["messages", "channels", "default", "channel", "security", "adding", "archived", "direct", "sending", "message", "managing", "the", "conversation", "list", "bubbles", "states", "delivery", "errors", "features", "quick", "chat", "searching", "text", "formatting", "mentions", "reactions", "replying", "day", "separators", "jump"],"aliases":["channels", "direct-messages", "messaging", "conversations"],"charCount":23868}, - {"id":"mqtt","title":"MQTT","section":"user","locale":"ht-rHT","resourcePath":"docs/ht-rHT/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "configuration", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12415}, + {"id":"mqtt","title":"MQTT","section":"user","locale":"ht-rHT","resourcePath":"docs/ht-rHT/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "configuration", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12403}, {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"ht-rHT","resourcePath":"docs/ht-rHT/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "device", "environment", "air", "quality", "kalite", "siynal", "signal", "reference", "power", "traceroute", "reading", "results", "jounal", "pozisyon", "neighbor", "info", "host", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12544}, {"id":"nodes","title":"Nodes","section":"user","locale":"ht-rHT","resourcePath":"docs/ht-rHT/user/nodes.html","navOrder":4,"keywords":["nodes", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "security", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "not", "heard", "your", "current", "settings", "sort", "options", "per"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":23277}, {"id":"onboarding","title":"Getting Started","section":"user","locale":"ht-rHT","resourcePath":"docs/ht-rHT/user/onboarding.html","navOrder":1,"keywords":["getting", "started", "first", "launch", "welcome", "screen", "permissions", "bluetooth", "permission", "location", "notifications", "critical", "alerts", "reviewing", "later", "after", "setup", "related", "topics"],"aliases":["first-launch", "setup", "intro"],"charCount":8461}, - {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"ht-rHT","resourcePath":"docs/ht-rHT/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "konfigirasyon", "modil", "mqtt", "module", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon"],"aliases":["modules", "module-config", "administration"],"charCount":33387}, - {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"ht-rHT","resourcePath":"docs/ht-rHT/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "configuration", "device", "config", "lora", "modem", "presets", "display", "position", "power", "network", "bluetooth", "security", "related", "topics"],"aliases":["settings", "radio-config", "user-config", "lora"],"charCount":41641}, + {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"ht-rHT","resourcePath":"docs/ht-rHT/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "konfigirasyon", "modil", "mqtt", "module", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon"],"aliases":["modules", "module-config", "administration"],"charCount":33041}, + {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"ht-rHT","resourcePath":"docs/ht-rHT/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "configuration", "device", "config", "lora", "modem", "presets", "display", "position", "power", "network", "bluetooth", "security", "related", "topics"],"aliases":["settings", "radio-config", "user-config", "lora"],"charCount":42001}, {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"ht-rHT","resourcePath":"docs/ht-rHT/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5239}, {"id":"tak","title":"TAK Integration","section":"user","locale":"ht-rHT","resourcePath":"docs/ht-rHT/user/tak.html","navOrder":10,"keywords":["tak", "integration", "overview", "setup", "prerequisites", "configuration", "local", "server", "roles", "cot", "cursor", "target", "format", "wire", "usage", "with", "atak", "troubleshooting", "security", "considerations", "related", "topics"],"aliases":["tak", "atak", "team-awareness-kit"],"charCount":10705}, {"id":"telemetry-and-sensors","title":"Telemetry and sensors","section":"user","locale":"ht-rHT","resourcePath":"docs/ht-rHT/user/telemetry-and-sensors.html","navOrder":999,"keywords":["telemetry", "and", "sensors", "device", "environment", "temperature", "humidity", "air", "quality", "soil", "light", "weather", "other", "readings", "power", "metrics", "configuring", "choosing", "interval", "viewing", "troubleshooting", "related", "topics"],"aliases":[],"charCount":12276}, @@ -371,17 +371,17 @@ {"id":"connections","title":"Connections","section":"user","locale":"hu-rHU","resourcePath":"docs/hu-rHU/user/connections.html","navOrder":2,"keywords":["connections", "bluetooth", "ble", "pairing", "radio", "connection", "status", "troubleshooting", "usb", "serial", "setup", "tcp", "network", "connecting", "over", "the", "when", "use", "provisioning", "for", "mpwrd", "after", "your", "first", "reconnection", "behavior", "desktop", "related", "topics"],"aliases":["bluetooth", "usb", "tcp", "pairing"],"charCount":11096}, {"id":"debug-logs","title":"Debug Logs","section":"user","locale":"hu-rHU","resourcePath":"docs/hu-rHU/user/debug-logs.html","navOrder":22,"keywords":["debug", "logs", "the", "two", "tabs", "viewing", "app", "exporting", "desktop", "related", "topics"],"aliases":["debug-logs", "logcat", "app-logs", "bug-report"],"charCount":3119}, {"id":"desktop","title":"Desktop App","section":"user","locale":"hu-rHU","resourcePath":"docs/hu-rHU/user/desktop.html","navOrder":14,"keywords":["desktop", "app", "installation", "linux", "macos", "windows", "connecting", "your", "radio", "usb", "serial", "primary", "tcp", "bluetooth", "ble", "feature", "parity", "differences", "keyboard", "shortcuts", "window", "system", "tray", "notification", "preferences", "built", "documentation", "browser", "building", "from"],"aliases":["desktop", "linux", "macos", "windows", "jvm"],"charCount":9955}, - {"id":"discovery","title":"Local Mesh Discovery","section":"user","locale":"hu-rHU","resourcePath":"docs/hu-rHU/user/discovery.html","navOrder":12,"keywords":["local", "mesh", "discovery", "scanner", "setting", "scan", "live", "progress", "reading", "the", "results", "beacon", "manual", "exploration", "traceroute", "szomsz", "inform", "node", "list", "tool", "tips", "for", "related", "topics"],"aliases":["discovery", "local-mesh-discovery", "mesh-discovery", "local-discovery", "network-scan", "traceroute", "neighbor-info"],"charCount":18340}, + {"id":"discovery","title":"Local Mesh Discovery","section":"user","locale":"hu-rHU","resourcePath":"docs/hu-rHU/user/discovery.html","navOrder":12,"keywords":["local", "mesh", "discovery", "scanner", "setting", "scan", "live", "progress", "reading", "the", "results", "beacon", "manual", "exploration", "traceroute", "szomsz", "inform", "node", "list", "tool", "tips", "for", "related", "topics"],"aliases":["discovery", "local-mesh-discovery", "mesh-discovery", "local-discovery", "network-scan", "traceroute", "neighbor-info"],"charCount":18330}, {"id":"firmware","title":"Firmware Updates","section":"user","locale":"hu-rHU","resourcePath":"docs/hu-rHU/user/firmware.html","navOrder":13,"keywords":["firmware", "updates", "checking", "for", "update", "methods", "ota", "over", "the", "air", "via", "bluetooth", "network", "connected", "esp32", "app", "usb", "factory", "erase", "and", "bootloader", "upgrade", "other", "flashing", "options", "version", "channels", "pre", "checklist", "post"],"aliases":["firmware", "update", "ota", "flash"],"charCount":11096}, {"id":"help-and-docs","title":"Help & In-App Docs","section":"user","locale":"hu-rHU","resourcePath":"docs/hu-rHU/user/help-and-docs.html","navOrder":21,"keywords":["help", "app", "docs", "browsing", "search", "chirpy", "the", "assistant", "related", "topics"],"aliases":["help", "docs-browser", "chirpy", "assistant"],"charCount":2306}, {"id":"map-and-waypoints","title":"Map & Waypoints","section":"user","locale":"hu-rHU","resourcePath":"docs/hu-rHU/user/map-and-waypoints.html","navOrder":6,"keywords":["map", "waypoints", "view", "node", "markers", "controls", "filtering", "the", "creating", "waypoint", "properties", "expiration", "geofences", "managing", "tegek", "site", "planner", "position", "sharing", "enabling", "privacy", "considerations", "sources", "adding", "your", "own", "tile", "source", "offline", "terrain"],"aliases":["map", "waypoints", "gps", "location", "site-planner", "map-layers", "geojson", "kml"],"charCount":14887}, {"id":"messages-and-channels","title":"Messages & Channels","section":"user","locale":"hu-rHU","resourcePath":"docs/hu-rHU/user/messages-and-channels.html","navOrder":3,"keywords":["messages", "channels", "csatorn", "default", "channel", "csatorna", "biztons", "adding", "archived", "direct", "sending", "message", "managing", "the", "conversation", "list", "bubbles", "states", "delivery", "errors", "features", "quick", "chat", "searching", "text", "formatting", "mentions", "reactions", "replying", "day"],"aliases":["channels", "direct-messages", "messaging", "conversations"],"charCount":23871}, - {"id":"mqtt","title":"MQTT","section":"user","locale":"hu-rHU","resourcePath":"docs/hu-rHU/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "configuration", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12415}, + {"id":"mqtt","title":"MQTT","section":"user","locale":"hu-rHU","resourcePath":"docs/hu-rHU/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "configuration", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12403}, {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"hu-rHU","resourcePath":"docs/hu-rHU/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "eszk", "zmetrik", "rnyezeti", "metrik", "air", "quality", "jelmin", "signal", "reference", "pell", "traceroute", "reading", "results", "poz", "napl", "szomsz", "inform", "host", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12579}, {"id":"nodes","title":"Csomópontok","section":"user","locale":"hu-rHU","resourcePath":"docs/hu-rHU/user/nodes.html","navOrder":4,"keywords":["csom", "pontok", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "security", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "nodes", "not", "heard", "your", "current", "settings", "sort"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":23350}, {"id":"onboarding","title":"Getting Started","section":"user","locale":"hu-rHU","resourcePath":"docs/hu-rHU/user/onboarding.html","navOrder":1,"keywords":["getting", "started", "first", "launch", "welcome", "screen", "permissions", "bluetooth", "permission", "location", "notifications", "critical", "alerts", "reviewing", "later", "after", "setup", "related", "topics"],"aliases":["first-launch", "setup", "intro"],"charCount":8566}, - {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"hu-rHU","resourcePath":"docs/hu-rHU/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "modul", "sok", "mqtt", "module", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon"],"aliases":["modules", "module-config", "administration"],"charCount":34306}, - {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"hu-rHU","resourcePath":"docs/hu-rHU/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "configuration", "eszk", "zbe", "sok", "lora", "modem", "presets", "kijelz", "poz", "energia", "zati", "bluetooth", "biztons", "related", "topics"],"aliases":["beállítások", "radio-config", "user-config", "lora"],"charCount":42288}, + {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"hu-rHU","resourcePath":"docs/hu-rHU/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "modul", "sok", "mqtt", "module", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon"],"aliases":["modules", "module-config", "administration"],"charCount":33776}, + {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"hu-rHU","resourcePath":"docs/hu-rHU/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "configuration", "eszk", "zbe", "sok", "lora", "modem", "presets", "kijelz", "poz", "energia", "zati", "bluetooth", "biztons", "related", "topics"],"aliases":["beállítások", "radio-config", "user-config", "lora"],"charCount":42486}, {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"hu-rHU","resourcePath":"docs/hu-rHU/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5257}, {"id":"tak","title":"TAK Integration","section":"user","locale":"hu-rHU","resourcePath":"docs/hu-rHU/user/tak.html","navOrder":10,"keywords":["tak", "integration", "overview", "setup", "prerequisites", "configuration", "local", "server", "roles", "cot", "cursor", "target", "format", "wire", "usage", "with", "atak", "troubleshooting", "security", "considerations", "related", "topics"],"aliases":["tak", "atak", "team-awareness-kit"],"charCount":10705}, {"id":"telemetry-and-sensors","title":"Telemetry and sensors","section":"user","locale":"hu-rHU","resourcePath":"docs/hu-rHU/user/telemetry-and-sensors.html","navOrder":999,"keywords":["telemetry", "and", "sensors", "device", "environment", "temperature", "humidity", "air", "quality", "soil", "light", "weather", "other", "readings", "pell", "metrik", "configuring", "choosing", "interval", "metrics", "viewing", "troubleshooting", "related", "topics"],"aliases":[],"charCount":12334}, @@ -392,17 +392,17 @@ {"id":"connections","title":"Connections","section":"user","locale":"is-rIS","resourcePath":"docs/is-rIS/user/connections.html","navOrder":2,"keywords":["connections", "bluetooth", "ble", "pairing", "radio", "connection", "status", "troubleshooting", "usb", "serial", "setup", "tcp", "network", "connecting", "over", "the", "when", "use", "provisioning", "for", "mpwrd", "after", "your", "first", "reconnection", "behavior", "desktop", "related", "topics"],"aliases":["bluetooth", "usb", "tcp", "pairing"],"charCount":11114}, {"id":"debug-logs","title":"Debug Logs","section":"user","locale":"is-rIS","resourcePath":"docs/is-rIS/user/debug-logs.html","navOrder":22,"keywords":["debug", "logs", "the", "two", "tabs", "viewing", "app", "exporting", "desktop", "related", "topics"],"aliases":["debug-logs", "logcat", "app-logs", "bug-report"],"charCount":3119}, {"id":"desktop","title":"Desktop App","section":"user","locale":"is-rIS","resourcePath":"docs/is-rIS/user/desktop.html","navOrder":14,"keywords":["desktop", "app", "installation", "linux", "macos", "windows", "connecting", "your", "radio", "usb", "serial", "primary", "tcp", "bluetooth", "ble", "feature", "parity", "differences", "keyboard", "shortcuts", "window", "system", "tray", "notification", "preferences", "built", "documentation", "browser", "building", "from"],"aliases":["desktop", "linux", "macos", "windows", "jvm"],"charCount":9955}, - {"id":"discovery","title":"Local Mesh Discovery","section":"user","locale":"is-rIS","resourcePath":"docs/is-rIS/user/discovery.html","navOrder":12,"keywords":["local", "mesh", "discovery", "scanner", "setting", "scan", "live", "progress", "reading", "the", "results", "beacon", "manual", "exploration", "ferilk", "nnun", "neighbor", "info", "node", "list", "tool", "tips", "for", "related", "topics"],"aliases":["discovery", "local-mesh-discovery", "mesh-discovery", "local-discovery", "network-scan", "traceroute", "neighbor-info"],"charCount":18335}, + {"id":"discovery","title":"Local Mesh Discovery","section":"user","locale":"is-rIS","resourcePath":"docs/is-rIS/user/discovery.html","navOrder":12,"keywords":["local", "mesh", "discovery", "scanner", "setting", "scan", "live", "progress", "reading", "the", "results", "beacon", "manual", "exploration", "ferilk", "nnun", "neighbor", "info", "node", "list", "tool", "tips", "for", "related", "topics"],"aliases":["discovery", "local-mesh-discovery", "mesh-discovery", "local-discovery", "network-scan", "traceroute", "neighbor-info"],"charCount":18325}, {"id":"firmware","title":"Firmware Updates","section":"user","locale":"is-rIS","resourcePath":"docs/is-rIS/user/firmware.html","navOrder":13,"keywords":["firmware", "updates", "checking", "for", "update", "methods", "ota", "over", "the", "air", "via", "bluetooth", "network", "connected", "esp32", "app", "usb", "factory", "erase", "and", "bootloader", "upgrade", "other", "flashing", "options", "version", "channels", "pre", "checklist", "post"],"aliases":["firmware", "update", "ota", "flash"],"charCount":11096}, {"id":"help-and-docs","title":"Help & In-App Docs","section":"user","locale":"is-rIS","resourcePath":"docs/is-rIS/user/help-and-docs.html","navOrder":21,"keywords":["help", "app", "docs", "browsing", "search", "chirpy", "the", "assistant", "related", "topics"],"aliases":["help", "docs-browser", "chirpy", "assistant"],"charCount":2306}, {"id":"map-and-waypoints","title":"Map & Waypoints","section":"user","locale":"is-rIS","resourcePath":"docs/is-rIS/user/map-and-waypoints.html","navOrder":6,"keywords":["map", "waypoints", "view", "node", "markers", "controls", "filtering", "the", "creating", "waypoint", "properties", "expiration", "geofences", "managing", "layers", "site", "planner", "position", "sharing", "enabling", "privacy", "considerations", "sources", "adding", "your", "own", "tile", "source", "offline", "terrain"],"aliases":["map", "waypoints", "gps", "location", "site-planner", "map-layers", "geojson", "kml"],"charCount":14884}, {"id":"messages-and-channels","title":"Messages & Channels","section":"user","locale":"is-rIS","resourcePath":"docs/is-rIS/user/messages-and-channels.html","navOrder":3,"keywords":["messages", "channels", "default", "channel", "security", "adding", "archived", "direct", "sending", "message", "managing", "the", "conversation", "list", "bubbles", "states", "delivery", "errors", "features", "quick", "chat", "searching", "text", "formatting", "mentions", "reactions", "replying", "day", "separators", "jump"],"aliases":["channels", "direct-messages", "messaging", "conversations"],"charCount":23868}, - {"id":"mqtt","title":"MQTT","section":"user","locale":"is-rIS","resourcePath":"docs/is-rIS/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "configuration", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12415}, + {"id":"mqtt","title":"MQTT","section":"user","locale":"is-rIS","resourcePath":"docs/is-rIS/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "configuration", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12403}, {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"is-rIS","resourcePath":"docs/is-rIS/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "device", "environment", "air", "quality", "signal", "reference", "power", "ferilk", "nnun", "reading", "traceroute", "results", "position", "log", "neighbor", "info", "host", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12543}, {"id":"nodes","title":"Nodes","section":"user","locale":"is-rIS","resourcePath":"docs/is-rIS/user/nodes.html","navOrder":4,"keywords":["nodes", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "security", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "not", "heard", "your", "current", "settings", "sort", "options", "per"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":23249}, {"id":"onboarding","title":"Getting Started","section":"user","locale":"is-rIS","resourcePath":"docs/is-rIS/user/onboarding.html","navOrder":1,"keywords":["getting", "started", "first", "launch", "welcome", "screen", "permissions", "bluetooth", "permission", "location", "notifications", "critical", "alerts", "reviewing", "later", "after", "setup", "related", "topics"],"aliases":["first-launch", "setup", "intro"],"charCount":8461}, - {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"is-rIS","resourcePath":"docs/is-rIS/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "stillingar", "aukaeininga", "mqtt", "module", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon"],"aliases":["modules", "module-config", "administration"],"charCount":33368}, - {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"is-rIS","resourcePath":"docs/is-rIS/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "configuration", "device", "config", "lora", "modem", "presets", "display", "position", "power", "network", "bluetooth", "security", "related", "topics"],"aliases":["settings", "radio-config", "user-config", "lora"],"charCount":41641}, + {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"is-rIS","resourcePath":"docs/is-rIS/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "stillingar", "aukaeininga", "mqtt", "module", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon"],"aliases":["modules", "module-config", "administration"],"charCount":33022}, + {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"is-rIS","resourcePath":"docs/is-rIS/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "configuration", "device", "config", "lora", "modem", "presets", "display", "position", "power", "network", "bluetooth", "security", "related", "topics"],"aliases":["settings", "radio-config", "user-config", "lora"],"charCount":42001}, {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"is-rIS","resourcePath":"docs/is-rIS/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5233}, {"id":"tak","title":"TAK Integration","section":"user","locale":"is-rIS","resourcePath":"docs/is-rIS/user/tak.html","navOrder":10,"keywords":["tak", "integration", "overview", "setup", "prerequisites", "configuration", "local", "server", "roles", "cot", "cursor", "target", "format", "wire", "usage", "with", "atak", "troubleshooting", "security", "considerations", "related", "topics"],"aliases":["tak", "atak", "team-awareness-kit"],"charCount":10705}, {"id":"telemetry-and-sensors","title":"Telemetry and sensors","section":"user","locale":"is-rIS","resourcePath":"docs/is-rIS/user/telemetry-and-sensors.html","navOrder":999,"keywords":["telemetry", "and", "sensors", "device", "environment", "temperature", "humidity", "air", "quality", "soil", "light", "weather", "other", "readings", "power", "metrics", "configuring", "choosing", "interval", "viewing", "troubleshooting", "related", "topics"],"aliases":[],"charCount":12297}, @@ -413,17 +413,17 @@ {"id":"connections","title":"Connessioni","section":"user","locale":"it-rIT","resourcePath":"docs/it-rIT/user/connections.html","navOrder":2,"keywords":["connessioni", "bluetooth", "ble", "pairing", "radio", "connection", "status", "troubleshooting", "usb", "serial", "configurazione", "tcp", "network", "connecting", "over", "the", "when", "use", "provisioning", "per", "mpwrd", "after", "your", "first", "reconnection", "behavior", "desktop", "connections", "related", "topics"],"aliases":["bluetooth", "usb", "tcp", "pairing"],"charCount":11159}, {"id":"debug-logs","title":"Debug Logs","section":"user","locale":"it-rIT","resourcePath":"docs/it-rIT/user/debug-logs.html","navOrder":22,"keywords":["debug", "logs", "the", "two", "tabs", "viewing", "app", "exporting", "desktop", "related", "topics"],"aliases":["debug-logs", "logcat", "app-logs", "bug-report"],"charCount":3119}, {"id":"desktop","title":"Desktop App","section":"user","locale":"it-rIT","resourcePath":"docs/it-rIT/user/desktop.html","navOrder":14,"keywords":["desktop", "app", "installazione", "linux", "macos", "windows", "connecting", "your", "radio", "usb", "serial", "primary", "tcp", "bluetooth", "ble", "feature", "parity", "differences", "keyboard", "shortcuts", "window", "system", "tray", "notification", "preferences", "built", "documentation", "browser", "building", "from"],"aliases":["desktop", "linux", "macos", "windows", "jvm"],"charCount":9958}, - {"id":"discovery","title":"Discovery della mesh locale","section":"user","locale":"it-rIT","resourcePath":"docs/it-rIT/user/discovery.html","navOrder":12,"keywords":["discovery", "della", "mesh", "locale", "local", "scanner", "setting", "scan", "live", "progress", "reading", "the", "results", "beacon", "manual", "exploration", "traceroute", "informazioni", "vicinato", "node", "list", "tool", "tips", "for", "related", "topics"],"aliases":["discovery", "local-mesh-discovery", "mesh-discovery", "local-discovery", "network-scan", "traceroute", "neighbor-info"],"charCount":18356}, + {"id":"discovery","title":"Discovery della mesh locale","section":"user","locale":"it-rIT","resourcePath":"docs/it-rIT/user/discovery.html","navOrder":12,"keywords":["discovery", "della", "mesh", "locale", "local", "scanner", "setting", "scan", "live", "progress", "reading", "the", "results", "beacon", "manual", "exploration", "traceroute", "informazioni", "vicinato", "node", "list", "tool", "tips", "for", "related", "topics"],"aliases":["discovery", "local-mesh-discovery", "mesh-discovery", "local-discovery", "network-scan", "traceroute", "neighbor-info"],"charCount":18346}, {"id":"firmware","title":"Firmware Updates","section":"user","locale":"it-rIT","resourcePath":"docs/it-rIT/user/firmware.html","navOrder":13,"keywords":["firmware", "updates", "checking", "for", "update", "methods", "ota", "over", "the", "air", "via", "bluetooth", "network", "connected", "esp32", "app", "usb", "factory", "erase", "and", "bootloader", "upgrade", "other", "flashing", "options", "version", "channels", "pre", "checklist", "post"],"aliases":["firmware", "update", "ota", "flash"],"charCount":11101}, {"id":"help-and-docs","title":"Help & In-App Docs","section":"user","locale":"it-rIT","resourcePath":"docs/it-rIT/user/help-and-docs.html","navOrder":21,"keywords":["help", "app", "docs", "browsing", "search", "chirpy", "the", "assistant", "related", "topics"],"aliases":["help", "docs-browser", "chirpy", "assistant"],"charCount":2306}, {"id":"map-and-waypoints","title":"Map & Waypoints","section":"user","locale":"it-rIT","resourcePath":"docs/it-rIT/user/map-and-waypoints.html","navOrder":6,"keywords":["map", "waypoints", "view", "node", "markers", "controls", "filtering", "the", "creating", "waypoint", "properties", "expiration", "geofences", "managing", "livelli", "della", "mappa", "site", "planner", "position", "sharing", "enabling", "privacy", "considerations", "sources", "adding", "your", "own", "tile", "source"],"aliases":["map", "waypoints", "gps", "location", "site-planner", "map-layers", "geojson", "kml"],"charCount":14901}, {"id":"messages-and-channels","title":"Messages & Channels","section":"user","locale":"it-rIT","resourcePath":"docs/it-rIT/user/messages-and-channels.html","navOrder":3,"keywords":["messages", "channels", "canali", "default", "channel", "sicurezza", "del", "canale", "adding", "archived", "messaggi", "diretti", "sending", "direct", "message", "managing", "the", "conversation", "list", "bubbles", "states", "delivery", "errors", "features", "quick", "chat", "searching", "text", "formatting", "mentions"],"aliases":["channels", "direct-messages", "messaging", "conversations"],"charCount":24126}, - {"id":"mqtt","title":"MQTT","section":"user","locale":"it-rIT","resourcePath":"docs/it-rIT/user/mqtt.html","navOrder":11,"keywords":["mqtt", "panoramica", "come", "funziona", "configurazione", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "buone", "pratiche", "risoluzione", "problemi", "not"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12424}, + {"id":"mqtt","title":"MQTT","section":"user","locale":"it-rIT","resourcePath":"docs/it-rIT/user/mqtt.html","navOrder":11,"keywords":["mqtt", "panoramica", "come", "funziona", "configurazione", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "buone", "pratiche", "risoluzione", "problemi", "not"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12412}, {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"it-rIT","resourcePath":"docs/it-rIT/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "metriche", "dispositivo", "ambientali", "air", "quality", "qualit", "segnale", "signal", "reference", "alimentazione", "traceroute", "reading", "results", "registro", "posizione", "informazioni", "vicinato", "host", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12626}, {"id":"nodes","title":"Nodi","section":"user","locale":"it-rIT","resourcePath":"docs/it-rIT/user/nodes.html","navOrder":4,"keywords":["nodi", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "security", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "nodes", "not", "heard", "your", "current", "settings", "sort", "options"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":23311}, {"id":"onboarding","title":"Come iniziare","section":"user","locale":"it-rIT","resourcePath":"docs/it-rIT/user/onboarding.html","navOrder":1,"keywords":["come", "iniziare", "first", "launch", "welcome", "screen", "permissions", "bluetooth", "permission", "location", "notifications", "critical", "alerts", "reviewing", "later", "after", "setup", "related", "topics"],"aliases":["first-launch", "setup", "intro"],"charCount":8547}, - {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"it-rIT","resourcePath":"docs/it-rIT/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "impostazioni", "moduli", "mqtt", "module", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon"],"aliases":["modules", "module-config", "administration"],"charCount":34292}, - {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"it-rIT","resourcePath":"docs/it-rIT/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "impostazioni", "utente", "profile", "applying", "changes", "configurazione", "dispositivo", "lora", "modem", "presets", "schermo", "posizione", "alimentazione", "della", "rete", "bluetooth", "sicurezza", "related", "topics"],"aliases":["impostazioni", "radio-config", "user-config", "lora"],"charCount":42552}, + {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"it-rIT","resourcePath":"docs/it-rIT/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "impostazioni", "moduli", "mqtt", "module", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon"],"aliases":["modules", "module-config", "administration"],"charCount":33872}, + {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"it-rIT","resourcePath":"docs/it-rIT/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "impostazioni", "utente", "profile", "applying", "changes", "configurazione", "dispositivo", "lora", "modem", "presets", "schermo", "posizione", "alimentazione", "della", "rete", "bluetooth", "sicurezza", "related", "topics"],"aliases":["impostazioni", "radio-config", "user-config", "lora"],"charCount":42714}, {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"it-rIT","resourcePath":"docs/it-rIT/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5251}, {"id":"tak","title":"TAK Integration","section":"user","locale":"it-rIT","resourcePath":"docs/it-rIT/user/tak.html","navOrder":10,"keywords":["tak", "integration", "panoramica", "configurazione", "prerequisiti", "local", "server", "roles", "cot", "cursor", "target", "format", "wire", "usage", "with", "atak", "risoluzione", "problemi", "security", "considerations", "related", "topics"],"aliases":["tak", "atak", "team-awareness-kit"],"charCount":10725}, {"id":"telemetry-and-sensors","title":"Telemetry and sensors","section":"user","locale":"it-rIT","resourcePath":"docs/it-rIT/user/telemetry-and-sensors.html","navOrder":999,"keywords":["telemetry", "and", "sensors", "telemetria", "dispositivo", "environment", "temperature", "humidity", "air", "quality", "soil", "light", "weather", "other", "readings", "metriche", "alimentazione", "configuring", "choosing", "interval", "metrics", "viewing", "risoluzione", "problemi", "related", "topics"],"aliases":[],"charCount":12393}, @@ -434,17 +434,17 @@ {"id":"connections","title":"Connections","section":"user","locale":"iw-rIL","resourcePath":"docs/iw-rIL/user/connections.html","navOrder":2,"keywords":["connections", "bluetooth", "ble", "pairing", "radio", "connection", "status", "troubleshooting", "usb", "serial", "setup", "tcp", "network", "connecting", "over", "the", "when", "use", "provisioning", "for", "mpwrd", "after", "your", "first", "reconnection", "behavior", "desktop", "related", "topics"],"aliases":["bluetooth", "usb", "tcp", "pairing"],"charCount":11090}, {"id":"debug-logs","title":"Debug Logs","section":"user","locale":"iw-rIL","resourcePath":"docs/iw-rIL/user/debug-logs.html","navOrder":22,"keywords":["debug", "logs", "the", "two", "tabs", "viewing", "app", "exporting", "desktop", "related", "topics"],"aliases":["debug-logs", "logcat", "app-logs", "bug-report"],"charCount":3119}, {"id":"desktop","title":"Desktop App","section":"user","locale":"iw-rIL","resourcePath":"docs/iw-rIL/user/desktop.html","navOrder":14,"keywords":["desktop", "app", "installation", "linux", "macos", "windows", "connecting", "your", "radio", "usb", "serial", "primary", "tcp", "bluetooth", "ble", "feature", "parity", "differences", "keyboard", "shortcuts", "window", "system", "tray", "notification", "preferences", "built", "documentation", "browser", "building", "from"],"aliases":["desktop", "linux", "macos", "windows", "jvm"],"charCount":9955}, - {"id":"discovery","title":"Local Mesh Discovery","section":"user","locale":"iw-rIL","resourcePath":"docs/iw-rIL/user/discovery.html","navOrder":12,"keywords":["local", "mesh", "discovery", "scanner", "setting", "scan", "live", "progress", "reading", "the", "results", "beacon", "manual", "exploration", "neighbor", "info", "node", "list", "tool", "tips", "for", "related", "topics"],"aliases":["discovery", "local-mesh-discovery", "mesh-discovery", "local-discovery", "network-scan", "traceroute", "neighbor-info"],"charCount":18335}, + {"id":"discovery","title":"Local Mesh Discovery","section":"user","locale":"iw-rIL","resourcePath":"docs/iw-rIL/user/discovery.html","navOrder":12,"keywords":["local", "mesh", "discovery", "scanner", "setting", "scan", "live", "progress", "reading", "the", "results", "beacon", "manual", "exploration", "neighbor", "info", "node", "list", "tool", "tips", "for", "related", "topics"],"aliases":["discovery", "local-mesh-discovery", "mesh-discovery", "local-discovery", "network-scan", "traceroute", "neighbor-info"],"charCount":18325}, {"id":"firmware","title":"Firmware Updates","section":"user","locale":"iw-rIL","resourcePath":"docs/iw-rIL/user/firmware.html","navOrder":13,"keywords":["firmware", "updates", "checking", "for", "update", "methods", "ota", "over", "the", "air", "via", "bluetooth", "network", "connected", "esp32", "app", "usb", "factory", "erase", "and", "bootloader", "upgrade", "other", "flashing", "options", "version", "channels", "pre", "checklist", "post"],"aliases":["firmware", "update", "ota", "flash"],"charCount":11096}, {"id":"help-and-docs","title":"Help & In-App Docs","section":"user","locale":"iw-rIL","resourcePath":"docs/iw-rIL/user/help-and-docs.html","navOrder":21,"keywords":["help", "app", "docs", "browsing", "search", "chirpy", "the", "assistant", "related", "topics"],"aliases":["help", "docs-browser", "chirpy", "assistant"],"charCount":2306}, {"id":"map-and-waypoints","title":"Map & Waypoints","section":"user","locale":"iw-rIL","resourcePath":"docs/iw-rIL/user/map-and-waypoints.html","navOrder":6,"keywords":["map", "waypoints", "view", "node", "markers", "controls", "filtering", "the", "creating", "waypoint", "properties", "expiration", "geofences", "managing", "layers", "site", "planner", "position", "sharing", "enabling", "privacy", "considerations", "sources", "adding", "your", "own", "tile", "source", "offline", "terrain"],"aliases":["map", "waypoints", "gps", "location", "site-planner", "map-layers", "geojson", "kml"],"charCount":14884}, {"id":"messages-and-channels","title":"Messages & Channels","section":"user","locale":"iw-rIL","resourcePath":"docs/iw-rIL/user/messages-and-channels.html","navOrder":3,"keywords":["messages", "channels", "default", "channel", "security", "adding", "archived", "direct", "sending", "message", "managing", "the", "conversation", "list", "bubbles", "states", "delivery", "errors", "features", "quick", "chat", "searching", "text", "formatting", "mentions", "reactions", "replying", "day", "separators", "jump"],"aliases":["channels", "direct-messages", "messaging", "conversations"],"charCount":23868}, - {"id":"mqtt","title":"MQTT","section":"user","locale":"iw-rIL","resourcePath":"docs/iw-rIL/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "configuration", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12415}, + {"id":"mqtt","title":"MQTT","section":"user","locale":"iw-rIL","resourcePath":"docs/iw-rIL/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "configuration", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12403}, {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"iw-rIL","resourcePath":"docs/iw-rIL/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "device", "environment", "air", "quality", "signal", "reference", "power", "reading", "traceroute", "results", "position", "log", "neighbor", "info", "host", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12543}, {"id":"nodes","title":"Nodes","section":"user","locale":"iw-rIL","resourcePath":"docs/iw-rIL/user/nodes.html","navOrder":4,"keywords":["nodes", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "security", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "not", "heard", "your", "current", "settings", "sort", "options", "per"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":23249}, {"id":"onboarding","title":"Getting Started","section":"user","locale":"iw-rIL","resourcePath":"docs/iw-rIL/user/onboarding.html","navOrder":1,"keywords":["getting", "started", "first", "launch", "welcome", "screen", "permissions", "bluetooth", "permission", "location", "notifications", "critical", "alerts", "reviewing", "later", "after", "setup", "related", "topics"],"aliases":["first-launch", "setup", "intro"],"charCount":8461}, - {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"iw-rIL","resourcePath":"docs/iw-rIL/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "mqtt", "module", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon", "tak", "administration"],"aliases":["modules", "module-config", "administration"],"charCount":33369}, - {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"iw-rIL","resourcePath":"docs/iw-rIL/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "configuration", "device", "config", "lora", "modem", "presets", "display", "position", "power", "network", "bluetooth", "security", "related", "topics"],"aliases":["הגדרות", "radio-config", "user-config", "lora"],"charCount":41639}, + {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"iw-rIL","resourcePath":"docs/iw-rIL/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "mqtt", "module", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon", "tak", "administration"],"aliases":["modules", "module-config", "administration"],"charCount":33023}, + {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"iw-rIL","resourcePath":"docs/iw-rIL/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "configuration", "device", "config", "lora", "modem", "presets", "display", "position", "power", "network", "bluetooth", "security", "related", "topics"],"aliases":["הגדרות", "radio-config", "user-config", "lora"],"charCount":41999}, {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"iw-rIL","resourcePath":"docs/iw-rIL/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5233}, {"id":"tak","title":"TAK Integration","section":"user","locale":"iw-rIL","resourcePath":"docs/iw-rIL/user/tak.html","navOrder":10,"keywords":["tak", "integration", "overview", "setup", "prerequisites", "configuration", "local", "server", "roles", "cot", "cursor", "target", "format", "wire", "usage", "with", "atak", "troubleshooting", "security", "considerations", "related", "topics"],"aliases":["tak", "atak", "team-awareness-kit"],"charCount":10705}, {"id":"telemetry-and-sensors","title":"Telemetry and sensors","section":"user","locale":"iw-rIL","resourcePath":"docs/iw-rIL/user/telemetry-and-sensors.html","navOrder":999,"keywords":["telemetry", "and", "sensors", "device", "environment", "temperature", "humidity", "air", "quality", "soil", "light", "weather", "other", "readings", "power", "metrics", "configuring", "choosing", "interval", "viewing", "troubleshooting", "related", "topics"],"aliases":[],"charCount":12297}, @@ -455,17 +455,17 @@ {"id":"connections","title":"コネクション","section":"user","locale":"ja-rJP","resourcePath":"docs/ja-rJP/user/connections.html","navOrder":2,"keywords":["bluetooth", "ble", "pairing", "radio", "usb", "troubleshooting", "tcp", "mpwrd", "after", "your", "first", "connection"],"aliases":["bluetooth", "usb", "tcp", "pairing"],"charCount":10227}, {"id":"debug-logs","title":"デバッグログ","section":"user","locale":"ja-rJP","resourcePath":"docs/ja-rJP/user/debug-logs.html","navOrder":22,"keywords":[],"aliases":["debug-logs", "logcat", "app-logs", "bug-report"],"charCount":2329}, {"id":"desktop","title":"デスクトップアプリ","section":"user","locale":"ja-rJP","resourcePath":"docs/ja-rJP/user/desktop.html","navOrder":14,"keywords":["linux", "macos", "windows", "usb", "tcp", "bluetooth", "ble"],"aliases":["desktop", "linux", "macos", "windows", "jvm"],"charCount":9301}, - {"id":"discovery","title":"ローカルメッシュ探索","section":"user","locale":"ja-rJP","resourcePath":"docs/ja-rJP/user/discovery.html","navOrder":12,"keywords":["setting", "scan", "live", "progress", "reading", "the", "results", "manual", "exploration", "node", "list", "discovery", "tool", "tips", "for", "mesh"],"aliases":["discovery", "local-mesh-discovery", "mesh-discovery", "local-discovery", "network-scan", "traceroute", "neighbor-info"],"charCount":15581}, + {"id":"discovery","title":"ローカルメッシュ探索","section":"user","locale":"ja-rJP","resourcePath":"docs/ja-rJP/user/discovery.html","navOrder":12,"keywords":["setting", "scan", "live", "progress", "reading", "the", "results", "manual", "exploration", "node", "list", "discovery", "tool", "tips", "for", "mesh"],"aliases":["discovery", "local-mesh-discovery", "mesh-discovery", "local-discovery", "network-scan", "traceroute", "neighbor-info"],"charCount":15571}, {"id":"firmware","title":"ファームウェア更新","section":"user","locale":"ja-rJP","resourcePath":"docs/ja-rJP/user/firmware.html","navOrder":13,"keywords":["bluetooth", "ota", "via", "network", "connected", "esp32", "usb", "factory", "erase", "and", "bootloader", "upgrade", "radio", "won", "boot", "after", "update"],"aliases":["firmware", "update", "ota", "flash"],"charCount":9836}, {"id":"help-and-docs","title":"ヘルプとアプリ内ドキュメント","section":"user","locale":"ja-rJP","resourcePath":"docs/ja-rJP/user/help-and-docs.html","navOrder":21,"keywords":["chirpy"],"aliases":["help", "docs-browser", "chirpy", "assistant"],"charCount":1786}, {"id":"map-and-waypoints","title":"マップとウェイポイント","section":"user","locale":"ja-rJP","resourcePath":"docs/ja-rJP/user/map-and-waypoints.html","navOrder":6,"keywords":["filtering", "the", "map", "adding", "your", "own", "tile", "source", "offline", "terrain", "going"],"aliases":["map", "waypoints", "gps", "location", "site-planner", "map-layers", "geojson", "kml"],"charCount":13318}, {"id":"messages-and-channels","title":"メッセージとチャンネル","section":"user","locale":"ja-rJP","resourcePath":"docs/ja-rJP/user/messages-and-channels.html","navOrder":3,"keywords":["archived", "channels", "managing", "the", "conversation", "list", "bubbles", "replying", "day", "separators", "jump", "latest"],"aliases":["channels", "direct-messages", "messaging", "conversations"],"charCount":21711}, - {"id":"mqtt","title":"MQTT","section":"user","locale":"ja-rJP","resourcePath":"docs/ja-rJP/user/mqtt.html","navOrder":11,"keywords":["mqtt", "connection", "status", "and", "test", "meshtastic"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":11234}, + {"id":"mqtt","title":"MQTT","section":"user","locale":"ja-rJP","resourcePath":"docs/ja-rJP/user/mqtt.html","navOrder":11,"keywords":["mqtt", "connection", "status", "and", "test", "meshtastic"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":11222}, {"id":"node-metrics","title":"ノードメトリクス","section":"user","locale":"ja-rJP","resourcePath":"docs/ja-rJP/user/node-metrics.html","navOrder":5,"keywords":["pax"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":10002}, {"id":"nodes","title":"ノード","section":"user","locale":"ja-rJP","resourcePath":"docs/ja-rJP/user/nodes.html","navOrder":4,"keywords":["node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "security", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "nodes", "not", "heard", "your", "current", "settings", "sort", "options", "per", "hop", "detail"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":21145}, {"id":"onboarding","title":"はじめに","section":"user","locale":"ja-rJP","resourcePath":"docs/ja-rJP/user/onboarding.html","navOrder":1,"keywords":["bluetooth", "reviewing", "permissions", "later"],"aliases":["初回起動", "セットアップ", "概要"],"charCount":7546}, - {"id":"settings-module-admin","title":"設定：モジュールと管理","section":"user","locale":"ja-rJP","resourcePath":"docs/ja-rJP/user/settings-module-admin.html","navOrder":8,"keywords":["mqtt", "module", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon", "tak", "device", "actions", "app", "settings"],"aliases":["modules", "module-config", "administration"],"charCount":27918}, - {"id":"settings-radio-user","title":"設定：無線機とユーザー","section":"user","locale":"ja-rJP","resourcePath":"docs/ja-rJP/user/settings-radio-user.html","navOrder":7,"keywords":["how", "these", "screens", "work", "applying", "changes", "lora", "modem", "presets", "bluetooth"],"aliases":["設定", "radio-config", "user-config", "lora"],"charCount":40150}, + {"id":"settings-module-admin","title":"設定：モジュールと管理","section":"user","locale":"ja-rJP","resourcePath":"docs/ja-rJP/user/settings-module-admin.html","navOrder":8,"keywords":["mqtt", "module", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon", "tak", "device", "actions", "app", "settings"],"aliases":["modules", "module-config", "administration"],"charCount":27950}, + {"id":"settings-radio-user","title":"設定：無線機とユーザー","section":"user","locale":"ja-rJP","resourcePath":"docs/ja-rJP/user/settings-radio-user.html","navOrder":7,"keywords":["how", "these", "screens", "work", "applying", "changes", "lora", "modem", "presets", "bluetooth"],"aliases":["設定", "radio-config", "user-config", "lora"],"charCount":40599}, {"id":"signal-meter","title":"Meshtastic の信号メーターの仕組み","section":"user","locale":"ja-rJP","resourcePath":"docs/ja-rJP/user/signal-meter.html","navOrder":15,"keywords":["meshtastic", "rssi", "and", "snr", "decoding", "below", "the", "noise", "floor", "rating", "signal", "quality", "diagnosing", "local", "interference"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":4980}, {"id":"tak","title":"TAK 連携","section":"user","locale":"ja-rJP","resourcePath":"docs/ja-rJP/user/tak.html","navOrder":10,"keywords":["tak", "cot", "cursor", "target", "atak"],"aliases":["tak", "atak", "team-awareness-kit"],"charCount":8480}, {"id":"telemetry-and-sensors","title":"Telemetry and sensors","section":"user","locale":"ja-rJP","resourcePath":"docs/ja-rJP/user/telemetry-and-sensors.html","navOrder":999,"keywords":["telemetry", "and", "sensors", "soil", "weather", "other", "readings", "choosing", "interval"],"aliases":[],"charCount":10995}, @@ -476,17 +476,17 @@ {"id":"connections","title":"Connections","section":"user","locale":"ko-rKR","resourcePath":"docs/ko-rKR/user/connections.html","navOrder":2,"keywords":["connections", "bluetooth", "ble", "pairing", "radio", "connection", "status", "troubleshooting", "usb", "serial", "setup", "tcp", "network", "connecting", "over", "the", "when", "use", "provisioning", "for", "mpwrd", "after", "your", "first", "reconnection", "behavior", "desktop", "related", "topics"],"aliases":["bluetooth", "usb", "tcp", "pairing"],"charCount":11030}, {"id":"debug-logs","title":"Debug Logs","section":"user","locale":"ko-rKR","resourcePath":"docs/ko-rKR/user/debug-logs.html","navOrder":22,"keywords":["debug", "logs", "the", "two", "tabs", "viewing", "app", "exporting", "desktop", "related", "topics"],"aliases":["debug-logs", "logcat", "app-logs", "bug-report"],"charCount":3119}, {"id":"desktop","title":"Desktop App","section":"user","locale":"ko-rKR","resourcePath":"docs/ko-rKR/user/desktop.html","navOrder":14,"keywords":["desktop", "app", "installation", "linux", "macos", "windows", "connecting", "your", "radio", "usb", "serial", "primary", "tcp", "bluetooth", "ble", "feature", "parity", "differences", "keyboard", "shortcuts", "window", "system", "tray", "notification", "preferences", "built", "documentation", "browser", "building", "from"],"aliases":["desktop", "linux", "macos", "windows", "jvm"],"charCount":9955}, - {"id":"discovery","title":"Local Mesh Discovery","section":"user","locale":"ko-rKR","resourcePath":"docs/ko-rKR/user/discovery.html","navOrder":12,"keywords":["local", "mesh", "discovery", "scanner", "setting", "scan", "live", "progress", "reading", "the", "results", "beacon", "manual", "exploration", "node", "list", "tool", "tips", "for", "related", "topics"],"aliases":["discovery", "local-mesh-discovery", "mesh-discovery", "local-discovery", "network-scan", "traceroute", "neighbor-info"],"charCount":18321}, + {"id":"discovery","title":"Local Mesh Discovery","section":"user","locale":"ko-rKR","resourcePath":"docs/ko-rKR/user/discovery.html","navOrder":12,"keywords":["local", "mesh", "discovery", "scanner", "setting", "scan", "live", "progress", "reading", "the", "results", "beacon", "manual", "exploration", "node", "list", "tool", "tips", "for", "related", "topics"],"aliases":["discovery", "local-mesh-discovery", "mesh-discovery", "local-discovery", "network-scan", "traceroute", "neighbor-info"],"charCount":18311}, {"id":"firmware","title":"Firmware Updates","section":"user","locale":"ko-rKR","resourcePath":"docs/ko-rKR/user/firmware.html","navOrder":13,"keywords":["firmware", "updates", "checking", "for", "update", "methods", "ota", "over", "the", "air", "via", "bluetooth", "network", "connected", "esp32", "app", "usb", "factory", "erase", "and", "bootloader", "upgrade", "other", "flashing", "options", "version", "channels", "pre", "checklist", "post"],"aliases":["firmware", "update", "ota", "flash"],"charCount":11096}, {"id":"help-and-docs","title":"Help & In-App Docs","section":"user","locale":"ko-rKR","resourcePath":"docs/ko-rKR/user/help-and-docs.html","navOrder":21,"keywords":["help", "app", "docs", "browsing", "search", "chirpy", "the", "assistant", "related", "topics"],"aliases":["help", "docs-browser", "chirpy", "assistant"],"charCount":2306}, {"id":"map-and-waypoints","title":"Map & Waypoints","section":"user","locale":"ko-rKR","resourcePath":"docs/ko-rKR/user/map-and-waypoints.html","navOrder":6,"keywords":["map", "waypoints", "view", "node", "markers", "controls", "filtering", "the", "creating", "waypoint", "properties", "expiration", "geofences", "managing", "layers", "site", "planner", "position", "sharing", "enabling", "privacy", "considerations", "sources", "adding", "your", "own", "tile", "source", "offline", "terrain"],"aliases":["map", "waypoints", "gps", "location", "site-planner", "map-layers", "geojson", "kml"],"charCount":14884}, {"id":"messages-and-channels","title":"Messages & Channels","section":"user","locale":"ko-rKR","resourcePath":"docs/ko-rKR/user/messages-and-channels.html","navOrder":3,"keywords":["messages", "channels", "default", "channel", "security", "adding", "archived", "direct", "sending", "message", "managing", "the", "conversation", "list", "bubbles", "states", "delivery", "errors", "features", "quick", "chat", "searching", "text", "formatting", "mentions", "reactions", "replying", "day", "separators", "jump"],"aliases":["channels", "direct-messages", "messaging", "conversations"],"charCount":23862}, - {"id":"mqtt","title":"MQTT","section":"user","locale":"ko-rKR","resourcePath":"docs/ko-rKR/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting", "messages"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12404}, + {"id":"mqtt","title":"MQTT","section":"user","locale":"ko-rKR","resourcePath":"docs/ko-rKR/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting", "messages"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12392}, {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"ko-rKR","resourcePath":"docs/ko-rKR/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "device", "environment", "air", "quality", "signal", "reference", "power", "reading", "traceroute", "results", "host", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12509}, {"id":"nodes","title":"노드","section":"user","locale":"ko-rKR","resourcePath":"docs/ko-rKR/user/nodes.html","navOrder":4,"keywords":["node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "security", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "nodes", "not", "heard", "your", "current", "settings", "sort", "options", "per"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":23240}, {"id":"onboarding","title":"Getting Started","section":"user","locale":"ko-rKR","resourcePath":"docs/ko-rKR/user/onboarding.html","navOrder":1,"keywords":["getting", "started", "first", "launch", "welcome", "screen", "permissions", "bluetooth", "permission", "location", "notifications", "critical", "alerts", "reviewing", "later", "after", "setup", "related", "topics"],"aliases":["first-launch", "setup", "intro"],"charCount":8461}, - {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"ko-rKR","resourcePath":"docs/ko-rKR/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "mqtt", "module", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon", "tak", "device"],"aliases":["modules", "module-config", "administration"],"charCount":32416}, - {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"ko-rKR","resourcePath":"docs/ko-rKR/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "lora", "modem", "presets", "related", "topics"],"aliases":["설정", "radio-config", "user-config", "lora"],"charCount":41457}, + {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"ko-rKR","resourcePath":"docs/ko-rKR/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "mqtt", "module", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon", "tak", "device"],"aliases":["modules", "module-config", "administration"],"charCount":32489}, + {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"ko-rKR","resourcePath":"docs/ko-rKR/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "lora", "modem", "presets", "related", "topics"],"aliases":["설정", "radio-config", "user-config", "lora"],"charCount":41835}, {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"ko-rKR","resourcePath":"docs/ko-rKR/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5233}, {"id":"tak","title":"TAK Integration","section":"user","locale":"ko-rKR","resourcePath":"docs/ko-rKR/user/tak.html","navOrder":10,"keywords":["tak", "integration", "overview", "setup", "prerequisites", "local", "server", "roles", "cot", "cursor", "target", "format", "wire", "usage", "with", "atak", "troubleshooting", "security", "considerations", "related", "topics"],"aliases":["tak", "atak", "team-awareness-kit"],"charCount":10694}, {"id":"telemetry-and-sensors","title":"Telemetry and sensors","section":"user","locale":"ko-rKR","resourcePath":"docs/ko-rKR/user/telemetry-and-sensors.html","navOrder":999,"keywords":["telemetry", "and", "sensors", "device", "environment", "temperature", "humidity", "air", "quality", "soil", "light", "weather", "other", "readings", "power", "metrics", "configuring", "choosing", "interval", "viewing", "troubleshooting", "related", "topics"],"aliases":[],"charCount":12146}, @@ -497,17 +497,17 @@ {"id":"connections","title":"Connections","section":"user","locale":"lt-rLT","resourcePath":"docs/lt-rLT/user/connections.html","navOrder":2,"keywords":["connections", "bluetooth", "ble", "pairing", "radio", "connection", "status", "troubleshooting", "usb", "serial", "setup", "tcp", "network", "connecting", "over", "the", "when", "use", "provisioning", "for", "mpwrd", "after", "your", "first", "reconnection", "behavior", "desktop", "related", "topics"],"aliases":["bluetooth", "usb", "tcp", "pairing"],"charCount":11090}, {"id":"debug-logs","title":"Debug Logs","section":"user","locale":"lt-rLT","resourcePath":"docs/lt-rLT/user/debug-logs.html","navOrder":22,"keywords":["debug", "logs", "the", "two", "tabs", "viewing", "app", "exporting", "desktop", "related", "topics"],"aliases":["debug-logs", "logcat", "app-logs", "bug-report"],"charCount":3119}, {"id":"desktop","title":"Desktop App","section":"user","locale":"lt-rLT","resourcePath":"docs/lt-rLT/user/desktop.html","navOrder":14,"keywords":["desktop", "app", "installation", "linux", "macos", "windows", "connecting", "your", "radio", "usb", "serial", "primary", "tcp", "bluetooth", "ble", "feature", "parity", "differences", "keyboard", "shortcuts", "window", "system", "tray", "notification", "preferences", "built", "documentation", "browser", "building", "from"],"aliases":["desktop", "linux", "macos", "windows", "jvm"],"charCount":9955}, - {"id":"discovery","title":"Local Mesh Discovery","section":"user","locale":"lt-rLT","resourcePath":"docs/lt-rLT/user/discovery.html","navOrder":12,"keywords":["local", "mesh", "discovery", "scanner", "setting", "scan", "live", "progress", "reading", "the", "results", "beacon", "manual", "exploration", "inut", "kelias", "neighbor", "info", "node", "list", "tool", "tips", "for", "related", "topics"],"aliases":["discovery", "local-mesh-discovery", "mesh-discovery", "local-discovery", "network-scan", "traceroute", "neighbor-info"],"charCount":18338}, + {"id":"discovery","title":"Local Mesh Discovery","section":"user","locale":"lt-rLT","resourcePath":"docs/lt-rLT/user/discovery.html","navOrder":12,"keywords":["local", "mesh", "discovery", "scanner", "setting", "scan", "live", "progress", "reading", "the", "results", "beacon", "manual", "exploration", "inut", "kelias", "neighbor", "info", "node", "list", "tool", "tips", "for", "related", "topics"],"aliases":["discovery", "local-mesh-discovery", "mesh-discovery", "local-discovery", "network-scan", "traceroute", "neighbor-info"],"charCount":18328}, {"id":"firmware","title":"Firmware Updates","section":"user","locale":"lt-rLT","resourcePath":"docs/lt-rLT/user/firmware.html","navOrder":13,"keywords":["firmware", "updates", "checking", "for", "update", "methods", "ota", "over", "the", "air", "via", "bluetooth", "network", "connected", "esp32", "app", "usb", "factory", "erase", "and", "bootloader", "upgrade", "other", "flashing", "options", "version", "channels", "pre", "checklist", "post"],"aliases":["firmware", "update", "ota", "flash"],"charCount":11096}, {"id":"help-and-docs","title":"Help & In-App Docs","section":"user","locale":"lt-rLT","resourcePath":"docs/lt-rLT/user/help-and-docs.html","navOrder":21,"keywords":["help", "app", "docs", "browsing", "search", "chirpy", "the", "assistant", "related", "topics"],"aliases":["help", "docs-browser", "chirpy", "assistant"],"charCount":2306}, {"id":"map-and-waypoints","title":"Map & Waypoints","section":"user","locale":"lt-rLT","resourcePath":"docs/lt-rLT/user/map-and-waypoints.html","navOrder":6,"keywords":["map", "waypoints", "view", "node", "markers", "controls", "filtering", "the", "creating", "waypoint", "properties", "expiration", "geofences", "managing", "layers", "site", "planner", "position", "sharing", "enabling", "privacy", "considerations", "sources", "adding", "your", "own", "tile", "source", "offline", "terrain"],"aliases":["map", "waypoints", "gps", "location", "site-planner", "map-layers", "geojson", "kml"],"charCount":14892}, {"id":"messages-and-channels","title":"Messages & Channels","section":"user","locale":"lt-rLT","resourcePath":"docs/lt-rLT/user/messages-and-channels.html","navOrder":3,"keywords":["messages", "channels", "default", "channel", "security", "adding", "archived", "direct", "sending", "message", "managing", "the", "conversation", "list", "bubbles", "states", "delivery", "errors", "features", "quick", "chat", "searching", "text", "formatting", "mentions", "reactions", "replying", "day", "separators", "jump"],"aliases":["channels", "direct-messages", "messaging", "conversations"],"charCount":23868}, - {"id":"mqtt","title":"MQTT","section":"user","locale":"lt-rLT","resourcePath":"docs/lt-rLT/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "configuration", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12415}, + {"id":"mqtt","title":"MQTT","section":"user","locale":"lt-rLT","resourcePath":"docs/lt-rLT/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "configuration", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12403}, {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"lt-rLT","resourcePath":"docs/lt-rLT/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "device", "environment", "air", "quality", "signalo", "kokyb", "signal", "reference", "power", "inut", "kelias", "reading", "traceroute", "results", "pozicijos", "duomen", "urnalas", "neighbor", "info", "host", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12579}, {"id":"nodes","title":"Nodes","section":"user","locale":"lt-rLT","resourcePath":"docs/lt-rLT/user/nodes.html","navOrder":4,"keywords":["nodes", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "security", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "not", "heard", "your", "current", "settings", "sort", "options", "per"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":23287}, {"id":"onboarding","title":"Getting Started","section":"user","locale":"lt-rLT","resourcePath":"docs/lt-rLT/user/onboarding.html","navOrder":1,"keywords":["getting", "started", "first", "launch", "welcome", "screen", "permissions", "bluetooth", "permission", "location", "notifications", "critical", "alerts", "reviewing", "later", "after", "setup", "related", "topics"],"aliases":["first-launch", "setup", "intro"],"charCount":8461}, - {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"lt-rLT","resourcePath":"docs/lt-rLT/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "modulio", "konfig", "racija", "mqtt", "module", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh"],"aliases":["modules", "module-config", "administration"],"charCount":33402}, - {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"lt-rLT","resourcePath":"docs/lt-rLT/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "configuration", "device", "config", "lora", "modem", "presets", "display", "position", "power", "network", "bluetooth", "security", "related", "topics"],"aliases":["settings", "radio-config", "user-config", "lora"],"charCount":41641}, + {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"lt-rLT","resourcePath":"docs/lt-rLT/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "modulio", "konfig", "racija", "mqtt", "module", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh"],"aliases":["modules", "module-config", "administration"],"charCount":33056}, + {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"lt-rLT","resourcePath":"docs/lt-rLT/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "configuration", "device", "config", "lora", "modem", "presets", "display", "position", "power", "network", "bluetooth", "security", "related", "topics"],"aliases":["settings", "radio-config", "user-config", "lora"],"charCount":42001}, {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"lt-rLT","resourcePath":"docs/lt-rLT/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5263}, {"id":"tak","title":"TAK Integration","section":"user","locale":"lt-rLT","resourcePath":"docs/lt-rLT/user/tak.html","navOrder":10,"keywords":["tak", "integration", "overview", "setup", "prerequisites", "configuration", "local", "server", "roles", "cot", "cursor", "target", "format", "wire", "usage", "with", "atak", "troubleshooting", "security", "considerations", "related", "topics"],"aliases":["tak", "atak", "team-awareness-kit"],"charCount":10705}, {"id":"telemetry-and-sensors","title":"Telemetry and sensors","section":"user","locale":"lt-rLT","resourcePath":"docs/lt-rLT/user/telemetry-and-sensors.html","navOrder":999,"keywords":["telemetry", "and", "sensors", "device", "environment", "temperature", "humidity", "air", "quality", "soil", "light", "weather", "other", "readings", "power", "metrics", "configuring", "choosing", "interval", "viewing", "troubleshooting", "related", "topics"],"aliases":[],"charCount":12283}, @@ -518,17 +518,17 @@ {"id":"connections","title":"Connections","section":"user","locale":"nl-rNL","resourcePath":"docs/nl-rNL/user/connections.html","navOrder":2,"keywords":["connections", "bluetooth", "ble", "pairing", "radio", "connection", "status", "troubleshooting", "usb", "serial", "setup", "tcp", "network", "connecting", "over", "the", "when", "use", "provisioning", "for", "mpwrd", "after", "your", "first", "reconnection", "behavior", "desktop", "related", "topics"],"aliases":["bluetooth", "usb", "tcp", "pairing"],"charCount":11132}, {"id":"debug-logs","title":"Debug Logs","section":"user","locale":"nl-rNL","resourcePath":"docs/nl-rNL/user/debug-logs.html","navOrder":22,"keywords":["debug", "logs", "the", "two", "tabs", "viewing", "app", "exporting", "desktop", "related", "topics"],"aliases":["debug-logs", "logcat", "app-logs", "bug-report"],"charCount":3119}, {"id":"desktop","title":"Desktop App","section":"user","locale":"nl-rNL","resourcePath":"docs/nl-rNL/user/desktop.html","navOrder":14,"keywords":["desktop", "app", "installation", "linux", "macos", "windows", "connecting", "your", "radio", "usb", "serial", "primary", "tcp", "bluetooth", "ble", "feature", "parity", "differences", "keyboard", "shortcuts", "window", "system", "tray", "notification", "preferences", "built", "documentation", "browser", "building", "from"],"aliases":["desktop", "linux", "macos", "windows", "jvm"],"charCount":9955}, - {"id":"discovery","title":"Local Mesh Discovery","section":"user","locale":"nl-rNL","resourcePath":"docs/nl-rNL/user/discovery.html","navOrder":12,"keywords":["local", "mesh", "discovery", "scanner", "setting", "scan", "live", "progress", "reading", "the", "results", "beacon", "manual", "exploration", "traceroute", "neighbor", "info", "node", "list", "tool", "tips", "for", "related", "topics"],"aliases":["discovery", "local-mesh-discovery", "mesh-discovery", "local-discovery", "network-scan", "traceroute", "neighbor-info"],"charCount":18334}, + {"id":"discovery","title":"Local Mesh Discovery","section":"user","locale":"nl-rNL","resourcePath":"docs/nl-rNL/user/discovery.html","navOrder":12,"keywords":["local", "mesh", "discovery", "scanner", "setting", "scan", "live", "progress", "reading", "the", "results", "beacon", "manual", "exploration", "traceroute", "neighbor", "info", "node", "list", "tool", "tips", "for", "related", "topics"],"aliases":["discovery", "local-mesh-discovery", "mesh-discovery", "local-discovery", "network-scan", "traceroute", "neighbor-info"],"charCount":18324}, {"id":"firmware","title":"Firmware Updates","section":"user","locale":"nl-rNL","resourcePath":"docs/nl-rNL/user/firmware.html","navOrder":13,"keywords":["firmware", "updates", "checking", "for", "update", "methods", "ota", "over", "the", "air", "via", "bluetooth", "network", "connected", "esp32", "app", "usb", "factory", "erase", "and", "bootloader", "upgrade", "other", "flashing", "options", "version", "channels", "pre", "checklist", "post"],"aliases":["firmware", "update", "ota", "flash"],"charCount":11096}, {"id":"help-and-docs","title":"Help & In-App Docs","section":"user","locale":"nl-rNL","resourcePath":"docs/nl-rNL/user/help-and-docs.html","navOrder":21,"keywords":["help", "app", "docs", "browsing", "search", "chirpy", "the", "assistant", "related", "topics"],"aliases":["help", "docs-browser", "chirpy", "assistant"],"charCount":2306}, {"id":"map-and-waypoints","title":"Map & Waypoints","section":"user","locale":"nl-rNL","resourcePath":"docs/nl-rNL/user/map-and-waypoints.html","navOrder":6,"keywords":["map", "waypoints", "view", "node", "markers", "controls", "filtering", "the", "creating", "waypoint", "properties", "expiration", "geofences", "managing", "layers", "site", "planner", "position", "sharing", "enabling", "privacy", "considerations", "sources", "adding", "your", "own", "tile", "source", "offline", "terrain"],"aliases":["map", "waypoints", "gps", "location", "site-planner", "map-layers", "geojson", "kml"],"charCount":14900}, {"id":"messages-and-channels","title":"Messages & Channels","section":"user","locale":"nl-rNL","resourcePath":"docs/nl-rNL/user/messages-and-channels.html","navOrder":3,"keywords":["messages", "channels", "kanalen", "default", "channel", "security", "adding", "archived", "direct", "sending", "message", "managing", "the", "conversation", "list", "bubbles", "states", "delivery", "errors", "features", "quick", "chat", "searching", "text", "formatting", "mentions", "reactions", "replying", "day", "separators"],"aliases":["channels", "direct-messages", "messaging", "conversations"],"charCount":23867}, - {"id":"mqtt","title":"MQTT","section":"user","locale":"nl-rNL","resourcePath":"docs/nl-rNL/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "configuration", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12415}, + {"id":"mqtt","title":"MQTT","section":"user","locale":"nl-rNL","resourcePath":"docs/nl-rNL/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "configuration", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12403}, {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"nl-rNL","resourcePath":"docs/nl-rNL/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "device", "environment", "air", "quality", "signaalkwaliteit", "signal", "reference", "power", "traceroute", "reading", "results", "positie", "logboek", "neighbor", "info", "host", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12551}, {"id":"nodes","title":"Nodes","section":"user","locale":"nl-rNL","resourcePath":"docs/nl-rNL/user/nodes.html","navOrder":4,"keywords":["nodes", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "security", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "not", "heard", "your", "current", "settings", "sort", "options", "per"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":23252}, {"id":"onboarding","title":"Getting Started","section":"user","locale":"nl-rNL","resourcePath":"docs/nl-rNL/user/onboarding.html","navOrder":1,"keywords":["getting", "started", "first", "launch", "welcome", "screen", "permissions", "bluetooth", "permission", "location", "notifications", "critical", "alerts", "reviewing", "later", "after", "setup", "related", "topics"],"aliases":["first-launch", "setup", "intro"],"charCount":8461}, - {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"nl-rNL","resourcePath":"docs/nl-rNL/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "module", "configuratie", "mqtt", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon", "tak"],"aliases":["modules", "module-config", "administration"],"charCount":33521}, - {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"nl-rNL","resourcePath":"docs/nl-rNL/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "configuration", "apparaat", "configuratie", "lora", "modem", "presets", "weergave", "positie", "energie", "netwerkconfiguratie", "bluetooth", "beveiligings", "related", "topics"],"aliases":["instellingen", "radio-config", "user-config", "lora"],"charCount":41789}, + {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"nl-rNL","resourcePath":"docs/nl-rNL/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "module", "configuratie", "mqtt", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon", "tak"],"aliases":["modules", "module-config", "administration"],"charCount":33186}, + {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"nl-rNL","resourcePath":"docs/nl-rNL/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "configuration", "apparaat", "configuratie", "lora", "modem", "presets", "weergave", "positie", "energie", "netwerkconfiguratie", "bluetooth", "beveiligings", "related", "topics"],"aliases":["instellingen", "radio-config", "user-config", "lora"],"charCount":42095}, {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"nl-rNL","resourcePath":"docs/nl-rNL/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5239}, {"id":"tak","title":"TAK Integration","section":"user","locale":"nl-rNL","resourcePath":"docs/nl-rNL/user/tak.html","navOrder":10,"keywords":["tak", "integration", "overview", "setup", "prerequisites", "configuration", "local", "server", "roles", "cot", "cursor", "target", "format", "wire", "usage", "with", "atak", "troubleshooting", "security", "considerations", "related", "topics"],"aliases":["tak", "atak", "team-awareness-kit"],"charCount":10705}, {"id":"telemetry-and-sensors","title":"Telemetry and sensors","section":"user","locale":"nl-rNL","resourcePath":"docs/nl-rNL/user/telemetry-and-sensors.html","navOrder":999,"keywords":["telemetry", "and", "sensors", "device", "environment", "temperature", "humidity", "air", "quality", "soil", "light", "weather", "other", "readings", "power", "metrics", "configuring", "choosing", "interval", "viewing", "troubleshooting", "related", "topics"],"aliases":[],"charCount":12294}, @@ -539,17 +539,17 @@ {"id":"connections","title":"Connections","section":"user","locale":"no-rNO","resourcePath":"docs/no-rNO/user/connections.html","navOrder":2,"keywords":["connections", "bluetooth", "ble", "pairing", "radio", "connection", "status", "troubleshooting", "usb", "serial", "setup", "tcp", "network", "connecting", "over", "the", "when", "use", "provisioning", "for", "mpwrd", "after", "your", "first", "reconnection", "behavior", "desktop", "related", "topics"],"aliases":["bluetooth", "usb", "tcp", "pairing"],"charCount":11066}, {"id":"debug-logs","title":"Debug Logs","section":"user","locale":"no-rNO","resourcePath":"docs/no-rNO/user/debug-logs.html","navOrder":22,"keywords":["debug", "logs", "the", "two", "tabs", "viewing", "app", "exporting", "desktop", "related", "topics"],"aliases":["debug-logs", "logcat", "app-logs", "bug-report"],"charCount":3119}, {"id":"desktop","title":"Desktop App","section":"user","locale":"no-rNO","resourcePath":"docs/no-rNO/user/desktop.html","navOrder":14,"keywords":["desktop", "app", "installation", "linux", "macos", "windows", "connecting", "your", "radio", "usb", "serial", "primary", "tcp", "bluetooth", "ble", "feature", "parity", "differences", "keyboard", "shortcuts", "window", "system", "tray", "notification", "preferences", "built", "documentation", "browser", "building", "from"],"aliases":["desktop", "linux", "macos", "windows", "jvm"],"charCount":9955}, - {"id":"discovery","title":"Local Mesh Discovery","section":"user","locale":"no-rNO","resourcePath":"docs/no-rNO/user/discovery.html","navOrder":12,"keywords":["local", "mesh", "discovery", "scanner", "setting", "scan", "live", "progress", "reading", "the", "results", "beacon", "manual", "exploration", "traceroute", "neighbor", "info", "node", "list", "tool", "tips", "for", "related", "topics"],"aliases":["discovery", "local-mesh-discovery", "mesh-discovery", "local-discovery", "network-scan", "traceroute", "neighbor-info"],"charCount":18334}, + {"id":"discovery","title":"Local Mesh Discovery","section":"user","locale":"no-rNO","resourcePath":"docs/no-rNO/user/discovery.html","navOrder":12,"keywords":["local", "mesh", "discovery", "scanner", "setting", "scan", "live", "progress", "reading", "the", "results", "beacon", "manual", "exploration", "traceroute", "neighbor", "info", "node", "list", "tool", "tips", "for", "related", "topics"],"aliases":["discovery", "local-mesh-discovery", "mesh-discovery", "local-discovery", "network-scan", "traceroute", "neighbor-info"],"charCount":18324}, {"id":"firmware","title":"Firmware Updates","section":"user","locale":"no-rNO","resourcePath":"docs/no-rNO/user/firmware.html","navOrder":13,"keywords":["firmware", "updates", "checking", "for", "update", "methods", "ota", "over", "the", "air", "via", "bluetooth", "network", "connected", "esp32", "app", "usb", "factory", "erase", "and", "bootloader", "upgrade", "other", "flashing", "options", "version", "channels", "pre", "checklist", "post"],"aliases":["firmware", "update", "ota", "flash"],"charCount":11096}, {"id":"help-and-docs","title":"Help & In-App Docs","section":"user","locale":"no-rNO","resourcePath":"docs/no-rNO/user/help-and-docs.html","navOrder":21,"keywords":["help", "app", "docs", "browsing", "search", "chirpy", "the", "assistant", "related", "topics"],"aliases":["help", "docs-browser", "chirpy", "assistant"],"charCount":2306}, {"id":"map-and-waypoints","title":"Map & Waypoints","section":"user","locale":"no-rNO","resourcePath":"docs/no-rNO/user/map-and-waypoints.html","navOrder":6,"keywords":["map", "waypoints", "view", "node", "markers", "controls", "filtering", "the", "creating", "waypoint", "properties", "expiration", "geofences", "managing", "layers", "site", "planner", "position", "sharing", "enabling", "privacy", "considerations", "sources", "adding", "your", "own", "tile", "source", "offline", "terrain"],"aliases":["map", "waypoints", "gps", "location", "site-planner", "map-layers", "geojson", "kml"],"charCount":14892}, {"id":"messages-and-channels","title":"Messages & Channels","section":"user","locale":"no-rNO","resourcePath":"docs/no-rNO/user/messages-and-channels.html","navOrder":3,"keywords":["messages", "channels", "default", "channel", "security", "adding", "archived", "direct", "sending", "message", "managing", "the", "conversation", "list", "bubbles", "states", "delivery", "errors", "features", "quick", "chat", "searching", "text", "formatting", "mentions", "reactions", "replying", "day", "separators", "jump"],"aliases":["channels", "direct-messages", "messaging", "conversations"],"charCount":23868}, - {"id":"mqtt","title":"MQTT","section":"user","locale":"no-rNO","resourcePath":"docs/no-rNO/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "configuration", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12415}, + {"id":"mqtt","title":"MQTT","section":"user","locale":"no-rNO","resourcePath":"docs/no-rNO/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "configuration", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12403}, {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"no-rNO","resourcePath":"docs/no-rNO/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "device", "environment", "air", "quality", "signalstyrke", "signal", "reference", "power", "traceroute", "reading", "results", "posisjonslogg", "neighbor", "info", "host", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12565}, {"id":"nodes","title":"Nodes","section":"user","locale":"no-rNO","resourcePath":"docs/no-rNO/user/nodes.html","navOrder":4,"keywords":["nodes", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "security", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "not", "heard", "your", "current", "settings", "sort", "options", "per"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":23248}, {"id":"onboarding","title":"Getting Started","section":"user","locale":"no-rNO","resourcePath":"docs/no-rNO/user/onboarding.html","navOrder":1,"keywords":["getting", "started", "first", "launch", "welcome", "screen", "permissions", "bluetooth", "permission", "location", "notifications", "critical", "alerts", "reviewing", "later", "after", "setup", "related", "topics"],"aliases":["first-launch", "setup", "intro"],"charCount":8461}, - {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"no-rNO","resourcePath":"docs/no-rNO/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "modul", "konfigurasjon", "mqtt", "module", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon"],"aliases":["modules", "module-config", "administration"],"charCount":33467}, - {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"no-rNO","resourcePath":"docs/no-rNO/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "configuration", "device", "config", "lora", "modem", "presets", "display", "position", "power", "network", "bluetooth", "security", "related", "topics"],"aliases":["settings", "radio-config", "user-config", "lora"],"charCount":41641}, + {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"no-rNO","resourcePath":"docs/no-rNO/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "modul", "konfigurasjon", "mqtt", "module", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon"],"aliases":["modules", "module-config", "administration"],"charCount":33121}, + {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"no-rNO","resourcePath":"docs/no-rNO/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "configuration", "device", "config", "lora", "modem", "presets", "display", "position", "power", "network", "bluetooth", "security", "related", "topics"],"aliases":["settings", "radio-config", "user-config", "lora"],"charCount":42001}, {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"no-rNO","resourcePath":"docs/no-rNO/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5269}, {"id":"tak","title":"TAK Integration","section":"user","locale":"no-rNO","resourcePath":"docs/no-rNO/user/tak.html","navOrder":10,"keywords":["tak", "integration", "overview", "setup", "prerequisites", "configuration", "local", "server", "roles", "cot", "cursor", "target", "format", "wire", "usage", "with", "atak", "troubleshooting", "security", "considerations", "related", "topics"],"aliases":["tak", "atak", "team-awareness-kit"],"charCount":10705}, {"id":"telemetry-and-sensors","title":"Telemetry and sensors","section":"user","locale":"no-rNO","resourcePath":"docs/no-rNO/user/telemetry-and-sensors.html","navOrder":999,"keywords":["telemetry", "and", "sensors", "device", "environment", "temperature", "humidity", "air", "quality", "soil", "light", "weather", "other", "readings", "power", "metrics", "configuring", "choosing", "interval", "viewing", "troubleshooting", "related", "topics"],"aliases":[],"charCount":12325}, @@ -560,17 +560,17 @@ {"id":"connections","title":"Connections","section":"user","locale":"pl-rPL","resourcePath":"docs/pl-rPL/user/connections.html","navOrder":2,"keywords":["connections", "bluetooth", "ble", "pairing", "radio", "connection", "status", "troubleshooting", "usb", "serial", "setup", "tcp", "network", "connecting", "over", "the", "when", "use", "provisioning", "for", "mpwrd", "after", "your", "first", "reconnection", "behavior", "desktop", "related", "topics"],"aliases":["bluetooth", "usb", "tcp", "pairing"],"charCount":11108}, {"id":"debug-logs","title":"Debug Logs","section":"user","locale":"pl-rPL","resourcePath":"docs/pl-rPL/user/debug-logs.html","navOrder":22,"keywords":["debug", "logs", "the", "two", "tabs", "viewing", "app", "exporting", "desktop", "related", "topics"],"aliases":["debug-logs", "logcat", "app-logs", "bug-report"],"charCount":3119}, {"id":"desktop","title":"Desktop App","section":"user","locale":"pl-rPL","resourcePath":"docs/pl-rPL/user/desktop.html","navOrder":14,"keywords":["desktop", "app", "installation", "linux", "macos", "windows", "connecting", "your", "radio", "usb", "serial", "primary", "tcp", "bluetooth", "ble", "feature", "parity", "differences", "keyboard", "shortcuts", "window", "system", "tray", "notification", "preferences", "built", "documentation", "browser", "building", "from"],"aliases":["desktop", "linux", "macos", "windows", "jvm"],"charCount":9955}, - {"id":"discovery","title":"Local Mesh Discovery","section":"user","locale":"pl-rPL","resourcePath":"docs/pl-rPL/user/discovery.html","navOrder":12,"keywords":["local", "mesh", "discovery", "scanner", "setting", "scan", "live", "progress", "reading", "the", "results", "beacon", "manual", "exploration", "poka", "tras", "informacje", "siadze", "node", "list", "tool", "tips", "for", "related", "topics"],"aliases":["discovery", "local-mesh-discovery", "mesh-discovery", "local-discovery", "network-scan", "traceroute", "neighbor-info"],"charCount":18343}, + {"id":"discovery","title":"Local Mesh Discovery","section":"user","locale":"pl-rPL","resourcePath":"docs/pl-rPL/user/discovery.html","navOrder":12,"keywords":["local", "mesh", "discovery", "scanner", "setting", "scan", "live", "progress", "reading", "the", "results", "beacon", "manual", "exploration", "poka", "tras", "informacje", "siadze", "node", "list", "tool", "tips", "for", "related", "topics"],"aliases":["discovery", "local-mesh-discovery", "mesh-discovery", "local-discovery", "network-scan", "traceroute", "neighbor-info"],"charCount":18333}, {"id":"firmware","title":"Firmware Updates","section":"user","locale":"pl-rPL","resourcePath":"docs/pl-rPL/user/firmware.html","navOrder":13,"keywords":["firmware", "updates", "checking", "for", "update", "methods", "ota", "over", "the", "air", "via", "bluetooth", "network", "connected", "esp32", "app", "usb", "factory", "erase", "and", "bootloader", "upgrade", "other", "flashing", "options", "version", "channels", "pre", "checklist", "post"],"aliases":["firmware", "update", "ota", "flash"],"charCount":11096}, {"id":"help-and-docs","title":"Help & In-App Docs","section":"user","locale":"pl-rPL","resourcePath":"docs/pl-rPL/user/help-and-docs.html","navOrder":21,"keywords":["help", "app", "docs", "browsing", "search", "chirpy", "the", "assistant", "related", "topics"],"aliases":["help", "docs-browser", "chirpy", "assistant"],"charCount":2306}, {"id":"map-and-waypoints","title":"Map & Waypoints","section":"user","locale":"pl-rPL","resourcePath":"docs/pl-rPL/user/map-and-waypoints.html","navOrder":6,"keywords":["map", "waypoints", "view", "node", "markers", "controls", "filtering", "the", "creating", "waypoint", "properties", "expiration", "geofences", "managing", "warstwy", "site", "planner", "position", "sharing", "enabling", "privacy", "considerations", "sources", "adding", "your", "own", "tile", "source", "offline", "terrain"],"aliases":["map", "waypoints", "gps", "location", "site-planner", "map-layers", "geojson", "kml"],"charCount":14893}, {"id":"messages-and-channels","title":"Messages & Channels","section":"user","locale":"pl-rPL","resourcePath":"docs/pl-rPL/user/messages-and-channels.html","navOrder":3,"keywords":["messages", "channels", "kana", "default", "channel", "bezpiecze", "stwo", "adding", "archived", "bezpo", "rednie", "wiadomo", "sending", "direct", "message", "managing", "the", "conversation", "list", "bubbles", "states", "delivery", "errors", "features", "quick", "chat", "searching", "text", "formatting", "mentions"],"aliases":["channels", "direct-messages", "messaging", "conversations"],"charCount":23879}, - {"id":"mqtt","title":"MQTT","section":"user","locale":"pl-rPL","resourcePath":"docs/pl-rPL/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "konfiguracja", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12414}, + {"id":"mqtt","title":"MQTT","section":"user","locale":"pl-rPL","resourcePath":"docs/pl-rPL/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "konfiguracja", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12402}, {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"pl-rPL","resourcePath":"docs/pl-rPL/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "metryka", "urz", "dzenia", "metryki", "rodowiskowe", "air", "quality", "jako", "sygna", "signal", "reference", "zasilania", "poka", "tras", "reading", "traceroute", "results", "historia", "pozycji", "informacje", "siadze", "statystyki", "hosta", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12731}, {"id":"nodes","title":"Węzły","section":"user","locale":"pl-rPL","resourcePath":"docs/pl-rPL/user/nodes.html","navOrder":4,"keywords":["node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "security", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "nodes", "not", "heard", "your", "current", "settings", "sort", "options", "per"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":23331}, {"id":"onboarding","title":"Getting Started","section":"user","locale":"pl-rPL","resourcePath":"docs/pl-rPL/user/onboarding.html","navOrder":1,"keywords":["getting", "started", "first", "launch", "welcome", "screen", "permissions", "bluetooth", "permission", "location", "notifications", "critical", "alerts", "reviewing", "later", "after", "setup", "related", "topics"],"aliases":["first-launch", "setup", "intro"],"charCount":8596}, - {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"pl-rPL","resourcePath":"docs/pl-rPL/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "ustawienia", "modu", "mqtt", "module", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon"],"aliases":["modules", "module-config", "administration"],"charCount":33983}, - {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"pl-rPL","resourcePath":"docs/pl-rPL/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "konfiguracja", "urz", "dzenia", "lora", "modem", "presets", "wietlacza", "pozycjonowania", "zarz", "dzania", "energi", "sieci", "bluetooth", "zabezpiecze", "related", "topics"],"aliases":["ustawienia", "radio-config", "user-config", "lora"],"charCount":42257}, + {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"pl-rPL","resourcePath":"docs/pl-rPL/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "ustawienia", "modu", "mqtt", "module", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon"],"aliases":["modules", "module-config", "administration"],"charCount":33592}, + {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"pl-rPL","resourcePath":"docs/pl-rPL/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "konfiguracja", "urz", "dzenia", "lora", "modem", "presets", "wietlacza", "pozycjonowania", "zarz", "dzania", "energi", "sieci", "bluetooth", "zabezpiecze", "related", "topics"],"aliases":["ustawienia", "radio-config", "user-config", "lora"],"charCount":42419}, {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"pl-rPL","resourcePath":"docs/pl-rPL/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5281}, {"id":"tak","title":"TAK Integration","section":"user","locale":"pl-rPL","resourcePath":"docs/pl-rPL/user/tak.html","navOrder":10,"keywords":["tak", "integration", "overview", "setup", "prerequisites", "konfiguracja", "local", "server", "roles", "cot", "cursor", "target", "format", "wire", "usage", "with", "atak", "troubleshooting", "security", "considerations", "related", "topics"],"aliases":["tak", "atak", "team-awareness-kit"],"charCount":10704}, {"id":"telemetry-and-sensors","title":"Telemetry and sensors","section":"user","locale":"pl-rPL","resourcePath":"docs/pl-rPL/user/telemetry-and-sensors.html","navOrder":999,"keywords":["telemetry", "and", "sensors", "device", "environment", "temperature", "humidity", "air", "quality", "soil", "light", "weather", "other", "readings", "metryki", "zasilania", "configuring", "choosing", "interval", "metrics", "viewing", "troubleshooting", "related", "topics"],"aliases":[],"charCount":12421}, @@ -581,17 +581,17 @@ {"id":"connections","title":"Conexões","section":"user","locale":"pt-rBR","resourcePath":"docs/pt-rBR/user/connections.html","navOrder":2,"keywords":["conex", "bluetooth", "ble", "pairing", "radio", "connection", "status", "troubleshooting", "usb", "serial", "setup", "tcp", "network", "connecting", "over", "the", "when", "use", "provisioning", "for", "mpwrd", "after", "your", "first", "reconnection", "behavior", "desktop", "connections", "related", "topics"],"aliases":["bluetooth", "usb", "tcp", "pairing"],"charCount":11281}, {"id":"debug-logs","title":"Debug Logs","section":"user","locale":"pt-rBR","resourcePath":"docs/pt-rBR/user/debug-logs.html","navOrder":22,"keywords":["debug", "logs", "the", "two", "tabs", "viewing", "app", "exporting", "desktop", "related", "topics"],"aliases":["debug-logs", "logcat", "app-logs", "bug-report"],"charCount":3119}, {"id":"desktop","title":"Desktop App","section":"user","locale":"pt-rBR","resourcePath":"docs/pt-rBR/user/desktop.html","navOrder":14,"keywords":["desktop", "app", "installation", "linux", "macos", "windows", "connecting", "your", "radio", "usb", "serial", "primary", "tcp", "bluetooth", "ble", "feature", "parity", "differences", "keyboard", "shortcuts", "window", "system", "tray", "notification", "preferences", "built", "documentation", "browser", "building", "from"],"aliases":["desktop", "linux", "macos", "windows", "jvm"],"charCount":9955}, - {"id":"discovery","title":"Local Mesh Discovery","section":"user","locale":"pt-rBR","resourcePath":"docs/pt-rBR/user/discovery.html","navOrder":12,"keywords":["local", "mesh", "discovery", "scanner", "setting", "scan", "live", "progress", "reading", "the", "results", "beacon", "manual", "exploration", "tra", "rota", "informa", "vizinho", "node", "list", "tool", "tips", "for", "related", "topics"],"aliases":["discovery", "local-mesh-discovery", "mesh-discovery", "local-discovery", "network-scan", "traceroute", "neighbor-info"],"charCount":18344}, + {"id":"discovery","title":"Local Mesh Discovery","section":"user","locale":"pt-rBR","resourcePath":"docs/pt-rBR/user/discovery.html","navOrder":12,"keywords":["local", "mesh", "discovery", "scanner", "setting", "scan", "live", "progress", "reading", "the", "results", "beacon", "manual", "exploration", "tra", "rota", "informa", "vizinho", "node", "list", "tool", "tips", "for", "related", "topics"],"aliases":["discovery", "local-mesh-discovery", "mesh-discovery", "local-discovery", "network-scan", "traceroute", "neighbor-info"],"charCount":18334}, {"id":"firmware","title":"Firmware Updates","section":"user","locale":"pt-rBR","resourcePath":"docs/pt-rBR/user/firmware.html","navOrder":13,"keywords":["firmware", "updates", "checking", "for", "update", "methods", "ota", "over", "the", "air", "via", "bluetooth", "network", "connected", "esp32", "app", "usb", "factory", "erase", "and", "bootloader", "upgrade", "other", "flashing", "options", "version", "channels", "pre", "checklist", "post"],"aliases":["firmware", "update", "ota", "flash"],"charCount":11096}, {"id":"help-and-docs","title":"Help & In-App Docs","section":"user","locale":"pt-rBR","resourcePath":"docs/pt-rBR/user/help-and-docs.html","navOrder":21,"keywords":["help", "app", "docs", "browsing", "search", "chirpy", "the", "assistant", "related", "topics"],"aliases":["help", "docs-browser", "chirpy", "assistant"],"charCount":2306}, {"id":"map-and-waypoints","title":"Map & Waypoints","section":"user","locale":"pt-rBR","resourcePath":"docs/pt-rBR/user/map-and-waypoints.html","navOrder":6,"keywords":["map", "waypoints", "view", "node", "markers", "controls", "filtering", "the", "creating", "waypoint", "properties", "expiration", "geofences", "managing", "camadas", "mapa", "site", "planner", "position", "sharing", "enabling", "privacy", "considerations", "sources", "adding", "your", "own", "tile", "source", "offline"],"aliases":["map", "waypoints", "gps", "location", "site-planner", "map-layers", "geojson", "kml"],"charCount":14889}, {"id":"messages-and-channels","title":"Messages & Channels","section":"user","locale":"pt-rBR","resourcePath":"docs/pt-rBR/user/messages-and-channels.html","navOrder":3,"keywords":["messages", "channels", "canais", "default", "channel", "seguran", "canal", "adding", "archived", "direct", "sending", "message", "managing", "the", "conversation", "list", "bubbles", "states", "delivery", "errors", "features", "quick", "chat", "searching", "text", "formatting", "mentions", "reactions", "replying", "day"],"aliases":["channels", "direct-messages", "messaging", "conversations"],"charCount":23868}, - {"id":"mqtt","title":"MQTT","section":"user","locale":"pt-rBR","resourcePath":"docs/pt-rBR/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "configuration", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12415}, + {"id":"mqtt","title":"MQTT","section":"user","locale":"pt-rBR","resourcePath":"docs/pt-rBR/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "configuration", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12403}, {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"pt-rBR","resourcePath":"docs/pt-rBR/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "device", "environment", "air", "quality", "qualidade", "sinal", "signal", "reference", "power", "tra", "rota", "reading", "traceroute", "results", "log", "posi", "informa", "vizinho", "tricas", "host", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12566}, {"id":"nodes","title":"Nós","section":"user","locale":"pt-rBR","resourcePath":"docs/pt-rBR/user/nodes.html","navOrder":4,"keywords":["node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "security", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "nodes", "not", "heard", "your", "current", "settings", "sort", "options", "per"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":23295}, {"id":"onboarding","title":"Getting Started","section":"user","locale":"pt-rBR","resourcePath":"docs/pt-rBR/user/onboarding.html","navOrder":1,"keywords":["getting", "started", "first", "launch", "welcome", "screen", "permissions", "bluetooth", "permission", "location", "notifications", "critical", "alerts", "reviewing", "later", "after", "setup", "related", "topics"],"aliases":["first-launch", "setup", "intro"],"charCount":8516}, - {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"pt-rBR","resourcePath":"docs/pt-rBR/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "configura", "dulos", "mqtt", "module", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon"],"aliases":["modules", "module-config", "administration"],"charCount":33930}, - {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"pt-rBR","resourcePath":"docs/pt-rBR/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "configuration", "configura", "dispositivo", "lora", "modem", "presets", "tela", "posi", "energia", "rede", "bluetooth", "seguran", "related", "topics"],"aliases":["configurações", "radio-config", "user-config", "lora"],"charCount":42095}, + {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"pt-rBR","resourcePath":"docs/pt-rBR/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "configura", "dulos", "mqtt", "module", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon"],"aliases":["modules", "module-config", "administration"],"charCount":33474}, + {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"pt-rBR","resourcePath":"docs/pt-rBR/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "configuration", "configura", "dispositivo", "lora", "modem", "presets", "tela", "posi", "energia", "rede", "bluetooth", "seguran", "related", "topics"],"aliases":["configurações", "radio-config", "user-config", "lora"],"charCount":42311}, {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"pt-rBR","resourcePath":"docs/pt-rBR/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5239}, {"id":"tak","title":"TAK Integration","section":"user","locale":"pt-rBR","resourcePath":"docs/pt-rBR/user/tak.html","navOrder":10,"keywords":["tak", "integration", "overview", "setup", "prerequisites", "configuration", "local", "server", "roles", "cot", "cursor", "target", "format", "wire", "usage", "with", "atak", "troubleshooting", "security", "considerations", "related", "topics"],"aliases":["tak", "atak", "team-awareness-kit"],"charCount":10705}, {"id":"telemetry-and-sensors","title":"Telemetry and sensors","section":"user","locale":"pt-rBR","resourcePath":"docs/pt-rBR/user/telemetry-and-sensors.html","navOrder":999,"keywords":["telemetry", "and", "sensors", "device", "environment", "temperature", "humidity", "air", "quality", "soil", "light", "weather", "other", "readings", "power", "metrics", "configuring", "choosing", "interval", "viewing", "troubleshooting", "related", "topics"],"aliases":[],"charCount":12287}, @@ -602,17 +602,17 @@ {"id":"connections","title":"Ligações","section":"user","locale":"pt-rPT","resourcePath":"docs/pt-rPT/user/connections.html","navOrder":2,"keywords":["liga", "bluetooth", "ble", "pairing", "radio", "connection", "status", "troubleshooting", "usb", "serial", "setup", "tcp", "network", "connecting", "over", "the", "when", "use", "provisioning", "for", "mpwrd", "after", "your", "first", "reconnection", "behavior", "desktop", "connections", "related", "topics"],"aliases":["bluetooth", "usb", "tcp", "pairing"],"charCount":11114}, {"id":"debug-logs","title":"Debug Logs","section":"user","locale":"pt-rPT","resourcePath":"docs/pt-rPT/user/debug-logs.html","navOrder":22,"keywords":["debug", "logs", "the", "two", "tabs", "viewing", "app", "exporting", "desktop", "related", "topics"],"aliases":["debug-logs", "logcat", "app-logs", "bug-report"],"charCount":3119}, {"id":"desktop","title":"Desktop App","section":"user","locale":"pt-rPT","resourcePath":"docs/pt-rPT/user/desktop.html","navOrder":14,"keywords":["desktop", "app", "installation", "linux", "macos", "windows", "connecting", "your", "radio", "usb", "serial", "primary", "tcp", "bluetooth", "ble", "feature", "parity", "differences", "keyboard", "shortcuts", "window", "system", "tray", "notification", "preferences", "built", "documentation", "browser", "building", "from"],"aliases":["desktop", "linux", "macos", "windows", "jvm"],"charCount":9955}, - {"id":"discovery","title":"Local Mesh Discovery","section":"user","locale":"pt-rPT","resourcePath":"docs/pt-rPT/user/discovery.html","navOrder":12,"keywords":["local", "mesh", "discovery", "scanner", "setting", "scan", "live", "progress", "reading", "the", "results", "beacon", "manual", "exploration", "tra", "rota", "informa", "vizinhan", "node", "list", "tool", "tips", "for", "related", "topics"],"aliases":["discovery", "local-mesh-discovery", "mesh-discovery", "local-discovery", "network-scan", "traceroute", "neighbor-info"],"charCount":18347}, + {"id":"discovery","title":"Local Mesh Discovery","section":"user","locale":"pt-rPT","resourcePath":"docs/pt-rPT/user/discovery.html","navOrder":12,"keywords":["local", "mesh", "discovery", "scanner", "setting", "scan", "live", "progress", "reading", "the", "results", "beacon", "manual", "exploration", "tra", "rota", "informa", "vizinhan", "node", "list", "tool", "tips", "for", "related", "topics"],"aliases":["discovery", "local-mesh-discovery", "mesh-discovery", "local-discovery", "network-scan", "traceroute", "neighbor-info"],"charCount":18337}, {"id":"firmware","title":"Firmware Updates","section":"user","locale":"pt-rPT","resourcePath":"docs/pt-rPT/user/firmware.html","navOrder":13,"keywords":["firmware", "updates", "checking", "for", "update", "methods", "ota", "over", "the", "air", "via", "bluetooth", "network", "connected", "esp32", "app", "usb", "factory", "erase", "and", "bootloader", "upgrade", "other", "flashing", "options", "version", "channels", "pre", "checklist", "post"],"aliases":["firmware", "update", "ota", "flash"],"charCount":11096}, {"id":"help-and-docs","title":"Help & In-App Docs","section":"user","locale":"pt-rPT","resourcePath":"docs/pt-rPT/user/help-and-docs.html","navOrder":21,"keywords":["help", "app", "docs", "browsing", "search", "chirpy", "the", "assistant", "related", "topics"],"aliases":["help", "docs-browser", "chirpy", "assistant"],"charCount":2306}, {"id":"map-and-waypoints","title":"Map & Waypoints","section":"user","locale":"pt-rPT","resourcePath":"docs/pt-rPT/user/map-and-waypoints.html","navOrder":6,"keywords":["map", "waypoints", "view", "node", "markers", "controls", "filtering", "the", "creating", "waypoint", "properties", "expiration", "geofences", "managing", "layers", "site", "planner", "position", "sharing", "enabling", "privacy", "considerations", "sources", "adding", "your", "own", "tile", "source", "offline", "terrain"],"aliases":["map", "waypoints", "gps", "location", "site-planner", "map-layers", "geojson", "kml"],"charCount":14884}, {"id":"messages-and-channels","title":"Messages & Channels","section":"user","locale":"pt-rPT","resourcePath":"docs/pt-rPT/user/messages-and-channels.html","navOrder":3,"keywords":["messages", "channels", "canal", "default", "channel", "security", "adding", "archived", "direct", "sending", "message", "managing", "the", "conversation", "list", "bubbles", "states", "delivery", "errors", "features", "quick", "chat", "searching", "text", "formatting", "mentions", "reactions", "replying", "day", "separators"],"aliases":["channels", "direct-messages", "messaging", "conversations"],"charCount":23865}, - {"id":"mqtt","title":"MQTT","section":"user","locale":"pt-rPT","resourcePath":"docs/pt-rPT/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "configura", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12414}, + {"id":"mqtt","title":"MQTT","section":"user","locale":"pt-rPT","resourcePath":"docs/pt-rPT/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "configura", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12402}, {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"pt-rPT","resourcePath":"docs/pt-rPT/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "device", "environment", "air", "quality", "qualidade", "sinal", "signal", "reference", "power", "tra", "rota", "reading", "traceroute", "results", "hist", "rico", "posi", "informa", "vizinhan", "host", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12577}, {"id":"nodes","title":"Nodes","section":"user","locale":"pt-rPT","resourcePath":"docs/pt-rPT/user/nodes.html","navOrder":4,"keywords":["nodes", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "security", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "not", "heard", "your", "current", "settings", "sort", "options", "per"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":23647}, {"id":"onboarding","title":"Getting Started","section":"user","locale":"pt-rPT","resourcePath":"docs/pt-rPT/user/onboarding.html","navOrder":1,"keywords":["getting", "started", "first", "launch", "welcome", "screen", "permissions", "bluetooth", "permission", "location", "notifications", "critical", "alerts", "reviewing", "later", "after", "setup", "related", "topics"],"aliases":["first-launch", "setup", "intro"],"charCount":8461}, - {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"pt-rPT","resourcePath":"docs/pt-rPT/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "configura", "dos", "dulos", "mqtt", "module", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh"],"aliases":["modules", "module-config", "administration"],"charCount":33963}, - {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"pt-rPT","resourcePath":"docs/pt-rPT/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "configura", "dispositivo", "lora", "modem", "presets", "ecr", "posi", "energia", "rede", "bluetooth", "seguran", "related", "topics"],"aliases":["definições", "radio-config", "user-config", "lora"],"charCount":42174}, + {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"pt-rPT","resourcePath":"docs/pt-rPT/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "configura", "dos", "dulos", "mqtt", "module", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh"],"aliases":["modules", "module-config", "administration"],"charCount":33545}, + {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"pt-rPT","resourcePath":"docs/pt-rPT/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "configura", "dispositivo", "lora", "modem", "presets", "ecr", "posi", "energia", "rede", "bluetooth", "seguran", "related", "topics"],"aliases":["definições", "radio-config", "user-config", "lora"],"charCount":42426}, {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"pt-rPT","resourcePath":"docs/pt-rPT/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5251}, {"id":"tak","title":"TAK Integration","section":"user","locale":"pt-rPT","resourcePath":"docs/pt-rPT/user/tak.html","navOrder":10,"keywords":["tak", "integration", "overview", "setup", "prerequisites", "configura", "local", "server", "roles", "cot", "cursor", "target", "format", "wire", "usage", "with", "atak", "troubleshooting", "security", "considerations", "related", "topics"],"aliases":["tak", "atak", "team-awareness-kit"],"charCount":10704}, {"id":"telemetry-and-sensors","title":"Telemetry and sensors","section":"user","locale":"pt-rPT","resourcePath":"docs/pt-rPT/user/telemetry-and-sensors.html","navOrder":999,"keywords":["telemetry", "and", "sensors", "device", "environment", "temperature", "humidity", "air", "quality", "soil", "light", "weather", "other", "readings", "power", "metrics", "configuring", "choosing", "interval", "viewing", "troubleshooting", "related", "topics"],"aliases":[],"charCount":12294}, @@ -623,17 +623,17 @@ {"id":"connections","title":"Connections","section":"user","locale":"ro-rRO","resourcePath":"docs/ro-rRO/user/connections.html","navOrder":2,"keywords":["connections", "bluetooth", "ble", "pairing", "radio", "connection", "status", "troubleshooting", "usb", "serial", "setup", "tcp", "network", "connecting", "over", "the", "when", "use", "provisioning", "for", "mpwrd", "after", "your", "first", "reconnection", "behavior", "desktop", "related", "topics"],"aliases":["bluetooth", "usb", "tcp", "pairing"],"charCount":11144}, {"id":"debug-logs","title":"Debug Logs","section":"user","locale":"ro-rRO","resourcePath":"docs/ro-rRO/user/debug-logs.html","navOrder":22,"keywords":["debug", "logs", "the", "two", "tabs", "viewing", "app", "exporting", "desktop", "related", "topics"],"aliases":["debug-logs", "logcat", "app-logs", "bug-report"],"charCount":3119}, {"id":"desktop","title":"Desktop App","section":"user","locale":"ro-rRO","resourcePath":"docs/ro-rRO/user/desktop.html","navOrder":14,"keywords":["desktop", "app", "installation", "linux", "macos", "windows", "connecting", "your", "radio", "usb", "serial", "primary", "tcp", "bluetooth", "ble", "feature", "parity", "differences", "keyboard", "shortcuts", "window", "system", "tray", "notification", "preferences", "built", "documentation", "browser", "building", "from"],"aliases":["desktop", "linux", "macos", "windows", "jvm"],"charCount":9955}, - {"id":"discovery","title":"Local Mesh Discovery","section":"user","locale":"ro-rRO","resourcePath":"docs/ro-rRO/user/discovery.html","navOrder":12,"keywords":["local", "mesh", "discovery", "scanner", "setting", "scan", "live", "progress", "reading", "the", "results", "beacon", "manual", "exploration", "trasare", "traseu", "informa", "vecin", "node", "list", "tool", "tips", "for", "related", "topics"],"aliases":["discovery", "local-mesh-discovery", "mesh-discovery", "local-discovery", "network-scan", "traceroute", "neighbor-info"],"charCount":18341}, + {"id":"discovery","title":"Local Mesh Discovery","section":"user","locale":"ro-rRO","resourcePath":"docs/ro-rRO/user/discovery.html","navOrder":12,"keywords":["local", "mesh", "discovery", "scanner", "setting", "scan", "live", "progress", "reading", "the", "results", "beacon", "manual", "exploration", "trasare", "traseu", "informa", "vecin", "node", "list", "tool", "tips", "for", "related", "topics"],"aliases":["discovery", "local-mesh-discovery", "mesh-discovery", "local-discovery", "network-scan", "traceroute", "neighbor-info"],"charCount":18331}, {"id":"firmware","title":"Firmware Updates","section":"user","locale":"ro-rRO","resourcePath":"docs/ro-rRO/user/firmware.html","navOrder":13,"keywords":["firmware", "updates", "checking", "for", "update", "methods", "ota", "over", "the", "air", "via", "bluetooth", "network", "connected", "esp32", "app", "usb", "factory", "erase", "and", "bootloader", "upgrade", "other", "flashing", "options", "version", "channels", "pre", "checklist", "post"],"aliases":["firmware", "update", "ota", "flash"],"charCount":11106}, {"id":"help-and-docs","title":"Help & In-App Docs","section":"user","locale":"ro-rRO","resourcePath":"docs/ro-rRO/user/help-and-docs.html","navOrder":21,"keywords":["help", "app", "docs", "browsing", "search", "chirpy", "the", "assistant", "related", "topics"],"aliases":["help", "docs-browser", "chirpy", "assistant"],"charCount":2306}, {"id":"map-and-waypoints","title":"Map & Waypoints","section":"user","locale":"ro-rRO","resourcePath":"docs/ro-rRO/user/map-and-waypoints.html","navOrder":6,"keywords":["map", "waypoints", "view", "node", "markers", "controls", "filtering", "the", "creating", "waypoint", "properties", "expiration", "geofences", "managing", "layers", "site", "planner", "position", "sharing", "enabling", "privacy", "considerations", "sources", "adding", "your", "own", "tile", "source", "offline", "terrain"],"aliases":["map", "waypoints", "gps", "location", "site-planner", "map-layers", "geojson", "kml"],"charCount":14884}, {"id":"messages-and-channels","title":"Messages & Channels","section":"user","locale":"ro-rRO","resourcePath":"docs/ro-rRO/user/messages-and-channels.html","navOrder":3,"keywords":["messages", "channels", "canale", "default", "channel", "securitate", "canal", "adding", "archived", "direct", "sending", "message", "managing", "the", "conversation", "list", "bubbles", "states", "delivery", "errors", "features", "quick", "chat", "searching", "text", "formatting", "mentions", "reactions", "replying", "day"],"aliases":["channels", "direct-messages", "messaging", "conversations"],"charCount":23866}, - {"id":"mqtt","title":"MQTT","section":"user","locale":"ro-rRO","resourcePath":"docs/ro-rRO/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "configuration", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12415}, + {"id":"mqtt","title":"MQTT","section":"user","locale":"ro-rRO","resourcePath":"docs/ro-rRO/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "configuration", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12403}, {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"ro-rRO","resourcePath":"docs/ro-rRO/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "valori", "dispozitiv", "indicatori", "mediu", "air", "quality", "calitatea", "semnalului", "signal", "reference", "putere", "trasare", "traseu", "reading", "traceroute", "results", "position", "log", "informa", "vecin", "gazd", "sur", "tori", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12641}, {"id":"nodes","title":"Noduri","section":"user","locale":"ro-rRO","resourcePath":"docs/ro-rRO/user/nodes.html","navOrder":4,"keywords":["noduri", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "security", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "nodes", "not", "heard", "your", "current", "settings", "sort", "options"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":23291}, {"id":"onboarding","title":"Getting Started","section":"user","locale":"ro-rRO","resourcePath":"docs/ro-rRO/user/onboarding.html","navOrder":1,"keywords":["getting", "started", "first", "launch", "welcome", "screen", "permissions", "bluetooth", "permission", "location", "notifications", "critical", "alerts", "reviewing", "later", "after", "setup", "related", "topics"],"aliases":["first-launch", "setup", "intro"],"charCount":8481}, - {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"ro-rRO","resourcePath":"docs/ro-rRO/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "configurare", "modul", "mqtt", "module", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon"],"aliases":["modules", "module-config", "administration"],"charCount":34058}, - {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"ro-rRO","resourcePath":"docs/ro-rRO/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "configuration", "device", "config", "lora", "modem", "presets", "display", "position", "configurare", "putere", "network", "bluetooth", "security", "related", "topics"],"aliases":["setari", "radio-config", "user-config", "lora"],"charCount":42118}, + {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"ro-rRO","resourcePath":"docs/ro-rRO/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "configurare", "modul", "mqtt", "module", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon"],"aliases":["modules", "module-config", "administration"],"charCount":33709}, + {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"ro-rRO","resourcePath":"docs/ro-rRO/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "configuration", "device", "config", "lora", "modem", "presets", "display", "position", "configurare", "putere", "network", "bluetooth", "security", "related", "topics"],"aliases":["setari", "radio-config", "user-config", "lora"],"charCount":42280}, {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"ro-rRO","resourcePath":"docs/ro-rRO/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5263}, {"id":"tak","title":"TAK Integration","section":"user","locale":"ro-rRO","resourcePath":"docs/ro-rRO/user/tak.html","navOrder":10,"keywords":["tak", "integration", "overview", "setup", "prerequisites", "configuration", "local", "server", "roles", "cot", "cursor", "target", "format", "wire", "usage", "with", "atak", "troubleshooting", "security", "considerations", "related", "topics"],"aliases":["tak", "atak", "team-awareness-kit"],"charCount":10725}, {"id":"telemetry-and-sensors","title":"Telemetry and sensors","section":"user","locale":"ro-rRO","resourcePath":"docs/ro-rRO/user/telemetry-and-sensors.html","navOrder":999,"keywords":["telemetry", "and", "sensors", "device", "environment", "temperature", "humidity", "air", "quality", "soil", "light", "weather", "other", "readings", "valori", "putere", "configuring", "choosing", "interval", "metrics", "viewing", "troubleshooting", "related", "topics"],"aliases":[],"charCount":12335}, @@ -644,17 +644,17 @@ {"id":"connections","title":"Соединения","section":"user","locale":"ru-rRU","resourcePath":"docs/ru-rRU/user/connections.html","navOrder":2,"keywords":["bluetooth", "ble", "pairing", "radio", "usb", "troubleshooting", "tcp", "mpwrd", "after", "your", "first", "connection"],"aliases":["bluetooth", "usb", "tcp", "pairing"],"charCount":11485}, {"id":"debug-logs","title":"Отладочные журналы","section":"user","locale":"ru-rRU","resourcePath":"docs/ru-rRU/user/debug-logs.html","navOrder":22,"keywords":["desktop"],"aliases":["debug-logs", "logcat", "app-logs", "bug-report"],"charCount":3625}, {"id":"desktop","title":"Настольное приложение","section":"user","locale":"ru-rRU","resourcePath":"docs/ru-rRU/user/desktop.html","navOrder":14,"keywords":["linux", "macos", "windows", "usb", "tcp", "bluetooth", "ble"],"aliases":["desktop", "linux", "macos", "windows", "jvm"],"charCount":10365}, - {"id":"discovery","title":"Локальное обнаружение сети","section":"user","locale":"ru-rRU","resourcePath":"docs/ru-rRU/user/discovery.html","navOrder":12,"keywords":["setting", "scan", "live", "progress", "reading", "the", "results", "manual", "exploration", "node", "list", "discovery", "tool", "tips", "for", "mesh"],"aliases":["discovery", "local-mesh-discovery", "mesh-discovery", "local-discovery", "network-scan", "traceroute", "neighbor-info"],"charCount":19396}, + {"id":"discovery","title":"Локальное обнаружение сети","section":"user","locale":"ru-rRU","resourcePath":"docs/ru-rRU/user/discovery.html","navOrder":12,"keywords":["setting", "scan", "live", "progress", "reading", "the", "results", "manual", "exploration", "node", "list", "discovery", "tool", "tips", "for", "mesh"],"aliases":["discovery", "local-mesh-discovery", "mesh-discovery", "local-discovery", "network-scan", "traceroute", "neighbor-info"],"charCount":19386}, {"id":"firmware","title":"Обновления прошивки","section":"user","locale":"ru-rRU","resourcePath":"docs/ru-rRU/user/firmware.html","navOrder":13,"keywords":["ota", "bluetooth", "via", "network", "connected", "esp32", "usb", "radio", "won", "boot", "after", "update"],"aliases":["firmware", "update", "ota", "flash"],"charCount":11625}, {"id":"help-and-docs","title":"Справка и встроенная документация","section":"user","locale":"ru-rRU","resourcePath":"docs/ru-rRU/user/help-and-docs.html","navOrder":21,"keywords":["chirpy"],"aliases":["help", "docs-browser", "chirpy", "assistant"],"charCount":2547}, {"id":"map-and-waypoints","title":"Карта и путевые точки","section":"user","locale":"ru-rRU","resourcePath":"docs/ru-rRU/user/map-and-waypoints.html","navOrder":6,"keywords":["filtering", "the", "map", "adding", "your", "own", "tile", "source", "offline", "terrain", "going"],"aliases":["map", "waypoints", "gps", "location", "site-planner", "map-layers", "geojson", "kml"],"charCount":15695}, {"id":"messages-and-channels","title":"Сообщения и каналы","section":"user","locale":"ru-rRU","resourcePath":"docs/ru-rRU/user/messages-and-channels.html","navOrder":3,"keywords":["archived", "channels", "managing", "the", "conversation", "list", "bubbles", "replying", "day", "separators", "jump", "latest"],"aliases":["channels", "direct-messages", "messaging", "conversations"],"charCount":25026}, - {"id":"mqtt","title":"MQTT","section":"user","locale":"ru-rRU","resourcePath":"docs/ru-rRU/user/mqtt.html","navOrder":11,"keywords":["mqtt", "connection", "status", "and", "test", "meshtastic", "uplink", "downlink"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12899}, + {"id":"mqtt","title":"MQTT","section":"user","locale":"ru-rRU","resourcePath":"docs/ru-rRU/user/mqtt.html","navOrder":11,"keywords":["mqtt", "connection", "status", "and", "test", "meshtastic", "uplink", "downlink"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12887}, {"id":"node-metrics","title":"Метрики ноды","section":"user","locale":"ru-rRU","resourcePath":"docs/ru-rRU/user/node-metrics.html","navOrder":5,"keywords":[],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":13654}, {"id":"nodes","title":"Ноды","section":"user","locale":"ru-rRU","resourcePath":"docs/ru-rRU/user/nodes.html","navOrder":4,"keywords":["node", "list", "choosing", "what", "the", "shows", "status", "indicators", "role", "security", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "nodes", "not", "heard", "your", "current", "settings", "sort", "options", "per", "hop", "detail", "hardware"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":23936}, {"id":"onboarding","title":"Начало работы","section":"user","locale":"ru-rRU","resourcePath":"docs/ru-rRU/user/onboarding.html","navOrder":1,"keywords":["bluetooth", "reviewing", "permissions", "later"],"aliases":["first-launch", "setup", "intro"],"charCount":8982}, - {"id":"settings-module-admin","title":"Настройки — Модули и администрирование","section":"user","locale":"ru-rRU","resourcePath":"docs/ru-rRU/user/settings-module-admin.html","navOrder":8,"keywords":["mqtt", "module", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon", "tak", "device", "actions", "app", "settings"],"aliases":["modules", "module-config", "administration"],"charCount":35402}, - {"id":"settings-radio-user","title":"Настройки - Радио и пользователь","section":"user","locale":"ru-rRU","resourcePath":"docs/ru-rRU/user/settings-radio-user.html","navOrder":7,"keywords":["how", "these", "screens", "work", "applying", "changes", "lora", "modem", "presets", "bluetooth"],"aliases":["настройки", "radio-config", "user-config", "lora"],"charCount":43205}, + {"id":"settings-module-admin","title":"Настройки — Модули и администрирование","section":"user","locale":"ru-rRU","resourcePath":"docs/ru-rRU/user/settings-module-admin.html","navOrder":8,"keywords":["mqtt", "module", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon", "tak", "device", "actions", "app", "settings"],"aliases":["modules", "module-config", "administration"],"charCount":34918}, + {"id":"settings-radio-user","title":"Настройки - Радио и пользователь","section":"user","locale":"ru-rRU","resourcePath":"docs/ru-rRU/user/settings-radio-user.html","navOrder":7,"keywords":["how", "these", "screens", "work", "applying", "changes", "lora", "modem", "presets", "bluetooth"],"aliases":["настройки", "radio-config", "user-config", "lora"],"charCount":43421}, {"id":"signal-meter","title":"Как работает измеритель сигнала Meshtastic","section":"user","locale":"ru-rRU","resourcePath":"docs/ru-rRU/user/signal-meter.html","navOrder":15,"keywords":["meshtastic", "rssi", "and", "snr", "decoding", "below", "the", "noise", "floor", "rating", "signal", "quality", "diagnosing", "local", "interference"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5368}, {"id":"tak","title":"Интеграция TAK","section":"user","locale":"ru-rRU","resourcePath":"docs/ru-rRU/user/tak.html","navOrder":10,"keywords":["tak", "cot", "cursor", "target", "atak"],"aliases":["tak", "atak", "team-awareness-kit"],"charCount":11528}, {"id":"telemetry-and-sensors","title":"Telemetry and sensors","section":"user","locale":"ru-rRU","resourcePath":"docs/ru-rRU/user/telemetry-and-sensors.html","navOrder":999,"keywords":["telemetry", "and", "sensors", "soil", "weather", "other", "readings", "choosing", "interval"],"aliases":[],"charCount":12791}, @@ -665,17 +665,17 @@ {"id":"connections","title":"Connections","section":"user","locale":"sk-rSK","resourcePath":"docs/sk-rSK/user/connections.html","navOrder":2,"keywords":["connections", "bluetooth", "ble", "pairing", "radio", "connection", "status", "troubleshooting", "usb", "serial", "setup", "tcp", "network", "connecting", "over", "the", "when", "use", "provisioning", "for", "mpwrd", "after", "your", "first", "reconnection", "behavior", "desktop", "related", "topics"],"aliases":["bluetooth", "usb", "tcp", "pairing"],"charCount":11114}, {"id":"debug-logs","title":"Debug Logs","section":"user","locale":"sk-rSK","resourcePath":"docs/sk-rSK/user/debug-logs.html","navOrder":22,"keywords":["debug", "logs", "the", "two", "tabs", "viewing", "app", "exporting", "desktop", "related", "topics"],"aliases":["debug-logs", "logcat", "app-logs", "bug-report"],"charCount":3119}, {"id":"desktop","title":"Desktop App","section":"user","locale":"sk-rSK","resourcePath":"docs/sk-rSK/user/desktop.html","navOrder":14,"keywords":["desktop", "app", "installation", "linux", "macos", "windows", "connecting", "your", "radio", "usb", "serial", "primary", "tcp", "bluetooth", "ble", "feature", "parity", "differences", "keyboard", "shortcuts", "window", "system", "tray", "notification", "preferences", "built", "documentation", "browser", "building", "from"],"aliases":["desktop", "linux", "macos", "windows", "jvm"],"charCount":9955}, - {"id":"discovery","title":"Local Mesh Discovery","section":"user","locale":"sk-rSK","resourcePath":"docs/sk-rSK/user/discovery.html","navOrder":12,"keywords":["local", "mesh", "discovery", "scanner", "setting", "scan", "live", "progress", "reading", "the", "results", "beacon", "manual", "exploration", "trasovanie", "inform", "cia", "susedoch", "node", "list", "tool", "tips", "for", "related", "topics"],"aliases":["discovery", "local-mesh-discovery", "mesh-discovery", "local-discovery", "network-scan", "traceroute", "neighbor-info"],"charCount":18342}, + {"id":"discovery","title":"Local Mesh Discovery","section":"user","locale":"sk-rSK","resourcePath":"docs/sk-rSK/user/discovery.html","navOrder":12,"keywords":["local", "mesh", "discovery", "scanner", "setting", "scan", "live", "progress", "reading", "the", "results", "beacon", "manual", "exploration", "trasovanie", "inform", "cia", "susedoch", "node", "list", "tool", "tips", "for", "related", "topics"],"aliases":["discovery", "local-mesh-discovery", "mesh-discovery", "local-discovery", "network-scan", "traceroute", "neighbor-info"],"charCount":18332}, {"id":"firmware","title":"Firmware Updates","section":"user","locale":"sk-rSK","resourcePath":"docs/sk-rSK/user/firmware.html","navOrder":13,"keywords":["firmware", "updates", "checking", "for", "update", "methods", "ota", "over", "the", "air", "via", "bluetooth", "network", "connected", "esp32", "app", "usb", "factory", "erase", "and", "bootloader", "upgrade", "other", "flashing", "options", "version", "channels", "pre", "checklist", "post"],"aliases":["firmware", "update", "ota", "flash"],"charCount":11096}, {"id":"help-and-docs","title":"Help & In-App Docs","section":"user","locale":"sk-rSK","resourcePath":"docs/sk-rSK/user/help-and-docs.html","navOrder":21,"keywords":["help", "app", "docs", "browsing", "search", "chirpy", "the", "assistant", "related", "topics"],"aliases":["help", "docs-browser", "chirpy", "assistant"],"charCount":2306}, {"id":"map-and-waypoints","title":"Map & Waypoints","section":"user","locale":"sk-rSK","resourcePath":"docs/sk-rSK/user/map-and-waypoints.html","navOrder":6,"keywords":["map", "waypoints", "view", "node", "markers", "controls", "filtering", "the", "creating", "waypoint", "properties", "expiration", "geofences", "managing", "layers", "site", "planner", "position", "sharing", "enabling", "privacy", "considerations", "sources", "adding", "your", "own", "tile", "source", "offline", "terrain"],"aliases":["map", "waypoints", "gps", "location", "site-planner", "map-layers", "geojson", "kml"],"charCount":14884}, {"id":"messages-and-channels","title":"Messages & Channels","section":"user","locale":"sk-rSK","resourcePath":"docs/sk-rSK/user/messages-and-channels.html","navOrder":3,"keywords":["messages", "channels", "kan", "default", "channel", "security", "adding", "archived", "direct", "sending", "message", "managing", "the", "conversation", "list", "bubbles", "states", "delivery", "errors", "features", "quick", "chat", "searching", "text", "formatting", "mentions", "reactions", "replying", "day", "separators"],"aliases":["channels", "direct-messages", "messaging", "conversations"],"charCount":23866}, - {"id":"mqtt","title":"MQTT","section":"user","locale":"sk-rSK","resourcePath":"docs/sk-rSK/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "configuration", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12415}, + {"id":"mqtt","title":"MQTT","section":"user","locale":"sk-rSK","resourcePath":"docs/sk-rSK/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "configuration", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12403}, {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"sk-rSK","resourcePath":"docs/sk-rSK/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "device", "environment", "air", "quality", "kvalita", "sign", "signal", "reference", "power", "trasovanie", "reading", "traceroute", "results", "log", "poz", "cie", "inform", "cia", "susedoch", "host", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12576}, {"id":"nodes","title":"Nodes","section":"user","locale":"sk-rSK","resourcePath":"docs/sk-rSK/user/nodes.html","navOrder":4,"keywords":["nodes", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "security", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "not", "heard", "your", "current", "settings", "sort", "options", "per"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":23334}, {"id":"onboarding","title":"Getting Started","section":"user","locale":"sk-rSK","resourcePath":"docs/sk-rSK/user/onboarding.html","navOrder":1,"keywords":["getting", "started", "first", "launch", "welcome", "screen", "permissions", "bluetooth", "permission", "location", "notifications", "critical", "alerts", "reviewing", "later", "after", "setup", "related", "topics"],"aliases":["first-launch", "setup", "intro"],"charCount":8461}, - {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"sk-rSK","resourcePath":"docs/sk-rSK/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "konfigur", "cia", "modulu", "mqtt", "module", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh"],"aliases":["modules", "module-config", "administration"],"charCount":33557}, - {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"sk-rSK","resourcePath":"docs/sk-rSK/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "configuration", "konfigur", "cia", "zariadenia", "lora", "modem", "presets", "displeju", "position", "config", "power", "siete", "bluetooth", "security", "related", "topics"],"aliases":["nastavenia", "radio-config", "user-config", "lora"],"charCount":41696}, + {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"sk-rSK","resourcePath":"docs/sk-rSK/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "konfigur", "cia", "modulu", "mqtt", "module", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh"],"aliases":["modules", "module-config", "administration"],"charCount":33216}, + {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"sk-rSK","resourcePath":"docs/sk-rSK/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "configuration", "konfigur", "cia", "zariadenia", "lora", "modem", "presets", "displeju", "position", "config", "power", "siete", "bluetooth", "security", "related", "topics"],"aliases":["nastavenia", "radio-config", "user-config", "lora"],"charCount":42056}, {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"sk-rSK","resourcePath":"docs/sk-rSK/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5257}, {"id":"tak","title":"TAK Integration","section":"user","locale":"sk-rSK","resourcePath":"docs/sk-rSK/user/tak.html","navOrder":10,"keywords":["tak", "integration", "overview", "setup", "prerequisites", "configuration", "local", "server", "roles", "cot", "cursor", "target", "format", "wire", "usage", "with", "atak", "troubleshooting", "security", "considerations", "related", "topics"],"aliases":["tak", "atak", "team-awareness-kit"],"charCount":10705}, {"id":"telemetry-and-sensors","title":"Telemetry and sensors","section":"user","locale":"sk-rSK","resourcePath":"docs/sk-rSK/user/telemetry-and-sensors.html","navOrder":999,"keywords":["telemetry", "and", "sensors", "device", "environment", "temperature", "humidity", "air", "quality", "soil", "light", "weather", "other", "readings", "power", "metrics", "configuring", "choosing", "interval", "viewing", "troubleshooting", "related", "topics"],"aliases":[],"charCount":12241}, @@ -686,17 +686,17 @@ {"id":"connections","title":"Connections","section":"user","locale":"sl-rSI","resourcePath":"docs/sl-rSI/user/connections.html","navOrder":2,"keywords":["connections", "bluetooth", "ble", "pairing", "radio", "connection", "status", "troubleshooting", "usb", "serial", "setup", "tcp", "network", "connecting", "over", "the", "when", "use", "provisioning", "for", "mpwrd", "after", "your", "first", "reconnection", "behavior", "desktop", "related", "topics"],"aliases":["bluetooth", "usb", "tcp", "pairing"],"charCount":11126}, {"id":"debug-logs","title":"Debug Logs","section":"user","locale":"sl-rSI","resourcePath":"docs/sl-rSI/user/debug-logs.html","navOrder":22,"keywords":["debug", "logs", "the", "two", "tabs", "viewing", "app", "exporting", "desktop", "related", "topics"],"aliases":["debug-logs", "logcat", "app-logs", "bug-report"],"charCount":3119}, {"id":"desktop","title":"Desktop App","section":"user","locale":"sl-rSI","resourcePath":"docs/sl-rSI/user/desktop.html","navOrder":14,"keywords":["desktop", "app", "installation", "linux", "macos", "windows", "connecting", "your", "radio", "usb", "serial", "primary", "tcp", "bluetooth", "ble", "feature", "parity", "differences", "keyboard", "shortcuts", "window", "system", "tray", "notification", "preferences", "built", "documentation", "browser", "building", "from"],"aliases":["desktop", "linux", "macos", "windows", "jvm"],"charCount":9955}, - {"id":"discovery","title":"Local Mesh Discovery","section":"user","locale":"sl-rSI","resourcePath":"docs/sl-rSI/user/discovery.html","navOrder":12,"keywords":["local", "mesh", "discovery", "scanner", "setting", "scan", "live", "progress", "reading", "the", "results", "beacon", "manual", "exploration", "pot", "neighbor", "info", "node", "list", "tool", "tips", "for", "related", "topics"],"aliases":["discovery", "local-mesh-discovery", "mesh-discovery", "local-discovery", "network-scan", "traceroute", "neighbor-info"],"charCount":18327}, + {"id":"discovery","title":"Local Mesh Discovery","section":"user","locale":"sl-rSI","resourcePath":"docs/sl-rSI/user/discovery.html","navOrder":12,"keywords":["local", "mesh", "discovery", "scanner", "setting", "scan", "live", "progress", "reading", "the", "results", "beacon", "manual", "exploration", "pot", "neighbor", "info", "node", "list", "tool", "tips", "for", "related", "topics"],"aliases":["discovery", "local-mesh-discovery", "mesh-discovery", "local-discovery", "network-scan", "traceroute", "neighbor-info"],"charCount":18317}, {"id":"firmware","title":"Firmware Updates","section":"user","locale":"sl-rSI","resourcePath":"docs/sl-rSI/user/firmware.html","navOrder":13,"keywords":["firmware", "updates", "checking", "for", "update", "methods", "ota", "over", "the", "air", "via", "bluetooth", "network", "connected", "esp32", "app", "usb", "factory", "erase", "and", "bootloader", "upgrade", "other", "flashing", "options", "version", "channels", "pre", "checklist", "post"],"aliases":["firmware", "update", "ota", "flash"],"charCount":11096}, {"id":"help-and-docs","title":"Help & In-App Docs","section":"user","locale":"sl-rSI","resourcePath":"docs/sl-rSI/user/help-and-docs.html","navOrder":21,"keywords":["help", "app", "docs", "browsing", "search", "chirpy", "the", "assistant", "related", "topics"],"aliases":["help", "docs-browser", "chirpy", "assistant"],"charCount":2306}, {"id":"map-and-waypoints","title":"Map & Waypoints","section":"user","locale":"sl-rSI","resourcePath":"docs/sl-rSI/user/map-and-waypoints.html","navOrder":6,"keywords":["map", "waypoints", "view", "node", "markers", "controls", "filtering", "the", "creating", "waypoint", "properties", "expiration", "geofences", "managing", "layers", "site", "planner", "position", "sharing", "enabling", "privacy", "considerations", "sources", "adding", "your", "own", "tile", "source", "offline", "terrain"],"aliases":["map", "waypoints", "gps", "location", "site-planner", "map-layers", "geojson", "kml"],"charCount":14884}, {"id":"messages-and-channels","title":"Messages & Channels","section":"user","locale":"sl-rSI","resourcePath":"docs/sl-rSI/user/messages-and-channels.html","navOrder":3,"keywords":["messages", "channels", "default", "channel", "security", "adding", "archived", "direct", "sending", "message", "managing", "the", "conversation", "list", "bubbles", "states", "delivery", "errors", "features", "quick", "chat", "searching", "text", "formatting", "mentions", "reactions", "replying", "day", "separators", "jump"],"aliases":["channels", "direct-messages", "messaging", "conversations"],"charCount":23868}, - {"id":"mqtt","title":"MQTT","section":"user","locale":"sl-rSI","resourcePath":"docs/sl-rSI/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "configuration", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12415}, + {"id":"mqtt","title":"MQTT","section":"user","locale":"sl-rSI","resourcePath":"docs/sl-rSI/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "configuration", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12403}, {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"sl-rSI","resourcePath":"docs/sl-rSI/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "device", "environment", "air", "quality", "kakovost", "signala", "signal", "reference", "power", "pot", "reading", "traceroute", "results", "dnevnik", "lokacije", "neighbor", "info", "host", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12553}, {"id":"nodes","title":"Nodes","section":"user","locale":"sl-rSI","resourcePath":"docs/sl-rSI/user/nodes.html","navOrder":4,"keywords":["nodes", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "security", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "not", "heard", "your", "current", "settings", "sort", "options", "per"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":23265}, {"id":"onboarding","title":"Getting Started","section":"user","locale":"sl-rSI","resourcePath":"docs/sl-rSI/user/onboarding.html","navOrder":1,"keywords":["getting", "started", "first", "launch", "welcome", "screen", "permissions", "bluetooth", "permission", "location", "notifications", "critical", "alerts", "reviewing", "later", "after", "setup", "related", "topics"],"aliases":["first-launch", "setup", "intro"],"charCount":8461}, - {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"sl-rSI","resourcePath":"docs/sl-rSI/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "nastavitev", "modula", "mqtt", "module", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon"],"aliases":["modules", "module-config", "administration"],"charCount":33490}, - {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"sl-rSI","resourcePath":"docs/sl-rSI/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "configuration", "device", "config", "lora", "modem", "presets", "display", "position", "power", "network", "bluetooth", "security", "related", "topics"],"aliases":["settings", "radio-config", "user-config", "lora"],"charCount":41641}, + {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"sl-rSI","resourcePath":"docs/sl-rSI/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "nastavitev", "modula", "mqtt", "module", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon"],"aliases":["modules", "module-config", "administration"],"charCount":33144}, + {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"sl-rSI","resourcePath":"docs/sl-rSI/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "configuration", "device", "config", "lora", "modem", "presets", "display", "position", "power", "network", "bluetooth", "security", "related", "topics"],"aliases":["settings", "radio-config", "user-config", "lora"],"charCount":42001}, {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"sl-rSI","resourcePath":"docs/sl-rSI/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5257}, {"id":"tak","title":"TAK Integration","section":"user","locale":"sl-rSI","resourcePath":"docs/sl-rSI/user/tak.html","navOrder":10,"keywords":["tak", "integration", "overview", "setup", "prerequisites", "configuration", "local", "server", "roles", "cot", "cursor", "target", "format", "wire", "usage", "with", "atak", "troubleshooting", "security", "considerations", "related", "topics"],"aliases":["tak", "atak", "team-awareness-kit"],"charCount":10705}, {"id":"telemetry-and-sensors","title":"Telemetry and sensors","section":"user","locale":"sl-rSI","resourcePath":"docs/sl-rSI/user/telemetry-and-sensors.html","navOrder":999,"keywords":["telemetry", "and", "sensors", "device", "environment", "temperature", "humidity", "air", "quality", "soil", "light", "weather", "other", "readings", "power", "metrics", "configuring", "choosing", "interval", "viewing", "troubleshooting", "related", "topics"],"aliases":[],"charCount":12276}, @@ -707,17 +707,17 @@ {"id":"connections","title":"Connections","section":"user","locale":"sq-rAL","resourcePath":"docs/sq-rAL/user/connections.html","navOrder":2,"keywords":["connections", "bluetooth", "ble", "pairing", "radio", "connection", "status", "troubleshooting", "usb", "serial", "setup", "tcp", "network", "connecting", "over", "the", "when", "use", "provisioning", "for", "mpwrd", "after", "your", "first", "reconnection", "behavior", "desktop", "related", "topics"],"aliases":["bluetooth", "usb", "tcp", "pairing"],"charCount":11084}, {"id":"debug-logs","title":"Debug Logs","section":"user","locale":"sq-rAL","resourcePath":"docs/sq-rAL/user/debug-logs.html","navOrder":22,"keywords":["debug", "logs", "the", "two", "tabs", "viewing", "app", "exporting", "desktop", "related", "topics"],"aliases":["debug-logs", "logcat", "app-logs", "bug-report"],"charCount":3119}, {"id":"desktop","title":"Desktop App","section":"user","locale":"sq-rAL","resourcePath":"docs/sq-rAL/user/desktop.html","navOrder":14,"keywords":["desktop", "app", "installation", "linux", "macos", "windows", "connecting", "your", "radio", "usb", "serial", "primary", "tcp", "bluetooth", "ble", "feature", "parity", "differences", "keyboard", "shortcuts", "window", "system", "tray", "notification", "preferences", "built", "documentation", "browser", "building", "from"],"aliases":["desktop", "linux", "macos", "windows", "jvm"],"charCount":9955}, - {"id":"discovery","title":"Local Mesh Discovery","section":"user","locale":"sq-rAL","resourcePath":"docs/sq-rAL/user/discovery.html","navOrder":12,"keywords":["local", "mesh", "discovery", "scanner", "setting", "scan", "live", "progress", "reading", "the", "results", "beacon", "manual", "exploration", "traceroute", "neighbor", "info", "node", "list", "tool", "tips", "for", "related", "topics"],"aliases":["discovery", "local-mesh-discovery", "mesh-discovery", "local-discovery", "network-scan", "traceroute", "neighbor-info"],"charCount":18334}, + {"id":"discovery","title":"Local Mesh Discovery","section":"user","locale":"sq-rAL","resourcePath":"docs/sq-rAL/user/discovery.html","navOrder":12,"keywords":["local", "mesh", "discovery", "scanner", "setting", "scan", "live", "progress", "reading", "the", "results", "beacon", "manual", "exploration", "traceroute", "neighbor", "info", "node", "list", "tool", "tips", "for", "related", "topics"],"aliases":["discovery", "local-mesh-discovery", "mesh-discovery", "local-discovery", "network-scan", "traceroute", "neighbor-info"],"charCount":18324}, {"id":"firmware","title":"Firmware Updates","section":"user","locale":"sq-rAL","resourcePath":"docs/sq-rAL/user/firmware.html","navOrder":13,"keywords":["firmware", "updates", "checking", "for", "update", "methods", "ota", "over", "the", "air", "via", "bluetooth", "network", "connected", "esp32", "app", "usb", "factory", "erase", "and", "bootloader", "upgrade", "other", "flashing", "options", "version", "channels", "pre", "checklist", "post"],"aliases":["firmware", "update", "ota", "flash"],"charCount":11096}, {"id":"help-and-docs","title":"Help & In-App Docs","section":"user","locale":"sq-rAL","resourcePath":"docs/sq-rAL/user/help-and-docs.html","navOrder":21,"keywords":["help", "app", "docs", "browsing", "search", "chirpy", "the", "assistant", "related", "topics"],"aliases":["help", "docs-browser", "chirpy", "assistant"],"charCount":2306}, {"id":"map-and-waypoints","title":"Map & Waypoints","section":"user","locale":"sq-rAL","resourcePath":"docs/sq-rAL/user/map-and-waypoints.html","navOrder":6,"keywords":["map", "waypoints", "view", "node", "markers", "controls", "filtering", "the", "creating", "waypoint", "properties", "expiration", "geofences", "managing", "layers", "site", "planner", "position", "sharing", "enabling", "privacy", "considerations", "sources", "adding", "your", "own", "tile", "source", "offline", "terrain"],"aliases":["map", "waypoints", "gps", "location", "site-planner", "map-layers", "geojson", "kml"],"charCount":14884}, {"id":"messages-and-channels","title":"Messages & Channels","section":"user","locale":"sq-rAL","resourcePath":"docs/sq-rAL/user/messages-and-channels.html","navOrder":3,"keywords":["messages", "channels", "default", "channel", "security", "adding", "archived", "direct", "sending", "message", "managing", "the", "conversation", "list", "bubbles", "states", "delivery", "errors", "features", "quick", "chat", "searching", "text", "formatting", "mentions", "reactions", "replying", "day", "separators", "jump"],"aliases":["channels", "direct-messages", "messaging", "conversations"],"charCount":23868}, - {"id":"mqtt","title":"MQTT","section":"user","locale":"sq-rAL","resourcePath":"docs/sq-rAL/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "configuration", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12415}, + {"id":"mqtt","title":"MQTT","section":"user","locale":"sq-rAL","resourcePath":"docs/sq-rAL/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "configuration", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12403}, {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"sq-rAL","resourcePath":"docs/sq-rAL/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "device", "environment", "air", "quality", "cil", "sia", "sinjalit", "signal", "reference", "power", "traceroute", "reading", "results", "regjistri", "pozit", "neighbor", "info", "host", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12553}, {"id":"nodes","title":"Nodes","section":"user","locale":"sq-rAL","resourcePath":"docs/sq-rAL/user/nodes.html","navOrder":4,"keywords":["nodes", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "security", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "not", "heard", "your", "current", "settings", "sort", "options", "per"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":23288}, {"id":"onboarding","title":"Getting Started","section":"user","locale":"sq-rAL","resourcePath":"docs/sq-rAL/user/onboarding.html","navOrder":1,"keywords":["getting", "started", "first", "launch", "welcome", "screen", "permissions", "bluetooth", "permission", "location", "notifications", "critical", "alerts", "reviewing", "later", "after", "setup", "related", "topics"],"aliases":["first-launch", "setup", "intro"],"charCount":8461}, - {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"sq-rAL","resourcePath":"docs/sq-rAL/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "konfigurimi", "modulit", "mqtt", "module", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon"],"aliases":["modules", "module-config", "administration"],"charCount":33395}, - {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"sq-rAL","resourcePath":"docs/sq-rAL/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "configuration", "device", "config", "lora", "modem", "presets", "display", "position", "power", "network", "bluetooth", "security", "related", "topics"],"aliases":["settings", "radio-config", "user-config", "lora"],"charCount":41641}, + {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"sq-rAL","resourcePath":"docs/sq-rAL/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "konfigurimi", "modulit", "mqtt", "module", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon"],"aliases":["modules", "module-config", "administration"],"charCount":33049}, + {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"sq-rAL","resourcePath":"docs/sq-rAL/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "configuration", "device", "config", "lora", "modem", "presets", "display", "position", "power", "network", "bluetooth", "security", "related", "topics"],"aliases":["settings", "radio-config", "user-config", "lora"],"charCount":42001}, {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"sq-rAL","resourcePath":"docs/sq-rAL/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5245}, {"id":"tak","title":"TAK Integration","section":"user","locale":"sq-rAL","resourcePath":"docs/sq-rAL/user/tak.html","navOrder":10,"keywords":["tak", "integration", "overview", "setup", "prerequisites", "configuration", "local", "server", "roles", "cot", "cursor", "target", "format", "wire", "usage", "with", "atak", "troubleshooting", "security", "considerations", "related", "topics"],"aliases":["tak", "atak", "team-awareness-kit"],"charCount":10705}, {"id":"telemetry-and-sensors","title":"Telemetry and sensors","section":"user","locale":"sq-rAL","resourcePath":"docs/sq-rAL/user/telemetry-and-sensors.html","navOrder":999,"keywords":["telemetry", "and", "sensors", "device", "environment", "temperature", "humidity", "air", "quality", "soil", "light", "weather", "other", "readings", "power", "metrics", "configuring", "choosing", "interval", "viewing", "troubleshooting", "related", "topics"],"aliases":[],"charCount":12304}, @@ -728,17 +728,17 @@ {"id":"connections","title":"Connections","section":"user","locale":"srp","resourcePath":"docs/srp/user/connections.html","navOrder":2,"keywords":["connections", "bluetooth", "ble", "pairing", "radio", "connection", "status", "troubleshooting", "usb", "serial", "setup", "tcp", "network", "connecting", "over", "the", "when", "use", "provisioning", "for", "mpwrd", "after", "your", "first", "reconnection", "behavior", "desktop", "related", "topics"],"aliases":["bluetooth", "usb", "tcp", "pairing"],"charCount":11168}, {"id":"debug-logs","title":"Дебаг логови","section":"user","locale":"srp","resourcePath":"docs/srp/user/debug-logs.html","navOrder":22,"keywords":["the", "two", "tabs", "viewing", "app", "logs", "exporting", "desktop", "related", "topics"],"aliases":["debug-logs", "logcat", "app-logs", "bug-report"],"charCount":3123}, {"id":"desktop","title":"Desktop App","section":"user","locale":"srp","resourcePath":"docs/srp/user/desktop.html","navOrder":14,"keywords":["desktop", "app", "installation", "linux", "macos", "windows", "connecting", "your", "radio", "usb", "serial", "primary", "tcp", "bluetooth", "ble", "feature", "parity", "differences", "keyboard", "shortcuts", "window", "system", "tray", "notification", "preferences", "built", "documentation", "browser", "building", "from"],"aliases":["desktop", "linux", "macos", "windows", "jvm"],"charCount":9955}, - {"id":"discovery","title":"Local Mesh Discovery","section":"user","locale":"srp","resourcePath":"docs/srp/user/discovery.html","navOrder":12,"keywords":["local", "mesh", "discovery", "scanner", "setting", "scan", "live", "progress", "reading", "the", "results", "beacon", "manual", "exploration", "neighbor", "info", "node", "list", "tool", "tips", "for", "related", "topics"],"aliases":["discovery", "local-mesh-discovery", "mesh-discovery", "local-discovery", "network-scan", "traceroute", "neighbor-info"],"charCount":18336}, + {"id":"discovery","title":"Local Mesh Discovery","section":"user","locale":"srp","resourcePath":"docs/srp/user/discovery.html","navOrder":12,"keywords":["local", "mesh", "discovery", "scanner", "setting", "scan", "live", "progress", "reading", "the", "results", "beacon", "manual", "exploration", "neighbor", "info", "node", "list", "tool", "tips", "for", "related", "topics"],"aliases":["discovery", "local-mesh-discovery", "mesh-discovery", "local-discovery", "network-scan", "traceroute", "neighbor-info"],"charCount":18326}, {"id":"firmware","title":"Ажурирања фирмвера","section":"user","locale":"srp","resourcePath":"docs/srp/user/firmware.html","navOrder":13,"keywords":["checking", "for", "updates", "update", "methods", "ota", "over", "the", "air", "via", "bluetooth", "network", "connected", "esp32", "app", "usb", "factory", "erase", "and", "bootloader", "upgrade", "other", "flashing", "options", "version", "channels", "pre", "checklist", "post", "troubleshooting"],"aliases":["firmware", "update", "ota", "flash"],"charCount":11100}, {"id":"help-and-docs","title":"Help & In-App Docs","section":"user","locale":"srp","resourcePath":"docs/srp/user/help-and-docs.html","navOrder":21,"keywords":["help", "app", "docs", "browsing", "chirpy", "the", "assistant", "related", "topics"],"aliases":["help", "docs-browser", "chirpy", "assistant"],"charCount":2308}, {"id":"map-and-waypoints","title":"Map & Waypoints","section":"user","locale":"srp","resourcePath":"docs/srp/user/map-and-waypoints.html","navOrder":6,"keywords":["map", "waypoints", "view", "node", "markers", "controls", "filtering", "the", "creating", "waypoint", "properties", "expiration", "geofences", "managing", "layers", "site", "planner", "position", "sharing", "enabling", "privacy", "considerations", "sources", "adding", "your", "own", "tile", "source", "offline", "terrain"],"aliases":["map", "waypoints", "gps", "location", "site-planner", "map-layers", "geojson", "kml"],"charCount":14884}, {"id":"messages-and-channels","title":"Messages & Channels","section":"user","locale":"srp","resourcePath":"docs/srp/user/messages-and-channels.html","navOrder":3,"keywords":["messages", "channels", "default", "channel", "security", "adding", "archived", "sending", "direct", "message", "managing", "the", "conversation", "list", "bubbles", "states", "delivery", "errors", "features", "quick", "chat", "searching", "text", "formatting", "mentions", "reactions", "replying", "day", "separators", "jump"],"aliases":["channels", "direct-messages", "messaging", "conversations"],"charCount":23866}, - {"id":"mqtt","title":"MQTT","section":"user","locale":"srp","resourcePath":"docs/srp/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "configuration", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12415}, + {"id":"mqtt","title":"MQTT","section":"user","locale":"srp","resourcePath":"docs/srp/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "configuration", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12403}, {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"srp","resourcePath":"docs/srp/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "air", "quality", "signal", "reference", "reading", "traceroute", "results", "neighbor", "info", "host", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12569}, {"id":"nodes","title":"Чворови","section":"user","locale":"srp","resourcePath":"docs/srp/user/nodes.html","navOrder":4,"keywords":["node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "security", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "nodes", "not", "heard", "your", "current", "settings", "sort", "options", "per"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":23296}, {"id":"onboarding","title":"Getting Started","section":"user","locale":"srp","resourcePath":"docs/srp/user/onboarding.html","navOrder":1,"keywords":["getting", "started", "first", "launch", "welcome", "screen", "permissions", "bluetooth", "permission", "location", "notifications", "critical", "alerts", "reviewing", "later", "after", "setup", "related", "topics"],"aliases":["first-launch", "setup", "intro"],"charCount":8461}, - {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"srp","resourcePath":"docs/srp/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "mqtt", "module", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon", "tak", "device"],"aliases":["modules", "module-config", "administration"],"charCount":33509}, - {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"srp","resourcePath":"docs/srp/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "configuration", "lora", "modem", "presets", "related", "topics"],"aliases":["подешавања", "radio-config", "user-config", "lora"],"charCount":42114}, + {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"srp","resourcePath":"docs/srp/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "mqtt", "module", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon", "tak", "device"],"aliases":["modules", "module-config", "administration"],"charCount":33168}, + {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"srp","resourcePath":"docs/srp/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "configuration", "lora", "modem", "presets", "related", "topics"],"aliases":["подешавања", "radio-config", "user-config", "lora"],"charCount":42240}, {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"srp","resourcePath":"docs/srp/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5263}, {"id":"tak","title":"TAK Integration","section":"user","locale":"srp","resourcePath":"docs/srp/user/tak.html","navOrder":10,"keywords":["tak", "integration", "overview", "setup", "prerequisites", "configuration", "local", "server", "roles", "cot", "cursor", "target", "format", "wire", "usage", "with", "atak", "troubleshooting", "security", "considerations", "related", "topics"],"aliases":["tak", "atak", "team-awareness-kit"],"charCount":10705}, {"id":"telemetry-and-sensors","title":"Telemetry and sensors","section":"user","locale":"srp","resourcePath":"docs/srp/user/telemetry-and-sensors.html","navOrder":999,"keywords":["telemetry", "and", "sensors", "device", "environment", "temperature", "humidity", "air", "quality", "soil", "light", "weather", "other", "readings", "configuring", "choosing", "interval", "metrics", "viewing", "troubleshooting", "related", "topics"],"aliases":[],"charCount":12301}, @@ -749,17 +749,17 @@ {"id":"connections","title":"Connections","section":"user","locale":"sv-rSE","resourcePath":"docs/sv-rSE/user/connections.html","navOrder":2,"keywords":["connections", "bluetooth", "ble", "pairing", "radio", "connection", "status", "troubleshooting", "usb", "serial", "setup", "tcp", "network", "connecting", "over", "the", "when", "use", "provisioning", "for", "mpwrd", "after", "your", "first", "reconnection", "behavior", "desktop", "related", "topics"],"aliases":["bluetooth", "usb", "tcp", "pairing"],"charCount":11102}, {"id":"debug-logs","title":"Debug Logs","section":"user","locale":"sv-rSE","resourcePath":"docs/sv-rSE/user/debug-logs.html","navOrder":22,"keywords":["debug", "logs", "the", "two", "tabs", "viewing", "app", "exporting", "desktop", "related", "topics"],"aliases":["debug-logs", "logcat", "app-logs", "bug-report"],"charCount":3122}, {"id":"desktop","title":"Desktop App","section":"user","locale":"sv-rSE","resourcePath":"docs/sv-rSE/user/desktop.html","navOrder":14,"keywords":["desktop", "app", "installation", "linux", "macos", "windows", "connecting", "your", "radio", "usb", "serial", "primary", "tcp", "bluetooth", "ble", "feature", "parity", "differences", "keyboard", "shortcuts", "window", "system", "tray", "notification", "preferences", "built", "documentation", "browser", "building", "from"],"aliases":["desktop", "linux", "macos", "windows", "jvm"],"charCount":9955}, - {"id":"discovery","title":"Local Mesh Discovery","section":"user","locale":"sv-rSE","resourcePath":"docs/sv-rSE/user/discovery.html","navOrder":12,"keywords":["local", "mesh", "discovery", "scanner", "setting", "scan", "live", "progress", "reading", "the", "results", "beacon", "manual", "exploration", "traceroute", "rutt", "granninformation", "node", "list", "tool", "tips", "for", "related", "topics"],"aliases":["discovery", "local-mesh-discovery", "mesh-discovery", "local-discovery", "network-scan", "traceroute", "neighbor-info"],"charCount":18350}, + {"id":"discovery","title":"Local Mesh Discovery","section":"user","locale":"sv-rSE","resourcePath":"docs/sv-rSE/user/discovery.html","navOrder":12,"keywords":["local", "mesh", "discovery", "scanner", "setting", "scan", "live", "progress", "reading", "the", "results", "beacon", "manual", "exploration", "traceroute", "rutt", "granninformation", "node", "list", "tool", "tips", "for", "related", "topics"],"aliases":["discovery", "local-mesh-discovery", "mesh-discovery", "local-discovery", "network-scan", "traceroute", "neighbor-info"],"charCount":18340}, {"id":"firmware","title":"Firmware Updates","section":"user","locale":"sv-rSE","resourcePath":"docs/sv-rSE/user/firmware.html","navOrder":13,"keywords":["firmware", "updates", "checking", "for", "update", "methods", "ota", "over", "the", "air", "via", "bluetooth", "network", "connected", "esp32", "app", "usb", "factory", "erase", "and", "bootloader", "upgrade", "other", "flashing", "options", "version", "channels", "pre", "checklist", "post"],"aliases":["firmware", "update", "ota", "flash"],"charCount":11111}, {"id":"help-and-docs","title":"Help & In-App Docs","section":"user","locale":"sv-rSE","resourcePath":"docs/sv-rSE/user/help-and-docs.html","navOrder":21,"keywords":["help", "app", "docs", "browsing", "search", "chirpy", "the", "assistant", "related", "topics"],"aliases":["help", "docs-browser", "chirpy", "assistant"],"charCount":2309}, {"id":"map-and-waypoints","title":"Map & Waypoints","section":"user","locale":"sv-rSE","resourcePath":"docs/sv-rSE/user/map-and-waypoints.html","navOrder":6,"keywords":["map", "waypoints", "view", "node", "markers", "controls", "filtering", "the", "creating", "waypoint", "properties", "expiration", "geofences", "managing", "kartlager", "site", "planner", "position", "sharing", "enabling", "privacy", "considerations", "sources", "adding", "your", "own", "tile", "source", "offline", "terrain"],"aliases":["map", "waypoints", "gps", "location", "site-planner", "map-layers", "geojson", "kml"],"charCount":14891}, {"id":"messages-and-channels","title":"Messages & Channels","section":"user","locale":"sv-rSE","resourcePath":"docs/sv-rSE/user/messages-and-channels.html","navOrder":3,"keywords":["messages", "channels", "kanaler", "default", "channel", "kanals", "kerhet", "adding", "archived", "direct", "sending", "message", "managing", "the", "conversation", "list", "bubbles", "states", "delivery", "errors", "features", "quick", "chat", "searching", "text", "formatting", "mentions", "reactions", "replying", "day"],"aliases":["channels", "direct-messages", "messaging", "conversations"],"charCount":23864}, - {"id":"mqtt","title":"MQTT","section":"user","locale":"sv-rSE","resourcePath":"docs/sv-rSE/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "konfiguration", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "fels", "kning", "not"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12410}, + {"id":"mqtt","title":"MQTT","section":"user","locale":"sv-rSE","resourcePath":"docs/sv-rSE/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "konfiguration", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "fels", "kning", "not"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12398}, {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"sv-rSE","resourcePath":"docs/sv-rSE/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "enhetens", "rden", "milj", "air", "quality", "signalkvalit", "signal", "reference", "str", "mdata", "traceroute", "rutt", "reading", "results", "position", "loggbok", "granninformation", "beg", "rdens", "pax", "nyckeltal", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12566}, {"id":"nodes","title":"Noder","section":"user","locale":"sv-rSE","resourcePath":"docs/sv-rSE/user/nodes.html","navOrder":4,"keywords":["noder", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "security", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "nodes", "not", "heard", "your", "current", "settings", "sort", "options"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":23250}, {"id":"onboarding","title":"Kom igång","section":"user","locale":"sv-rSE","resourcePath":"docs/sv-rSE/user/onboarding.html","navOrder":1,"keywords":["kom", "first", "launch", "welcome", "screen", "permissions", "bluetooth", "permission", "location", "notifications", "critical", "alerts", "reviewing", "later", "after", "setup", "related", "topics"],"aliases":["first-launch", "setup", "intro"],"charCount":8459}, - {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"sv-rSE","resourcePath":"docs/sv-rSE/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "modul", "konfiguration", "mqtt", "module", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon"],"aliases":["modules", "module-config", "administration"],"charCount":34197}, - {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"sv-rSE","resourcePath":"docs/sv-rSE/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "anv", "ndarinst", "llningar", "profile", "applying", "changes", "konfiguration", "enhetskonfiguration", "lora", "config", "modem", "presets", "display", "position", "str", "minst", "network", "bluetooth", "inst", "security", "related", "topics"],"aliases":["inställningar", "radio-config", "user-config", "lora"],"charCount":42023}, + {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"sv-rSE","resourcePath":"docs/sv-rSE/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "modul", "konfiguration", "mqtt", "module", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon"],"aliases":["modules", "module-config", "administration"],"charCount":33927}, + {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"sv-rSE","resourcePath":"docs/sv-rSE/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "anv", "ndarinst", "llningar", "profile", "applying", "changes", "konfiguration", "enhetskonfiguration", "lora", "config", "modem", "presets", "display", "position", "str", "minst", "network", "bluetooth", "inst", "security", "related", "topics"],"aliases":["inställningar", "radio-config", "user-config", "lora"],"charCount":42203}, {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"sv-rSE","resourcePath":"docs/sv-rSE/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5233}, {"id":"tak","title":"TAK Integration","section":"user","locale":"sv-rSE","resourcePath":"docs/sv-rSE/user/tak.html","navOrder":10,"keywords":["tak", "integration", "overview", "setup", "prerequisites", "konfiguration", "local", "server", "roles", "cot", "cursor", "target", "format", "wire", "usage", "with", "atak", "fels", "kning", "security", "considerations", "related", "topics"],"aliases":["tak", "atak", "team-awareness-kit"],"charCount":10700}, {"id":"telemetry-and-sensors","title":"Telemetry and sensors","section":"user","locale":"sv-rSE","resourcePath":"docs/sv-rSE/user/telemetry-and-sensors.html","navOrder":999,"keywords":["telemetry", "and", "sensors", "device", "environment", "temperature", "humidity", "air", "quality", "soil", "light", "weather", "other", "readings", "str", "mdata", "configuring", "choosing", "interval", "metrics", "viewing", "fels", "kning", "related", "topics"],"aliases":[],"charCount":12331}, @@ -770,17 +770,17 @@ {"id":"connections","title":"Bağlantılar","section":"user","locale":"tr-rTR","resourcePath":"docs/tr-rTR/user/connections.html","navOrder":2,"keywords":["lant", "lar", "bluetooth", "ble", "pairing", "radio", "connection", "status", "troubleshooting", "usb", "serial", "setup", "tcp", "network", "connecting", "over", "the", "when", "use", "provisioning", "for", "mpwrd", "after", "your", "first", "reconnection", "behavior", "desktop", "connections", "related"],"aliases":["bluetooth", "usb", "tcp", "pairing"],"charCount":11120}, {"id":"debug-logs","title":"Debug Logs","section":"user","locale":"tr-rTR","resourcePath":"docs/tr-rTR/user/debug-logs.html","navOrder":22,"keywords":["debug", "logs", "the", "two", "tabs", "viewing", "app", "exporting", "desktop", "related", "topics"],"aliases":["debug-logs", "logcat", "app-logs", "bug-report"],"charCount":3119}, {"id":"desktop","title":"Desktop App","section":"user","locale":"tr-rTR","resourcePath":"docs/tr-rTR/user/desktop.html","navOrder":14,"keywords":["desktop", "app", "installation", "linux", "macos", "windows", "connecting", "your", "radio", "usb", "serial", "primary", "tcp", "bluetooth", "ble", "feature", "parity", "differences", "keyboard", "shortcuts", "window", "system", "tray", "notification", "preferences", "built", "documentation", "browser", "building", "from"],"aliases":["desktop", "linux", "macos", "windows", "jvm"],"charCount":9955}, - {"id":"discovery","title":"Local Mesh Discovery","section":"user","locale":"tr-rTR","resourcePath":"docs/tr-rTR/user/discovery.html","navOrder":12,"keywords":["local", "mesh", "discovery", "scanner", "setting", "scan", "live", "progress", "reading", "the", "results", "beacon", "manual", "exploration", "yol", "izle", "kom", "bilgisi", "node", "list", "tool", "tips", "for", "related", "topics"],"aliases":["discovery", "local-mesh-discovery", "mesh-discovery", "local-discovery", "network-scan", "traceroute", "neighbor-info"],"charCount":18332}, + {"id":"discovery","title":"Local Mesh Discovery","section":"user","locale":"tr-rTR","resourcePath":"docs/tr-rTR/user/discovery.html","navOrder":12,"keywords":["local", "mesh", "discovery", "scanner", "setting", "scan", "live", "progress", "reading", "the", "results", "beacon", "manual", "exploration", "yol", "izle", "kom", "bilgisi", "node", "list", "tool", "tips", "for", "related", "topics"],"aliases":["discovery", "local-mesh-discovery", "mesh-discovery", "local-discovery", "network-scan", "traceroute", "neighbor-info"],"charCount":18322}, {"id":"firmware","title":"Firmware Updates","section":"user","locale":"tr-rTR","resourcePath":"docs/tr-rTR/user/firmware.html","navOrder":13,"keywords":["firmware", "updates", "checking", "for", "update", "methods", "ota", "over", "the", "air", "via", "bluetooth", "network", "connected", "esp32", "app", "usb", "factory", "erase", "and", "bootloader", "upgrade", "other", "flashing", "options", "version", "channels", "pre", "checklist", "post"],"aliases":["firmware", "update", "Kablosuz Güncelleme", "flash"],"charCount":11112}, {"id":"help-and-docs","title":"Help & In-App Docs","section":"user","locale":"tr-rTR","resourcePath":"docs/tr-rTR/user/help-and-docs.html","navOrder":21,"keywords":["help", "app", "docs", "browsing", "search", "chirpy", "the", "assistant", "related", "topics"],"aliases":["help", "docs-browser", "chirpy", "assistant"],"charCount":2306}, {"id":"map-and-waypoints","title":"Map & Waypoints","section":"user","locale":"tr-rTR","resourcePath":"docs/tr-rTR/user/map-and-waypoints.html","navOrder":6,"keywords":["map", "waypoints", "view", "node", "markers", "controls", "filtering", "the", "creating", "waypoint", "properties", "expiration", "geofences", "managing", "layers", "site", "planner", "position", "sharing", "enabling", "privacy", "considerations", "sources", "adding", "your", "own", "tile", "source", "offline", "terrain"],"aliases":["map", "waypoints", "gps", "location", "site-planner", "map-layers", "geojson", "kml"],"charCount":14884}, {"id":"messages-and-channels","title":"Messages & Channels","section":"user","locale":"tr-rTR","resourcePath":"docs/tr-rTR/user/messages-and-channels.html","navOrder":3,"keywords":["messages", "channels", "kanallar", "default", "channel", "security", "adding", "archived", "direct", "sending", "message", "managing", "the", "conversation", "list", "bubbles", "states", "delivery", "errors", "features", "quick", "chat", "searching", "text", "formatting", "mentions", "reactions", "replying", "day", "separators"],"aliases":["channels", "direct-messages", "messaging", "conversations"],"charCount":23868}, - {"id":"mqtt","title":"MQTT","section":"user","locale":"tr-rTR","resourcePath":"docs/tr-rTR/user/mqtt.html","navOrder":11,"keywords":["mqtt", "genel", "bak", "how", "works", "yap", "land", "rma", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12417}, + {"id":"mqtt","title":"MQTT","section":"user","locale":"tr-rTR","resourcePath":"docs/tr-rTR/user/mqtt.html","navOrder":11,"keywords":["mqtt", "genel", "bak", "how", "works", "yap", "land", "rma", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12405}, {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"tr-rTR","resourcePath":"docs/tr-rTR/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "device", "environment", "air", "quality", "sinyal", "kalitesi", "signal", "reference", "power", "yol", "izle", "reading", "traceroute", "results", "konum", "kay", "tlar", "kom", "bilgisi", "sunucu", "mleri", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12566}, {"id":"nodes","title":"Nodelar","section":"user","locale":"tr-rTR","resourcePath":"docs/tr-rTR/user/nodes.html","navOrder":4,"keywords":["nodelar", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "security", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "nodes", "not", "heard", "your", "current", "settings", "sort", "options"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":23253}, {"id":"onboarding","title":"Getting Started","section":"user","locale":"tr-rTR","resourcePath":"docs/tr-rTR/user/onboarding.html","navOrder":1,"keywords":["getting", "started", "first", "launch", "welcome", "screen", "permissions", "bluetooth", "permission", "location", "notifications", "critical", "alerts", "reviewing", "later", "after", "setup", "related", "topics"],"aliases":["first-launch", "setup", "intro"],"charCount":8461}, - {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"tr-rTR","resourcePath":"docs/tr-rTR/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "mod", "ayarlar", "mqtt", "module", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon"],"aliases":["modules", "module-config", "administration"],"charCount":33477}, - {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"tr-rTR","resourcePath":"docs/tr-rTR/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "yap", "land", "rma", "cihaz", "ayar", "lora", "modem", "presets", "akran", "konum", "bluetooth", "venlik", "related", "topics"],"aliases":["ayarlar", "radio-config", "user-config", "lora"],"charCount":41890}, + {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"tr-rTR","resourcePath":"docs/tr-rTR/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "mod", "ayarlar", "mqtt", "module", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon"],"aliases":["modules", "module-config", "administration"],"charCount":33238}, + {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"tr-rTR","resourcePath":"docs/tr-rTR/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "yap", "land", "rma", "cihaz", "ayar", "lora", "modem", "presets", "akran", "konum", "bluetooth", "venlik", "related", "topics"],"aliases":["ayarlar", "radio-config", "user-config", "lora"],"charCount":42088}, {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"tr-rTR","resourcePath":"docs/tr-rTR/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5263}, {"id":"tak","title":"TAK Integration","section":"user","locale":"tr-rTR","resourcePath":"docs/tr-rTR/user/tak.html","navOrder":10,"keywords":["tak", "integration", "genel", "bak", "setup", "prerequisites", "yap", "land", "rma", "local", "server", "roles", "cot", "cursor", "target", "format", "wire", "usage", "with", "atak", "troubleshooting", "security", "considerations", "related", "topics"],"aliases":["tak", "atak", "team-awareness-kit"],"charCount":10707}, {"id":"telemetry-and-sensors","title":"Telemetry and sensors","section":"user","locale":"tr-rTR","resourcePath":"docs/tr-rTR/user/telemetry-and-sensors.html","navOrder":999,"keywords":["telemetry", "and", "sensors", "device", "environment", "temperature", "humidity", "air", "quality", "soil", "light", "weather", "other", "readings", "power", "metrics", "configuring", "choosing", "interval", "viewing", "troubleshooting", "related", "topics"],"aliases":[],"charCount":12230}, @@ -791,16 +791,16 @@ {"id":"connections","title":"Connections","section":"user","locale":"uk-rUA","resourcePath":"docs/uk-rUA/user/connections.html","navOrder":2,"keywords":["connections", "bluetooth", "ble", "pairing", "radio", "connection", "status", "troubleshooting", "usb", "serial", "setup", "tcp", "network", "connecting", "over", "the", "when", "use", "mpwrd", "after", "your", "first", "reconnection", "behavior", "desktop", "related", "topics"],"aliases":["bluetooth", "usb", "tcp", "pairing"],"charCount":11126}, {"id":"debug-logs","title":"Debug Logs","section":"user","locale":"uk-rUA","resourcePath":"docs/uk-rUA/user/debug-logs.html","navOrder":22,"keywords":["debug", "logs", "the", "two", "tabs", "viewing", "app", "exporting", "desktop", "related", "topics"],"aliases":["debug-logs", "logcat", "app-logs", "bug-report"],"charCount":3129}, {"id":"desktop","title":"Desktop App","section":"user","locale":"uk-rUA","resourcePath":"docs/uk-rUA/user/desktop.html","navOrder":14,"keywords":["desktop", "app", "installation", "linux", "macos", "windows", "connecting", "your", "radio", "usb", "serial", "primary", "tcp", "bluetooth", "ble", "feature", "parity", "differences", "keyboard", "shortcuts", "window", "system", "tray", "notification", "preferences", "built", "documentation", "browser", "building", "from"],"aliases":["desktop", "linux", "macos", "windows", "jvm"],"charCount":9955}, - {"id":"discovery","title":"Local Mesh Discovery","section":"user","locale":"uk-rUA","resourcePath":"docs/uk-rUA/user/discovery.html","navOrder":12,"keywords":["local", "mesh", "discovery", "scanner", "setting", "scan", "live", "progress", "reading", "the", "results", "beacon", "manual", "exploration", "node", "list", "tool", "tips", "for", "related", "topics"],"aliases":["discovery", "local-mesh-discovery", "mesh-discovery", "local-discovery", "network-scan", "traceroute", "neighbor-info"],"charCount":18340}, + {"id":"discovery","title":"Local Mesh Discovery","section":"user","locale":"uk-rUA","resourcePath":"docs/uk-rUA/user/discovery.html","navOrder":12,"keywords":["local", "mesh", "discovery", "scanner", "setting", "scan", "live", "progress", "reading", "the", "results", "beacon", "manual", "exploration", "node", "list", "tool", "tips", "for", "related", "topics"],"aliases":["discovery", "local-mesh-discovery", "mesh-discovery", "local-discovery", "network-scan", "traceroute", "neighbor-info"],"charCount":18330}, {"id":"firmware","title":"Firmware Updates","section":"user","locale":"uk-rUA","resourcePath":"docs/uk-rUA/user/firmware.html","navOrder":13,"keywords":["firmware", "updates", "checking", "for", "update", "methods", "ota", "over", "the", "air", "via", "bluetooth", "network", "connected", "esp32", "app", "usb", "factory", "erase", "and", "bootloader", "upgrade", "other", "flashing", "options", "version", "channels", "pre", "checklist", "post"],"aliases":["firmware", "update", "ota", "flash"],"charCount":11091}, {"id":"help-and-docs","title":"Help & In-App Docs","section":"user","locale":"uk-rUA","resourcePath":"docs/uk-rUA/user/help-and-docs.html","navOrder":21,"keywords":["help", "app", "docs", "browsing", "search", "chirpy", "the", "assistant", "related", "topics"],"aliases":["help", "docs-browser", "chirpy", "assistant"],"charCount":2316}, {"id":"map-and-waypoints","title":"Map & Waypoints","section":"user","locale":"uk-rUA","resourcePath":"docs/uk-rUA/user/map-and-waypoints.html","navOrder":6,"keywords":["map", "waypoints", "view", "node", "markers", "controls", "filtering", "the", "creating", "waypoint", "properties", "expiration", "geofences", "managing", "site", "planner", "position", "sharing", "enabling", "privacy", "considerations", "sources", "adding", "your", "own", "tile", "source", "offline", "terrain", "going"],"aliases":["map", "waypoints", "gps", "location", "site-planner", "map-layers", "geojson", "kml"],"charCount":14883}, {"id":"messages-and-channels","title":"Messages & Channels","section":"user","locale":"uk-rUA","resourcePath":"docs/uk-rUA/user/messages-and-channels.html","navOrder":3,"keywords":["messages", "channels", "default", "channel", "adding", "archived", "direct", "sending", "message", "managing", "the", "conversation", "list", "bubbles", "states", "delivery", "errors", "features", "quick", "chat", "searching", "text", "formatting", "mentions", "reactions", "replying", "day", "separators", "jump", "latest"],"aliases":["channels", "direct-messages", "messaging", "conversations"],"charCount":23864}, - {"id":"mqtt","title":"MQTT","section":"user","locale":"uk-rUA","resourcePath":"docs/uk-rUA/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting", "messages"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12414}, + {"id":"mqtt","title":"MQTT","section":"user","locale":"uk-rUA","resourcePath":"docs/uk-rUA/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting", "messages"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12402}, {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"uk-rUA","resourcePath":"docs/uk-rUA/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "air", "quality", "signal", "reference", "reading", "traceroute", "results", "position", "log", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12671}, {"id":"nodes","title":"Вузли","section":"user","locale":"uk-rUA","resourcePath":"docs/uk-rUA/user/nodes.html","navOrder":4,"keywords":["node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "security", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "nodes", "not", "heard", "your", "current", "settings", "sort", "options", "per"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":23300}, {"id":"onboarding","title":"Getting Started","section":"user","locale":"uk-rUA","resourcePath":"docs/uk-rUA/user/onboarding.html","navOrder":1,"keywords":["getting", "started", "first", "launch", "welcome", "screen", "permissions", "bluetooth", "permission", "location", "notifications", "critical", "alerts", "reviewing", "later", "after", "setup", "related", "topics"],"aliases":["first-launch", "setup", "intro"],"charCount":8506}, - {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"uk-rUA","resourcePath":"docs/uk-rUA/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "mqtt", "module", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon", "tak", "device"],"aliases":["modules", "module-config", "administration"],"charCount":34096}, + {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"uk-rUA","resourcePath":"docs/uk-rUA/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "mqtt", "module", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon", "tak", "device"],"aliases":["modules", "module-config", "administration"],"charCount":33873}, {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"uk-rUA","resourcePath":"docs/uk-rUA/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "lora", "modem", "presets", "position", "config", "bluetooth", "related", "topics"],"aliases":["налаштування", "radio-config", "user-config", "lora"],"charCount":42576}, {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"uk-rUA","resourcePath":"docs/uk-rUA/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5269}, {"id":"tak","title":"TAK Integration","section":"user","locale":"uk-rUA","resourcePath":"docs/uk-rUA/user/tak.html","navOrder":10,"keywords":["tak", "integration", "overview", "setup", "prerequisites", "local", "server", "roles", "cot", "cursor", "target", "format", "wire", "usage", "with", "atak", "troubleshooting", "security", "considerations", "related", "topics"],"aliases":["tak", "atak", "team-awareness-kit"],"charCount":10704}, @@ -812,17 +812,17 @@ {"id":"connections","title":"连接数","section":"user","locale":"zh-rCN","resourcePath":"docs/zh-rCN/user/connections.html","navOrder":2,"keywords":["bluetooth", "ble", "pairing", "radio", "connection", "status", "troubleshooting", "usb", "serial", "setup", "tcp", "network", "connecting", "over", "the", "when", "use", "mpwrd", "after", "your", "first", "reconnection", "behavior", "desktop", "connections", "related", "topics"],"aliases":["bluetooth", "usb", "tcp", "pairing"],"charCount":10991}, {"id":"debug-logs","title":"Debug Logs","section":"user","locale":"zh-rCN","resourcePath":"docs/zh-rCN/user/debug-logs.html","navOrder":22,"keywords":["debug", "logs", "the", "two", "tabs", "viewing", "app", "exporting", "desktop", "related", "topics"],"aliases":["debug-logs", "logcat", "app-logs", "bug-report"],"charCount":3113}, {"id":"desktop","title":"Desktop App","section":"user","locale":"zh-rCN","resourcePath":"docs/zh-rCN/user/desktop.html","navOrder":14,"keywords":["desktop", "app", "linux", "macos", "windows", "connecting", "your", "radio", "usb", "serial", "primary", "tcp", "bluetooth", "ble", "feature", "parity", "differences", "keyboard", "shortcuts", "window", "system", "tray", "notification", "preferences", "built", "documentation", "browser", "building", "from", "source"],"aliases":["desktop", "linux", "macos", "windows", "jvm"],"charCount":9945}, - {"id":"discovery","title":"本地网状网络发现","section":"user","locale":"zh-rCN","resourcePath":"docs/zh-rCN/user/discovery.html","navOrder":12,"keywords":["local", "mesh", "discovery", "scanner", "setting", "scan", "live", "progress", "reading", "the", "results", "manual", "exploration", "node", "list", "tool", "tips", "for", "related", "topics"],"aliases":["discovery", "local-mesh-discovery", "mesh-discovery", "local-discovery", "network-scan", "traceroute", "neighbor-info"],"charCount":18290}, + {"id":"discovery","title":"本地网状网络发现","section":"user","locale":"zh-rCN","resourcePath":"docs/zh-rCN/user/discovery.html","navOrder":12,"keywords":["local", "mesh", "discovery", "scanner", "setting", "scan", "live", "progress", "reading", "the", "results", "manual", "exploration", "node", "list", "tool", "tips", "for", "related", "topics"],"aliases":["discovery", "local-mesh-discovery", "mesh-discovery", "local-discovery", "network-scan", "traceroute", "neighbor-info"],"charCount":18280}, {"id":"firmware","title":"固件升级","section":"user","locale":"zh-rCN","resourcePath":"docs/zh-rCN/user/firmware.html","navOrder":13,"keywords":["checking", "for", "updates", "update", "methods", "ota", "over", "the", "air", "via", "bluetooth", "network", "connected", "esp32", "app", "usb", "factory", "erase", "and", "bootloader", "upgrade", "other", "flashing", "options", "version", "channels", "pre", "checklist", "post", "stuck"],"aliases":["firmware", "update", "OTA（空中升级）", "flash"],"charCount":11037}, {"id":"help-and-docs","title":"Help & In-App Docs","section":"user","locale":"zh-rCN","resourcePath":"docs/zh-rCN/user/help-and-docs.html","navOrder":21,"keywords":["help", "app", "docs", "browsing", "search", "chirpy", "the", "assistant", "related", "topics"],"aliases":["help", "docs-browser", "chirpy", "assistant"],"charCount":2306}, {"id":"map-and-waypoints","title":"Map & Waypoints","section":"user","locale":"zh-rCN","resourcePath":"docs/zh-rCN/user/map-and-waypoints.html","navOrder":6,"keywords":["map", "waypoints", "view", "node", "markers", "controls", "filtering", "the", "creating", "waypoint", "properties", "expiration", "geofences", "managing", "site", "planner", "position", "sharing", "enabling", "privacy", "considerations", "sources", "adding", "your", "own", "tile", "source", "offline", "terrain", "going"],"aliases":["map", "waypoints", "gps", "location", "site-planner", "map-layers", "geojson", "kml"],"charCount":14878}, {"id":"messages-and-channels","title":"Messages & Channels","section":"user","locale":"zh-rCN","resourcePath":"docs/zh-rCN/user/messages-and-channels.html","navOrder":3,"keywords":["messages", "channels", "default", "channel", "adding", "archived", "sending", "direct", "message", "managing", "the", "conversation", "list", "bubbles", "states", "delivery", "errors", "features", "quick", "chat", "searching", "text", "formatting", "mentions", "reactions", "replying", "day", "separators", "jump", "latest"],"aliases":["channels", "direct-messages", "messaging", "conversations"],"charCount":23701}, - {"id":"mqtt","title":"MQTT","section":"user","locale":"zh-rCN","resourcePath":"docs/zh-rCN/user/mqtt.html","navOrder":11,"keywords":["mqtt", "how", "works", "configuration", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "not", "connecting", "messages", "bridging"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12398}, + {"id":"mqtt","title":"MQTT","section":"user","locale":"zh-rCN","resourcePath":"docs/zh-rCN/user/mqtt.html","navOrder":11,"keywords":["mqtt", "how", "works", "configuration", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "not", "connecting", "messages", "bridging"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12386}, {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"zh-rCN","resourcePath":"docs/zh-rCN/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "air", "quality", "signal", "reference", "reading", "traceroute", "results", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12396}, {"id":"nodes","title":"节点","section":"user","locale":"zh-rCN","resourcePath":"docs/zh-rCN/user/nodes.html","navOrder":4,"keywords":["node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "security", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "nodes", "not", "heard", "your", "current", "settings", "sort", "options", "per"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":23239}, {"id":"onboarding","title":"Getting Started","section":"user","locale":"zh-rCN","resourcePath":"docs/zh-rCN/user/onboarding.html","navOrder":1,"keywords":["getting", "started", "first", "launch", "welcome", "screen", "permissions", "bluetooth", "permission", "location", "notifications", "critical", "alerts", "reviewing", "later", "after", "setup", "related", "topics"],"aliases":["first-launch", "setup", "intro"],"charCount":8109}, - {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"zh-rCN","resourcePath":"docs/zh-rCN/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "mqtt", "module", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon", "tak", "device"],"aliases":["modules", "module-config", "administration"],"charCount":31273}, - {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"zh-rCN","resourcePath":"docs/zh-rCN/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "configuration", "lora", "modem", "presets", "related", "topics"],"aliases":["设置", "radio-config", "user-config", "lora"],"charCount":40740}, + {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"zh-rCN","resourcePath":"docs/zh-rCN/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "mqtt", "module", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon", "tak", "device"],"aliases":["modules", "module-config", "administration"],"charCount":31528}, + {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"zh-rCN","resourcePath":"docs/zh-rCN/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "configuration", "lora", "modem", "presets", "related", "topics"],"aliases":["设置", "radio-config", "user-config", "lora"],"charCount":41316}, {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"zh-rCN","resourcePath":"docs/zh-rCN/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5233}, {"id":"tak","title":"TAK Integration","section":"user","locale":"zh-rCN","resourcePath":"docs/zh-rCN/user/tak.html","navOrder":10,"keywords":["tak", "integration", "setup", "configuration", "local", "server", "roles", "cot", "cursor", "target", "format", "wire", "usage", "with", "atak", "security", "considerations", "related", "topics"],"aliases":["tak", "atak", "team-awareness-kit"],"charCount":10663}, {"id":"telemetry-and-sensors","title":"Telemetry and sensors","section":"user","locale":"zh-rCN","resourcePath":"docs/zh-rCN/user/telemetry-and-sensors.html","navOrder":999,"keywords":["telemetry", "and", "sensors", "device", "environment", "temperature", "humidity", "air", "quality", "soil", "light", "weather", "other", "readings", "configuring", "choosing", "interval", "metrics", "viewing", "related", "topics"],"aliases":[],"charCount":12035}, @@ -833,17 +833,17 @@ {"id":"connections","title":"連線","section":"user","locale":"zh-rTW","resourcePath":"docs/zh-rTW/user/connections.html","navOrder":2,"keywords":["ble", "pairing", "radio", "usb", "troubleshooting", "tcp", "network", "connecting", "over", "the", "mpwrd", "after", "your", "first", "connection"],"aliases":["藍牙", "usb", "tcp", "配對"],"charCount":10212}, {"id":"debug-logs","title":"Debug Logs","section":"user","locale":"zh-rTW","resourcePath":"docs/zh-rTW/user/debug-logs.html","navOrder":22,"keywords":["debug", "logs", "the", "two", "tabs", "viewing", "app", "exporting"],"aliases":["debug-logs", "logcat", "app-logs", "bug-report"],"charCount":3105}, {"id":"desktop","title":"桌面版應用程式","section":"user","locale":"zh-rTW","resourcePath":"docs/zh-rTW/user/desktop.html","navOrder":14,"keywords":["linux", "macos", "windows", "usb", "tcp", "ble"],"aliases":["桌面", "linux", "macos", "windows", "jvm"],"charCount":9035}, - {"id":"discovery","title":"Local Mesh Discovery","section":"user","locale":"zh-rTW","resourcePath":"docs/zh-rTW/user/discovery.html","navOrder":12,"keywords":["local", "mesh", "discovery", "scanner", "setting", "scan", "live", "progress", "reading", "the", "results", "beacon", "manual", "exploration", "node", "list", "tool", "tips", "for"],"aliases":["discovery", "local-mesh-discovery", "mesh-探索", "本地-探索", "網路-掃描", "traceroute", "鄰居資訊"],"charCount":16564}, + {"id":"discovery","title":"Local Mesh Discovery","section":"user","locale":"zh-rTW","resourcePath":"docs/zh-rTW/user/discovery.html","navOrder":12,"keywords":["local", "mesh", "discovery", "scanner", "setting", "scan", "live", "progress", "reading", "the", "results", "beacon", "manual", "exploration", "node", "list", "tool", "tips", "for"],"aliases":["discovery", "local-mesh-discovery", "mesh-探索", "本地-探索", "網路-掃描", "traceroute", "鄰居資訊"],"charCount":16554}, {"id":"firmware","title":"韌體更新","section":"user","locale":"zh-rTW","resourcePath":"docs/zh-rTW/user/firmware.html","navOrder":13,"keywords":["ota", "via", "network", "connected", "esp32", "app", "usb", "update", "factory", "erase", "and", "bootloader", "upgrade", "other", "flashing", "options", "radio", "won", "boot", "after"],"aliases":["韌體", "更新", "OTA（空中升级）", "記憶體"],"charCount":10273}, {"id":"help-and-docs","title":"Help & In-App Docs","section":"user","locale":"zh-rTW","resourcePath":"docs/zh-rTW/user/help-and-docs.html","navOrder":21,"keywords":["help", "app", "docs", "browsing", "chirpy", "the", "assistant"],"aliases":["help", "docs-browser", "chirpy", "assistant"],"charCount":2292}, {"id":"map-and-waypoints","title":"地圖與航點","section":"user","locale":"zh-rTW","resourcePath":"docs/zh-rTW/user/map-and-waypoints.html","navOrder":6,"keywords":["filtering", "the", "map", "waypoint", "geofences", "site", "planner", "adding", "your", "own", "tile", "source", "offline", "terrain", "going"],"aliases":["map", "waypoints", "gps", "location", "site-planner", "map-layers", "geojson", "kml"],"charCount":13885}, {"id":"messages-and-channels","title":"訊息與頻道","section":"user","locale":"zh-rTW","resourcePath":"docs/zh-rTW/user/messages-and-channels.html","navOrder":3,"keywords":["archived", "channels", "managing", "the", "conversation", "list", "bubbles", "searching", "messages", "text", "formatting", "mentions", "replying", "day", "separators", "jump", "latest"],"aliases":["頻道", "direct-messages", "messaging", "conversations"],"charCount":22549}, - {"id":"mqtt","title":"MQTT","section":"user","locale":"zh-rTW","resourcePath":"docs/zh-rTW/user/mqtt.html","navOrder":11,"keywords":["mqtt", "connection", "status", "and", "test", "proxy", "this", "phone", "meshtastic"],"aliases":["MQTT", "internet-bridge", "broker"],"charCount":10659}, + {"id":"mqtt","title":"MQTT","section":"user","locale":"zh-rTW","resourcePath":"docs/zh-rTW/user/mqtt.html","navOrder":11,"keywords":["mqtt", "connection", "status", "and", "test", "proxy", "this", "phone", "meshtastic"],"aliases":["MQTT", "internet-bridge", "broker"],"charCount":10647}, {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"zh-rTW","resourcePath":"docs/zh-rTW/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "air", "quality", "signal", "reference", "reading", "traceroute", "results", "pax"],"aliases":["metrics", "遙測", "device-metrics", "signal"],"charCount":12464}, {"id":"nodes","title":"節點","section":"user","locale":"zh-rTW","resourcePath":"docs/zh-rTW/user/nodes.html","navOrder":4,"keywords":["node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "security", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "nodes", "not", "heard", "your", "current", "settings", "sort", "options", "per"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":23239}, {"id":"onboarding","title":"新手入門","section":"user","locale":"zh-rTW","resourcePath":"docs/zh-rTW/user/onboarding.html","navOrder":999,"keywords":["first", "launch", "welcome", "screen", "permissions", "bluetooth", "permission", "location", "notifications", "critical", "alerts", "reviewing", "later", "after", "setup"],"aliases":["first-launch", "setup", "intro"],"charCount":15168}, - {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"zh-rTW","resourcePath":"docs/zh-rTW/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "mqtt", "module", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon", "tak", "device"],"aliases":["modules", "模組設定", "administration"],"charCount":31613}, - {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"zh-rTW","resourcePath":"docs/zh-rTW/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "lora", "modem", "presets", "related", "topics"],"aliases":["設定", "radio-config", "user-config", "LoRa"],"charCount":40879}, + {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"zh-rTW","resourcePath":"docs/zh-rTW/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "mqtt", "module", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon", "tak", "device"],"aliases":["modules", "模組設定", "administration"],"charCount":31886}, + {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"zh-rTW","resourcePath":"docs/zh-rTW/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "lora", "modem", "presets", "related", "topics"],"aliases":["設定", "radio-config", "user-config", "LoRa"],"charCount":41401}, {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"zh-rTW","resourcePath":"docs/zh-rTW/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":50663}, {"id":"tak","title":"TAK Integration","section":"user","locale":"zh-rTW","resourcePath":"docs/zh-rTW/user/tak.html","navOrder":10,"keywords":["tak", "integration", "local", "server", "roles", "cot", "cursor", "target", "format", "wire", "usage", "with", "atak", "security", "considerations", "related", "topics"],"aliases":["tak", "atak", "team-awareness-kit"],"charCount":10637}, {"id":"telemetry-and-sensors","title":"Telemetry and sensors","section":"user","locale":"zh-rTW","resourcePath":"docs/zh-rTW/user/telemetry-and-sensors.html","navOrder":999,"keywords":["telemetry", "and", "sensors", "environment", "temperature", "humidity", "air", "quality", "soil", "light", "weather", "other", "readings", "configuring", "choosing", "interval", "metrics", "viewing", "related", "topics"],"aliases":[],"charCount":12124}, diff --git a/main/is-rIS/user/discovery.html b/main/is-rIS/user/discovery.html index eda76b011b..bf493ee028 100644 --- a/main/is-rIS/user/discovery.html +++ b/main/is-rIS/user/discovery.html @@ -5,4 +5,4 @@ ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) -

Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:.

What to look for What it means
All hops show Good SNR (green) Healthy path — messages flow reliably
One hop shows a poor SNR (orange or red) Weak link — this relay segment is fragile
Many hops (4+) Long path — consider repositioning a node to shorten it
Different path on retry Mesh is adapting — multiple routes exist (this is good!)

💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network.

Troubleshooting with Traceroute

  • No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key.
  • Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa.
  • Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position.
  • Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric.

Neighbor Info

The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh.

Enabling Neighbor Info

  1. Navigate to Settings → Module configuration → Neighbor Info.
  2. Enable the module.
  3. Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
  4. Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air.

Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.

Viewing neighbor data

  • Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors.
  • Each neighbor entry shows the node that was directly heard and its signal quality.
  • Combine neighbor data from multiple nodes to understand the full mesh topology.

ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further.

Node list as a discovery tool

The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively.

Finding new nodes

  • Sort by Last heard to see the most recently active nodes at the top.
  • Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes.

Assessing connectivity

  • Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed.
  • Sort by Distance to find nearby nodes and verify they’re reachable.
  • Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge).

Infrastructure audit

  • Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes.
  • Check their signal quality and last-heard times to verify your infrastructure nodes are healthy.

See Nodes for full details on filtering and sorting options.

Tips for Mesh exploration

  • Start with traceroute — it gives you immediate, actionable information about a specific path.
  • Enable Neighbor Info on key nodes — especially routers and repeaters, to build a picture of the backbone.
  • Check the map — node positions on the Map combined with signal data help you understand why some links are strong and others are weak.
  • Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly.
+

Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:.

What to look for What it means
All hops show Good SNR (green) Healthy path — messages flow reliably
One hop shows a poor SNR (orange or red) Weak link — this relay segment is fragile
Many hops (4+) Long path — consider repositioning a node to shorten it
Different path on retry Mesh is adapting — multiple routes exist (this is good!)

💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network.

Troubleshooting with Traceroute

  • No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key.
  • Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa.
  • Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position.
  • Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric.

Neighbor Info

The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh.

Enabling Neighbor Info

  1. Navigate to Settings → Module configuration → Neighbor Info.
  2. Enable the module.
  3. Set Update Interval. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
  4. Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air.

Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.

Viewing neighbor data

  • Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors.
  • Each neighbor entry shows the node that was directly heard and its signal quality.
  • Combine neighbor data from multiple nodes to understand the full mesh topology.

ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further.

Node list as a discovery tool

The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively.

Finding new nodes

  • Sort by Last heard to see the most recently active nodes at the top.
  • Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes.

Assessing connectivity

  • Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed.
  • Sort by Distance to find nearby nodes and verify they’re reachable.
  • Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge).

Infrastructure audit

  • Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes.
  • Check their signal quality and last-heard times to verify your infrastructure nodes are healthy.

See Nodes for full details on filtering and sorting options.

Tips for Mesh exploration

  • Start with traceroute — it gives you immediate, actionable information about a specific path.
  • Enable Neighbor Info on key nodes — especially routers and repeaters, to build a picture of the backbone.
  • Check the map — node positions on the Map combined with signal data help you understand why some links are strong and others are weak.
  • Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly.
diff --git a/main/is-rIS/user/mqtt.html b/main/is-rIS/user/mqtt.html index e7877e4a2c..7dd97c8b62 100644 --- a/main/is-rIS/user/mqtt.html +++ b/main/is-rIS/user/mqtt.html @@ -1,2 +1,2 @@ MQTT | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Íslenska
Meshtastic Docs ↗

🌐 Íslenska — Community translation View in English

MQTT

MQTT bridges your Meshtastic mesh network to the internet, enabling long-range communication beyond radio range.

Overview

The MQTT module connects your node to an MQTT broker, allowing:

  • Messages to reach nodes on different physical meshes via the internet
  • Integration with home automation and monitoring systems
  • Publishing node positions to the public Meshtastic map
  • Custom data pipelines for logging and alerting

How It Works 

[Your Node] → Radio → [Gateway Node with Wi-Fi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node]
-

A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh.

Configuration

Enabling MQTT

  1. Navigate to Settings → Module configuration → MQTT.
  2. Enable the MQTT module.
  3. Configure the broker connection:
Setting Lýsing Default
Address MQTT broker hostname mqtt.meshtastic.org
Username Broker authentication meshdev
Password Broker authentication large4cats
Root topic Base topic for messages msh, which the radio rewrites to msh/<REGION> once you set a region
Encryption enabled Encrypt MQTT payload Enabled
JSON output enabled Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it Disabled
TLS enabled Secure connection to broker Disabled
Map reporting Report position to public map Disabled
Proxy to client enabled Relay MQTT through the connected phone Disabled

Connection Status and Test Connection

The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here.

Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason.

MQTT Proxy on This Phone

If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection.

ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them.

The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration.

Default Meshtastic Broker

The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing.

When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without).

🔒 Privacy: Messages on the public broker are readable by anyone subscribed. Always use channel encryption for private communications.

Private Broker

For better privacy and control, you can run your own MQTT broker:

  • Mosquitto (lightweight, open-source)
  • HiveMQ
  • EMQX

Configure your node to point to your private broker with appropriate credentials.

Map Reporting

When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.

Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.

Reports appear at meshmap.net and similar community map services.

🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published.

Direction Lýsing
Uplink Messages from mesh → MQTT broker
Downlink Messages from MQTT broker → mesh

Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on.

Message Formats

MQTT carries two payload formats:

Format Lýsing Use case
Protobuf Binary Meshtastic protobuf encoding Node-to-node mesh bridging
JSON Human-readable JSON on the /2/json/ topic Consumers outside the mesh (dashboards, home automation)

ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads.

Encryption & Privacy

Understanding the layered encryption model:

  1. Channel encryption happens on the mesh before MQTT. If your channel has a PSK, the MQTT payload is already encrypted — the broker and any subscribers see only the ciphertext.
  2. Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard.
  3. TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping.

🔒 Security: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications.

Best Practices

  • Use channel-level encryption (PSK) on channels that bridge to MQTT
  • Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes memory)
  • Use a private broker for sensitive deployments
  • Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh
  • Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back

Troubleshooting

MQTT Not Connecting

  • Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself.
  • Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces.
  • Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443).
  • DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly.

Messages Not Bridging

  • Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway.
  • Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage.
  • Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root.
  • Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway.
  • Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in.
+

A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh.

Configuration

Enabling MQTT

  1. Navigate to Settings → Module configuration → MQTT.
  2. Enable the MQTT module.
  3. Configure the broker connection:
Setting Lýsing Default
Address MQTT broker hostname mqtt.meshtastic.org
Username Broker authentication meshdev
Password Broker authentication large4cats
Root topic Base topic for messages msh, which the radio rewrites to msh/<REGION> once you set a region
Encryption enabled Encrypt MQTT payload Enabled
JSON output enabled Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it Disabled
TLS enabled Secure connection to broker Disabled
Map reporting Report position to public map Disabled
Proxy to client enabled Relay MQTT through the connected phone Disabled

Connection Status and Test Connection

The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here.

Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason.

MQTT Proxy on This Phone

If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection.

ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them.

The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration.

Default Meshtastic Broker

The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing.

When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without).

🔒 Privacy: Messages on the public broker are readable by anyone subscribed. Always use channel encryption for private communications.

Private Broker

For better privacy and control, you can run your own MQTT broker:

  • Mosquitto (lightweight, open-source)
  • HiveMQ
  • EMQX

Configure your node to point to your private broker with appropriate credentials.

Map Reporting

When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.

Turning it on opens a consent card. Turn on I agree. and choose a Map Publish Interval of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.

Reports appear at meshmap.net and similar community map services.

🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published.

Direction Lýsing
Uplink Messages from mesh → MQTT broker
Downlink Messages from MQTT broker → mesh

Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on.

Message Formats

MQTT carries two payload formats:

Format Lýsing Use case
Protobuf Binary Meshtastic protobuf encoding Node-to-node mesh bridging
JSON Human-readable JSON on the /2/json/ topic Consumers outside the mesh (dashboards, home automation)

ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads.

Encryption & Privacy

Understanding the layered encryption model:

  1. Channel encryption happens on the mesh before MQTT. If your channel has a PSK, the MQTT payload is already encrypted — the broker and any subscribers see only the ciphertext.
  2. Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard.
  3. TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping.

🔒 Security: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications.

Best Practices

  • Use channel-level encryption (PSK) on channels that bridge to MQTT
  • Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes memory)
  • Use a private broker for sensitive deployments
  • Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh
  • Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back

Troubleshooting

MQTT Not Connecting

  • Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself.
  • Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces.
  • Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443).
  • DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly.

Messages Not Bridging

  • Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway.
  • Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage.
  • Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root.
  • Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway.
  • Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in.
diff --git a/main/is-rIS/user/settings-module-admin.html b/main/is-rIS/user/settings-module-admin.html index 62057dba6c..6373bb6682 100644 --- a/main/is-rIS/user/settings-module-admin.html +++ b/main/is-rIS/user/settings-module-admin.html @@ -1 +1 @@ - Settings — Modules & Admin | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Íslenska
Meshtastic Docs ↗

🌐 Íslenska — Community translation View in English

Settings — Modules & Admin

Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.

💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.

Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:

A toggle setting in the on position

A dropdown setting, expanded to show its list of options

A text field setting with a value entered

A module settings card with its title and grouped controls

Stillingar aukaeininga

Every module lives under Settings → Module configuration.

⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes.

MQTT module

Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.

Setting Lýsing
MQTT enabled Toggle MQTT bridge
Address MQTT broker address
Username Authentication username
Password Authentication password
Encryption enabled Encrypt MQTT payloads
JSON output enabled Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS enabled Use secure connection
Root topic Base MQTT topic path
Proxy to client enabled Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy on this phone The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT
Map reporting Publish position to the public map — see the Map reporting group that follows

Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:

Setting Lýsing
I agree. Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map reporting interval (seconds) How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered

See MQTT for a detailed usage guide including encryption, privacy, and broker setup.

Serial module

Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.

Setting Lýsing
Serial enabled Activate serial communication
Echo enabled Echo received serial data back
Serial mode Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX GPIO pins for the serial connection
Serial baud rate Port speed
Timeout How long to wait before considering an incoming message complete
Override console serial port Take over the port the debug console normally uses

External Notification module

Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.

There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.

Setting Lýsing
External notification enabled Master toggle for the module
Alert message LED / buzzer / vibra Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra Which outputs fire on a received bell character
Output LED (GPIO) Pin the LED is wired to
Output LED active high Whether the LED pin is active high or low
Output buzzer (GPIO) Pin the buzzer is wired to
Output vibra (GPIO) Pin the vibration motor is wired to
Use PWM buzzer Drive the buzzer with PWM, which allows tones rather than a single pitch
Use I2S as buzzer Send the alert through an I2S audio output instead
Output duration (milliseconds) How long a single alert lasts
Nag timeout (seconds) Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Ringtone The tone played on a PWM buzzer, in RTTTL. Can be imported from a file

Store & Forward module

Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.

Setting Lýsing
Store & Forward enabled Activate store and forward
Heartbeat Periodically announce this node’s store-and-forward capability
Number of records Maximum stored messages
History return max Max messages to replay
History return window Time window for replay
Server Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)

💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.

Range Test module

⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.

Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.

Setting Lýsing
Range test enabled Activate range testing
Sender message interval (seconds) Time between test transmissions, chosen from a dropdown of fixed intervals
Save .CSV in storage (ESP32 only) Log received test data to the node’s own filesystem. ESP32 hardware only

Telemetry module

Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).

Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.

Setting Lýsing
Send Device Telemetry Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval How often to report battery, uptime and channel utilization
Environment metrics module enabled Report the attached environment sensors
Environment metrics update interval How often to report them
Environment metrics on-screen enabled Also show these readings on the device’s own display
Environment metrics use Fahrenheit Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Air quality metrics module enabled Report particulate and CO₂ sensor data
Air quality metrics update interval How often to report them
Power metrics module enabled Report the per-channel voltage and current readings
Power metrics update interval How often to report them
Power metrics on-screen enabled Also show power readings on the device’s display

See Telemetry & Sensors for supported sensors and configuration recommendations.

Canned Message module

Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.

Setting Lýsing
Canned message enabled ⚠️ Deprecated in the protobuf schema
Messages Newline-separated list of messages
Send bell Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Rotary encoder #1 enabled Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port The three pins the encoder is wired to
Generate input event on Press / CW / CCW Which key event each encoder action produces
Up/Down/Select input enabled A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source ⚠️ Deprecated in the protobuf schema

Audio module

Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.

Setting Lýsing
CODEC 2 enabled Activate audio module
CODEC2 sample rate Audio quality/bandwidth tradeoff
PTT pin GPIO pin for the push-to-talk button
I2S word select GPIO pin for I2S WS
I2S data in GPIO pin for I2S DIN
I2S data out GPIO pin for I2S DOUT
I2S clock GPIO pin for the I2S bit clock

ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.

Remote Hardware module

GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.

⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.

Setting Lýsing
Remote Hardware enabled Activate remote GPIO access
Allow undefined pin access Allow access to any GPIO pin (security risk)
Available pins Up to 4 GPIO pins this node exposes for remote read/write

Neighbor Info module

Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.

Setting Lýsing
Neighbor Info enabled Activate neighbor broadcasting
Update interval (seconds) How often to broadcast neighbor list
Transmit over LoRa Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name

See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.

Ambient Lighting module

Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.

Setting Lýsing
LED state Turn the LED on or off
Current LED current limit (0–31)
Red / Green / Blue Individual color channel values (0–255)

Detection Sensor module

Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.

Setting Lýsing
Detection Sensor enabled Activate detection sensor
GPIO pin to monitor GPIO pin connected to sensor
Detection trigger type How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Use INPUT_PULLUP mode Enable the pin’s internal pull-up resistor
Minimum broadcast (seconds) Minimum time between alert broadcasts
State broadcast (seconds) Periodic state broadcast interval
Send bell with alert message Include bell character in alerts
Friendly name Custom name for this sensor

Paxcounter module

People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.

Setting Lýsing
Paxcounter enabled Activate people counting
Update interval (seconds) How often to report counts
Wi-Fi RSSI threshold Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE RSSI threshold The same cut-off for BLE advertisements (defaults to −80 dBm)

💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.

Status Message module

The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.

Mesh Beacon module

Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.

TAK module

Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.

Administration

Remote Administration

Remotely configure nodes that share your admin key:

  1. Select the target node in the node list.
  2. Navigate to Settings for that node.
  3. Modify configuration.
  4. Tap Save — changes are sent over the mesh.

⚠️ Important: Requires an admin key configured on both your node and the target node.

Device Actions

Settings → Administration holds five one-shot actions, each behind a confirmation dialog:

Action What it does
Set time Sends your phone’s clock to the node
Endurræsa Restarts the node
Slökkva Powers the node down
Grunnstilla Returns every setting to its factory default
Endurræsa NodeDB Clears the node database. This dialog carries a Preserve Favorites? switch

⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.

Backup & Restore

Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.

Advanced

Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.

Clean Node Database

Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.

  • Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
  • Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.

The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.

Villuleitarborð

Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.

App Settings

The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:

Privacy

  • Allow analytics and crash reporting — opt in or out of diagnostics.
  • Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
  • Homoglyph encoding — how look-alike characters in names are handled.

Appearance

  • Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
  • Theme and Language.
  • Show full message timestamps.

Persistence

  • A cache limit for how much history is kept.
  • Export rangetest packets, Export all packets and Export node database.

On their own

  • Node Layout — how much detail each row of the node list shows.
  • Wi-Fi Provisioning for mPWRD-OS — see Connections.
  • Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
  • System AI — appears only where app functions are available; see App Functions.

A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.

Um smáforrit

Settings → About carries the app’s own identity rather than the node’s:

Three sections:

  • What is Meshtastic? — a short description of the project.
  • Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
  • Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.

The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.

Acknowledgements

Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.

Troubleshooting remote admin

  • “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
  • Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
  • Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
+ Settings — Modules & Admin | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Íslenska
Meshtastic Docs ↗

🌐 Íslenska — Community translation View in English

Settings — Modules & Admin

Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.

💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.

Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:

A toggle setting in the on position

A dropdown setting, expanded to show its list of options

A text field setting with a value entered

A module settings card with its title and grouped controls

Stillingar aukaeininga

Every module lives under Settings → Module configuration.

⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes.

MQTT module

Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.

Setting Lýsing
MQTT enabled Toggle MQTT bridge
Address MQTT broker address
Username Authentication username
Password Authentication password
Encryption enabled Encrypt MQTT payloads
JSON output enabled Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS enabled Use secure connection
Root topic Base MQTT topic path
Proxy to client enabled Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy on this phone The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT
Map reporting Publish position to the public map — see the Map reporting group that follows

Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:

Setting Lýsing
I agree. Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered

See MQTT for a detailed usage guide including encryption, privacy, and broker setup.

Serial module

Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.

Setting Lýsing
Serial enabled Activate serial communication
Echo enabled Echo received serial data back
Serial mode Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX GPIO pins for the serial connection
Serial baud rate Port speed
Timeout How long to wait before considering an incoming message complete
Override console serial port Take over the port the debug console normally uses

External Notification module

Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.

There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.

Setting Lýsing
External notification enabled Master toggle for the module
Alert message LED / buzzer / vibra Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra Which outputs fire on a received bell character
Output LED (GPIO) Pin the LED is wired to
Output LED active high Whether the LED pin is active high or low
Output buzzer (GPIO) Pin the buzzer is wired to
Output vibra (GPIO) Pin the vibration motor is wired to
Use PWM buzzer Drive the buzzer with PWM, which allows tones rather than a single pitch
Use I2S as buzzer Send the alert through an I2S audio output instead
GPIO Output Duration How long a single alert lasts
Nag Timeout Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Ringtone The tone played on a PWM buzzer, in RTTTL. Can be imported from a file

Store & Forward module

Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.

Setting Lýsing
Store & Forward enabled Activate store and forward
Heartbeat Periodically announce this node’s store-and-forward capability
Number of records Maximum stored messages
History return max Max messages to replay
History return window Time window for replay
Server Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)

💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.

Range Test module

⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.

Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.

Setting Lýsing
Range test enabled Activate range testing
Sender Interval Time between test transmissions, chosen from a dropdown of fixed intervals
Save .CSV in storage (ESP32 only) Log received test data to the node’s own filesystem. ESP32 hardware only

Telemetry module

Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).

Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.

Setting Lýsing
Send Device Telemetry Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval How often to report battery, uptime and channel utilization
Environment metrics module enabled Report the attached environment sensors
Environment metrics update interval How often to report them
Environment metrics on-screen enabled Also show these readings on the device’s own display
Environment metrics use Fahrenheit Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Air quality metrics module enabled Report particulate and CO₂ sensor data
Air quality metrics update interval How often to report them
Power metrics module enabled Report the per-channel voltage and current readings
Power metrics update interval How often to report them
Power metrics on-screen enabled Also show power readings on the device’s display

See Telemetry & Sensors for supported sensors and configuration recommendations.

Canned Message module

Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.

Setting Lýsing
Canned message enabled ⚠️ Deprecated in the protobuf schema
Messages Newline-separated list of messages
Send bell Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Rotary encoder #1 enabled Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port The three pins the encoder is wired to
Generate input event on Press / CW / CCW Which key event each encoder action produces
Up/Down/Select input enabled A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source ⚠️ Deprecated in the protobuf schema

Audio module

Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.

Setting Lýsing
CODEC 2 enabled Activate audio module
CODEC2 sample rate Audio quality/bandwidth tradeoff
PTT pin GPIO pin for the push-to-talk button
I2S word select GPIO pin for I2S WS
I2S data in GPIO pin for I2S DIN
I2S data out GPIO pin for I2S DOUT
I2S clock GPIO pin for the I2S bit clock

ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.

Remote Hardware module

GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.

⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.

Setting Lýsing
Remote Hardware enabled Activate remote GPIO access
Allow undefined pin access Allow access to any GPIO pin (security risk)
Available pins Up to 4 GPIO pins this node exposes for remote read/write

Neighbor Info module

Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.

Setting Lýsing
Neighbor Info enabled Activate neighbor broadcasting
Update Interval How often to broadcast neighbor list
Transmit over LoRa Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name

See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.

Ambient Lighting module

Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.

Setting Lýsing
LED state Turn the LED on or off
Current LED current limit (0–31)
Red / Green / Blue Individual color channel values (0–255)

Detection Sensor module

Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.

Setting Lýsing
Detection Sensor enabled Activate detection sensor
GPIO pin to monitor GPIO pin connected to sensor
Detection trigger type How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Use INPUT_PULLUP mode Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts Minimum time between alert broadcasts
State Broadcast Interval Periodic state broadcast interval
Send bell with alert message Include bell character in alerts
Friendly name Custom name for this sensor

Paxcounter module

People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.

Setting Lýsing
Paxcounter enabled Activate people counting
Update Interval How often to report counts
WiFi Threshold (dBm) Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm) The same cut-off for BLE advertisements (defaults to −80 dBm)

💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.

Status Message module

The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.

Mesh Beacon module

Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.

TAK module

Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.

Administration

Remote Administration

Remotely configure nodes that share your admin key:

  1. Select the target node in the node list.
  2. Navigate to Settings for that node.
  3. Modify configuration.
  4. Tap Save — changes are sent over the mesh.

⚠️ Important: Requires an admin key configured on both your node and the target node.

Device Actions

Settings → Administration holds five one-shot actions, each behind a confirmation dialog:

Action What it does
Set time Sends your phone’s clock to the node
Endurræsa Restarts the node
Slökkva Powers the node down
Grunnstilla Returns every setting to its factory default
Endurræsa NodeDB Clears the node database. This dialog carries a Preserve Favorites? switch

⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.

Backup & Restore

Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.

Advanced

Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.

Clean Node Database

Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.

  • Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
  • Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.

The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.

Villuleitarborð

Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.

App Settings

The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:

Privacy

  • Allow analytics and crash reporting — opt in or out of diagnostics.
  • Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
  • Homoglyph encoding — how look-alike characters in names are handled.

Appearance

  • Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
  • Theme and Language.
  • Show full message timestamps.

Persistence

  • A cache limit for how much history is kept.
  • Export rangetest packets, Export all packets and Export node database.

On their own

  • Node Layout — how much detail each row of the node list shows.
  • Wi-Fi Provisioning for mPWRD-OS — see Connections.
  • Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
  • System AI — appears only where app functions are available; see App Functions.

A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.

Um smáforrit

Settings → About carries the app’s own identity rather than the node’s:

Three sections:

  • What is Meshtastic? — a short description of the project.
  • Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
  • Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.

The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.

Acknowledgements

Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.

Troubleshooting remote admin

  • “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
  • Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
  • Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
diff --git a/main/is-rIS/user/settings-radio-user.html b/main/is-rIS/user/settings-radio-user.html index de4b9dc14f..7865248096 100644 --- a/main/is-rIS/user/settings-radio-user.html +++ b/main/is-rIS/user/settings-radio-user.html @@ -1 +1 @@ - Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Íslenska
Meshtastic Docs ↗

🌐 Íslenska — Community translation View in English

Settings — Radio & User

Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How these screens work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Lýsing
Long Name Your display name (up to 39 characters)
Short Name 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Unmessageable Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur node (Ham) Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in.

Configuration

Device Config

On Settings → Device configuration → Device.

Setting Lýsing Default
Device Role Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Rebroadcast Mode How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Node Info Broadcast Interval How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Double Tap as Button Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Enabled
LED Heartbeat Blink the status LED periodically Enabled
Time Zone POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it —
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to —

LoRa Config

On Settings → LoRa.

Setting Lýsing Default
Svæði Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number Unset (must configure)
Presets Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Transmit Power Transmission power (dBm); 0 = max allowed for region 0 (region max)
Frequency Override Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Use Preset On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead From preset
Coding Rate Manual mode only: 5–8. More redundancy costs airtime From preset
Bandwidth Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Frequency Slot Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmit Enabled Turning this off makes the node receive-only On
Override Duty Cycle Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
Ignore MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok to MQTT Allow your packets to be forwarded to MQTT by gateways Off
RX Boosted Gain Extra receive gain on SX126x radios; costs a little current Off
PA fan disabled Turn off the power-amplifier fan on hardware that has one Off

The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set.

Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Speed SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a modem preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Display Config

On Settings → Device configuration → Display. These control the node’s own screen, not the app’s.

Setting Lýsing
Screen on for How long the display stays lit before sleeping
Carousel interval How often the node cycles between screens on its own
Display mode Screen layout/density used by the firmware
Display units Metric or Imperial on the node’s screen
Use 12h clock format Show the node’s clock as 12-hour rather than 24-hour
Bold Heading Draw the screen’s heading text in bold
Flip screen Rotate the display 180° for an inverted mounting
OLED type Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED
Wake on tap or motion Light the screen when the node is tapped or moved
Compass orientation Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each
Always point north Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Position Config

On Settings → Device configuration → Position.

Setting Lýsing
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the node asks its GPS for a fix
Broadcast Interval How often the position is shared with the mesh
Smart Position Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Fixed Position Use a manually entered latitude, longitude and altitude instead of the GPS
Position Flags A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Power Config

On Settings → Device configuration → Power.

Setting Lýsing
Enable power saving mode Let the node sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the node stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC multiplier override ratio The correction factor itself, used only when the override is on
Battery INA_2XX I2C address Address of an external INA-series power sensor, if fitted

Network Config

On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node.

Setting Lýsing
Wi-Fi enabled Enable the Wi-Fi node (ESP32 nodes)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Password Network password
Ethernet enabled Use a wired connection on hardware that has one
IPv4 mode DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP server Time synchronization server
rsyslog server Remote logging server

Network Config with a static IPv4 address entered

Bluetooth Config

On Settings → Device configuration → Bluetooth, on nodes with Bluetooth.

Setting Lýsing
Bluetooth enabled Enable/disable BLE radio
Pairing mode Fixed PIN, Random PIN, or No PIN
Fixed PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Security Config

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

Setting Lýsing
Public Key Your node’s public key (read-only)
Admin Key Keys permitted to administer this node remotely — up to three
Private Key Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it
Regenerate Private Key Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Serial console Serial console over the Stream API
Debug log API enabled Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth
Managed Mode Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.

+ Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Íslenska
Meshtastic Docs ↗

🌐 Íslenska — Community translation View in English

Settings — Radio & User

Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How these screens work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Lýsing
Long Name Your display name (up to 39 characters)
Short Name 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Unmessageable Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur node (Ham) Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in.

Configuration

Device Config

On Settings → Device configuration → Device.

Setting Lýsing Default
Device Role Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Rebroadcast Mode How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Node Info Broadcast Interval How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Double Tap as Button Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Enabled
LED Heartbeat Blink the status LED periodically Enabled
Time Zone POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it —
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to —

LoRa Config

On Settings → LoRa.

Setting Lýsing Default
Svæði Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number Unset (must configure)
Presets Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Transmit Power (dBm) Transmission power; 0 = max allowed for region 0 (region max)
Frequency Override Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Use Preset On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead From preset
Coding Rate Manual mode only: 5–8. More redundancy costs airtime From preset
Bandwidth Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Frequency Slot Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmit Enabled Turning this off makes the node receive-only On
Override Duty Cycle Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
Ignore MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok to MQTT Allow your packets to be forwarded to MQTT by gateways Off
RX Boosted Gain Extra receive gain on SX126x radios; costs a little current Off
PA fan disabled Turn off the power-amplifier fan on hardware that has one Off

The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set.

Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Speed SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a modem preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Display Config

On Settings → Device configuration → Display. These control the node’s own screen, not the app’s.

Setting Lýsing
Screen on for How long the display stays lit before sleeping
Carousel interval How often the node cycles between screens on its own
Display mode Screen layout/density used by the firmware
Display units Metric or Imperial on the node’s screen
Use 12h clock format Show the node’s clock as 12-hour rather than 24-hour
Bold Heading Draw the screen’s heading text in bold
Flip screen Rotate the display 180° for an inverted mounting
OLED type Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED
Wake on tap or motion Light the screen when the node is tapped or moved
Compass orientation Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each
Always point north Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Position Config

On Settings → Device configuration → Position.

Setting Lýsing
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the node asks its GPS for a fix
Broadcast Interval How often the position is shared with the mesh
Smart Position Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Fixed Position Use a manually entered latitude, longitude and altitude instead of the GPS
Position Flags A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Power Config

On Settings → Device configuration → Power.

Setting Lýsing
Enable power saving mode Let the node sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the node stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC multiplier override ratio The correction factor itself, used only when the override is on
Battery INA_2XX I2C address Address of an external INA-series power sensor, if fitted

Network Config

On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node.

Setting Lýsing
Wi-Fi enabled Enable the Wi-Fi node (ESP32 nodes)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Password Network password
Ethernet enabled Use a wired connection on hardware that has one
IPv4 mode DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP server Time synchronization server
rsyslog server Remote logging server

Network Config with a static IPv4 address entered

Bluetooth Config

On Settings → Device configuration → Bluetooth, on nodes with Bluetooth.

Setting Lýsing
Bluetooth enabled Enable/disable BLE radio
Pairing mode Fixed PIN, Random PIN, or No PIN
Fixed PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Security Config

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

Setting Lýsing
Public Key Your node’s public key (read-only)
Admin Key Keys permitted to administer this node remotely — up to three
Private Key Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it
Regenerate Private Key Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Serial console Serial console over the Stream API
Debug log API enabled Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth
Managed Mode Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.

diff --git a/main/it-rIT/user/discovery.html b/main/it-rIT/user/discovery.html index 99ce43798b..3f449037da 100644 --- a/main/it-rIT/user/discovery.html +++ b/main/it-rIT/user/discovery.html @@ -5,4 +5,4 @@ ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) -

Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:.

What to look for What it means
All hops show Good SNR (green) Healthy path — messages flow reliably
One hop shows a poor SNR (orange or red) Weak link — this relay segment is fragile
Many hops (4+) Long path — consider repositioning a node to shorten it
Different path on retry Mesh is adapting — multiple routes exist (this is good!)

💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network.

Troubleshooting with Traceroute

  • No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key.
  • Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa.
  • Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position.
  • Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric.

Informazioni Vicinato

The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh.

Enabling Neighbor Info

  1. Navigate to Settings → Module configuration → Neighbor Info.
  2. Enable the module.
  3. Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
  4. Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air.

Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.

Viewing neighbor data

  • Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors.
  • Each neighbor entry shows the node that was directly heard and its signal quality.
  • Combine neighbor data from multiple nodes to understand the full mesh topology.

ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further.

Node list as a discovery tool

The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively.

Finding new nodes

  • Sort by Last heard to see the most recently active nodes at the top.
  • Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes.

Assessing connectivity

  • Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed.
  • Sort by Distance to find nearby nodes and verify they’re reachable.
  • Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge).

Infrastructure audit

  • Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes.
  • Check their signal quality and last-heard times to verify your infrastructure nodes are healthy.

See Nodes for full details on filtering and sorting options.

Tips for Mesh exploration

  • Start with traceroute — it gives you immediate, actionable information about a specific path.
  • Enable Neighbor Info on key nodes — especially routers and repeaters, to build a picture of the backbone.
  • Check the map — node positions on the Map combined with signal data help you understand why some links are strong and others are weak.
  • Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly.
+

Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:.

What to look for What it means
All hops show Good SNR (green) Healthy path — messages flow reliably
One hop shows a poor SNR (orange or red) Weak link — this relay segment is fragile
Many hops (4+) Long path — consider repositioning a node to shorten it
Different path on retry Mesh is adapting — multiple routes exist (this is good!)

💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network.

Troubleshooting with Traceroute

  • No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key.
  • Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa.
  • Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position.
  • Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric.

Informazioni Vicinato

The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh.

Enabling Neighbor Info

  1. Navigate to Settings → Module configuration → Neighbor Info.
  2. Enable the module.
  3. Set Update Interval. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
  4. Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air.

Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.

Viewing neighbor data

  • Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors.
  • Each neighbor entry shows the node that was directly heard and its signal quality.
  • Combine neighbor data from multiple nodes to understand the full mesh topology.

ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further.

Node list as a discovery tool

The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively.

Finding new nodes

  • Sort by Last heard to see the most recently active nodes at the top.
  • Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes.

Assessing connectivity

  • Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed.
  • Sort by Distance to find nearby nodes and verify they’re reachable.
  • Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge).

Infrastructure audit

  • Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes.
  • Check their signal quality and last-heard times to verify your infrastructure nodes are healthy.

See Nodes for full details on filtering and sorting options.

Tips for Mesh exploration

  • Start with traceroute — it gives you immediate, actionable information about a specific path.
  • Enable Neighbor Info on key nodes — especially routers and repeaters, to build a picture of the backbone.
  • Check the map — node positions on the Map combined with signal data help you understand why some links are strong and others are weak.
  • Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly.
diff --git a/main/it-rIT/user/mqtt.html b/main/it-rIT/user/mqtt.html index 89f90b4b58..9ce4f31da1 100644 --- a/main/it-rIT/user/mqtt.html +++ b/main/it-rIT/user/mqtt.html @@ -1,2 +1,2 @@ MQTT | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Italiano
Meshtastic Docs ↗

🌐 Italiano — Community translation View in English

MQTT

MQTT bridges your Meshtastic mesh network to the internet, enabling long-range communication beyond radio range.

Panoramica

The MQTT module connects your node to an MQTT broker, allowing:

  • Messages to reach nodes on different physical meshes via the internet
  • Integration with home automation and monitoring systems
  • Publishing node positions to the public Meshtastic map
  • Custom data pipelines for logging and alerting

Come funziona 

[Your Node] → Radio → [Gateway Node with Wi-Fi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node]
-

A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh.

Configurazione

Enabling MQTT

  1. Navigate to Settings → Module configuration → MQTT.
  2. Enable the MQTT module.
  3. Configure the broker connection:
Impostazione Descrizione Predefinito
Address MQTT broker hostname mqtt.meshtastic.org
Username Broker authentication meshdev
Password Broker authentication large4cats
Root topic Base topic for messages msh, which the radio rewrites to msh/<REGION> once you set a region
Encryption enabled Encrypt MQTT payload Abilitato
JSON output enabled Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it Disabled
TLS enabled Secure connection to broker Disabled
Map reporting Report position to public map Disabled
Proxy to client enabled Relay MQTT through the connected phone Disabled

Connection Status and Test Connection

The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here.

Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason.

MQTT Proxy on This Phone

If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection.

ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them.

The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration.

Default Meshtastic Broker

The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing.

When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without).

🔒 Privacy: Messages on the public broker are readable by anyone subscribed. Always use channel encryption for private communications.

Private Broker

For better privacy and control, you can run your own MQTT broker:

  • Mosquitto (lightweight, open-source)
  • HiveMQ
  • EMQX

Configure your node to point to your private broker with appropriate credentials.

Map Reporting

When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.

Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.

Reports appear at meshmap.net and similar community map services.

🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published.

Direction Descrizione
Uplink Messages from mesh → MQTT broker
Downlink Messages from MQTT broker → mesh

Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on.

Message Formats

MQTT carries two payload formats:

Format Descrizione Use case
Protobuf Binary Meshtastic protobuf encoding Node-to-node mesh bridging
JSON Human-readable JSON on the /2/json/ topic Consumers outside the mesh (dashboards, home automation)

ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads.

Encryption & Privacy

Understanding the layered encryption model:

  1. Channel encryption happens on the mesh before MQTT. If your channel has a PSK, the MQTT payload is already encrypted — the broker and any subscribers see only the ciphertext.
  2. Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard.
  3. TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping.

🔒 Security: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications.

Buone pratiche

  • Use channel-level encryption (PSK) on channels that bridge to MQTT
  • Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes memory)
  • Use a private broker for sensitive deployments
  • Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh
  • Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back

Risoluzione problemi

MQTT Not Connecting

  • Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself.
  • Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces.
  • Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443).
  • DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly.

Messages Not Bridging

  • Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway.
  • Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage.
  • Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root.
  • Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway.
  • Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in.
+

A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh.

Configurazione

Enabling MQTT

  1. Navigate to Settings → Module configuration → MQTT.
  2. Enable the MQTT module.
  3. Configure the broker connection:
Impostazione Descrizione Predefinito
Address MQTT broker hostname mqtt.meshtastic.org
Username Broker authentication meshdev
Password Broker authentication large4cats
Root topic Base topic for messages msh, which the radio rewrites to msh/<REGION> once you set a region
Encryption enabled Encrypt MQTT payload Abilitato
JSON output enabled Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it Disabled
TLS enabled Secure connection to broker Disabled
Map reporting Report position to public map Disabled
Proxy to client enabled Relay MQTT through the connected phone Disabled

Connection Status and Test Connection

The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here.

Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason.

MQTT Proxy on This Phone

If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection.

ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them.

The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration.

Default Meshtastic Broker

The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing.

When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without).

🔒 Privacy: Messages on the public broker are readable by anyone subscribed. Always use channel encryption for private communications.

Private Broker

For better privacy and control, you can run your own MQTT broker:

  • Mosquitto (lightweight, open-source)
  • HiveMQ
  • EMQX

Configure your node to point to your private broker with appropriate credentials.

Map Reporting

When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.

Turning it on opens a consent card. Turn on I agree. and choose a Map Publish Interval of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.

Reports appear at meshmap.net and similar community map services.

🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published.

Direction Descrizione
Uplink Messages from mesh → MQTT broker
Downlink Messages from MQTT broker → mesh

Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on.

Message Formats

MQTT carries two payload formats:

Format Descrizione Use case
Protobuf Binary Meshtastic protobuf encoding Node-to-node mesh bridging
JSON Human-readable JSON on the /2/json/ topic Consumers outside the mesh (dashboards, home automation)

ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads.

Encryption & Privacy

Understanding the layered encryption model:

  1. Channel encryption happens on the mesh before MQTT. If your channel has a PSK, the MQTT payload is already encrypted — the broker and any subscribers see only the ciphertext.
  2. Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard.
  3. TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping.

🔒 Security: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications.

Buone pratiche

  • Use channel-level encryption (PSK) on channels that bridge to MQTT
  • Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes memory)
  • Use a private broker for sensitive deployments
  • Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh
  • Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back

Risoluzione problemi

MQTT Not Connecting

  • Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself.
  • Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces.
  • Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443).
  • DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly.

Messages Not Bridging

  • Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway.
  • Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage.
  • Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root.
  • Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway.
  • Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in.
diff --git a/main/it-rIT/user/settings-module-admin.html b/main/it-rIT/user/settings-module-admin.html index 13018e2a2c..61b8de6c78 100644 --- a/main/it-rIT/user/settings-module-admin.html +++ b/main/it-rIT/user/settings-module-admin.html @@ -1 +1 @@ - Settings — Modules & Admin | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Italiano
Meshtastic Docs ↗

🌐 Italiano — Community translation View in English

Settings — Modules & Admin

Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.

💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.

Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:

A toggle setting in the on position

A dropdown setting, expanded to show its list of options

A text field setting with a value entered

A module settings card with its title and grouped controls

Impostazioni moduli

Every module lives under Settings → Module configuration.

⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes.

MQTT module

Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.

Impostazione Descrizione
MQTT abilitato Toggle MQTT bridge
Indirizzo MQTT broker address
Username Authentication username
Password Authentication password
Crittografia abilitata Encrypt MQTT payloads
Output JSON abilitato Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS abilitato Use secure connection
Root topic Base MQTT topic path
Proxy to client attivato Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself
Proxy MQTT su questo telefono The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT
Segnalazione su mappa Publish position to the public map — see the Map reporting group that follows

Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:

Impostazione Descrizione
Sono d’accordo. Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Intervallo di segnalazione su mappa (secondi) How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered

See MQTT for a detailed usage guide including encryption, privacy, and broker setup.

Serial module

Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.

Impostazione Descrizione
Seriale abilitata Activate serial communication
Echo abilitato Echo received serial data back
Modalità seriale Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX GPIO pins for the serial connection
Velocità della seriale Port speed
Timeout How long to wait before considering an incoming message complete
Sovrascrivi porta seriale della console Take over the port the debug console normally uses

External Notification module

Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.

There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.

Impostazione Descrizione
Notifica esterna attivata Master toggle for the module
Alert message LED / buzzer / vibra Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra Which outputs fire on a received bell character
LED Output (GPIO) Pin the LED is wired to
Output per LED active high Whether the LED pin is active high or low
Output buzzer (GPIO) Pin the buzzer is wired to
Output vibrazione (GPIO) Pin the vibration motor is wired to
Usa buzzer PWM Drive the buzzer with PWM, which allows tones rather than a single pitch
Usa I2S come buzzer Send the alert through an I2S audio output instead
Durata output (millisecondi) How long a single alert lasts
Timeout chiusura popup (secondi) Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Suoneria The tone played on a PWM buzzer, in RTTTL. Can be imported from a file

Store & Forward module

Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.

Impostazione Descrizione
Store & Forward abilitato Activate store and forward
Heartbeat Periodically announce this node’s store-and-forward capability
Numero di record Maximum stored messages
Cronologia ritorno max Max messages to replay
Finestra di ritorno cronologia Time window for replay
Server Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)

💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.

Range Test module

⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.

Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.

Impostazione Descrizione
Test distanza massima abilitato Activate range testing
Intervallo messaggio mittente (secondi) Time between test transmissions, chosen from a dropdown of fixed intervals
Salva .CSV nella memoria (solo ESP32) Log received test data to the node’s own filesystem. ESP32 hardware only

Telemetry module

Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).

Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.

Impostazione Descrizione
Invia Telemetria Dispositivo Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Intervallo aggiornamento metriche dispositivo How often to report battery, uptime and channel utilization
Modulo metriche ambientali abilitato Report the attached environment sensors
Intervallo aggiornamento metriche ambientali How often to report them
Metriche ambientali visualizzate su schermo Also show these readings on the device’s own display
Usa i gradi Fahrenheit nelle metriche ambientali Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Modulo metriche della qualità dell’aria abilitato Report particulate and CO₂ sensor data
Intervallo aggiornamento metriche qualità aria How often to report them
Modulo metriche di alimentazione abilitato Report the per-channel voltage and current readings
Intervallo aggiornamento metriche alimentazione How often to report them
Metriche di alimentazione visualizzate su schermo Also show power readings on the device’s display

See Telemetry & Sensors for supported sensors and configuration recommendations.

Canned Message module

Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.

Impostazione Descrizione
Canned message enabled ⚠️ Deprecated in the protobuf schema
Messaggi Newline-separated list of messages
Invia campanella Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Encoder rotativo #1 abilitato Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port The three pins the encoder is wired to
Generate input event on Press / CW / CCW Which key event each encoder action produces
Input Su/Giu/Selezione abilitato A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source ⚠️ Deprecated in the protobuf schema

Audio module

Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.

Impostazione Descrizione
CODEC 2 attivato Activate audio module
Frequenza di campionamento CODEC2 Audio quality/bandwidth tradeoff
Pin PTT GPIO pin for the push-to-talk button
I2S word select GPIO pin for I2S WS
I2S data in GPIO pin for I2S DIN
I2S data out GPIO pin for I2S DOUT
I2S clock GPIO pin for the I2S bit clock

ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.

Remote Hardware module

GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.

⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.

Impostazione Descrizione
Hardware Remoto abilitato Activate remote GPIO access
Consenti accesso a pin non definiti Allow access to any GPIO pin (security risk)
Pin disponibili Up to 4 GPIO pins this node exposes for remote read/write

Neighbor Info module

Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.

Impostazione Descrizione
Info Nodi Vicini abilitato Activate neighbor broadcasting
Intervallo di aggiornamento (secondi) How often to broadcast neighbor list
Trasmettere su LoRa Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name

See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.

Ambient Lighting module

Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.

Impostazione Descrizione
LED di stato Turn the LED on or off
Attuale LED current limit (0–31)
Red / Green / Blue Individual color channel values (0–255)

Detection Sensor module

Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.

Impostazione Descrizione
Sensore Rilevamento attivo Activate detection sensor
Pin GPIO da monitorare GPIO pin connected to sensor
Tipo di trigger di rilevamento How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Usa modalità INPUT_PULLUP Enable the pin’s internal pull-up resistor
Trasmissione minima (secondi) Minimum time between alert broadcasts
Trasmissione stato (secondi) Periodic state broadcast interval
Invia campanella con messaggio di avviso Include bell character in alerts
Nome semplificato Custom name for this sensor

Paxcounter module

People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.

Impostazione Descrizione
Paxcounter abilitato Activate people counting
Intervallo di aggiornamento (secondi) How often to report counts
Wi-Fi RSSI threshold Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE RSSI threshold The same cut-off for BLE advertisements (defaults to −80 dBm)

💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.

Status Message module

The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.

Mesh Beacon module

Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.

TAK module

Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.

Amministrazione

Amministrazione Remota

Remotely configure nodes that share your admin key:

  1. Select the target node in the node list.
  2. Navigate to Settings for that node.
  3. Modify configuration.
  4. Tap Save — changes are sent over the mesh.

⚠️ Important: Requires an admin key configured on both your node and the target node.

Device Actions

Settings → Administration holds five one-shot actions, each behind a confirmation dialog:

Action What it does
Imposta l’ora Sends your phone’s clock to the node
Riavvia Restarts the node
Spegni Powers the node down
Ripristina impostazioni di fabbrica Returns every setting to its factory default
NodeDB reset Clears the node database. This dialog carries a Preserve Favorites? switch

⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.

Backup & Ripristino

Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.

Avanzate

Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.

Azzera il database dei nodi

Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.

  • Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
  • Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.

The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.

Pannello Di Debug

Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.

App Settings

The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:

Privacy

  • Allow analytics and crash reporting — opt in or out of diagnostics.
  • Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
  • Homoglyph encoding — how look-alike characters in names are handled.

Appearance

  • Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
  • Theme and Language.
  • Show full message timestamps.

Persistence

  • A cache limit for how much history is kept.
  • Export rangetest packets, Export all packets and Export node database.

On their own

  • Node Layout — how much detail each row of the node list shows.
  • Wi-Fi Provisioning for mPWRD-OS — see Connections.
  • Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
  • System AI — appears only where app functions are available; see App Functions.

A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.

Informazioni

Settings → About carries the app’s own identity rather than the node’s:

Three sections:

  • What is Meshtastic? — a short description of the project.
  • Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
  • Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.

The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.

Ringraziamenti

Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.

Troubleshooting remote admin

  • “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
  • Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
  • Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
+ Settings — Modules & Admin | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Italiano
Meshtastic Docs ↗

🌐 Italiano — Community translation View in English

Settings — Modules & Admin

Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.

💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.

Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:

A toggle setting in the on position

A dropdown setting, expanded to show its list of options

A text field setting with a value entered

A module settings card with its title and grouped controls

Impostazioni moduli

Every module lives under Settings → Module configuration.

⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes.

MQTT module

Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.

Impostazione Descrizione
MQTT abilitato Toggle MQTT bridge
Indirizzo MQTT broker address
Username Authentication username
Password Authentication password
Crittografia abilitata Encrypt MQTT payloads
Output JSON abilitato Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS abilitato Use secure connection
Root topic Base MQTT topic path
Proxy to client attivato Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself
Proxy MQTT su questo telefono The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT
Segnalazione su mappa Publish position to the public map — see the Map reporting group that follows

Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:

Impostazione Descrizione
Sono d’accordo. Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered

See MQTT for a detailed usage guide including encryption, privacy, and broker setup.

Serial module

Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.

Impostazione Descrizione
Seriale abilitata Activate serial communication
Echo abilitato Echo received serial data back
Modalità seriale Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX GPIO pins for the serial connection
Velocità della seriale Port speed
Timeout How long to wait before considering an incoming message complete
Sovrascrivi porta seriale della console Take over the port the debug console normally uses

External Notification module

Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.

There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.

Impostazione Descrizione
Notifica esterna attivata Master toggle for the module
Alert message LED / buzzer / vibra Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra Which outputs fire on a received bell character
LED Output (GPIO) Pin the LED is wired to
Output per LED active high Whether the LED pin is active high or low
Output buzzer (GPIO) Pin the buzzer is wired to
Output vibrazione (GPIO) Pin the vibration motor is wired to
Usa buzzer PWM Drive the buzzer with PWM, which allows tones rather than a single pitch
Usa I2S come buzzer Send the alert through an I2S audio output instead
GPIO Output Duration How long a single alert lasts
Nag Timeout Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Suoneria The tone played on a PWM buzzer, in RTTTL. Can be imported from a file

Store & Forward module

Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.

Impostazione Descrizione
Store & Forward abilitato Activate store and forward
Heartbeat Periodically announce this node’s store-and-forward capability
Numero di record Maximum stored messages
Cronologia ritorno max Max messages to replay
Finestra di ritorno cronologia Time window for replay
Server Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)

💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.

Range Test module

⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.

Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.

Impostazione Descrizione
Test distanza massima abilitato Activate range testing
Intervallo Del Mittente Time between test transmissions, chosen from a dropdown of fixed intervals
Salva .CSV nella memoria (solo ESP32) Log received test data to the node’s own filesystem. ESP32 hardware only

Telemetry module

Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).

Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.

Impostazione Descrizione
Invia Telemetria Dispositivo Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Intervallo aggiornamento metriche dispositivo How often to report battery, uptime and channel utilization
Modulo metriche ambientali abilitato Report the attached environment sensors
Intervallo aggiornamento metriche ambientali How often to report them
Metriche ambientali visualizzate su schermo Also show these readings on the device’s own display
Usa i gradi Fahrenheit nelle metriche ambientali Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Modulo metriche della qualità dell’aria abilitato Report particulate and CO₂ sensor data
Intervallo aggiornamento metriche qualità aria How often to report them
Modulo metriche di alimentazione abilitato Report the per-channel voltage and current readings
Intervallo aggiornamento metriche alimentazione How often to report them
Metriche di alimentazione visualizzate su schermo Also show power readings on the device’s display

See Telemetry & Sensors for supported sensors and configuration recommendations.

Canned Message module

Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.

Impostazione Descrizione
Canned message enabled ⚠️ Deprecated in the protobuf schema
Messaggi Newline-separated list of messages
Invia campanella Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Encoder rotativo #1 abilitato Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port The three pins the encoder is wired to
Generate input event on Press / CW / CCW Which key event each encoder action produces
Input Su/Giu/Selezione abilitato A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source ⚠️ Deprecated in the protobuf schema

Audio module

Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.

Impostazione Descrizione
CODEC 2 attivato Activate audio module
Frequenza di campionamento CODEC2 Audio quality/bandwidth tradeoff
Pin PTT GPIO pin for the push-to-talk button
I2S word select GPIO pin for I2S WS
I2S data in GPIO pin for I2S DIN
I2S data out GPIO pin for I2S DOUT
I2S clock GPIO pin for the I2S bit clock

ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.

Remote Hardware module

GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.

⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.

Impostazione Descrizione
Hardware Remoto abilitato Activate remote GPIO access
Consenti accesso a pin non definiti Allow access to any GPIO pin (security risk)
Pin disponibili Up to 4 GPIO pins this node exposes for remote read/write

Neighbor Info module

Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.

Impostazione Descrizione
Info Nodi Vicini abilitato Activate neighbor broadcasting
Intervallo Interrogazione GPS How often to broadcast neighbor list
Trasmettere su LoRa Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name

See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.

Ambient Lighting module

Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.

Impostazione Descrizione
LED di stato Turn the LED on or off
Attuale LED current limit (0–31)
Red / Green / Blue Individual color channel values (0–255)

Detection Sensor module

Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.

Impostazione Descrizione
Sensore Rilevamento attivo Activate detection sensor
Pin GPIO da monitorare GPIO pin connected to sensor
Tipo di trigger di rilevamento How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Usa modalità INPUT_PULLUP Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts Minimum time between alert broadcasts
Intervallo Di Trasmissione Periodic state broadcast interval
Invia campanella con messaggio di avviso Include bell character in alerts
Nome semplificato Custom name for this sensor

Paxcounter module

People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.

Impostazione Descrizione
Paxcounter abilitato Activate people counting
Intervallo Interrogazione GPS How often to report counts
WiFi Threshold (dBm) Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm) The same cut-off for BLE advertisements (defaults to −80 dBm)

💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.

Status Message module

The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.

Mesh Beacon module

Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.

TAK module

Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.

Amministrazione

Amministrazione Remota

Remotely configure nodes that share your admin key:

  1. Select the target node in the node list.
  2. Navigate to Settings for that node.
  3. Modify configuration.
  4. Tap Save — changes are sent over the mesh.

⚠️ Important: Requires an admin key configured on both your node and the target node.

Device Actions

Settings → Administration holds five one-shot actions, each behind a confirmation dialog:

Action What it does
Imposta l’ora Sends your phone’s clock to the node
Riavvia Restarts the node
Spegni Powers the node down
Ripristina impostazioni di fabbrica Returns every setting to its factory default
NodeDB reset Clears the node database. This dialog carries a Preserve Favorites? switch

⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.

Backup & Ripristino

Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.

Avanzate

Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.

Azzera il database dei nodi

Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.

  • Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
  • Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.

The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.

Pannello Di Debug

Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.

App Settings

The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:

Privacy

  • Allow analytics and crash reporting — opt in or out of diagnostics.
  • Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
  • Homoglyph encoding — how look-alike characters in names are handled.

Appearance

  • Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
  • Theme and Language.
  • Show full message timestamps.

Persistence

  • A cache limit for how much history is kept.
  • Export rangetest packets, Export all packets and Export node database.

On their own

  • Node Layout — how much detail each row of the node list shows.
  • Wi-Fi Provisioning for mPWRD-OS — see Connections.
  • Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
  • System AI — appears only where app functions are available; see App Functions.

A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.

Informazioni

Settings → About carries the app’s own identity rather than the node’s:

Three sections:

  • What is Meshtastic? — a short description of the project.
  • Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
  • Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.

The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.

Ringraziamenti

Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.

Troubleshooting remote admin

  • “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
  • Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
  • Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
diff --git a/main/it-rIT/user/settings-radio-user.html b/main/it-rIT/user/settings-radio-user.html index b29362b081..7909b93d9d 100644 --- a/main/it-rIT/user/settings-radio-user.html +++ b/main/it-rIT/user/settings-radio-user.html @@ -1 +1 @@ - Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Italiano
Meshtastic Docs ↗

🌐 Italiano — Community translation View in English

Settings — Radio & User

Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How these screens work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

Impostazioni Utente

User Profile

On Settings → User.

Impostazione Descrizione
Nome Lungo Your display name (up to 39 characters)
Nome Breve 4-character abbreviated name
Messaggio di Stato A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Non messaggiabile Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur node (Ham) Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in.

Configurazione

Configurazione Dispositivo

On Settings → Device configuration → Device.

Impostazione Descrizione Predefinito
Ruolo Del Dispositivo Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Modalità Ritrasmissione How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Intervallo Di Trasmissione Info Nodo How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Doppio tocco come pressione pulsante Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Abilitato
Battito Cuore Led Blink the status LED periodically Abilitato
Fuso Orario POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it —
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to —

Configurazione LoRa

On Settings → LoRa.

Impostazione Descrizione Predefinito
Regione Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number Unset (must configure)
Preset Speed/range tradeoff LongFast
Numero di Hop Maximum retransmit hops 3
Potenza di Trasmissione Transmission power (dBm); 0 = max allowed for region 0 (region max)
Sovrascrivi Frequenza Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Usa Preset On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead From preset
Coding Rate Manual mode only: 5–8. More redundancy costs airtime From preset
Larghezza di banda Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Slot di Frequenza Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Trasmissione Abilitata Turning this off makes the node receive-only On
Ignora limite di Duty Cycle Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Disattivato
Ignora MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
OK per MQTT Allow your packets to be forwarded to MQTT by gateways Disattivato
Migliora guadagno in Ricezione Extra receive gain on SX126x radios; costs a little current Disattivato
Ventola PA disabilitata Turn off the power-amplifier fan on hardware that has one Disattivato

The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set.

Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Velocità SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6,25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3,52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1,95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0,34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements
Long Slow ~30 km 0,18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a modem preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Configurazione Schermo

On Settings → Device configuration → Display. These control the node’s own screen, not the app’s.

Impostazione Descrizione
Tieni lo schermo acceso per How long the display stays lit before sleeping
Durata di ogni schermata How often the node cycles between screens on its own
Modalità schermo Screen layout/density used by the firmware
Unità di misura visualizzata Metric or Imperial on the node’s screen
Usa formato orologio 12h Show the node’s clock as 12-hour rather than 24-hour
Intestazione in grassetto Draw the screen’s heading text in bold
Capovolgi schermo Rotate the display 180° for an inverted mounting
Tipo OLED Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED
Accendi lo schermo al tocco o al movimento Light the screen when the node is tapped or moved
Orientamento bussola Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each
Punta sempre a nord Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Configurazione Posizione

On Settings → Device configuration → Position.

Impostazione Descrizione
Modalità GPS (Hardware Fisico) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
Intervallo Interrogazione GPS How often the node asks its GPS for a fix
Intervallo Di Trasmissione How often the position is shared with the mesh
Posizione Smart Broadcast based on movement rather than purely on the clock
Intervallo Intelligente With Smart Position on, the shortest gap between broadcasts
Distanza Intelligente With Smart Position on, how far you must move before broadcasting
Posizione Fissa Use a manually entered latitude, longitude and altitude instead of the GPS
Flag Di Posizione A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Configurazione Alimentazione

On Settings → Device configuration → Power.

Impostazione Descrizione
Abilita modalità risparmio energetico Let the node sleep aggressively between activity
Spegnimento in mancanza di alimentazione Power the device down after external power disappears
Durata super deep sleep How long the deepest sleep state lasts
Tempo minimo di risveglio The shortest time the node stays awake once woken
Durata attesa Bluetooth How long to wait for a phone to connect before sleeping
Sovrascrivi moltiplicatore ADC Turn on a manual correction for battery-voltage readings
Sovrascrivi rapporto moltiplicatore ADC The correction factor itself, used only when the override is on
Indirizzo INA_2XX I2C della batteria Address of an external INA-series power sensor, if fitted

Configurazione Della Rete

On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node.

Impostazione Descrizione
Wi-Fi enabled Enable the Wi-Fi node (ESP32 nodes)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Password Password di rete
Ethernet abilitato Use a wired connection on hardware that has one
Modalità IPv4 DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
Trasmissione UDP Share mesh traffic with other nodes over the local network
Server NTP Time synchronization server
server rsyslog Remote logging server

Network Config with a static IPv4 address entered

Configurazione Bluetooth

On Settings → Device configuration → Bluetooth, on nodes with Bluetooth.

Impostazione Descrizione
Bluetooth attivo Enable/disable BLE radio
Modalità abbinamento Fixed PIN, Random PIN, or No PIN
PIN Fisso PIN code for pairing. Must be exactly six digits — the field rejects anything else

Configurazione Sicurezza

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

Impostazione Descrizione
Chiave Pubblica Your node’s public key (read-only)
Chiave Amministratore Keys permitted to administer this node remotely — up to three
Chiave Privata Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it
Rigenera Chiavi Private Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Console seriale Serial console over the Stream API
Debug log API abilitato Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth
Modalità Gestita Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set
Backup chiavi Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Livello di protezione How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Avvii rimanenti How many device boots the unlocked state survives
Ore alla scadenza Wall-clock lifetime of the unlocked state
Limite di sessione (minuti) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.

+ Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Italiano
Meshtastic Docs ↗

🌐 Italiano — Community translation View in English

Settings — Radio & User

Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How these screens work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

Impostazioni Utente

User Profile

On Settings → User.

Impostazione Descrizione
Nome Lungo Your display name (up to 39 characters)
Nome Breve 4-character abbreviated name
Messaggio di Stato A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Non messaggiabile Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur node (Ham) Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in.

Configurazione

Configurazione Dispositivo

On Settings → Device configuration → Device.

Impostazione Descrizione Predefinito
Ruolo Del Dispositivo Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Modalità Ritrasmissione How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Intervallo Di Trasmissione Info Nodo How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Doppio tocco come pressione pulsante Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Abilitato
Battito Cuore Led Blink the status LED periodically Abilitato
Fuso Orario POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it —
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to —

Configurazione LoRa

On Settings → LoRa.

Impostazione Descrizione Predefinito
Regione Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number Unset (must configure)
Preset Speed/range tradeoff LongFast
Numero di Hop Maximum retransmit hops 3
Transmit Power (dBm) Transmission power; 0 = max allowed for region 0 (region max)
Sovrascrivi Frequenza Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Usa Preset On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead From preset
Coding Rate Manual mode only: 5–8. More redundancy costs airtime From preset
Larghezza di banda Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Slot di Frequenza Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Trasmissione Abilitata Turning this off makes the node receive-only On
Ignora limite di Duty Cycle Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Disattivato
Ignora MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
OK per MQTT Allow your packets to be forwarded to MQTT by gateways Disattivato
Migliora guadagno in Ricezione Extra receive gain on SX126x radios; costs a little current Disattivato
Ventola PA disabilitata Turn off the power-amplifier fan on hardware that has one Disattivato

The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set.

Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Velocità SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6,25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3,52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1,95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0,34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements
Long Slow ~30 km 0,18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a modem preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Configurazione Schermo

On Settings → Device configuration → Display. These control the node’s own screen, not the app’s.

Impostazione Descrizione
Tieni lo schermo acceso per How long the display stays lit before sleeping
Durata di ogni schermata How often the node cycles between screens on its own
Modalità schermo Screen layout/density used by the firmware
Unità di misura visualizzata Metric or Imperial on the node’s screen
Usa formato orologio 12h Show the node’s clock as 12-hour rather than 24-hour
Intestazione in grassetto Draw the screen’s heading text in bold
Capovolgi schermo Rotate the display 180° for an inverted mounting
Tipo OLED Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED
Accendi lo schermo al tocco o al movimento Light the screen when the node is tapped or moved
Orientamento bussola Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each
Punta sempre a nord Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Configurazione Posizione

On Settings → Device configuration → Position.

Impostazione Descrizione
Modalità GPS (Hardware Fisico) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
Intervallo Interrogazione GPS How often the node asks its GPS for a fix
Intervallo Di Trasmissione How often the position is shared with the mesh
Posizione Smart Broadcast based on movement rather than purely on the clock
Intervallo Intelligente With Smart Position on, the shortest gap between broadcasts
Distanza Intelligente With Smart Position on, how far you must move before broadcasting
Posizione Fissa Use a manually entered latitude, longitude and altitude instead of the GPS
Flag Di Posizione A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Configurazione Alimentazione

On Settings → Device configuration → Power.

Impostazione Descrizione
Abilita modalità risparmio energetico Let the node sleep aggressively between activity
Spegnimento in mancanza di alimentazione Power the device down after external power disappears
Durata super deep sleep How long the deepest sleep state lasts
Tempo minimo di risveglio The shortest time the node stays awake once woken
Durata attesa Bluetooth How long to wait for a phone to connect before sleeping
Sovrascrivi moltiplicatore ADC Turn on a manual correction for battery-voltage readings
Sovrascrivi rapporto moltiplicatore ADC The correction factor itself, used only when the override is on
Indirizzo INA_2XX I2C della batteria Address of an external INA-series power sensor, if fitted

Configurazione Della Rete

On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node.

Impostazione Descrizione
Wi-Fi enabled Enable the Wi-Fi node (ESP32 nodes)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Password Password di rete
Ethernet abilitato Use a wired connection on hardware that has one
Modalità IPv4 DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
Trasmissione UDP Share mesh traffic with other nodes over the local network
Server NTP Time synchronization server
server rsyslog Remote logging server

Network Config with a static IPv4 address entered

Configurazione Bluetooth

On Settings → Device configuration → Bluetooth, on nodes with Bluetooth.

Impostazione Descrizione
Bluetooth attivo Enable/disable BLE radio
Modalità abbinamento Fixed PIN, Random PIN, or No PIN
PIN Fisso PIN code for pairing. Must be exactly six digits — the field rejects anything else

Configurazione Sicurezza

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

Impostazione Descrizione
Chiave Pubblica Your node’s public key (read-only)
Chiave Amministratore Keys permitted to administer this node remotely — up to three
Chiave Privata Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it
Rigenera Chiavi Private Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Console seriale Serial console over the Stream API
Debug log API abilitato Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth
Modalità Gestita Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set
Backup chiavi Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Livello di protezione How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Avvii rimanenti How many device boots the unlocked state survives
Ore alla scadenza Wall-clock lifetime of the unlocked state
Limite di sessione (minuti) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.

diff --git a/main/iw-rIL/user/discovery.html b/main/iw-rIL/user/discovery.html index ce3364e248..e22ec04a1b 100644 --- a/main/iw-rIL/user/discovery.html +++ b/main/iw-rIL/user/discovery.html @@ -5,4 +5,4 @@ ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) -

Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:.

What to look for What it means
All hops show Good SNR (green) Healthy path — messages flow reliably
One hop shows a poor SNR (orange or red) Weak link — this relay segment is fragile
Many hops (4+) Long path — consider repositioning a node to shorten it
Different path on retry Mesh is adapting — multiple routes exist (this is good!)

💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network.

Troubleshooting with Traceroute

  • No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key.
  • Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa.
  • Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position.
  • Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric.

Neighbor Info

The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh.

Enabling Neighbor Info

  1. Navigate to Settings → Module configuration → Neighbor Info.
  2. Enable the module.
  3. Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
  4. Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air.

Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.

Viewing neighbor data

  • Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors.
  • Each neighbor entry shows the node that was directly heard and its signal quality.
  • Combine neighbor data from multiple nodes to understand the full mesh topology.

ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further.

Node list as a discovery tool

The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively.

Finding new nodes

  • Sort by Last heard to see the most recently active nodes at the top.
  • Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes.

Assessing connectivity

  • Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed.
  • Sort by Distance to find nearby nodes and verify they’re reachable.
  • Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge).

Infrastructure audit

  • Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes.
  • Check their signal quality and last-heard times to verify your infrastructure nodes are healthy.

See Nodes for full details on filtering and sorting options.

Tips for Mesh exploration

  • Start with traceroute — it gives you immediate, actionable information about a specific path.
  • Enable Neighbor Info on key nodes — especially routers and repeaters, to build a picture of the backbone.
  • Check the map — node positions on the Map combined with signal data help you understand why some links are strong and others are weak.
  • Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly.
+

Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:.

What to look for What it means
All hops show Good SNR (green) Healthy path — messages flow reliably
One hop shows a poor SNR (orange or red) Weak link — this relay segment is fragile
Many hops (4+) Long path — consider repositioning a node to shorten it
Different path on retry Mesh is adapting — multiple routes exist (this is good!)

💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network.

Troubleshooting with Traceroute

  • No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key.
  • Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa.
  • Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position.
  • Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric.

Neighbor Info

The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh.

Enabling Neighbor Info

  1. Navigate to Settings → Module configuration → Neighbor Info.
  2. Enable the module.
  3. Set Update Interval. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
  4. Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air.

Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.

Viewing neighbor data

  • Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors.
  • Each neighbor entry shows the node that was directly heard and its signal quality.
  • Combine neighbor data from multiple nodes to understand the full mesh topology.

ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further.

Node list as a discovery tool

The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively.

Finding new nodes

  • Sort by Last heard to see the most recently active nodes at the top.
  • Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes.

Assessing connectivity

  • Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed.
  • Sort by Distance to find nearby nodes and verify they’re reachable.
  • Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge).

Infrastructure audit

  • Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes.
  • Check their signal quality and last-heard times to verify your infrastructure nodes are healthy.

See Nodes for full details on filtering and sorting options.

Tips for Mesh exploration

  • Start with traceroute — it gives you immediate, actionable information about a specific path.
  • Enable Neighbor Info on key nodes — especially routers and repeaters, to build a picture of the backbone.
  • Check the map — node positions on the Map combined with signal data help you understand why some links are strong and others are weak.
  • Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly.
diff --git a/main/iw-rIL/user/mqtt.html b/main/iw-rIL/user/mqtt.html index fe810af101..b4935dcf24 100644 --- a/main/iw-rIL/user/mqtt.html +++ b/main/iw-rIL/user/mqtt.html @@ -1,2 +1,2 @@ MQTT | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 עברית
Meshtastic Docs ↗

🌐 עברית — Community translation View in English

MQTT

MQTT bridges your Meshtastic mesh network to the internet, enabling long-range communication beyond radio range.

Overview

The MQTT module connects your node to an MQTT broker, allowing:

  • Messages to reach nodes on different physical meshes via the internet
  • Integration with home automation and monitoring systems
  • Publishing node positions to the public Meshtastic map
  • Custom data pipelines for logging and alerting

How It Works 

[Your Node] → Radio → [Gateway Node with Wi-Fi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node]
-

A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh.

Configuration

Enabling MQTT

  1. Navigate to Settings → Module configuration → MQTT.
  2. Enable the MQTT module.
  3. Configure the broker connection:
Setting תיאור Default
Address MQTT broker hostname mqtt.meshtastic.org
Username Broker authentication meshdev
Password Broker authentication large4cats
Root topic Base topic for messages msh, which the radio rewrites to msh/<REGION> once you set a region
Encryption enabled Encrypt MQTT payload Enabled
JSON output enabled Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it Disabled
TLS enabled Secure connection to broker Disabled
Map reporting Report position to public map Disabled
Proxy to client enabled Relay MQTT through the connected phone Disabled

Connection Status and Test Connection

The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here.

Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason.

MQTT Proxy on This Phone

If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection.

ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them.

The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration.

Default Meshtastic Broker

The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing.

When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without).

🔒 Privacy: Messages on the public broker are readable by anyone subscribed. Always use channel encryption for private communications.

Private Broker

For better privacy and control, you can run your own MQTT broker:

  • Mosquitto (lightweight, open-source)
  • HiveMQ
  • EMQX

Configure your node to point to your private broker with appropriate credentials.

Map Reporting

When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.

Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.

Reports appear at meshmap.net and similar community map services.

🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published.

Direction תיאור
Uplink Messages from mesh → MQTT broker
Downlink Messages from MQTT broker → mesh

Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on.

Message Formats

MQTT carries two payload formats:

Format תיאור Use case
Protobuf Binary Meshtastic protobuf encoding Node-to-node mesh bridging
JSON Human-readable JSON on the /2/json/ topic Consumers outside the mesh (dashboards, home automation)

ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads.

Encryption & Privacy

Understanding the layered encryption model:

  1. Channel encryption happens on the mesh before MQTT. If your channel has a PSK, the MQTT payload is already encrypted — the broker and any subscribers see only the ciphertext.
  2. Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard.
  3. TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping.

🔒 Security: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications.

Best Practices

  • Use channel-level encryption (PSK) on channels that bridge to MQTT
  • Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes memory)
  • Use a private broker for sensitive deployments
  • Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh
  • Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back

Troubleshooting

MQTT Not Connecting

  • Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself.
  • Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces.
  • Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443).
  • DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly.

Messages Not Bridging

  • Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway.
  • Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage.
  • Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root.
  • Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway.
  • Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in.
+

A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh.

Configuration

Enabling MQTT

  1. Navigate to Settings → Module configuration → MQTT.
  2. Enable the MQTT module.
  3. Configure the broker connection:
Setting תיאור Default
Address MQTT broker hostname mqtt.meshtastic.org
Username Broker authentication meshdev
Password Broker authentication large4cats
Root topic Base topic for messages msh, which the radio rewrites to msh/<REGION> once you set a region
Encryption enabled Encrypt MQTT payload Enabled
JSON output enabled Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it Disabled
TLS enabled Secure connection to broker Disabled
Map reporting Report position to public map Disabled
Proxy to client enabled Relay MQTT through the connected phone Disabled

Connection Status and Test Connection

The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here.

Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason.

MQTT Proxy on This Phone

If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection.

ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them.

The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration.

Default Meshtastic Broker

The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing.

When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without).

🔒 Privacy: Messages on the public broker are readable by anyone subscribed. Always use channel encryption for private communications.

Private Broker

For better privacy and control, you can run your own MQTT broker:

  • Mosquitto (lightweight, open-source)
  • HiveMQ
  • EMQX

Configure your node to point to your private broker with appropriate credentials.

Map Reporting

When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.

Turning it on opens a consent card. Turn on I agree. and choose a Map Publish Interval of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.

Reports appear at meshmap.net and similar community map services.

🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published.

Direction תיאור
Uplink Messages from mesh → MQTT broker
Downlink Messages from MQTT broker → mesh

Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on.

Message Formats

MQTT carries two payload formats:

Format תיאור Use case
Protobuf Binary Meshtastic protobuf encoding Node-to-node mesh bridging
JSON Human-readable JSON on the /2/json/ topic Consumers outside the mesh (dashboards, home automation)

ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads.

Encryption & Privacy

Understanding the layered encryption model:

  1. Channel encryption happens on the mesh before MQTT. If your channel has a PSK, the MQTT payload is already encrypted — the broker and any subscribers see only the ciphertext.
  2. Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard.
  3. TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping.

🔒 Security: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications.

Best Practices

  • Use channel-level encryption (PSK) on channels that bridge to MQTT
  • Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes memory)
  • Use a private broker for sensitive deployments
  • Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh
  • Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back

Troubleshooting

MQTT Not Connecting

  • Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself.
  • Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces.
  • Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443).
  • DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly.

Messages Not Bridging

  • Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway.
  • Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage.
  • Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root.
  • Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway.
  • Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in.
diff --git a/main/iw-rIL/user/settings-module-admin.html b/main/iw-rIL/user/settings-module-admin.html index cfa63471bb..321024a3a2 100644 --- a/main/iw-rIL/user/settings-module-admin.html +++ b/main/iw-rIL/user/settings-module-admin.html @@ -1 +1 @@ - Settings — Modules & Admin | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 עברית
Meshtastic Docs ↗

🌐 עברית — Community translation View in English

Settings — Modules & Admin

Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.

💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.

Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:

A toggle setting in the on position

A dropdown setting, expanded to show its list of options

A text field setting with a value entered

A module settings card with its title and grouped controls

הגדרות מודולות

Every module lives under Settings → Module configuration.

⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes.

MQTT module

Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.

Setting תיאור
MQTT enabled Toggle MQTT bridge
Address MQTT broker address
Username Authentication username
Password Authentication password
Encryption enabled Encrypt MQTT payloads
JSON output enabled Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS enabled Use secure connection
Root topic Base MQTT topic path
Proxy to client enabled Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy on this phone The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT
Map reporting Publish position to the public map — see the Map reporting group that follows

Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:

Setting תיאור
I agree. Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map reporting interval (seconds) How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered

See MQTT for a detailed usage guide including encryption, privacy, and broker setup.

Serial module

Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.

Setting תיאור
Serial enabled Activate serial communication
Echo enabled Echo received serial data back
Serial mode Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX GPIO pins for the serial connection
Serial baud rate Port speed
Timeout How long to wait before considering an incoming message complete
Override console serial port Take over the port the debug console normally uses

External Notification module

Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.

There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.

Setting תיאור
External notification enabled Master toggle for the module
Alert message LED / buzzer / vibra Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra Which outputs fire on a received bell character
Output LED (GPIO) Pin the LED is wired to
Output LED active high Whether the LED pin is active high or low
Output buzzer (GPIO) Pin the buzzer is wired to
Output vibra (GPIO) Pin the vibration motor is wired to
Use PWM buzzer Drive the buzzer with PWM, which allows tones rather than a single pitch
Use I2S as buzzer Send the alert through an I2S audio output instead
Output duration (milliseconds) How long a single alert lasts
Nag timeout (seconds) Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Ringtone The tone played on a PWM buzzer, in RTTTL. Can be imported from a file

Store & Forward module

Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.

Setting תיאור
Store & Forward enabled Activate store and forward
Heartbeat Periodically announce this node’s store-and-forward capability
Number of records Maximum stored messages
History return max Max messages to replay
History return window Time window for replay
Server Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)

💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.

Range Test module

⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.

Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.

Setting תיאור
Range test enabled Activate range testing
Sender message interval (seconds) Time between test transmissions, chosen from a dropdown of fixed intervals
Save .CSV in storage (ESP32 only) Log received test data to the node’s own filesystem. ESP32 hardware only

Telemetry module

Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).

Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.

Setting תיאור
Send Device Telemetry Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval How often to report battery, uptime and channel utilization
Environment metrics module enabled Report the attached environment sensors
Environment metrics update interval How often to report them
Environment metrics on-screen enabled Also show these readings on the device’s own display
Environment metrics use Fahrenheit Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Air quality metrics module enabled Report particulate and CO₂ sensor data
Air quality metrics update interval How often to report them
Power metrics module enabled Report the per-channel voltage and current readings
Power metrics update interval How often to report them
Power metrics on-screen enabled Also show power readings on the device’s display

See Telemetry & Sensors for supported sensors and configuration recommendations.

Canned Message module

Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.

Setting תיאור
Canned message enabled ⚠️ Deprecated in the protobuf schema
הודעות Newline-separated list of messages
Send bell Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Rotary encoder #1 enabled Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port The three pins the encoder is wired to
Generate input event on Press / CW / CCW Which key event each encoder action produces
Up/Down/Select input enabled A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source ⚠️ Deprecated in the protobuf schema

Audio module

Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.

Setting תיאור
CODEC 2 enabled Activate audio module
CODEC2 sample rate Audio quality/bandwidth tradeoff
PTT pin GPIO pin for the push-to-talk button
I2S word select GPIO pin for I2S WS
I2S data in GPIO pin for I2S DIN
I2S data out GPIO pin for I2S DOUT
I2S clock GPIO pin for the I2S bit clock

ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.

Remote Hardware module

GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.

⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.

Setting תיאור
Remote Hardware enabled Activate remote GPIO access
Allow undefined pin access Allow access to any GPIO pin (security risk)
Available pins Up to 4 GPIO pins this node exposes for remote read/write

Neighbor Info module

Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.

Setting תיאור
Neighbor Info enabled Activate neighbor broadcasting
Update interval (seconds) How often to broadcast neighbor list
Transmit over LoRa Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name

See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.

Ambient Lighting module

Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.

Setting תיאור
LED state Turn the LED on or off
Current LED current limit (0–31)
Red / Green / Blue Individual color channel values (0–255)

Detection Sensor module

Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.

Setting תיאור
Detection Sensor enabled Activate detection sensor
GPIO pin to monitor GPIO pin connected to sensor
Detection trigger type How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Use INPUT_PULLUP mode Enable the pin’s internal pull-up resistor
Minimum broadcast (seconds) Minimum time between alert broadcasts
State broadcast (seconds) Periodic state broadcast interval
Send bell with alert message Include bell character in alerts
Friendly name Custom name for this sensor

Paxcounter module

People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.

Setting תיאור
Paxcounter enabled Activate people counting
Update interval (seconds) How often to report counts
Wi-Fi RSSI threshold Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE RSSI threshold The same cut-off for BLE advertisements (defaults to −80 dBm)

💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.

Status Message module

The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.

Mesh Beacon module

Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.

TAK module

Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.

Administration

Remote Administration

Remotely configure nodes that share your admin key:

  1. Select the target node in the node list.
  2. Navigate to Settings for that node.
  3. Modify configuration.
  4. Tap Save — changes are sent over the mesh.

⚠️ Important: Requires an admin key configured on both your node and the target node.

Device Actions

Settings → Administration holds five one-shot actions, each behind a confirmation dialog:

Action What it does
Set time Sends your phone’s clock to the node
אתחול מחדש Restarts the node
כיבוי Powers the node down
איפוס להגדרות היצרן Returns every setting to its factory default
איפוס NodeDB Clears the node database. This dialog carries a Preserve Favorites? switch

⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.

Backup & Restore

Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.

Advanced

Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.

Clean Node Database

Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.

  • Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
  • Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.

The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.

פאנל דיבאג

Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.

App Settings

The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:

Privacy

  • Allow analytics and crash reporting — opt in or out of diagnostics.
  • Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
  • Homoglyph encoding — how look-alike characters in names are handled.

Appearance

  • Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
  • Theme and Language.
  • Show full message timestamps.

Persistence

  • A cache limit for how much history is kept.
  • Export rangetest packets, Export all packets and Export node database.

On their own

  • Node Layout — how much detail each row of the node list shows.
  • Wi-Fi Provisioning for mPWRD-OS — see Connections.
  • Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
  • System AI — appears only where app functions are available; see App Functions.

A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.

אודות

Settings → About carries the app’s own identity rather than the node’s:

Three sections:

  • What is Meshtastic? — a short description of the project.
  • Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
  • Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.

The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.

Acknowledgements

Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.

Troubleshooting remote admin

  • “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
  • Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
  • Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
+ Settings — Modules & Admin | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 עברית
Meshtastic Docs ↗

🌐 עברית — Community translation View in English

Settings — Modules & Admin

Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.

💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.

Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:

A toggle setting in the on position

A dropdown setting, expanded to show its list of options

A text field setting with a value entered

A module settings card with its title and grouped controls

הגדרות מודולות

Every module lives under Settings → Module configuration.

⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes.

MQTT module

Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.

Setting תיאור
MQTT enabled Toggle MQTT bridge
Address MQTT broker address
Username Authentication username
Password Authentication password
Encryption enabled Encrypt MQTT payloads
JSON output enabled Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS enabled Use secure connection
Root topic Base MQTT topic path
Proxy to client enabled Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy on this phone The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT
Map reporting Publish position to the public map — see the Map reporting group that follows

Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:

Setting תיאור
I agree. Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered

See MQTT for a detailed usage guide including encryption, privacy, and broker setup.

Serial module

Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.

Setting תיאור
Serial enabled Activate serial communication
Echo enabled Echo received serial data back
Serial mode Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX GPIO pins for the serial connection
Serial baud rate Port speed
Timeout How long to wait before considering an incoming message complete
Override console serial port Take over the port the debug console normally uses

External Notification module

Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.

There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.

Setting תיאור
External notification enabled Master toggle for the module
Alert message LED / buzzer / vibra Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra Which outputs fire on a received bell character
Output LED (GPIO) Pin the LED is wired to
Output LED active high Whether the LED pin is active high or low
Output buzzer (GPIO) Pin the buzzer is wired to
Output vibra (GPIO) Pin the vibration motor is wired to
Use PWM buzzer Drive the buzzer with PWM, which allows tones rather than a single pitch
Use I2S as buzzer Send the alert through an I2S audio output instead
GPIO Output Duration How long a single alert lasts
Nag Timeout Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Ringtone The tone played on a PWM buzzer, in RTTTL. Can be imported from a file

Store & Forward module

Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.

Setting תיאור
Store & Forward enabled Activate store and forward
Heartbeat Periodically announce this node’s store-and-forward capability
Number of records Maximum stored messages
History return max Max messages to replay
History return window Time window for replay
Server Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)

💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.

Range Test module

⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.

Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.

Setting תיאור
Range test enabled Activate range testing
Sender Interval Time between test transmissions, chosen from a dropdown of fixed intervals
Save .CSV in storage (ESP32 only) Log received test data to the node’s own filesystem. ESP32 hardware only

Telemetry module

Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).

Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.

Setting תיאור
Send Device Telemetry Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval How often to report battery, uptime and channel utilization
Environment metrics module enabled Report the attached environment sensors
Environment metrics update interval How often to report them
Environment metrics on-screen enabled Also show these readings on the device’s own display
Environment metrics use Fahrenheit Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Air quality metrics module enabled Report particulate and CO₂ sensor data
Air quality metrics update interval How often to report them
Power metrics module enabled Report the per-channel voltage and current readings
Power metrics update interval How often to report them
Power metrics on-screen enabled Also show power readings on the device’s display

See Telemetry & Sensors for supported sensors and configuration recommendations.

Canned Message module

Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.

Setting תיאור
Canned message enabled ⚠️ Deprecated in the protobuf schema
הודעות Newline-separated list of messages
Send bell Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Rotary encoder #1 enabled Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port The three pins the encoder is wired to
Generate input event on Press / CW / CCW Which key event each encoder action produces
Up/Down/Select input enabled A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source ⚠️ Deprecated in the protobuf schema

Audio module

Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.

Setting תיאור
CODEC 2 enabled Activate audio module
CODEC2 sample rate Audio quality/bandwidth tradeoff
PTT pin GPIO pin for the push-to-talk button
I2S word select GPIO pin for I2S WS
I2S data in GPIO pin for I2S DIN
I2S data out GPIO pin for I2S DOUT
I2S clock GPIO pin for the I2S bit clock

ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.

Remote Hardware module

GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.

⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.

Setting תיאור
Remote Hardware enabled Activate remote GPIO access
Allow undefined pin access Allow access to any GPIO pin (security risk)
Available pins Up to 4 GPIO pins this node exposes for remote read/write

Neighbor Info module

Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.

Setting תיאור
Neighbor Info enabled Activate neighbor broadcasting
Update Interval How often to broadcast neighbor list
Transmit over LoRa Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name

See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.

Ambient Lighting module

Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.

Setting תיאור
LED state Turn the LED on or off
Current LED current limit (0–31)
Red / Green / Blue Individual color channel values (0–255)

Detection Sensor module

Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.

Setting תיאור
Detection Sensor enabled Activate detection sensor
GPIO pin to monitor GPIO pin connected to sensor
Detection trigger type How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Use INPUT_PULLUP mode Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts Minimum time between alert broadcasts
State Broadcast Interval Periodic state broadcast interval
Send bell with alert message Include bell character in alerts
Friendly name Custom name for this sensor

Paxcounter module

People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.

Setting תיאור
Paxcounter enabled Activate people counting
Update Interval How often to report counts
WiFi Threshold (dBm) Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm) The same cut-off for BLE advertisements (defaults to −80 dBm)

💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.

Status Message module

The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.

Mesh Beacon module

Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.

TAK module

Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.

Administration

Remote Administration

Remotely configure nodes that share your admin key:

  1. Select the target node in the node list.
  2. Navigate to Settings for that node.
  3. Modify configuration.
  4. Tap Save — changes are sent over the mesh.

⚠️ Important: Requires an admin key configured on both your node and the target node.

Device Actions

Settings → Administration holds five one-shot actions, each behind a confirmation dialog:

Action What it does
Set time Sends your phone’s clock to the node
אתחול מחדש Restarts the node
כיבוי Powers the node down
איפוס להגדרות היצרן Returns every setting to its factory default
איפוס NodeDB Clears the node database. This dialog carries a Preserve Favorites? switch

⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.

Backup & Restore

Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.

Advanced

Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.

Clean Node Database

Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.

  • Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
  • Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.

The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.

פאנל דיבאג

Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.

App Settings

The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:

Privacy

  • Allow analytics and crash reporting — opt in or out of diagnostics.
  • Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
  • Homoglyph encoding — how look-alike characters in names are handled.

Appearance

  • Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
  • Theme and Language.
  • Show full message timestamps.

Persistence

  • A cache limit for how much history is kept.
  • Export rangetest packets, Export all packets and Export node database.

On their own

  • Node Layout — how much detail each row of the node list shows.
  • Wi-Fi Provisioning for mPWRD-OS — see Connections.
  • Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
  • System AI — appears only where app functions are available; see App Functions.

A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.

אודות

Settings → About carries the app’s own identity rather than the node’s:

Three sections:

  • What is Meshtastic? — a short description of the project.
  • Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
  • Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.

The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.

Acknowledgements

Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.

Troubleshooting remote admin

  • “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
  • Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
  • Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
diff --git a/main/iw-rIL/user/settings-radio-user.html b/main/iw-rIL/user/settings-radio-user.html index 4b0c089c2d..1ff9078f7e 100644 --- a/main/iw-rIL/user/settings-radio-user.html +++ b/main/iw-rIL/user/settings-radio-user.html @@ -1 +1 @@ - Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 עברית
Meshtastic Docs ↗

🌐 עברית — Community translation View in English

Settings — Radio & User

Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How these screens work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting תיאור
Long Name Your display name (up to 39 characters)
Short Name 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Unmessageable Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur node (Ham) Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in.

Configuration

Device Config

On Settings → Device configuration → Device.

Setting תיאור Default
Device Role Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Rebroadcast Mode How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Node Info Broadcast Interval How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Double Tap as Button Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Enabled
LED Heartbeat Blink the status LED periodically Enabled
Time Zone POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it —
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to —

LoRa Config

On Settings → LoRa.

Setting תיאור Default
אזור Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number Unset (must configure)
Presets Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Transmit Power Transmission power (dBm); 0 = max allowed for region 0 (region max)
Frequency Override Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Use Preset On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead From preset
Coding Rate Manual mode only: 5–8. More redundancy costs airtime From preset
Bandwidth Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Frequency Slot Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmit Enabled Turning this off makes the node receive-only On
Override Duty Cycle Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
Ignore MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok to MQTT Allow your packets to be forwarded to MQTT by gateways Off
RX Boosted Gain Extra receive gain on SX126x radios; costs a little current Off
PA fan disabled Turn off the power-amplifier fan on hardware that has one Off

The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set.

Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Speed SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a modem preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Display Config

On Settings → Device configuration → Display. These control the node’s own screen, not the app’s.

Setting תיאור
Screen on for How long the display stays lit before sleeping
Carousel interval How often the node cycles between screens on its own
Display mode Screen layout/density used by the firmware
Display units Metric or Imperial on the node’s screen
Use 12h clock format Show the node’s clock as 12-hour rather than 24-hour
Bold Heading Draw the screen’s heading text in bold
Flip screen Rotate the display 180° for an inverted mounting
OLED type Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED
Wake on tap or motion Light the screen when the node is tapped or moved
Compass orientation Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each
Always point north Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Position Config

On Settings → Device configuration → Position.

Setting תיאור
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the node asks its GPS for a fix
Broadcast Interval How often the position is shared with the mesh
Smart Position Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Fixed Position Use a manually entered latitude, longitude and altitude instead of the GPS
Position Flags A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Power Config

On Settings → Device configuration → Power.

Setting תיאור
Enable power saving mode Let the node sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the node stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC multiplier override ratio The correction factor itself, used only when the override is on
Battery INA_2XX I2C address Address of an external INA-series power sensor, if fitted

Network Config

On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node.

Setting תיאור
Wi-Fi enabled Enable the Wi-Fi node (ESP32 nodes)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Password Network password
Ethernet enabled Use a wired connection on hardware that has one
IPv4 mode DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP server Time synchronization server
rsyslog server Remote logging server

Network Config with a static IPv4 address entered

Bluetooth Config

On Settings → Device configuration → Bluetooth, on nodes with Bluetooth.

Setting תיאור
Bluetooth enabled Enable/disable BLE radio
Pairing mode Fixed PIN, Random PIN, or No PIN
Fixed PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Security Config

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

Setting תיאור
Public Key Your node’s public key (read-only)
Admin Key Keys permitted to administer this node remotely — up to three
Private Key Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it
Regenerate Private Key Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Serial console Serial console over the Stream API
Debug log API enabled Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth
Managed Mode Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.

+ Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 עברית
Meshtastic Docs ↗

🌐 עברית — Community translation View in English

Settings — Radio & User

Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How these screens work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting תיאור
Long Name Your display name (up to 39 characters)
Short Name 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Unmessageable Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur node (Ham) Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in.

Configuration

Device Config

On Settings → Device configuration → Device.

Setting תיאור Default
Device Role Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Rebroadcast Mode How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Node Info Broadcast Interval How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Double Tap as Button Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Enabled
LED Heartbeat Blink the status LED periodically Enabled
Time Zone POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it —
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to —

LoRa Config

On Settings → LoRa.

Setting תיאור Default
אזור Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number Unset (must configure)
Presets Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Transmit Power (dBm) Transmission power; 0 = max allowed for region 0 (region max)
Frequency Override Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Use Preset On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead From preset
Coding Rate Manual mode only: 5–8. More redundancy costs airtime From preset
Bandwidth Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Frequency Slot Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmit Enabled Turning this off makes the node receive-only On
Override Duty Cycle Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
Ignore MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok to MQTT Allow your packets to be forwarded to MQTT by gateways Off
RX Boosted Gain Extra receive gain on SX126x radios; costs a little current Off
PA fan disabled Turn off the power-amplifier fan on hardware that has one Off

The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set.

Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Speed SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a modem preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Display Config

On Settings → Device configuration → Display. These control the node’s own screen, not the app’s.

Setting תיאור
Screen on for How long the display stays lit before sleeping
Carousel interval How often the node cycles between screens on its own
Display mode Screen layout/density used by the firmware
Display units Metric or Imperial on the node’s screen
Use 12h clock format Show the node’s clock as 12-hour rather than 24-hour
Bold Heading Draw the screen’s heading text in bold
Flip screen Rotate the display 180° for an inverted mounting
OLED type Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED
Wake on tap or motion Light the screen when the node is tapped or moved
Compass orientation Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each
Always point north Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Position Config

On Settings → Device configuration → Position.

Setting תיאור
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the node asks its GPS for a fix
Broadcast Interval How often the position is shared with the mesh
Smart Position Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Fixed Position Use a manually entered latitude, longitude and altitude instead of the GPS
Position Flags A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Power Config

On Settings → Device configuration → Power.

Setting תיאור
Enable power saving mode Let the node sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the node stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC multiplier override ratio The correction factor itself, used only when the override is on
Battery INA_2XX I2C address Address of an external INA-series power sensor, if fitted

Network Config

On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node.

Setting תיאור
Wi-Fi enabled Enable the Wi-Fi node (ESP32 nodes)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Password Network password
Ethernet enabled Use a wired connection on hardware that has one
IPv4 mode DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP server Time synchronization server
rsyslog server Remote logging server

Network Config with a static IPv4 address entered

Bluetooth Config

On Settings → Device configuration → Bluetooth, on nodes with Bluetooth.

Setting תיאור
Bluetooth enabled Enable/disable BLE radio
Pairing mode Fixed PIN, Random PIN, or No PIN
Fixed PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Security Config

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

Setting תיאור
Public Key Your node’s public key (read-only)
Admin Key Keys permitted to administer this node remotely — up to three
Private Key Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it
Regenerate Private Key Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Serial console Serial console over the Stream API
Debug log API enabled Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth
Managed Mode Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.

diff --git a/main/ja-rJP/user/discovery.html b/main/ja-rJP/user/discovery.html index c0dc691704..0acb5d7901 100644 --- a/main/ja-rJP/user/discovery.html +++ b/main/ja-rJP/user/discovery.html @@ -5,4 +5,4 @@ ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) -

Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:.

確認すべき点 意味
All hops show Good SNR (green) 健全な経路。メッセージが確実に流れます
One hop shows a poor SNR (orange or red) 弱いリンク。この中継区間は脆弱です
ホップ数が多い（4 以上） 長い経路。短くするためにノードの再配置を検討してください
再試行で経路が変わる メッシュが適応しています。複数の経路が存在します（これは良いことです！）

💡 ヒント： ルート追跡を数分間かけて何度か実行してください。経路が変わる場合、メッシュには冗長な経路があり、よくつながったネットワークの兆候です。

ルート追跡によるトラブルシューティング

  • No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. 両方のノードが、同じ暗号化鍵を持つチャンネルを少なくとも 1 つ共有しているか確認してください。
  • ルート追跡がタイムアウトする：経路が長すぎる（ホップ数上限を超える）か、中継ノードが混雑している可能性があります。 Try increasing the hop limit in Settings → LoRa.
  • Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position.
  • 非対称な経路：A→B のルート追跡は、B→A とは異なる経路を通ることがあります。 This is normal — radio propagation isn’t always symmetric.

隣接ノード情報

隣接ノード情報モジュールを使うと、各ノードが直接受信できる（シングルホップの）ノードのリストをブロードキャストできます。複数のノードが隣接ノードのリストを共有すると、メッシュ全体のトポロジーマップを組み立てられます。

隣接ノード情報を有効にする

  1. Navigate to Settings → Module configuration → Neighbor Info.
  2. モジュールを有効にします。
  3. Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
  4. Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air.

Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. 隣接ノード情報を有効にしている他のノードも、同じことを行います。

Viewing neighbor data

  • Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors.
  • 各隣接ノードの項目には、直接受信したノードとその信号品質が表示されます。
  • 複数のノードの隣接ノードデータを組み合わせて、メッシュ全体のトポロジーを把握します。

ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further.

Node list as a discovery tool

ノードリスト自体も、絞り込みと並べ替えの機能を効果的に使えば、強力な探索ツールになります。

Finding new nodes

  • 「最後の通信」で並べ替えると、最近アクティブだったノードが先頭に表示されます。
  • Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes.

Assessing connectivity

  • 「ホップ数」で並べ替えると、直接到達できるノード（0 ホップ）と中継されるノードが分かります。
  • 「距離」で並べ替えると、近くのノードを見つけて、到達できるか確認できます。
  • Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge).

Infrastructure audit

  • 「インフラを除外」を無効にすると、ルーター、ルーター・レイト、クライアント・ベースのノードが表示されます。
  • 信号品質と最後の通信時刻を確認して、インフラのノードが健全であることを確かめます。

絞り込みと並べ替えのオプションの詳細については、ノード を参照してください。

Tips for Mesh exploration

  • まずルート追跡から：特定の経路について、すぐに役立つ情報が得られます。
  • 主要なノードで隣接ノード情報を有効に：特にルーターやリピーターで有効にして、バックボーンの全体像を組み立てます。
  • マップを確認：マップ 上のノードの位置と信号データを組み合わせると、なぜあるリンクは強く、別のリンクは弱いのかが分かります。
  • 信号を時系列で比較：信号メーター のガイドを使って、SNR と RSSI の値を正しく解釈します。

関連トピック

+

Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:.

確認すべき点 意味
All hops show Good SNR (green) 健全な経路。メッセージが確実に流れます
One hop shows a poor SNR (orange or red) 弱いリンク。この中継区間は脆弱です
ホップ数が多い（4 以上） 長い経路。短くするためにノードの再配置を検討してください
再試行で経路が変わる メッシュが適応しています。複数の経路が存在します（これは良いことです！）

💡 ヒント： ルート追跡を数分間かけて何度か実行してください。経路が変わる場合、メッシュには冗長な経路があり、よくつながったネットワークの兆候です。

ルート追跡によるトラブルシューティング

  • No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. 両方のノードが、同じ暗号化鍵を持つチャンネルを少なくとも 1 つ共有しているか確認してください。
  • ルート追跡がタイムアウトする：経路が長すぎる（ホップ数上限を超える）か、中継ノードが混雑している可能性があります。 Try increasing the hop limit in Settings → LoRa.
  • Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position.
  • 非対称な経路：A→B のルート追跡は、B→A とは異なる経路を通ることがあります。 This is normal — radio propagation isn’t always symmetric.

隣接ノード情報

隣接ノード情報モジュールを使うと、各ノードが直接受信できる（シングルホップの）ノードのリストをブロードキャストできます。複数のノードが隣接ノードのリストを共有すると、メッシュ全体のトポロジーマップを組み立てられます。

隣接ノード情報を有効にする

  1. Navigate to Settings → Module configuration → Neighbor Info.
  2. モジュールを有効にします。
  3. Set Update Interval. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
  4. Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air.

Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. 隣接ノード情報を有効にしている他のノードも、同じことを行います。

Viewing neighbor data

  • Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors.
  • 各隣接ノードの項目には、直接受信したノードとその信号品質が表示されます。
  • 複数のノードの隣接ノードデータを組み合わせて、メッシュ全体のトポロジーを把握します。

ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further.

Node list as a discovery tool

ノードリスト自体も、絞り込みと並べ替えの機能を効果的に使えば、強力な探索ツールになります。

Finding new nodes

  • 「最後の通信」で並べ替えると、最近アクティブだったノードが先頭に表示されます。
  • Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes.

Assessing connectivity

  • 「ホップ数」で並べ替えると、直接到達できるノード（0 ホップ）と中継されるノードが分かります。
  • 「距離」で並べ替えると、近くのノードを見つけて、到達できるか確認できます。
  • Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge).

Infrastructure audit

  • 「インフラを除外」を無効にすると、ルーター、ルーター・レイト、クライアント・ベースのノードが表示されます。
  • 信号品質と最後の通信時刻を確認して、インフラのノードが健全であることを確かめます。

絞り込みと並べ替えのオプションの詳細については、ノード を参照してください。

Tips for Mesh exploration

  • まずルート追跡から：特定の経路について、すぐに役立つ情報が得られます。
  • 主要なノードで隣接ノード情報を有効に：特にルーターやリピーターで有効にして、バックボーンの全体像を組み立てます。
  • マップを確認：マップ 上のノードの位置と信号データを組み合わせると、なぜあるリンクは強く、別のリンクは弱いのかが分かります。
  • 信号を時系列で比較：信号メーター のガイドを使って、SNR と RSSI の値を正しく解釈します。

関連トピック

diff --git a/main/ja-rJP/user/mqtt.html b/main/ja-rJP/user/mqtt.html index 39b07b69de..763373b482 100644 --- a/main/ja-rJP/user/mqtt.html +++ b/main/ja-rJP/user/mqtt.html @@ -1,2 +1,2 @@ MQTT | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 日本語
Meshtastic Docs ↗

🌐 日本語 — Community translation View in English

MQTT

MQTT は、Meshtastic のメッシュネットワークをインターネットに橋渡しし、無線の到達範囲を超えた長距離通信を可能にします。

概要

MQTT モジュールは、ノードを MQTT サーバーに接続し、次のことを可能にします：

  • インターネット経由で、物理的に異なるメッシュ上のノードにメッセージを届ける
  • ホームオートメーションや監視システムとの連携
  • ノードの位置を公開の Meshtastic マップに公開する
  • ログ記録や通知のためのカスタムデータパイプライン

仕組み 

[Your Node] → Radio → [Gateway Node with Wi-Fi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node]
-

A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. 同じトピックを購読しているリモートのゲートウェイが、それらのメッセージを自分のローカルメッシュに取り込みます。

設定

MQTT を有効にする

  1. Navigate to Settings → Module configuration → MQTT.
  2. MQTT モジュールを有効にします。
  3. サーバーへの接続を設定します：
設定項目 説明 デフォルト
Address MQTT サーバーのホスト名 mqtt.meshtastic.org
Username サーバーの認証 meshdev
Password サーバーの認証 large4cats
Root topic メッセージのベーストピック msh, which the radio rewrites to msh/<REGION> once you set a region
Encryption enabled MQTT ペイロードを暗号化 有効
JSON output enabled Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it 無効
TLS enabled サーバーへのセキュアな接続 無効
Map reporting 公開マップに位置を報告 無効
Proxy to client enabled Relay MQTT through the connected phone 無効

Connection Status and Test Connection

The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here.

Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason.

このスマートフォンでの MQTT プロキシ

If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection.

ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them.

The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration.

デフォルトの Meshtastic サーバー

コミュニティが mqtt.meshtastic.org で公開サーバーを運用しています。これは一般的な利用やテストを目的としています。

When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without).

🔒 プライバシー： 公開サーバー上のメッセージは、購読している誰もが読めます。プライベートな通信には、必ずチャンネルの暗号化を使用してください。

プライベートサーバー

プライバシーと制御を高めるために、独自の MQTT サーバーを運用できます：

  • Mosquitto（軽量、オープンソース）
  • HiveMQ
  • EMQX

適切な認証情報を設定して、ノードがプライベートサーバーに接続するよう構成します。

マップ報告

When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.

Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.

Reports appear at meshmap.net and similar community map services.

🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published.

アップリンクとダウンリンク

方向 説明
アップリンク メッシュ → MQTT サーバーへのメッセージ
ダウンリンク MQTT サーバー → メッシュへのメッセージ

Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on.

メッセージ形式

MQTT carries two payload formats:

形式 説明 用途
Protobuf バイナリの Meshtastic protobuf エンコード ノード間のメッシュ橋渡し
JSON Human-readable JSON on the /2/json/ topic Consumers outside the mesh (dashboards, home automation)

ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads.

暗号化とプライバシー

階層化された暗号化モデルを理解する：

  1. チャンネルの暗号化は、MQTT の前にメッシュ上で行われます。チャンネルに PSK が設定されている場合、MQTT ペイロードはすでに暗号化されています。サーバーや購読者には暗号文しか見えません。
  2. Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard.
  3. TLS はサーバーへの TCP 接続自体を暗号化し、ネットワークレベルの盗聴を防ぎます。

🔒 Security: The default public channel has a well-known key. デフォルトチャンネルで MQTT 経由で送信されるメッセージは、実質的に暗号化されていません。誰でも解読できます。プライベートな通信には、必ずカスタムの PSK を使用してください。

ベストプラクティス

  • MQTT に橋渡しするチャンネルでは、チャンネルレベルの暗号化（PSK）を使用します
  • Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes memory)
  • 機密性の高い運用にはプライベートサーバーを使用します
  • 混雑した MQTT トピックからメッセージをダウンリンクする際は、電波利用時間に注意してください。ダウンリンクされたメッセージはすべて、ローカルメッシュの無線の電波利用時間を消費します
  • メッセージを送り返さず、リモートでメッシュを監視するだけでよい場合は、アップリンクのみを有効にすることを検討してください

トラブルシューティング

MQTT が接続できない

  • Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT は LoRa の無線リンク自体では動作しません。
  • Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces.
  • Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443).
  • DNS 解決： カスタムのサーバーホスト名を使う場合は、ノードがそれを解決できるか確認してください。サーバーの IP アドレスを直接試してみてください。

メッセージが橋渡しされない

  • アップリンク／ダウンリンクの設定を確認： アップリンクのみが有効な場合、メッセージはメッシュから MQTT へ流れますが、戻ってきません。受信側のゲートウェイでダウンリンクを有効にしてください。
  • チャンネルの不一致： 両方のゲートウェイが、同じ PSK を持つ同じチャンネルを共有している必要があります。不一致の場合、メッセージは異なる鍵で暗号化され、判読できないデータとして表示されます。
  • Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root.
  • Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway.
  • Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in.

関連トピック

+

A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. 同じトピックを購読しているリモートのゲートウェイが、それらのメッセージを自分のローカルメッシュに取り込みます。

設定

MQTT を有効にする

  1. Navigate to Settings → Module configuration → MQTT.
  2. MQTT モジュールを有効にします。
  3. サーバーへの接続を設定します：
設定項目 説明 デフォルト
Address MQTT サーバーのホスト名 mqtt.meshtastic.org
Username サーバーの認証 meshdev
Password サーバーの認証 large4cats
Root topic メッセージのベーストピック msh, which the radio rewrites to msh/<REGION> once you set a region
Encryption enabled MQTT ペイロードを暗号化 有効
JSON output enabled Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it 無効
TLS enabled サーバーへのセキュアな接続 無効
Map reporting 公開マップに位置を報告 無効
Proxy to client enabled Relay MQTT through the connected phone 無効

Connection Status and Test Connection

The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here.

Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason.

このスマートフォンでの MQTT プロキシ

If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection.

ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them.

The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration.

デフォルトの Meshtastic サーバー

コミュニティが mqtt.meshtastic.org で公開サーバーを運用しています。これは一般的な利用やテストを目的としています。

When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without).

🔒 プライバシー： 公開サーバー上のメッセージは、購読している誰もが読めます。プライベートな通信には、必ずチャンネルの暗号化を使用してください。

プライベートサーバー

プライバシーと制御を高めるために、独自の MQTT サーバーを運用できます：

  • Mosquitto（軽量、オープンソース）
  • HiveMQ
  • EMQX

適切な認証情報を設定して、ノードがプライベートサーバーに接続するよう構成します。

マップ報告

When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.

Turning it on opens a consent card. Turn on I agree. and choose a Map Publish Interval of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.

Reports appear at meshmap.net and similar community map services.

🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published.

アップリンクとダウンリンク

方向 説明
アップリンク メッシュ → MQTT サーバーへのメッセージ
ダウンリンク MQTT サーバー → メッシュへのメッセージ

Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on.

メッセージ形式

MQTT carries two payload formats:

形式 説明 用途
Protobuf バイナリの Meshtastic protobuf エンコード ノード間のメッシュ橋渡し
JSON Human-readable JSON on the /2/json/ topic Consumers outside the mesh (dashboards, home automation)

ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads.

暗号化とプライバシー

階層化された暗号化モデルを理解する：

  1. チャンネルの暗号化は、MQTT の前にメッシュ上で行われます。チャンネルに PSK が設定されている場合、MQTT ペイロードはすでに暗号化されています。サーバーや購読者には暗号文しか見えません。
  2. Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard.
  3. TLS はサーバーへの TCP 接続自体を暗号化し、ネットワークレベルの盗聴を防ぎます。

🔒 Security: The default public channel has a well-known key. デフォルトチャンネルで MQTT 経由で送信されるメッセージは、実質的に暗号化されていません。誰でも解読できます。プライベートな通信には、必ずカスタムの PSK を使用してください。

ベストプラクティス

  • MQTT に橋渡しするチャンネルでは、チャンネルレベルの暗号化（PSK）を使用します
  • Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes memory)
  • 機密性の高い運用にはプライベートサーバーを使用します
  • 混雑した MQTT トピックからメッセージをダウンリンクする際は、電波利用時間に注意してください。ダウンリンクされたメッセージはすべて、ローカルメッシュの無線の電波利用時間を消費します
  • メッセージを送り返さず、リモートでメッシュを監視するだけでよい場合は、アップリンクのみを有効にすることを検討してください

トラブルシューティング

MQTT が接続できない

  • Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT は LoRa の無線リンク自体では動作しません。
  • Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces.
  • Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443).
  • DNS 解決： カスタムのサーバーホスト名を使う場合は、ノードがそれを解決できるか確認してください。サーバーの IP アドレスを直接試してみてください。

メッセージが橋渡しされない

  • アップリンク／ダウンリンクの設定を確認： アップリンクのみが有効な場合、メッセージはメッシュから MQTT へ流れますが、戻ってきません。受信側のゲートウェイでダウンリンクを有効にしてください。
  • チャンネルの不一致： 両方のゲートウェイが、同じ PSK を持つ同じチャンネルを共有している必要があります。不一致の場合、メッセージは異なる鍵で暗号化され、判読できないデータとして表示されます。
  • Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root.
  • Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway.
  • Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in.

関連トピック

diff --git a/main/ja-rJP/user/settings-module-admin.html b/main/ja-rJP/user/settings-module-admin.html index 34fcdea307..35125fab9f 100644 --- a/main/ja-rJP/user/settings-module-admin.html +++ b/main/ja-rJP/user/settings-module-admin.html @@ -1 +1 @@ - 設定：モジュールと管理 | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 日本語
Meshtastic Docs ↗

🌐 日本語 — Community translation View in English

設定：モジュールと管理

オプションの機能モジュールを設定し、デバイスの管理を行います。モジュールは、専用の機能で Meshtastic を拡張します。それぞれ個別に有効・無効を切り替えられます。

💡 ヒント： 実際に使うモジュールだけを有効にすれば十分です。使わないモジュールを無効にすると、電波利用時間が減り、バッテリーを節約でき、設定もシンプルになります。 A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.

モジュールの設定は、トグルスイッチ、ドロップダウン、テキストフィールド、スライダーを備えたカード形式のレイアウトを使用します：

A toggle setting in the on position

A dropdown setting, expanded to show its list of options

A text field setting with a value entered

A module settings card with its title and grouped controls

追加機能の設定

Every module lives under Settings → Module configuration.

⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes.

MQTT module

インターネット接続のために、メッシュのメッセージを MQTT サーバーとの間で橋渡しします。 This is how you extend your mesh beyond LoRa range or integrate with home automation systems.

設定項目 説明
MQTTを有効化 MQTT ブリッジを切り替え
アドレス MQTT サーバーのアドレス
ユーザー名 認証用のユーザー名
パスワード 認証用のパスワード
暗号化の有効化 MQTT ペイロードを暗号化
JSON出力の有効化 Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS の有効化 セキュアな接続を使用
ルート トピック MQTT のベーストピックパス
クライアントへのプロキシの有効化 Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself
このスマートフォンの MQTT プロキシ The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT
マップレポート Publish position to the public map — see the Map reporting group that follows

Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:

設定項目 説明
同意します。 Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
マップレポートの間隔 (秒) How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered

暗号化、プライバシー、サーバーの設定を含む詳しい使い方は、MQTT を参照してください。

Serial module

外部デバイスとの連携（GPS モジュール、センサー、カスタムハードウェア）のために、シリアルポート通信を有効にします。有効にすると、ノードのシリアルポートで protobuf またはテキストデータを送受信でき、外部のマイコンやコンピューターがメッシュとやり取りできるようになります。

設定項目 説明
シリアル通信を有効化 シリアル通信を有効化
Echoを有効化 受信したシリアルデータをそのまま返す
シリアルモード Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX GPIO pins for the serial connection
シリアルボーレイト Port speed
タイムアウト How long to wait before considering an incoming message complete
コンソールのシリアルポートを上書き Take over the port the debug console normally uses

External Notification module

Controls buzzer, LED, or vibration alerts on your node hardware. メッセージ到着時に物理的に知らせる必要があるデバイスに便利です。特に無人設置や屋外設置で役立ちます。

There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.

設定項目 説明
外部通知を有効化 Master toggle for the module
Alert message LED / buzzer / vibra Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra Which outputs fire on a received bell character
LED出力 (GPIO) Pin the LED is wired to
LED出力 アクティブハイ Whether the LED pin is active high or low
ブザー出力(GPIO) Pin the buzzer is wired to
バイブレーション出力 (GPIO) Pin the vibration motor is wired to
PWMブザーを使用 Drive the buzzer with PWM, which allows tones rather than a single pitch
I2Sをブザーとして使用 Send the alert through an I2S audio output instead
出力時間 (ミリ秒) How long a single alert lasts
繰り返し通知間隔（秒） Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
着信音 The tone played on a PWM buzzer, in RTTTL. Can be imported from a file

Store & Forward module

一時的にオフラインだったノードのためにメッセージをバッファリングし、それらのノードが再接続したときに再送します。ノードが頻繁に圏内・圏外を行き来するメッシュに不可欠です。短時間の切断中にメッセージが失われないようにします。

設定項目 説明
一時保管と転送の有効化 ストア＆フォワードを有効化
ハートビート このノードのストア＆フォワード機能を定期的に告知する
サーバーの最大保管レコード数 (デフォルト 約11,000レコード) 保存するメッセージの最大数
リクエスト可能な最大の履歴件数 再送するメッセージの最大数
リクエスト可能な履歴の期間 (分) 再送する時間の範囲
サーバー メッシュのストア＆フォワードサーバーとして動作する（十分なメモリが必要、例：PSRAM 搭載の ESP32）

💡 ヒント： ストア＆フォワードは、十分なメモリを持つノード（PSRAM 搭載の ESP32）で最も良く機能します。ルーターノードは通常は常時起動しているため、理想的な候補です。

Range Test module

⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.

ノード間のリンク品質を評価するための、自動レンジテストツールです。有効にすると、ノードはカウンターを増やしながらテストメッセージを定期的に送信します。受信側のノードがこれらのメッセージを記録するため、歩いたり車で移動したりして、後からどの距離でメッセージが届かなくなったかを分析できます。

設定項目 説明
レンジテストを有効化 レンジテストを有効化
送信者のメッセージ間隔 (秒) Time between test transmissions, chosen from a dropdown of fixed intervals
ストレージにCSVファイルを保存(ESP32のみ) Log received test data to the node’s own filesystem. ESP32 hardware only

Telemetry module

ノードがメッシュと共有するテレメトリデータを制御します。テレメトリには、デバイスの状態（バッテリー、連続稼働時間）と環境センサーのデータ（温度、湿度、気圧）が含まれます。

Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.

設定項目 説明
デバイステレメトリを送信 Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
デバイスメトリクスの更新間隔 How often to report battery, uptime and channel utilization
環境メトリクスモジュールを有効化 Report the attached environment sensors
環境メトリクスの更新間隔 How often to report them
環境メトリクスを画面上で有効化 Also show these readings on the device’s own display
環境メトリクスは華氏を使用 Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
空気品質測定モジュールを有効化 Report particulate and CO₂ sensor data
空気品質メトリクスの更新間隔 How often to report them
電源メトリクスモジュール有効 Report the per-channel voltage and current readings
電源メトリクスの更新間隔 How often to report them
電源メトリクスを画面上で有効化 Also show power readings on the device’s display

対応センサーと設定の推奨事項については、テレメトリとセンサー を参照してください。

Canned Message module

Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). スマートフォンを接続していなくても送信できる、クイック送信メッセージのリストを定義します。フィールドでの使用に最適です。

設定項目 説明
Canned message enabled ⚠️ Deprecated in the protobuf schema
メッセージ 改行で区切ったメッセージのリスト
ベルを送信 Send a bell character alongside the message, so a receiving node’s External Notification module can sound
ロータリーエンコーダ #1 を有効化 Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port The three pins the encoder is wired to
Generate input event on Press / CW / CCW Which key event each encoder action produces
上下/選択入力を有効化 A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source ⚠️ Deprecated in the protobuf schema

Audio module

メッシュ上での低帯域幅の音声通信のための、Codec2 音声サポートです。これは、Codec2 コーデックを使って音声を非常に小さなデータパケットにエンコードする、実験的な機能です。

設定項目 説明
CODEC 2 を有効化 オーディオモジュールを有効化
CODEC2 サンプルレート 音質と帯域幅のトレードオフ
PTT端子 GPIO pin for the push-to-talk button
I2S ワードセレクト I2S WS 用の GPIO ピン
I2S データ IN I2S DIN 用の GPIO ピン
I2S データ OUT I2S DOUT 用の GPIO ピン
I2S クロック GPIO pin for the I2S bit clock

ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). 音質は非常に低帯域です。「聞き取れる無線の声」程度で、電話並みの品質ではないと考えてください。

Remote Hardware module

メッシュネットワーク経由での GPIO 制御です。リモートのノードが、別のノードの GPIO ピンを読み書きできるようにします。リレーの作動、スイッチの読み取り、離れた場所からの外部ハードウェア制御に便利です。

⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.

設定項目 説明
リモートハードウェアを有効化 リモート GPIO アクセスを有効化
未定義のピンへのアクセスを許可 任意の GPIO ピンへのアクセスを許可（セキュリティリスク）
使用可能な端子 このノードがリモートの読み書き用に公開する GPIO ピン（最大 4 個）

Neighbor Info module

直接受信した隣接ノードの情報をブロードキャストし、メッシュのトポロジーマッピングを可能にします。有効にした各ノードは、受信できる他のノードとその信号品質のリストを定期的に共有します。

設定項目 説明
近隣ノード情報を有効化 隣接ノードのブロードキャストを有効化
更新間隔 (秒) 隣接ノードのリストをブロードキャストする頻度
LoRaで送信 MQTT／スマートフォンだけでなく、LoRa 経由でも隣接ノード情報をブロードキャストします。デフォルトの鍵と名前を使用しているチャンネルでは利用できません

See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.

Ambient Lighting module

対応ハードウェア上の、オンボードの NeoPixel やその他のアドレサブル RGB LED を制御します。視覚的なステータス表示、通知ライト、装飾的な演出に使用できます。

設定項目 説明
LEDの状態 LED のオン／オフを切り替え
電流 LED の電流制限（0〜31）
赤／緑／青 各色チャンネルの値（0〜255）

Detection Sensor module

ノードを、動きやドアを検知するセンサーアラートシステムに変えます。 GPIO ピンが状態の変化（動きの検知、ドアの開放）を検出すると、ノードはメッシュ経由でアラートメッセージをブロードキャストします。

設定項目 説明
検出センサーを有効化 検知センサーを有効化
モニターのGPIOピン センサーに接続された GPIO ピン
検出トリガーの種類 ピンの状態を検知イベントにどう対応させるか（例：アクティブハイ／ロー、エッジトリガー）
INPUT_PULLUP モードを使用 ピンの内蔵プルアップ抵抗を有効にする
最小ブロードキャスト間隔(秒) アラートのブロードキャスト間の最小時間
状態のブロードキャスト間隔 (秒) 定期的な状態ブロードキャストの間隔
アラートメッセージ付きのベルを送信 アラートにベル文字を含める
名前 このセンサーのカスタム名

Paxcounter module

People counter using Wi-Fi and BLE probe requests. スマートフォンやノートパソコンがネットワークを探すときに発するプローブ要求を受動的に受信して、近くのデバイスを数えます。 ESP32 デバイスでのみ利用できます。

設定 説明
Paxcounter を有効化 人数カウントを有効化
更新間隔 (秒) カウントを報告する頻度
Wi-Fi RSSI threshold Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE RSSI threshold The same cut-off for BLE advertisements (defaults to −80 dBm)

💡 ヒント： Paxcounter は、登山口やイベント会場などの人出を推定するのに便利です。カウントはおおよその値です。1 人が複数のデバイスを持っていることがあります。

Status Message module

The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.

Mesh Beacon module

Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.

TAK module

ATAK および WinTAK と相互運用するための、Team Awareness Kit 連携です。 Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. 詳しい設定と使い方は、TAK 連携 を参照してください。

管理

リモート管理

管理者鍵を共有しているノードをリモートで設定します：

  1. ノードリストで対象のノードを選択します。
  2. そのノードの「設定」に移動します。
  3. 設定を変更します。
  4. 「保存」をタップします。変更がメッシュ経由で送信されます。

⚠️ Important: Requires an admin key configured on both your node and the target node.

Device Actions

Settings → Administration holds five one-shot actions, each behind a confirmation dialog:

操作 内容
時刻を設定 Sends your phone’s clock to the node
再起動 Restarts the node
シャットダウン Powers the node down
出荷時にリセット Returns every setting to its factory default
NodeDBをリセット Clears the node database. This dialog carries a Preserve Favorites? switch

⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.

バックアップと復元

Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.

詳細設定

Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.

ノードデータベースの整理

Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.

  • Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
  • Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.

The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.

デバッグ

診断出力の表示・絞り込み・エクスポートを行う「パケット」タブと「アプリログ」タブを開きます。詳しい手順は、デバッグログ を参照してください。

App Settings

The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:

Privacy

  • Allow analytics and crash reporting — opt in or out of diagnostics.
  • Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
  • Homoglyph encoding — how look-alike characters in names are handled.

Appearance

  • Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
  • Theme and Language.
  • Show full message timestamps.

Persistence

  • A cache limit for how much history is kept.
  • Export rangetest packets, Export all packets and Export node database.

On their own

  • Node Layout — how much detail each row of the node list shows.
  • Wi-Fi Provisioning for mPWRD-OS — see Connections.
  • Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
  • System AI — appears only where app functions are available; see App Functions.

A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.

概要

Settings → About carries the app’s own identity rather than the node’s:

Three sections:

  • What is Meshtastic? — a short description of the project.
  • Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
  • Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.

The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.

謝辞

Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.

Troubleshooting remote admin

  • 「対象ノードから応答がありません」：対象が圏外、オフライン、または管理者鍵が一致していない可能性があります。両方のノードで管理者鍵が一致しているか確認してください。
  • 変更が適用されない：一部の設定は、反映に再起動が必要です。保存後に「再起動」を実行してみてください。
  • リモートの設定が表示されない：自分のノードに、対象ノードの管理者鍵があることを確認してください。管理チャンネルは、管理者鍵を設定すると自動的に構成されます。

関連トピック

+ 設定：モジュールと管理 | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 日本語
Meshtastic Docs ↗

🌐 日本語 — Community translation View in English

設定：モジュールと管理

オプションの機能モジュールを設定し、デバイスの管理を行います。モジュールは、専用の機能で Meshtastic を拡張します。それぞれ個別に有効・無効を切り替えられます。

💡 ヒント： 実際に使うモジュールだけを有効にすれば十分です。使わないモジュールを無効にすると、電波利用時間が減り、バッテリーを節約でき、設定もシンプルになります。 A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.

モジュールの設定は、トグルスイッチ、ドロップダウン、テキストフィールド、スライダーを備えたカード形式のレイアウトを使用します：

A toggle setting in the on position

A dropdown setting, expanded to show its list of options

A text field setting with a value entered

A module settings card with its title and grouped controls

追加機能の設定

Every module lives under Settings → Module configuration.

⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes.

MQTT module

インターネット接続のために、メッシュのメッセージを MQTT サーバーとの間で橋渡しします。 This is how you extend your mesh beyond LoRa range or integrate with home automation systems.

設定項目 説明
MQTTを有効化 MQTT ブリッジを切り替え
アドレス MQTT サーバーのアドレス
ユーザー名 認証用のユーザー名
パスワード 認証用のパスワード
暗号化の有効化 MQTT ペイロードを暗号化
JSON出力の有効化 Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS の有効化 セキュアな接続を使用
ルート トピック MQTT のベーストピックパス
クライアントへのプロキシの有効化 Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself
このスマートフォンの MQTT プロキシ The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT
マップレポート Publish position to the public map — see the Map reporting group that follows

Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:

設定項目 説明
同意します。 Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered

暗号化、プライバシー、サーバーの設定を含む詳しい使い方は、MQTT を参照してください。

Serial module

外部デバイスとの連携（GPS モジュール、センサー、カスタムハードウェア）のために、シリアルポート通信を有効にします。有効にすると、ノードのシリアルポートで protobuf またはテキストデータを送受信でき、外部のマイコンやコンピューターがメッシュとやり取りできるようになります。

設定項目 説明
シリアル通信を有効化 シリアル通信を有効化
Echoを有効化 受信したシリアルデータをそのまま返す
シリアルモード Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX GPIO pins for the serial connection
シリアルボーレイト Port speed
タイムアウト How long to wait before considering an incoming message complete
コンソールのシリアルポートを上書き Take over the port the debug console normally uses

External Notification module

Controls buzzer, LED, or vibration alerts on your node hardware. メッセージ到着時に物理的に知らせる必要があるデバイスに便利です。特に無人設置や屋外設置で役立ちます。

There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.

設定項目 説明
外部通知を有効化 Master toggle for the module
Alert message LED / buzzer / vibra Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra Which outputs fire on a received bell character
LED出力 (GPIO) Pin the LED is wired to
LED出力 アクティブハイ Whether the LED pin is active high or low
ブザー出力(GPIO) Pin the buzzer is wired to
バイブレーション出力 (GPIO) Pin the vibration motor is wired to
PWMブザーを使用 Drive the buzzer with PWM, which allows tones rather than a single pitch
I2Sをブザーとして使用 Send the alert through an I2S audio output instead
GPIO Output Duration How long a single alert lasts
Nag Timeout Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
着信音 The tone played on a PWM buzzer, in RTTTL. Can be imported from a file

Store & Forward module

一時的にオフラインだったノードのためにメッセージをバッファリングし、それらのノードが再接続したときに再送します。ノードが頻繁に圏内・圏外を行き来するメッシュに不可欠です。短時間の切断中にメッセージが失われないようにします。

設定項目 説明
一時保管と転送の有効化 ストア＆フォワードを有効化
ハートビート このノードのストア＆フォワード機能を定期的に告知する
サーバーの最大保管レコード数 (デフォルト 約11,000レコード) 保存するメッセージの最大数
リクエスト可能な最大の履歴件数 再送するメッセージの最大数
リクエスト可能な履歴の期間 (分) 再送する時間の範囲
サーバー メッシュのストア＆フォワードサーバーとして動作する（十分なメモリが必要、例：PSRAM 搭載の ESP32）

💡 ヒント： ストア＆フォワードは、十分なメモリを持つノード（PSRAM 搭載の ESP32）で最も良く機能します。ルーターノードは通常は常時起動しているため、理想的な候補です。

Range Test module

⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.

ノード間のリンク品質を評価するための、自動レンジテストツールです。有効にすると、ノードはカウンターを増やしながらテストメッセージを定期的に送信します。受信側のノードがこれらのメッセージを記録するため、歩いたり車で移動したりして、後からどの距離でメッセージが届かなくなったかを分析できます。

設定項目 説明
レンジテストを有効化 レンジテストを有効化
Sender Interval Time between test transmissions, chosen from a dropdown of fixed intervals
ストレージにCSVファイルを保存(ESP32のみ) Log received test data to the node’s own filesystem. ESP32 hardware only

Telemetry module

ノードがメッシュと共有するテレメトリデータを制御します。テレメトリには、デバイスの状態（バッテリー、連続稼働時間）と環境センサーのデータ（温度、湿度、気圧）が含まれます。

Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.

設定項目 説明
デバイステレメトリを送信 Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
デバイスメトリクスの更新間隔 How often to report battery, uptime and channel utilization
環境メトリクスモジュールを有効化 Report the attached environment sensors
環境メトリクスの更新間隔 How often to report them
環境メトリクスを画面上で有効化 Also show these readings on the device’s own display
環境メトリクスは華氏を使用 Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
空気品質測定モジュールを有効化 Report particulate and CO₂ sensor data
空気品質メトリクスの更新間隔 How often to report them
電源メトリクスモジュール有効 Report the per-channel voltage and current readings
電源メトリクスの更新間隔 How often to report them
電源メトリクスを画面上で有効化 Also show power readings on the device’s display

対応センサーと設定の推奨事項については、テレメトリとセンサー を参照してください。

Canned Message module

Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). スマートフォンを接続していなくても送信できる、クイック送信メッセージのリストを定義します。フィールドでの使用に最適です。

設定項目 説明
Canned message enabled ⚠️ Deprecated in the protobuf schema
メッセージ 改行で区切ったメッセージのリスト
ベルを送信 Send a bell character alongside the message, so a receiving node’s External Notification module can sound
ロータリーエンコーダ #1 を有効化 Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port The three pins the encoder is wired to
Generate input event on Press / CW / CCW Which key event each encoder action produces
上下/選択入力を有効化 A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source ⚠️ Deprecated in the protobuf schema

Audio module

メッシュ上での低帯域幅の音声通信のための、Codec2 音声サポートです。これは、Codec2 コーデックを使って音声を非常に小さなデータパケットにエンコードする、実験的な機能です。

設定項目 説明
CODEC 2 を有効化 オーディオモジュールを有効化
CODEC2 サンプルレート 音質と帯域幅のトレードオフ
PTT端子 GPIO pin for the push-to-talk button
I2S ワードセレクト I2S WS 用の GPIO ピン
I2S データ IN I2S DIN 用の GPIO ピン
I2S データ OUT I2S DOUT 用の GPIO ピン
I2S クロック GPIO pin for the I2S bit clock

ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). 音質は非常に低帯域です。「聞き取れる無線の声」程度で、電話並みの品質ではないと考えてください。

Remote Hardware module

メッシュネットワーク経由での GPIO 制御です。リモートのノードが、別のノードの GPIO ピンを読み書きできるようにします。リレーの作動、スイッチの読み取り、離れた場所からの外部ハードウェア制御に便利です。

⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.

設定項目 説明
リモートハードウェアを有効化 リモート GPIO アクセスを有効化
未定義のピンへのアクセスを許可 任意の GPIO ピンへのアクセスを許可（セキュリティリスク）
使用可能な端子 このノードがリモートの読み書き用に公開する GPIO ピン（最大 4 個）

Neighbor Info module

直接受信した隣接ノードの情報をブロードキャストし、メッシュのトポロジーマッピングを可能にします。有効にした各ノードは、受信できる他のノードとその信号品質のリストを定期的に共有します。

設定項目 説明
近隣ノード情報を有効化 隣接ノードのブロードキャストを有効化
GPS ポーリング間隔 隣接ノードのリストをブロードキャストする頻度
LoRaで送信 MQTT／スマートフォンだけでなく、LoRa 経由でも隣接ノード情報をブロードキャストします。デフォルトの鍵と名前を使用しているチャンネルでは利用できません

See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.

Ambient Lighting module

対応ハードウェア上の、オンボードの NeoPixel やその他のアドレサブル RGB LED を制御します。視覚的なステータス表示、通知ライト、装飾的な演出に使用できます。

設定項目 説明
LEDの状態 LED のオン／オフを切り替え
電流 LED の電流制限（0〜31）
赤／緑／青 各色チャンネルの値（0〜255）

Detection Sensor module

ノードを、動きやドアを検知するセンサーアラートシステムに変えます。 GPIO ピンが状態の変化（動きの検知、ドアの開放）を検出すると、ノードはメッシュ経由でアラートメッセージをブロードキャストします。

設定項目 説明
検出センサーを有効化 検知センサーを有効化
モニターのGPIOピン センサーに接続された GPIO ピン
検出トリガーの種類 ピンの状態を検知イベントにどう対応させるか（例：アクティブハイ／ロー、エッジトリガー）
INPUT_PULLUP モードを使用 ピンの内蔵プルアップ抵抗を有効にする
Minimum time between detection broadcasts アラートのブロードキャスト間の最小時間
State Broadcast Interval 定期的な状態ブロードキャストの間隔
アラートメッセージ付きのベルを送信 アラートにベル文字を含める
名前 このセンサーのカスタム名

Paxcounter module

People counter using Wi-Fi and BLE probe requests. スマートフォンやノートパソコンがネットワークを探すときに発するプローブ要求を受動的に受信して、近くのデバイスを数えます。 ESP32 デバイスでのみ利用できます。

設定 説明
Paxcounter を有効化 人数カウントを有効化
GPS ポーリング間隔 カウントを報告する頻度
WiFi Threshold (dBm) Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm) The same cut-off for BLE advertisements (defaults to −80 dBm)

💡 ヒント： Paxcounter は、登山口やイベント会場などの人出を推定するのに便利です。カウントはおおよその値です。1 人が複数のデバイスを持っていることがあります。

Status Message module

The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.

Mesh Beacon module

Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.

TAK module

ATAK および WinTAK と相互運用するための、Team Awareness Kit 連携です。 Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. 詳しい設定と使い方は、TAK 連携 を参照してください。

管理

リモート管理

管理者鍵を共有しているノードをリモートで設定します：

  1. ノードリストで対象のノードを選択します。
  2. そのノードの「設定」に移動します。
  3. 設定を変更します。
  4. 「保存」をタップします。変更がメッシュ経由で送信されます。

⚠️ Important: Requires an admin key configured on both your node and the target node.

Device Actions

Settings → Administration holds five one-shot actions, each behind a confirmation dialog:

操作 内容
時刻を設定 Sends your phone’s clock to the node
再起動 Restarts the node
シャットダウン Powers the node down
出荷時にリセット Returns every setting to its factory default
NodeDBをリセット Clears the node database. This dialog carries a Preserve Favorites? switch

⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.

バックアップと復元

Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.

詳細設定

Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.

ノードデータベースの整理

Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.

  • Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
  • Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.

The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.

デバッグ

診断出力の表示・絞り込み・エクスポートを行う「パケット」タブと「アプリログ」タブを開きます。詳しい手順は、デバッグログ を参照してください。

App Settings

The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:

Privacy

  • Allow analytics and crash reporting — opt in or out of diagnostics.
  • Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
  • Homoglyph encoding — how look-alike characters in names are handled.

Appearance

  • Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
  • Theme and Language.
  • Show full message timestamps.

Persistence

  • A cache limit for how much history is kept.
  • Export rangetest packets, Export all packets and Export node database.

On their own

  • Node Layout — how much detail each row of the node list shows.
  • Wi-Fi Provisioning for mPWRD-OS — see Connections.
  • Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
  • System AI — appears only where app functions are available; see App Functions.

A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.

概要

Settings → About carries the app’s own identity rather than the node’s:

Three sections:

  • What is Meshtastic? — a short description of the project.
  • Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
  • Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.

The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.

謝辞

Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.

Troubleshooting remote admin

  • 「対象ノードから応答がありません」：対象が圏外、オフライン、または管理者鍵が一致していない可能性があります。両方のノードで管理者鍵が一致しているか確認してください。
  • 変更が適用されない：一部の設定は、反映に再起動が必要です。保存後に「再起動」を実行してみてください。
  • リモートの設定が表示されない：自分のノードに、対象ノードの管理者鍵があることを確認してください。管理チャンネルは、管理者鍵を設定すると自動的に構成されます。

関連トピック

diff --git a/main/ja-rJP/user/settings-radio-user.html b/main/ja-rJP/user/settings-radio-user.html index 9d11d75001..a85f4e1782 100644 --- a/main/ja-rJP/user/settings-radio-user.html +++ b/main/ja-rJP/user/settings-radio-user.html @@ -1 +1 @@ - 設定：無線機とユーザー | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 日本語
Meshtastic Docs ↗

🌐 日本語 — Community translation View in English

設定：無線機とユーザー

Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How these screens work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth.

設定には、標準的な設定コントロール（ドロップダウン、トグル、スライダー）を使用します：

コントロール スクリーンショット
ドロップダウン A dropdown setting, expanded to show its list of options
トグル A toggle setting in the on position
スライダー A slider setting with its current numeric value shown

ユーザー設定

ユーザープロファイル

On Settings → User.

設定項目 説明
正式名称 表示名（最大 39 文字）
短縮名 4 文字の短縮名
ステータスメッセージ A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
メッセージ不可 Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur node (Ham) Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in.

設定

デバイスの設定

On Settings → Device configuration → Device.

設定項目 説明 デフォルト
デバイスの役割 Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
再ブロードキャストモード How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
ノード情報のブロードキャスト間隔 How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
ダブルタップをボタンとして使用 Treat a double tap as a button press 無効
トリプルクリックでアドホック Ping Send an ad-hoc position ping on a triple click 有効
LED ハートビート Blink the status LED periodically 有効
タイムゾーン POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it —
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to —

LoRa設定

On Settings → LoRa.

設定項目 説明 デフォルト
リージョン Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number 未設定（要設定）
プリセット 速度と距離のトレードオフ LongFast
ホップ数 再送信の最大ホップ数 3
送信出力 送信出力（dBm）。0 = リージョンで許可された最大値 0（リージョン最大）
周波数の上書き Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
プリセットを使用 On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
拡散率 Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead From preset
符号化レート Manual mode only: 5–8. More redundancy costs airtime From preset
帯域 Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one From preset
周波数スロット Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
送信を有効化 Turning this off makes the node receive-only On
デューティサイクルを上書き Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits オフ
MQTT を無視 Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
MQTT への送信を許可 Allow your packets to be forwarded to MQTT by gateways オフ
RX ブーストゲイン Extra receive gain on SX126x radios; costs a little current オフ
PAファン無効 Turn off the power-amplifier fan on hardware that has one オフ

The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set.

Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. 詳しくは、meshtastic.org の リージョン設定ガイド を参照してください。

Modem presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes.

💡 ヒント： SNR 限界の値は意図的に負の数になっています。 LoRa はノイズフロアを下回る信号でも復調できるため、より負の大きい限界値ほど、そのプリセットは弱くノイズの多い信号に耐えられます（より遠くまで届きます）。詳しい説明は、信号メーターの仕組み を参照してください。

プリセット 距離 速度 SNR 限界 最適な用途
Short Turbo ~1 km 21.9 kbps −7.5 dB 見通しのある高密度な都市部。データ量の多い用途
Short Fast ~3 km 10.9 kbps −7.5 dB 都市の住宅街。数ブロック以内の建物
Short Slow ~5 km 6.25 kbps −10 dB 郊外の短距離。中程度の建物密度
Medium Fast ~5 km 3.52 kbps −12.5 dB 郊外エリア。中程度の建物密度
Medium Slow ~8 km 1.95 kbps −15 dB 郊外・地方。中程度の距離で低速
Long Turbo ~10 km 1.34 kbps −17.5 dB Long Fast と同程度の距離だが 500 kHz 帯域幅。スループットが速い
Long Fast ~10 km 1.1 kbps −17.5 dB 一般用途（デフォルト）：距離と速度のバランスが良い
Long Moderate ~20 km 0.34 kbps −17.5 dB 起伏のある地方。ときどき使う用途
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD 帯（125 kHz 帯域幅）。Medium Fast に相当
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD 帯（125 kHz 帯域幅）。Long Fast に相当
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz 帯（62.5 kHz 帯域幅）。他のデバイスとの干渉を避ける
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz 帯（62.5 kHz 帯域幅）。Long Fast に相当
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ 非推奨：まだ選択できますが、将来のファームウェアリリースで削除される可能性があります
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ 非推奨：まだ選択できますが、将来のファームウェアリリースで削除される可能性があります

ℹ️ 注意： この表では、一般的な短い名前を使用しています。 The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a modem preset

モデムプリセットは、距離とデータ速度の基本的なトレードオフを制御します：

  • 遅いプリセットは拡散をより多く使い、より弱い信号レベルでも復調できるようにします（SNR 限界が低い）。これは、より遠くまで届く一方で、1 秒あたりのバイト数が少ないことを意味します。
  • 速いプリセットは 1 回の送信でより多くのデータを詰め込みますが、復調にはより強い信号が必要です。

実用的な指針：

  • 都市部のメッシュ（多数のノード、短距離）： Long Fast（デフォルト）または Short Fast を使用します。速度が速いほど、多くのノードがチャンネルを共有するときの電波利用時間の輻輳が減ります。
  • 地方・まばらなメッシュ（少数のノード、長距離）： Long Moderate を使用します。ノードが離れている場合は、速度よりも距離が重要です。
  • EU 866／868 MHz の規制対応： Lite Fast、Lite Slow、Narrow Fast、Narrow Slow を使用します。これらは、より狭い帯域幅で EU の SRD／868 MHz 帯に最適化されています。
  • 固定インフラのリンク： 良好なアンテナと見通しがある専用のポイントツーポイントリンクには、Short Turbo または Long Turbo を使用します。
  • 混在した環境： Long Fast のままにします。これはコミュニティのデフォルトで、地域内の他のユーザーとの互換性を確保します。

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. 高所（丘の上、屋上）にあると、実効的な距離が大幅に伸びます。適切に設置された Long Fast のルーターは、地上に置かれた Long Slow のノードを上回ることがよくあります。

表示設定

On Settings → Device configuration → Display. These control the node’s own screen, not the app’s.

設定項目 説明
画面オンの時間 How long the display stays lit before sleeping
カルーセルの間隔 How often the node cycles between screens on its own
表示モード Screen layout/density used by the firmware
表示単位 Metric or Imperial on the node’s screen
12時間の時計形式を使用 Show the node’s clock as 12-hour rather than 24-hour
太字の見出し Draw the screen’s heading text in bold
画面反転 Rotate the display 180° for an inverted mounting
OLED タイプ Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED
タップまたは動作で起動 Light the screen when the node is tapped or moved
コンパスの向き Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each
常に北を上にする Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

位置情報設定

On Settings → Device configuration → Position.

設定項目 説明
GPS モード（物理ハードウェア） Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS ポーリング間隔 How often the node asks its GPS for a fix
ブロードキャスト間隔 How often the position is shared with the mesh
スマート位置 Broadcast based on movement rather than purely on the clock
スマート間隔 With Smart Position on, the shortest gap between broadcasts
スマート距離 With Smart Position on, how far you must move before broadcasting
固定位置 Use a manually entered latitude, longitude and altitude instead of the GPS
位置情報フラグ A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

電源設定

On Settings → Device configuration → Power.

設定項目 説明
省電力モードを有効化 Let the node sleep aggressively between activity
電源喪失時にシャットダウン Power the device down after external power disappears
スーパーディープスリープの時間 How long the deepest sleep state lasts
最小起動時間 The shortest time the node stays awake once woken
Bluetooth 待機時間 How long to wait for a phone to connect before sleeping
ADC倍率のオーバーライド Turn on a manual correction for battery-voltage readings
ADC倍率のオーバーライド比 The correction factor itself, used only when the override is on
バッテリー INA_2XX I2C アドレス Address of an external INA-series power sensor, if fitted

ネットワーク設定

On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node.

設定項目 説明
Wi-Fi enabled Enable the Wi-Fi node (ESP32 nodes)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
パスワード ネットワークのパスワード
イーサネット有効 Use a wired connection on hardware that has one
IPv4 モード DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP ブロードキャスト Share mesh traffic with other nodes over the local network
NTPサーバー 時刻同期サーバー
rsyslogサーバー リモートログサーバー

Network Config with a static IPv4 address entered

Bluetooth 設定

On Settings → Device configuration → Bluetooth, on nodes with Bluetooth.

設定項目 説明
Bluetoothを有効 BLE 無線の有効／無効
ペアリングモード 固定 PIN、ランダム PIN、または PIN なし
固定 PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

セキュリティ設定

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

設定項目 説明
公開鍵 ノードの公開鍵（読み取り専用）
管理者鍵 Keys permitted to administer this node remotely — up to three
秘密鍵 Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it
秘密鍵を再生成 Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
管理チャンネルを有効化 ⚠️ 削除されました：管理者キーを設定すると自動的に構成されるようになりました
シリアルコンソール Serial console over the Stream API
デバッグログAPIを有効化 Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth
管理モード Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set
鍵をバックアップ Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
鍵を復元 バックアップした鍵をノードに書き戻します（バックアップがある場合に利用可能）
鍵のバックアップを削除 Remove the stored key backup from this phone
保護レベル How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device.

Alongside the passphrase you set the limits that end a session automatically:

Field 内容
残りの起動回数 How many device boots the unlocked state survives
有効期限までの時間 Wall-clock lifetime of the unlocked state
セッション上限（分） A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.

関連トピック

+ 設定：無線機とユーザー | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 日本語
Meshtastic Docs ↗

🌐 日本語 — Community translation View in English

設定：無線機とユーザー

Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How these screens work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth.

設定には、標準的な設定コントロール（ドロップダウン、トグル、スライダー）を使用します：

コントロール スクリーンショット
ドロップダウン A dropdown setting, expanded to show its list of options
トグル A toggle setting in the on position
スライダー A slider setting with its current numeric value shown

ユーザー設定

ユーザープロファイル

On Settings → User.

設定項目 説明
正式名称 表示名（最大 39 文字）
短縮名 4 文字の短縮名
ステータスメッセージ A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
メッセージ不可 Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur node (Ham) Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in.

設定

デバイスの設定

On Settings → Device configuration → Device.

設定項目 説明 デフォルト
デバイスの役割 Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
再ブロードキャストモード How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
ノード情報のブロードキャスト間隔 How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
ダブルタップをボタンとして使用 Treat a double tap as a button press 無効
トリプルクリックでアドホック Ping Send an ad-hoc position ping on a triple click 有効
LED ハートビート Blink the status LED periodically 有効
タイムゾーン POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it —
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to —

LoRa設定

On Settings → LoRa.

設定項目 説明 デフォルト
リージョン Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number 未設定（要設定）
プリセット 速度と距離のトレードオフ LongFast
ホップ数 再送信の最大ホップ数 3
Transmit Power (dBm) Transmission power; 0 = max allowed for region 0（リージョン最大）
周波数の上書き Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
プリセットを使用 On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
拡散率 Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead From preset
符号化レート Manual mode only: 5–8. More redundancy costs airtime From preset
帯域 Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one From preset
周波数スロット Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
送信を有効化 Turning this off makes the node receive-only On
デューティサイクルを上書き Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits オフ
MQTT を無視 Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
MQTT への送信を許可 Allow your packets to be forwarded to MQTT by gateways オフ
RX ブーストゲイン Extra receive gain on SX126x radios; costs a little current オフ
PAファン無効 Turn off the power-amplifier fan on hardware that has one オフ

The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set.

Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. 詳しくは、meshtastic.org の リージョン設定ガイド を参照してください。

Modem presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes.

💡 ヒント： SNR 限界の値は意図的に負の数になっています。 LoRa はノイズフロアを下回る信号でも復調できるため、より負の大きい限界値ほど、そのプリセットは弱くノイズの多い信号に耐えられます（より遠くまで届きます）。詳しい説明は、信号メーターの仕組み を参照してください。

プリセット 距離 速度 SNR 限界 最適な用途
Short Turbo ~1 km 21.9 kbps −7.5 dB 見通しのある高密度な都市部。データ量の多い用途
Short Fast ~3 km 10.9 kbps −7.5 dB 都市の住宅街。数ブロック以内の建物
Short Slow ~5 km 6.25 kbps −10 dB 郊外の短距離。中程度の建物密度
Medium Fast ~5 km 3.52 kbps −12.5 dB 郊外エリア。中程度の建物密度
Medium Slow ~8 km 1.95 kbps −15 dB 郊外・地方。中程度の距離で低速
Long Turbo ~10 km 1.34 kbps −17.5 dB Long Fast と同程度の距離だが 500 kHz 帯域幅。スループットが速い
Long Fast ~10 km 1.1 kbps −17.5 dB 一般用途（デフォルト）：距離と速度のバランスが良い
Long Moderate ~20 km 0.34 kbps −17.5 dB 起伏のある地方。ときどき使う用途
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD 帯（125 kHz 帯域幅）。Medium Fast に相当
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD 帯（125 kHz 帯域幅）。Long Fast に相当
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz 帯（62.5 kHz 帯域幅）。他のデバイスとの干渉を避ける
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz 帯（62.5 kHz 帯域幅）。Long Fast に相当
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ 非推奨：まだ選択できますが、将来のファームウェアリリースで削除される可能性があります
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ 非推奨：まだ選択できますが、将来のファームウェアリリースで削除される可能性があります

ℹ️ 注意： この表では、一般的な短い名前を使用しています。 The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a modem preset

モデムプリセットは、距離とデータ速度の基本的なトレードオフを制御します：

  • 遅いプリセットは拡散をより多く使い、より弱い信号レベルでも復調できるようにします（SNR 限界が低い）。これは、より遠くまで届く一方で、1 秒あたりのバイト数が少ないことを意味します。
  • 速いプリセットは 1 回の送信でより多くのデータを詰め込みますが、復調にはより強い信号が必要です。

実用的な指針：

  • 都市部のメッシュ（多数のノード、短距離）： Long Fast（デフォルト）または Short Fast を使用します。速度が速いほど、多くのノードがチャンネルを共有するときの電波利用時間の輻輳が減ります。
  • 地方・まばらなメッシュ（少数のノード、長距離）： Long Moderate を使用します。ノードが離れている場合は、速度よりも距離が重要です。
  • EU 866／868 MHz の規制対応： Lite Fast、Lite Slow、Narrow Fast、Narrow Slow を使用します。これらは、より狭い帯域幅で EU の SRD／868 MHz 帯に最適化されています。
  • 固定インフラのリンク： 良好なアンテナと見通しがある専用のポイントツーポイントリンクには、Short Turbo または Long Turbo を使用します。
  • 混在した環境： Long Fast のままにします。これはコミュニティのデフォルトで、地域内の他のユーザーとの互換性を確保します。

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. 高所（丘の上、屋上）にあると、実効的な距離が大幅に伸びます。適切に設置された Long Fast のルーターは、地上に置かれた Long Slow のノードを上回ることがよくあります。

表示設定

On Settings → Device configuration → Display. These control the node’s own screen, not the app’s.

設定項目 説明
画面オンの時間 How long the display stays lit before sleeping
カルーセルの間隔 How often the node cycles between screens on its own
表示モード Screen layout/density used by the firmware
表示単位 Metric or Imperial on the node’s screen
12時間の時計形式を使用 Show the node’s clock as 12-hour rather than 24-hour
太字の見出し Draw the screen’s heading text in bold
画面反転 Rotate the display 180° for an inverted mounting
OLED タイプ Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED
タップまたは動作で起動 Light the screen when the node is tapped or moved
コンパスの向き Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each
常に北を上にする Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

位置情報設定

On Settings → Device configuration → Position.

設定項目 説明
GPS モード（物理ハードウェア） Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS ポーリング間隔 How often the node asks its GPS for a fix
ブロードキャスト間隔 How often the position is shared with the mesh
スマート位置 Broadcast based on movement rather than purely on the clock
スマート間隔 With Smart Position on, the shortest gap between broadcasts
スマート距離 With Smart Position on, how far you must move before broadcasting
固定位置 Use a manually entered latitude, longitude and altitude instead of the GPS
位置情報フラグ A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

電源設定

On Settings → Device configuration → Power.

設定項目 説明
省電力モードを有効化 Let the node sleep aggressively between activity
電源喪失時にシャットダウン Power the device down after external power disappears
スーパーディープスリープの時間 How long the deepest sleep state lasts
最小起動時間 The shortest time the node stays awake once woken
Bluetooth 待機時間 How long to wait for a phone to connect before sleeping
ADC倍率のオーバーライド Turn on a manual correction for battery-voltage readings
ADC倍率のオーバーライド比 The correction factor itself, used only when the override is on
バッテリー INA_2XX I2C アドレス Address of an external INA-series power sensor, if fitted

ネットワーク設定

On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node.

設定項目 説明
Wi-Fi enabled Enable the Wi-Fi node (ESP32 nodes)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
パスワード ネットワークのパスワード
イーサネット有効 Use a wired connection on hardware that has one
IPv4 モード DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP ブロードキャスト Share mesh traffic with other nodes over the local network
NTPサーバー 時刻同期サーバー
rsyslogサーバー リモートログサーバー

Network Config with a static IPv4 address entered

Bluetooth 設定

On Settings → Device configuration → Bluetooth, on nodes with Bluetooth.

設定項目 説明
Bluetoothを有効 BLE 無線の有効／無効
ペアリングモード 固定 PIN、ランダム PIN、または PIN なし
固定 PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

セキュリティ設定

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

設定項目 説明
公開鍵 ノードの公開鍵（読み取り専用）
管理者鍵 Keys permitted to administer this node remotely — up to three
秘密鍵 Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it
秘密鍵を再生成 Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
管理チャンネルを有効化 ⚠️ 削除されました：管理者キーを設定すると自動的に構成されるようになりました
シリアルコンソール Serial console over the Stream API
デバッグログAPIを有効化 Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth
管理モード Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set
鍵をバックアップ Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
鍵を復元 バックアップした鍵をノードに書き戻します（バックアップがある場合に利用可能）
鍵のバックアップを削除 Remove the stored key backup from this phone
保護レベル How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device.

Alongside the passphrase you set the limits that end a session automatically:

Field 内容
残りの起動回数 How many device boots the unlocked state survives
有効期限までの時間 Wall-clock lifetime of the unlocked state
セッション上限（分） A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.

関連トピック

diff --git a/main/ko-rKR/user/discovery.html b/main/ko-rKR/user/discovery.html index 81fece1663..e40cd6785f 100644 --- a/main/ko-rKR/user/discovery.html +++ b/main/ko-rKR/user/discovery.html @@ -5,4 +5,4 @@ ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) -

Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:.

What to look for What it means
All hops show Good SNR (green) Healthy path — messages flow reliably
One hop shows a poor SNR (orange or red) Weak link — this relay segment is fragile
Many hops (4+) Long path — consider repositioning a node to shorten it
Different path on retry Mesh is adapting — multiple routes exist (this is good!)

💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network.

Troubleshooting with Traceroute

  • No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key.
  • Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa.
  • Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position.
  • Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric.

이웃 정보

The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh.

Enabling Neighbor Info

  1. Navigate to Settings → Module configuration → Neighbor Info.
  2. Enable the module.
  3. Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
  4. Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air.

Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.

Viewing neighbor data

  • Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors.
  • Each neighbor entry shows the node that was directly heard and its signal quality.
  • Combine neighbor data from multiple nodes to understand the full mesh topology.

ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further.

Node list as a discovery tool

The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively.

Finding new nodes

  • Sort by Last heard to see the most recently active nodes at the top.
  • Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes.

Assessing connectivity

  • Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed.
  • Sort by Distance to find nearby nodes and verify they’re reachable.
  • Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge).

Infrastructure audit

  • Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes.
  • Check their signal quality and last-heard times to verify your infrastructure nodes are healthy.

See Nodes for full details on filtering and sorting options.

Tips for Mesh exploration

  • Start with traceroute — it gives you immediate, actionable information about a specific path.
  • Enable Neighbor Info on key nodes — especially routers and repeaters, to build a picture of the backbone.
  • Check the map — node positions on the Map combined with signal data help you understand why some links are strong and others are weak.
  • Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly.
+

Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:.

What to look for What it means
All hops show Good SNR (green) Healthy path — messages flow reliably
One hop shows a poor SNR (orange or red) Weak link — this relay segment is fragile
Many hops (4+) Long path — consider repositioning a node to shorten it
Different path on retry Mesh is adapting — multiple routes exist (this is good!)

💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network.

Troubleshooting with Traceroute

  • No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key.
  • Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa.
  • Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position.
  • Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric.

이웃 정보

The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh.

Enabling Neighbor Info

  1. Navigate to Settings → Module configuration → Neighbor Info.
  2. Enable the module.
  3. Set Update Interval. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
  4. Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air.

Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.

Viewing neighbor data

  • Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors.
  • Each neighbor entry shows the node that was directly heard and its signal quality.
  • Combine neighbor data from multiple nodes to understand the full mesh topology.

ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further.

Node list as a discovery tool

The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively.

Finding new nodes

  • Sort by Last heard to see the most recently active nodes at the top.
  • Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes.

Assessing connectivity

  • Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed.
  • Sort by Distance to find nearby nodes and verify they’re reachable.
  • Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge).

Infrastructure audit

  • Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes.
  • Check their signal quality and last-heard times to verify your infrastructure nodes are healthy.

See Nodes for full details on filtering and sorting options.

Tips for Mesh exploration

  • Start with traceroute — it gives you immediate, actionable information about a specific path.
  • Enable Neighbor Info on key nodes — especially routers and repeaters, to build a picture of the backbone.
  • Check the map — node positions on the Map combined with signal data help you understand why some links are strong and others are weak.
  • Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly.
diff --git a/main/ko-rKR/user/mqtt.html b/main/ko-rKR/user/mqtt.html index 3124893d27..b867a9176a 100644 --- a/main/ko-rKR/user/mqtt.html +++ b/main/ko-rKR/user/mqtt.html @@ -1,2 +1,2 @@ MQTT | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 한국어
Meshtastic Docs ↗

🌐 한국어 — Community translation View in English

MQTT

MQTT bridges your Meshtastic mesh network to the internet, enabling long-range communication beyond radio range.

Overview

The MQTT module connects your node to an MQTT broker, allowing:

  • Messages to reach nodes on different physical meshes via the internet
  • Integration with home automation and monitoring systems
  • Publishing node positions to the public Meshtastic map
  • Custom data pipelines for logging and alerting

How It Works 

[Your Node] → Radio → [Gateway Node with Wi-Fi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node]
-

A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh.

설정

Enabling MQTT

  1. Navigate to Settings → Module configuration → MQTT.
  2. Enable the MQTT module.
  3. Configure the broker connection:
Setting 설명 기본값
Address MQTT broker hostname mqtt.meshtastic.org
Username Broker authentication meshdev
Password Broker authentication large4cats
Root topic Base topic for messages msh, which the radio rewrites to msh/<REGION> once you set a region
Encryption enabled Encrypt MQTT payload 활성화
JSON output enabled Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it Disabled
TLS enabled Secure connection to broker Disabled
Map reporting Report position to public map Disabled
Proxy to client enabled Relay MQTT through the connected phone Disabled

Connection Status and Test Connection

The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here.

Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason.

MQTT Proxy on This Phone

If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection.

ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them.

The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration.

Default Meshtastic Broker

The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing.

When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without).

🔒 Privacy: Messages on the public broker are readable by anyone subscribed. Always use channel encryption for private communications.

Private Broker

For better privacy and control, you can run your own MQTT broker:

  • Mosquitto (lightweight, open-source)
  • HiveMQ
  • EMQX

Configure your node to point to your private broker with appropriate credentials.

Map Reporting

When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.

Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.

Reports appear at meshmap.net and similar community map services.

🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published.

Direction 설명
Uplink Messages from mesh → MQTT broker
Downlink Messages from MQTT broker → mesh

Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on.

Message Formats

MQTT carries two payload formats:

Format 설명 Use case
Protobuf Binary Meshtastic protobuf encoding Node-to-node mesh bridging
JSON Human-readable JSON on the /2/json/ topic Consumers outside the mesh (dashboards, home automation)

ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads.

Encryption & Privacy

Understanding the layered encryption model:

  1. Channel encryption happens on the mesh before MQTT. If your channel has a PSK, the MQTT payload is already encrypted — the broker and any subscribers see only the ciphertext.
  2. Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard.
  3. TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping.

🔒 Security: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications.

Best Practices

  • Use channel-level encryption (PSK) on channels that bridge to MQTT
  • Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes memory)
  • Use a private broker for sensitive deployments
  • Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh
  • Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back

Troubleshooting

MQTT Not Connecting

  • Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself.
  • Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces.
  • Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443).
  • DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly.

Messages Not Bridging

  • Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway.
  • Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage.
  • Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root.
  • Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway.
  • Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in.
+

A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh.

설정

Enabling MQTT

  1. Navigate to Settings → Module configuration → MQTT.
  2. Enable the MQTT module.
  3. Configure the broker connection:
Setting 설명 기본값
Address MQTT broker hostname mqtt.meshtastic.org
Username Broker authentication meshdev
Password Broker authentication large4cats
Root topic Base topic for messages msh, which the radio rewrites to msh/<REGION> once you set a region
Encryption enabled Encrypt MQTT payload 활성화
JSON output enabled Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it Disabled
TLS enabled Secure connection to broker Disabled
Map reporting Report position to public map Disabled
Proxy to client enabled Relay MQTT through the connected phone Disabled

Connection Status and Test Connection

The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here.

Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason.

MQTT Proxy on This Phone

If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection.

ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them.

The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration.

Default Meshtastic Broker

The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing.

When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without).

🔒 Privacy: Messages on the public broker are readable by anyone subscribed. Always use channel encryption for private communications.

Private Broker

For better privacy and control, you can run your own MQTT broker:

  • Mosquitto (lightweight, open-source)
  • HiveMQ
  • EMQX

Configure your node to point to your private broker with appropriate credentials.

Map Reporting

When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.

Turning it on opens a consent card. Turn on I agree. and choose a Map Publish Interval of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.

Reports appear at meshmap.net and similar community map services.

🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published.

Direction 설명
Uplink Messages from mesh → MQTT broker
Downlink Messages from MQTT broker → mesh

Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on.

Message Formats

MQTT carries two payload formats:

Format 설명 Use case
Protobuf Binary Meshtastic protobuf encoding Node-to-node mesh bridging
JSON Human-readable JSON on the /2/json/ topic Consumers outside the mesh (dashboards, home automation)

ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads.

Encryption & Privacy

Understanding the layered encryption model:

  1. Channel encryption happens on the mesh before MQTT. If your channel has a PSK, the MQTT payload is already encrypted — the broker and any subscribers see only the ciphertext.
  2. Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard.
  3. TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping.

🔒 Security: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications.

Best Practices

  • Use channel-level encryption (PSK) on channels that bridge to MQTT
  • Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes memory)
  • Use a private broker for sensitive deployments
  • Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh
  • Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back

Troubleshooting

MQTT Not Connecting

  • Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself.
  • Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces.
  • Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443).
  • DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly.

Messages Not Bridging

  • Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway.
  • Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage.
  • Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root.
  • Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway.
  • Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in.
diff --git a/main/ko-rKR/user/settings-module-admin.html b/main/ko-rKR/user/settings-module-admin.html index 1b01bb4d57..0b8236f7d0 100644 --- a/main/ko-rKR/user/settings-module-admin.html +++ b/main/ko-rKR/user/settings-module-admin.html @@ -1 +1 @@ - Settings — Modules & Admin | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 한국어
Meshtastic Docs ↗

🌐 한국어 — Community translation View in English

Settings — Modules & Admin

Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.

💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.

Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:

A toggle setting in the on position

A dropdown setting, expanded to show its list of options

A text field setting with a value entered

A module settings card with its title and grouped controls

모듈 설정

Every module lives under Settings → Module configuration.

⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes.

MQTT module

Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.

Setting 설명
MQTT 활성화 Toggle MQTT bridge
서버 주소 MQTT broker address
사용자명 Authentication username
비밀번호 Authentication password
암호화 사용 Encrypt MQTT payloads
JSON 사용 Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS 사용 Use secure connection
Root topic Base MQTT topic path
Proxy to client 사용 Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy on this phone The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT
맵 보고 Publish position to the public map — see the Map reporting group that follows

Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:

Setting 설명
동의합니다. Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
맵 보고 간격 (초) How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered

See MQTT for a detailed usage guide including encryption, privacy, and broker setup.

Serial module

Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.

Setting 설명
시리얼 활성화 Activate serial communication
에코 활성화 Echo received serial data back
시리얼 모드 Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX GPIO pins for the serial connection
시리얼 baud rate Port speed
시간 초과 How long to wait before considering an incoming message complete
Override console serial port Take over the port the debug console normally uses

External Notification module

Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.

There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.

Setting 설명
외부 알림 활성화 Master toggle for the module
Alert message LED / buzzer / vibra Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra Which outputs fire on a received bell character
LED 출력 (GPIO) Pin the LED is wired to
LED 출력 active high Whether the LED pin is active high or low
부저 출력 (GPIO) Pin the buzzer is wired to
진동 출력 (GPIO) Pin the vibration motor is wired to
PWM 부저 사용 Drive the buzzer with PWM, which allows tones rather than a single pitch
I2S 부저 사용 Send the alert through an I2S audio output instead
출력 지속시간 (밀리초) How long a single alert lasts
반복 종료 시간 (초) Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
벨소리 The tone played on a PWM buzzer, in RTTTL. Can be imported from a file

Store & Forward module

Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.

Setting 설명
저장 및 전달 활성화 Activate store and forward
Heartbeat Periodically announce this node’s store-and-forward capability
Number of records Maximum stored messages
History return max Max messages to replay
History return window Time window for replay
서버 Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)

💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.

Range Test module

⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.

Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.

Setting 설명
거리 테스트 활성화 Activate range testing
송신 장치 메시지 간격 (초) Time between test transmissions, chosen from a dropdown of fixed intervals
.CSV 파일 저장 (EPS32만 동작) Log received test data to the node’s own filesystem. ESP32 hardware only

Telemetry module

Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).

Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.

Setting 설명
Send Device Telemetry Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval How often to report battery, uptime and channel utilization
환경 메트릭 모듈 사용 Report the attached environment sensors
Environment metrics update interval How often to report them
환경 메트릭 화면 사용 Also show these readings on the device’s own display
환경 메트릭에서 화씨 사용 Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
대기질 메트릭 모듈 사용 Report particulate and CO₂ sensor data
Air quality metrics update interval How often to report them
전력 메트릭 모듈 사용 Report the per-channel voltage and current readings
Power metrics update interval How often to report them
전력 메트릭 화면 사용 Also show power readings on the device’s display

See Telemetry & Sensors for supported sensors and configuration recommendations.

Canned Message module

Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.

Setting 설명
Canned message enabled ⚠️ Deprecated in the protobuf schema
메시지기기 Newline-separated list of messages
벨 전송 Send a bell character alongside the message, so a receiving node’s External Notification module can sound
로터리 엔코더 #1 활성화 Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port The three pins the encoder is wired to
Generate input event on Press / CW / CCW Which key event each encoder action produces
업/다운/선택 입력 활성화 A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source ⚠️ Deprecated in the protobuf schema

Audio module

Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.

Setting 설명
CODEC2 활성화 Activate audio module
CODEC2 샘플 레이트 Audio quality/bandwidth tradeoff
PTT 핀 GPIO pin for the push-to-talk button
I2S 단어 선택 GPIO pin for I2S WS
I2S 데이터 in GPIO pin for I2S DIN
I2S 데이터 out GPIO pin for I2S DOUT
I2S 시간 GPIO pin for the I2S bit clock

ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.

Remote Hardware module

GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.

⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.

Setting 설명
원격 하드웨어 활성화 Activate remote GPIO access
Allow undefined pin access Allow access to any GPIO pin (security risk)
Available pins Up to 4 GPIO pins this node exposes for remote read/write

Neighbor Info module

Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.

Setting 설명
이웃 정보 활성화 Activate neighbor broadcasting
업데이트 간격 (초) How often to broadcast neighbor list
LoRa로 전송 Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name

See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.

Ambient Lighting module

Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.

Setting 설명
LED 상태 Turn the LED on or off
전류 LED current limit (0–31)
Red / Green / Blue Individual color channel values (0–255)

Detection Sensor module

Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.

Setting 설명
감지 센서 활성화 Activate detection sensor
상태 모니터링 GPIO 핀 GPIO pin connected to sensor
디텍션 트리거 타입 How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
INPUT_PULLUP 모드 사용 Enable the pin’s internal pull-up resistor
최소 전송 간격 (초) Minimum time between alert broadcasts
상태 전송 간격 (초) Periodic state broadcast interval
알람 메시지와 벨 전송 Include bell character in alerts
식별 이름 Custom name for this sensor

Paxcounter module

People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.

Setting 설명
팍스카운터 활성화 Activate people counting
업데이트 간격 (초) How often to report counts
Wi-Fi RSSI threshold Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE RSSI threshold The same cut-off for BLE advertisements (defaults to −80 dBm)

💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.

Status Message module

The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.

Mesh Beacon module

Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.

TAK module

Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.

관리

원격 설정

Remotely configure nodes that share your admin key:

  1. Select the target node in the node list.
  2. Navigate to Settings for that node.
  3. Modify configuration.
  4. Tap Save — changes are sent over the mesh.

⚠️ Important: Requires an admin key configured on both your node and the target node.

Device Actions

Settings → Administration holds five one-shot actions, each behind a confirmation dialog:

Action What it does
Set time Sends your phone’s clock to the node
재부팅 Restarts the node
종료 Powers the node down
공장초기화 Returns every setting to its factory default
노드 목록 리셋 Clears the node database. This dialog carries a Preserve Favorites? switch

⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.

백업 & 복구

Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.

고급

Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.

Clean Node Database

Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.

  • Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
  • Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.

The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.

디버그 패널

Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.

App Settings

The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:

Privacy

  • Allow analytics and crash reporting — opt in or out of diagnostics.
  • Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
  • Homoglyph encoding — how look-alike characters in names are handled.

Appearance

  • Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
  • Theme and Language.
  • Show full message timestamps.

Persistence

  • A cache limit for how much history is kept.
  • Export rangetest packets, Export all packets and Export node database.

On their own

  • Node Layout — how much detail each row of the node list shows.
  • Wi-Fi Provisioning for mPWRD-OS — see Connections.
  • Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
  • System AI — appears only where app functions are available; see App Functions.

A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.

앱에 대하여

Settings → About carries the app’s own identity rather than the node’s:

Three sections:

  • What is Meshtastic? — a short description of the project.
  • Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
  • Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.

The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.

Acknowledgements

Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.

Troubleshooting remote admin

  • “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
  • Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
  • Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
+ Settings — Modules & Admin | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 한국어
Meshtastic Docs ↗

🌐 한국어 — Community translation View in English

Settings — Modules & Admin

Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.

💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.

Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:

A toggle setting in the on position

A dropdown setting, expanded to show its list of options

A text field setting with a value entered

A module settings card with its title and grouped controls

모듈 설정

Every module lives under Settings → Module configuration.

⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes.

MQTT module

Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.

Setting 설명
MQTT 활성화 Toggle MQTT bridge
서버 주소 MQTT broker address
사용자명 Authentication username
비밀번호 Authentication password
암호화 사용 Encrypt MQTT payloads
JSON 사용 Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS 사용 Use secure connection
Root topic Base MQTT topic path
Proxy to client 사용 Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy on this phone The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT
맵 보고 Publish position to the public map — see the Map reporting group that follows

Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:

Setting 설명
동의합니다. Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered

See MQTT for a detailed usage guide including encryption, privacy, and broker setup.

Serial module

Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.

Setting 설명
시리얼 활성화 Activate serial communication
에코 활성화 Echo received serial data back
시리얼 모드 Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX GPIO pins for the serial connection
시리얼 baud rate Port speed
시간 초과 How long to wait before considering an incoming message complete
Override console serial port Take over the port the debug console normally uses

External Notification module

Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.

There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.

Setting 설명
외부 알림 활성화 Master toggle for the module
Alert message LED / buzzer / vibra Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra Which outputs fire on a received bell character
LED 출력 (GPIO) Pin the LED is wired to
LED 출력 active high Whether the LED pin is active high or low
부저 출력 (GPIO) Pin the buzzer is wired to
진동 출력 (GPIO) Pin the vibration motor is wired to
PWM 부저 사용 Drive the buzzer with PWM, which allows tones rather than a single pitch
I2S 부저 사용 Send the alert through an I2S audio output instead
GPIO Output Duration How long a single alert lasts
Nag Timeout Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
벨소리 The tone played on a PWM buzzer, in RTTTL. Can be imported from a file

Store & Forward module

Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.

Setting 설명
저장 및 전달 활성화 Activate store and forward
Heartbeat Periodically announce this node’s store-and-forward capability
Number of records Maximum stored messages
History return max Max messages to replay
History return window Time window for replay
서버 Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)

💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.

Range Test module

⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.

Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.

Setting 설명
거리 테스트 활성화 Activate range testing
Sender Interval Time between test transmissions, chosen from a dropdown of fixed intervals
.CSV 파일 저장 (EPS32만 동작) Log received test data to the node’s own filesystem. ESP32 hardware only

Telemetry module

Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).

Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.

Setting 설명
Send Device Telemetry Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval How often to report battery, uptime and channel utilization
환경 메트릭 모듈 사용 Report the attached environment sensors
Environment metrics update interval How often to report them
환경 메트릭 화면 사용 Also show these readings on the device’s own display
환경 메트릭에서 화씨 사용 Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
대기질 메트릭 모듈 사용 Report particulate and CO₂ sensor data
Air quality metrics update interval How often to report them
전력 메트릭 모듈 사용 Report the per-channel voltage and current readings
Power metrics update interval How often to report them
전력 메트릭 화면 사용 Also show power readings on the device’s display

See Telemetry & Sensors for supported sensors and configuration recommendations.

Canned Message module

Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.

Setting 설명
Canned message enabled ⚠️ Deprecated in the protobuf schema
메시지기기 Newline-separated list of messages
벨 전송 Send a bell character alongside the message, so a receiving node’s External Notification module can sound
로터리 엔코더 #1 활성화 Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port The three pins the encoder is wired to
Generate input event on Press / CW / CCW Which key event each encoder action produces
업/다운/선택 입력 활성화 A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source ⚠️ Deprecated in the protobuf schema

Audio module

Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.

Setting 설명
CODEC2 활성화 Activate audio module
CODEC2 샘플 레이트 Audio quality/bandwidth tradeoff
PTT 핀 GPIO pin for the push-to-talk button
I2S 단어 선택 GPIO pin for I2S WS
I2S 데이터 in GPIO pin for I2S DIN
I2S 데이터 out GPIO pin for I2S DOUT
I2S 시간 GPIO pin for the I2S bit clock

ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.

Remote Hardware module

GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.

⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.

Setting 설명
원격 하드웨어 활성화 Activate remote GPIO access
Allow undefined pin access Allow access to any GPIO pin (security risk)
Available pins Up to 4 GPIO pins this node exposes for remote read/write

Neighbor Info module

Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.

Setting 설명
이웃 정보 활성화 Activate neighbor broadcasting
Update Interval How often to broadcast neighbor list
LoRa로 전송 Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name

See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.

Ambient Lighting module

Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.

Setting 설명
LED 상태 Turn the LED on or off
전류 LED current limit (0–31)
Red / Green / Blue Individual color channel values (0–255)

Detection Sensor module

Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.

Setting 설명
감지 센서 활성화 Activate detection sensor
상태 모니터링 GPIO 핀 GPIO pin connected to sensor
디텍션 트리거 타입 How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
INPUT_PULLUP 모드 사용 Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts Minimum time between alert broadcasts
State Broadcast Interval Periodic state broadcast interval
알람 메시지와 벨 전송 Include bell character in alerts
식별 이름 Custom name for this sensor

Paxcounter module

People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.

Setting 설명
팍스카운터 활성화 Activate people counting
Update Interval How often to report counts
WiFi Threshold (dBm) Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm) The same cut-off for BLE advertisements (defaults to −80 dBm)

💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.

Status Message module

The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.

Mesh Beacon module

Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.

TAK module

Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.

관리

원격 설정

Remotely configure nodes that share your admin key:

  1. Select the target node in the node list.
  2. Navigate to Settings for that node.
  3. Modify configuration.
  4. Tap Save — changes are sent over the mesh.

⚠️ Important: Requires an admin key configured on both your node and the target node.

Device Actions

Settings → Administration holds five one-shot actions, each behind a confirmation dialog:

Action What it does
Set time Sends your phone’s clock to the node
재부팅 Restarts the node
종료 Powers the node down
공장초기화 Returns every setting to its factory default
노드 목록 리셋 Clears the node database. This dialog carries a Preserve Favorites? switch

⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.

백업 & 복구

Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.

고급

Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.

Clean Node Database

Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.

  • Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
  • Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.

The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.

디버그 패널

Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.

App Settings

The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:

Privacy

  • Allow analytics and crash reporting — opt in or out of diagnostics.
  • Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
  • Homoglyph encoding — how look-alike characters in names are handled.

Appearance

  • Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
  • Theme and Language.
  • Show full message timestamps.

Persistence

  • A cache limit for how much history is kept.
  • Export rangetest packets, Export all packets and Export node database.

On their own

  • Node Layout — how much detail each row of the node list shows.
  • Wi-Fi Provisioning for mPWRD-OS — see Connections.
  • Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
  • System AI — appears only where app functions are available; see App Functions.

A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.

앱에 대하여

Settings → About carries the app’s own identity rather than the node’s:

Three sections:

  • What is Meshtastic? — a short description of the project.
  • Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
  • Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.

The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.

Acknowledgements

Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.

Troubleshooting remote admin

  • “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
  • Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
  • Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
diff --git a/main/ko-rKR/user/settings-radio-user.html b/main/ko-rKR/user/settings-radio-user.html index 408d9477f7..ae47125a17 100644 --- a/main/ko-rKR/user/settings-radio-user.html +++ b/main/ko-rKR/user/settings-radio-user.html @@ -1 +1 @@ - Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 한국어
Meshtastic Docs ↗

🌐 한국어 — Community translation View in English

Settings — Radio & User

Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How these screens work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting 설명
긴 이름 Your display name (up to 39 characters)
짧은 이름 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
메시지 제한 Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur node (Ham) Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in.

설정

장치 설정

On Settings → Device configuration → Device.

Setting 설명 기본값
Device Role Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
중계 모드 How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
노드 정보 발송 주기 How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Double Tap as Button Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click 활성화
LED Heartbeat Blink the status LED periodically 활성화
Time Zone POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it —
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to —

LoRa 설정

On Settings → LoRa.

Setting 설명 기본값
지역 Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number Unset (must configure)
Presets Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
전송 출력 Transmission power (dBm); 0 = max allowed for region 0 (region max)
Frequency Override Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
프리셋 사용 On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead From preset
Coding rate Manual mode only: 5–8. More redundancy costs airtime From preset
대역폭 Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one From preset
주파수 슬롯 Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
전송 활성화 Turning this off makes the node receive-only On
Duty Cycle 무시 Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
MQTT로 부터 수신 무시 Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok to MQTT Allow your packets to be forwarded to MQTT by gateways Off
RX Boosted Gain Extra receive gain on SX126x radios; costs a little current Off
PA fan 비활성화됨 Turn off the power-amplifier fan on hardware that has one Off

The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set.

Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Speed SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a modem preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

화면 설정

On Settings → Device configuration → Display. These control the node’s own screen, not the app’s.

Setting 설명
Screen on for How long the display stays lit before sleeping
Carousel interval How often the node cycles between screens on its own
디스플레이 모드 Screen layout/density used by the firmware
단위 표시 Metric or Imperial on the node’s screen
12시간제 보기 Show the node’s clock as 12-hour rather than 24-hour
상태표시줄 볼드체 Draw the screen’s heading text in bold
화면 뒤집기 Rotate the display 180° for an inverted mounting
OLED type Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED
Wake on tap or motion Light the screen when the node is tapped or moved
나침반 방향 Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each
Always point north Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

위치 설정

On Settings → Device configuration → Position.

Setting 설명
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the node asks its GPS for a fix
전송 간격 How often the position is shared with the mesh
Smart Position Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Fixed Position Use a manually entered latitude, longitude and altitude instead of the GPS
Position Flags A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

전원 설정

On Settings → Device configuration → Power.

Setting 설명
저전력 모드 설정 Let the node sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the node stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC multiplier override ratio The correction factor itself, used only when the override is on
Battery INA_2XX I2C address Address of an external INA-series power sensor, if fitted

네트워크 설정

On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node.

Setting 설명
Wi-Fi enabled Enable the Wi-Fi node (ESP32 nodes)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
비밀번호 네트워크 암호
이더넷 활성화 Use a wired connection on hardware that has one
IPv4 모드 DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP 서버 Time synchronization server
rsyslog 서버 Remote logging server

Network Config with a static IPv4 address entered

블루투스 설정

On Settings → Device configuration → Bluetooth, on nodes with Bluetooth.

Setting 설명
블루투스 활성화 Enable/disable BLE radio
페어링 모드 Fixed PIN, Random PIN, or No PIN
고정 PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

보안 설정

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

Setting 설명
공개 키 Your node’s public key (read-only)
Admin 키 Keys permitted to administer this node remotely — up to three
개인 키 Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it
개인 키 다시 생성하기 Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
시리얼 콘솔 Serial console over the Stream API
Debug log API enabled Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth
관리 모드 Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.

+ Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 한국어
Meshtastic Docs ↗

🌐 한국어 — Community translation View in English

Settings — Radio & User

Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How these screens work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting 설명
긴 이름 Your display name (up to 39 characters)
짧은 이름 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
메시지 제한 Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur node (Ham) Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in.

설정

장치 설정

On Settings → Device configuration → Device.

Setting 설명 기본값
Device Role Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
중계 모드 How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
노드 정보 발송 주기 How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Double Tap as Button Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click 활성화
LED Heartbeat Blink the status LED periodically 활성화
Time Zone POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it —
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to —

LoRa 설정

On Settings → LoRa.

Setting 설명 기본값
지역 Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number Unset (must configure)
Presets Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Transmit Power (dBm) Transmission power; 0 = max allowed for region 0 (region max)
Frequency Override Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
프리셋 사용 On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead From preset
Coding rate Manual mode only: 5–8. More redundancy costs airtime From preset
대역폭 Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one From preset
주파수 슬롯 Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
전송 활성화 Turning this off makes the node receive-only On
Duty Cycle 무시 Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
MQTT로 부터 수신 무시 Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok to MQTT Allow your packets to be forwarded to MQTT by gateways Off
RX Boosted Gain Extra receive gain on SX126x radios; costs a little current Off
PA fan 비활성화됨 Turn off the power-amplifier fan on hardware that has one Off

The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set.

Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Speed SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a modem preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

화면 설정

On Settings → Device configuration → Display. These control the node’s own screen, not the app’s.

Setting 설명
Screen on for How long the display stays lit before sleeping
Carousel interval How often the node cycles between screens on its own
디스플레이 모드 Screen layout/density used by the firmware
단위 표시 Metric or Imperial on the node’s screen
12시간제 보기 Show the node’s clock as 12-hour rather than 24-hour
상태표시줄 볼드체 Draw the screen’s heading text in bold
화면 뒤집기 Rotate the display 180° for an inverted mounting
OLED type Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED
Wake on tap or motion Light the screen when the node is tapped or moved
나침반 방향 Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each
Always point north Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

위치 설정

On Settings → Device configuration → Position.

Setting 설명
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the node asks its GPS for a fix
전송 간격 How often the position is shared with the mesh
Smart Position Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Fixed Position Use a manually entered latitude, longitude and altitude instead of the GPS
Position Flags A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

전원 설정

On Settings → Device configuration → Power.

Setting 설명
저전력 모드 설정 Let the node sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the node stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC multiplier override ratio The correction factor itself, used only when the override is on
Battery INA_2XX I2C address Address of an external INA-series power sensor, if fitted

네트워크 설정

On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node.

Setting 설명
Wi-Fi enabled Enable the Wi-Fi node (ESP32 nodes)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
비밀번호 네트워크 암호
이더넷 활성화 Use a wired connection on hardware that has one
IPv4 모드 DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP 서버 Time synchronization server
rsyslog 서버 Remote logging server

Network Config with a static IPv4 address entered

블루투스 설정

On Settings → Device configuration → Bluetooth, on nodes with Bluetooth.

Setting 설명
블루투스 활성화 Enable/disable BLE radio
페어링 모드 Fixed PIN, Random PIN, or No PIN
고정 PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

보안 설정

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

Setting 설명
공개 키 Your node’s public key (read-only)
Admin 키 Keys permitted to administer this node remotely — up to three
개인 키 Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it
개인 키 다시 생성하기 Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
시리얼 콘솔 Serial console over the Stream API
Debug log API enabled Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth
관리 모드 Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.

diff --git a/main/lt-rLT/user/discovery.html b/main/lt-rLT/user/discovery.html index eac18c16c6..088d30f3af 100644 --- a/main/lt-rLT/user/discovery.html +++ b/main/lt-rLT/user/discovery.html @@ -5,4 +5,4 @@ ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) -

Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:.

What to look for What it means
All hops show Good SNR (green) Healthy path — messages flow reliably
One hop shows a poor SNR (orange or red) Weak link — this relay segment is fragile
Many hops (4+) Long path — consider repositioning a node to shorten it
Different path on retry Mesh is adapting — multiple routes exist (this is good!)

💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network.

Troubleshooting with Traceroute

  • No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key.
  • Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa.
  • Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position.
  • Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric.

Neighbor Info

The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh.

Enabling Neighbor Info

  1. Navigate to Settings → Module configuration → Neighbor Info.
  2. Enable the module.
  3. Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
  4. Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air.

Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.

Viewing neighbor data

  • Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors.
  • Each neighbor entry shows the node that was directly heard and its signal quality.
  • Combine neighbor data from multiple nodes to understand the full mesh topology.

ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further.

Node list as a discovery tool

The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively.

Finding new nodes

  • Sort by Last heard to see the most recently active nodes at the top.
  • Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes.

Assessing connectivity

  • Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed.
  • Sort by Distance to find nearby nodes and verify they’re reachable.
  • Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge).

Infrastructure audit

  • Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes.
  • Check their signal quality and last-heard times to verify your infrastructure nodes are healthy.

See Nodes for full details on filtering and sorting options.

Tips for Mesh exploration

  • Start with traceroute — it gives you immediate, actionable information about a specific path.
  • Enable Neighbor Info on key nodes — especially routers and repeaters, to build a picture of the backbone.
  • Check the map — node positions on the Map combined with signal data help you understand why some links are strong and others are weak.
  • Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly.
+

Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:.

What to look for What it means
All hops show Good SNR (green) Healthy path — messages flow reliably
One hop shows a poor SNR (orange or red) Weak link — this relay segment is fragile
Many hops (4+) Long path — consider repositioning a node to shorten it
Different path on retry Mesh is adapting — multiple routes exist (this is good!)

💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network.

Troubleshooting with Traceroute

  • No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key.
  • Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa.
  • Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position.
  • Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric.

Neighbor Info

The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh.

Enabling Neighbor Info

  1. Navigate to Settings → Module configuration → Neighbor Info.
  2. Enable the module.
  3. Set Update Interval. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
  4. Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air.

Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.

Viewing neighbor data

  • Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors.
  • Each neighbor entry shows the node that was directly heard and its signal quality.
  • Combine neighbor data from multiple nodes to understand the full mesh topology.

ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further.

Node list as a discovery tool

The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively.

Finding new nodes

  • Sort by Last heard to see the most recently active nodes at the top.
  • Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes.

Assessing connectivity

  • Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed.
  • Sort by Distance to find nearby nodes and verify they’re reachable.
  • Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge).

Infrastructure audit

  • Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes.
  • Check their signal quality and last-heard times to verify your infrastructure nodes are healthy.

See Nodes for full details on filtering and sorting options.

Tips for Mesh exploration

  • Start with traceroute — it gives you immediate, actionable information about a specific path.
  • Enable Neighbor Info on key nodes — especially routers and repeaters, to build a picture of the backbone.
  • Check the map — node positions on the Map combined with signal data help you understand why some links are strong and others are weak.
  • Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly.
diff --git a/main/lt-rLT/user/mqtt.html b/main/lt-rLT/user/mqtt.html index 56df27f202..a793b589a2 100644 --- a/main/lt-rLT/user/mqtt.html +++ b/main/lt-rLT/user/mqtt.html @@ -1,2 +1,2 @@ MQTT | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Lietuvių
Meshtastic Docs ↗

🌐 Lietuvių — Community translation View in English

MQTT

MQTT bridges your Meshtastic mesh network to the internet, enabling long-range communication beyond radio range.

Overview

The MQTT module connects your node to an MQTT broker, allowing:

  • Messages to reach nodes on different physical meshes via the internet
  • Integration with home automation and monitoring systems
  • Publishing node positions to the public Meshtastic map
  • Custom data pipelines for logging and alerting

How It Works 

[Your Node] → Radio → [Gateway Node with Wi-Fi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node]
-

A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh.

Configuration

Enabling MQTT

  1. Navigate to Settings → Module configuration → MQTT.
  2. Enable the MQTT module.
  3. Configure the broker connection:
Setting Aprašymas Default
Address MQTT broker hostname mqtt.meshtastic.org
Username Broker authentication meshdev
Password Broker authentication large4cats
Root topic Base topic for messages msh, which the radio rewrites to msh/<REGION> once you set a region
Encryption enabled Encrypt MQTT payload Enabled
JSON output enabled Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it Disabled
TLS enabled Secure connection to broker Disabled
Map reporting Report position to public map Disabled
Proxy to client enabled Relay MQTT through the connected phone Disabled

Connection Status and Test Connection

The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here.

Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason.

MQTT Proxy on This Phone

If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection.

ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them.

The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration.

Default Meshtastic Broker

The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing.

When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without).

🔒 Privacy: Messages on the public broker are readable by anyone subscribed. Always use channel encryption for private communications.

Private Broker

For better privacy and control, you can run your own MQTT broker:

  • Mosquitto (lightweight, open-source)
  • HiveMQ
  • EMQX

Configure your node to point to your private broker with appropriate credentials.

Map Reporting

When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.

Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.

Reports appear at meshmap.net and similar community map services.

🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published.

Direction Aprašymas
Uplink Messages from mesh → MQTT broker
Downlink Messages from MQTT broker → mesh

Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on.

Message Formats

MQTT carries two payload formats:

Format Aprašymas Use case
Protobuf Binary Meshtastic protobuf encoding Node-to-node mesh bridging
JSON Human-readable JSON on the /2/json/ topic Consumers outside the mesh (dashboards, home automation)

ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads.

Encryption & Privacy

Understanding the layered encryption model:

  1. Channel encryption happens on the mesh before MQTT. If your channel has a PSK, the MQTT payload is already encrypted — the broker and any subscribers see only the ciphertext.
  2. Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard.
  3. TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping.

🔒 Security: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications.

Best Practices

  • Use channel-level encryption (PSK) on channels that bridge to MQTT
  • Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes memory)
  • Use a private broker for sensitive deployments
  • Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh
  • Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back

Troubleshooting

MQTT Not Connecting

  • Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself.
  • Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces.
  • Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443).
  • DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly.

Messages Not Bridging

  • Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway.
  • Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage.
  • Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root.
  • Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway.
  • Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in.
+

A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh.

Configuration

Enabling MQTT

  1. Navigate to Settings → Module configuration → MQTT.
  2. Enable the MQTT module.
  3. Configure the broker connection:
Setting Aprašymas Default
Address MQTT broker hostname mqtt.meshtastic.org
Username Broker authentication meshdev
Password Broker authentication large4cats
Root topic Base topic for messages msh, which the radio rewrites to msh/<REGION> once you set a region
Encryption enabled Encrypt MQTT payload Enabled
JSON output enabled Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it Disabled
TLS enabled Secure connection to broker Disabled
Map reporting Report position to public map Disabled
Proxy to client enabled Relay MQTT through the connected phone Disabled

Connection Status and Test Connection

The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here.

Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason.

MQTT Proxy on This Phone

If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection.

ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them.

The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration.

Default Meshtastic Broker

The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing.

When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without).

🔒 Privacy: Messages on the public broker are readable by anyone subscribed. Always use channel encryption for private communications.

Private Broker

For better privacy and control, you can run your own MQTT broker:

  • Mosquitto (lightweight, open-source)
  • HiveMQ
  • EMQX

Configure your node to point to your private broker with appropriate credentials.

Map Reporting

When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.

Turning it on opens a consent card. Turn on I agree. and choose a Map Publish Interval of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.

Reports appear at meshmap.net and similar community map services.

🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published.

Direction Aprašymas
Uplink Messages from mesh → MQTT broker
Downlink Messages from MQTT broker → mesh

Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on.

Message Formats

MQTT carries two payload formats:

Format Aprašymas Use case
Protobuf Binary Meshtastic protobuf encoding Node-to-node mesh bridging
JSON Human-readable JSON on the /2/json/ topic Consumers outside the mesh (dashboards, home automation)

ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads.

Encryption & Privacy

Understanding the layered encryption model:

  1. Channel encryption happens on the mesh before MQTT. If your channel has a PSK, the MQTT payload is already encrypted — the broker and any subscribers see only the ciphertext.
  2. Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard.
  3. TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping.

🔒 Security: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications.

Best Practices

  • Use channel-level encryption (PSK) on channels that bridge to MQTT
  • Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes memory)
  • Use a private broker for sensitive deployments
  • Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh
  • Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back

Troubleshooting

MQTT Not Connecting

  • Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself.
  • Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces.
  • Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443).
  • DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly.

Messages Not Bridging

  • Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway.
  • Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage.
  • Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root.
  • Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway.
  • Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in.
diff --git a/main/lt-rLT/user/settings-module-admin.html b/main/lt-rLT/user/settings-module-admin.html index 3b0ddf6bac..e09d771df1 100644 --- a/main/lt-rLT/user/settings-module-admin.html +++ b/main/lt-rLT/user/settings-module-admin.html @@ -1 +1 @@ - Settings — Modules & Admin | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Lietuvių
Meshtastic Docs ↗

🌐 Lietuvių — Community translation View in English

Settings — Modules & Admin

Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.

💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.

Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:

A toggle setting in the on position

A dropdown setting, expanded to show its list of options

A text field setting with a value entered

A module settings card with its title and grouped controls

Modulio konfigūracija

Every module lives under Settings → Module configuration.

⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes.

MQTT module

Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.

Setting Aprašymas
MQTT enabled Toggle MQTT bridge
Address MQTT broker address
Username Authentication username
Password Authentication password
Encryption enabled Encrypt MQTT payloads
JSON output enabled Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS enabled Use secure connection
Root topic Base MQTT topic path
Proxy to client enabled Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy on this phone The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT
Map reporting Publish position to the public map — see the Map reporting group that follows

Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:

Setting Aprašymas
I agree. Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map reporting interval (seconds) How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered

See MQTT for a detailed usage guide including encryption, privacy, and broker setup.

Serial module

Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.

Setting Aprašymas
Serial enabled Activate serial communication
Echo enabled Echo received serial data back
Serial mode Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX GPIO pins for the serial connection
Serial baud rate Port speed
Baigėsi laikas How long to wait before considering an incoming message complete
Override console serial port Take over the port the debug console normally uses

External Notification module

Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.

There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.

Setting Aprašymas
External notification enabled Master toggle for the module
Alert message LED / buzzer / vibra Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra Which outputs fire on a received bell character
Output LED (GPIO) Pin the LED is wired to
Output LED active high Whether the LED pin is active high or low
Output buzzer (GPIO) Pin the buzzer is wired to
Output vibra (GPIO) Pin the vibration motor is wired to
Use PWM buzzer Drive the buzzer with PWM, which allows tones rather than a single pitch
Use I2S as buzzer Send the alert through an I2S audio output instead
Output duration (milliseconds) How long a single alert lasts
Nag timeout (seconds) Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Ringtone The tone played on a PWM buzzer, in RTTTL. Can be imported from a file

Store & Forward module

Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.

Setting Aprašymas
Store & Forward enabled Activate store and forward
Heartbeat Periodically announce this node’s store-and-forward capability
Number of records Maximum stored messages
History return max Max messages to replay
History return window Time window for replay
Server Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)

💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.

Range Test module

⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.

Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.

Setting Aprašymas
Range test enabled Activate range testing
Sender message interval (seconds) Time between test transmissions, chosen from a dropdown of fixed intervals
Save .CSV in storage (ESP32 only) Log received test data to the node’s own filesystem. ESP32 hardware only

Telemetry module

Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).

Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.

Setting Aprašymas
Send Device Telemetry Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval How often to report battery, uptime and channel utilization
Environment metrics module enabled Report the attached environment sensors
Environment metrics update interval How often to report them
Environment metrics on-screen enabled Also show these readings on the device’s own display
Environment metrics use Fahrenheit Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Air quality metrics module enabled Report particulate and CO₂ sensor data
Air quality metrics update interval How often to report them
Power metrics module enabled Report the per-channel voltage and current readings
Power metrics update interval How often to report them
Power metrics on-screen enabled Also show power readings on the device’s display

See Telemetry & Sensors for supported sensors and configuration recommendations.

Canned Message module

Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.

Setting Aprašymas
Canned message enabled ⚠️ Deprecated in the protobuf schema
Messages Newline-separated list of messages
Send bell Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Rotary encoder #1 enabled Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port The three pins the encoder is wired to
Generate input event on Press / CW / CCW Which key event each encoder action produces
Up/Down/Select input enabled A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source ⚠️ Deprecated in the protobuf schema

Audio module

Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.

Setting Aprašymas
CODEC 2 enabled Activate audio module
CODEC2 sample rate Audio quality/bandwidth tradeoff
PTT pin GPIO pin for the push-to-talk button
I2S word select GPIO pin for I2S WS
I2S data in GPIO pin for I2S DIN
I2S data out GPIO pin for I2S DOUT
I2S clock GPIO pin for the I2S bit clock

ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.

Remote Hardware module

GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.

⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.

Setting Aprašymas
Remote Hardware enabled Activate remote GPIO access
Allow undefined pin access Allow access to any GPIO pin (security risk)
Available pins Up to 4 GPIO pins this node exposes for remote read/write

Neighbor Info module

Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.

Setting Aprašymas
Neighbor Info enabled Activate neighbor broadcasting
Update interval (seconds) How often to broadcast neighbor list
Transmit over LoRa Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name

See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.

Ambient Lighting module

Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.

Setting Aprašymas
LED state Turn the LED on or off
Current LED current limit (0–31)
Red / Green / Blue Individual color channel values (0–255)

Detection Sensor module

Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.

Setting Aprašymas
Detection Sensor enabled Activate detection sensor
GPIO pin to monitor GPIO pin connected to sensor
Detection trigger type How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Use INPUT_PULLUP mode Enable the pin’s internal pull-up resistor
Minimum broadcast (seconds) Minimum time between alert broadcasts
State broadcast (seconds) Periodic state broadcast interval
Send bell with alert message Include bell character in alerts
Friendly name Custom name for this sensor

Paxcounter module

People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.

Setting Aprašymas
Paxcounter enabled Activate people counting
Update interval (seconds) How often to report counts
Wi-Fi RSSI threshold Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE RSSI threshold The same cut-off for BLE advertisements (defaults to −80 dBm)

💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.

Status Message module

The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.

Mesh Beacon module

Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.

TAK module

Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.

Administravimas

Nuotolinis administravimas

Remotely configure nodes that share your admin key:

  1. Select the target node in the node list.
  2. Navigate to Settings for that node.
  3. Modify configuration.
  4. Tap Save — changes are sent over the mesh.

⚠️ Important: Requires an admin key configured on both your node and the target node.

Device Actions

Settings → Administration holds five one-shot actions, each behind a confirmation dialog:

Action What it does
Set time Sends your phone’s clock to the node
Perkrauti Restarts the node
Išjungti Powers the node down
Gamyklinis atstatymas Returns every setting to its factory default
NodeDB perkrauti Clears the node database. This dialog carries a Preserve Favorites? switch

⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.

Backup & Restore

Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.

Advanced

Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.

Clean Node Database

Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.

  • Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
  • Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.

The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.

Derinimo skydelis

Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.

App Settings

The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:

Privacy

  • Allow analytics and crash reporting — opt in or out of diagnostics.
  • Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
  • Homoglyph encoding — how look-alike characters in names are handled.

Appearance

  • Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
  • Theme and Language.
  • Show full message timestamps.

Persistence

  • A cache limit for how much history is kept.
  • Export rangetest packets, Export all packets and Export node database.

On their own

  • Node Layout — how much detail each row of the node list shows.
  • Wi-Fi Provisioning for mPWRD-OS — see Connections.
  • Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
  • System AI — appears only where app functions are available; see App Functions.

A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.

Apie

Settings → About carries the app’s own identity rather than the node’s:

Three sections:

  • What is Meshtastic? — a short description of the project.
  • Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
  • Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.

The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.

Acknowledgements

Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.

Troubleshooting remote admin

  • “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
  • Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
  • Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
+ Settings — Modules & Admin | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Lietuvių
Meshtastic Docs ↗

🌐 Lietuvių — Community translation View in English

Settings — Modules & Admin

Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.

💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.

Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:

A toggle setting in the on position

A dropdown setting, expanded to show its list of options

A text field setting with a value entered

A module settings card with its title and grouped controls

Modulio konfigūracija

Every module lives under Settings → Module configuration.

⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes.

MQTT module

Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.

Setting Aprašymas
MQTT enabled Toggle MQTT bridge
Address MQTT broker address
Username Authentication username
Password Authentication password
Encryption enabled Encrypt MQTT payloads
JSON output enabled Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS enabled Use secure connection
Root topic Base MQTT topic path
Proxy to client enabled Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy on this phone The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT
Map reporting Publish position to the public map — see the Map reporting group that follows

Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:

Setting Aprašymas
I agree. Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered

See MQTT for a detailed usage guide including encryption, privacy, and broker setup.

Serial module

Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.

Setting Aprašymas
Serial enabled Activate serial communication
Echo enabled Echo received serial data back
Serial mode Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX GPIO pins for the serial connection
Serial baud rate Port speed
Baigėsi laikas How long to wait before considering an incoming message complete
Override console serial port Take over the port the debug console normally uses

External Notification module

Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.

There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.

Setting Aprašymas
External notification enabled Master toggle for the module
Alert message LED / buzzer / vibra Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra Which outputs fire on a received bell character
Output LED (GPIO) Pin the LED is wired to
Output LED active high Whether the LED pin is active high or low
Output buzzer (GPIO) Pin the buzzer is wired to
Output vibra (GPIO) Pin the vibration motor is wired to
Use PWM buzzer Drive the buzzer with PWM, which allows tones rather than a single pitch
Use I2S as buzzer Send the alert through an I2S audio output instead
GPIO Output Duration How long a single alert lasts
Nag Timeout Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Ringtone The tone played on a PWM buzzer, in RTTTL. Can be imported from a file

Store & Forward module

Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.

Setting Aprašymas
Store & Forward enabled Activate store and forward
Heartbeat Periodically announce this node’s store-and-forward capability
Number of records Maximum stored messages
History return max Max messages to replay
History return window Time window for replay
Server Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)

💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.

Range Test module

⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.

Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.

Setting Aprašymas
Range test enabled Activate range testing
Sender Interval Time between test transmissions, chosen from a dropdown of fixed intervals
Save .CSV in storage (ESP32 only) Log received test data to the node’s own filesystem. ESP32 hardware only

Telemetry module

Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).

Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.

Setting Aprašymas
Send Device Telemetry Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval How often to report battery, uptime and channel utilization
Environment metrics module enabled Report the attached environment sensors
Environment metrics update interval How often to report them
Environment metrics on-screen enabled Also show these readings on the device’s own display
Environment metrics use Fahrenheit Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Air quality metrics module enabled Report particulate and CO₂ sensor data
Air quality metrics update interval How often to report them
Power metrics module enabled Report the per-channel voltage and current readings
Power metrics update interval How often to report them
Power metrics on-screen enabled Also show power readings on the device’s display

See Telemetry & Sensors for supported sensors and configuration recommendations.

Canned Message module

Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.

Setting Aprašymas
Canned message enabled ⚠️ Deprecated in the protobuf schema
Messages Newline-separated list of messages
Send bell Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Rotary encoder #1 enabled Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port The three pins the encoder is wired to
Generate input event on Press / CW / CCW Which key event each encoder action produces
Up/Down/Select input enabled A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source ⚠️ Deprecated in the protobuf schema

Audio module

Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.

Setting Aprašymas
CODEC 2 enabled Activate audio module
CODEC2 sample rate Audio quality/bandwidth tradeoff
PTT pin GPIO pin for the push-to-talk button
I2S word select GPIO pin for I2S WS
I2S data in GPIO pin for I2S DIN
I2S data out GPIO pin for I2S DOUT
I2S clock GPIO pin for the I2S bit clock

ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.

Remote Hardware module

GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.

⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.

Setting Aprašymas
Remote Hardware enabled Activate remote GPIO access
Allow undefined pin access Allow access to any GPIO pin (security risk)
Available pins Up to 4 GPIO pins this node exposes for remote read/write

Neighbor Info module

Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.

Setting Aprašymas
Neighbor Info enabled Activate neighbor broadcasting
Update Interval How often to broadcast neighbor list
Transmit over LoRa Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name

See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.

Ambient Lighting module

Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.

Setting Aprašymas
LED state Turn the LED on or off
Current LED current limit (0–31)
Red / Green / Blue Individual color channel values (0–255)

Detection Sensor module

Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.

Setting Aprašymas
Detection Sensor enabled Activate detection sensor
GPIO pin to monitor GPIO pin connected to sensor
Detection trigger type How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Use INPUT_PULLUP mode Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts Minimum time between alert broadcasts
State Broadcast Interval Periodic state broadcast interval
Send bell with alert message Include bell character in alerts
Friendly name Custom name for this sensor

Paxcounter module

People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.

Setting Aprašymas
Paxcounter enabled Activate people counting
Update Interval How often to report counts
WiFi Threshold (dBm) Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm) The same cut-off for BLE advertisements (defaults to −80 dBm)

💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.

Status Message module

The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.

Mesh Beacon module

Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.

TAK module

Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.

Administravimas

Nuotolinis administravimas

Remotely configure nodes that share your admin key:

  1. Select the target node in the node list.
  2. Navigate to Settings for that node.
  3. Modify configuration.
  4. Tap Save — changes are sent over the mesh.

⚠️ Important: Requires an admin key configured on both your node and the target node.

Device Actions

Settings → Administration holds five one-shot actions, each behind a confirmation dialog:

Action What it does
Set time Sends your phone’s clock to the node
Perkrauti Restarts the node
Išjungti Powers the node down
Gamyklinis atstatymas Returns every setting to its factory default
NodeDB perkrauti Clears the node database. This dialog carries a Preserve Favorites? switch

⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.

Backup & Restore

Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.

Advanced

Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.

Clean Node Database

Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.

  • Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
  • Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.

The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.

Derinimo skydelis

Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.

App Settings

The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:

Privacy

  • Allow analytics and crash reporting — opt in or out of diagnostics.
  • Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
  • Homoglyph encoding — how look-alike characters in names are handled.

Appearance

  • Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
  • Theme and Language.
  • Show full message timestamps.

Persistence

  • A cache limit for how much history is kept.
  • Export rangetest packets, Export all packets and Export node database.

On their own

  • Node Layout — how much detail each row of the node list shows.
  • Wi-Fi Provisioning for mPWRD-OS — see Connections.
  • Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
  • System AI — appears only where app functions are available; see App Functions.

A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.

Apie

Settings → About carries the app’s own identity rather than the node’s:

Three sections:

  • What is Meshtastic? — a short description of the project.
  • Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
  • Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.

The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.

Acknowledgements

Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.

Troubleshooting remote admin

  • “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
  • Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
  • Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
diff --git a/main/lt-rLT/user/settings-radio-user.html b/main/lt-rLT/user/settings-radio-user.html index 8d91374213..8fb17b5d4d 100644 --- a/main/lt-rLT/user/settings-radio-user.html +++ b/main/lt-rLT/user/settings-radio-user.html @@ -1 +1 @@ - Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Lietuvių
Meshtastic Docs ↗

🌐 Lietuvių — Community translation View in English

Settings — Radio & User

Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How these screens work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Aprašymas
Long Name Your display name (up to 39 characters)
Short Name 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Unmessageable Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur node (Ham) Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in.

Configuration

Device Config

On Settings → Device configuration → Device.

Setting Aprašymas Default
Device Role Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Rebroadcast Mode How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Node Info Broadcast Interval How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Double Tap as Button Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Enabled
LED Heartbeat Blink the status LED periodically Enabled
Time Zone POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it —
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to —

LoRa Config

On Settings → LoRa.

Setting Aprašymas Default
Regionas Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number Unset (must configure)
Presets Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Transmit Power Transmission power (dBm); 0 = max allowed for region 0 (region max)
Frequency Override Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Use Preset On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead From preset
Coding Rate Manual mode only: 5–8. More redundancy costs airtime From preset
Bandwidth Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Frequency Slot Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmit Enabled Turning this off makes the node receive-only On
Override Duty Cycle Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
Ignore MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok to MQTT Allow your packets to be forwarded to MQTT by gateways Off
RX Boosted Gain Extra receive gain on SX126x radios; costs a little current Off
PA fan disabled Turn off the power-amplifier fan on hardware that has one Off

The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set.

Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Speed SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a modem preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Display Config

On Settings → Device configuration → Display. These control the node’s own screen, not the app’s.

Setting Aprašymas
Screen on for How long the display stays lit before sleeping
Carousel interval How often the node cycles between screens on its own
Display mode Screen layout/density used by the firmware
Display units Metric or Imperial on the node’s screen
Use 12h clock format Show the node’s clock as 12-hour rather than 24-hour
Bold Heading Draw the screen’s heading text in bold
Flip screen Rotate the display 180° for an inverted mounting
OLED type Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED
Wake on tap or motion Light the screen when the node is tapped or moved
Compass orientation Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each
Always point north Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Position Config

On Settings → Device configuration → Position.

Setting Aprašymas
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the node asks its GPS for a fix
Broadcast Interval How often the position is shared with the mesh
Smart Position Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Fixed Position Use a manually entered latitude, longitude and altitude instead of the GPS
Position Flags A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Power Config

On Settings → Device configuration → Power.

Setting Aprašymas
Enable power saving mode Let the node sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the node stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC multiplier override ratio The correction factor itself, used only when the override is on
Battery INA_2XX I2C address Address of an external INA-series power sensor, if fitted

Network Config

On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node.

Setting Aprašymas
Wi-Fi enabled Enable the Wi-Fi node (ESP32 nodes)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Password Network password
Ethernet enabled Use a wired connection on hardware that has one
IPv4 mode DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP server Time synchronization server
rsyslog server Remote logging server

Network Config with a static IPv4 address entered

Bluetooth Config

On Settings → Device configuration → Bluetooth, on nodes with Bluetooth.

Setting Aprašymas
Bluetooth enabled Enable/disable BLE radio
Pairing mode Fixed PIN, Random PIN, or No PIN
Fixed PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Security Config

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

Setting Aprašymas
Viešasis raktas Your node’s public key (read-only)
Admin Key Keys permitted to administer this node remotely — up to three
Privatus raktas Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it
Regenerate Private Key Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Serial console Serial console over the Stream API
Debug log API enabled Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth
Managed Mode Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.

+ Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Lietuvių
Meshtastic Docs ↗

🌐 Lietuvių — Community translation View in English

Settings — Radio & User

Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How these screens work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Aprašymas
Long Name Your display name (up to 39 characters)
Short Name 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Unmessageable Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur node (Ham) Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in.

Configuration

Device Config

On Settings → Device configuration → Device.

Setting Aprašymas Default
Device Role Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Rebroadcast Mode How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Node Info Broadcast Interval How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Double Tap as Button Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Enabled
LED Heartbeat Blink the status LED periodically Enabled
Time Zone POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it —
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to —

LoRa Config

On Settings → LoRa.

Setting Aprašymas Default
Regionas Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number Unset (must configure)
Presets Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Transmit Power (dBm) Transmission power; 0 = max allowed for region 0 (region max)
Frequency Override Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Use Preset On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead From preset
Coding Rate Manual mode only: 5–8. More redundancy costs airtime From preset
Bandwidth Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Frequency Slot Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmit Enabled Turning this off makes the node receive-only On
Override Duty Cycle Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
Ignore MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok to MQTT Allow your packets to be forwarded to MQTT by gateways Off
RX Boosted Gain Extra receive gain on SX126x radios; costs a little current Off
PA fan disabled Turn off the power-amplifier fan on hardware that has one Off

The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set.

Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Speed SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a modem preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Display Config

On Settings → Device configuration → Display. These control the node’s own screen, not the app’s.

Setting Aprašymas
Screen on for How long the display stays lit before sleeping
Carousel interval How often the node cycles between screens on its own
Display mode Screen layout/density used by the firmware
Display units Metric or Imperial on the node’s screen
Use 12h clock format Show the node’s clock as 12-hour rather than 24-hour
Bold Heading Draw the screen’s heading text in bold
Flip screen Rotate the display 180° for an inverted mounting
OLED type Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED
Wake on tap or motion Light the screen when the node is tapped or moved
Compass orientation Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each
Always point north Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Position Config

On Settings → Device configuration → Position.

Setting Aprašymas
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the node asks its GPS for a fix
Broadcast Interval How often the position is shared with the mesh
Smart Position Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Fixed Position Use a manually entered latitude, longitude and altitude instead of the GPS
Position Flags A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Power Config

On Settings → Device configuration → Power.

Setting Aprašymas
Enable power saving mode Let the node sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the node stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC multiplier override ratio The correction factor itself, used only when the override is on
Battery INA_2XX I2C address Address of an external INA-series power sensor, if fitted

Network Config

On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node.

Setting Aprašymas
Wi-Fi enabled Enable the Wi-Fi node (ESP32 nodes)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Password Network password
Ethernet enabled Use a wired connection on hardware that has one
IPv4 mode DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP server Time synchronization server
rsyslog server Remote logging server

Network Config with a static IPv4 address entered

Bluetooth Config

On Settings → Device configuration → Bluetooth, on nodes with Bluetooth.

Setting Aprašymas
Bluetooth enabled Enable/disable BLE radio
Pairing mode Fixed PIN, Random PIN, or No PIN
Fixed PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Security Config

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

Setting Aprašymas
Viešasis raktas Your node’s public key (read-only)
Admin Key Keys permitted to administer this node remotely — up to three
Privatus raktas Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it
Regenerate Private Key Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Serial console Serial console over the Stream API
Debug log API enabled Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth
Managed Mode Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.

diff --git a/main/nl-rNL/user/discovery.html b/main/nl-rNL/user/discovery.html index 9ca82ca069..725655c414 100644 --- a/main/nl-rNL/user/discovery.html +++ b/main/nl-rNL/user/discovery.html @@ -5,4 +5,4 @@ ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) -

Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:.

What to look for What it means
All hops show Good SNR (green) Healthy path — messages flow reliably
One hop shows a poor SNR (orange or red) Weak link — this relay segment is fragile
Many hops (4+) Long path — consider repositioning a node to shorten it
Different path on retry Mesh is adapting — multiple routes exist (this is good!)

💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network.

Troubleshooting with Traceroute

  • No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key.
  • Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa.
  • Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position.
  • Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric.

Neighbor Info

The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh.

Enabling Neighbor Info

  1. Navigate to Settings → Module configuration → Neighbor Info.
  2. Enable the module.
  3. Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
  4. Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air.

Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.

Viewing neighbor data

  • Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors.
  • Each neighbor entry shows the node that was directly heard and its signal quality.
  • Combine neighbor data from multiple nodes to understand the full mesh topology.

ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further.

Node list as a discovery tool

The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively.

Finding new nodes

  • Sort by Last heard to see the most recently active nodes at the top.
  • Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes.

Assessing connectivity

  • Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed.
  • Sort by Distance to find nearby nodes and verify they’re reachable.
  • Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge).

Infrastructure audit

  • Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes.
  • Check their signal quality and last-heard times to verify your infrastructure nodes are healthy.

See Nodes for full details on filtering and sorting options.

Tips for Mesh exploration

  • Start with traceroute — it gives you immediate, actionable information about a specific path.
  • Enable Neighbor Info on key nodes — especially routers and repeaters, to build a picture of the backbone.
  • Check the map — node positions on the Map combined with signal data help you understand why some links are strong and others are weak.
  • Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly.
+

Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:.

What to look for What it means
All hops show Good SNR (green) Healthy path — messages flow reliably
One hop shows a poor SNR (orange or red) Weak link — this relay segment is fragile
Many hops (4+) Long path — consider repositioning a node to shorten it
Different path on retry Mesh is adapting — multiple routes exist (this is good!)

💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network.

Troubleshooting with Traceroute

  • No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key.
  • Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa.
  • Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position.
  • Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric.

Neighbor Info

The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh.

Enabling Neighbor Info

  1. Navigate to Settings → Module configuration → Neighbor Info.
  2. Enable the module.
  3. Set Update Interval. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
  4. Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air.

Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.

Viewing neighbor data

  • Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors.
  • Each neighbor entry shows the node that was directly heard and its signal quality.
  • Combine neighbor data from multiple nodes to understand the full mesh topology.

ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further.

Node list as a discovery tool

The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively.

Finding new nodes

  • Sort by Last heard to see the most recently active nodes at the top.
  • Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes.

Assessing connectivity

  • Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed.
  • Sort by Distance to find nearby nodes and verify they’re reachable.
  • Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge).

Infrastructure audit

  • Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes.
  • Check their signal quality and last-heard times to verify your infrastructure nodes are healthy.

See Nodes for full details on filtering and sorting options.

Tips for Mesh exploration

  • Start with traceroute — it gives you immediate, actionable information about a specific path.
  • Enable Neighbor Info on key nodes — especially routers and repeaters, to build a picture of the backbone.
  • Check the map — node positions on the Map combined with signal data help you understand why some links are strong and others are weak.
  • Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly.
diff --git a/main/nl-rNL/user/mqtt.html b/main/nl-rNL/user/mqtt.html index b216dd13aa..6530b55b48 100644 --- a/main/nl-rNL/user/mqtt.html +++ b/main/nl-rNL/user/mqtt.html @@ -1,2 +1,2 @@ MQTT | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Nederlands
Meshtastic Docs ↗

🌐 Nederlands — Community translation View in English

MQTT

MQTT bridges your Meshtastic mesh network to the internet, enabling long-range communication beyond radio range.

Overview

The MQTT module connects your node to an MQTT broker, allowing:

  • Messages to reach nodes on different physical meshes via the internet
  • Integration with home automation and monitoring systems
  • Publishing node positions to the public Meshtastic map
  • Custom data pipelines for logging and alerting

How It Works 

[Your Node] → Radio → [Gateway Node with Wi-Fi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node]
-

A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh.

Configuration

Enabling MQTT

  1. Navigate to Settings → Module configuration → MQTT.
  2. Enable the MQTT module.
  3. Configure the broker connection:
Setting Beschrijving Standaard
Address MQTT broker hostname mqtt.meshtastic.org
Username Broker authentication meshdev
Password Broker authentication large4cats
Root topic Base topic for messages msh, which the radio rewrites to msh/<REGION> once you set a region
Encryption enabled Encrypt MQTT payload Enabled
JSON output enabled Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it Disabled
TLS enabled Secure connection to broker Disabled
Map reporting Report position to public map Disabled
Proxy to client enabled Relay MQTT through the connected phone Disabled

Connection Status and Test Connection

The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here.

Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason.

MQTT Proxy on This Phone

If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection.

ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them.

The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration.

Default Meshtastic Broker

The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing.

When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without).

🔒 Privacy: Messages on the public broker are readable by anyone subscribed. Always use channel encryption for private communications.

Private Broker

For better privacy and control, you can run your own MQTT broker:

  • Mosquitto (lightweight, open-source)
  • HiveMQ
  • EMQX

Configure your node to point to your private broker with appropriate credentials.

Map Reporting

When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.

Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.

Reports appear at meshmap.net and similar community map services.

🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published.

Direction Beschrijving
Uplink Messages from mesh → MQTT broker
Downlink Messages from MQTT broker → mesh

Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on.

Message Formats

MQTT carries two payload formats:

Format Beschrijving Use case
Protobuf Binary Meshtastic protobuf encoding Node-to-node mesh bridging
JSON Human-readable JSON on the /2/json/ topic Consumers outside the mesh (dashboards, home automation)

ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads.

Encryption & Privacy

Understanding the layered encryption model:

  1. Channel encryption happens on the mesh before MQTT. If your channel has a PSK, the MQTT payload is already encrypted — the broker and any subscribers see only the ciphertext.
  2. Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard.
  3. TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping.

🔒 Security: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications.

Best Practices

  • Use channel-level encryption (PSK) on channels that bridge to MQTT
  • Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes memory)
  • Use a private broker for sensitive deployments
  • Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh
  • Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back

Troubleshooting

MQTT Not Connecting

  • Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself.
  • Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces.
  • Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443).
  • DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly.

Messages Not Bridging

  • Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway.
  • Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage.
  • Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root.
  • Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway.
  • Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in.
+

A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh.

Configuration

Enabling MQTT

  1. Navigate to Settings → Module configuration → MQTT.
  2. Enable the MQTT module.
  3. Configure the broker connection:
Setting Beschrijving Standaard
Address MQTT broker hostname mqtt.meshtastic.org
Username Broker authentication meshdev
Password Broker authentication large4cats
Root topic Base topic for messages msh, which the radio rewrites to msh/<REGION> once you set a region
Encryption enabled Encrypt MQTT payload Enabled
JSON output enabled Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it Disabled
TLS enabled Secure connection to broker Disabled
Map reporting Report position to public map Disabled
Proxy to client enabled Relay MQTT through the connected phone Disabled

Connection Status and Test Connection

The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here.

Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason.

MQTT Proxy on This Phone

If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection.

ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them.

The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration.

Default Meshtastic Broker

The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing.

When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without).

🔒 Privacy: Messages on the public broker are readable by anyone subscribed. Always use channel encryption for private communications.

Private Broker

For better privacy and control, you can run your own MQTT broker:

  • Mosquitto (lightweight, open-source)
  • HiveMQ
  • EMQX

Configure your node to point to your private broker with appropriate credentials.

Map Reporting

When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.

Turning it on opens a consent card. Turn on I agree. and choose a Map Publish Interval of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.

Reports appear at meshmap.net and similar community map services.

🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published.

Direction Beschrijving
Uplink Messages from mesh → MQTT broker
Downlink Messages from MQTT broker → mesh

Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on.

Message Formats

MQTT carries two payload formats:

Format Beschrijving Use case
Protobuf Binary Meshtastic protobuf encoding Node-to-node mesh bridging
JSON Human-readable JSON on the /2/json/ topic Consumers outside the mesh (dashboards, home automation)

ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads.

Encryption & Privacy

Understanding the layered encryption model:

  1. Channel encryption happens on the mesh before MQTT. If your channel has a PSK, the MQTT payload is already encrypted — the broker and any subscribers see only the ciphertext.
  2. Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard.
  3. TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping.

🔒 Security: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications.

Best Practices

  • Use channel-level encryption (PSK) on channels that bridge to MQTT
  • Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes memory)
  • Use a private broker for sensitive deployments
  • Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh
  • Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back

Troubleshooting

MQTT Not Connecting

  • Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself.
  • Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces.
  • Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443).
  • DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly.

Messages Not Bridging

  • Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway.
  • Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage.
  • Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root.
  • Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway.
  • Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in.
diff --git a/main/nl-rNL/user/settings-module-admin.html b/main/nl-rNL/user/settings-module-admin.html index d9cd3ddf77..4885c903a4 100644 --- a/main/nl-rNL/user/settings-module-admin.html +++ b/main/nl-rNL/user/settings-module-admin.html @@ -1 +1 @@ - Settings — Modules & Admin | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Nederlands
Meshtastic Docs ↗

🌐 Nederlands — Community translation View in English

Settings — Modules & Admin

Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.

💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.

Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:

A toggle setting in the on position

A dropdown setting, expanded to show its list of options

A text field setting with a value entered

A module settings card with its title and grouped controls

Module-configuratie

Every module lives under Settings → Module configuration.

⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes.

MQTT module

Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.

Setting Beschrijving
MQTT ingeschakeld Toggle MQTT bridge
Adres MQTT broker address
Gebruikersnaam Authentication username
Wachtwoord Authentication password
Encryptie ingeschakeld Encrypt MQTT payloads
JSON uitvoer ingeschakeld Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS ingeschakeld Use secure connection
Root topic Base MQTT topic path
Proxy to client ingeschakeld Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy on this phone The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT
Kaartrapportage Publish position to the public map — see the Map reporting group that follows

Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:

Setting Beschrijving
I agree. Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map reporting interval (seconds) How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered

See MQTT for a detailed usage guide including encryption, privacy, and broker setup.

Serial module

Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.

Setting Beschrijving
Serieel ingeschakeld Activate serial communication
Echo ingeschakeld Echo received serial data back
Seriële modus Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX GPIO pins for the serial connection
Serial baud rate Port speed
Time-Out How long to wait before considering an incoming message complete
Override console serial port Take over the port the debug console normally uses

External Notification module

Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.

There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.

Setting Beschrijving
External notification enabled Master toggle for the module
Alert message LED / buzzer / vibra Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra Which outputs fire on a received bell character
Output LED (GPIO) Pin the LED is wired to
Output LED active high Whether the LED pin is active high or low
Output buzzer (GPIO) Pin the buzzer is wired to
Output vibra (GPIO) Pin the vibration motor is wired to
Gebruik PWM zoemer Drive the buzzer with PWM, which allows tones rather than a single pitch
Use I2S as buzzer Send the alert through an I2S audio output instead
Output duur (milliseconden) How long a single alert lasts
Nag timeout (seconds) Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Beltoon The tone played on a PWM buzzer, in RTTTL. Can be imported from a file

Store & Forward module

Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.

Setting Beschrijving
Store & Forward enabled Activate store and forward
Hartslag Periodically announce this node’s store-and-forward capability
Aantal records Maximum stored messages
History return max Max messages to replay
History return window Time window for replay
Server Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)

💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.

Range Test module

⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.

Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.

Setting Beschrijving
Range test enabled Activate range testing
Sender message interval (seconds) Time between test transmissions, chosen from a dropdown of fixed intervals
Save .CSV in storage (ESP32 only) Log received test data to the node’s own filesystem. ESP32 hardware only

Telemetry module

Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).

Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.

Setting Beschrijving
Send Device Telemetry Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval How often to report battery, uptime and channel utilization
Environment metrics module enabled Report the attached environment sensors
Environment metrics update interval How often to report them
Environment metrics on-screen enabled Also show these readings on the device’s own display
Environment metrics use Fahrenheit Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Air quality metrics module enabled Report particulate and CO₂ sensor data
Air quality metrics update interval How often to report them
Power metrics module enabled Report the per-channel voltage and current readings
Power metrics update interval How often to report them
Power metrics on-screen enabled Also show power readings on the device’s display

See Telemetry & Sensors for supported sensors and configuration recommendations.

Canned Message module

Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.

Setting Beschrijving
Canned message enabled ⚠️ Deprecated in the protobuf schema
Berichten Newline-separated list of messages
Verstuur bel Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Rotary encoder #1 enabled Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port The three pins the encoder is wired to
Generate input event on Press / CW / CCW Which key event each encoder action produces
Up/Down/Select input enabled A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source ⚠️ Deprecated in the protobuf schema

Audio module

Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.

Setting Beschrijving
CODEC 2 ingeschakeld Activate audio module
CODEC2 sample rate Audio quality/bandwidth tradeoff
PTT pin GPIO pin for the push-to-talk button
I2S word select GPIO pin for I2S WS
I2S data in GPIO pin for I2S DIN
I2S data out GPIO pin for I2S DOUT
I2S klok GPIO pin for the I2S bit clock

ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.

Remote Hardware module

GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.

⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.

Setting Beschrijving
Externe hardware ingeschakeld Activate remote GPIO access
Allow undefined pin access Allow access to any GPIO pin (security risk)
Beschikbare pinnen Up to 4 GPIO pins this node exposes for remote read/write

Neighbor Info module

Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.

Setting Beschrijving
Neighbor Info enabled Activate neighbor broadcasting
Update-interval (seconden) How often to broadcast neighbor list
Zend over LoRa Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name

See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.

Ambient Lighting module

Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.

Setting Beschrijving
LED status Turn the LED on or off
Huidige LED current limit (0–31)
Red / Green / Blue Individual color channel values (0–255)

Detection Sensor module

Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.

Setting Beschrijving
Bewegingssensor Ingeschakeld Activate detection sensor
GPIO pin om te monitoren GPIO pin connected to sensor
Detectie trigger type How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Use INPUT_PULLUP mode Enable the pin’s internal pull-up resistor
Minimale broadcast (seconden) Minimum time between alert broadcasts
State broadcast (seconds) Periodic state broadcast interval
Send bell with alert message Include bell character in alerts
Weergavenaam Custom name for this sensor

Paxcounter module

People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.

Setting Beschrijving
Paxcounter ingeschakeld Activate people counting
Update-interval (seconden) How often to report counts
Wi-Fi RSSI threshold Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE RSSI threshold The same cut-off for BLE advertisements (defaults to −80 dBm)

💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.

Status Message module

The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.

Mesh Beacon module

Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.

TAK module

Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.

Beheer

Extern beheer

Remotely configure nodes that share your admin key:

  1. Select the target node in the node list.
  2. Navigate to Settings for that node.
  3. Modify configuration.
  4. Tap Save — changes are sent over the mesh.

⚠️ Important: Requires an admin key configured on both your node and the target node.

Device Actions

Settings → Administration holds five one-shot actions, each behind a confirmation dialog:

Action What it does
Set time Sends your phone’s clock to the node
Herstart Restarts the node
Zet uit Powers the node down
Reset naar fabrieksinstellingen Returns every setting to its factory default
NodeDB reset Clears the node database. This dialog carries a Preserve Favorites? switch

⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.

Back-up & Herstellen

Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.

Advanced

Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.

Clean Node Database

Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.

  • Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
  • Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.

The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.

Debug-paneel

Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.

App Settings

The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:

Privacy

  • Allow analytics and crash reporting — opt in or out of diagnostics.
  • Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
  • Homoglyph encoding — how look-alike characters in names are handled.

Appearance

  • Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
  • Theme and Language.
  • Show full message timestamps.

Persistence

  • A cache limit for how much history is kept.
  • Export rangetest packets, Export all packets and Export node database.

On their own

  • Node Layout — how much detail each row of the node list shows.
  • Wi-Fi Provisioning for mPWRD-OS — see Connections.
  • Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
  • System AI — appears only where app functions are available; see App Functions.

A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.

Over

Settings → About carries the app’s own identity rather than the node’s:

Three sections:

  • What is Meshtastic? — a short description of the project.
  • Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
  • Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.

The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.

Acknowledgements

Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.

Troubleshooting remote admin

  • “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
  • Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
  • Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
+ Settings — Modules & Admin | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Nederlands
Meshtastic Docs ↗

🌐 Nederlands — Community translation View in English

Settings — Modules & Admin

Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.

💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.

Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:

A toggle setting in the on position

A dropdown setting, expanded to show its list of options

A text field setting with a value entered

A module settings card with its title and grouped controls

Module-configuratie

Every module lives under Settings → Module configuration.

⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes.

MQTT module

Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.

Setting Beschrijving
MQTT ingeschakeld Toggle MQTT bridge
Adres MQTT broker address
Gebruikersnaam Authentication username
Wachtwoord Authentication password
Encryptie ingeschakeld Encrypt MQTT payloads
JSON uitvoer ingeschakeld Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS ingeschakeld Use secure connection
Root topic Base MQTT topic path
Proxy to client ingeschakeld Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy on this phone The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT
Kaartrapportage Publish position to the public map — see the Map reporting group that follows

Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:

Setting Beschrijving
I agree. Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered

See MQTT for a detailed usage guide including encryption, privacy, and broker setup.

Serial module

Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.

Setting Beschrijving
Serieel ingeschakeld Activate serial communication
Echo ingeschakeld Echo received serial data back
Seriële modus Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX GPIO pins for the serial connection
Serial baud rate Port speed
Time-Out How long to wait before considering an incoming message complete
Override console serial port Take over the port the debug console normally uses

External Notification module

Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.

There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.

Setting Beschrijving
External notification enabled Master toggle for the module
Alert message LED / buzzer / vibra Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra Which outputs fire on a received bell character
Output LED (GPIO) Pin the LED is wired to
Output LED active high Whether the LED pin is active high or low
Output buzzer (GPIO) Pin the buzzer is wired to
Output vibra (GPIO) Pin the vibration motor is wired to
Gebruik PWM zoemer Drive the buzzer with PWM, which allows tones rather than a single pitch
Use I2S as buzzer Send the alert through an I2S audio output instead
GPIO Output Duration How long a single alert lasts
Nag Timeout Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Beltoon The tone played on a PWM buzzer, in RTTTL. Can be imported from a file

Store & Forward module

Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.

Setting Beschrijving
Store & Forward enabled Activate store and forward
Hartslag Periodically announce this node’s store-and-forward capability
Aantal records Maximum stored messages
History return max Max messages to replay
History return window Time window for replay
Server Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)

💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.

Range Test module

⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.

Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.

Setting Beschrijving
Range test enabled Activate range testing
Sender Interval Time between test transmissions, chosen from a dropdown of fixed intervals
Save .CSV in storage (ESP32 only) Log received test data to the node’s own filesystem. ESP32 hardware only

Telemetry module

Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).

Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.

Setting Beschrijving
Send Device Telemetry Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval How often to report battery, uptime and channel utilization
Environment metrics module enabled Report the attached environment sensors
Environment metrics update interval How often to report them
Environment metrics on-screen enabled Also show these readings on the device’s own display
Environment metrics use Fahrenheit Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Air quality metrics module enabled Report particulate and CO₂ sensor data
Air quality metrics update interval How often to report them
Power metrics module enabled Report the per-channel voltage and current readings
Power metrics update interval How often to report them
Power metrics on-screen enabled Also show power readings on the device’s display

See Telemetry & Sensors for supported sensors and configuration recommendations.

Canned Message module

Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.

Setting Beschrijving
Canned message enabled ⚠️ Deprecated in the protobuf schema
Berichten Newline-separated list of messages
Verstuur bel Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Rotary encoder #1 enabled Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port The three pins the encoder is wired to
Generate input event on Press / CW / CCW Which key event each encoder action produces
Up/Down/Select input enabled A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source ⚠️ Deprecated in the protobuf schema

Audio module

Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.

Setting Beschrijving
CODEC 2 ingeschakeld Activate audio module
CODEC2 sample rate Audio quality/bandwidth tradeoff
PTT pin GPIO pin for the push-to-talk button
I2S word select GPIO pin for I2S WS
I2S data in GPIO pin for I2S DIN
I2S data out GPIO pin for I2S DOUT
I2S klok GPIO pin for the I2S bit clock

ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.

Remote Hardware module

GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.

⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.

Setting Beschrijving
Externe hardware ingeschakeld Activate remote GPIO access
Allow undefined pin access Allow access to any GPIO pin (security risk)
Beschikbare pinnen Up to 4 GPIO pins this node exposes for remote read/write

Neighbor Info module

Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.

Setting Beschrijving
Neighbor Info enabled Activate neighbor broadcasting
Update Interval How often to broadcast neighbor list
Zend over LoRa Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name

See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.

Ambient Lighting module

Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.

Setting Beschrijving
LED status Turn the LED on or off
Huidige LED current limit (0–31)
Red / Green / Blue Individual color channel values (0–255)

Detection Sensor module

Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.

Setting Beschrijving
Bewegingssensor Ingeschakeld Activate detection sensor
GPIO pin om te monitoren GPIO pin connected to sensor
Detectie trigger type How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Use INPUT_PULLUP mode Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts Minimum time between alert broadcasts
State Broadcast Interval Periodic state broadcast interval
Send bell with alert message Include bell character in alerts
Weergavenaam Custom name for this sensor

Paxcounter module

People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.

Setting Beschrijving
Paxcounter ingeschakeld Activate people counting
Update Interval How often to report counts
WiFi Threshold (dBm) Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm) The same cut-off for BLE advertisements (defaults to −80 dBm)

💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.

Status Message module

The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.

Mesh Beacon module

Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.

TAK module

Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.

Beheer

Extern beheer

Remotely configure nodes that share your admin key:

  1. Select the target node in the node list.
  2. Navigate to Settings for that node.
  3. Modify configuration.
  4. Tap Save — changes are sent over the mesh.

⚠️ Important: Requires an admin key configured on both your node and the target node.

Device Actions

Settings → Administration holds five one-shot actions, each behind a confirmation dialog:

Action What it does
Set time Sends your phone’s clock to the node
Herstart Restarts the node
Zet uit Powers the node down
Reset naar fabrieksinstellingen Returns every setting to its factory default
NodeDB reset Clears the node database. This dialog carries a Preserve Favorites? switch

⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.

Back-up & Herstellen

Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.

Advanced

Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.

Clean Node Database

Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.

  • Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
  • Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.

The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.

Debug-paneel

Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.

App Settings

The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:

Privacy

  • Allow analytics and crash reporting — opt in or out of diagnostics.
  • Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
  • Homoglyph encoding — how look-alike characters in names are handled.

Appearance

  • Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
  • Theme and Language.
  • Show full message timestamps.

Persistence

  • A cache limit for how much history is kept.
  • Export rangetest packets, Export all packets and Export node database.

On their own

  • Node Layout — how much detail each row of the node list shows.
  • Wi-Fi Provisioning for mPWRD-OS — see Connections.
  • Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
  • System AI — appears only where app functions are available; see App Functions.

A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.

Over

Settings → About carries the app’s own identity rather than the node’s:

Three sections:

  • What is Meshtastic? — a short description of the project.
  • Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
  • Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.

The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.

Acknowledgements

Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.

Troubleshooting remote admin

  • “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
  • Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
  • Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
diff --git a/main/nl-rNL/user/settings-radio-user.html b/main/nl-rNL/user/settings-radio-user.html index 8631cd2019..a17ccabe7e 100644 --- a/main/nl-rNL/user/settings-radio-user.html +++ b/main/nl-rNL/user/settings-radio-user.html @@ -1 +1 @@ - Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Nederlands
Meshtastic Docs ↗

🌐 Nederlands — Community translation View in English

Settings — Radio & User

Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How these screens work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Beschrijving
Long Name Your display name (up to 39 characters)
Short Name 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Niet berichtbaar Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur node (Ham) Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in.

Configuration

Apparaat Configuratie

On Settings → Device configuration → Device.

Setting Beschrijving Standaard
Device Role Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Rebroadcast Mode How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Node Info Broadcast Interval How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Double Tap as Button Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Enabled
LED Heartbeat Blink the status LED periodically Enabled
Time Zone POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it —
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to —

LoRa Configuratie

On Settings → LoRa.

Setting Beschrijving Standaard
Regio Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number Unset (must configure)
Presets Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Transmit Power Transmission power (dBm); 0 = max allowed for region 0 (region max)
Frequency Override Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Use Preset On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead From preset
Coding Rate Manual mode only: 5–8. More redundancy costs airtime From preset
Bandbreedte Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Frequency Slot Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmit Enabled Turning this off makes the node receive-only On
Overschrijf Duty Cycle Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
Negeer MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok to MQTT Allow your packets to be forwarded to MQTT by gateways Off
RX Boosted Gain Extra receive gain on SX126x radios; costs a little current Off
PA fan disabled Turn off the power-amplifier fan on hardware that has one Off

The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set.

Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Speed SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a modem preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Weergave Configuratie

On Settings → Device configuration → Display. These control the node’s own screen, not the app’s.

Setting Beschrijving
Screen on for How long the display stays lit before sleeping
Carousel interval How often the node cycles between screens on its own
Weergavemodus Screen layout/density used by the firmware
Geef eenheden weer Metric or Imperial on the node’s screen
Use 12h clock format Show the node’s clock as 12-hour rather than 24-hour
Bold Heading Draw the screen’s heading text in bold
Scherm omdraaien Rotate the display 180° for an inverted mounting
OLED type Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED
Wake on tap or motion Light the screen when the node is tapped or moved
Kompas oriëntatie Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each
Always point north Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Positie Configuratie

On Settings → Device configuration → Position.

Setting Beschrijving
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the node asks its GPS for a fix
Broadcast Interval How often the position is shared with the mesh
Smart Position Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Fixed Position Use a manually entered latitude, longitude and altitude instead of the GPS
Position Flags A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Energie configuratie

On Settings → Device configuration → Power.

Setting Beschrijving
Energiebesparingsmodus inschakelen Let the node sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the node stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC multiplier override ratio The correction factor itself, used only when the override is on
Battery INA_2XX I2C address Address of an external INA-series power sensor, if fitted

Netwerkconfiguratie

On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node.

Setting Beschrijving
Wi-Fi enabled Enable the Wi-Fi node (ESP32 nodes)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Wachtwoord Network password
Ethernet ingeschakeld Use a wired connection on hardware that has one
IPv4 modus DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP server Time synchronization server
rsyslog server Remote logging server

Network Config with a static IPv4 address entered

Bluetooth Configuratie

On Settings → Device configuration → Bluetooth, on nodes with Bluetooth.

Setting Beschrijving
Bluetooth ingeschakeld Enable/disable BLE radio
Koppelmodus Fixed PIN, Random PIN, or No PIN
Vaste PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Beveiligings Configuratie

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

Setting Beschrijving
Publieke sleutel Your node’s public key (read-only)
Admin Sleutel Keys permitted to administer this node remotely — up to three
Privésleutel Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it
Regenerate Private Key Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Seriële console Serial console over the Stream API
Debug log API enabled Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth
Beheerde modus Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.

+ Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Nederlands
Meshtastic Docs ↗

🌐 Nederlands — Community translation View in English

Settings — Radio & User

Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How these screens work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Beschrijving
Long Name Your display name (up to 39 characters)
Short Name 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Niet berichtbaar Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur node (Ham) Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in.

Configuration

Apparaat Configuratie

On Settings → Device configuration → Device.

Setting Beschrijving Standaard
Device Role Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Rebroadcast Mode How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Node Info Broadcast Interval How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Double Tap as Button Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Enabled
LED Heartbeat Blink the status LED periodically Enabled
Time Zone POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it —
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to —

LoRa Configuratie

On Settings → LoRa.

Setting Beschrijving Standaard
Regio Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number Unset (must configure)
Presets Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Transmit Power (dBm) Transmission power; 0 = max allowed for region 0 (region max)
Frequency Override Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Use Preset On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead From preset
Coding Rate Manual mode only: 5–8. More redundancy costs airtime From preset
Bandbreedte Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Frequency Slot Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmit Enabled Turning this off makes the node receive-only On
Overschrijf Duty Cycle Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
Negeer MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok to MQTT Allow your packets to be forwarded to MQTT by gateways Off
RX Boosted Gain Extra receive gain on SX126x radios; costs a little current Off
PA fan disabled Turn off the power-amplifier fan on hardware that has one Off

The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set.

Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Speed SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a modem preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Weergave Configuratie

On Settings → Device configuration → Display. These control the node’s own screen, not the app’s.

Setting Beschrijving
Screen on for How long the display stays lit before sleeping
Carousel interval How often the node cycles between screens on its own
Weergavemodus Screen layout/density used by the firmware
Geef eenheden weer Metric or Imperial on the node’s screen
Use 12h clock format Show the node’s clock as 12-hour rather than 24-hour
Bold Heading Draw the screen’s heading text in bold
Scherm omdraaien Rotate the display 180° for an inverted mounting
OLED type Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED
Wake on tap or motion Light the screen when the node is tapped or moved
Kompas oriëntatie Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each
Always point north Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Positie Configuratie

On Settings → Device configuration → Position.

Setting Beschrijving
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the node asks its GPS for a fix
Broadcast Interval How often the position is shared with the mesh
Smart Position Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Fixed Position Use a manually entered latitude, longitude and altitude instead of the GPS
Position Flags A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Energie configuratie

On Settings → Device configuration → Power.

Setting Beschrijving
Energiebesparingsmodus inschakelen Let the node sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the node stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC multiplier override ratio The correction factor itself, used only when the override is on
Battery INA_2XX I2C address Address of an external INA-series power sensor, if fitted

Netwerkconfiguratie

On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node.

Setting Beschrijving
Wi-Fi enabled Enable the Wi-Fi node (ESP32 nodes)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Wachtwoord Network password
Ethernet ingeschakeld Use a wired connection on hardware that has one
IPv4 modus DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP server Time synchronization server
rsyslog server Remote logging server

Network Config with a static IPv4 address entered

Bluetooth Configuratie

On Settings → Device configuration → Bluetooth, on nodes with Bluetooth.

Setting Beschrijving
Bluetooth ingeschakeld Enable/disable BLE radio
Koppelmodus Fixed PIN, Random PIN, or No PIN
Vaste PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Beveiligings Configuratie

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

Setting Beschrijving
Publieke sleutel Your node’s public key (read-only)
Admin Sleutel Keys permitted to administer this node remotely — up to three
Privésleutel Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it
Regenerate Private Key Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Seriële console Serial console over the Stream API
Debug log API enabled Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth
Beheerde modus Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.

diff --git a/main/no-rNO/user/discovery.html b/main/no-rNO/user/discovery.html index 46e59d5c0b..d74d4cb792 100644 --- a/main/no-rNO/user/discovery.html +++ b/main/no-rNO/user/discovery.html @@ -5,4 +5,4 @@ ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) -

Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:.

What to look for What it means
All hops show Good SNR (green) Healthy path — messages flow reliably
One hop shows a poor SNR (orange or red) Weak link — this relay segment is fragile
Many hops (4+) Long path — consider repositioning a node to shorten it
Different path on retry Mesh is adapting — multiple routes exist (this is good!)

💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network.

Troubleshooting with Traceroute

  • No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key.
  • Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa.
  • Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position.
  • Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric.

Neighbor Info

The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh.

Enabling Neighbor Info

  1. Navigate to Settings → Module configuration → Neighbor Info.
  2. Enable the module.
  3. Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
  4. Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air.

Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.

Viewing neighbor data

  • Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors.
  • Each neighbor entry shows the node that was directly heard and its signal quality.
  • Combine neighbor data from multiple nodes to understand the full mesh topology.

ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further.

Node list as a discovery tool

The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively.

Finding new nodes

  • Sort by Last heard to see the most recently active nodes at the top.
  • Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes.

Assessing connectivity

  • Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed.
  • Sort by Distance to find nearby nodes and verify they’re reachable.
  • Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge).

Infrastructure audit

  • Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes.
  • Check their signal quality and last-heard times to verify your infrastructure nodes are healthy.

See Nodes for full details on filtering and sorting options.

Tips for Mesh exploration

  • Start with traceroute — it gives you immediate, actionable information about a specific path.
  • Enable Neighbor Info on key nodes — especially routers and repeaters, to build a picture of the backbone.
  • Check the map — node positions on the Map combined with signal data help you understand why some links are strong and others are weak.
  • Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly.
+

Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:.

What to look for What it means
All hops show Good SNR (green) Healthy path — messages flow reliably
One hop shows a poor SNR (orange or red) Weak link — this relay segment is fragile
Many hops (4+) Long path — consider repositioning a node to shorten it
Different path on retry Mesh is adapting — multiple routes exist (this is good!)

💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network.

Troubleshooting with Traceroute

  • No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key.
  • Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa.
  • Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position.
  • Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric.

Neighbor Info

The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh.

Enabling Neighbor Info

  1. Navigate to Settings → Module configuration → Neighbor Info.
  2. Enable the module.
  3. Set Update Interval. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
  4. Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air.

Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.

Viewing neighbor data

  • Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors.
  • Each neighbor entry shows the node that was directly heard and its signal quality.
  • Combine neighbor data from multiple nodes to understand the full mesh topology.

ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further.

Node list as a discovery tool

The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively.

Finding new nodes

  • Sort by Last heard to see the most recently active nodes at the top.
  • Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes.

Assessing connectivity

  • Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed.
  • Sort by Distance to find nearby nodes and verify they’re reachable.
  • Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge).

Infrastructure audit

  • Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes.
  • Check their signal quality and last-heard times to verify your infrastructure nodes are healthy.

See Nodes for full details on filtering and sorting options.

Tips for Mesh exploration

  • Start with traceroute — it gives you immediate, actionable information about a specific path.
  • Enable Neighbor Info on key nodes — especially routers and repeaters, to build a picture of the backbone.
  • Check the map — node positions on the Map combined with signal data help you understand why some links are strong and others are weak.
  • Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly.
diff --git a/main/no-rNO/user/mqtt.html b/main/no-rNO/user/mqtt.html index a628c2f93a..b0be69e651 100644 --- a/main/no-rNO/user/mqtt.html +++ b/main/no-rNO/user/mqtt.html @@ -1,2 +1,2 @@ MQTT | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Norsk
Meshtastic Docs ↗

🌐 Norsk — Community translation View in English

MQTT

MQTT bridges your Meshtastic mesh network to the internet, enabling long-range communication beyond radio range.

Overview

The MQTT module connects your node to an MQTT broker, allowing:

  • Messages to reach nodes on different physical meshes via the internet
  • Integration with home automation and monitoring systems
  • Publishing node positions to the public Meshtastic map
  • Custom data pipelines for logging and alerting

How It Works 

[Your Node] → Radio → [Gateway Node with Wi-Fi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node]
-

A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh.

Configuration

Enabling MQTT

  1. Navigate to Settings → Module configuration → MQTT.
  2. Enable the MQTT module.
  3. Configure the broker connection:
Setting Beskrivelse Default
Address MQTT broker hostname mqtt.meshtastic.org
Username Broker authentication meshdev
Password Broker authentication large4cats
Root topic Base topic for messages msh, which the radio rewrites to msh/<REGION> once you set a region
Encryption enabled Encrypt MQTT payload Enabled
JSON output enabled Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it Disabled
TLS enabled Secure connection to broker Disabled
Map reporting Report position to public map Disabled
Proxy to client enabled Relay MQTT through the connected phone Disabled

Connection Status and Test Connection

The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here.

Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason.

MQTT Proxy on This Phone

If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection.

ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them.

The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration.

Default Meshtastic Broker

The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing.

When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without).

🔒 Privacy: Messages on the public broker are readable by anyone subscribed. Always use channel encryption for private communications.

Private Broker

For better privacy and control, you can run your own MQTT broker:

  • Mosquitto (lightweight, open-source)
  • HiveMQ
  • EMQX

Configure your node to point to your private broker with appropriate credentials.

Map Reporting

When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.

Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.

Reports appear at meshmap.net and similar community map services.

🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published.

Direction Beskrivelse
Uplink Messages from mesh → MQTT broker
Downlink Messages from MQTT broker → mesh

Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on.

Message Formats

MQTT carries two payload formats:

Format Beskrivelse Use case
Protobuf Binary Meshtastic protobuf encoding Node-to-node mesh bridging
JSON Human-readable JSON on the /2/json/ topic Consumers outside the mesh (dashboards, home automation)

ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads.

Encryption & Privacy

Understanding the layered encryption model:

  1. Channel encryption happens on the mesh before MQTT. If your channel has a PSK, the MQTT payload is already encrypted — the broker and any subscribers see only the ciphertext.
  2. Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard.
  3. TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping.

🔒 Security: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications.

Best Practices

  • Use channel-level encryption (PSK) on channels that bridge to MQTT
  • Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes memory)
  • Use a private broker for sensitive deployments
  • Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh
  • Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back

Troubleshooting

MQTT Not Connecting

  • Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself.
  • Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces.
  • Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443).
  • DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly.

Messages Not Bridging

  • Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway.
  • Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage.
  • Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root.
  • Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway.
  • Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in.
+

A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh.

Configuration

Enabling MQTT

  1. Navigate to Settings → Module configuration → MQTT.
  2. Enable the MQTT module.
  3. Configure the broker connection:
Setting Beskrivelse Default
Address MQTT broker hostname mqtt.meshtastic.org
Username Broker authentication meshdev
Password Broker authentication large4cats
Root topic Base topic for messages msh, which the radio rewrites to msh/<REGION> once you set a region
Encryption enabled Encrypt MQTT payload Enabled
JSON output enabled Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it Disabled
TLS enabled Secure connection to broker Disabled
Map reporting Report position to public map Disabled
Proxy to client enabled Relay MQTT through the connected phone Disabled

Connection Status and Test Connection

The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here.

Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason.

MQTT Proxy on This Phone

If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection.

ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them.

The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration.

Default Meshtastic Broker

The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing.

When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without).

🔒 Privacy: Messages on the public broker are readable by anyone subscribed. Always use channel encryption for private communications.

Private Broker

For better privacy and control, you can run your own MQTT broker:

  • Mosquitto (lightweight, open-source)
  • HiveMQ
  • EMQX

Configure your node to point to your private broker with appropriate credentials.

Map Reporting

When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.

Turning it on opens a consent card. Turn on I agree. and choose a Map Publish Interval of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.

Reports appear at meshmap.net and similar community map services.

🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published.

Direction Beskrivelse
Uplink Messages from mesh → MQTT broker
Downlink Messages from MQTT broker → mesh

Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on.

Message Formats

MQTT carries two payload formats:

Format Beskrivelse Use case
Protobuf Binary Meshtastic protobuf encoding Node-to-node mesh bridging
JSON Human-readable JSON on the /2/json/ topic Consumers outside the mesh (dashboards, home automation)

ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads.

Encryption & Privacy

Understanding the layered encryption model:

  1. Channel encryption happens on the mesh before MQTT. If your channel has a PSK, the MQTT payload is already encrypted — the broker and any subscribers see only the ciphertext.
  2. Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard.
  3. TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping.

🔒 Security: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications.

Best Practices

  • Use channel-level encryption (PSK) on channels that bridge to MQTT
  • Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes memory)
  • Use a private broker for sensitive deployments
  • Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh
  • Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back

Troubleshooting

MQTT Not Connecting

  • Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself.
  • Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces.
  • Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443).
  • DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly.

Messages Not Bridging

  • Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway.
  • Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage.
  • Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root.
  • Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway.
  • Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in.
diff --git a/main/no-rNO/user/settings-module-admin.html b/main/no-rNO/user/settings-module-admin.html index 9d7f05492a..966fa01958 100644 --- a/main/no-rNO/user/settings-module-admin.html +++ b/main/no-rNO/user/settings-module-admin.html @@ -1 +1 @@ - Settings — Modules & Admin | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Norsk
Meshtastic Docs ↗

🌐 Norsk — Community translation View in English

Settings — Modules & Admin

Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.

💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.

Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:

A toggle setting in the on position

A dropdown setting, expanded to show its list of options

A text field setting with a value entered

A module settings card with its title and grouped controls

Modul konfigurasjon

Every module lives under Settings → Module configuration.

⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes.

MQTT module

Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.

Setting Beskrivelse
MQTT enabled Toggle MQTT bridge
Address MQTT broker address
Username Authentication username
Password Authentication password
Encryption enabled Encrypt MQTT payloads
JSON output enabled Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS enabled Use secure connection
Root topic Base MQTT topic path
Proxy to client enabled Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy on this phone The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT
Map reporting Publish position to the public map — see the Map reporting group that follows

Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:

Setting Beskrivelse
I agree. Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map reporting interval (seconds) How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered

See MQTT for a detailed usage guide including encryption, privacy, and broker setup.

Serial module

Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.

Setting Beskrivelse
Serial enabled Activate serial communication
Echo enabled Echo received serial data back
Serial mode Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX GPIO pins for the serial connection
Serial baud rate Port speed
Tidsavbrudd How long to wait before considering an incoming message complete
Override console serial port Take over the port the debug console normally uses

External Notification module

Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.

There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.

Setting Beskrivelse
External notification enabled Master toggle for the module
Alert message LED / buzzer / vibra Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra Which outputs fire on a received bell character
Output LED (GPIO) Pin the LED is wired to
Output LED active high Whether the LED pin is active high or low
Output buzzer (GPIO) Pin the buzzer is wired to
Output vibra (GPIO) Pin the vibration motor is wired to
Use PWM buzzer Drive the buzzer with PWM, which allows tones rather than a single pitch
Use I2S as buzzer Send the alert through an I2S audio output instead
Output duration (milliseconds) How long a single alert lasts
Nag timeout (seconds) Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Ringtone The tone played on a PWM buzzer, in RTTTL. Can be imported from a file

Store & Forward module

Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.

Setting Beskrivelse
Store & Forward enabled Activate store and forward
Heartbeat Periodically announce this node’s store-and-forward capability
Number of records Maximum stored messages
History return max Max messages to replay
History return window Time window for replay
Server Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)

💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.

Range Test module

⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.

Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.

Setting Beskrivelse
Range test enabled Activate range testing
Sender message interval (seconds) Time between test transmissions, chosen from a dropdown of fixed intervals
Save .CSV in storage (ESP32 only) Log received test data to the node’s own filesystem. ESP32 hardware only

Telemetry module

Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).

Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.

Setting Beskrivelse
Send Device Telemetry Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval How often to report battery, uptime and channel utilization
Environment metrics module enabled Report the attached environment sensors
Environment metrics update interval How often to report them
Environment metrics on-screen enabled Also show these readings on the device’s own display
Environment metrics use Fahrenheit Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Air quality metrics module enabled Report particulate and CO₂ sensor data
Air quality metrics update interval How often to report them
Power metrics module enabled Report the per-channel voltage and current readings
Power metrics update interval How often to report them
Power metrics on-screen enabled Also show power readings on the device’s display

See Telemetry & Sensors for supported sensors and configuration recommendations.

Canned Message module

Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.

Setting Beskrivelse
Canned message enabled ⚠️ Deprecated in the protobuf schema
Messages Newline-separated list of messages
Send bell Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Rotary encoder #1 enabled Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port The three pins the encoder is wired to
Generate input event on Press / CW / CCW Which key event each encoder action produces
Up/Down/Select input enabled A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source ⚠️ Deprecated in the protobuf schema

Audio module

Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.

Setting Beskrivelse
CODEC 2 enabled Activate audio module
CODEC2 sample rate Audio quality/bandwidth tradeoff
PTT pin GPIO pin for the push-to-talk button
I2S word select GPIO pin for I2S WS
I2S data in GPIO pin for I2S DIN
I2S data out GPIO pin for I2S DOUT
I2S clock GPIO pin for the I2S bit clock

ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.

Remote Hardware module

GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.

⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.

Setting Beskrivelse
Remote Hardware enabled Activate remote GPIO access
Allow undefined pin access Allow access to any GPIO pin (security risk)
Available pins Up to 4 GPIO pins this node exposes for remote read/write

Neighbor Info module

Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.

Setting Beskrivelse
Neighbor Info enabled Activate neighbor broadcasting
Update interval (seconds) How often to broadcast neighbor list
Transmit over LoRa Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name

See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.

Ambient Lighting module

Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.

Setting Beskrivelse
LED state Turn the LED on or off
Current LED current limit (0–31)
Red / Green / Blue Individual color channel values (0–255)

Detection Sensor module

Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.

Setting Beskrivelse
Detection Sensor enabled Activate detection sensor
GPIO pin to monitor GPIO pin connected to sensor
Detection trigger type How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Use INPUT_PULLUP mode Enable the pin’s internal pull-up resistor
Minimum broadcast (seconds) Minimum time between alert broadcasts
State broadcast (seconds) Periodic state broadcast interval
Send bell with alert message Include bell character in alerts
Friendly name Custom name for this sensor

Paxcounter module

People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.

Setting Beskrivelse
Paxcounter enabled Activate people counting
Update interval (seconds) How often to report counts
Wi-Fi RSSI threshold Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE RSSI threshold The same cut-off for BLE advertisements (defaults to −80 dBm)

💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.

Status Message module

The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.

Mesh Beacon module

Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.

TAK module

Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.

Administrasjon

Fjernadministrasjon

Remotely configure nodes that share your admin key:

  1. Select the target node in the node list.
  2. Navigate to Settings for that node.
  3. Modify configuration.
  4. Tap Save — changes are sent over the mesh.

⚠️ Important: Requires an admin key configured on both your node and the target node.

Device Actions

Settings → Administration holds five one-shot actions, each behind a confirmation dialog:

Action What it does
Set time Sends your phone’s clock to the node
Omstart Restarts the node
Avslutt Powers the node down
Tilbakestill til fabrikkstandard Returns every setting to its factory default
NodeDB reset Clears the node database. This dialog carries a Preserve Favorites? switch

⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.

Backup & Restore

Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.

Advanced

Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.

Clean Node Database

Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.

  • Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
  • Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.

The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.

Feilsøkningspanel

Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.

App Settings

The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:

Privacy

  • Allow analytics and crash reporting — opt in or out of diagnostics.
  • Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
  • Homoglyph encoding — how look-alike characters in names are handled.

Appearance

  • Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
  • Theme and Language.
  • Show full message timestamps.

Persistence

  • A cache limit for how much history is kept.
  • Export rangetest packets, Export all packets and Export node database.

On their own

  • Node Layout — how much detail each row of the node list shows.
  • Wi-Fi Provisioning for mPWRD-OS — see Connections.
  • Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
  • System AI — appears only where app functions are available; see App Functions.

A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.

Om

Settings → About carries the app’s own identity rather than the node’s:

Three sections:

  • What is Meshtastic? — a short description of the project.
  • Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
  • Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.

The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.

Acknowledgements

Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.

Troubleshooting remote admin

  • “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
  • Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
  • Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
+ Settings — Modules & Admin | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Norsk
Meshtastic Docs ↗

🌐 Norsk — Community translation View in English

Settings — Modules & Admin

Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.

💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.

Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:

A toggle setting in the on position

A dropdown setting, expanded to show its list of options

A text field setting with a value entered

A module settings card with its title and grouped controls

Modul konfigurasjon

Every module lives under Settings → Module configuration.

⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes.

MQTT module

Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.

Setting Beskrivelse
MQTT enabled Toggle MQTT bridge
Address MQTT broker address
Username Authentication username
Password Authentication password
Encryption enabled Encrypt MQTT payloads
JSON output enabled Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS enabled Use secure connection
Root topic Base MQTT topic path
Proxy to client enabled Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy on this phone The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT
Map reporting Publish position to the public map — see the Map reporting group that follows

Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:

Setting Beskrivelse
I agree. Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered

See MQTT for a detailed usage guide including encryption, privacy, and broker setup.

Serial module

Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.

Setting Beskrivelse
Serial enabled Activate serial communication
Echo enabled Echo received serial data back
Serial mode Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX GPIO pins for the serial connection
Serial baud rate Port speed
Tidsavbrudd How long to wait before considering an incoming message complete
Override console serial port Take over the port the debug console normally uses

External Notification module

Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.

There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.

Setting Beskrivelse
External notification enabled Master toggle for the module
Alert message LED / buzzer / vibra Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra Which outputs fire on a received bell character
Output LED (GPIO) Pin the LED is wired to
Output LED active high Whether the LED pin is active high or low
Output buzzer (GPIO) Pin the buzzer is wired to
Output vibra (GPIO) Pin the vibration motor is wired to
Use PWM buzzer Drive the buzzer with PWM, which allows tones rather than a single pitch
Use I2S as buzzer Send the alert through an I2S audio output instead
GPIO Output Duration How long a single alert lasts
Nag Timeout Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Ringtone The tone played on a PWM buzzer, in RTTTL. Can be imported from a file

Store & Forward module

Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.

Setting Beskrivelse
Store & Forward enabled Activate store and forward
Heartbeat Periodically announce this node’s store-and-forward capability
Number of records Maximum stored messages
History return max Max messages to replay
History return window Time window for replay
Server Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)

💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.

Range Test module

⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.

Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.

Setting Beskrivelse
Range test enabled Activate range testing
Sender Interval Time between test transmissions, chosen from a dropdown of fixed intervals
Save .CSV in storage (ESP32 only) Log received test data to the node’s own filesystem. ESP32 hardware only

Telemetry module

Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).

Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.

Setting Beskrivelse
Send Device Telemetry Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval How often to report battery, uptime and channel utilization
Environment metrics module enabled Report the attached environment sensors
Environment metrics update interval How often to report them
Environment metrics on-screen enabled Also show these readings on the device’s own display
Environment metrics use Fahrenheit Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Air quality metrics module enabled Report particulate and CO₂ sensor data
Air quality metrics update interval How often to report them
Power metrics module enabled Report the per-channel voltage and current readings
Power metrics update interval How often to report them
Power metrics on-screen enabled Also show power readings on the device’s display

See Telemetry & Sensors for supported sensors and configuration recommendations.

Canned Message module

Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.

Setting Beskrivelse
Canned message enabled ⚠️ Deprecated in the protobuf schema
Messages Newline-separated list of messages
Send bell Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Rotary encoder #1 enabled Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port The three pins the encoder is wired to
Generate input event on Press / CW / CCW Which key event each encoder action produces
Up/Down/Select input enabled A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source ⚠️ Deprecated in the protobuf schema

Audio module

Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.

Setting Beskrivelse
CODEC 2 enabled Activate audio module
CODEC2 sample rate Audio quality/bandwidth tradeoff
PTT pin GPIO pin for the push-to-talk button
I2S word select GPIO pin for I2S WS
I2S data in GPIO pin for I2S DIN
I2S data out GPIO pin for I2S DOUT
I2S clock GPIO pin for the I2S bit clock

ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.

Remote Hardware module

GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.

⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.

Setting Beskrivelse
Remote Hardware enabled Activate remote GPIO access
Allow undefined pin access Allow access to any GPIO pin (security risk)
Available pins Up to 4 GPIO pins this node exposes for remote read/write

Neighbor Info module

Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.

Setting Beskrivelse
Neighbor Info enabled Activate neighbor broadcasting
Update Interval How often to broadcast neighbor list
Transmit over LoRa Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name

See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.

Ambient Lighting module

Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.

Setting Beskrivelse
LED state Turn the LED on or off
Current LED current limit (0–31)
Red / Green / Blue Individual color channel values (0–255)

Detection Sensor module

Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.

Setting Beskrivelse
Detection Sensor enabled Activate detection sensor
GPIO pin to monitor GPIO pin connected to sensor
Detection trigger type How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Use INPUT_PULLUP mode Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts Minimum time between alert broadcasts
State Broadcast Interval Periodic state broadcast interval
Send bell with alert message Include bell character in alerts
Friendly name Custom name for this sensor

Paxcounter module

People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.

Setting Beskrivelse
Paxcounter enabled Activate people counting
Update Interval How often to report counts
WiFi Threshold (dBm) Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm) The same cut-off for BLE advertisements (defaults to −80 dBm)

💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.

Status Message module

The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.

Mesh Beacon module

Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.

TAK module

Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.

Administrasjon

Fjernadministrasjon

Remotely configure nodes that share your admin key:

  1. Select the target node in the node list.
  2. Navigate to Settings for that node.
  3. Modify configuration.
  4. Tap Save — changes are sent over the mesh.

⚠️ Important: Requires an admin key configured on both your node and the target node.

Device Actions

Settings → Administration holds five one-shot actions, each behind a confirmation dialog:

Action What it does
Set time Sends your phone’s clock to the node
Omstart Restarts the node
Avslutt Powers the node down
Tilbakestill til fabrikkstandard Returns every setting to its factory default
NodeDB reset Clears the node database. This dialog carries a Preserve Favorites? switch

⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.

Backup & Restore

Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.

Advanced

Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.

Clean Node Database

Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.

  • Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
  • Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.

The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.

Feilsøkningspanel

Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.

App Settings

The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:

Privacy

  • Allow analytics and crash reporting — opt in or out of diagnostics.
  • Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
  • Homoglyph encoding — how look-alike characters in names are handled.

Appearance

  • Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
  • Theme and Language.
  • Show full message timestamps.

Persistence

  • A cache limit for how much history is kept.
  • Export rangetest packets, Export all packets and Export node database.

On their own

  • Node Layout — how much detail each row of the node list shows.
  • Wi-Fi Provisioning for mPWRD-OS — see Connections.
  • Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
  • System AI — appears only where app functions are available; see App Functions.

A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.

Om

Settings → About carries the app’s own identity rather than the node’s:

Three sections:

  • What is Meshtastic? — a short description of the project.
  • Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
  • Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.

The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.

Acknowledgements

Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.

Troubleshooting remote admin

  • “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
  • Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
  • Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
diff --git a/main/no-rNO/user/settings-radio-user.html b/main/no-rNO/user/settings-radio-user.html index c31b420f7d..a824a091b8 100644 --- a/main/no-rNO/user/settings-radio-user.html +++ b/main/no-rNO/user/settings-radio-user.html @@ -1 +1 @@ - Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Norsk
Meshtastic Docs ↗

🌐 Norsk — Community translation View in English

Settings — Radio & User

Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How these screens work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Beskrivelse
Long Name Your display name (up to 39 characters)
Short Name 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Unmessageable Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur node (Ham) Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in.

Configuration

Device Config

On Settings → Device configuration → Device.

Setting Beskrivelse Default
Device Role Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Rebroadcast Mode How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Node Info Broadcast Interval How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Double Tap as Button Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Enabled
LED Heartbeat Blink the status LED periodically Enabled
Time Zone POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it —
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to —

LoRa Config

On Settings → LoRa.

Setting Beskrivelse Default
Region Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number Unset (must configure)
Presets Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Transmit Power Transmission power (dBm); 0 = max allowed for region 0 (region max)
Frequency Override Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Use Preset On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead From preset
Coding Rate Manual mode only: 5–8. More redundancy costs airtime From preset
Bandwidth Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Frequency Slot Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmit Enabled Turning this off makes the node receive-only On
Override Duty Cycle Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
Ignore MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok to MQTT Allow your packets to be forwarded to MQTT by gateways Off
RX Boosted Gain Extra receive gain on SX126x radios; costs a little current Off
PA fan disabled Turn off the power-amplifier fan on hardware that has one Off

The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set.

Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Speed SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a modem preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Display Config

On Settings → Device configuration → Display. These control the node’s own screen, not the app’s.

Setting Beskrivelse
Screen on for How long the display stays lit before sleeping
Carousel interval How often the node cycles between screens on its own
Display mode Screen layout/density used by the firmware
Display units Metric or Imperial on the node’s screen
Use 12h clock format Show the node’s clock as 12-hour rather than 24-hour
Bold Heading Draw the screen’s heading text in bold
Flip screen Rotate the display 180° for an inverted mounting
OLED type Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED
Wake on tap or motion Light the screen when the node is tapped or moved
Compass orientation Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each
Always point north Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Position Config

On Settings → Device configuration → Position.

Setting Beskrivelse
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the node asks its GPS for a fix
Broadcast Interval How often the position is shared with the mesh
Smart Position Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Fixed Position Use a manually entered latitude, longitude and altitude instead of the GPS
Position Flags A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Power Config

On Settings → Device configuration → Power.

Setting Beskrivelse
Enable power saving mode Let the node sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the node stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC multiplier override ratio The correction factor itself, used only when the override is on
Battery INA_2XX I2C address Address of an external INA-series power sensor, if fitted

Network Config

On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node.

Setting Beskrivelse
Wi-Fi enabled Enable the Wi-Fi node (ESP32 nodes)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Password Network password
Ethernet enabled Use a wired connection on hardware that has one
IPv4 mode DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP server Time synchronization server
rsyslog server Remote logging server

Network Config with a static IPv4 address entered

Bluetooth Config

On Settings → Device configuration → Bluetooth, on nodes with Bluetooth.

Setting Beskrivelse
Bluetooth enabled Enable/disable BLE radio
Pairing mode Fixed PIN, Random PIN, or No PIN
Fixed PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Security Config

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

Setting Beskrivelse
Offentlig nøkkel Your node’s public key (read-only)
Admin Key Keys permitted to administer this node remotely — up to three
Privat nøkkel Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it
Regenerate Private Key Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Serial console Serial console over the Stream API
Debug log API enabled Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth
Managed Mode Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.

+ Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Norsk
Meshtastic Docs ↗

🌐 Norsk — Community translation View in English

Settings — Radio & User

Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How these screens work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Beskrivelse
Long Name Your display name (up to 39 characters)
Short Name 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Unmessageable Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur node (Ham) Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in.

Configuration

Device Config

On Settings → Device configuration → Device.

Setting Beskrivelse Default
Device Role Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Rebroadcast Mode How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Node Info Broadcast Interval How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Double Tap as Button Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Enabled
LED Heartbeat Blink the status LED periodically Enabled
Time Zone POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it —
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to —

LoRa Config

On Settings → LoRa.

Setting Beskrivelse Default
Region Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number Unset (must configure)
Presets Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Transmit Power (dBm) Transmission power; 0 = max allowed for region 0 (region max)
Frequency Override Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Use Preset On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead From preset
Coding Rate Manual mode only: 5–8. More redundancy costs airtime From preset
Bandwidth Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Frequency Slot Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmit Enabled Turning this off makes the node receive-only On
Override Duty Cycle Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
Ignore MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok to MQTT Allow your packets to be forwarded to MQTT by gateways Off
RX Boosted Gain Extra receive gain on SX126x radios; costs a little current Off
PA fan disabled Turn off the power-amplifier fan on hardware that has one Off

The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set.

Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Speed SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a modem preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Display Config

On Settings → Device configuration → Display. These control the node’s own screen, not the app’s.

Setting Beskrivelse
Screen on for How long the display stays lit before sleeping
Carousel interval How often the node cycles between screens on its own
Display mode Screen layout/density used by the firmware
Display units Metric or Imperial on the node’s screen
Use 12h clock format Show the node’s clock as 12-hour rather than 24-hour
Bold Heading Draw the screen’s heading text in bold
Flip screen Rotate the display 180° for an inverted mounting
OLED type Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED
Wake on tap or motion Light the screen when the node is tapped or moved
Compass orientation Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each
Always point north Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Position Config

On Settings → Device configuration → Position.

Setting Beskrivelse
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the node asks its GPS for a fix
Broadcast Interval How often the position is shared with the mesh
Smart Position Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Fixed Position Use a manually entered latitude, longitude and altitude instead of the GPS
Position Flags A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Power Config

On Settings → Device configuration → Power.

Setting Beskrivelse
Enable power saving mode Let the node sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the node stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC multiplier override ratio The correction factor itself, used only when the override is on
Battery INA_2XX I2C address Address of an external INA-series power sensor, if fitted

Network Config

On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node.

Setting Beskrivelse
Wi-Fi enabled Enable the Wi-Fi node (ESP32 nodes)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Password Network password
Ethernet enabled Use a wired connection on hardware that has one
IPv4 mode DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP server Time synchronization server
rsyslog server Remote logging server

Network Config with a static IPv4 address entered

Bluetooth Config

On Settings → Device configuration → Bluetooth, on nodes with Bluetooth.

Setting Beskrivelse
Bluetooth enabled Enable/disable BLE radio
Pairing mode Fixed PIN, Random PIN, or No PIN
Fixed PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Security Config

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

Setting Beskrivelse
Offentlig nøkkel Your node’s public key (read-only)
Admin Key Keys permitted to administer this node remotely — up to three
Privat nøkkel Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it
Regenerate Private Key Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Serial console Serial console over the Stream API
Debug log API enabled Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth
Managed Mode Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.

diff --git a/main/pl-rPL/user/discovery.html b/main/pl-rPL/user/discovery.html index de8608a866..ff3ba1b859 100644 --- a/main/pl-rPL/user/discovery.html +++ b/main/pl-rPL/user/discovery.html @@ -5,4 +5,4 @@ ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) -

Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:.

What to look for What it means
All hops show Good SNR (green) Healthy path — messages flow reliably
One hop shows a poor SNR (orange or red) Weak link — this relay segment is fragile
Many hops (4+) Long path — consider repositioning a node to shorten it
Different path on retry Mesh is adapting — multiple routes exist (this is good!)

💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network.

Troubleshooting with Traceroute

  • No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key.
  • Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa.
  • Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position.
  • Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric.

Informacje o sąsiadze

The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh.

Enabling Neighbor Info

  1. Navigate to Settings → Module configuration → Neighbor Info.
  2. Enable the module.
  3. Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
  4. Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air.

Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.

Viewing neighbor data

  • Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors.
  • Each neighbor entry shows the node that was directly heard and its signal quality.
  • Combine neighbor data from multiple nodes to understand the full mesh topology.

ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further.

Node list as a discovery tool

The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively.

Finding new nodes

  • Sort by Last heard to see the most recently active nodes at the top.
  • Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes.

Assessing connectivity

  • Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed.
  • Sort by Distance to find nearby nodes and verify they’re reachable.
  • Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge).

Infrastructure audit

  • Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes.
  • Check their signal quality and last-heard times to verify your infrastructure nodes are healthy.

See Nodes for full details on filtering and sorting options.

Tips for Mesh exploration

  • Start with traceroute — it gives you immediate, actionable information about a specific path.
  • Enable Neighbor Info on key nodes — especially routers and repeaters, to build a picture of the backbone.
  • Check the map — node positions on the Map combined with signal data help you understand why some links are strong and others are weak.
  • Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly.
+

Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:.

What to look for What it means
All hops show Good SNR (green) Healthy path — messages flow reliably
One hop shows a poor SNR (orange or red) Weak link — this relay segment is fragile
Many hops (4+) Long path — consider repositioning a node to shorten it
Different path on retry Mesh is adapting — multiple routes exist (this is good!)

💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network.

Troubleshooting with Traceroute

  • No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key.
  • Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa.
  • Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position.
  • Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric.

Informacje o sąsiadze

The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh.

Enabling Neighbor Info

  1. Navigate to Settings → Module configuration → Neighbor Info.
  2. Enable the module.
  3. Set Update Interval. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
  4. Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air.

Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.

Viewing neighbor data

  • Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors.
  • Each neighbor entry shows the node that was directly heard and its signal quality.
  • Combine neighbor data from multiple nodes to understand the full mesh topology.

ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further.

Node list as a discovery tool

The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively.

Finding new nodes

  • Sort by Last heard to see the most recently active nodes at the top.
  • Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes.

Assessing connectivity

  • Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed.
  • Sort by Distance to find nearby nodes and verify they’re reachable.
  • Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge).

Infrastructure audit

  • Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes.
  • Check their signal quality and last-heard times to verify your infrastructure nodes are healthy.

See Nodes for full details on filtering and sorting options.

Tips for Mesh exploration

  • Start with traceroute — it gives you immediate, actionable information about a specific path.
  • Enable Neighbor Info on key nodes — especially routers and repeaters, to build a picture of the backbone.
  • Check the map — node positions on the Map combined with signal data help you understand why some links are strong and others are weak.
  • Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly.
diff --git a/main/pl-rPL/user/mqtt.html b/main/pl-rPL/user/mqtt.html index 4d542cd431..aa2ef0412e 100644 --- a/main/pl-rPL/user/mqtt.html +++ b/main/pl-rPL/user/mqtt.html @@ -1,2 +1,2 @@ MQTT | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Polski
Meshtastic Docs ↗

🌐 Polski — Community translation View in English

MQTT

MQTT bridges your Meshtastic mesh network to the internet, enabling long-range communication beyond radio range.

Overview

The MQTT module connects your node to an MQTT broker, allowing:

  • Messages to reach nodes on different physical meshes via the internet
  • Integration with home automation and monitoring systems
  • Publishing node positions to the public Meshtastic map
  • Custom data pipelines for logging and alerting

How It Works 

[Your Node] → Radio → [Gateway Node with Wi-Fi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node]
-

A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh.

Konfiguracja

Enabling MQTT

  1. Navigate to Settings → Module configuration → MQTT.
  2. Enable the MQTT module.
  3. Configure the broker connection:
Setting Opis Domyślny
Address MQTT broker hostname mqtt.meshtastic.org
Username Broker authentication meshdev
Password Broker authentication large4cats
Root topic Base topic for messages msh, which the radio rewrites to msh/<REGION> once you set a region
Encryption enabled Encrypt MQTT payload Włączony
JSON output enabled Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it Wyłączony
TLS enabled Secure connection to broker Wyłączony
Map reporting Report position to public map Wyłączony
Proxy to client enabled Relay MQTT through the connected phone Wyłączony

Connection Status and Test Connection

The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here.

Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason.

MQTT Proxy on This Phone

If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection.

ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them.

The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration.

Default Meshtastic Broker

The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing.

When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without).

🔒 Privacy: Messages on the public broker are readable by anyone subscribed. Always use channel encryption for private communications.

Private Broker

For better privacy and control, you can run your own MQTT broker:

  • Mosquitto (lightweight, open-source)
  • HiveMQ
  • EMQX

Configure your node to point to your private broker with appropriate credentials.

Map Reporting

When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.

Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.

Reports appear at meshmap.net and similar community map services.

🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published.

Direction Opis
Uplink Messages from mesh → MQTT broker
Downlink Messages from MQTT broker → mesh

Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on.

Message Formats

MQTT carries two payload formats:

Format Opis Use case
Protobuf Binary Meshtastic protobuf encoding Node-to-node mesh bridging
JSON Human-readable JSON on the /2/json/ topic Consumers outside the mesh (dashboards, home automation)

ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads.

Encryption & Privacy

Understanding the layered encryption model:

  1. Channel encryption happens on the mesh before MQTT. If your channel has a PSK, the MQTT payload is already encrypted — the broker and any subscribers see only the ciphertext.
  2. Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard.
  3. TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping.

🔒 Security: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications.

Best Practices

  • Use channel-level encryption (PSK) on channels that bridge to MQTT
  • Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes memory)
  • Use a private broker for sensitive deployments
  • Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh
  • Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back

Troubleshooting

MQTT Not Connecting

  • Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself.
  • Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces.
  • Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443).
  • DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly.

Messages Not Bridging

  • Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway.
  • Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage.
  • Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root.
  • Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway.
  • Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in.
+

A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh.

Konfiguracja

Enabling MQTT

  1. Navigate to Settings → Module configuration → MQTT.
  2. Enable the MQTT module.
  3. Configure the broker connection:
Setting Opis Domyślny
Address MQTT broker hostname mqtt.meshtastic.org
Username Broker authentication meshdev
Password Broker authentication large4cats
Root topic Base topic for messages msh, which the radio rewrites to msh/<REGION> once you set a region
Encryption enabled Encrypt MQTT payload Włączony
JSON output enabled Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it Wyłączony
TLS enabled Secure connection to broker Wyłączony
Map reporting Report position to public map Wyłączony
Proxy to client enabled Relay MQTT through the connected phone Wyłączony

Connection Status and Test Connection

The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here.

Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason.

MQTT Proxy on This Phone

If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection.

ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them.

The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration.

Default Meshtastic Broker

The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing.

When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without).

🔒 Privacy: Messages on the public broker are readable by anyone subscribed. Always use channel encryption for private communications.

Private Broker

For better privacy and control, you can run your own MQTT broker:

  • Mosquitto (lightweight, open-source)
  • HiveMQ
  • EMQX

Configure your node to point to your private broker with appropriate credentials.

Map Reporting

When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.

Turning it on opens a consent card. Turn on I agree. and choose a Map Publish Interval of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.

Reports appear at meshmap.net and similar community map services.

🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published.

Direction Opis
Uplink Messages from mesh → MQTT broker
Downlink Messages from MQTT broker → mesh

Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on.

Message Formats

MQTT carries two payload formats:

Format Opis Use case
Protobuf Binary Meshtastic protobuf encoding Node-to-node mesh bridging
JSON Human-readable JSON on the /2/json/ topic Consumers outside the mesh (dashboards, home automation)

ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads.

Encryption & Privacy

Understanding the layered encryption model:

  1. Channel encryption happens on the mesh before MQTT. If your channel has a PSK, the MQTT payload is already encrypted — the broker and any subscribers see only the ciphertext.
  2. Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard.
  3. TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping.

🔒 Security: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications.

Best Practices

  • Use channel-level encryption (PSK) on channels that bridge to MQTT
  • Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes memory)
  • Use a private broker for sensitive deployments
  • Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh
  • Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back

Troubleshooting

MQTT Not Connecting

  • Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself.
  • Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces.
  • Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443).
  • DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly.

Messages Not Bridging

  • Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway.
  • Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage.
  • Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root.
  • Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway.
  • Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in.
diff --git a/main/pl-rPL/user/settings-module-admin.html b/main/pl-rPL/user/settings-module-admin.html index 6adcb7b5b5..8b549f9181 100644 --- a/main/pl-rPL/user/settings-module-admin.html +++ b/main/pl-rPL/user/settings-module-admin.html @@ -1 +1 @@ - Settings — Modules & Admin | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Polski
Meshtastic Docs ↗

🌐 Polski — Community translation View in English

Settings — Modules & Admin

Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.

💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.

Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:

A toggle setting in the on position

A dropdown setting, expanded to show its list of options

A text field setting with a value entered

A module settings card with its title and grouped controls

Ustawienia modułu

Every module lives under Settings → Module configuration.

⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes.

MQTT module

Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.

Setting Opis
Włącz MQTT Toggle MQTT bridge
Adres MQTT broker address
Nazwa użytkownika Authentication username
Hasło Authentication password
Szyfrowanie włączone Encrypt MQTT payloads
Włącz wyjście JSON Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
Włącz TLS Use secure connection
Główny wątek Base MQTT topic path
Proxy to client enabled Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy on this phone The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT
Raportowanie map Publish position to the public map — see the Map reporting group that follows

Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:

Setting Opis
Zgadzam się. Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Interwał raportowania map (sekundy) How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered

See MQTT for a detailed usage guide including encryption, privacy, and broker setup.

Serial module

Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.

Setting Opis
Włącz tryb serial Activate serial communication
Włącz echo Echo received serial data back
Tryb serial Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX GPIO pins for the serial connection
Prędkość transmisji Port speed
Limit czasu How long to wait before considering an incoming message complete
Override console serial port Take over the port the debug console normally uses

External Notification module

Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.

There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.

Setting Opis
Powiadomienia zewnętrzne włączone Master toggle for the module
Alert message LED / buzzer / vibra Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra Which outputs fire on a received bell character
Wyjście LED (GPIO) Pin the LED is wired to
Output LED active high Whether the LED pin is active high or low
Wyjście buzzera (GPIO) Pin the buzzer is wired to
Wyjście silnika wibracyjnego (GPIO) Pin the vibration motor is wired to
Użyj buzzer PWM Drive the buzzer with PWM, which allows tones rather than a single pitch
Użyj I2S jako buzzer Send the alert through an I2S audio output instead
Czas trwania (w milisekundach) How long a single alert lasts
Nag timeout (seconds) Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Dzwonek The tone played on a PWM buzzer, in RTTTL. Can be imported from a file

Store & Forward module

Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.

Setting Opis
Store & Forward enabled Activate store and forward
Bicie serca Periodically announce this node’s store-and-forward capability
Liczba rekordów Maximum stored messages
Maks zwrotnej historii Max messages to replay
Okno zwrotu historii Time window for replay
Serwer Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)

💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.

Range Test module

⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.

Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.

Setting Opis
Range test enabled Activate range testing
Sender message interval (seconds) Time between test transmissions, chosen from a dropdown of fixed intervals
Save .CSV in storage (ESP32 only) Log received test data to the node’s own filesystem. ESP32 hardware only

Telemetry module

Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).

Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.

Setting Opis
Send Device Telemetry Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval How often to report battery, uptime and channel utilization
Environment metrics module enabled Report the attached environment sensors
Environment metrics update interval How often to report them
Environment metrics on-screen enabled Also show these readings on the device’s own display
Environment metrics use Fahrenheit Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Włącz moduł metryk jakości powietrza Report particulate and CO₂ sensor data
Czas aktualizacji metryk jakości powietrza How often to report them
Włącz moduł metryk zasilania Report the per-channel voltage and current readings
Czas aktualizacji metryk zasilania How often to report them
Wyświetlaj metryki zasilania na ekranie Also show power readings on the device’s display

See Telemetry & Sensors for supported sensors and configuration recommendations.

Canned Message module

Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.

Setting Opis
Canned message enabled ⚠️ Deprecated in the protobuf schema
Wiadomości Newline-separated list of messages
Send bell Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Rotary encoder #1 enabled Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port The three pins the encoder is wired to
Generate input event on Press / CW / CCW Which key event each encoder action produces
Up/Down/Select input enabled A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source ⚠️ Deprecated in the protobuf schema

Audio module

Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.

Setting Opis
CODEC 2 włączony Activate audio module
Częstotliwość próbkowania CODEC2 Audio quality/bandwidth tradeoff
Pin PTT (Push-To-Talk) GPIO pin for the push-to-talk button
I2S word select GPIO pin for I2S WS
I2S data in GPIO pin for I2S DIN
I2S data out GPIO pin for I2S DOUT
Zegar I2S GPIO pin for the I2S bit clock

ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.

Remote Hardware module

GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.

⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.

Setting Opis
Remote Hardware enabled Activate remote GPIO access
Allow undefined pin access Allow access to any GPIO pin (security risk)
Dostępne piny Up to 4 GPIO pins this node exposes for remote read/write

Neighbor Info module

Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.

Setting Opis
Włącz informacje o sąsiedzie Activate neighbor broadcasting
Częstotliwość aktualizacji (w sekundach) How often to broadcast neighbor list
Nadaj przez LoRa Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name

See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.

Ambient Lighting module

Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.

Setting Opis
Stan diody LED Turn the LED on or off
Natężenie LED current limit (0–31)
Red / Green / Blue Individual color channel values (0–255)

Detection Sensor module

Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.

Setting Opis
Czujnik detekcji włączony Activate detection sensor
Pin GPIO do monitorowania GPIO pin connected to sensor
Detection trigger type How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Użyj trybu INPUT_PULLUP Enable the pin’s internal pull-up resistor
Minimalny czas transmisji (sekundy) Minimum time between alert broadcasts
State broadcast (seconds) Periodic state broadcast interval
Send bell with alert message Include bell character in alerts
Przyjazna nazwa Custom name for this sensor

Paxcounter module

People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.

Setting Opis
Paxcounter enabled Activate people counting
Częstotliwość aktualizacji (w sekundach) How often to report counts
Wi-Fi RSSI threshold Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE RSSI threshold The same cut-off for BLE advertisements (defaults to −80 dBm)

💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.

Status Message module

The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.

Mesh Beacon module

Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.

TAK module

Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.

Zarządzanie

Zdalne zarządzanie

Remotely configure nodes that share your admin key:

  1. Select the target node in the node list.
  2. Navigate to Settings for that node.
  3. Modify configuration.
  4. Tap Save — changes are sent over the mesh.

⚠️ Important: Requires an admin key configured on both your node and the target node.

Device Actions

Settings → Administration holds five one-shot actions, each behind a confirmation dialog:

Action What it does
Set time Sends your phone’s clock to the node
Uruchom ponownie Restarts the node
Wyłącz Powers the node down
Ustawienia fabryczne Returns every setting to its factory default
Zresetuj NodeDB Clears the node database. This dialog carries a Preserve Favorites? switch

⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.

Kopia zapasowa i przywracanie

Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.

Zaawansowane

Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.

Wyczyść bazę węzłów

Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.

  • Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
  • Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.

The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.

Panel debugowania

Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.

App Settings

The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:

Privacy

  • Allow analytics and crash reporting — opt in or out of diagnostics.
  • Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
  • Homoglyph encoding — how look-alike characters in names are handled.

Appearance

  • Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
  • Theme and Language.
  • Show full message timestamps.

Persistence

  • A cache limit for how much history is kept.
  • Export rangetest packets, Export all packets and Export node database.

On their own

  • Node Layout — how much detail each row of the node list shows.
  • Wi-Fi Provisioning for mPWRD-OS — see Connections.
  • Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
  • System AI — appears only where app functions are available; see App Functions.

A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.

O aplikacji

Settings → About carries the app’s own identity rather than the node’s:

Three sections:

  • What is Meshtastic? — a short description of the project.
  • Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
  • Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.

The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.

Potwierdzenia

Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.

Troubleshooting remote admin

  • “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
  • Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
  • Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
+ Settings — Modules & Admin | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Polski
Meshtastic Docs ↗

🌐 Polski — Community translation View in English

Settings — Modules & Admin

Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.

💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.

Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:

A toggle setting in the on position

A dropdown setting, expanded to show its list of options

A text field setting with a value entered

A module settings card with its title and grouped controls

Ustawienia modułu

Every module lives under Settings → Module configuration.

⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes.

MQTT module

Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.

Setting Opis
Włącz MQTT Toggle MQTT bridge
Adres MQTT broker address
Nazwa użytkownika Authentication username
Hasło Authentication password
Szyfrowanie włączone Encrypt MQTT payloads
Włącz wyjście JSON Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
Włącz TLS Use secure connection
Główny wątek Base MQTT topic path
Proxy to client enabled Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy on this phone The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT
Raportowanie map Publish position to the public map — see the Map reporting group that follows

Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:

Setting Opis
Zgadzam się. Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered

See MQTT for a detailed usage guide including encryption, privacy, and broker setup.

Serial module

Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.

Setting Opis
Włącz tryb serial Activate serial communication
Włącz echo Echo received serial data back
Tryb serial Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX GPIO pins for the serial connection
Prędkość transmisji Port speed
Limit czasu How long to wait before considering an incoming message complete
Override console serial port Take over the port the debug console normally uses

External Notification module

Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.

There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.

Setting Opis
Powiadomienia zewnętrzne włączone Master toggle for the module
Alert message LED / buzzer / vibra Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra Which outputs fire on a received bell character
Wyjście LED (GPIO) Pin the LED is wired to
Output LED active high Whether the LED pin is active high or low
Wyjście buzzera (GPIO) Pin the buzzer is wired to
Wyjście silnika wibracyjnego (GPIO) Pin the vibration motor is wired to
Użyj buzzer PWM Drive the buzzer with PWM, which allows tones rather than a single pitch
Użyj I2S jako buzzer Send the alert through an I2S audio output instead
GPIO Output Duration How long a single alert lasts
Nag Czas przerwy Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Dzwonek The tone played on a PWM buzzer, in RTTTL. Can be imported from a file

Store & Forward module

Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.

Setting Opis
Store & Forward enabled Activate store and forward
Bicie serca Periodically announce this node’s store-and-forward capability
Liczba rekordów Maximum stored messages
Maks zwrotnej historii Max messages to replay
Okno zwrotu historii Time window for replay
Serwer Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)

💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.

Range Test module

⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.

Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.

Setting Opis
Range test enabled Activate range testing
Sender Interval Time between test transmissions, chosen from a dropdown of fixed intervals
Save .CSV in storage (ESP32 only) Log received test data to the node’s own filesystem. ESP32 hardware only

Telemetry module

Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).

Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.

Setting Opis
Send Device Telemetry Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval How often to report battery, uptime and channel utilization
Environment metrics module enabled Report the attached environment sensors
Environment metrics update interval How often to report them
Environment metrics on-screen enabled Also show these readings on the device’s own display
Environment metrics use Fahrenheit Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Włącz moduł metryk jakości powietrza Report particulate and CO₂ sensor data
Czas aktualizacji metryk jakości powietrza How often to report them
Włącz moduł metryk zasilania Report the per-channel voltage and current readings
Czas aktualizacji metryk zasilania How often to report them
Wyświetlaj metryki zasilania na ekranie Also show power readings on the device’s display

See Telemetry & Sensors for supported sensors and configuration recommendations.

Canned Message module

Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.

Setting Opis
Canned message enabled ⚠️ Deprecated in the protobuf schema
Wiadomości Newline-separated list of messages
Send bell Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Rotary encoder #1 enabled Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port The three pins the encoder is wired to
Generate input event on Press / CW / CCW Which key event each encoder action produces
Up/Down/Select input enabled A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source ⚠️ Deprecated in the protobuf schema

Audio module

Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.

Setting Opis
CODEC 2 włączony Activate audio module
Częstotliwość próbkowania CODEC2 Audio quality/bandwidth tradeoff
Pin PTT (Push-To-Talk) GPIO pin for the push-to-talk button
I2S word select GPIO pin for I2S WS
I2S data in GPIO pin for I2S DIN
I2S data out GPIO pin for I2S DOUT
Zegar I2S GPIO pin for the I2S bit clock

ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.

Remote Hardware module

GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.

⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.

Setting Opis
Remote Hardware enabled Activate remote GPIO access
Allow undefined pin access Allow access to any GPIO pin (security risk)
Dostępne piny Up to 4 GPIO pins this node exposes for remote read/write

Neighbor Info module

Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.

Setting Opis
Włącz informacje o sąsiedzie Activate neighbor broadcasting
Częstotliwość aktualizacji How often to broadcast neighbor list
Nadaj przez LoRa Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name

See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.

Ambient Lighting module

Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.

Setting Opis
Stan diody LED Turn the LED on or off
Natężenie LED current limit (0–31)
Red / Green / Blue Individual color channel values (0–255)

Detection Sensor module

Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.

Setting Opis
Czujnik detekcji włączony Activate detection sensor
Pin GPIO do monitorowania GPIO pin connected to sensor
Detection trigger type How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Użyj trybu INPUT_PULLUP Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts Minimum time between alert broadcasts
State Broadcast Interval Periodic state broadcast interval
Send bell with alert message Include bell character in alerts
Przyjazna nazwa Custom name for this sensor

Paxcounter module

People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.

Setting Opis
Paxcounter enabled Activate people counting
Częstotliwość aktualizacji How often to report counts
WiFi Threshold (dBm) Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm) The same cut-off for BLE advertisements (defaults to −80 dBm)

💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.

Status Message module

The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.

Mesh Beacon module

Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.

TAK module

Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.

Zarządzanie

Zdalne zarządzanie

Remotely configure nodes that share your admin key:

  1. Select the target node in the node list.
  2. Navigate to Settings for that node.
  3. Modify configuration.
  4. Tap Save — changes are sent over the mesh.

⚠️ Important: Requires an admin key configured on both your node and the target node.

Device Actions

Settings → Administration holds five one-shot actions, each behind a confirmation dialog:

Action What it does
Set time Sends your phone’s clock to the node
Uruchom ponownie Restarts the node
Wyłącz Powers the node down
Ustawienia fabryczne Returns every setting to its factory default
Zresetuj NodeDB Clears the node database. This dialog carries a Preserve Favorites? switch

⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.

Kopia zapasowa i przywracanie

Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.

Zaawansowane

Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.

Wyczyść bazę węzłów

Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.

  • Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
  • Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.

The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.

Panel debugowania

Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.

App Settings

The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:

Privacy

  • Allow analytics and crash reporting — opt in or out of diagnostics.
  • Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
  • Homoglyph encoding — how look-alike characters in names are handled.

Appearance

  • Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
  • Theme and Language.
  • Show full message timestamps.

Persistence

  • A cache limit for how much history is kept.
  • Export rangetest packets, Export all packets and Export node database.

On their own

  • Node Layout — how much detail each row of the node list shows.
  • Wi-Fi Provisioning for mPWRD-OS — see Connections.
  • Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
  • System AI — appears only where app functions are available; see App Functions.

A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.

O aplikacji

Settings → About carries the app’s own identity rather than the node’s:

Three sections:

  • What is Meshtastic? — a short description of the project.
  • Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
  • Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.

The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.

Potwierdzenia

Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.

Troubleshooting remote admin

  • “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
  • Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
  • Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
diff --git a/main/pl-rPL/user/settings-radio-user.html b/main/pl-rPL/user/settings-radio-user.html index f6b1d208c7..167f6311a3 100644 --- a/main/pl-rPL/user/settings-radio-user.html +++ b/main/pl-rPL/user/settings-radio-user.html @@ -1 +1 @@ - Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Polski
Meshtastic Docs ↗

🌐 Polski — Community translation View in English

Settings — Radio & User

Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How these screens work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Opis
Długa nazwa Your display name (up to 39 characters)
Krótka nazwa 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Nie przyjmuje wiadomości Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur node (Ham) Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in.

Konfiguracja

Konfiguracja urządzenia

On Settings → Device configuration → Device.

Setting Opis Domyślny
Rola urządzenia Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Tryb retransmisji How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Interwał transmisji informacji o węźle How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Podwójne dotknięcie jako naciśnięcie przycisku Treat a double tap as a button press Wyłączony
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Włączony
LED bicia serca Blink the status LED periodically Włączony
Strefa czasowa POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it —
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to —

Konfiguracja LoRa

On Settings → LoRa.

Setting Opis Domyślny
Region Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number Unset (must configure)
Presety Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Moc nadawania Transmission power (dBm); 0 = max allowed for region 0 (region max)
Frequency Override Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Użyj predefiniowanych ustawień On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead From preset
Szybkość kodowania Manual mode only: 5–8. More redundancy costs airtime From preset
Pasmo Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Slot częstotliwości Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmisja włączona Turning this off makes the node receive-only On
Nadpisz cykl pracy Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Wyłączony
Zignoruj MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok dla MQTT Allow your packets to be forwarded to MQTT by gateways Wyłączony
RX Boosted Gain Extra receive gain on SX126x radios; costs a little current Wyłączony
PA fan disabled Turn off the power-amplifier fan on hardware that has one Wyłączony

The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set.

Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Prędkość SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a modem preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Konfiguracja wyświetlacza

On Settings → Device configuration → Display. These control the node’s own screen, not the app’s.

Setting Opis
Ekran włączony na How long the display stays lit before sleeping
Interwał karuzeli How often the node cycles between screens on its own
Tryb wyświetlania Screen layout/density used by the firmware
Wyświetlana jednostka Metric or Imperial on the node’s screen
Użyj formatu 12-godzinnego Show the node’s clock as 12-hour rather than 24-hour
Pogrubiony nagłówek Draw the screen’s heading text in bold
Odwróć ekran Rotate the display 180° for an inverted mounting
Typ ekranu OLED Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED
Wybudź przy dotknięciu lub ruchu Light the screen when the node is tapped or moved
Orientacja kompasu Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each
Zawsze wskazywać na północ Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Konfiguracja pozycjonowania

On Settings → Device configuration → Position.

Setting Opis
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the node asks its GPS for a fix
Interwał transmisji How often the position is shared with the mesh
Inteligentne Pozycjonowanie Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Położenie stałe Use a manually entered latitude, longitude and altitude instead of the GPS
Flagi położenia A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Konfiguracja zarządzania energią

On Settings → Device configuration → Power.

Setting Opis
Włącz tryb oszczędzania energii Let the node sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the node stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC multiplier override ratio The correction factor itself, used only when the override is on
Battery INA_2XX I2C address Address of an external INA-series power sensor, if fitted

Konfiguracja sieci

On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node.

Setting Opis
Wi-Fi enabled Enable the Wi-Fi node (ESP32 nodes)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Hasło Hasło do sieci
Ethernet włączony Use a wired connection on hardware that has one
Tryb IPv4 DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
Serwer NTP Time synchronization server
Serwer rsyslog Remote logging server

Network Config with a static IPv4 address entered

Konfiguracja Bluetooth

On Settings → Device configuration → Bluetooth, on nodes with Bluetooth.

Setting Opis
Bluetooth włączony Enable/disable BLE radio
Tryb parowania Fixed PIN, Random PIN, or No PIN
Stały PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Konfiguracja zabezpieczeń

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

Setting Opis
Klucz publiczny Your node’s public key (read-only)
Klucz administratora Keys permitted to administer this node remotely — up to three
Klucz prywatny Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it
Regenerate Private Key Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Serial console Serial console over the Stream API
Debug log API enabled Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth
Managed Mode Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set
Klucze zapasowe Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.

+ Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Polski
Meshtastic Docs ↗

🌐 Polski — Community translation View in English

Settings — Radio & User

Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How these screens work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Opis
Długa nazwa Your display name (up to 39 characters)
Krótka nazwa 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Nie przyjmuje wiadomości Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur node (Ham) Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in.

Konfiguracja

Konfiguracja urządzenia

On Settings → Device configuration → Device.

Setting Opis Domyślny
Rola urządzenia Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Tryb retransmisji How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Interwał transmisji informacji o węźle How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Podwójne dotknięcie jako naciśnięcie przycisku Treat a double tap as a button press Wyłączony
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Włączony
LED bicia serca Blink the status LED periodically Włączony
Strefa czasowa POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it —
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to —

Konfiguracja LoRa

On Settings → LoRa.

Setting Opis Domyślny
Region Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number Unset (must configure)
Presety Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Transmit Power (dBm) Transmission power; 0 = max allowed for region 0 (region max)
Frequency Override Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Użyj predefiniowanych ustawień On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead From preset
Szybkość kodowania Manual mode only: 5–8. More redundancy costs airtime From preset
Pasmo Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Slot częstotliwości Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmisja włączona Turning this off makes the node receive-only On
Nadpisz cykl pracy Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Wyłączony
Zignoruj MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok dla MQTT Allow your packets to be forwarded to MQTT by gateways Wyłączony
RX Boosted Gain Extra receive gain on SX126x radios; costs a little current Wyłączony
PA fan disabled Turn off the power-amplifier fan on hardware that has one Wyłączony

The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set.

Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Prędkość SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a modem preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Konfiguracja wyświetlacza

On Settings → Device configuration → Display. These control the node’s own screen, not the app’s.

Setting Opis
Ekran włączony na How long the display stays lit before sleeping
Interwał karuzeli How often the node cycles between screens on its own
Tryb wyświetlania Screen layout/density used by the firmware
Wyświetlana jednostka Metric or Imperial on the node’s screen
Użyj formatu 12-godzinnego Show the node’s clock as 12-hour rather than 24-hour
Pogrubiony nagłówek Draw the screen’s heading text in bold
Odwróć ekran Rotate the display 180° for an inverted mounting
Typ ekranu OLED Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED
Wybudź przy dotknięciu lub ruchu Light the screen when the node is tapped or moved
Orientacja kompasu Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each
Zawsze wskazywać na północ Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Konfiguracja pozycjonowania

On Settings → Device configuration → Position.

Setting Opis
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the node asks its GPS for a fix
Interwał transmisji How often the position is shared with the mesh
Inteligentne Pozycjonowanie Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Położenie stałe Use a manually entered latitude, longitude and altitude instead of the GPS
Flagi położenia A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Konfiguracja zarządzania energią

On Settings → Device configuration → Power.

Setting Opis
Włącz tryb oszczędzania energii Let the node sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the node stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC multiplier override ratio The correction factor itself, used only when the override is on
Battery INA_2XX I2C address Address of an external INA-series power sensor, if fitted

Konfiguracja sieci

On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node.

Setting Opis
Wi-Fi enabled Enable the Wi-Fi node (ESP32 nodes)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Hasło Hasło do sieci
Ethernet włączony Use a wired connection on hardware that has one
Tryb IPv4 DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
Serwer NTP Time synchronization server
Serwer rsyslog Remote logging server

Network Config with a static IPv4 address entered

Konfiguracja Bluetooth

On Settings → Device configuration → Bluetooth, on nodes with Bluetooth.

Setting Opis
Bluetooth włączony Enable/disable BLE radio
Tryb parowania Fixed PIN, Random PIN, or No PIN
Stały PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Konfiguracja zabezpieczeń

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

Setting Opis
Klucz publiczny Your node’s public key (read-only)
Klucz administratora Keys permitted to administer this node remotely — up to three
Klucz prywatny Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it
Regenerate Private Key Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Serial console Serial console over the Stream API
Debug log API enabled Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth
Managed Mode Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set
Klucze zapasowe Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.

diff --git a/main/pt-rBR/user/discovery.html b/main/pt-rBR/user/discovery.html index 29a67deba7..25c9d767d2 100644 --- a/main/pt-rBR/user/discovery.html +++ b/main/pt-rBR/user/discovery.html @@ -5,4 +5,4 @@ ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) -

Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:.

What to look for What it means
All hops show Good SNR (green) Healthy path — messages flow reliably
One hop shows a poor SNR (orange or red) Weak link — this relay segment is fragile
Many hops (4+) Long path — consider repositioning a node to shorten it
Different path on retry Mesh is adapting — multiple routes exist (this is good!)

💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network.

Troubleshooting with Traceroute

  • No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key.
  • Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa.
  • Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position.
  • Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric.

Informações do Vizinho

The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh.

Enabling Neighbor Info

  1. Navigate to Settings → Module configuration → Neighbor Info.
  2. Enable the module.
  3. Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
  4. Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air.

Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.

Viewing neighbor data

  • Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors.
  • Each neighbor entry shows the node that was directly heard and its signal quality.
  • Combine neighbor data from multiple nodes to understand the full mesh topology.

ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further.

Node list as a discovery tool

The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively.

Finding new nodes

  • Sort by Last heard to see the most recently active nodes at the top.
  • Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes.

Assessing connectivity

  • Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed.
  • Sort by Distance to find nearby nodes and verify they’re reachable.
  • Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge).

Infrastructure audit

  • Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes.
  • Check their signal quality and last-heard times to verify your infrastructure nodes are healthy.

See Nodes for full details on filtering and sorting options.

Tips for Mesh exploration

  • Start with traceroute — it gives you immediate, actionable information about a specific path.
  • Enable Neighbor Info on key nodes — especially routers and repeaters, to build a picture of the backbone.
  • Check the map — node positions on the Map combined with signal data help you understand why some links are strong and others are weak.
  • Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly.
+

Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:.

What to look for What it means
All hops show Good SNR (green) Healthy path — messages flow reliably
One hop shows a poor SNR (orange or red) Weak link — this relay segment is fragile
Many hops (4+) Long path — consider repositioning a node to shorten it
Different path on retry Mesh is adapting — multiple routes exist (this is good!)

💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network.

Troubleshooting with Traceroute

  • No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key.
  • Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa.
  • Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position.
  • Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric.

Informações do Vizinho

The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh.

Enabling Neighbor Info

  1. Navigate to Settings → Module configuration → Neighbor Info.
  2. Enable the module.
  3. Set Update Interval. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
  4. Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air.

Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.

Viewing neighbor data

  • Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors.
  • Each neighbor entry shows the node that was directly heard and its signal quality.
  • Combine neighbor data from multiple nodes to understand the full mesh topology.

ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further.

Node list as a discovery tool

The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively.

Finding new nodes

  • Sort by Last heard to see the most recently active nodes at the top.
  • Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes.

Assessing connectivity

  • Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed.
  • Sort by Distance to find nearby nodes and verify they’re reachable.
  • Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge).

Infrastructure audit

  • Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes.
  • Check their signal quality and last-heard times to verify your infrastructure nodes are healthy.

See Nodes for full details on filtering and sorting options.

Tips for Mesh exploration

  • Start with traceroute — it gives you immediate, actionable information about a specific path.
  • Enable Neighbor Info on key nodes — especially routers and repeaters, to build a picture of the backbone.
  • Check the map — node positions on the Map combined with signal data help you understand why some links are strong and others are weak.
  • Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly.
diff --git a/main/pt-rBR/user/mqtt.html b/main/pt-rBR/user/mqtt.html index 40e2863eda..6895880609 100644 --- a/main/pt-rBR/user/mqtt.html +++ b/main/pt-rBR/user/mqtt.html @@ -1,2 +1,2 @@ MQTT | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Português (Brasil)
Meshtastic Docs ↗

🌐 Português (Brasil) — Community translation View in English

MQTT

MQTT bridges your Meshtastic mesh network to the internet, enabling long-range communication beyond radio range.

Overview

The MQTT module connects your node to an MQTT broker, allowing:

  • Messages to reach nodes on different physical meshes via the internet
  • Integration with home automation and monitoring systems
  • Publishing node positions to the public Meshtastic map
  • Custom data pipelines for logging and alerting

How It Works 

[Your Node] → Radio → [Gateway Node with Wi-Fi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node]
-

A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh.

Configuration

Enabling MQTT

  1. Navigate to Settings → Module configuration → MQTT.
  2. Enable the MQTT module.
  3. Configure the broker connection:
Setting Descrição Padrão
Address MQTT broker hostname mqtt.meshtastic.org
Username Broker authentication meshdev
Password Broker authentication large4cats
Root topic Base topic for messages msh, which the radio rewrites to msh/<REGION> once you set a region
Encryption enabled Encrypt MQTT payload Enabled
JSON output enabled Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it Disabled
TLS enabled Secure connection to broker Disabled
Map reporting Report position to public map Disabled
Proxy to client enabled Relay MQTT through the connected phone Disabled

Connection Status and Test Connection

The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here.

Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason.

MQTT Proxy on This Phone

If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection.

ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them.

The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration.

Default Meshtastic Broker

The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing.

When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without).

🔒 Privacy: Messages on the public broker are readable by anyone subscribed. Always use channel encryption for private communications.

Private Broker

For better privacy and control, you can run your own MQTT broker:

  • Mosquitto (lightweight, open-source)
  • HiveMQ
  • EMQX

Configure your node to point to your private broker with appropriate credentials.

Map Reporting

When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.

Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.

Reports appear at meshmap.net and similar community map services.

🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published.

Direction Descrição
Uplink Messages from mesh → MQTT broker
Downlink Messages from MQTT broker → mesh

Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on.

Message Formats

MQTT carries two payload formats:

Format Descrição Use case
Protobuf Binary Meshtastic protobuf encoding Node-to-node mesh bridging
JSON Human-readable JSON on the /2/json/ topic Consumers outside the mesh (dashboards, home automation)

ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads.

Encryption & Privacy

Understanding the layered encryption model:

  1. Channel encryption happens on the mesh before MQTT. If your channel has a PSK, the MQTT payload is already encrypted — the broker and any subscribers see only the ciphertext.
  2. Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard.
  3. TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping.

🔒 Security: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications.

Best Practices

  • Use channel-level encryption (PSK) on channels that bridge to MQTT
  • Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes memory)
  • Use a private broker for sensitive deployments
  • Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh
  • Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back

Troubleshooting

MQTT Not Connecting

  • Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself.
  • Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces.
  • Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443).
  • DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly.

Messages Not Bridging

  • Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway.
  • Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage.
  • Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root.
  • Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway.
  • Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in.
+

A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh.

Configuration

Enabling MQTT

  1. Navigate to Settings → Module configuration → MQTT.
  2. Enable the MQTT module.
  3. Configure the broker connection:
Setting Descrição Padrão
Address MQTT broker hostname mqtt.meshtastic.org
Username Broker authentication meshdev
Password Broker authentication large4cats
Root topic Base topic for messages msh, which the radio rewrites to msh/<REGION> once you set a region
Encryption enabled Encrypt MQTT payload Enabled
JSON output enabled Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it Disabled
TLS enabled Secure connection to broker Disabled
Map reporting Report position to public map Disabled
Proxy to client enabled Relay MQTT through the connected phone Disabled

Connection Status and Test Connection

The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here.

Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason.

MQTT Proxy on This Phone

If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection.

ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them.

The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration.

Default Meshtastic Broker

The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing.

When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without).

🔒 Privacy: Messages on the public broker are readable by anyone subscribed. Always use channel encryption for private communications.

Private Broker

For better privacy and control, you can run your own MQTT broker:

  • Mosquitto (lightweight, open-source)
  • HiveMQ
  • EMQX

Configure your node to point to your private broker with appropriate credentials.

Map Reporting

When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.

Turning it on opens a consent card. Turn on I agree. and choose a Map Publish Interval of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.

Reports appear at meshmap.net and similar community map services.

🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published.

Direction Descrição
Uplink Messages from mesh → MQTT broker
Downlink Messages from MQTT broker → mesh

Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on.

Message Formats

MQTT carries two payload formats:

Format Descrição Use case
Protobuf Binary Meshtastic protobuf encoding Node-to-node mesh bridging
JSON Human-readable JSON on the /2/json/ topic Consumers outside the mesh (dashboards, home automation)

ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads.

Encryption & Privacy

Understanding the layered encryption model:

  1. Channel encryption happens on the mesh before MQTT. If your channel has a PSK, the MQTT payload is already encrypted — the broker and any subscribers see only the ciphertext.
  2. Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard.
  3. TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping.

🔒 Security: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications.

Best Practices

  • Use channel-level encryption (PSK) on channels that bridge to MQTT
  • Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes memory)
  • Use a private broker for sensitive deployments
  • Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh
  • Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back

Troubleshooting

MQTT Not Connecting

  • Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself.
  • Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces.
  • Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443).
  • DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly.

Messages Not Bridging

  • Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway.
  • Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage.
  • Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root.
  • Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway.
  • Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in.
diff --git a/main/pt-rBR/user/settings-module-admin.html b/main/pt-rBR/user/settings-module-admin.html index 938d10097b..724a5d4abe 100644 --- a/main/pt-rBR/user/settings-module-admin.html +++ b/main/pt-rBR/user/settings-module-admin.html @@ -1 +1 @@ - Settings — Modules & Admin | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Português (Brasil)
Meshtastic Docs ↗

🌐 Português (Brasil) — Community translation View in English

Settings — Modules & Admin

Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.

💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.

Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:

A toggle setting in the on position

A dropdown setting, expanded to show its list of options

A text field setting with a value entered

A module settings card with its title and grouped controls

Configuração de módulos

Every module lives under Settings → Module configuration.

⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes.

MQTT module

Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.

Setting Descrição
MQTT habilitado Toggle MQTT bridge
Endereço MQTT broker address
Nome de usuário Authentication username
Senha Authentication password
Criptografia ativada Encrypt MQTT payloads
Saída JSON ativada Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS ativado Use secure connection
Tópico principal Base MQTT topic path
Proxy para cliente ativado Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy on this phone The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT
Relatório de mapa Publish position to the public map — see the Map reporting group that follows

Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:

Setting Descrição
Eu concordo. Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Intervalo de relatório de mapa (segundos) How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered

See MQTT for a detailed usage guide including encryption, privacy, and broker setup.

Serial module

Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.

Setting Descrição
Serial ativado Activate serial communication
Eco habilitado Echo received serial data back
Modo de série Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX GPIO pins for the serial connection
Taxa de transmissão série Port speed
Tempo esgotado How long to wait before considering an incoming message complete
Substituir porta série do console Take over the port the debug console normally uses

External Notification module

Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.

There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.

Setting Descrição
Notificação Externa habilitada Master toggle for the module
Alert message LED / buzzer / vibra Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra Which outputs fire on a received bell character
LED de Saída (GPIO) Pin the LED is wired to
LED de saída habilitado alto Whether the LED pin is active high or low
Saída Campainha (GPIO) Pin the buzzer is wired to
Vibra de saída (GPIO) Pin the vibration motor is wired to
Usar uma campainha PWM Drive the buzzer with PWM, which allows tones rather than a single pitch
Usar I2S como campainha Send the alert through an I2S audio output instead
Duração da Saída (milissegundos) How long a single alert lasts
Tempo limite do Nag (segundos) Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Toque The tone played on a PWM buzzer, in RTTTL. Can be imported from a file

Store & Forward module

Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.

Setting Descrição
Guardar e Encaminhar ativado Activate store and forward
Batimento Periodically announce this node’s store-and-forward capability
Número de registros Maximum stored messages
Histórico de retorno máximo Max messages to replay
Janela de retorno do histórico Time window for replay
Servidor Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)

💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.

Range Test module

⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.

Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.

Setting Descrição
Teste de distância ativado Activate range testing
Intervalo de mensagem do remetente (segundos) Time between test transmissions, chosen from a dropdown of fixed intervals
Salvar .CSV no armazenamento (apenas ESP32) Log received test data to the node’s own filesystem. ESP32 hardware only

Telemetry module

Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).

Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.

Setting Descrição
Send Device Telemetry Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval How often to report battery, uptime and channel utilization
Módulo de métricas do ambiente ativado Report the attached environment sensors
Environment metrics update interval How often to report them
Métricas de ambiente na tela habilitado Also show these readings on the device’s own display
Métricas de Ambiente usam Fahrenheit Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Módulo de métricas de qualidade do ar habilitado Report particulate and CO₂ sensor data
Air quality metrics update interval How often to report them
Módulo de métricas de energia habilitado Report the per-channel voltage and current readings
Power metrics update interval How often to report them
Métricas de ambiente na tela habilitado Also show power readings on the device’s display

See Telemetry & Sensors for supported sensors and configuration recommendations.

Canned Message module

Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.

Setting Descrição
Canned message enabled ⚠️ Deprecated in the protobuf schema
Mensagens Newline-separated list of messages
Enviar sino Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Codificador rotativo #1 ativado Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port The three pins the encoder is wired to
Generate input event on Press / CW / CCW Which key event each encoder action produces
Entrada Cima/Baixo/Selecionar ativada A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source ⚠️ Deprecated in the protobuf schema

Audio module

Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.

Setting Descrição
CODEC 2 ativado Activate audio module
Taxa de amostragem CODEC2 Audio quality/bandwidth tradeoff
Pino de PTT GPIO pin for the push-to-talk button
CS I2S GPIO pin for I2S WS
MOSI I2S GPIO pin for I2S DIN
MISO I2S GPIO pin for I2S DOUT
CLK I2S GPIO pin for the I2S bit clock

ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.

Remote Hardware module

GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.

⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.

Setting Descrição
Hardware Remoto ativado Activate remote GPIO access
Permitir acesso indefinido ao pino Allow access to any GPIO pin (security risk)
Pinos disponíveis Up to 4 GPIO pins this node exposes for remote read/write

Neighbor Info module

Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.

Setting Descrição
Informações do Vizinho ativado Activate neighbor broadcasting
Intervalo de atualização (segundos) How often to broadcast neighbor list
Transmitir por LoRa Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name

See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.

Ambient Lighting module

Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.

Setting Descrição
Estado do LED Turn the LED on or off
Atual LED current limit (0–31)
Red / Green / Blue Individual color channel values (0–255)

Detection Sensor module

Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.

Setting Descrição
Sensor de Detecção ativado Activate detection sensor
Pino GPIO para monitorar GPIO pin connected to sensor
Tipo de gatilho de deteção How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Usar o modo INPUT_PULLUP Enable the pin’s internal pull-up resistor
Transmissão mínima (segundos) Minimum time between alert broadcasts
Transmissão de estado (segundos) Periodic state broadcast interval
Enviar sino com mensagem de alerta Include bell character in alerts
Nome amigável Custom name for this sensor

Paxcounter module

People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.

Setting Descrição
Contador de Pessoas ativado Activate people counting
Intervalo de atualização (segundos) How often to report counts
Wi-Fi RSSI threshold Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE RSSI threshold The same cut-off for BLE advertisements (defaults to −80 dBm)

💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.

Status Message module

The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.

Mesh Beacon module

Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.

TAK module

Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.

Administração

Administração Remota

Remotely configure nodes that share your admin key:

  1. Select the target node in the node list.
  2. Navigate to Settings for that node.
  3. Modify configuration.
  4. Tap Save — changes are sent over the mesh.

⚠️ Important: Requires an admin key configured on both your node and the target node.

Device Actions

Settings → Administration holds five one-shot actions, each behind a confirmation dialog:

Action What it does
Set time Sends your phone’s clock to the node
Reiniciar Restarts the node
Desligar Powers the node down
Redefinição de fábrica Returns every setting to its factory default
Redefinir NodeDB Clears the node database. This dialog carries a Preserve Favorites? switch

⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.

Backup e Restaurar

Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.

Avançado

Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.

Limpar Banco de Dados de Nó

Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.

  • Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
  • Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.

The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.

Painel de depuração

Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.

App Settings

The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:

Privacy

  • Allow analytics and crash reporting — opt in or out of diagnostics.
  • Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
  • Homoglyph encoding — how look-alike characters in names are handled.

Appearance

  • Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
  • Theme and Language.
  • Show full message timestamps.

Persistence

  • A cache limit for how much history is kept.
  • Export rangetest packets, Export all packets and Export node database.

On their own

  • Node Layout — how much detail each row of the node list shows.
  • Wi-Fi Provisioning for mPWRD-OS — see Connections.
  • Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
  • System AI — appears only where app functions are available; see App Functions.

A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.

Sobre

Settings → About carries the app’s own identity rather than the node’s:

Three sections:

  • What is Meshtastic? — a short description of the project.
  • Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
  • Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.

The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.

Agradecimentos

Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.

Troubleshooting remote admin

  • “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
  • Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
  • Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
+ Settings — Modules & Admin | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Português (Brasil)
Meshtastic Docs ↗

🌐 Português (Brasil) — Community translation View in English

Settings — Modules & Admin

Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.

💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.

Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:

A toggle setting in the on position

A dropdown setting, expanded to show its list of options

A text field setting with a value entered

A module settings card with its title and grouped controls

Configuração de módulos

Every module lives under Settings → Module configuration.

⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes.

MQTT module

Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.

Setting Descrição
MQTT habilitado Toggle MQTT bridge
Endereço MQTT broker address
Nome de usuário Authentication username
Senha Authentication password
Criptografia ativada Encrypt MQTT payloads
Saída JSON ativada Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS ativado Use secure connection
Tópico principal Base MQTT topic path
Proxy para cliente ativado Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy on this phone The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT
Relatório de mapa Publish position to the public map — see the Map reporting group that follows

Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:

Setting Descrição
Eu concordo. Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered

See MQTT for a detailed usage guide including encryption, privacy, and broker setup.

Serial module

Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.

Setting Descrição
Serial ativado Activate serial communication
Eco habilitado Echo received serial data back
Modo de série Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX GPIO pins for the serial connection
Taxa de transmissão série Port speed
Tempo esgotado How long to wait before considering an incoming message complete
Substituir porta série do console Take over the port the debug console normally uses

External Notification module

Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.

There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.

Setting Descrição
Notificação Externa habilitada Master toggle for the module
Alert message LED / buzzer / vibra Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra Which outputs fire on a received bell character
LED de Saída (GPIO) Pin the LED is wired to
LED de saída habilitado alto Whether the LED pin is active high or low
Saída Campainha (GPIO) Pin the buzzer is wired to
Vibra de saída (GPIO) Pin the vibration motor is wired to
Usar uma campainha PWM Drive the buzzer with PWM, which allows tones rather than a single pitch
Usar I2S como campainha Send the alert through an I2S audio output instead
GPIO Output Duration How long a single alert lasts
Nag Timeout Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Toque The tone played on a PWM buzzer, in RTTTL. Can be imported from a file

Store & Forward module

Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.

Setting Descrição
Guardar e Encaminhar ativado Activate store and forward
Batimento Periodically announce this node’s store-and-forward capability
Número de registros Maximum stored messages
Histórico de retorno máximo Max messages to replay
Janela de retorno do histórico Time window for replay
Servidor Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)

💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.

Range Test module

⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.

Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.

Setting Descrição
Teste de distância ativado Activate range testing
Sender Interval Time between test transmissions, chosen from a dropdown of fixed intervals
Salvar .CSV no armazenamento (apenas ESP32) Log received test data to the node’s own filesystem. ESP32 hardware only

Telemetry module

Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).

Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.

Setting Descrição
Send Device Telemetry Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval How often to report battery, uptime and channel utilization
Módulo de métricas do ambiente ativado Report the attached environment sensors
Environment metrics update interval How often to report them
Métricas de ambiente na tela habilitado Also show these readings on the device’s own display
Métricas de Ambiente usam Fahrenheit Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Módulo de métricas de qualidade do ar habilitado Report particulate and CO₂ sensor data
Air quality metrics update interval How often to report them
Módulo de métricas de energia habilitado Report the per-channel voltage and current readings
Power metrics update interval How often to report them
Métricas de ambiente na tela habilitado Also show power readings on the device’s display

See Telemetry & Sensors for supported sensors and configuration recommendations.

Canned Message module

Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.

Setting Descrição
Canned message enabled ⚠️ Deprecated in the protobuf schema
Mensagens Newline-separated list of messages
Enviar sino Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Codificador rotativo #1 ativado Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port The three pins the encoder is wired to
Generate input event on Press / CW / CCW Which key event each encoder action produces
Entrada Cima/Baixo/Selecionar ativada A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source ⚠️ Deprecated in the protobuf schema

Audio module

Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.

Setting Descrição
CODEC 2 ativado Activate audio module
Taxa de amostragem CODEC2 Audio quality/bandwidth tradeoff
Pino de PTT GPIO pin for the push-to-talk button
CS I2S GPIO pin for I2S WS
MOSI I2S GPIO pin for I2S DIN
MISO I2S GPIO pin for I2S DOUT
CLK I2S GPIO pin for the I2S bit clock

ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.

Remote Hardware module

GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.

⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.

Setting Descrição
Hardware Remoto ativado Activate remote GPIO access
Permitir acesso indefinido ao pino Allow access to any GPIO pin (security risk)
Pinos disponíveis Up to 4 GPIO pins this node exposes for remote read/write

Neighbor Info module

Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.

Setting Descrição
Informações do Vizinho ativado Activate neighbor broadcasting
Update Interval How often to broadcast neighbor list
Transmitir por LoRa Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name

See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.

Ambient Lighting module

Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.

Setting Descrição
Estado do LED Turn the LED on or off
Atual LED current limit (0–31)
Red / Green / Blue Individual color channel values (0–255)

Detection Sensor module

Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.

Setting Descrição
Sensor de Detecção ativado Activate detection sensor
Pino GPIO para monitorar GPIO pin connected to sensor
Tipo de gatilho de deteção How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Usar o modo INPUT_PULLUP Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts Minimum time between alert broadcasts
State Broadcast Interval Periodic state broadcast interval
Enviar sino com mensagem de alerta Include bell character in alerts
Nome amigável Custom name for this sensor

Paxcounter module

People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.

Setting Descrição
Contador de Pessoas ativado Activate people counting
Update Interval How often to report counts
WiFi Threshold (dBm) Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm) The same cut-off for BLE advertisements (defaults to −80 dBm)

💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.

Status Message module

The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.

Mesh Beacon module

Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.

TAK module

Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.

Administração

Administração Remota

Remotely configure nodes that share your admin key:

  1. Select the target node in the node list.
  2. Navigate to Settings for that node.
  3. Modify configuration.
  4. Tap Save — changes are sent over the mesh.

⚠️ Important: Requires an admin key configured on both your node and the target node.

Device Actions

Settings → Administration holds five one-shot actions, each behind a confirmation dialog:

Action What it does
Set time Sends your phone’s clock to the node
Reiniciar Restarts the node
Desligar Powers the node down
Redefinição de fábrica Returns every setting to its factory default
Redefinir NodeDB Clears the node database. This dialog carries a Preserve Favorites? switch

⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.

Backup e Restaurar

Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.

Avançado

Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.

Limpar Banco de Dados de Nó

Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.

  • Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
  • Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.

The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.

Painel de depuração

Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.

App Settings

The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:

Privacy

  • Allow analytics and crash reporting — opt in or out of diagnostics.
  • Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
  • Homoglyph encoding — how look-alike characters in names are handled.

Appearance

  • Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
  • Theme and Language.
  • Show full message timestamps.

Persistence

  • A cache limit for how much history is kept.
  • Export rangetest packets, Export all packets and Export node database.

On their own

  • Node Layout — how much detail each row of the node list shows.
  • Wi-Fi Provisioning for mPWRD-OS — see Connections.
  • Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
  • System AI — appears only where app functions are available; see App Functions.

A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.

Sobre

Settings → About carries the app’s own identity rather than the node’s:

Three sections:

  • What is Meshtastic? — a short description of the project.
  • Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
  • Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.

The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.

Agradecimentos

Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.

Troubleshooting remote admin

  • “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
  • Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
  • Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
diff --git a/main/pt-rBR/user/settings-radio-user.html b/main/pt-rBR/user/settings-radio-user.html index 04c135e7e6..1c64b216a1 100644 --- a/main/pt-rBR/user/settings-radio-user.html +++ b/main/pt-rBR/user/settings-radio-user.html @@ -1 +1 @@ - Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Português (Brasil)
Meshtastic Docs ↗

🌐 Português (Brasil) — Community translation View in English

Settings — Radio & User

Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How these screens work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Descrição
Long Name Your display name (up to 39 characters)
Short Name 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Impossível enviar mensagens Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur node (Ham) Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in.

Configuration

Configuração do Dispositivo

On Settings → Device configuration → Device.

Setting Descrição Padrão
Device Role Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Rebroadcast Mode How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Node Info Broadcast Interval How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Double Tap as Button Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Enabled
LED Heartbeat Blink the status LED periodically Enabled
Time Zone POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it —
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to —

Configuração do LoRa

On Settings → LoRa.

Setting Descrição Padrão
Região Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number Unset (must configure)
Presets Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Transmit Power Transmission power (dBm); 0 = max allowed for region 0 (region max)
Frequency Override Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Use Preset On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead From preset
Coding Rate Manual mode only: 5–8. More redundancy costs airtime From preset
Largura da banda Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Frequency Slot Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmit Enabled Turning this off makes the node receive-only On
Ignorar ciclo de trabalho Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
Ignorar MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok to MQTT Allow your packets to be forwarded to MQTT by gateways Off
RX Boosted Gain Extra receive gain on SX126x radios; costs a little current Off
Ventilador do PA desativado Turn off the power-amplifier fan on hardware that has one Off

The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set.

Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Velocidade SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a modem preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Configuração da Tela

On Settings → Device configuration → Display. These control the node’s own screen, not the app’s.

Setting Descrição
Screen on for How long the display stays lit before sleeping
Carousel interval How often the node cycles between screens on its own
Modo da tela Screen layout/density used by the firmware
Unidades de exibição Metric or Imperial on the node’s screen
Usar formato de relógio 12h Show the node’s clock as 12-hour rather than 24-hour
Bold Heading Draw the screen’s heading text in bold
Inverter tela Rotate the display 180° for an inverted mounting
OLED type Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED
Wake on tap or motion Light the screen when the node is tapped or moved
Orientação da bússola Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each
Always point north Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Configuração da Posição

On Settings → Device configuration → Position.

Setting Descrição
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the node asks its GPS for a fix
Broadcast Interval How often the position is shared with the mesh
Smart Position Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Fixed Position Use a manually entered latitude, longitude and altitude instead of the GPS
Position Flags A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Configuração de Energia

On Settings → Device configuration → Power.

Setting Descrição
Ativar modo de economia de energia Let the node sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the node stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
Alterar proporção do multiplicador ADC The correction factor itself, used only when the override is on
Endereço I2C da bateria INA_2XX Address of an external INA-series power sensor, if fitted

Configuração de Rede

On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node.

Setting Descrição
Wi-Fi enabled Enable the Wi-Fi node (ESP32 nodes)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Senha Network password
Ethernet ativado Use a wired connection on hardware that has one
Modo IPv4 DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
Servidor NTP Time synchronization server
Servidor rsyslog Remote logging server

Network Config with a static IPv4 address entered

Configuração do Bluetooth

On Settings → Device configuration → Bluetooth, on nodes with Bluetooth.

Setting Descrição
Bluetooth habilitado Enable/disable BLE radio
Modo de pareamento Fixed PIN, Random PIN, or No PIN
PIN fixo PIN code for pairing. Must be exactly six digits — the field rejects anything else

Configurações de Segurança

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

Setting Descrição
Chave Publica Your node’s public key (read-only)
Chave do Administrador Keys permitted to administer this node remotely — up to three
Chave Privada Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it
Regenerar a chave privada Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Console serial Serial console over the Stream API
API de logs de depuração ativada Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth
Modo Administrado Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.

+ Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Português (Brasil)
Meshtastic Docs ↗

🌐 Português (Brasil) — Community translation View in English

Settings — Radio & User

Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How these screens work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Descrição
Long Name Your display name (up to 39 characters)
Short Name 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Impossível enviar mensagens Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur node (Ham) Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in.

Configuration

Configuração do Dispositivo

On Settings → Device configuration → Device.

Setting Descrição Padrão
Device Role Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Rebroadcast Mode How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Node Info Broadcast Interval How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Double Tap as Button Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Enabled
LED Heartbeat Blink the status LED periodically Enabled
Time Zone POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it —
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to —

Configuração do LoRa

On Settings → LoRa.

Setting Descrição Padrão
Região Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number Unset (must configure)
Presets Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Transmit Power (dBm) Transmission power; 0 = max allowed for region 0 (region max)
Frequency Override Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Use Preset On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead From preset
Coding Rate Manual mode only: 5–8. More redundancy costs airtime From preset
Largura da banda Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Frequency Slot Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmit Enabled Turning this off makes the node receive-only On
Ignorar ciclo de trabalho Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
Ignorar MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok to MQTT Allow your packets to be forwarded to MQTT by gateways Off
RX Boosted Gain Extra receive gain on SX126x radios; costs a little current Off
Ventilador do PA desativado Turn off the power-amplifier fan on hardware that has one Off

The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set.

Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Velocidade SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a modem preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Configuração da Tela

On Settings → Device configuration → Display. These control the node’s own screen, not the app’s.

Setting Descrição
Screen on for How long the display stays lit before sleeping
Carousel interval How often the node cycles between screens on its own
Modo da tela Screen layout/density used by the firmware
Unidades de exibição Metric or Imperial on the node’s screen
Usar formato de relógio 12h Show the node’s clock as 12-hour rather than 24-hour
Bold Heading Draw the screen’s heading text in bold
Inverter tela Rotate the display 180° for an inverted mounting
OLED type Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED
Wake on tap or motion Light the screen when the node is tapped or moved
Orientação da bússola Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each
Always point north Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Configuração da Posição

On Settings → Device configuration → Position.

Setting Descrição
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the node asks its GPS for a fix
Broadcast Interval How often the position is shared with the mesh
Smart Position Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Fixed Position Use a manually entered latitude, longitude and altitude instead of the GPS
Position Flags A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Configuração de Energia

On Settings → Device configuration → Power.

Setting Descrição
Ativar modo de economia de energia Let the node sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the node stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
Alterar proporção do multiplicador ADC The correction factor itself, used only when the override is on
Endereço I2C da bateria INA_2XX Address of an external INA-series power sensor, if fitted

Configuração de Rede

On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node.

Setting Descrição
Wi-Fi enabled Enable the Wi-Fi node (ESP32 nodes)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Senha Network password
Ethernet ativado Use a wired connection on hardware that has one
Modo IPv4 DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
Servidor NTP Time synchronization server
Servidor rsyslog Remote logging server

Network Config with a static IPv4 address entered

Configuração do Bluetooth

On Settings → Device configuration → Bluetooth, on nodes with Bluetooth.

Setting Descrição
Bluetooth habilitado Enable/disable BLE radio
Modo de pareamento Fixed PIN, Random PIN, or No PIN
PIN fixo PIN code for pairing. Must be exactly six digits — the field rejects anything else

Configurações de Segurança

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

Setting Descrição
Chave Publica Your node’s public key (read-only)
Chave do Administrador Keys permitted to administer this node remotely — up to three
Chave Privada Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it
Regenerar a chave privada Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Console serial Serial console over the Stream API
API de logs de depuração ativada Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth
Modo Administrado Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.

diff --git a/main/pt-rPT/user/discovery.html b/main/pt-rPT/user/discovery.html index 7525246243..d3e4c71ecc 100644 --- a/main/pt-rPT/user/discovery.html +++ b/main/pt-rPT/user/discovery.html @@ -5,4 +5,4 @@ ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) -

Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:.

What to look for What it means
All hops show Good SNR (green) Healthy path — messages flow reliably
One hop shows a poor SNR (orange or red) Weak link — this relay segment is fragile
Many hops (4+) Long path — consider repositioning a node to shorten it
Different path on retry Mesh is adapting — multiple routes exist (this is good!)

💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network.

Troubleshooting with Traceroute

  • No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key.
  • Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa.
  • Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position.
  • Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric.

Informações da vizinhança

The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh.

Enabling Neighbor Info

  1. Navigate to Settings → Module configuration → Neighbor Info.
  2. Enable the module.
  3. Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
  4. Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air.

Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.

Viewing neighbor data

  • Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors.
  • Each neighbor entry shows the node that was directly heard and its signal quality.
  • Combine neighbor data from multiple nodes to understand the full mesh topology.

ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further.

Node list as a discovery tool

The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively.

Finding new nodes

  • Sort by Last heard to see the most recently active nodes at the top.
  • Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes.

Assessing connectivity

  • Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed.
  • Sort by Distance to find nearby nodes and verify they’re reachable.
  • Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge).

Infrastructure audit

  • Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes.
  • Check their signal quality and last-heard times to verify your infrastructure nodes are healthy.

See Nodes for full details on filtering and sorting options.

Tips for Mesh exploration

  • Start with traceroute — it gives you immediate, actionable information about a specific path.
  • Enable Neighbor Info on key nodes — especially routers and repeaters, to build a picture of the backbone.
  • Check the map — node positions on the Map combined with signal data help you understand why some links are strong and others are weak.
  • Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly.
+

Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:.

What to look for What it means
All hops show Good SNR (green) Healthy path — messages flow reliably
One hop shows a poor SNR (orange or red) Weak link — this relay segment is fragile
Many hops (4+) Long path — consider repositioning a node to shorten it
Different path on retry Mesh is adapting — multiple routes exist (this is good!)

💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network.

Troubleshooting with Traceroute

  • No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key.
  • Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa.
  • Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position.
  • Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric.

Informações da vizinhança

The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh.

Enabling Neighbor Info

  1. Navigate to Settings → Module configuration → Neighbor Info.
  2. Enable the module.
  3. Set Update Interval. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
  4. Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air.

Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.

Viewing neighbor data

  • Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors.
  • Each neighbor entry shows the node that was directly heard and its signal quality.
  • Combine neighbor data from multiple nodes to understand the full mesh topology.

ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further.

Node list as a discovery tool

The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively.

Finding new nodes

  • Sort by Last heard to see the most recently active nodes at the top.
  • Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes.

Assessing connectivity

  • Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed.
  • Sort by Distance to find nearby nodes and verify they’re reachable.
  • Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge).

Infrastructure audit

  • Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes.
  • Check their signal quality and last-heard times to verify your infrastructure nodes are healthy.

See Nodes for full details on filtering and sorting options.

Tips for Mesh exploration

  • Start with traceroute — it gives you immediate, actionable information about a specific path.
  • Enable Neighbor Info on key nodes — especially routers and repeaters, to build a picture of the backbone.
  • Check the map — node positions on the Map combined with signal data help you understand why some links are strong and others are weak.
  • Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly.
diff --git a/main/pt-rPT/user/mqtt.html b/main/pt-rPT/user/mqtt.html index 343b5ca8fe..7666a50a49 100644 --- a/main/pt-rPT/user/mqtt.html +++ b/main/pt-rPT/user/mqtt.html @@ -1,2 +1,2 @@ MQTT | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Português
Meshtastic Docs ↗

🌐 Português — Community translation View in English

MQTT

MQTT bridges your Meshtastic mesh network to the internet, enabling long-range communication beyond radio range.

Overview

The MQTT module connects your node to an MQTT broker, allowing:

  • Messages to reach nodes on different physical meshes via the internet
  • Integration with home automation and monitoring systems
  • Publishing node positions to the public Meshtastic map
  • Custom data pipelines for logging and alerting

How It Works 

[Your Node] → Radio → [Gateway Node with Wi-Fi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node]
-

A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh.

Configuração

Enabling MQTT

  1. Navigate to Settings → Module configuration → MQTT.
  2. Enable the MQTT module.
  3. Configure the broker connection:
Setting Descrição Predefinição
Address MQTT broker hostname mqtt.meshtastic.org
Username Broker authentication meshdev
Password Broker authentication large4cats
Root topic Base topic for messages msh, which the radio rewrites to msh/<REGION> once you set a region
Encryption enabled Encrypt MQTT payload Enabled
JSON output enabled Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it Disabled
TLS enabled Secure connection to broker Disabled
Map reporting Report position to public map Disabled
Proxy to client enabled Relay MQTT through the connected phone Disabled

Connection Status and Test Connection

The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here.

Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason.

MQTT Proxy on This Phone

If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection.

ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them.

The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration.

Default Meshtastic Broker

The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing.

When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without).

🔒 Privacy: Messages on the public broker are readable by anyone subscribed. Always use channel encryption for private communications.

Private Broker

For better privacy and control, you can run your own MQTT broker:

  • Mosquitto (lightweight, open-source)
  • HiveMQ
  • EMQX

Configure your node to point to your private broker with appropriate credentials.

Map Reporting

When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.

Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.

Reports appear at meshmap.net and similar community map services.

🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published.

Direction Descrição
Uplink Messages from mesh → MQTT broker
Downlink Messages from MQTT broker → mesh

Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on.

Message Formats

MQTT carries two payload formats:

Format Descrição Use case
Protobuf Binary Meshtastic protobuf encoding Node-to-node mesh bridging
JSON Human-readable JSON on the /2/json/ topic Consumers outside the mesh (dashboards, home automation)

ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads.

Encryption & Privacy

Understanding the layered encryption model:

  1. Channel encryption happens on the mesh before MQTT. If your channel has a PSK, the MQTT payload is already encrypted — the broker and any subscribers see only the ciphertext.
  2. Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard.
  3. TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping.

🔒 Security: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications.

Best Practices

  • Use channel-level encryption (PSK) on channels that bridge to MQTT
  • Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes memory)
  • Use a private broker for sensitive deployments
  • Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh
  • Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back

Troubleshooting

MQTT Not Connecting

  • Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself.
  • Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces.
  • Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443).
  • DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly.

Messages Not Bridging

  • Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway.
  • Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage.
  • Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root.
  • Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway.
  • Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in.
+

A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh.

Configuração

Enabling MQTT

  1. Navigate to Settings → Module configuration → MQTT.
  2. Enable the MQTT module.
  3. Configure the broker connection:
Setting Descrição Predefinição
Address MQTT broker hostname mqtt.meshtastic.org
Username Broker authentication meshdev
Password Broker authentication large4cats
Root topic Base topic for messages msh, which the radio rewrites to msh/<REGION> once you set a region
Encryption enabled Encrypt MQTT payload Enabled
JSON output enabled Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it Disabled
TLS enabled Secure connection to broker Disabled
Map reporting Report position to public map Disabled
Proxy to client enabled Relay MQTT through the connected phone Disabled

Connection Status and Test Connection

The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here.

Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason.

MQTT Proxy on This Phone

If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection.

ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them.

The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration.

Default Meshtastic Broker

The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing.

When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without).

🔒 Privacy: Messages on the public broker are readable by anyone subscribed. Always use channel encryption for private communications.

Private Broker

For better privacy and control, you can run your own MQTT broker:

  • Mosquitto (lightweight, open-source)
  • HiveMQ
  • EMQX

Configure your node to point to your private broker with appropriate credentials.

Map Reporting

When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.

Turning it on opens a consent card. Turn on I agree. and choose a Map Publish Interval of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.

Reports appear at meshmap.net and similar community map services.

🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published.

Direction Descrição
Uplink Messages from mesh → MQTT broker
Downlink Messages from MQTT broker → mesh

Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on.

Message Formats

MQTT carries two payload formats:

Format Descrição Use case
Protobuf Binary Meshtastic protobuf encoding Node-to-node mesh bridging
JSON Human-readable JSON on the /2/json/ topic Consumers outside the mesh (dashboards, home automation)

ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads.

Encryption & Privacy

Understanding the layered encryption model:

  1. Channel encryption happens on the mesh before MQTT. If your channel has a PSK, the MQTT payload is already encrypted — the broker and any subscribers see only the ciphertext.
  2. Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard.
  3. TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping.

🔒 Security: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications.

Best Practices

  • Use channel-level encryption (PSK) on channels that bridge to MQTT
  • Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes memory)
  • Use a private broker for sensitive deployments
  • Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh
  • Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back

Troubleshooting

MQTT Not Connecting

  • Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself.
  • Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces.
  • Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443).
  • DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly.

Messages Not Bridging

  • Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway.
  • Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage.
  • Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root.
  • Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway.
  • Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in.
diff --git a/main/pt-rPT/user/settings-module-admin.html b/main/pt-rPT/user/settings-module-admin.html index b171ffa368..bb120947e3 100644 --- a/main/pt-rPT/user/settings-module-admin.html +++ b/main/pt-rPT/user/settings-module-admin.html @@ -1 +1 @@ - Settings — Modules & Admin | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Português
Meshtastic Docs ↗

🌐 Português — Community translation View in English

Settings — Modules & Admin

Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.

💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.

Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:

A toggle setting in the on position

A dropdown setting, expanded to show its list of options

A text field setting with a value entered

A module settings card with its title and grouped controls

Configurações dos módulos

Every module lives under Settings → Module configuration.

⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes.

MQTT module

Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.

Setting Descrição
MQTT ativo Toggle MQTT bridge
Endereço MQTT broker address
Utilizador Authentication username
Palavra-passe Authentication password
Encriptação ativada Encrypt MQTT payloads
Saída JSON ativada Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
Ativar TLS Use secure connection
Tópico principal Base MQTT topic path
Enviar através do cliente Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy on this phone The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT
Enviar para o mapa Publish position to the public map — see the Map reporting group that follows

Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:

Setting Descrição
Estou de acordo. Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Intervalo de envio (segundos) How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered

See MQTT for a detailed usage guide including encryption, privacy, and broker setup.

Serial module

Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.

Setting Descrição
Série ativada Activate serial communication
Eco ativado Echo received serial data back
Modo de série Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX GPIO pins for the serial connection
Taxa de transmissão série Port speed
Timeout How long to wait before considering an incoming message complete
Substituir porta série do console Take over the port the debug console normally uses

External Notification module

Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.

There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.

Setting Descrição
Ativar notificações externas Master toggle for the module
Alert message LED / buzzer / vibra Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra Which outputs fire on a received bell character
LED de Saída (GPIO) Pin the LED is wired to
LED de saída ativo alto Whether the LED pin is active high or low
Buzzer de saída (GPIO) Pin the buzzer is wired to
Vibra de saída (GPIO) Pin the vibration motor is wired to
Usar um buzzer PWM Drive the buzzer with PWM, which allows tones rather than a single pitch
Usar I2S como buzzer Send the alert through an I2S audio output instead
Duração da Saída (milissegundos) How long a single alert lasts
Tempo limite a incomodar (segundos) Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Toque The tone played on a PWM buzzer, in RTTTL. Can be imported from a file

Store & Forward module

Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.

Setting Descrição
Guardar & encaminhar ativo Activate store and forward
Batimento Periodically announce this node’s store-and-forward capability
Número de registos Maximum stored messages
History return max Max messages to replay
History return window Time window for replay
Servidor Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)

💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.

Range Test module

⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.

Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.

Setting Descrição
Ativar Teste de alcance Activate range testing
Sender message interval (seconds) Time between test transmissions, chosen from a dropdown of fixed intervals
Guardar .CSV no armazenamento (apenas ESP32) Log received test data to the node’s own filesystem. ESP32 hardware only

Telemetry module

Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).

Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.

Setting Descrição
Send Device Telemetry Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval How often to report battery, uptime and channel utilization
Módulo de métricas de ambiente ativado Report the attached environment sensors
Environment metrics update interval How often to report them
Mostrar métricas de ambiente no ecrã Also show these readings on the device’s own display
Métricas de Ambiente usam Fahrenheit Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Módulo de métricas de qualidade do ar ativado Report particulate and CO₂ sensor data
Air quality metrics update interval How often to report them
Módulo de métricas de energia ativado Report the per-channel voltage and current readings
Power metrics update interval How often to report them
Mostrar métricas de energia no ecrã Also show power readings on the device’s display

See Telemetry & Sensors for supported sensors and configuration recommendations.

Canned Message module

Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.

Setting Descrição
Canned message enabled ⚠️ Deprecated in the protobuf schema
Mensagens Newline-separated list of messages
Enviar sino Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Ativar Codificador rotativo #1 Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port The three pins the encoder is wired to
Generate input event on Press / CW / CCW Which key event each encoder action produces
Entrada Cima/Baixo/Selecionar ativa A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source ⚠️ Deprecated in the protobuf schema

Audio module

Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.

Setting Descrição
CODEC 2 ativado Activate audio module
Taxa de amostragem CODEC2 Audio quality/bandwidth tradeoff
Pin de PTT GPIO pin for the push-to-talk button
Selecionar palavra I2S GPIO pin for I2S WS
Entrada de dados I2S GPIO pin for I2S DIN
Saída de dados I2S GPIO pin for I2S DOUT
Relógio I2S GPIO pin for the I2S bit clock

ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.

Remote Hardware module

GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.

⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.

Setting Descrição
Hardware Remoto ativado Activate remote GPIO access
Permitir acesso indefinido ao pin Allow access to any GPIO pin (security risk)
Pins disponíveis Up to 4 GPIO pins this node exposes for remote read/write

Neighbor Info module

Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.

Setting Descrição
Enviar informações de vizinhos Activate neighbor broadcasting
Intervalo de atualização (segundos) How often to broadcast neighbor list
Enviar por LoRa Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name

See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.

Ambient Lighting module

Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.

Setting Descrição
Estado do LED Turn the LED on or off
Atual LED current limit (0–31)
Red / Green / Blue Individual color channel values (0–255)

Detection Sensor module

Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.

Setting Descrição
Sensor de deteção ativado Activate detection sensor
Pin GPIO para monitorizar GPIO pin connected to sensor
Tipo de gatilho de deteção How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Usar o modo INPUT_PULLUP Enable the pin’s internal pull-up resistor
Transmissão mínima (segundos) Minimum time between alert broadcasts
Transmissão de estado (segundos) Periodic state broadcast interval
Enviar sino com mensagem de alerta Include bell character in alerts
Nome amigável Custom name for this sensor

Paxcounter module

People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.

Setting Descrição
Ativar contador de pessoas Activate people counting
Intervalo de atualização (segundos) How often to report counts
Wi-Fi RSSI threshold Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE RSSI threshold The same cut-off for BLE advertisements (defaults to −80 dBm)

💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.

Status Message module

The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.

Mesh Beacon module

Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.

TAK module

Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.

Administração

Administração Remota

Remotely configure nodes that share your admin key:

  1. Select the target node in the node list.
  2. Navigate to Settings for that node.
  3. Modify configuration.
  4. Tap Save — changes are sent over the mesh.

⚠️ Important: Requires an admin key configured on both your node and the target node.

Device Actions

Settings → Administration holds five one-shot actions, each behind a confirmation dialog:

Action What it does
Set time Sends your phone’s clock to the node
Reiniciar Restarts the node
Desligar Powers the node down
Redefinição de fábrica Returns every setting to its factory default
Redefinir NodeDB Clears the node database. This dialog carries a Preserve Favorites? switch

⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.

Backup & Restauro

Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.

Advanced

Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.

Clean Node Database

Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.

  • Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
  • Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.

The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.

Painel de depuração

Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.

App Settings

The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:

Privacy

  • Allow analytics and crash reporting — opt in or out of diagnostics.
  • Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
  • Homoglyph encoding — how look-alike characters in names are handled.

Appearance

  • Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
  • Theme and Language.
  • Show full message timestamps.

Persistence

  • A cache limit for how much history is kept.
  • Export rangetest packets, Export all packets and Export node database.

On their own

  • Node Layout — how much detail each row of the node list shows.
  • Wi-Fi Provisioning for mPWRD-OS — see Connections.
  • Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
  • System AI — appears only where app functions are available; see App Functions.

A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.

Sobre

Settings → About carries the app’s own identity rather than the node’s:

Three sections:

  • What is Meshtastic? — a short description of the project.
  • Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
  • Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.

The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.

Acknowledgements

Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.

Troubleshooting remote admin

  • “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
  • Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
  • Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
+ Settings — Modules & Admin | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Português
Meshtastic Docs ↗

🌐 Português — Community translation View in English

Settings — Modules & Admin

Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.

💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.

Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:

A toggle setting in the on position

A dropdown setting, expanded to show its list of options

A text field setting with a value entered

A module settings card with its title and grouped controls

Configurações dos módulos

Every module lives under Settings → Module configuration.

⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes.

MQTT module

Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.

Setting Descrição
MQTT ativo Toggle MQTT bridge
Endereço MQTT broker address
Utilizador Authentication username
Palavra-passe Authentication password
Encriptação ativada Encrypt MQTT payloads
Saída JSON ativada Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
Ativar TLS Use secure connection
Tópico principal Base MQTT topic path
Enviar através do cliente Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy on this phone The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT
Enviar para o mapa Publish position to the public map — see the Map reporting group that follows

Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:

Setting Descrição
Estou de acordo. Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered

See MQTT for a detailed usage guide including encryption, privacy, and broker setup.

Serial module

Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.

Setting Descrição
Série ativada Activate serial communication
Eco ativado Echo received serial data back
Modo de série Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX GPIO pins for the serial connection
Taxa de transmissão série Port speed
Timeout How long to wait before considering an incoming message complete
Substituir porta série do console Take over the port the debug console normally uses

External Notification module

Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.

There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.

Setting Descrição
Ativar notificações externas Master toggle for the module
Alert message LED / buzzer / vibra Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra Which outputs fire on a received bell character
LED de Saída (GPIO) Pin the LED is wired to
LED de saída ativo alto Whether the LED pin is active high or low
Buzzer de saída (GPIO) Pin the buzzer is wired to
Vibra de saída (GPIO) Pin the vibration motor is wired to
Usar um buzzer PWM Drive the buzzer with PWM, which allows tones rather than a single pitch
Usar I2S como buzzer Send the alert through an I2S audio output instead
GPIO Output Duration How long a single alert lasts
Nag Timeout Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Toque The tone played on a PWM buzzer, in RTTTL. Can be imported from a file

Store & Forward module

Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.

Setting Descrição
Guardar & encaminhar ativo Activate store and forward
Batimento Periodically announce this node’s store-and-forward capability
Número de registos Maximum stored messages
History return max Max messages to replay
History return window Time window for replay
Servidor Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)

💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.

Range Test module

⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.

Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.

Setting Descrição
Ativar Teste de alcance Activate range testing
Sender Interval Time between test transmissions, chosen from a dropdown of fixed intervals
Guardar .CSV no armazenamento (apenas ESP32) Log received test data to the node’s own filesystem. ESP32 hardware only

Telemetry module

Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).

Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.

Setting Descrição
Send Device Telemetry Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval How often to report battery, uptime and channel utilization
Módulo de métricas de ambiente ativado Report the attached environment sensors
Environment metrics update interval How often to report them
Mostrar métricas de ambiente no ecrã Also show these readings on the device’s own display
Métricas de Ambiente usam Fahrenheit Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Módulo de métricas de qualidade do ar ativado Report particulate and CO₂ sensor data
Air quality metrics update interval How often to report them
Módulo de métricas de energia ativado Report the per-channel voltage and current readings
Power metrics update interval How often to report them
Mostrar métricas de energia no ecrã Also show power readings on the device’s display

See Telemetry & Sensors for supported sensors and configuration recommendations.

Canned Message module

Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.

Setting Descrição
Canned message enabled ⚠️ Deprecated in the protobuf schema
Mensagens Newline-separated list of messages
Enviar sino Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Ativar Codificador rotativo #1 Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port The three pins the encoder is wired to
Generate input event on Press / CW / CCW Which key event each encoder action produces
Entrada Cima/Baixo/Selecionar ativa A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source ⚠️ Deprecated in the protobuf schema

Audio module

Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.

Setting Descrição
CODEC 2 ativado Activate audio module
Taxa de amostragem CODEC2 Audio quality/bandwidth tradeoff
Pin de PTT GPIO pin for the push-to-talk button
Selecionar palavra I2S GPIO pin for I2S WS
Entrada de dados I2S GPIO pin for I2S DIN
Saída de dados I2S GPIO pin for I2S DOUT
Relógio I2S GPIO pin for the I2S bit clock

ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.

Remote Hardware module

GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.

⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.

Setting Descrição
Hardware Remoto ativado Activate remote GPIO access
Permitir acesso indefinido ao pin Allow access to any GPIO pin (security risk)
Pins disponíveis Up to 4 GPIO pins this node exposes for remote read/write

Neighbor Info module

Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.

Setting Descrição
Enviar informações de vizinhos Activate neighbor broadcasting
Intervalo de Atualização How often to broadcast neighbor list
Enviar por LoRa Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name

See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.

Ambient Lighting module

Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.

Setting Descrição
Estado do LED Turn the LED on or off
Atual LED current limit (0–31)
Red / Green / Blue Individual color channel values (0–255)

Detection Sensor module

Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.

Setting Descrição
Sensor de deteção ativado Activate detection sensor
Pin GPIO para monitorizar GPIO pin connected to sensor
Tipo de gatilho de deteção How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Usar o modo INPUT_PULLUP Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts Minimum time between alert broadcasts
State Broadcast Interval Periodic state broadcast interval
Enviar sino com mensagem de alerta Include bell character in alerts
Nome amigável Custom name for this sensor

Paxcounter module

People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.

Setting Descrição
Ativar contador de pessoas Activate people counting
Intervalo de Atualização How often to report counts
WiFi Threshold (dBm) Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm) The same cut-off for BLE advertisements (defaults to −80 dBm)

💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.

Status Message module

The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.

Mesh Beacon module

Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.

TAK module

Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.

Administração

Administração Remota

Remotely configure nodes that share your admin key:

  1. Select the target node in the node list.
  2. Navigate to Settings for that node.
  3. Modify configuration.
  4. Tap Save — changes are sent over the mesh.

⚠️ Important: Requires an admin key configured on both your node and the target node.

Device Actions

Settings → Administration holds five one-shot actions, each behind a confirmation dialog:

Action What it does
Set time Sends your phone’s clock to the node
Reiniciar Restarts the node
Desligar Powers the node down
Redefinição de fábrica Returns every setting to its factory default
Redefinir NodeDB Clears the node database. This dialog carries a Preserve Favorites? switch

⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.

Backup & Restauro

Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.

Advanced

Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.

Clean Node Database

Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.

  • Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
  • Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.

The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.

Painel de depuração

Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.

App Settings

The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:

Privacy

  • Allow analytics and crash reporting — opt in or out of diagnostics.
  • Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
  • Homoglyph encoding — how look-alike characters in names are handled.

Appearance

  • Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
  • Theme and Language.
  • Show full message timestamps.

Persistence

  • A cache limit for how much history is kept.
  • Export rangetest packets, Export all packets and Export node database.

On their own

  • Node Layout — how much detail each row of the node list shows.
  • Wi-Fi Provisioning for mPWRD-OS — see Connections.
  • Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
  • System AI — appears only where app functions are available; see App Functions.

A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.

Sobre

Settings → About carries the app’s own identity rather than the node’s:

Three sections:

  • What is Meshtastic? — a short description of the project.
  • Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
  • Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.

The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.

Acknowledgements

Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.

Troubleshooting remote admin

  • “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
  • Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
  • Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
diff --git a/main/pt-rPT/user/settings-radio-user.html b/main/pt-rPT/user/settings-radio-user.html index cd467231cd..dee7f32d5f 100644 --- a/main/pt-rPT/user/settings-radio-user.html +++ b/main/pt-rPT/user/settings-radio-user.html @@ -1 +1 @@ - Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Português
Meshtastic Docs ↗

🌐 Português — Community translation View in English

Settings — Radio & User

Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How these screens work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Descrição
Long Name Your display name (up to 39 characters)
Short Name 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Impossível enviar mensagens Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur node (Ham) Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in.

Configuração

Configuração do Dispositivo

On Settings → Device configuration → Device.

Setting Descrição Predefinição
Device Role Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Rebroadcast Mode How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Node Info Broadcast Interval How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Double Tap as Button Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Enabled
LED Heartbeat Blink the status LED periodically Enabled
Time Zone POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it —
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to —

Configuração de LoRa

On Settings → LoRa.

Setting Descrição Predefinição
Região Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number Unset (must configure)
Presets Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Transmit Power Transmission power (dBm); 0 = max allowed for region 0 (region max)
Frequency Override Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Use Preset On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead From preset
Coding Rate Manual mode only: 5–8. More redundancy costs airtime From preset
Largura de banda Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Frequency Slot Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmit Enabled Turning this off makes the node receive-only On
Ignorar ciclo de trabalho Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
Ignorar MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok to MQTT Allow your packets to be forwarded to MQTT by gateways Off
RX Boosted Gain Extra receive gain on SX126x radios; costs a little current Off
PA fan disabled Turn off the power-amplifier fan on hardware that has one Off

The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set.

Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Speed SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a modem preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Configuração do Ecrã

On Settings → Device configuration → Display. These control the node’s own screen, not the app’s.

Setting Descrição
Screen on for How long the display stays lit before sleeping
Carousel interval How often the node cycles between screens on its own
Modo de visualização Screen layout/density used by the firmware
Unidade de visualização Metric or Imperial on the node’s screen
Usar formato de relógio 12h Show the node’s clock as 12-hour rather than 24-hour
Bold Heading Draw the screen’s heading text in bold
Inverter ecrã Rotate the display 180° for an inverted mounting
OLED type Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED
Wake on tap or motion Light the screen when the node is tapped or moved
Orientação da bússola Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each
Always point north Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Configuração da posição

On Settings → Device configuration → Position.

Setting Descrição
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the node asks its GPS for a fix
Intervalo de difusão How often the position is shared with the mesh
Posição Inteligente Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Posição fixa Use a manually entered latitude, longitude and altitude instead of the GPS
Position Flags A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Configuração de Energia

On Settings → Device configuration → Power.

Setting Descrição
Ativar modo de poupança de energia Let the node sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the node stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
Alterar rácio do multiplicador ADC The correction factor itself, used only when the override is on
Endereço I2C da bateria INA_2XX Address of an external INA-series power sensor, if fitted

Configuração de Rede

On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node.

Setting Descrição
Wi-Fi enabled Enable the Wi-Fi node (ESP32 nodes)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Palavra-passe Network password
Ethernet ativada Use a wired connection on hardware that has one
Modo IPv4 DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
Servidor NTP Time synchronization server
servidor rsyslog Remote logging server

Network Config with a static IPv4 address entered

Configuração de Bluetooth

On Settings → Device configuration → Bluetooth, on nodes with Bluetooth.

Setting Descrição
Bluetooth ativado Enable/disable BLE radio
Modo de emparelhamento Fixed PIN, Random PIN, or No PIN
PIN fixo PIN code for pairing. Must be exactly six digits — the field rejects anything else

Configuração de Segurança

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

Setting Descrição
Chave pública Your node’s public key (read-only)
Chave do Administrador Keys permitted to administer this node remotely — up to three
Chave privada Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it
Regenerate Private Key Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Consola de série Serial console over the Stream API
API de histórico de depuração ativada Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth
Modo Administrado Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.

+ Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Português
Meshtastic Docs ↗

🌐 Português — Community translation View in English

Settings — Radio & User

Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How these screens work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Descrição
Long Name Your display name (up to 39 characters)
Short Name 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Impossível enviar mensagens Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur node (Ham) Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in.

Configuração

Configuração do Dispositivo

On Settings → Device configuration → Device.

Setting Descrição Predefinição
Device Role Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Rebroadcast Mode How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Node Info Broadcast Interval How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Double Tap as Button Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Enabled
LED Heartbeat Blink the status LED periodically Enabled
Time Zone POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it —
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to —

Configuração de LoRa

On Settings → LoRa.

Setting Descrição Predefinição
Região Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number Unset (must configure)
Presets Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Transmit Power (dBm) Transmission power; 0 = max allowed for region 0 (region max)
Frequency Override Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Use Preset On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead From preset
Coding Rate Manual mode only: 5–8. More redundancy costs airtime From preset
Largura de banda Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Frequency Slot Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmit Enabled Turning this off makes the node receive-only On
Ignorar ciclo de trabalho Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
Ignorar MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok to MQTT Allow your packets to be forwarded to MQTT by gateways Off
RX Boosted Gain Extra receive gain on SX126x radios; costs a little current Off
PA fan disabled Turn off the power-amplifier fan on hardware that has one Off

The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set.

Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Speed SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a modem preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Configuração do Ecrã

On Settings → Device configuration → Display. These control the node’s own screen, not the app’s.

Setting Descrição
Screen on for How long the display stays lit before sleeping
Carousel interval How often the node cycles between screens on its own
Modo de visualização Screen layout/density used by the firmware
Unidade de visualização Metric or Imperial on the node’s screen
Usar formato de relógio 12h Show the node’s clock as 12-hour rather than 24-hour
Bold Heading Draw the screen’s heading text in bold
Inverter ecrã Rotate the display 180° for an inverted mounting
OLED type Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED
Wake on tap or motion Light the screen when the node is tapped or moved
Orientação da bússola Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each
Always point north Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Configuração da posição

On Settings → Device configuration → Position.

Setting Descrição
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the node asks its GPS for a fix
Intervalo de difusão How often the position is shared with the mesh
Posição Inteligente Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Posição fixa Use a manually entered latitude, longitude and altitude instead of the GPS
Position Flags A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Configuração de Energia

On Settings → Device configuration → Power.

Setting Descrição
Ativar modo de poupança de energia Let the node sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the node stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
Alterar rácio do multiplicador ADC The correction factor itself, used only when the override is on
Endereço I2C da bateria INA_2XX Address of an external INA-series power sensor, if fitted

Configuração de Rede

On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node.

Setting Descrição
Wi-Fi enabled Enable the Wi-Fi node (ESP32 nodes)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Palavra-passe Network password
Ethernet ativada Use a wired connection on hardware that has one
Modo IPv4 DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
Servidor NTP Time synchronization server
servidor rsyslog Remote logging server

Network Config with a static IPv4 address entered

Configuração de Bluetooth

On Settings → Device configuration → Bluetooth, on nodes with Bluetooth.

Setting Descrição
Bluetooth ativado Enable/disable BLE radio
Modo de emparelhamento Fixed PIN, Random PIN, or No PIN
PIN fixo PIN code for pairing. Must be exactly six digits — the field rejects anything else

Configuração de Segurança

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

Setting Descrição
Chave pública Your node’s public key (read-only)
Chave do Administrador Keys permitted to administer this node remotely — up to three
Chave privada Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it
Regenerate Private Key Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Consola de série Serial console over the Stream API
API de histórico de depuração ativada Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth
Modo Administrado Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.

diff --git a/main/ro-rRO/user/discovery.html b/main/ro-rRO/user/discovery.html index d6f0e898f1..48578aeb26 100644 --- a/main/ro-rRO/user/discovery.html +++ b/main/ro-rRO/user/discovery.html @@ -5,4 +5,4 @@ ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) -

Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:.

What to look for What it means
All hops show Good SNR (green) Healthy path — messages flow reliably
One hop shows a poor SNR (orange or red) Weak link — this relay segment is fragile
Many hops (4+) Long path — consider repositioning a node to shorten it
Different path on retry Mesh is adapting — multiple routes exist (this is good!)

💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network.

Troubleshooting with Traceroute

  • No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key.
  • Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa.
  • Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position.
  • Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric.

Informații vecin

The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh.

Enabling Neighbor Info

  1. Navigate to Settings → Module configuration → Neighbor Info.
  2. Enable the module.
  3. Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
  4. Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air.

Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.

Viewing neighbor data

  • Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors.
  • Each neighbor entry shows the node that was directly heard and its signal quality.
  • Combine neighbor data from multiple nodes to understand the full mesh topology.

ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further.

Node list as a discovery tool

The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively.

Finding new nodes

  • Sort by Last heard to see the most recently active nodes at the top.
  • Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes.

Assessing connectivity

  • Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed.
  • Sort by Distance to find nearby nodes and verify they’re reachable.
  • Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge).

Infrastructure audit

  • Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes.
  • Check their signal quality and last-heard times to verify your infrastructure nodes are healthy.

See Nodes for full details on filtering and sorting options.

Tips for Mesh exploration

  • Start with traceroute — it gives you immediate, actionable information about a specific path.
  • Enable Neighbor Info on key nodes — especially routers and repeaters, to build a picture of the backbone.
  • Check the map — node positions on the Map combined with signal data help you understand why some links are strong and others are weak.
  • Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly.
+

Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:.

What to look for What it means
All hops show Good SNR (green) Healthy path — messages flow reliably
One hop shows a poor SNR (orange or red) Weak link — this relay segment is fragile
Many hops (4+) Long path — consider repositioning a node to shorten it
Different path on retry Mesh is adapting — multiple routes exist (this is good!)

💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network.

Troubleshooting with Traceroute

  • No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key.
  • Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa.
  • Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position.
  • Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric.

Informații vecin

The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh.

Enabling Neighbor Info

  1. Navigate to Settings → Module configuration → Neighbor Info.
  2. Enable the module.
  3. Set Update Interval. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
  4. Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air.

Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.

Viewing neighbor data

  • Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors.
  • Each neighbor entry shows the node that was directly heard and its signal quality.
  • Combine neighbor data from multiple nodes to understand the full mesh topology.

ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further.

Node list as a discovery tool

The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively.

Finding new nodes

  • Sort by Last heard to see the most recently active nodes at the top.
  • Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes.

Assessing connectivity

  • Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed.
  • Sort by Distance to find nearby nodes and verify they’re reachable.
  • Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge).

Infrastructure audit

  • Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes.
  • Check their signal quality and last-heard times to verify your infrastructure nodes are healthy.

See Nodes for full details on filtering and sorting options.

Tips for Mesh exploration

  • Start with traceroute — it gives you immediate, actionable information about a specific path.
  • Enable Neighbor Info on key nodes — especially routers and repeaters, to build a picture of the backbone.
  • Check the map — node positions on the Map combined with signal data help you understand why some links are strong and others are weak.
  • Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly.
diff --git a/main/ro-rRO/user/mqtt.html b/main/ro-rRO/user/mqtt.html index 6a518be734..cfc76d7857 100644 --- a/main/ro-rRO/user/mqtt.html +++ b/main/ro-rRO/user/mqtt.html @@ -1,2 +1,2 @@ MQTT | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Română
Meshtastic Docs ↗

🌐 Română — Community translation View in English

MQTT

MQTT bridges your Meshtastic mesh network to the internet, enabling long-range communication beyond radio range.

Overview

The MQTT module connects your node to an MQTT broker, allowing:

  • Messages to reach nodes on different physical meshes via the internet
  • Integration with home automation and monitoring systems
  • Publishing node positions to the public Meshtastic map
  • Custom data pipelines for logging and alerting

How It Works 

[Your Node] → Radio → [Gateway Node with Wi-Fi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node]
-

A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh.

Configuration

Enabling MQTT

  1. Navigate to Settings → Module configuration → MQTT.
  2. Enable the MQTT module.
  3. Configure the broker connection:
Setting Descriere Prestabilit
Address MQTT broker hostname mqtt.meshtastic.org
Username Broker authentication meshdev
Password Broker authentication large4cats
Root topic Base topic for messages msh, which the radio rewrites to msh/<REGION> once you set a region
Encryption enabled Encrypt MQTT payload Activat
JSON output enabled Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it Disabled
TLS enabled Secure connection to broker Disabled
Map reporting Report position to public map Disabled
Proxy to client enabled Relay MQTT through the connected phone Disabled

Connection Status and Test Connection

The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here.

Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason.

MQTT Proxy on This Phone

If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection.

ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them.

The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration.

Default Meshtastic Broker

The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing.

When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without).

🔒 Privacy: Messages on the public broker are readable by anyone subscribed. Always use channel encryption for private communications.

Private Broker

For better privacy and control, you can run your own MQTT broker:

  • Mosquitto (lightweight, open-source)
  • HiveMQ
  • EMQX

Configure your node to point to your private broker with appropriate credentials.

Map Reporting

When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.

Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.

Reports appear at meshmap.net and similar community map services.

🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published.

Direction Descriere
Uplink Messages from mesh → MQTT broker
Downlink Messages from MQTT broker → mesh

Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on.

Message Formats

MQTT carries two payload formats:

Format Descriere Use case
Protobuf Binary Meshtastic protobuf encoding Node-to-node mesh bridging
JSON Human-readable JSON on the /2/json/ topic Consumers outside the mesh (dashboards, home automation)

ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads.

Encryption & Privacy

Understanding the layered encryption model:

  1. Channel encryption happens on the mesh before MQTT. If your channel has a PSK, the MQTT payload is already encrypted — the broker and any subscribers see only the ciphertext.
  2. Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard.
  3. TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping.

🔒 Security: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications.

Best Practices

  • Use channel-level encryption (PSK) on channels that bridge to MQTT
  • Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes memory)
  • Use a private broker for sensitive deployments
  • Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh
  • Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back

Troubleshooting

MQTT Not Connecting

  • Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself.
  • Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces.
  • Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443).
  • DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly.

Messages Not Bridging

  • Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway.
  • Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage.
  • Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root.
  • Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway.
  • Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in.
+

A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh.

Configuration

Enabling MQTT

  1. Navigate to Settings → Module configuration → MQTT.
  2. Enable the MQTT module.
  3. Configure the broker connection:
Setting Descriere Prestabilit
Address MQTT broker hostname mqtt.meshtastic.org
Username Broker authentication meshdev
Password Broker authentication large4cats
Root topic Base topic for messages msh, which the radio rewrites to msh/<REGION> once you set a region
Encryption enabled Encrypt MQTT payload Activat
JSON output enabled Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it Disabled
TLS enabled Secure connection to broker Disabled
Map reporting Report position to public map Disabled
Proxy to client enabled Relay MQTT through the connected phone Disabled

Connection Status and Test Connection

The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here.

Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason.

MQTT Proxy on This Phone

If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection.

ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them.

The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration.

Default Meshtastic Broker

The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing.

When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without).

🔒 Privacy: Messages on the public broker are readable by anyone subscribed. Always use channel encryption for private communications.

Private Broker

For better privacy and control, you can run your own MQTT broker:

  • Mosquitto (lightweight, open-source)
  • HiveMQ
  • EMQX

Configure your node to point to your private broker with appropriate credentials.

Map Reporting

When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.

Turning it on opens a consent card. Turn on I agree. and choose a Map Publish Interval of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.

Reports appear at meshmap.net and similar community map services.

🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published.

Direction Descriere
Uplink Messages from mesh → MQTT broker
Downlink Messages from MQTT broker → mesh

Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on.

Message Formats

MQTT carries two payload formats:

Format Descriere Use case
Protobuf Binary Meshtastic protobuf encoding Node-to-node mesh bridging
JSON Human-readable JSON on the /2/json/ topic Consumers outside the mesh (dashboards, home automation)

ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads.

Encryption & Privacy

Understanding the layered encryption model:

  1. Channel encryption happens on the mesh before MQTT. If your channel has a PSK, the MQTT payload is already encrypted — the broker and any subscribers see only the ciphertext.
  2. Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard.
  3. TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping.

🔒 Security: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications.

Best Practices

  • Use channel-level encryption (PSK) on channels that bridge to MQTT
  • Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes memory)
  • Use a private broker for sensitive deployments
  • Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh
  • Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back

Troubleshooting

MQTT Not Connecting

  • Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself.
  • Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces.
  • Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443).
  • DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly.

Messages Not Bridging

  • Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway.
  • Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage.
  • Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root.
  • Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway.
  • Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in.
diff --git a/main/ro-rRO/user/settings-module-admin.html b/main/ro-rRO/user/settings-module-admin.html index 3f63ca7a0c..4de9efcce7 100644 --- a/main/ro-rRO/user/settings-module-admin.html +++ b/main/ro-rRO/user/settings-module-admin.html @@ -1 +1 @@ - Settings — Modules & Admin | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Română
Meshtastic Docs ↗

🌐 Română — Community translation View in English

Settings — Modules & Admin

Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.

💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.

Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:

A toggle setting in the on position

A dropdown setting, expanded to show its list of options

A text field setting with a value entered

A module settings card with its title and grouped controls

Configurare modul

Every module lives under Settings → Module configuration.

⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes.

MQTT module

Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.

Setting Descriere
MQTT activat Toggle MQTT bridge
Adresă MQTT broker address
Nume de utilizator Authentication username
Parolă Authentication password
Criptare activată Encrypt MQTT payloads
Ieșire JSON activată Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS activat Use secure connection
Temă rădăcină Base MQTT topic path
Proxy-ul pentru client activat Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy on this phone The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT
Raportarea hărții Publish position to the public map — see the Map reporting group that follows

Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:

Setting Descriere
Sunt de acord Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Intervalul de raportare hartă (secunde) How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered

See MQTT for a detailed usage guide including encryption, privacy, and broker setup.

Serial module

Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.

Setting Descriere
Serial activat Activate serial communication
Echo activat Echo received serial data back
Mod serial Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX GPIO pins for the serial connection
Rata baud-ului serial Port speed
Expirat How long to wait before considering an incoming message complete
Suprascrie portul serial al consolei Take over the port the debug console normally uses

External Notification module

Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.

There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.

Setting Descriere
Notificare externă activată Master toggle for the module
Alert message LED / buzzer / vibra Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra Which outputs fire on a received bell character
LED ieșire (GPIO) Pin the LED is wired to
LED de ieșire activ ridicat Whether the LED pin is active high or low
Buzzer ieșire (GPIO) Pin the buzzer is wired to
Ieșire vibrație (GPIO) Pin the vibration motor is wired to
Utilizează buzzer PWM Drive the buzzer with PWM, which allows tones rather than a single pitch
Utilizează I2S ca buzzer Send the alert through an I2S audio output instead
Durată ieșire (milisecunde) How long a single alert lasts
Durată notificare (secunde) Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Sonerie The tone played on a PWM buzzer, in RTTTL. Can be imported from a file

Store & Forward module

Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.

Setting Descriere
Reținere și redirecționare activată Activate store and forward
Puls Periodically announce this node’s store-and-forward capability
Numarul de inregistrari Maximum stored messages
istoric număr maxim de retur Max messages to replay
Fereastra de returnare a istoricului Time window for replay
Server Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)

💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.

Range Test module

⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.

Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.

Setting Descriere
Testul de gamă activat Activate range testing
Interval mesaj expeditor (secunde) Time between test transmissions, chosen from a dropdown of fixed intervals
Salvați .CSV doar în memorie (ESP32) Log received test data to the node’s own filesystem. ESP32 hardware only

Telemetry module

Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).

Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.

Setting Descriere
Trimite telemetrie dispozitiv Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Intervalul de actualizare a parametrilor dispozitivului How often to report battery, uptime and channel utilization
Modul de măsurare mediu activat Report the attached environment sensors
Interval actualizare valori mediu How often to report them
Valorile de mediu pe ecran sunt activate Also show these readings on the device’s own display
Valorile de mediu utilizează Fahrenheit Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Air quality metrics module enabled Report particulate and CO₂ sensor data
Interval actualizare măsurători de calitate a aerului How often to report them
Modul de măsurare putere activat Report the per-channel voltage and current readings
Interval actualizare măsurători de putere How often to report them
Valori pe ecran activate Also show power readings on the device’s display

See Telemetry & Sensors for supported sensors and configuration recommendations.

Canned Message module

Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.

Setting Descriere
Canned message enabled ⚠️ Deprecated in the protobuf schema
Mesaje Newline-separated list of messages
Trimite clopoțel Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Encoder rotativ #1 activat Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port The three pins the encoder is wired to
Generate input event on Press / CW / CCW Which key event each encoder action produces
Intrare sus/jos/selectare activată A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source ⚠️ Deprecated in the protobuf schema

Audio module

Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.

Setting Descriere
CODEC 2 activat Activate audio module
Rată de eșantionare CODEC2 Audio quality/bandwidth tradeoff
Pin PTT GPIO pin for the push-to-talk button
Selectare cuvânt I2S GPIO pin for I2S WS
Intrare date I2S GPIO pin for I2S DIN
Ieșire date I2S GPIO pin for I2S DOUT
Ceas I2S GPIO pin for the I2S bit clock

ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.

Remote Hardware module

GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.

⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.

Setting Descriere
Hardware extern activat Activate remote GPIO access
Permite acces Pin nedefinit Allow access to any GPIO pin (security risk)
Pin-uri disponibile Up to 4 GPIO pins this node exposes for remote read/write

Neighbor Info module

Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.

Setting Descriere
Info vecin activat Activate neighbor broadcasting
Interval de actualizare (secunde) How often to broadcast neighbor list
Transmite peste LoRA Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name

See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.

Ambient Lighting module

Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.

Setting Descriere
Stare LED Turn the LED on or off
Actual LED current limit (0–31)
Red / Green / Blue Individual color channel values (0–255)

Detection Sensor module

Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.

Setting Descriere
Senzor detectare activat Activate detection sensor
Pin GPIO de monitorizat GPIO pin connected to sensor
Tip declanșator detectare How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Folosește modul INPUT_PULLUP Enable the pin’s internal pull-up resistor
Difuzare minimă (secunde) Minimum time between alert broadcasts
Difuzare stare (secunde) Periodic state broadcast interval
Trimite clopoțelul cu mesaj de alertă Include bell character in alerts
Nume comun Custom name for this sensor

Paxcounter module

People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.

Setting Descriere
Paxcounter activat Activate people counting
Interval de actualizare (secunde) How often to report counts
Wi-Fi RSSI threshold Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE RSSI threshold The same cut-off for BLE advertisements (defaults to −80 dBm)

💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.

Status Message module

The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.

Mesh Beacon module

Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.

TAK module

Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.

Administrare

Administrare la distanță

Remotely configure nodes that share your admin key:

  1. Select the target node in the node list.
  2. Navigate to Settings for that node.
  3. Modify configuration.
  4. Tap Save — changes are sent over the mesh.

⚠️ Important: Requires an admin key configured on both your node and the target node.

Device Actions

Settings → Administration holds five one-shot actions, each behind a confirmation dialog:

Action What it does
Set time Sends your phone’s clock to the node
Restartează Restarts the node
Oprire Powers the node down
Resetare la setările din fabrică Returns every setting to its factory default
Resetare NodeDB Clears the node database. This dialog carries a Preserve Favorites? switch

⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.

Copie de rezervă și restaurare

Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.

Avansate

Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.

Curăță baza de date a nodurilor

Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.

  • Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
  • Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.

The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.

Panou de depanare

Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.

App Settings

The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:

Privacy

  • Allow analytics and crash reporting — opt in or out of diagnostics.
  • Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
  • Homoglyph encoding — how look-alike characters in names are handled.

Appearance

  • Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
  • Theme and Language.
  • Show full message timestamps.

Persistence

  • A cache limit for how much history is kept.
  • Export rangetest packets, Export all packets and Export node database.

On their own

  • Node Layout — how much detail each row of the node list shows.
  • Wi-Fi Provisioning for mPWRD-OS — see Connections.
  • Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
  • System AI — appears only where app functions are available; see App Functions.

A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.

Despre

Settings → About carries the app’s own identity rather than the node’s:

Three sections:

  • What is Meshtastic? — a short description of the project.
  • Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
  • Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.

The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.

Mulțumiri

Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.

Troubleshooting remote admin

  • “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
  • Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
  • Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
+ Settings — Modules & Admin | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Română
Meshtastic Docs ↗

🌐 Română — Community translation View in English

Settings — Modules & Admin

Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.

💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.

Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:

A toggle setting in the on position

A dropdown setting, expanded to show its list of options

A text field setting with a value entered

A module settings card with its title and grouped controls

Configurare modul

Every module lives under Settings → Module configuration.

⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes.

MQTT module

Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.

Setting Descriere
MQTT activat Toggle MQTT bridge
Adresă MQTT broker address
Nume de utilizator Authentication username
Parolă Authentication password
Criptare activată Encrypt MQTT payloads
Ieșire JSON activată Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS activat Use secure connection
Temă rădăcină Base MQTT topic path
Proxy-ul pentru client activat Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy on this phone The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT
Raportarea hărții Publish position to the public map — see the Map reporting group that follows

Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:

Setting Descriere
Sunt de acord Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered

See MQTT for a detailed usage guide including encryption, privacy, and broker setup.

Serial module

Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.

Setting Descriere
Serial activat Activate serial communication
Echo activat Echo received serial data back
Mod serial Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX GPIO pins for the serial connection
Rata baud-ului serial Port speed
Expirat How long to wait before considering an incoming message complete
Suprascrie portul serial al consolei Take over the port the debug console normally uses

External Notification module

Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.

There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.

Setting Descriere
Notificare externă activată Master toggle for the module
Alert message LED / buzzer / vibra Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra Which outputs fire on a received bell character
LED ieșire (GPIO) Pin the LED is wired to
LED de ieșire activ ridicat Whether the LED pin is active high or low
Buzzer ieșire (GPIO) Pin the buzzer is wired to
Ieșire vibrație (GPIO) Pin the vibration motor is wired to
Utilizează buzzer PWM Drive the buzzer with PWM, which allows tones rather than a single pitch
Utilizează I2S ca buzzer Send the alert through an I2S audio output instead
GPIO Output Duration How long a single alert lasts
Nag Timeout Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Sonerie The tone played on a PWM buzzer, in RTTTL. Can be imported from a file

Store & Forward module

Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.

Setting Descriere
Reținere și redirecționare activată Activate store and forward
Puls Periodically announce this node’s store-and-forward capability
Numarul de inregistrari Maximum stored messages
istoric număr maxim de retur Max messages to replay
Fereastra de returnare a istoricului Time window for replay
Server Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)

💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.

Range Test module

⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.

Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.

Setting Descriere
Testul de gamă activat Activate range testing
Sender Interval Time between test transmissions, chosen from a dropdown of fixed intervals
Salvați .CSV doar în memorie (ESP32) Log received test data to the node’s own filesystem. ESP32 hardware only

Telemetry module

Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).

Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.

Setting Descriere
Trimite telemetrie dispozitiv Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Intervalul de actualizare a parametrilor dispozitivului How often to report battery, uptime and channel utilization
Modul de măsurare mediu activat Report the attached environment sensors
Interval actualizare valori mediu How often to report them
Valorile de mediu pe ecran sunt activate Also show these readings on the device’s own display
Valorile de mediu utilizează Fahrenheit Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Air quality metrics module enabled Report particulate and CO₂ sensor data
Interval actualizare măsurători de calitate a aerului How often to report them
Modul de măsurare putere activat Report the per-channel voltage and current readings
Interval actualizare măsurători de putere How often to report them
Valori pe ecran activate Also show power readings on the device’s display

See Telemetry & Sensors for supported sensors and configuration recommendations.

Canned Message module

Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.

Setting Descriere
Canned message enabled ⚠️ Deprecated in the protobuf schema
Mesaje Newline-separated list of messages
Trimite clopoțel Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Encoder rotativ #1 activat Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port The three pins the encoder is wired to
Generate input event on Press / CW / CCW Which key event each encoder action produces
Intrare sus/jos/selectare activată A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source ⚠️ Deprecated in the protobuf schema

Audio module

Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.

Setting Descriere
CODEC 2 activat Activate audio module
Rată de eșantionare CODEC2 Audio quality/bandwidth tradeoff
Pin PTT GPIO pin for the push-to-talk button
Selectare cuvânt I2S GPIO pin for I2S WS
Intrare date I2S GPIO pin for I2S DIN
Ieșire date I2S GPIO pin for I2S DOUT
Ceas I2S GPIO pin for the I2S bit clock

ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.

Remote Hardware module

GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.

⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.

Setting Descriere
Hardware extern activat Activate remote GPIO access
Permite acces Pin nedefinit Allow access to any GPIO pin (security risk)
Pin-uri disponibile Up to 4 GPIO pins this node exposes for remote read/write

Neighbor Info module

Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.

Setting Descriere
Info vecin activat Activate neighbor broadcasting
Interval de actualizare GPS How often to broadcast neighbor list
Transmite peste LoRA Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name

See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.

Ambient Lighting module

Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.

Setting Descriere
Stare LED Turn the LED on or off
Actual LED current limit (0–31)
Red / Green / Blue Individual color channel values (0–255)

Detection Sensor module

Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.

Setting Descriere
Senzor detectare activat Activate detection sensor
Pin GPIO de monitorizat GPIO pin connected to sensor
Tip declanșator detectare How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Folosește modul INPUT_PULLUP Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts Minimum time between alert broadcasts
State Broadcast Interval Periodic state broadcast interval
Trimite clopoțelul cu mesaj de alertă Include bell character in alerts
Nume comun Custom name for this sensor

Paxcounter module

People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.

Setting Descriere
Paxcounter activat Activate people counting
Interval de actualizare GPS How often to report counts
WiFi Threshold (dBm) Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm) The same cut-off for BLE advertisements (defaults to −80 dBm)

💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.

Status Message module

The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.

Mesh Beacon module

Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.

TAK module

Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.

Administrare

Administrare la distanță

Remotely configure nodes that share your admin key:

  1. Select the target node in the node list.
  2. Navigate to Settings for that node.
  3. Modify configuration.
  4. Tap Save — changes are sent over the mesh.

⚠️ Important: Requires an admin key configured on both your node and the target node.

Device Actions

Settings → Administration holds five one-shot actions, each behind a confirmation dialog:

Action What it does
Set time Sends your phone’s clock to the node
Restartează Restarts the node
Oprire Powers the node down
Resetare la setările din fabrică Returns every setting to its factory default
Resetare NodeDB Clears the node database. This dialog carries a Preserve Favorites? switch

⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.

Copie de rezervă și restaurare

Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.

Avansate

Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.

Curăță baza de date a nodurilor

Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.

  • Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
  • Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.

The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.

Panou de depanare

Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.

App Settings

The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:

Privacy

  • Allow analytics and crash reporting — opt in or out of diagnostics.
  • Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
  • Homoglyph encoding — how look-alike characters in names are handled.

Appearance

  • Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
  • Theme and Language.
  • Show full message timestamps.

Persistence

  • A cache limit for how much history is kept.
  • Export rangetest packets, Export all packets and Export node database.

On their own

  • Node Layout — how much detail each row of the node list shows.
  • Wi-Fi Provisioning for mPWRD-OS — see Connections.
  • Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
  • System AI — appears only where app functions are available; see App Functions.

A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.

Despre

Settings → About carries the app’s own identity rather than the node’s:

Three sections:

  • What is Meshtastic? — a short description of the project.
  • Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
  • Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.

The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.

Mulțumiri

Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.

Troubleshooting remote admin

  • “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
  • Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
  • Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
diff --git a/main/ro-rRO/user/settings-radio-user.html b/main/ro-rRO/user/settings-radio-user.html index ea1c69d666..ffde04722e 100644 --- a/main/ro-rRO/user/settings-radio-user.html +++ b/main/ro-rRO/user/settings-radio-user.html @@ -1 +1 @@ - Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Română
Meshtastic Docs ↗

🌐 Română — Community translation View in English

Settings — Radio & User

Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How these screens work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Descriere
Nume lung Your display name (up to 39 characters)
Nume scurt 4-character abbreviated name
Mesaj de stare: A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Netransmisibil Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur node (Ham) Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in.

Configuration

Device Config

On Settings → Device configuration → Device.

Setting Descriere Prestabilit
Rolul dispozitivului Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Mod de redifuzare How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Intervalul de difuzare a informațiilor nodului How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Apăsare dublă ca buton Treat a double tap as a button press Disabled
Apăsare triplă pentru ping Ad Hoc Send an ad-hoc position ping on a triple click Activat
Puls LED Blink the status LED periodically Activat
Fus orar POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it —
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to —

LoRa Config

On Settings → LoRa.

Setting Descriere Prestabilit
Regiune Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number Unset (must configure)
Presetări Speed/range tradeoff LongFast
Numărul de Hops Maximum retransmit hops 3
Putere transmisie Transmission power (dBm); 0 = max allowed for region 0 (region max)
Suprascriere frecvență Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Utilizare presetare On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Factor de răspândire Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead From preset
Rata de codificare Manual mode only: 5–8. More redundancy costs airtime From preset
Lățime bandă Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Slot pentru frecvenţă Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmisie activată Turning this off makes the node receive-only On
Suprascrie ciclul de obligații Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
Ignoră MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Acceptă MQTT Allow your packets to be forwarded to MQTT by gateways Off
Amplificare RX amplificată Extra receive gain on SX126x radios; costs a little current Off
Ventilator PA dezactivat Turn off the power-amplifier fan on hardware that has one Off

The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set.

Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Viteza SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a modem preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Display Config

On Settings → Device configuration → Display. These control the node’s own screen, not the app’s.

Setting Descriere
Ecran pornit pentru How long the display stays lit before sleeping
Intervalul caruselului How often the node cycles between screens on its own
Mod ecran Screen layout/density used by the firmware
Unități de măsură afișate Metric or Imperial on the node’s screen
Utilizaţi formatul ceasului 12h Show the node’s clock as 12-hour rather than 24-hour
Direcție îngroșat Draw the screen’s heading text in bold
Rotire ecran Rotate the display 180° for an inverted mounting
Tip OLED Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED
Trezire la apăsare sau mișcare Light the screen when the node is tapped or moved
Orientarea busolei Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each
Indică mereu spre nord Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Position Config

On Settings → Device configuration → Position.

Setting Descriere
Mod GPS (hardware fizic) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
Interval de actualizare GPS How often the node asks its GPS for a fix
Interval de difuzare How often the position is shared with the mesh
Poziție inteligentă Broadcast based on movement rather than purely on the clock
Interval inteligent With Smart Position on, the shortest gap between broadcasts
Distanță inteligentă With Smart Position on, how far you must move before broadcasting
Poziție fixă Use a manually entered latitude, longitude and altitude instead of the GPS
Steaguri poziție A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Configurare Putere

On Settings → Device configuration → Power.

Setting Descriere
Activează modul de economisire a energiei Let the node sleep aggressively between activity
Închidere la pierderea de energie Power the device down after external power disappears
Durată maximă de somn How long the deepest sleep state lasts
Durata minimă a trezirii The shortest time the node stays awake once woken
Așteptați pentru durata Bluetooth How long to wait for a phone to connect before sleeping
Suprascriere multiplicator ADC Turn on a manual correction for battery-voltage readings
Raportul suprascrierii multiplicatorului ADC The correction factor itself, used only when the override is on
Adresa baterie INA_2XX I2C Address of an external INA-series power sensor, if fitted

Network Config

On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node.

Setting Descriere
Wi-Fi enabled Enable the Wi-Fi node (ESP32 nodes)
Numele rețelei Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Parolă Network password
Ethernet activat Use a wired connection on hardware that has one
Mod IPv4 DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
Server NTP Time synchronization server
server rsyslog Remote logging server

Network Config with a static IPv4 address entered

Configurare Bluetooth

On Settings → Device configuration → Bluetooth, on nodes with Bluetooth.

Setting Descriere
Bluetooth activat Enable/disable BLE radio
Mod împerechere Fixed PIN, Random PIN, or No PIN
PIN fix PIN code for pairing. Must be exactly six digits — the field rejects anything else

Security Config

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

Setting Descriere
Chei publice Your node’s public key (read-only)
Cheie Administrator Keys permitted to administer this node remotely — up to three
Cheia privată Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it
Regenerează Cheia privată Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Consolă serială Serial console over the Stream API
Debug log API activat Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth
Mod Gestionat Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.

+ Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Română
Meshtastic Docs ↗

🌐 Română — Community translation View in English

Settings — Radio & User

Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How these screens work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Descriere
Nume lung Your display name (up to 39 characters)
Nume scurt 4-character abbreviated name
Mesaj de stare: A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Netransmisibil Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur node (Ham) Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in.

Configuration

Device Config

On Settings → Device configuration → Device.

Setting Descriere Prestabilit
Rolul dispozitivului Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Mod de redifuzare How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Intervalul de difuzare a informațiilor nodului How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Apăsare dublă ca buton Treat a double tap as a button press Disabled
Apăsare triplă pentru ping Ad Hoc Send an ad-hoc position ping on a triple click Activat
Puls LED Blink the status LED periodically Activat
Fus orar POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it —
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to —

LoRa Config

On Settings → LoRa.

Setting Descriere Prestabilit
Regiune Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number Unset (must configure)
Presetări Speed/range tradeoff LongFast
Numărul de Hops Maximum retransmit hops 3
Transmit Power (dBm) Transmission power; 0 = max allowed for region 0 (region max)
Suprascriere frecvență Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Utilizare presetare On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Factor de răspândire Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead From preset
Rata de codificare Manual mode only: 5–8. More redundancy costs airtime From preset
Lățime bandă Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Slot pentru frecvenţă Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmisie activată Turning this off makes the node receive-only On
Suprascrie ciclul de obligații Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
Ignoră MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Acceptă MQTT Allow your packets to be forwarded to MQTT by gateways Off
Amplificare RX amplificată Extra receive gain on SX126x radios; costs a little current Off
Ventilator PA dezactivat Turn off the power-amplifier fan on hardware that has one Off

The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set.

Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Viteza SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a modem preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Display Config

On Settings → Device configuration → Display. These control the node’s own screen, not the app’s.

Setting Descriere
Ecran pornit pentru How long the display stays lit before sleeping
Intervalul caruselului How often the node cycles between screens on its own
Mod ecran Screen layout/density used by the firmware
Unități de măsură afișate Metric or Imperial on the node’s screen
Utilizaţi formatul ceasului 12h Show the node’s clock as 12-hour rather than 24-hour
Direcție îngroșat Draw the screen’s heading text in bold
Rotire ecran Rotate the display 180° for an inverted mounting
Tip OLED Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED
Trezire la apăsare sau mișcare Light the screen when the node is tapped or moved
Orientarea busolei Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each
Indică mereu spre nord Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Position Config

On Settings → Device configuration → Position.

Setting Descriere
Mod GPS (hardware fizic) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
Interval de actualizare GPS How often the node asks its GPS for a fix
Interval de difuzare How often the position is shared with the mesh
Poziție inteligentă Broadcast based on movement rather than purely on the clock
Interval inteligent With Smart Position on, the shortest gap between broadcasts
Distanță inteligentă With Smart Position on, how far you must move before broadcasting
Poziție fixă Use a manually entered latitude, longitude and altitude instead of the GPS
Steaguri poziție A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Configurare Putere

On Settings → Device configuration → Power.

Setting Descriere
Activează modul de economisire a energiei Let the node sleep aggressively between activity
Închidere la pierderea de energie Power the device down after external power disappears
Durată maximă de somn How long the deepest sleep state lasts
Durata minimă a trezirii The shortest time the node stays awake once woken
Așteptați pentru durata Bluetooth How long to wait for a phone to connect before sleeping
Suprascriere multiplicator ADC Turn on a manual correction for battery-voltage readings
Raportul suprascrierii multiplicatorului ADC The correction factor itself, used only when the override is on
Adresa baterie INA_2XX I2C Address of an external INA-series power sensor, if fitted

Network Config

On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node.

Setting Descriere
Wi-Fi enabled Enable the Wi-Fi node (ESP32 nodes)
Numele rețelei Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Parolă Network password
Ethernet activat Use a wired connection on hardware that has one
Mod IPv4 DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
Server NTP Time synchronization server
server rsyslog Remote logging server

Network Config with a static IPv4 address entered

Configurare Bluetooth

On Settings → Device configuration → Bluetooth, on nodes with Bluetooth.

Setting Descriere
Bluetooth activat Enable/disable BLE radio
Mod împerechere Fixed PIN, Random PIN, or No PIN
PIN fix PIN code for pairing. Must be exactly six digits — the field rejects anything else

Security Config

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

Setting Descriere
Chei publice Your node’s public key (read-only)
Cheie Administrator Keys permitted to administer this node remotely — up to three
Cheia privată Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it
Regenerează Cheia privată Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Consolă serială Serial console over the Stream API
Debug log API activat Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth
Mod Gestionat Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.

diff --git a/main/ru-rRU/user/discovery.html b/main/ru-rRU/user/discovery.html index ff0ca0ae6b..7f26c743a8 100644 --- a/main/ru-rRU/user/discovery.html +++ b/main/ru-rRU/user/discovery.html @@ -5,4 +5,4 @@ ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) -

Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:.

На что обращать внимание Что это значит
All hops show Good SNR (green) Здоровый путь — сообщения идут без сбоев
One hop shows a poor SNR (orange or red) Слабое звено — этот сегмент ретрансляции хрупкий
Много хопов (4+) Длинный путь — подумай о перемещении ноды для его сокращения
Другой путь при повторе Сеть адаптируется — существуют несколько маршрутов (это хорошо!)

💡 Совет: Запусти трассировку несколько раз в течение нескольких минут. Если путь изменяется, у твоей сети есть лишние маршруты — признак хорошо связанной сети.

Устранение неполадок с трассировкой

  • No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Проверь, что обе ноды имеют хотя бы один канал с одинаковым ключом шифрования.
  • Время ожидания трассировки истекло — путь может быть слишком длинным (превышен лимит хопов) или нода ретрансляции перегружена. Try increasing the hop limit in Settings → LoRa.
  • Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position.
  • Асимметричные маршруты — трассировка от A→B может проходить по другому пути, чем B→A. This is normal — radio propagation isn’t always symmetric.

Информация об окружении

Модуль информации о соседях позволяет каждой ноде передавать список нод, которые она может слышать напрямую (на расстоянии одного хопа). Когда несколько нод делятся своими списками соседей, ты можешь составить карту топологии всей mesh-сети.

Включение информации о соседях

  1. Navigate to Settings → Module configuration → Neighbor Info.
  2. Включение модуля
  3. Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
  4. Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air.

Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Другие ноды с включённым модулем информации о соседях делают то же самое.

Viewing neighbor data

  • Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors.
  • Каждая запись о соседе показывает ноду, которая была услышана напрямую, и качество её сигнала.
  • Объединяйте данные о соседях от нескольких нод, чтобы понять полную топологию mesh-сети.

ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further.

Node list as a discovery tool

Сам по себе список нод — мощный инструмент обнаружения, если ты эффективно будешь использовать его возможности фильтрации и сортировки.

Finding new nodes

  • Сортируйте по “Последнему приёму”, чтобы увидеть вверху списка ноды, активные в последнее время.
  • Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes.

Assessing connectivity

  • Сортируйте по «Хопам», чтобы видеть, какие ноды доступны напрямую (0 хопов), а какие — через ретрансляцию.
  • Сортируйте по “Расстоянию”, чтобы найти близлежащие ноды и убедиться, что они доступны.
  • Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge).

Infrastructure audit

  • Отключите “Исключить инфраструктуру”, чтобы увидеть ноды Router, Router Late и Client Base.
  • Проверьте качество их сигнала и время последнего приёма, чтобы убедиться, что твои ноды инфраструктуры работают исправно.

См. раздел Ноды для получения полной информации о параметрах фильтрации и сортировки.

Tips for Mesh exploration

  • Начните с трассировки — она даёт тебе немедленную, пригодную для использования информацию о конкретном пути.
  • Включите информацию о соседях на ключевых нодах — особенно на роутерах и ретрансляторах, чтобы составить картину магистральной сети.
  • Проверьте карту — расположение нод на Карте в сочетании с данными о сигнале помогает тебе понять, почему одни соединения сильные, а другие слабые.
  • Сравнивайте сигнал с течением времени — используйте руководство по Измерителю сигнала для правильной интерпретации значений SNR и RSSI.

Связанные темы

+

Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:.

На что обращать внимание Что это значит
All hops show Good SNR (green) Здоровый путь — сообщения идут без сбоев
One hop shows a poor SNR (orange or red) Слабое звено — этот сегмент ретрансляции хрупкий
Много хопов (4+) Длинный путь — подумай о перемещении ноды для его сокращения
Другой путь при повторе Сеть адаптируется — существуют несколько маршрутов (это хорошо!)

💡 Совет: Запусти трассировку несколько раз в течение нескольких минут. Если путь изменяется, у твоей сети есть лишние маршруты — признак хорошо связанной сети.

Устранение неполадок с трассировкой

  • No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Проверь, что обе ноды имеют хотя бы один канал с одинаковым ключом шифрования.
  • Время ожидания трассировки истекло — путь может быть слишком длинным (превышен лимит хопов) или нода ретрансляции перегружена. Try increasing the hop limit in Settings → LoRa.
  • Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position.
  • Асимметричные маршруты — трассировка от A→B может проходить по другому пути, чем B→A. This is normal — radio propagation isn’t always symmetric.

Информация об окружении

Модуль информации о соседях позволяет каждой ноде передавать список нод, которые она может слышать напрямую (на расстоянии одного хопа). Когда несколько нод делятся своими списками соседей, ты можешь составить карту топологии всей mesh-сети.

Включение информации о соседях

  1. Navigate to Settings → Module configuration → Neighbor Info.
  2. Включение модуля
  3. Set Update Interval. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
  4. Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air.

Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Другие ноды с включённым модулем информации о соседях делают то же самое.

Viewing neighbor data

  • Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors.
  • Каждая запись о соседе показывает ноду, которая была услышана напрямую, и качество её сигнала.
  • Объединяйте данные о соседях от нескольких нод, чтобы понять полную топологию mesh-сети.

ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further.

Node list as a discovery tool

Сам по себе список нод — мощный инструмент обнаружения, если ты эффективно будешь использовать его возможности фильтрации и сортировки.

Finding new nodes

  • Сортируйте по “Последнему приёму”, чтобы увидеть вверху списка ноды, активные в последнее время.
  • Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes.

Assessing connectivity

  • Сортируйте по «Хопам», чтобы видеть, какие ноды доступны напрямую (0 хопов), а какие — через ретрансляцию.
  • Сортируйте по “Расстоянию”, чтобы найти близлежащие ноды и убедиться, что они доступны.
  • Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge).

Infrastructure audit

  • Отключите “Исключить инфраструктуру”, чтобы увидеть ноды Router, Router Late и Client Base.
  • Проверьте качество их сигнала и время последнего приёма, чтобы убедиться, что твои ноды инфраструктуры работают исправно.

См. раздел Ноды для получения полной информации о параметрах фильтрации и сортировки.

Tips for Mesh exploration

  • Начните с трассировки — она даёт тебе немедленную, пригодную для использования информацию о конкретном пути.
  • Включите информацию о соседях на ключевых нодах — особенно на роутерах и ретрансляторах, чтобы составить картину магистральной сети.
  • Проверьте карту — расположение нод на Карте в сочетании с данными о сигнале помогает тебе понять, почему одни соединения сильные, а другие слабые.
  • Сравнивайте сигнал с течением времени — используйте руководство по Измерителю сигнала для правильной интерпретации значений SNR и RSSI.

Связанные темы

diff --git a/main/ru-rRU/user/mqtt.html b/main/ru-rRU/user/mqtt.html index 1949784f76..bda1c55c9b 100644 --- a/main/ru-rRU/user/mqtt.html +++ b/main/ru-rRU/user/mqtt.html @@ -1,2 +1,2 @@ MQTT | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Русский
Meshtastic Docs ↗

🌐 Русский — Community translation View in English

MQTT

MQTT соединяет твою mesh-сеть Meshtastic с интернетом, обеспечивая связь на больших расстояниях за пределами радиодиапазона.

Обзор

Модуль MQTT подключает вашу ноду к MQTT-брокеру, что позволяет:

  • Сообщениям достигать нод в других физических mesh-сетях через интернет
  • Интегрироваться с системами домашней автоматизации и мониторинга
  • Публиковать местоположения нод на публичной карте Meshtastic
  • Создавать собственные каналы данных для журналирования и оповещений

Как это работает 

[Your Node] → Radio → [Gateway Node with Wi-Fi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node]
-

A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Удалённые шлюзы, подписанные на тот же топик, передают эти сообщения в свою локальную mesh-сеть.

Настройки

Включение MQTT

  1. Navigate to Settings → Module configuration → MQTT.
  2. Включите модуль MQTT.
  3. Настройте подключение к брокеру:
Настройка Описание По умолчанию
Address Имя хоста MQTT-брокера mqtt.meshtastic.org
Username Аутентификация брокера meshdev
Password Аутентификация брокера large4cats
Root topic Базовый топик для сообщений msh, which the radio rewrites to msh/<REGION> once you set a region
Encryption enabled Шифровать полезную нагрузку MQTT Включено
JSON output enabled Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it Отключено
TLS enabled Безопасное подключение к брокеру Отключено
Map reporting Сообщать о местоположении на публичную карту Отключено
Proxy to client enabled Relay MQTT through the connected phone Включено

Connection Status and Test Connection

The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here.

Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason.

MQTT-прокси на этом телефоне

If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection.

ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them.

The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration.

Стандартный брокер Meshtastic

Сообщество поддерживает публичный брокер по адресу mqtt.meshtastic.org. Он предназначен для общего использования и тестирования.

When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without).

🔒 Приватность: Сообщения на публичном брокере доступны для чтения всем, кто подписан. Всегда используйте шифрование каналов для конфиденциальной связи.

Частный брокер

Для большей приватности и контроля ты можешь запустить собственный MQTT-брокер:

  • Mosquitto (легковесный, с открытым исходным кодом)
  • HiveMQ
  • EMQX

Настройте свою ноду на подключение к частному брокеру с соответствующими учётными данными.

Публикация на карте

When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.

Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.

Reports appear at meshmap.net and similar community map services.

🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published.

Направление Описание
Uplink (восходящий) Сообщения из mesh-сети → MQTT-брокер
Downlink (нисходящий) Сообщения от MQTT-брокера → mesh-сеть

Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on.

Форматы сообщений

MQTT carries two payload formats:

Формат Описание Сценарий использования
Protobuf Бинарное кодирование Meshtastic protobuf Соединение нод между mesh-сетями
JSON Human-readable JSON on the /2/json/ topic Consumers outside the mesh (dashboards, home automation)

ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads.

Шифрование и приватность

Понимание многоуровневой модели шифрования:

  1. Шифрование канала происходит в mesh-сети до MQTT. Если твой канал использует PSK, полезная нагрузка MQTT уже зашифрована — брокер и любые подписчики видят только зашифрованный текст.
  2. Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard.
  3. TLS шифрует само TCP-соединение с брокером, предотвращая перехват на сетевом уровне.

🔒 Security: The default public channel has a well-known key. Сообщения в канале по умолчанию, отправленные через MQTT, фактически не зашифрованы — кто угодно может их расшифровать. Всегда используйте собственный PSK для конфиденциальной связи.

Рекомендации

  • Используйте шифрование на уровне канала (PSK) на каналах, подключённых к MQTT
  • Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes memory)
  • Используйте частный брокер для задач, требующих повышенной безопасности
  • Учитывайте эфирное время при передаче сообщений из загруженных MQTT-топиков — каждое такое сообщение расходует радиоэфирное время в вашей локальной mesh-сети
  • Рассмотрите включение режима “только uplink”, если нужно лишь удалённо наблюдать за mesh-сетью, не отправляя сообщения обратно

Устранение неполадок

MQTT не подключается

  • Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT не работает через сам радиоканал LoRa.
  • Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces.
  • Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443).
  • Разрешение DNS — если используется имя хоста собственного брокера, убедитесь, что нода может его разрешить. Попробуйте подключиться напрямую по IP-адресу брокера.

Сообщения не проходят через мост

  • Проверьте настройки uplink/downlink — если включён только uplink, сообщения идут из mesh-сети в MQTT, но не обратно. Включите downlink на принимающем шлюзе.
  • Несовпадение каналов — оба шлюза должны использовать один и тот же канал с одинаковым PSK. Несовпадение означает, что сообщения зашифрованы разными ключами и выглядят как мусор.
  • Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root.
  • Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway.
  • Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in.

Связанные темы

+

A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Удалённые шлюзы, подписанные на тот же топик, передают эти сообщения в свою локальную mesh-сеть.

Настройки

Включение MQTT

  1. Navigate to Settings → Module configuration → MQTT.
  2. Включите модуль MQTT.
  3. Настройте подключение к брокеру:
Настройка Описание По умолчанию
Address Имя хоста MQTT-брокера mqtt.meshtastic.org
Username Аутентификация брокера meshdev
Password Аутентификация брокера large4cats
Root topic Базовый топик для сообщений msh, which the radio rewrites to msh/<REGION> once you set a region
Encryption enabled Шифровать полезную нагрузку MQTT Включено
JSON output enabled Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it Отключено
TLS enabled Безопасное подключение к брокеру Отключено
Map reporting Сообщать о местоположении на публичную карту Отключено
Proxy to client enabled Relay MQTT through the connected phone Включено

Connection Status and Test Connection

The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here.

Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason.

MQTT-прокси на этом телефоне

If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection.

ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them.

The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration.

Стандартный брокер Meshtastic

Сообщество поддерживает публичный брокер по адресу mqtt.meshtastic.org. Он предназначен для общего использования и тестирования.

When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without).

🔒 Приватность: Сообщения на публичном брокере доступны для чтения всем, кто подписан. Всегда используйте шифрование каналов для конфиденциальной связи.

Частный брокер

Для большей приватности и контроля ты можешь запустить собственный MQTT-брокер:

  • Mosquitto (легковесный, с открытым исходным кодом)
  • HiveMQ
  • EMQX

Настройте свою ноду на подключение к частному брокеру с соответствующими учётными данными.

Публикация на карте

When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.

Turning it on opens a consent card. Turn on I agree. and choose a Map Publish Interval of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.

Reports appear at meshmap.net and similar community map services.

🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published.

Направление Описание
Uplink (восходящий) Сообщения из mesh-сети → MQTT-брокер
Downlink (нисходящий) Сообщения от MQTT-брокера → mesh-сеть

Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on.

Форматы сообщений

MQTT carries two payload formats:

Формат Описание Сценарий использования
Protobuf Бинарное кодирование Meshtastic protobuf Соединение нод между mesh-сетями
JSON Human-readable JSON on the /2/json/ topic Consumers outside the mesh (dashboards, home automation)

ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads.

Шифрование и приватность

Понимание многоуровневой модели шифрования:

  1. Шифрование канала происходит в mesh-сети до MQTT. Если твой канал использует PSK, полезная нагрузка MQTT уже зашифрована — брокер и любые подписчики видят только зашифрованный текст.
  2. Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard.
  3. TLS шифрует само TCP-соединение с брокером, предотвращая перехват на сетевом уровне.

🔒 Security: The default public channel has a well-known key. Сообщения в канале по умолчанию, отправленные через MQTT, фактически не зашифрованы — кто угодно может их расшифровать. Всегда используйте собственный PSK для конфиденциальной связи.

Рекомендации

  • Используйте шифрование на уровне канала (PSK) на каналах, подключённых к MQTT
  • Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes memory)
  • Используйте частный брокер для задач, требующих повышенной безопасности
  • Учитывайте эфирное время при передаче сообщений из загруженных MQTT-топиков — каждое такое сообщение расходует радиоэфирное время в вашей локальной mesh-сети
  • Рассмотрите включение режима “только uplink”, если нужно лишь удалённо наблюдать за mesh-сетью, не отправляя сообщения обратно

Устранение неполадок

MQTT не подключается

  • Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT не работает через сам радиоканал LoRa.
  • Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces.
  • Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443).
  • Разрешение DNS — если используется имя хоста собственного брокера, убедитесь, что нода может его разрешить. Попробуйте подключиться напрямую по IP-адресу брокера.

Сообщения не проходят через мост

  • Проверьте настройки uplink/downlink — если включён только uplink, сообщения идут из mesh-сети в MQTT, но не обратно. Включите downlink на принимающем шлюзе.
  • Несовпадение каналов — оба шлюза должны использовать один и тот же канал с одинаковым PSK. Несовпадение означает, что сообщения зашифрованы разными ключами и выглядят как мусор.
  • Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root.
  • Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway.
  • Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in.

Связанные темы

diff --git a/main/ru-rRU/user/settings-module-admin.html b/main/ru-rRU/user/settings-module-admin.html index 25ec2cdaaf..54678b1aaa 100644 --- a/main/ru-rRU/user/settings-module-admin.html +++ b/main/ru-rRU/user/settings-module-admin.html @@ -1 +1 @@ - Настройки — Модули и администрирование | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Русский
Meshtastic Docs ↗

🌐 Русский — Community translation View in English

Настройки — Модули и администрирование

Настрой дополнительные функциональные модули и выполняй управление устройством. Модули расширяют Meshtastic с помощью специализированных возможностей — каждый из них можно включать или отключать отдельно.

💡 Совет: Тебе нужно включать только те модули, которые действительно используешь. Отключение неиспользуемых модулей снижает время передачи, экономит батарею и упрощает конфигурацию. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.

Настройки модулей используют макет на основе карточек с переключателями, выпадающими списками, текстовыми полями и ползунками:

A toggle setting in the on position

A dropdown setting, expanded to show its list of options

A text field setting with a value entered

A module settings card with its title and grouped controls

Настройки модуля

Every module lives under Settings → Module configuration.

⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes.

MQTT module

Мосты передают сообщения туда и обратно от брокера MQTT для подключения к интернету. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.

Настройка Описание
MQTT включен Переключить MQTT мост
Адрес Адрес MQTT брокера
Имя пользователя Имя пользователя для аутентификации
Пароль Пароль аутентификации
Шифрование включено Зашифровать MQTT-пейлоады
Вывод JSON включен Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS включен Использовать защищённое соединение
Корневая тема Базовый путь темы MQTT
Прокси клиенту включен Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT-прокси на этом телефоне The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT
Отчёты по карте Publish position to the public map — see the Map reporting group that follows

Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:

Настройка Описание
Я согласен. Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Интервал отчета карты (в секундах) How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered

См. MQTT для подробного руководства по использованию, включая шифрование, конфиденциальность и настройку брокера.

Serial module

Позволяет общаться через последовательный порт с внешними устройствами (GPS-модулями, датчиками или собственной техникой). Когда включено, последовательный порт ноды может отправлять и получать данные в формате protobuf или текст, что позволяет внешним микроконтроллерам или компьютерам взаимодействовать с сетью.

Настройка Описание
COM-порт включен Включить последовательное соединение
Echo включен Echo получил обратно последовательные данные
Режим COM-порта Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX GPIO pins for the serial connection
Скорость COM-порта Port speed
Время ожидания истекло How long to wait before considering an incoming message complete
Переопределить COM-порт консоли Take over the port the debug console normally uses

External Notification module

Controls buzzer, LED, or vibration alerts on your node hardware. Полезно для устройств, которым нужно физически сигнализировать о приходе сообщения — особенно удобно для неоснащенных персоналом или уличных установок.

There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.

Настройка Описание
Внешние уведомления включены Master toggle for the module
Alert message LED / buzzer / vibra Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra Which outputs fire on a received bell character
Выход LED (GPIO) Pin the LED is wired to
Вывод светодиода активный высокий Whether the LED pin is active high or low
Выход Буззера (GPIO) Pin the buzzer is wired to
Вибросигнал (GPIO) Pin the vibration motor is wired to
Использовать PWM-звукоизлучатель Drive the buzzer with PWM, which allows tones rather than a single pitch
Использовать I2S как буззер Send the alert through an I2S audio output instead
Продолжительность вывода (миллисекунды) How long a single alert lasts
Таймаут Nag (в секундах) Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Рингтон The tone played on a PWM buzzer, in RTTTL. Can be imported from a file

Store & Forward module

Буферизирует сообщения для узлов, которые временно были недоступны, а затем ретранслирует их, когда эти узлы переподключаются. Важное значение для сеток, где узлы входят и выходят вне диапазона регулярно - обеспечивает отсутствие потери сообщений при коротких разъединениях.

Настройка Описание
Store & Forward включен Активировать режим хранения и пересылки
Heartbeat Периодически объявлять о наличии функции хранения и пересылки у этого узла
Количество записей Максимальное количество сохраненных сообщений
Макс возврат истории Максимум сообщений для повтора
Окно возврата истории Окно времени для повтора
Сервер Действовать как сервер хранения и пересылки для mesh-сети (требуется большой объем памяти, например, ESP32 с PSRAM)

💡 Совет: Хранение и пересылка лучше всего работает на узлах с достаточной памятью (ESP32 с PSRAM). Узлы маршрутизатора являются идеальными кандидатами, так как они обычно всегда включены.

Range Test module

⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.

Автоматизированный инструмент для проверки дальности и оценки качества связи между нодами. Когда включено, нода периодически отправляет сообщения с увеличивающимся счетчиком. Приёмная нода записывает эти сообщения, что позволяет тебе уйти пешком или уехать на машине, а потом проанализировать, на каком расстоянии сообщения перестали приходить.

Настройка Описание
Проверка дальности включена Активировать проверку дальности
Интервал сообщений отправителя (в секундах) Time between test transmissions, chosen from a dropdown of fixed intervals
Сохранить .CSV в хранилище (только ESP32) Log received test data to the node’s own filesystem. ESP32 hardware only

Telemetry module

Контролирует какими телеметрическими данными ваш узел делится с сеткой. Телеметрия включает данные о состоянии устройства (заряд батареи, время работы) и данные с датчиков окружающей среды (температура, влажность, давление).

Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.

Настройка Описание
Отправлять телеметрию устройства Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Интервал обновления метрик устройства How often to report battery, uptime and channel utilization
Модуль метрик окружения включен Report the attached environment sensors
Интервал обновления метрик среды How often to report them
Показатели окружения на экране включены Also show these readings on the device’s own display
Использовать метрику окружения в Fahrenheit Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Модуль измерения качества воздуха включен Report particulate and CO₂ sensor data
Интервал обновления данных качества воздуха How often to report them
Модуль метрик питания включен Report the per-channel voltage and current readings
Интервал обновления метрик электропитания How often to report them
Включить метрики питания на экране Also show power readings on the device’s display

Посмотрите Телеметрия и датчики — для получения информации о поддерживаемых датчиках и рекомендациях по настройке.

Canned Message module

Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Определите список быстрых сообщений, которые могут быть переданы без подключённого телефона — идеально подходит для использования в поле.

Настройка Описание
Canned message enabled ⚠️ Deprecated in the protobuf schema
Сообщения Список сообщений, разделённых новой строкой
Отправить колокольчик Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Поворотный энкодер #1 включен Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port The three pins the encoder is wired to
Generate input event on Press / CW / CCW Which key event each encoder action produces
Вверх/Вниз/Выбирать включён A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source ⚠️ Deprecated in the protobuf schema

Audio module

Поддержка аудио Codec2 для низкополосной голосовой связи через сетку. Это экспериментальная функция, которая кодирует голос в очень маленькие пакеты данных с помощью кодека Codec2.

Настройка Описание
CODEC 2 включен Активировать модуль аудио
Частота дискретизации CODEC2 Компромисс между качеством звука и полосой пропускания
Контакт PTT GPIO pin for the push-to-talk button
I2S Word Select GPIO контакт для I2S WS
I2S Data In Пин GPIO для I2S DIN
I2S Data Out Пин GPIO для I2S DOUT
I2S Clock GPIO pin for the I2S bit clock

ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Качество голоса очень низкополосное — представьте себе «разборчивую радиосвязь», а не качество телефонного звонка.

Remote Hardware module

Управление GPIO через mesh-сеть. Позволяет удалённому узлу читать и записывать состояния выводов GPIO на другом узле — полезно для активации реле, опроса переключателей или удалённого управления внешним оборудованием.

⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.

Настройка Описание
Удаленное оборудование включено Активировать удаленный GPIO доступ
Разрешить неопределённый контакт Разрешить доступ к любому GPIO-пину (риск для безопасности)
Доступные контакты До 4 пинов GPIO, которые этот узел предоставляет для удалённого чтения и записи

Neighbor Info module

Транслирует информацию о доступных услышанных соседей, включив ячейку сеточной топологии. Каждый включенный узел периодически делится списком других узлов которые он может слышать и их качество сигнала.

Настройка Описание
Информация о соседях включена Включить трансляцию соседей
Интервал обновления (в секундах) Как часто транслировать список соседей
Передать через LoRa Также транслировать информацию соседей по LoRa, а не только MQTT/телефон. Недоступно на канале используя ключ по умолчанию и имя

See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.

Ambient Lighting module

Управляет встроенными светодиодами NeoPixel или другими адресуемыми RGB-светодиодами на поддерживаемом оборудовании. Может использоваться для визуальных статусовых индикаторов, световых уведомлений, или декоративных эффектов.

Настройка Описание
Состояние LED Включить или выключить светодиод
Ток Текущий лимит светодиодов (0–31)
Красный / Зеленый / Синий Индивидуальные значения цветов канала (0–255)

Detection Sensor module

Превращает ваш узел в систему сигнализации на основе датчика движения или открытия двери. При обнаружении изменения состояния на выводе GPIO (например, сработал датчик движения или открылась дверь) узел отправляет по меш-сети оповещение.

Настройка Описание
Датчик определения включен Активировать датчик обнаружения
GPIO контакт для мониторинга Пин GPIO, подключенный к датчику
Тип триггера обнаружения Как состояние пина интерпретируется как событие обнаружения (например, активный высокий/низкий уровень, срабатывание по фронту)
Использовать режим INPUT_PULLUP Включить внутренний подтягивающий резистор пина
Минимальная трансляция (в секундах) Минимальный интервал между оповещениями
Трансляция состояния (в секундах) Интервал периодической отправки состояния
Отправить колокол с уведомлением Включать символ колокола в оповещения
Понятное имя Пользовательское имя для этого датчика

Paxcounter module

People counter using Wi-Fi and BLE probe requests. Засчитывает ближайшие устройства, пассивно прослушивая зондирующие запросы, чтобы телефоны и ноутбуки излучали при сканировании сетей. Доступно только на устройствах ESP32.

Настройка Описание
Paxcounter включен Активировать подсчет людей
Интервал обновления (в секундах) Как часто сообщать подсчитывания
Wi-Fi RSSI threshold Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE RSSI threshold The same cut-off for BLE advertisements (defaults to −80 dBm)

💡 Совет: Paxcounter полезен для приблизительной оценки пешеходного потока в местах начала маршрутов, на мероприятийных площадках или в других локациях. Счетчики приблизительны — один человек может иметь несколько устройств.

Status Message module

The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.

Mesh Beacon module

Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.

TAK module

Интеграция Team Awareness Kit для совместимости с ATAK и WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. См. TAK Integration для детальной настройки и использования.

Администрирование

Удаленное администрирование

Удалённо настраивай ноды, которые используют твой ключ администрирования:

  1. Выбери целевую ноду в списке нод.
  2. Перейди в Настройки этой ноды.
  3. Измени конфигурацию.
  4. Нажми Сохранить — изменения отправляются через сеть.

⚠️ Important: Requires an admin key configured on both your node and the target node.

Device Actions

Settings → Administration holds five one-shot actions, each behind a confirmation dialog:

Действие Что она делает
Установить время Sends your phone’s clock to the node
Перезагрузка Restarts the node
Выключение Powers the node down
Сброс до заводских настроек Returns every setting to its factory default
Очистка списка нод сети Clears the node database. This dialog carries a Preserve Favorites? switch

⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.

Бэкап & Восстановление

Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.

Расширенные

Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.

Очистить базу данных нод

Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.

  • Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
  • Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.

The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.

Панель отладки

Открывает вкладки Пакет и Журналы приложений для просмотра, фильтрации и экспорта диагностических выходов. См. Отладочные журналы для полного прохождения.

App Settings

The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:

Privacy

  • Allow analytics and crash reporting — opt in or out of diagnostics.
  • Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
  • Homoglyph encoding — how look-alike characters in names are handled.

Appearance

  • Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
  • Theme and Language.
  • Show full message timestamps.

Persistence

  • A cache limit for how much history is kept.
  • Export rangetest packets, Export all packets and Export node database.

On their own

  • Node Layout — how much detail each row of the node list shows.
  • Wi-Fi Provisioning for mPWRD-OS — see Connections.
  • Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
  • System AI — appears only where app functions are available; see App Functions.

A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.

О приложении

Settings → About carries the app’s own identity rather than the node’s:

Three sections:

  • What is Meshtastic? — a short description of the project.
  • Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
  • Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.

The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.

Благодарности

Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.

Troubleshooting remote admin

  • “Нет ответа от целевого узла” — цель может находиться вне диапазона, в автономном режиме или иметь несоответствующий ключ администратора. Проверьте соответствие ключа администратора на обоих узлах.
  • Изменения не применены — чтобы некоторые настройки вступили в силу, нужно перезагрузить устройство. Попробуй перезагрузить после сохранения.
  • Не видны настройки удалённой ноды — убедись, что твоя нода имеет админ-ключ для целевой ноды. Админ-канал настраивается автоматически, когда задан ключ администратора.

Связанные темы

+ Настройки — Модули и администрирование | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Русский
Meshtastic Docs ↗

🌐 Русский — Community translation View in English

Настройки — Модули и администрирование

Настрой дополнительные функциональные модули и выполняй управление устройством. Модули расширяют Meshtastic с помощью специализированных возможностей — каждый из них можно включать или отключать отдельно.

💡 Совет: Тебе нужно включать только те модули, которые действительно используешь. Отключение неиспользуемых модулей снижает время передачи, экономит батарею и упрощает конфигурацию. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.

Настройки модулей используют макет на основе карточек с переключателями, выпадающими списками, текстовыми полями и ползунками:

A toggle setting in the on position

A dropdown setting, expanded to show its list of options

A text field setting with a value entered

A module settings card with its title and grouped controls

Настройки модуля

Every module lives under Settings → Module configuration.

⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes.

MQTT module

Мосты передают сообщения туда и обратно от брокера MQTT для подключения к интернету. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.

Настройка Описание
MQTT включен Переключить MQTT мост
Адрес Адрес MQTT брокера
Имя пользователя Имя пользователя для аутентификации
Пароль Пароль аутентификации
Шифрование включено Зашифровать MQTT-пейлоады
Вывод JSON включен Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS включен Использовать защищённое соединение
Корневая тема Базовый путь темы MQTT
Прокси клиенту включен Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT-прокси на этом телефоне The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT
Отчёты по карте Publish position to the public map — see the Map reporting group that follows

Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:

Настройка Описание
Я согласен. Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered

См. MQTT для подробного руководства по использованию, включая шифрование, конфиденциальность и настройку брокера.

Serial module

Позволяет общаться через последовательный порт с внешними устройствами (GPS-модулями, датчиками или собственной техникой). Когда включено, последовательный порт ноды может отправлять и получать данные в формате protobuf или текст, что позволяет внешним микроконтроллерам или компьютерам взаимодействовать с сетью.

Настройка Описание
COM-порт включен Включить последовательное соединение
Echo включен Echo получил обратно последовательные данные
Режим COM-порта Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX GPIO pins for the serial connection
Скорость COM-порта Port speed
Время ожидания истекло How long to wait before considering an incoming message complete
Переопределить COM-порт консоли Take over the port the debug console normally uses

External Notification module

Controls buzzer, LED, or vibration alerts on your node hardware. Полезно для устройств, которым нужно физически сигнализировать о приходе сообщения — особенно удобно для неоснащенных персоналом или уличных установок.

There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.

Настройка Описание
Внешние уведомления включены Master toggle for the module
Alert message LED / buzzer / vibra Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra Which outputs fire on a received bell character
Выход LED (GPIO) Pin the LED is wired to
Вывод светодиода активный высокий Whether the LED pin is active high or low
Выход Буззера (GPIO) Pin the buzzer is wired to
Вибросигнал (GPIO) Pin the vibration motor is wired to
Использовать PWM-звукоизлучатель Drive the buzzer with PWM, which allows tones rather than a single pitch
Использовать I2S как буззер Send the alert through an I2S audio output instead
GPIO Output Duration How long a single alert lasts
Интервал повтора Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Рингтон The tone played on a PWM buzzer, in RTTTL. Can be imported from a file

Store & Forward module

Буферизирует сообщения для узлов, которые временно были недоступны, а затем ретранслирует их, когда эти узлы переподключаются. Важное значение для сеток, где узлы входят и выходят вне диапазона регулярно - обеспечивает отсутствие потери сообщений при коротких разъединениях.

Настройка Описание
Store & Forward включен Активировать режим хранения и пересылки
Heartbeat Периодически объявлять о наличии функции хранения и пересылки у этого узла
Количество записей Максимальное количество сохраненных сообщений
Макс возврат истории Максимум сообщений для повтора
Окно возврата истории Окно времени для повтора
Сервер Действовать как сервер хранения и пересылки для mesh-сети (требуется большой объем памяти, например, ESP32 с PSRAM)

💡 Совет: Хранение и пересылка лучше всего работает на узлах с достаточной памятью (ESP32 с PSRAM). Узлы маршрутизатора являются идеальными кандидатами, так как они обычно всегда включены.

Range Test module

⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.

Автоматизированный инструмент для проверки дальности и оценки качества связи между нодами. Когда включено, нода периодически отправляет сообщения с увеличивающимся счетчиком. Приёмная нода записывает эти сообщения, что позволяет тебе уйти пешком или уехать на машине, а потом проанализировать, на каком расстоянии сообщения перестали приходить.

Настройка Описание
Проверка дальности включена Активировать проверку дальности
Sender Interval Time between test transmissions, chosen from a dropdown of fixed intervals
Сохранить .CSV в хранилище (только ESP32) Log received test data to the node’s own filesystem. ESP32 hardware only

Telemetry module

Контролирует какими телеметрическими данными ваш узел делится с сеткой. Телеметрия включает данные о состоянии устройства (заряд батареи, время работы) и данные с датчиков окружающей среды (температура, влажность, давление).

Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.

Настройка Описание
Отправлять телеметрию устройства Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Интервал обновления метрик устройства How often to report battery, uptime and channel utilization
Модуль метрик окружения включен Report the attached environment sensors
Интервал обновления метрик среды How often to report them
Показатели окружения на экране включены Also show these readings on the device’s own display
Использовать метрику окружения в Fahrenheit Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Модуль измерения качества воздуха включен Report particulate and CO₂ sensor data
Интервал обновления данных качества воздуха How often to report them
Модуль метрик питания включен Report the per-channel voltage and current readings
Интервал обновления метрик электропитания How often to report them
Включить метрики питания на экране Also show power readings on the device’s display

Посмотрите Телеметрия и датчики — для получения информации о поддерживаемых датчиках и рекомендациях по настройке.

Canned Message module

Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Определите список быстрых сообщений, которые могут быть переданы без подключённого телефона — идеально подходит для использования в поле.

Настройка Описание
Canned message enabled ⚠️ Deprecated in the protobuf schema
Сообщения Список сообщений, разделённых новой строкой
Отправить колокольчик Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Поворотный энкодер #1 включен Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port The three pins the encoder is wired to
Generate input event on Press / CW / CCW Which key event each encoder action produces
Вверх/Вниз/Выбирать включён A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source ⚠️ Deprecated in the protobuf schema

Audio module

Поддержка аудио Codec2 для низкополосной голосовой связи через сетку. Это экспериментальная функция, которая кодирует голос в очень маленькие пакеты данных с помощью кодека Codec2.

Настройка Описание
CODEC 2 включен Активировать модуль аудио
Частота дискретизации CODEC2 Компромисс между качеством звука и полосой пропускания
Контакт PTT GPIO pin for the push-to-talk button
I2S Word Select GPIO контакт для I2S WS
I2S Data In Пин GPIO для I2S DIN
I2S Data Out Пин GPIO для I2S DOUT
I2S Clock GPIO pin for the I2S bit clock

ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Качество голоса очень низкополосное — представьте себе «разборчивую радиосвязь», а не качество телефонного звонка.

Remote Hardware module

Управление GPIO через mesh-сеть. Позволяет удалённому узлу читать и записывать состояния выводов GPIO на другом узле — полезно для активации реле, опроса переключателей или удалённого управления внешним оборудованием.

⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.

Настройка Описание
Удаленное оборудование включено Активировать удаленный GPIO доступ
Разрешить неопределённый контакт Разрешить доступ к любому GPIO-пину (риск для безопасности)
Доступные контакты До 4 пинов GPIO, которые этот узел предоставляет для удалённого чтения и записи

Neighbor Info module

Транслирует информацию о доступных услышанных соседей, включив ячейку сеточной топологии. Каждый включенный узел периодически делится списком других узлов которые он может слышать и их качество сигнала.

Настройка Описание
Информация о соседях включена Включить трансляцию соседей
Интервал опроса GPS Как часто транслировать список соседей
Передать через LoRa Также транслировать информацию соседей по LoRa, а не только MQTT/телефон. Недоступно на канале используя ключ по умолчанию и имя

See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.

Ambient Lighting module

Управляет встроенными светодиодами NeoPixel или другими адресуемыми RGB-светодиодами на поддерживаемом оборудовании. Может использоваться для визуальных статусовых индикаторов, световых уведомлений, или декоративных эффектов.

Настройка Описание
Состояние LED Включить или выключить светодиод
Ток Текущий лимит светодиодов (0–31)
Красный / Зеленый / Синий Индивидуальные значения цветов канала (0–255)

Detection Sensor module

Превращает ваш узел в систему сигнализации на основе датчика движения или открытия двери. При обнаружении изменения состояния на выводе GPIO (например, сработал датчик движения или открылась дверь) узел отправляет по меш-сети оповещение.

Настройка Описание
Датчик определения включен Активировать датчик обнаружения
GPIO контакт для мониторинга Пин GPIO, подключенный к датчику
Тип триггера обнаружения Как состояние пина интерпретируется как событие обнаружения (например, активный высокий/низкий уровень, срабатывание по фронту)
Использовать режим INPUT_PULLUP Включить внутренний подтягивающий резистор пина
Minimum time between detection broadcasts Минимальный интервал между оповещениями
State Broadcast Interval Интервал периодической отправки состояния
Отправить колокол с уведомлением Включать символ колокола в оповещения
Понятное имя Пользовательское имя для этого датчика

Paxcounter module

People counter using Wi-Fi and BLE probe requests. Засчитывает ближайшие устройства, пассивно прослушивая зондирующие запросы, чтобы телефоны и ноутбуки излучали при сканировании сетей. Доступно только на устройствах ESP32.

Настройка Описание
Paxcounter включен Активировать подсчет людей
Интервал опроса GPS Как часто сообщать подсчитывания
WiFi Threshold (dBm) Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm) The same cut-off for BLE advertisements (defaults to −80 dBm)

💡 Совет: Paxcounter полезен для приблизительной оценки пешеходного потока в местах начала маршрутов, на мероприятийных площадках или в других локациях. Счетчики приблизительны — один человек может иметь несколько устройств.

Status Message module

The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.

Mesh Beacon module

Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.

TAK module

Интеграция Team Awareness Kit для совместимости с ATAK и WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. См. TAK Integration для детальной настройки и использования.

Администрирование

Удаленное администрирование

Удалённо настраивай ноды, которые используют твой ключ администрирования:

  1. Выбери целевую ноду в списке нод.
  2. Перейди в Настройки этой ноды.
  3. Измени конфигурацию.
  4. Нажми Сохранить — изменения отправляются через сеть.

⚠️ Important: Requires an admin key configured on both your node and the target node.

Device Actions

Settings → Administration holds five one-shot actions, each behind a confirmation dialog:

Действие Что она делает
Установить время Sends your phone’s clock to the node
Перезагрузка Restarts the node
Выключение Powers the node down
Сброс до заводских настроек Returns every setting to its factory default
Очистка списка нод сети Clears the node database. This dialog carries a Preserve Favorites? switch

⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.

Бэкап & Восстановление

Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.

Расширенные

Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.

Очистить базу данных нод

Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.

  • Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
  • Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.

The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.

Панель отладки

Открывает вкладки Пакет и Журналы приложений для просмотра, фильтрации и экспорта диагностических выходов. См. Отладочные журналы для полного прохождения.

App Settings

The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:

Privacy

  • Allow analytics and crash reporting — opt in or out of diagnostics.
  • Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
  • Homoglyph encoding — how look-alike characters in names are handled.

Appearance

  • Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
  • Theme and Language.
  • Show full message timestamps.

Persistence

  • A cache limit for how much history is kept.
  • Export rangetest packets, Export all packets and Export node database.

On their own

  • Node Layout — how much detail each row of the node list shows.
  • Wi-Fi Provisioning for mPWRD-OS — see Connections.
  • Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
  • System AI — appears only where app functions are available; see App Functions.

A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.

О приложении

Settings → About carries the app’s own identity rather than the node’s:

Three sections:

  • What is Meshtastic? — a short description of the project.
  • Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
  • Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.

The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.

Благодарности

Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.

Troubleshooting remote admin

  • “Нет ответа от целевого узла” — цель может находиться вне диапазона, в автономном режиме или иметь несоответствующий ключ администратора. Проверьте соответствие ключа администратора на обоих узлах.
  • Изменения не применены — чтобы некоторые настройки вступили в силу, нужно перезагрузить устройство. Попробуй перезагрузить после сохранения.
  • Не видны настройки удалённой ноды — убедись, что твоя нода имеет админ-ключ для целевой ноды. Админ-канал настраивается автоматически, когда задан ключ администратора.

Связанные темы

diff --git a/main/ru-rRU/user/settings-radio-user.html b/main/ru-rRU/user/settings-radio-user.html index 2cedd92262..33e31e7373 100644 --- a/main/ru-rRU/user/settings-radio-user.html +++ b/main/ru-rRU/user/settings-radio-user.html @@ -1 +1 @@ - Настройки - Радио и пользователь | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Русский
Meshtastic Docs ↗

🌐 Русский — Community translation View in English

Настройки - Радио и пользователь

Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How these screens work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth.

Настройки используют стандартные элементы управления предпочтениями — выпадающие списки, переключатели и ползунки:

Управление Снимок экрана
Выпадающий список A dropdown setting, expanded to show its list of options
Переключатель A toggle setting in the on position
Ползунок A slider setting with its current numeric value shown

Настройки пользователя

Профиль пользователя

On Settings → User.

Настройка Описание
Полное имя Ваше отображаемое имя (до 39 символов)
Короткое имя 4-символьное сокращённое имя
Состояние сообщения A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Без сообщений Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur node (Ham) Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in.

Настройки

Настройки устройства

On Settings → Device configuration → Device.

Настройка Описание По умолчанию
Роль устройства Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Режим ретрансляции How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Интервал вещания передачи информации об узле How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Двойное нажатие как кнопка Treat a double tap as a button press Включено
Маякнуть при тройном нажатии Send an ad-hoc position ping on a triple click Включено
Сердцебиение светодиодом Blink the status LED periodically Включено
Часовой пояс POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it —
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to —

Настройка LoRa

On Settings → LoRa.

Настройка Описание По умолчанию
Регион / Страна Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number Не установлено (необходимо настроить)
Шаблоны Компромисс между скоростью и дальностью LongFast
Количество прыжков Максимальное количество ретрансляций 3
Мощность передатчика Мощность передачи (дБм); 0 = максимально разрешённая для региона 0 (максимум региона)
Переопределить частоту Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Использовать шаблон On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Коэффициент распространения Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead From preset
Частота кодирования Manual mode only: 5–8. More redundancy costs airtime From preset
Ширина канала Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Частота слота Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Передача включена Turning this off makes the node receive-only On
Переопределить рабочий цикл Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Выкл
Игнорировать MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
ОК в MQTT Allow your packets to be forwarded to MQTT by gateways Выкл
Усиление RX Extra receive gain on SX126x radios; costs a little current Выкл
PA вентилятор выключен Turn off the power-amplifier fan on hardware that has one Выкл

The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set.

Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. Смотрите руководство по настройке региона на сайте meshtastic.org для получения подробной информации.

Modem presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes.

💡 Совет: Значения порога SNR специально отрицательные. LoRa может декодировать сигналы ниже уровня шума, поэтому более отрицательный предел означает, что пресет допускает более слабый, шумный сигнал (больший радиус действия). Смотрите Как работает измеритель сигнала для полного объяснения.

Предустановка Диапазон Скорость Предел SNR Лучше всего для
Short Turbo ~1 км 21.9 кб/с −7.5 дБ Плотная городская застройка с прямой видимостью; приложения, требующие высокой передачи данных
Short Fast ~3 км 10.9 кб/с −7.5 дБ Городские районы; здания в пределах нескольких кварталов
Short Slow ~5 км 6.25 kbps -10 дБ Пригородная зона с коротким диапазоном; умеренная плотность застройки
Medium Fast ~5 км 3.52 kbps −12.5 дБ Пригородные районы; умеренная плотность застройки
Medium Slow ~8 км 1.95 kbps -15 дБ Пригородный/сельский; умеренный диапазон со сниженной скоростью
Long Turbo ~10 км 1.34 kbps −17.5 дБ Диапазон, похожий на Long Fast, но с полосой пропускания 500 кГц; более высокая пропускная способность
Long Fast ~10 км 1.1 кб/с −17.5 дБ Общее использование (по умолчанию) — сбалансированный диапазон и скорость
Long Moderate ~20 км 0.34 кб/с −17.5 дБ Сельская местность с некоторым рельефом; случайное использование
Lite Fast ~5 км 1.76 kbps −12.5 дБ Диапазон RU 866 МГц SRD (ширина полосы 125 кГц); аналогично Medium Fast
Lite Slow ~10 км 0.98 kbps -15 дБ Диапазон RU 866 МГц SRD (ширина полосы 125 кГц); аналогично Long Fast
Narrow Fast ~5 км 2.28 kbps −7.5 дБ Диапазон RU 868 МГц (полоса пропускания 62,5 кГц); предотвращает помехи с другими устройствами
Narrow Slow ~10 км 1.30 kbps -10 дБ Диапазон RU 868 МГц (ширина полосы 62,5 кГц); аналогично Long Fast
Medium Turbo ~5 км 7.0 kbps −12.5 дБ Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 км 0.68 kbps −7.5 дБ Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 км 0.33 kbps -10 дБ Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements
Long Slow ~30 км 0.18 кб/с −20 дБ ⚠️ Устарел — всё ещё доступен для выбора, но может быть удален в будущих версиях прошивки
Very Long Slow ~40+ км 0.09 кб/с −20 дБ ⚠️ Устарел — всё ещё доступен для выбора, но может быть удален в будущих версиях прошивки

i Примечание: В этой таблице используются общие короткие имена. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a modem preset

Предустановка модема управляет основным компромиссом между дальностью и скоростью передачи данных:

  • Медленные предустановки используют большее распространение, что позволяет декодировать сигналы при более слабых уровнях сигнала (ниже порога SNR). Это означает большую дальность, но меньше байт в секунду.
  • Быстрые предустановки передают больше данных за одну передачу, но требуют более сильного сигнала для декодирования.

Практическое руководство:

  • Городская сеть (много нод, короткие расстояния): Используй Long Fast (по умолчанию) или Short Fast. Более высокая скорость означает меньшее переполнение канала эфирного времени, когда многие ноды используют канал.
  • Сельская/разреженная сеть (мало нод, большие расстояния): Используй Long Moderate. Дальность важнее скорости, когда ноды находятся далеко друг от друга.
  • Соответствие нормативным требованиям RU 866/868 МГц: Используй Lite Fast, Lite Slow, Narrow Fast или Narrow Slow — они оптимизированы для диапазонов RU SRD/868 МГц с более узкой полосой пропускания.
  • Фиксированные инфраструктурные связи: Используй Short Turbo или Long Turbo для выделенных соединений точка-точка с хорошими антеннами и прямой видимостью.
  • Смешанные среды: Используй Long Fast — это настройка по умолчанию в сообществе и она обеспечит совместимость с другими в вашем регионе.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Преимущество высоты (вершина холма, крыша) значительно увеличивает эффективную дальность. Хорошо размещённый маршрутизатор с Long Fast часто может превзойти наземную ноду с Long Slow.

Параметры дисплея

On Settings → Device configuration → Display. These control the node’s own screen, not the app’s.

Настройка Описание
Включать экран на How long the display stays lit before sleeping
Интервал карусели How often the node cycles between screens on its own
Режим экрана Screen layout/density used by the firmware
Система измерения Metric or Imperial on the node’s screen
Использовать 12-часовой формат времени Show the node’s clock as 12-hour rather than 24-hour
Выделять заголовок жирным Draw the screen’s heading text in bold
Повернуть экран Rotate the display 180° for an inverted mounting
Тип OLED Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED
Включать экран при касании или движении Light the screen when the node is tapped or moved
Направление компаса Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each
Всегда указывать на север Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Настройки местоположения

On Settings → Device configuration → Position.

Настройка Описание
Режим GPS (физическое оборудование) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
Интервал опроса GPS How often the node asks its GPS for a fix
Период рассылки How often the position is shared with the mesh
Умная позиция Broadcast based on movement rather than purely on the clock
Умный интервал With Smart Position on, the shortest gap between broadcasts
Умное расстояние With Smart Position on, how far you must move before broadcasting
Фиксированная позиция Use a manually entered latitude, longitude and altitude instead of the GPS
Флаги позиции A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Настройка питания

On Settings → Device configuration → Power.

Настройка Описание
Включить режим энергосбережения Let the node sleep aggressively between activity
Выключение при потере мощности Power the device down after external power disappears
Длительность супер-глубокого сна How long the deepest sleep state lasts
Минимальное время бодрствования The shortest time the node stays awake once woken
Длительность ожидания Bluetooth How long to wait for a phone to connect before sleeping
Коэффициент переопределения ADC Turn on a manual correction for battery-voltage readings
Коэффициент переопределения ADC The correction factor itself, used only when the override is on
I2C-адрес INA_2XX батареи Address of an external INA-series power sensor, if fitted

Настройка сети

On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node.

Настройка Описание
Wi-Fi enabled Enable the Wi-Fi node (ESP32 nodes)
Название сети Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Пароль Пароль сети
Ethernet включен Use a wired connection on hardware that has one
Режим IPv4 DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP трансляция Share mesh traffic with other nodes over the local network
NTP-сервер Сервер синхронизации времени
Сервер rsyslog Удалённый сервер логирования

Network Config with a static IPv4 address entered

Настройка Bluetooth

On Settings → Device configuration → Bluetooth, on nodes with Bluetooth.

Настройка Описание
Bluetooth включен Включение/отключение BLE радиостанции
Режим сопряжения Фиксированный PIN, случайный PIN или без PIN
Фиксированный PIN-код PIN code for pairing. Must be exactly six digits — the field rejects anything else

Настройки безопасности

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

Настройка Описание
Публичный ключ Публичный ключ твоей ноды (только для чтения)
Ключ администратора Keys permitted to administer this node remotely — up to three
Приватный ключ Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it
Пересоздать приватный ключ Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Канал администратора включен ⚠️ Удалено — теперь настраивается автоматически при установке ключа администратора
Консоль COM-порта Serial console over the Stream API
API журнала отладки включен Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth
Управляемый режим Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set
Резервное копирование Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Восстановить ключи Запишисать сохранённые ключи обратно на ноду (доступно, как только есть резервная копия)
Удалить резервную копию ключа Remove the stored key backup from this phone
Уровень защиты How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device.

Alongside the passphrase you set the limits that end a session automatically:

Field Что она делает
Осталось загрузок How many device boots the unlocked state survives
Часов до истечения Wall-clock lifetime of the unlocked state
Ограничение сессии (минуты) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.

Связанные темы

+ Настройки - Радио и пользователь | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Русский
Meshtastic Docs ↗

🌐 Русский — Community translation View in English

Настройки - Радио и пользователь

Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How these screens work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth.

Настройки используют стандартные элементы управления предпочтениями — выпадающие списки, переключатели и ползунки:

Управление Снимок экрана
Выпадающий список A dropdown setting, expanded to show its list of options
Переключатель A toggle setting in the on position
Ползунок A slider setting with its current numeric value shown

Настройки пользователя

Профиль пользователя

On Settings → User.

Настройка Описание
Полное имя Ваше отображаемое имя (до 39 символов)
Короткое имя 4-символьное сокращённое имя
Состояние сообщения A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Без сообщений Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur node (Ham) Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in.

Настройки

Настройки устройства

On Settings → Device configuration → Device.

Настройка Описание По умолчанию
Роль устройства Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Режим ретрансляции How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Интервал вещания передачи информации об узле How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Двойное нажатие как кнопка Treat a double tap as a button press Включено
Маякнуть при тройном нажатии Send an ad-hoc position ping on a triple click Включено
Сердцебиение светодиодом Blink the status LED periodically Включено
Часовой пояс POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it —
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to —

Настройка LoRa

On Settings → LoRa.

Настройка Описание По умолчанию
Регион / Страна Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number Не установлено (необходимо настроить)
Шаблоны Компромисс между скоростью и дальностью LongFast
Количество прыжков Максимальное количество ретрансляций 3
Transmit Power (dBm) Transmission power; 0 = max allowed for region 0 (максимум региона)
Переопределить частоту Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Использовать шаблон On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Коэффициент распространения Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead From preset
Частота кодирования Manual mode only: 5–8. More redundancy costs airtime From preset
Ширина канала Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Частота слота Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Передача включена Turning this off makes the node receive-only On
Переопределить рабочий цикл Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Выкл
Игнорировать MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
ОК в MQTT Allow your packets to be forwarded to MQTT by gateways Выкл
Усиление RX Extra receive gain on SX126x radios; costs a little current Выкл
PA вентилятор выключен Turn off the power-amplifier fan on hardware that has one Выкл

The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set.

Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. Смотрите руководство по настройке региона на сайте meshtastic.org для получения подробной информации.

Modem presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes.

💡 Совет: Значения порога SNR специально отрицательные. LoRa может декодировать сигналы ниже уровня шума, поэтому более отрицательный предел означает, что пресет допускает более слабый, шумный сигнал (больший радиус действия). Смотрите Как работает измеритель сигнала для полного объяснения.

Предустановка Диапазон Скорость Предел SNR Лучше всего для
Short Turbo ~1 км 21.9 кб/с −7.5 дБ Плотная городская застройка с прямой видимостью; приложения, требующие высокой передачи данных
Short Fast ~3 км 10.9 кб/с −7.5 дБ Городские районы; здания в пределах нескольких кварталов
Short Slow ~5 км 6.25 kbps -10 дБ Пригородная зона с коротким диапазоном; умеренная плотность застройки
Medium Fast ~5 км 3.52 kbps −12.5 дБ Пригородные районы; умеренная плотность застройки
Medium Slow ~8 км 1.95 kbps -15 дБ Пригородный/сельский; умеренный диапазон со сниженной скоростью
Long Turbo ~10 км 1.34 kbps −17.5 дБ Диапазон, похожий на Long Fast, но с полосой пропускания 500 кГц; более высокая пропускная способность
Long Fast ~10 км 1.1 кб/с −17.5 дБ Общее использование (по умолчанию) — сбалансированный диапазон и скорость
Long Moderate ~20 км 0.34 кб/с −17.5 дБ Сельская местность с некоторым рельефом; случайное использование
Lite Fast ~5 км 1.76 kbps −12.5 дБ Диапазон RU 866 МГц SRD (ширина полосы 125 кГц); аналогично Medium Fast
Lite Slow ~10 км 0.98 kbps -15 дБ Диапазон RU 866 МГц SRD (ширина полосы 125 кГц); аналогично Long Fast
Narrow Fast ~5 км 2.28 kbps −7.5 дБ Диапазон RU 868 МГц (полоса пропускания 62,5 кГц); предотвращает помехи с другими устройствами
Narrow Slow ~10 км 1.30 kbps -10 дБ Диапазон RU 868 МГц (ширина полосы 62,5 кГц); аналогично Long Fast
Medium Turbo ~5 км 7.0 kbps −12.5 дБ Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 км 0.68 kbps −7.5 дБ Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 км 0.33 kbps -10 дБ Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements
Long Slow ~30 км 0.18 кб/с −20 дБ ⚠️ Устарел — всё ещё доступен для выбора, но может быть удален в будущих версиях прошивки
Very Long Slow ~40+ км 0.09 кб/с −20 дБ ⚠️ Устарел — всё ещё доступен для выбора, но может быть удален в будущих версиях прошивки

i Примечание: В этой таблице используются общие короткие имена. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a modem preset

Предустановка модема управляет основным компромиссом между дальностью и скоростью передачи данных:

  • Медленные предустановки используют большее распространение, что позволяет декодировать сигналы при более слабых уровнях сигнала (ниже порога SNR). Это означает большую дальность, но меньше байт в секунду.
  • Быстрые предустановки передают больше данных за одну передачу, но требуют более сильного сигнала для декодирования.

Практическое руководство:

  • Городская сеть (много нод, короткие расстояния): Используй Long Fast (по умолчанию) или Short Fast. Более высокая скорость означает меньшее переполнение канала эфирного времени, когда многие ноды используют канал.
  • Сельская/разреженная сеть (мало нод, большие расстояния): Используй Long Moderate. Дальность важнее скорости, когда ноды находятся далеко друг от друга.
  • Соответствие нормативным требованиям RU 866/868 МГц: Используй Lite Fast, Lite Slow, Narrow Fast или Narrow Slow — они оптимизированы для диапазонов RU SRD/868 МГц с более узкой полосой пропускания.
  • Фиксированные инфраструктурные связи: Используй Short Turbo или Long Turbo для выделенных соединений точка-точка с хорошими антеннами и прямой видимостью.
  • Смешанные среды: Используй Long Fast — это настройка по умолчанию в сообществе и она обеспечит совместимость с другими в вашем регионе.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Преимущество высоты (вершина холма, крыша) значительно увеличивает эффективную дальность. Хорошо размещённый маршрутизатор с Long Fast часто может превзойти наземную ноду с Long Slow.

Параметры дисплея

On Settings → Device configuration → Display. These control the node’s own screen, not the app’s.

Настройка Описание
Включать экран на How long the display stays lit before sleeping
Интервал карусели How often the node cycles between screens on its own
Режим экрана Screen layout/density used by the firmware
Система измерения Metric or Imperial on the node’s screen
Использовать 12-часовой формат времени Show the node’s clock as 12-hour rather than 24-hour
Выделять заголовок жирным Draw the screen’s heading text in bold
Повернуть экран Rotate the display 180° for an inverted mounting
Тип OLED Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED
Включать экран при касании или движении Light the screen when the node is tapped or moved
Направление компаса Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each
Всегда указывать на север Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Настройки местоположения

On Settings → Device configuration → Position.

Настройка Описание
Режим GPS (физическое оборудование) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
Интервал опроса GPS How often the node asks its GPS for a fix
Период рассылки How often the position is shared with the mesh
Умная позиция Broadcast based on movement rather than purely on the clock
Умный интервал With Smart Position on, the shortest gap between broadcasts
Умное расстояние With Smart Position on, how far you must move before broadcasting
Фиксированная позиция Use a manually entered latitude, longitude and altitude instead of the GPS
Флаги позиции A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Настройка питания

On Settings → Device configuration → Power.

Настройка Описание
Включить режим энергосбережения Let the node sleep aggressively between activity
Выключение при потере мощности Power the device down after external power disappears
Длительность супер-глубокого сна How long the deepest sleep state lasts
Минимальное время бодрствования The shortest time the node stays awake once woken
Длительность ожидания Bluetooth How long to wait for a phone to connect before sleeping
Коэффициент переопределения ADC Turn on a manual correction for battery-voltage readings
Коэффициент переопределения ADC The correction factor itself, used only when the override is on
I2C-адрес INA_2XX батареи Address of an external INA-series power sensor, if fitted

Настройка сети

On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node.

Настройка Описание
Wi-Fi enabled Enable the Wi-Fi node (ESP32 nodes)
Название сети Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Пароль Пароль сети
Ethernet включен Use a wired connection on hardware that has one
Режим IPv4 DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP трансляция Share mesh traffic with other nodes over the local network
NTP-сервер Сервер синхронизации времени
Сервер rsyslog Удалённый сервер логирования

Network Config with a static IPv4 address entered

Настройка Bluetooth

On Settings → Device configuration → Bluetooth, on nodes with Bluetooth.

Настройка Описание
Bluetooth включен Включение/отключение BLE радиостанции
Режим сопряжения Фиксированный PIN, случайный PIN или без PIN
Фиксированный PIN-код PIN code for pairing. Must be exactly six digits — the field rejects anything else

Настройки безопасности

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

Настройка Описание
Публичный ключ Публичный ключ твоей ноды (только для чтения)
Ключ администратора Keys permitted to administer this node remotely — up to three
Приватный ключ Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it
Пересоздать приватный ключ Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Канал администратора включен ⚠️ Удалено — теперь настраивается автоматически при установке ключа администратора
Консоль COM-порта Serial console over the Stream API
API журнала отладки включен Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth
Управляемый режим Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set
Резервное копирование Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Восстановить ключи Запишисать сохранённые ключи обратно на ноду (доступно, как только есть резервная копия)
Удалить резервную копию ключа Remove the stored key backup from this phone
Уровень защиты How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device.

Alongside the passphrase you set the limits that end a session automatically:

Field Что она делает
Осталось загрузок How many device boots the unlocked state survives
Часов до истечения Wall-clock lifetime of the unlocked state
Ограничение сессии (минуты) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.

Связанные темы

diff --git a/main/sk-rSK/user/discovery.html b/main/sk-rSK/user/discovery.html index 293c5e9c54..349bcc1fb0 100644 --- a/main/sk-rSK/user/discovery.html +++ b/main/sk-rSK/user/discovery.html @@ -5,4 +5,4 @@ ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) -

Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:.

What to look for What it means
All hops show Good SNR (green) Healthy path — messages flow reliably
One hop shows a poor SNR (orange or red) Weak link — this relay segment is fragile
Many hops (4+) Long path — consider repositioning a node to shorten it
Different path on retry Mesh is adapting — multiple routes exist (this is good!)

💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network.

Troubleshooting with Traceroute

  • No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key.
  • Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa.
  • Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position.
  • Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric.

Informácia o susedoch

The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh.

Enabling Neighbor Info

  1. Navigate to Settings → Module configuration → Neighbor Info.
  2. Enable the module.
  3. Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
  4. Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air.

Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.

Viewing neighbor data

  • Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors.
  • Each neighbor entry shows the node that was directly heard and its signal quality.
  • Combine neighbor data from multiple nodes to understand the full mesh topology.

ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further.

Node list as a discovery tool

The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively.

Finding new nodes

  • Sort by Last heard to see the most recently active nodes at the top.
  • Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes.

Assessing connectivity

  • Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed.
  • Sort by Distance to find nearby nodes and verify they’re reachable.
  • Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge).

Infrastructure audit

  • Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes.
  • Check their signal quality and last-heard times to verify your infrastructure nodes are healthy.

See Nodes for full details on filtering and sorting options.

Tips for Mesh exploration

  • Start with traceroute — it gives you immediate, actionable information about a specific path.
  • Enable Neighbor Info on key nodes — especially routers and repeaters, to build a picture of the backbone.
  • Check the map — node positions on the Map combined with signal data help you understand why some links are strong and others are weak.
  • Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly.
+

Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:.

What to look for What it means
All hops show Good SNR (green) Healthy path — messages flow reliably
One hop shows a poor SNR (orange or red) Weak link — this relay segment is fragile
Many hops (4+) Long path — consider repositioning a node to shorten it
Different path on retry Mesh is adapting — multiple routes exist (this is good!)

💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network.

Troubleshooting with Traceroute

  • No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key.
  • Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa.
  • Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position.
  • Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric.

Informácia o susedoch

The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh.

Enabling Neighbor Info

  1. Navigate to Settings → Module configuration → Neighbor Info.
  2. Enable the module.
  3. Set Update Interval. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
  4. Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air.

Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.

Viewing neighbor data

  • Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors.
  • Each neighbor entry shows the node that was directly heard and its signal quality.
  • Combine neighbor data from multiple nodes to understand the full mesh topology.

ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further.

Node list as a discovery tool

The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively.

Finding new nodes

  • Sort by Last heard to see the most recently active nodes at the top.
  • Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes.

Assessing connectivity

  • Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed.
  • Sort by Distance to find nearby nodes and verify they’re reachable.
  • Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge).

Infrastructure audit

  • Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes.
  • Check their signal quality and last-heard times to verify your infrastructure nodes are healthy.

See Nodes for full details on filtering and sorting options.

Tips for Mesh exploration

  • Start with traceroute — it gives you immediate, actionable information about a specific path.
  • Enable Neighbor Info on key nodes — especially routers and repeaters, to build a picture of the backbone.
  • Check the map — node positions on the Map combined with signal data help you understand why some links are strong and others are weak.
  • Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly.
diff --git a/main/sk-rSK/user/mqtt.html b/main/sk-rSK/user/mqtt.html index 51453a73a6..a34ea9b0c8 100644 --- a/main/sk-rSK/user/mqtt.html +++ b/main/sk-rSK/user/mqtt.html @@ -1,2 +1,2 @@ MQTT | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Slovenčina
Meshtastic Docs ↗

🌐 Slovenčina — Community translation View in English

MQTT

MQTT bridges your Meshtastic mesh network to the internet, enabling long-range communication beyond radio range.

Overview

The MQTT module connects your node to an MQTT broker, allowing:

  • Messages to reach nodes on different physical meshes via the internet
  • Integration with home automation and monitoring systems
  • Publishing node positions to the public Meshtastic map
  • Custom data pipelines for logging and alerting

How It Works 

[Your Node] → Radio → [Gateway Node with Wi-Fi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node]
-

A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh.

Configuration

Enabling MQTT

  1. Navigate to Settings → Module configuration → MQTT.
  2. Enable the MQTT module.
  3. Configure the broker connection:
Setting Popis Predvolené
Address MQTT broker hostname mqtt.meshtastic.org
Username Broker authentication meshdev
Password Broker authentication large4cats
Root topic Base topic for messages msh, which the radio rewrites to msh/<REGION> once you set a region
Encryption enabled Encrypt MQTT payload Enabled
JSON output enabled Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it Disabled
TLS enabled Secure connection to broker Disabled
Map reporting Report position to public map Disabled
Proxy to client enabled Relay MQTT through the connected phone Disabled

Connection Status and Test Connection

The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here.

Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason.

MQTT Proxy on This Phone

If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection.

ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them.

The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration.

Default Meshtastic Broker

The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing.

When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without).

🔒 Privacy: Messages on the public broker are readable by anyone subscribed. Always use channel encryption for private communications.

Private Broker

For better privacy and control, you can run your own MQTT broker:

  • Mosquitto (lightweight, open-source)
  • HiveMQ
  • EMQX

Configure your node to point to your private broker with appropriate credentials.

Map Reporting

When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.

Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.

Reports appear at meshmap.net and similar community map services.

🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published.

Direction Popis
Uplink Messages from mesh → MQTT broker
Downlink Messages from MQTT broker → mesh

Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on.

Message Formats

MQTT carries two payload formats:

Format Popis Use case
Protobuf Binary Meshtastic protobuf encoding Node-to-node mesh bridging
JSON Human-readable JSON on the /2/json/ topic Consumers outside the mesh (dashboards, home automation)

ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads.

Encryption & Privacy

Understanding the layered encryption model:

  1. Channel encryption happens on the mesh before MQTT. If your channel has a PSK, the MQTT payload is already encrypted — the broker and any subscribers see only the ciphertext.
  2. Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard.
  3. TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping.

🔒 Security: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications.

Best Practices

  • Use channel-level encryption (PSK) on channels that bridge to MQTT
  • Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes memory)
  • Use a private broker for sensitive deployments
  • Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh
  • Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back

Troubleshooting

MQTT Not Connecting

  • Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself.
  • Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces.
  • Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443).
  • DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly.

Messages Not Bridging

  • Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway.
  • Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage.
  • Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root.
  • Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway.
  • Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in.
+

A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh.

Configuration

Enabling MQTT

  1. Navigate to Settings → Module configuration → MQTT.
  2. Enable the MQTT module.
  3. Configure the broker connection:
Setting Popis Predvolené
Address MQTT broker hostname mqtt.meshtastic.org
Username Broker authentication meshdev
Password Broker authentication large4cats
Root topic Base topic for messages msh, which the radio rewrites to msh/<REGION> once you set a region
Encryption enabled Encrypt MQTT payload Enabled
JSON output enabled Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it Disabled
TLS enabled Secure connection to broker Disabled
Map reporting Report position to public map Disabled
Proxy to client enabled Relay MQTT through the connected phone Disabled

Connection Status and Test Connection

The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here.

Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason.

MQTT Proxy on This Phone

If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection.

ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them.

The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration.

Default Meshtastic Broker

The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing.

When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without).

🔒 Privacy: Messages on the public broker are readable by anyone subscribed. Always use channel encryption for private communications.

Private Broker

For better privacy and control, you can run your own MQTT broker:

  • Mosquitto (lightweight, open-source)
  • HiveMQ
  • EMQX

Configure your node to point to your private broker with appropriate credentials.

Map Reporting

When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.

Turning it on opens a consent card. Turn on I agree. and choose a Map Publish Interval of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.

Reports appear at meshmap.net and similar community map services.

🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published.

Direction Popis
Uplink Messages from mesh → MQTT broker
Downlink Messages from MQTT broker → mesh

Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on.

Message Formats

MQTT carries two payload formats:

Format Popis Use case
Protobuf Binary Meshtastic protobuf encoding Node-to-node mesh bridging
JSON Human-readable JSON on the /2/json/ topic Consumers outside the mesh (dashboards, home automation)

ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads.

Encryption & Privacy

Understanding the layered encryption model:

  1. Channel encryption happens on the mesh before MQTT. If your channel has a PSK, the MQTT payload is already encrypted — the broker and any subscribers see only the ciphertext.
  2. Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard.
  3. TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping.

🔒 Security: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications.

Best Practices

  • Use channel-level encryption (PSK) on channels that bridge to MQTT
  • Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes memory)
  • Use a private broker for sensitive deployments
  • Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh
  • Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back

Troubleshooting

MQTT Not Connecting

  • Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself.
  • Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces.
  • Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443).
  • DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly.

Messages Not Bridging

  • Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway.
  • Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage.
  • Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root.
  • Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway.
  • Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in.
diff --git a/main/sk-rSK/user/settings-module-admin.html b/main/sk-rSK/user/settings-module-admin.html index 58003e7c1e..284d99c796 100644 --- a/main/sk-rSK/user/settings-module-admin.html +++ b/main/sk-rSK/user/settings-module-admin.html @@ -1 +1 @@ - Settings — Modules & Admin | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Slovenčina
Meshtastic Docs ↗

🌐 Slovenčina — Community translation View in English

Settings — Modules & Admin

Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.

💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.

Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:

A toggle setting in the on position

A dropdown setting, expanded to show its list of options

A text field setting with a value entered

A module settings card with its title and grouped controls

Konfigurácia modulu

Every module lives under Settings → Module configuration.

⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes.

MQTT module

Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.

Setting Popis
MQTT enabled Toggle MQTT bridge
Adresa MQTT broker address
Používateľské meno Authentication username
Heslo Authentication password
Encryption enabled Encrypt MQTT payloads
JSON output enabled Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS enabled Use secure connection
Root topic Base MQTT topic path
Proxy to client enabled Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy on this phone The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT
Map reporting Publish position to the public map — see the Map reporting group that follows

Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:

Setting Popis
I agree. Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map reporting interval (seconds) How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered

See MQTT for a detailed usage guide including encryption, privacy, and broker setup.

Serial module

Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.

Setting Popis
Serial enabled Activate serial communication
Echo enabled Echo received serial data back
Serial mode Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX GPIO pins for the serial connection
Serial baud rate Port speed
Časový limit How long to wait before considering an incoming message complete
Override console serial port Take over the port the debug console normally uses

External Notification module

Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.

There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.

Setting Popis
External notification enabled Master toggle for the module
Alert message LED / buzzer / vibra Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra Which outputs fire on a received bell character
Output LED (GPIO) Pin the LED is wired to
Output LED active high Whether the LED pin is active high or low
Output buzzer (GPIO) Pin the buzzer is wired to
Output vibra (GPIO) Pin the vibration motor is wired to
Use PWM buzzer Drive the buzzer with PWM, which allows tones rather than a single pitch
Use I2S as buzzer Send the alert through an I2S audio output instead
Output duration (milliseconds) How long a single alert lasts
Nag timeout (seconds) Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Zvonenie The tone played on a PWM buzzer, in RTTTL. Can be imported from a file

Store & Forward module

Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.

Setting Popis
Store & Forward enabled Activate store and forward
Heartbeat Periodically announce this node’s store-and-forward capability
Number of records Maximum stored messages
History return max Max messages to replay
History return window Time window for replay
Server Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)

💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.

Range Test module

⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.

Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.

Setting Popis
Range test enabled Activate range testing
Sender message interval (seconds) Time between test transmissions, chosen from a dropdown of fixed intervals
Save .CSV in storage (ESP32 only) Log received test data to the node’s own filesystem. ESP32 hardware only

Telemetry module

Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).

Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.

Setting Popis
Send Device Telemetry Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval How often to report battery, uptime and channel utilization
Environment metrics module enabled Report the attached environment sensors
Environment metrics update interval How often to report them
Environment metrics on-screen enabled Also show these readings on the device’s own display
Environment metrics use Fahrenheit Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Air quality metrics module enabled Report particulate and CO₂ sensor data
Air quality metrics update interval How often to report them
Power metrics module enabled Report the per-channel voltage and current readings
Power metrics update interval How often to report them
Power metrics on-screen enabled Also show power readings on the device’s display

See Telemetry & Sensors for supported sensors and configuration recommendations.

Canned Message module

Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.

Setting Popis
Canned message enabled ⚠️ Deprecated in the protobuf schema
Správy Newline-separated list of messages
Send bell Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Enkóder #1 aktivovaný Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port The three pins the encoder is wired to
Generate input event on Press / CW / CCW Which key event each encoder action produces
Up/Down/Select input enabled A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source ⚠️ Deprecated in the protobuf schema

Audio module

Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.

Setting Popis
CODEC 2 zapnutý Activate audio module
CODEC2 vzorkovacia frekvencia Audio quality/bandwidth tradeoff
PTT pin GPIO pin for the push-to-talk button
I2C výber slova GPIO pin for I2S WS
I2S vstup dát GPIO pin for I2S DIN
I2S výstup dát GPIO pin for I2S DOUT
I2S čas GPIO pin for the I2S bit clock

ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.

Remote Hardware module

GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.

⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.

Setting Popis
Remote Hardware enabled Activate remote GPIO access
Allow undefined pin access Allow access to any GPIO pin (security risk)
Available pins Up to 4 GPIO pins this node exposes for remote read/write

Neighbor Info module

Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.

Setting Popis
Neighbor Info enabled Activate neighbor broadcasting
Update interval (seconds) How often to broadcast neighbor list
Vysielať cez sieť LoRa Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name

See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.

Ambient Lighting module

Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.

Setting Popis
Stav LED Turn the LED on or off
Prúd LED current limit (0–31)
Red / Green / Blue Individual color channel values (0–255)

Detection Sensor module

Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.

Setting Popis
Detection Sensor enabled Activate detection sensor
GPIO pin to monitor GPIO pin connected to sensor
Detection trigger type How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Use INPUT_PULLUP mode Enable the pin’s internal pull-up resistor
Minimum broadcast (seconds) Minimum time between alert broadcasts
State broadcast (seconds) Periodic state broadcast interval
Send bell with alert message Include bell character in alerts
Friendly name Custom name for this sensor

Paxcounter module

People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.

Setting Popis
Paxcounter enabled Activate people counting
Update interval (seconds) How often to report counts
Wi-Fi RSSI threshold Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE RSSI threshold The same cut-off for BLE advertisements (defaults to −80 dBm)

💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.

Status Message module

The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.

Mesh Beacon module

Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.

TAK module

Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.

Administrácia

Administrácia na diaľku

Remotely configure nodes that share your admin key:

  1. Select the target node in the node list.
  2. Navigate to Settings for that node.
  3. Modify configuration.
  4. Tap Save — changes are sent over the mesh.

⚠️ Important: Requires an admin key configured on both your node and the target node.

Device Actions

Settings → Administration holds five one-shot actions, each behind a confirmation dialog:

Action What it does
Set time Sends your phone’s clock to the node
Reštartovať Restarts the node
Vypnúť Powers the node down
Obnova do výrobných nastavení Returns every setting to its factory default
Reset databázy uzlov Clears the node database. This dialog carries a Preserve Favorites? switch

⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.

Zálohovanie a Obnovenie

Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.

Advanced

Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.

Clean Node Database

Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.

  • Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
  • Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.

The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.

Debug okno

Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.

App Settings

The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:

Privacy

  • Allow analytics and crash reporting — opt in or out of diagnostics.
  • Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
  • Homoglyph encoding — how look-alike characters in names are handled.

Appearance

  • Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
  • Theme and Language.
  • Show full message timestamps.

Persistence

  • A cache limit for how much history is kept.
  • Export rangetest packets, Export all packets and Export node database.

On their own

  • Node Layout — how much detail each row of the node list shows.
  • Wi-Fi Provisioning for mPWRD-OS — see Connections.
  • Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
  • System AI — appears only where app functions are available; see App Functions.

A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.

O aplikácii

Settings → About carries the app’s own identity rather than the node’s:

Three sections:

  • What is Meshtastic? — a short description of the project.
  • Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
  • Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.

The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.

Acknowledgements

Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.

Troubleshooting remote admin

  • “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
  • Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
  • Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
+ Settings — Modules & Admin | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Slovenčina
Meshtastic Docs ↗

🌐 Slovenčina — Community translation View in English

Settings — Modules & Admin

Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.

💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.

Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:

A toggle setting in the on position

A dropdown setting, expanded to show its list of options

A text field setting with a value entered

A module settings card with its title and grouped controls

Konfigurácia modulu

Every module lives under Settings → Module configuration.

⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes.

MQTT module

Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.

Setting Popis
MQTT enabled Toggle MQTT bridge
Adresa MQTT broker address
Používateľské meno Authentication username
Heslo Authentication password
Encryption enabled Encrypt MQTT payloads
JSON output enabled Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS enabled Use secure connection
Root topic Base MQTT topic path
Proxy to client enabled Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy on this phone The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT
Map reporting Publish position to the public map — see the Map reporting group that follows

Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:

Setting Popis
I agree. Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered

See MQTT for a detailed usage guide including encryption, privacy, and broker setup.

Serial module

Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.

Setting Popis
Serial enabled Activate serial communication
Echo enabled Echo received serial data back
Serial mode Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX GPIO pins for the serial connection
Serial baud rate Port speed
Časový limit How long to wait before considering an incoming message complete
Override console serial port Take over the port the debug console normally uses

External Notification module

Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.

There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.

Setting Popis
External notification enabled Master toggle for the module
Alert message LED / buzzer / vibra Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra Which outputs fire on a received bell character
Output LED (GPIO) Pin the LED is wired to
Output LED active high Whether the LED pin is active high or low
Output buzzer (GPIO) Pin the buzzer is wired to
Output vibra (GPIO) Pin the vibration motor is wired to
Use PWM buzzer Drive the buzzer with PWM, which allows tones rather than a single pitch
Use I2S as buzzer Send the alert through an I2S audio output instead
GPIO Output Duration How long a single alert lasts
Nag Timeout Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Zvonenie The tone played on a PWM buzzer, in RTTTL. Can be imported from a file

Store & Forward module

Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.

Setting Popis
Store & Forward enabled Activate store and forward
Heartbeat Periodically announce this node’s store-and-forward capability
Number of records Maximum stored messages
History return max Max messages to replay
History return window Time window for replay
Server Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)

💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.

Range Test module

⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.

Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.

Setting Popis
Range test enabled Activate range testing
Sender Interval Time between test transmissions, chosen from a dropdown of fixed intervals
Save .CSV in storage (ESP32 only) Log received test data to the node’s own filesystem. ESP32 hardware only

Telemetry module

Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).

Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.

Setting Popis
Send Device Telemetry Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval How often to report battery, uptime and channel utilization
Environment metrics module enabled Report the attached environment sensors
Environment metrics update interval How often to report them
Environment metrics on-screen enabled Also show these readings on the device’s own display
Environment metrics use Fahrenheit Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Air quality metrics module enabled Report particulate and CO₂ sensor data
Air quality metrics update interval How often to report them
Power metrics module enabled Report the per-channel voltage and current readings
Power metrics update interval How often to report them
Power metrics on-screen enabled Also show power readings on the device’s display

See Telemetry & Sensors for supported sensors and configuration recommendations.

Canned Message module

Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.

Setting Popis
Canned message enabled ⚠️ Deprecated in the protobuf schema
Správy Newline-separated list of messages
Send bell Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Enkóder #1 aktivovaný Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port The three pins the encoder is wired to
Generate input event on Press / CW / CCW Which key event each encoder action produces
Up/Down/Select input enabled A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source ⚠️ Deprecated in the protobuf schema

Audio module

Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.

Setting Popis
CODEC 2 zapnutý Activate audio module
CODEC2 vzorkovacia frekvencia Audio quality/bandwidth tradeoff
PTT pin GPIO pin for the push-to-talk button
I2C výber slova GPIO pin for I2S WS
I2S vstup dát GPIO pin for I2S DIN
I2S výstup dát GPIO pin for I2S DOUT
I2S čas GPIO pin for the I2S bit clock

ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.

Remote Hardware module

GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.

⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.

Setting Popis
Remote Hardware enabled Activate remote GPIO access
Allow undefined pin access Allow access to any GPIO pin (security risk)
Available pins Up to 4 GPIO pins this node exposes for remote read/write

Neighbor Info module

Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.

Setting Popis
Neighbor Info enabled Activate neighbor broadcasting
Aktualizačný interval How often to broadcast neighbor list
Vysielať cez sieť LoRa Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name

See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.

Ambient Lighting module

Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.

Setting Popis
Stav LED Turn the LED on or off
Prúd LED current limit (0–31)
Red / Green / Blue Individual color channel values (0–255)

Detection Sensor module

Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.

Setting Popis
Detection Sensor enabled Activate detection sensor
GPIO pin to monitor GPIO pin connected to sensor
Detection trigger type How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Use INPUT_PULLUP mode Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts Minimum time between alert broadcasts
State Broadcast Interval Periodic state broadcast interval
Send bell with alert message Include bell character in alerts
Friendly name Custom name for this sensor

Paxcounter module

People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.

Setting Popis
Paxcounter enabled Activate people counting
Aktualizačný interval How often to report counts
WiFi Threshold (dBm) Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm) The same cut-off for BLE advertisements (defaults to −80 dBm)

💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.

Status Message module

The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.

Mesh Beacon module

Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.

TAK module

Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.

Administrácia

Administrácia na diaľku

Remotely configure nodes that share your admin key:

  1. Select the target node in the node list.
  2. Navigate to Settings for that node.
  3. Modify configuration.
  4. Tap Save — changes are sent over the mesh.

⚠️ Important: Requires an admin key configured on both your node and the target node.

Device Actions

Settings → Administration holds five one-shot actions, each behind a confirmation dialog:

Action What it does
Set time Sends your phone’s clock to the node
Reštartovať Restarts the node
Vypnúť Powers the node down
Obnova do výrobných nastavení Returns every setting to its factory default
Reset databázy uzlov Clears the node database. This dialog carries a Preserve Favorites? switch

⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.

Zálohovanie a Obnovenie

Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.

Advanced

Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.

Clean Node Database

Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.

  • Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
  • Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.

The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.

Debug okno

Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.

App Settings

The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:

Privacy

  • Allow analytics and crash reporting — opt in or out of diagnostics.
  • Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
  • Homoglyph encoding — how look-alike characters in names are handled.

Appearance

  • Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
  • Theme and Language.
  • Show full message timestamps.

Persistence

  • A cache limit for how much history is kept.
  • Export rangetest packets, Export all packets and Export node database.

On their own

  • Node Layout — how much detail each row of the node list shows.
  • Wi-Fi Provisioning for mPWRD-OS — see Connections.
  • Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
  • System AI — appears only where app functions are available; see App Functions.

A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.

O aplikácii

Settings → About carries the app’s own identity rather than the node’s:

Three sections:

  • What is Meshtastic? — a short description of the project.
  • Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
  • Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.

The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.

Acknowledgements

Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.

Troubleshooting remote admin

  • “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
  • Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
  • Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
diff --git a/main/sk-rSK/user/settings-radio-user.html b/main/sk-rSK/user/settings-radio-user.html index 56a8f9f6bc..1ec357f4d0 100644 --- a/main/sk-rSK/user/settings-radio-user.html +++ b/main/sk-rSK/user/settings-radio-user.html @@ -1 +1 @@ - Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Slovenčina
Meshtastic Docs ↗

🌐 Slovenčina — Community translation View in English

Settings — Radio & User

Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How these screens work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Popis
Dlhé Meno Your display name (up to 39 characters)
Krátke Meno 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Unmessageable Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur node (Ham) Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in.

Configuration

Konfigurácia Zariadenia

On Settings → Device configuration → Device.

Setting Popis Predvolené
Device Role Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Rebroadcast Mode How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Node Info Broadcast Interval How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Double Tap as Button Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Enabled
LED Heartbeat Blink the status LED periodically Enabled
Time Zone POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it —
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to —

Konfigurácia LoRa

On Settings → LoRa.

Setting Popis Predvolené
Región Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number Unset (must configure)
Presets Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Transmit Power Transmission power (dBm); 0 = max allowed for region 0 (region max)
Frequency Override Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Use Preset On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead From preset
Coding Rate Manual mode only: 5–8. More redundancy costs airtime From preset
Šírka pásma Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Frequency Slot Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmit Enabled Turning this off makes the node receive-only On
Override Duty Cycle Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
Ignore MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok to MQTT Allow your packets to be forwarded to MQTT by gateways Off
RX Boosted Gain Extra receive gain on SX126x radios; costs a little current Off
PA fan disabled Turn off the power-amplifier fan on hardware that has one Off

The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set.

Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Rýchlosť SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a modem preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Konfigurácia Displeju

On Settings → Device configuration → Display. These control the node’s own screen, not the app’s.

Setting Popis
Screen on for How long the display stays lit before sleeping
Carousel interval How often the node cycles between screens on its own
Display mode Screen layout/density used by the firmware
Display units Metric or Imperial on the node’s screen
Use 12h clock format Show the node’s clock as 12-hour rather than 24-hour
Bold Heading Draw the screen’s heading text in bold
Otoč Obrazovku Rotate the display 180° for an inverted mounting
OLED type Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED
Wake on tap or motion Light the screen when the node is tapped or moved
Compass orientation Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each
Always point north Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Position Config

On Settings → Device configuration → Position.

Setting Popis
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the node asks its GPS for a fix
Broadcastový Interval How often the position is shared with the mesh
Inteligentná poloha Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Fixná Pozícia Use a manually entered latitude, longitude and altitude instead of the GPS
Position Flags A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Power Config

On Settings → Device configuration → Power.

Setting Popis
Enable power saving mode Let the node sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the node stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC multiplier override ratio The correction factor itself, used only when the override is on
Battery INA_2XX I2C address Address of an external INA-series power sensor, if fitted

Konfigurácia siete

On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node.

Setting Popis
Wi-Fi enabled Enable the Wi-Fi node (ESP32 nodes)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Heslo Network password
Ethernet zapnutý Use a wired connection on hardware that has one
IPv4 režim DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP server Time synchronization server
rsyslog server Remote logging server

Network Config with a static IPv4 address entered

Konfigurácia Bluetooth

On Settings → Device configuration → Bluetooth, on nodes with Bluetooth.

Setting Popis
Bluetooth zapnuté Enable/disable BLE radio
Režim párovania Fixed PIN, Random PIN, or No PIN
Pevný PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Security Config

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

Setting Popis
Verejný kľúč Your node’s public key (read-only)
Admin Key Keys permitted to administer this node remotely — up to three
Súkromný kľúč Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it
Regenerate Private Key Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Serial console Serial console over the Stream API
Debug log API enabled Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth
Managed Mode Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.

+ Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Slovenčina
Meshtastic Docs ↗

🌐 Slovenčina — Community translation View in English

Settings — Radio & User

Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How these screens work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Popis
Dlhé Meno Your display name (up to 39 characters)
Krátke Meno 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Unmessageable Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur node (Ham) Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in.

Configuration

Konfigurácia Zariadenia

On Settings → Device configuration → Device.

Setting Popis Predvolené
Device Role Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Rebroadcast Mode How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Node Info Broadcast Interval How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Double Tap as Button Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Enabled
LED Heartbeat Blink the status LED periodically Enabled
Time Zone POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it —
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to —

Konfigurácia LoRa

On Settings → LoRa.

Setting Popis Predvolené
Región Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number Unset (must configure)
Presets Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Transmit Power (dBm) Transmission power; 0 = max allowed for region 0 (region max)
Frequency Override Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Use Preset On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead From preset
Coding Rate Manual mode only: 5–8. More redundancy costs airtime From preset
Šírka pásma Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Frequency Slot Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmit Enabled Turning this off makes the node receive-only On
Override Duty Cycle Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
Ignore MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok to MQTT Allow your packets to be forwarded to MQTT by gateways Off
RX Boosted Gain Extra receive gain on SX126x radios; costs a little current Off
PA fan disabled Turn off the power-amplifier fan on hardware that has one Off

The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set.

Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Rýchlosť SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a modem preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Konfigurácia Displeju

On Settings → Device configuration → Display. These control the node’s own screen, not the app’s.

Setting Popis
Screen on for How long the display stays lit before sleeping
Carousel interval How often the node cycles between screens on its own
Display mode Screen layout/density used by the firmware
Display units Metric or Imperial on the node’s screen
Use 12h clock format Show the node’s clock as 12-hour rather than 24-hour
Bold Heading Draw the screen’s heading text in bold
Otoč Obrazovku Rotate the display 180° for an inverted mounting
OLED type Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED
Wake on tap or motion Light the screen when the node is tapped or moved
Compass orientation Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each
Always point north Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Position Config

On Settings → Device configuration → Position.

Setting Popis
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the node asks its GPS for a fix
Broadcastový Interval How often the position is shared with the mesh
Inteligentná poloha Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Fixná Pozícia Use a manually entered latitude, longitude and altitude instead of the GPS
Position Flags A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Power Config

On Settings → Device configuration → Power.

Setting Popis
Enable power saving mode Let the node sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the node stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC multiplier override ratio The correction factor itself, used only when the override is on
Battery INA_2XX I2C address Address of an external INA-series power sensor, if fitted

Konfigurácia siete

On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node.

Setting Popis
Wi-Fi enabled Enable the Wi-Fi node (ESP32 nodes)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Heslo Network password
Ethernet zapnutý Use a wired connection on hardware that has one
IPv4 režim DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP server Time synchronization server
rsyslog server Remote logging server

Network Config with a static IPv4 address entered

Konfigurácia Bluetooth

On Settings → Device configuration → Bluetooth, on nodes with Bluetooth.

Setting Popis
Bluetooth zapnuté Enable/disable BLE radio
Režim párovania Fixed PIN, Random PIN, or No PIN
Pevný PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Security Config

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

Setting Popis
Verejný kľúč Your node’s public key (read-only)
Admin Key Keys permitted to administer this node remotely — up to three
Súkromný kľúč Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it
Regenerate Private Key Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Serial console Serial console over the Stream API
Debug log API enabled Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth
Managed Mode Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.

diff --git a/main/sl-rSI/user/discovery.html b/main/sl-rSI/user/discovery.html index fb289ce587..aa659510da 100644 --- a/main/sl-rSI/user/discovery.html +++ b/main/sl-rSI/user/discovery.html @@ -5,4 +5,4 @@ ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) -

Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:.

What to look for What it means
All hops show Good SNR (green) Healthy path — messages flow reliably
One hop shows a poor SNR (orange or red) Weak link — this relay segment is fragile
Many hops (4+) Long path — consider repositioning a node to shorten it
Different path on retry Mesh is adapting — multiple routes exist (this is good!)

💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network.

Troubleshooting with Traceroute

  • No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key.
  • Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa.
  • Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position.
  • Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric.

Neighbor Info

The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh.

Enabling Neighbor Info

  1. Navigate to Settings → Module configuration → Neighbor Info.
  2. Enable the module.
  3. Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
  4. Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air.

Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.

Viewing neighbor data

  • Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors.
  • Each neighbor entry shows the node that was directly heard and its signal quality.
  • Combine neighbor data from multiple nodes to understand the full mesh topology.

ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further.

Node list as a discovery tool

The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively.

Finding new nodes

  • Sort by Last heard to see the most recently active nodes at the top.
  • Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes.

Assessing connectivity

  • Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed.
  • Sort by Distance to find nearby nodes and verify they’re reachable.
  • Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge).

Infrastructure audit

  • Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes.
  • Check their signal quality and last-heard times to verify your infrastructure nodes are healthy.

See Nodes for full details on filtering and sorting options.

Tips for Mesh exploration

  • Start with traceroute — it gives you immediate, actionable information about a specific path.
  • Enable Neighbor Info on key nodes — especially routers and repeaters, to build a picture of the backbone.
  • Check the map — node positions on the Map combined with signal data help you understand why some links are strong and others are weak.
  • Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly.
+

Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:.

What to look for What it means
All hops show Good SNR (green) Healthy path — messages flow reliably
One hop shows a poor SNR (orange or red) Weak link — this relay segment is fragile
Many hops (4+) Long path — consider repositioning a node to shorten it
Different path on retry Mesh is adapting — multiple routes exist (this is good!)

💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network.

Troubleshooting with Traceroute

  • No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key.
  • Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa.
  • Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position.
  • Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric.

Neighbor Info

The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh.

Enabling Neighbor Info

  1. Navigate to Settings → Module configuration → Neighbor Info.
  2. Enable the module.
  3. Set Update Interval. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
  4. Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air.

Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.

Viewing neighbor data

  • Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors.
  • Each neighbor entry shows the node that was directly heard and its signal quality.
  • Combine neighbor data from multiple nodes to understand the full mesh topology.

ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further.

Node list as a discovery tool

The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively.

Finding new nodes

  • Sort by Last heard to see the most recently active nodes at the top.
  • Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes.

Assessing connectivity

  • Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed.
  • Sort by Distance to find nearby nodes and verify they’re reachable.
  • Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge).

Infrastructure audit

  • Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes.
  • Check their signal quality and last-heard times to verify your infrastructure nodes are healthy.

See Nodes for full details on filtering and sorting options.

Tips for Mesh exploration

  • Start with traceroute — it gives you immediate, actionable information about a specific path.
  • Enable Neighbor Info on key nodes — especially routers and repeaters, to build a picture of the backbone.
  • Check the map — node positions on the Map combined with signal data help you understand why some links are strong and others are weak.
  • Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly.
diff --git a/main/sl-rSI/user/mqtt.html b/main/sl-rSI/user/mqtt.html index 00b2ab6e83..5a0a438367 100644 --- a/main/sl-rSI/user/mqtt.html +++ b/main/sl-rSI/user/mqtt.html @@ -1,2 +1,2 @@ MQTT | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Slovenščina
Meshtastic Docs ↗

🌐 Slovenščina — Community translation View in English

MQTT

MQTT bridges your Meshtastic mesh network to the internet, enabling long-range communication beyond radio range.

Overview

The MQTT module connects your node to an MQTT broker, allowing:

  • Messages to reach nodes on different physical meshes via the internet
  • Integration with home automation and monitoring systems
  • Publishing node positions to the public Meshtastic map
  • Custom data pipelines for logging and alerting

How It Works 

[Your Node] → Radio → [Gateway Node with Wi-Fi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node]
-

A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh.

Configuration

Enabling MQTT

  1. Navigate to Settings → Module configuration → MQTT.
  2. Enable the MQTT module.
  3. Configure the broker connection:
Setting Opis Default
Address MQTT broker hostname mqtt.meshtastic.org
Username Broker authentication meshdev
Password Broker authentication large4cats
Root topic Base topic for messages msh, which the radio rewrites to msh/<REGION> once you set a region
Encryption enabled Encrypt MQTT payload Enabled
JSON output enabled Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it Disabled
TLS enabled Secure connection to broker Disabled
Map reporting Report position to public map Disabled
Proxy to client enabled Relay MQTT through the connected phone Disabled

Connection Status and Test Connection

The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here.

Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason.

MQTT Proxy on This Phone

If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection.

ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them.

The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration.

Default Meshtastic Broker

The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing.

When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without).

🔒 Privacy: Messages on the public broker are readable by anyone subscribed. Always use channel encryption for private communications.

Private Broker

For better privacy and control, you can run your own MQTT broker:

  • Mosquitto (lightweight, open-source)
  • HiveMQ
  • EMQX

Configure your node to point to your private broker with appropriate credentials.

Map Reporting

When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.

Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.

Reports appear at meshmap.net and similar community map services.

🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published.

Direction Opis
Uplink Messages from mesh → MQTT broker
Downlink Messages from MQTT broker → mesh

Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on.

Message Formats

MQTT carries two payload formats:

Format Opis Use case
Protobuf Binary Meshtastic protobuf encoding Node-to-node mesh bridging
JSON Human-readable JSON on the /2/json/ topic Consumers outside the mesh (dashboards, home automation)

ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads.

Encryption & Privacy

Understanding the layered encryption model:

  1. Channel encryption happens on the mesh before MQTT. If your channel has a PSK, the MQTT payload is already encrypted — the broker and any subscribers see only the ciphertext.
  2. Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard.
  3. TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping.

🔒 Security: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications.

Best Practices

  • Use channel-level encryption (PSK) on channels that bridge to MQTT
  • Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes memory)
  • Use a private broker for sensitive deployments
  • Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh
  • Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back

Troubleshooting

MQTT Not Connecting

  • Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself.
  • Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces.
  • Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443).
  • DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly.

Messages Not Bridging

  • Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway.
  • Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage.
  • Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root.
  • Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway.
  • Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in.
+

A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh.

Configuration

Enabling MQTT

  1. Navigate to Settings → Module configuration → MQTT.
  2. Enable the MQTT module.
  3. Configure the broker connection:
Setting Opis Default
Address MQTT broker hostname mqtt.meshtastic.org
Username Broker authentication meshdev
Password Broker authentication large4cats
Root topic Base topic for messages msh, which the radio rewrites to msh/<REGION> once you set a region
Encryption enabled Encrypt MQTT payload Enabled
JSON output enabled Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it Disabled
TLS enabled Secure connection to broker Disabled
Map reporting Report position to public map Disabled
Proxy to client enabled Relay MQTT through the connected phone Disabled

Connection Status and Test Connection

The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here.

Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason.

MQTT Proxy on This Phone

If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection.

ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them.

The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration.

Default Meshtastic Broker

The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing.

When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without).

🔒 Privacy: Messages on the public broker are readable by anyone subscribed. Always use channel encryption for private communications.

Private Broker

For better privacy and control, you can run your own MQTT broker:

  • Mosquitto (lightweight, open-source)
  • HiveMQ
  • EMQX

Configure your node to point to your private broker with appropriate credentials.

Map Reporting

When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.

Turning it on opens a consent card. Turn on I agree. and choose a Map Publish Interval of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.

Reports appear at meshmap.net and similar community map services.

🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published.

Direction Opis
Uplink Messages from mesh → MQTT broker
Downlink Messages from MQTT broker → mesh

Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on.

Message Formats

MQTT carries two payload formats:

Format Opis Use case
Protobuf Binary Meshtastic protobuf encoding Node-to-node mesh bridging
JSON Human-readable JSON on the /2/json/ topic Consumers outside the mesh (dashboards, home automation)

ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads.

Encryption & Privacy

Understanding the layered encryption model:

  1. Channel encryption happens on the mesh before MQTT. If your channel has a PSK, the MQTT payload is already encrypted — the broker and any subscribers see only the ciphertext.
  2. Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard.
  3. TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping.

🔒 Security: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications.

Best Practices

  • Use channel-level encryption (PSK) on channels that bridge to MQTT
  • Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes memory)
  • Use a private broker for sensitive deployments
  • Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh
  • Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back

Troubleshooting

MQTT Not Connecting

  • Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself.
  • Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces.
  • Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443).
  • DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly.

Messages Not Bridging

  • Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway.
  • Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage.
  • Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root.
  • Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway.
  • Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in.
diff --git a/main/sl-rSI/user/settings-module-admin.html b/main/sl-rSI/user/settings-module-admin.html index 321b654baa..c940169d01 100644 --- a/main/sl-rSI/user/settings-module-admin.html +++ b/main/sl-rSI/user/settings-module-admin.html @@ -1 +1 @@ - Settings — Modules & Admin | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Slovenščina
Meshtastic Docs ↗

🌐 Slovenščina — Community translation View in English

Settings — Modules & Admin

Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.

💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.

Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:

A toggle setting in the on position

A dropdown setting, expanded to show its list of options

A text field setting with a value entered

A module settings card with its title and grouped controls

Nastavitev modula

Every module lives under Settings → Module configuration.

⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes.

MQTT module

Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.

Setting Opis
MQTT enabled Toggle MQTT bridge
Address MQTT broker address
Username Authentication username
Password Authentication password
Encryption enabled Encrypt MQTT payloads
JSON output enabled Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS enabled Use secure connection
Root topic Base MQTT topic path
Proxy to client enabled Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy on this phone The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT
Map reporting Publish position to the public map — see the Map reporting group that follows

Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:

Setting Opis
I agree. Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map reporting interval (seconds) How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered

See MQTT for a detailed usage guide including encryption, privacy, and broker setup.

Serial module

Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.

Setting Opis
Serial enabled Activate serial communication
Echo enabled Echo received serial data back
Serial mode Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX GPIO pins for the serial connection
Serial baud rate Port speed
Časovna omejitev How long to wait before considering an incoming message complete
Override console serial port Take over the port the debug console normally uses

External Notification module

Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.

There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.

Setting Opis
External notification enabled Master toggle for the module
Alert message LED / buzzer / vibra Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra Which outputs fire on a received bell character
Output LED (GPIO) Pin the LED is wired to
Output LED active high Whether the LED pin is active high or low
Output buzzer (GPIO) Pin the buzzer is wired to
Output vibra (GPIO) Pin the vibration motor is wired to
Use PWM buzzer Drive the buzzer with PWM, which allows tones rather than a single pitch
Use I2S as buzzer Send the alert through an I2S audio output instead
Output duration (milliseconds) How long a single alert lasts
Nag timeout (seconds) Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Ringtone The tone played on a PWM buzzer, in RTTTL. Can be imported from a file

Store & Forward module

Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.

Setting Opis
Store & Forward enabled Activate store and forward
Heartbeat Periodically announce this node’s store-and-forward capability
Number of records Maximum stored messages
History return max Max messages to replay
History return window Time window for replay
Server Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)

💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.

Range Test module

⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.

Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.

Setting Opis
Range test enabled Activate range testing
Sender message interval (seconds) Time between test transmissions, chosen from a dropdown of fixed intervals
Save .CSV in storage (ESP32 only) Log received test data to the node’s own filesystem. ESP32 hardware only

Telemetry module

Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).

Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.

Setting Opis
Send Device Telemetry Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval How often to report battery, uptime and channel utilization
Environment metrics module enabled Report the attached environment sensors
Environment metrics update interval How often to report them
Environment metrics on-screen enabled Also show these readings on the device’s own display
Environment metrics use Fahrenheit Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Air quality metrics module enabled Report particulate and CO₂ sensor data
Air quality metrics update interval How often to report them
Power metrics module enabled Report the per-channel voltage and current readings
Power metrics update interval How often to report them
Power metrics on-screen enabled Also show power readings on the device’s display

See Telemetry & Sensors for supported sensors and configuration recommendations.

Canned Message module

Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.

Setting Opis
Canned message enabled ⚠️ Deprecated in the protobuf schema
Messages Newline-separated list of messages
Send bell Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Rotary encoder #1 enabled Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port The three pins the encoder is wired to
Generate input event on Press / CW / CCW Which key event each encoder action produces
Up/Down/Select input enabled A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source ⚠️ Deprecated in the protobuf schema

Audio module

Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.

Setting Opis
CODEC 2 enabled Activate audio module
CODEC2 sample rate Audio quality/bandwidth tradeoff
PTT pin GPIO pin for the push-to-talk button
I2S word select GPIO pin for I2S WS
I2S data in GPIO pin for I2S DIN
I2S data out GPIO pin for I2S DOUT
I2S clock GPIO pin for the I2S bit clock

ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.

Remote Hardware module

GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.

⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.

Setting Opis
Remote Hardware enabled Activate remote GPIO access
Allow undefined pin access Allow access to any GPIO pin (security risk)
Available pins Up to 4 GPIO pins this node exposes for remote read/write

Neighbor Info module

Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.

Setting Opis
Neighbor Info enabled Activate neighbor broadcasting
Update interval (seconds) How often to broadcast neighbor list
Transmit over LoRa Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name

See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.

Ambient Lighting module

Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.

Setting Opis
LED state Turn the LED on or off
Current LED current limit (0–31)
Red / Green / Blue Individual color channel values (0–255)

Detection Sensor module

Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.

Setting Opis
Detection Sensor enabled Activate detection sensor
GPIO pin to monitor GPIO pin connected to sensor
Detection trigger type How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Use INPUT_PULLUP mode Enable the pin’s internal pull-up resistor
Minimum broadcast (seconds) Minimum time between alert broadcasts
State broadcast (seconds) Periodic state broadcast interval
Send bell with alert message Include bell character in alerts
Friendly name Custom name for this sensor

Paxcounter module

People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.

Setting Opis
Paxcounter enabled Activate people counting
Update interval (seconds) How often to report counts
Wi-Fi RSSI threshold Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE RSSI threshold The same cut-off for BLE advertisements (defaults to −80 dBm)

💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.

Status Message module

The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.

Mesh Beacon module

Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.

TAK module

Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.

Administracija

Administracija na daljavo

Remotely configure nodes that share your admin key:

  1. Select the target node in the node list.
  2. Navigate to Settings for that node.
  3. Modify configuration.
  4. Tap Save — changes are sent over the mesh.

⚠️ Important: Requires an admin key configured on both your node and the target node.

Device Actions

Settings → Administration holds five one-shot actions, each behind a confirmation dialog:

Action What it does
Set time Sends your phone’s clock to the node
Ponovni zagon Restarts the node
Ugasni Powers the node down
Povrnitev tovarniških nastavitev Returns every setting to its factory default
Ponastavi NodeDB Clears the node database. This dialog carries a Preserve Favorites? switch

⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.

Backup & Restore

Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.

Advanced

Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.

Clean Node Database

Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.

  • Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
  • Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.

The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.

Plošča za odpravljanje napak

Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.

App Settings

The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:

Privacy

  • Allow analytics and crash reporting — opt in or out of diagnostics.
  • Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
  • Homoglyph encoding — how look-alike characters in names are handled.

Appearance

  • Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
  • Theme and Language.
  • Show full message timestamps.

Persistence

  • A cache limit for how much history is kept.
  • Export rangetest packets, Export all packets and Export node database.

On their own

  • Node Layout — how much detail each row of the node list shows.
  • Wi-Fi Provisioning for mPWRD-OS — see Connections.
  • Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
  • System AI — appears only where app functions are available; see App Functions.

A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.

O programu

Settings → About carries the app’s own identity rather than the node’s:

Three sections:

  • What is Meshtastic? — a short description of the project.
  • Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
  • Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.

The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.

Acknowledgements

Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.

Troubleshooting remote admin

  • “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
  • Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
  • Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
+ Settings — Modules & Admin | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Slovenščina
Meshtastic Docs ↗

🌐 Slovenščina — Community translation View in English

Settings — Modules & Admin

Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.

💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.

Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:

A toggle setting in the on position

A dropdown setting, expanded to show its list of options

A text field setting with a value entered

A module settings card with its title and grouped controls

Nastavitev modula

Every module lives under Settings → Module configuration.

⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes.

MQTT module

Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.

Setting Opis
MQTT enabled Toggle MQTT bridge
Address MQTT broker address
Username Authentication username
Password Authentication password
Encryption enabled Encrypt MQTT payloads
JSON output enabled Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS enabled Use secure connection
Root topic Base MQTT topic path
Proxy to client enabled Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy on this phone The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT
Map reporting Publish position to the public map — see the Map reporting group that follows

Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:

Setting Opis
I agree. Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered

See MQTT for a detailed usage guide including encryption, privacy, and broker setup.

Serial module

Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.

Setting Opis
Serial enabled Activate serial communication
Echo enabled Echo received serial data back
Serial mode Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX GPIO pins for the serial connection
Serial baud rate Port speed
Časovna omejitev How long to wait before considering an incoming message complete
Override console serial port Take over the port the debug console normally uses

External Notification module

Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.

There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.

Setting Opis
External notification enabled Master toggle for the module
Alert message LED / buzzer / vibra Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra Which outputs fire on a received bell character
Output LED (GPIO) Pin the LED is wired to
Output LED active high Whether the LED pin is active high or low
Output buzzer (GPIO) Pin the buzzer is wired to
Output vibra (GPIO) Pin the vibration motor is wired to
Use PWM buzzer Drive the buzzer with PWM, which allows tones rather than a single pitch
Use I2S as buzzer Send the alert through an I2S audio output instead
GPIO Output Duration How long a single alert lasts
Nag Timeout Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Ringtone The tone played on a PWM buzzer, in RTTTL. Can be imported from a file

Store & Forward module

Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.

Setting Opis
Store & Forward enabled Activate store and forward
Heartbeat Periodically announce this node’s store-and-forward capability
Number of records Maximum stored messages
History return max Max messages to replay
History return window Time window for replay
Server Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)

💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.

Range Test module

⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.

Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.

Setting Opis
Range test enabled Activate range testing
Sender Interval Time between test transmissions, chosen from a dropdown of fixed intervals
Save .CSV in storage (ESP32 only) Log received test data to the node’s own filesystem. ESP32 hardware only

Telemetry module

Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).

Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.

Setting Opis
Send Device Telemetry Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval How often to report battery, uptime and channel utilization
Environment metrics module enabled Report the attached environment sensors
Environment metrics update interval How often to report them
Environment metrics on-screen enabled Also show these readings on the device’s own display
Environment metrics use Fahrenheit Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Air quality metrics module enabled Report particulate and CO₂ sensor data
Air quality metrics update interval How often to report them
Power metrics module enabled Report the per-channel voltage and current readings
Power metrics update interval How often to report them
Power metrics on-screen enabled Also show power readings on the device’s display

See Telemetry & Sensors for supported sensors and configuration recommendations.

Canned Message module

Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.

Setting Opis
Canned message enabled ⚠️ Deprecated in the protobuf schema
Messages Newline-separated list of messages
Send bell Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Rotary encoder #1 enabled Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port The three pins the encoder is wired to
Generate input event on Press / CW / CCW Which key event each encoder action produces
Up/Down/Select input enabled A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source ⚠️ Deprecated in the protobuf schema

Audio module

Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.

Setting Opis
CODEC 2 enabled Activate audio module
CODEC2 sample rate Audio quality/bandwidth tradeoff
PTT pin GPIO pin for the push-to-talk button
I2S word select GPIO pin for I2S WS
I2S data in GPIO pin for I2S DIN
I2S data out GPIO pin for I2S DOUT
I2S clock GPIO pin for the I2S bit clock

ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.

Remote Hardware module

GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.

⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.

Setting Opis
Remote Hardware enabled Activate remote GPIO access
Allow undefined pin access Allow access to any GPIO pin (security risk)
Available pins Up to 4 GPIO pins this node exposes for remote read/write

Neighbor Info module

Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.

Setting Opis
Neighbor Info enabled Activate neighbor broadcasting
Update Interval How often to broadcast neighbor list
Transmit over LoRa Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name

See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.

Ambient Lighting module

Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.

Setting Opis
LED state Turn the LED on or off
Current LED current limit (0–31)
Red / Green / Blue Individual color channel values (0–255)

Detection Sensor module

Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.

Setting Opis
Detection Sensor enabled Activate detection sensor
GPIO pin to monitor GPIO pin connected to sensor
Detection trigger type How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Use INPUT_PULLUP mode Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts Minimum time between alert broadcasts
State Broadcast Interval Periodic state broadcast interval
Send bell with alert message Include bell character in alerts
Friendly name Custom name for this sensor

Paxcounter module

People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.

Setting Opis
Paxcounter enabled Activate people counting
Update Interval How often to report counts
WiFi Threshold (dBm) Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm) The same cut-off for BLE advertisements (defaults to −80 dBm)

💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.

Status Message module

The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.

Mesh Beacon module

Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.

TAK module

Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.

Administracija

Administracija na daljavo

Remotely configure nodes that share your admin key:

  1. Select the target node in the node list.
  2. Navigate to Settings for that node.
  3. Modify configuration.
  4. Tap Save — changes are sent over the mesh.

⚠️ Important: Requires an admin key configured on both your node and the target node.

Device Actions

Settings → Administration holds five one-shot actions, each behind a confirmation dialog:

Action What it does
Set time Sends your phone’s clock to the node
Ponovni zagon Restarts the node
Ugasni Powers the node down
Povrnitev tovarniških nastavitev Returns every setting to its factory default
Ponastavi NodeDB Clears the node database. This dialog carries a Preserve Favorites? switch

⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.

Backup & Restore

Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.

Advanced

Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.

Clean Node Database

Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.

  • Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
  • Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.

The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.

Plošča za odpravljanje napak

Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.

App Settings

The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:

Privacy

  • Allow analytics and crash reporting — opt in or out of diagnostics.
  • Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
  • Homoglyph encoding — how look-alike characters in names are handled.

Appearance

  • Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
  • Theme and Language.
  • Show full message timestamps.

Persistence

  • A cache limit for how much history is kept.
  • Export rangetest packets, Export all packets and Export node database.

On their own

  • Node Layout — how much detail each row of the node list shows.
  • Wi-Fi Provisioning for mPWRD-OS — see Connections.
  • Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
  • System AI — appears only where app functions are available; see App Functions.

A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.

O programu

Settings → About carries the app’s own identity rather than the node’s:

Three sections:

  • What is Meshtastic? — a short description of the project.
  • Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
  • Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.

The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.

Acknowledgements

Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.

Troubleshooting remote admin

  • “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
  • Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
  • Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
diff --git a/main/sl-rSI/user/settings-radio-user.html b/main/sl-rSI/user/settings-radio-user.html index 628f928b68..1635ef2528 100644 --- a/main/sl-rSI/user/settings-radio-user.html +++ b/main/sl-rSI/user/settings-radio-user.html @@ -1 +1 @@ - Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Slovenščina
Meshtastic Docs ↗

🌐 Slovenščina — Community translation View in English

Settings — Radio & User

Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How these screens work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Opis
Long Name Your display name (up to 39 characters)
Short Name 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Unmessageable Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur node (Ham) Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in.

Configuration

Device Config

On Settings → Device configuration → Device.

Setting Opis Default
Device Role Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Rebroadcast Mode How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Node Info Broadcast Interval How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Double Tap as Button Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Enabled
LED Heartbeat Blink the status LED periodically Enabled
Time Zone POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it —
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to —

LoRa Config

On Settings → LoRa.

Setting Opis Default
Regija Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number Unset (must configure)
Presets Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Transmit Power Transmission power (dBm); 0 = max allowed for region 0 (region max)
Frequency Override Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Use Preset On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead From preset
Coding Rate Manual mode only: 5–8. More redundancy costs airtime From preset
Bandwidth Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Frequency Slot Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmit Enabled Turning this off makes the node receive-only On
Override Duty Cycle Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
Ignore MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok to MQTT Allow your packets to be forwarded to MQTT by gateways Off
RX Boosted Gain Extra receive gain on SX126x radios; costs a little current Off
PA fan disabled Turn off the power-amplifier fan on hardware that has one Off

The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set.

Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Speed SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a modem preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Display Config

On Settings → Device configuration → Display. These control the node’s own screen, not the app’s.

Setting Opis
Screen on for How long the display stays lit before sleeping
Carousel interval How often the node cycles between screens on its own
Display mode Screen layout/density used by the firmware
Display units Metric or Imperial on the node’s screen
Use 12h clock format Show the node’s clock as 12-hour rather than 24-hour
Bold Heading Draw the screen’s heading text in bold
Flip screen Rotate the display 180° for an inverted mounting
OLED type Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED
Wake on tap or motion Light the screen when the node is tapped or moved
Compass orientation Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each
Always point north Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Position Config

On Settings → Device configuration → Position.

Setting Opis
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the node asks its GPS for a fix
Broadcast Interval How often the position is shared with the mesh
Smart Position Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Fixed Position Use a manually entered latitude, longitude and altitude instead of the GPS
Position Flags A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Power Config

On Settings → Device configuration → Power.

Setting Opis
Enable power saving mode Let the node sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the node stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC multiplier override ratio The correction factor itself, used only when the override is on
Battery INA_2XX I2C address Address of an external INA-series power sensor, if fitted

Network Config

On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node.

Setting Opis
Wi-Fi enabled Enable the Wi-Fi node (ESP32 nodes)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Password Network password
Ethernet enabled Use a wired connection on hardware that has one
IPv4 mode DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP server Time synchronization server
rsyslog server Remote logging server

Network Config with a static IPv4 address entered

Bluetooth Config

On Settings → Device configuration → Bluetooth, on nodes with Bluetooth.

Setting Opis
Bluetooth enabled Enable/disable BLE radio
Pairing mode Fixed PIN, Random PIN, or No PIN
Fixed PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Security Config

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

Setting Opis
Javni ključ Your node’s public key (read-only)
Admin Key Keys permitted to administer this node remotely — up to three
Zasebni ključ Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it
Regenerate Private Key Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Serial console Serial console over the Stream API
Debug log API enabled Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth
Managed Mode Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.

+ Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Slovenščina
Meshtastic Docs ↗

🌐 Slovenščina — Community translation View in English

Settings — Radio & User

Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How these screens work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Opis
Long Name Your display name (up to 39 characters)
Short Name 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Unmessageable Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur node (Ham) Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in.

Configuration

Device Config

On Settings → Device configuration → Device.

Setting Opis Default
Device Role Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Rebroadcast Mode How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Node Info Broadcast Interval How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Double Tap as Button Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Enabled
LED Heartbeat Blink the status LED periodically Enabled
Time Zone POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it —
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to —

LoRa Config

On Settings → LoRa.

Setting Opis Default
Regija Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number Unset (must configure)
Presets Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Transmit Power (dBm) Transmission power; 0 = max allowed for region 0 (region max)
Frequency Override Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Use Preset On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead From preset
Coding Rate Manual mode only: 5–8. More redundancy costs airtime From preset
Bandwidth Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Frequency Slot Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmit Enabled Turning this off makes the node receive-only On
Override Duty Cycle Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
Ignore MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok to MQTT Allow your packets to be forwarded to MQTT by gateways Off
RX Boosted Gain Extra receive gain on SX126x radios; costs a little current Off
PA fan disabled Turn off the power-amplifier fan on hardware that has one Off

The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set.

Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Speed SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a modem preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Display Config

On Settings → Device configuration → Display. These control the node’s own screen, not the app’s.

Setting Opis
Screen on for How long the display stays lit before sleeping
Carousel interval How often the node cycles between screens on its own
Display mode Screen layout/density used by the firmware
Display units Metric or Imperial on the node’s screen
Use 12h clock format Show the node’s clock as 12-hour rather than 24-hour
Bold Heading Draw the screen’s heading text in bold
Flip screen Rotate the display 180° for an inverted mounting
OLED type Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED
Wake on tap or motion Light the screen when the node is tapped or moved
Compass orientation Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each
Always point north Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Position Config

On Settings → Device configuration → Position.

Setting Opis
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the node asks its GPS for a fix
Broadcast Interval How often the position is shared with the mesh
Smart Position Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Fixed Position Use a manually entered latitude, longitude and altitude instead of the GPS
Position Flags A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Power Config

On Settings → Device configuration → Power.

Setting Opis
Enable power saving mode Let the node sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the node stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC multiplier override ratio The correction factor itself, used only when the override is on
Battery INA_2XX I2C address Address of an external INA-series power sensor, if fitted

Network Config

On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node.

Setting Opis
Wi-Fi enabled Enable the Wi-Fi node (ESP32 nodes)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Password Network password
Ethernet enabled Use a wired connection on hardware that has one
IPv4 mode DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP server Time synchronization server
rsyslog server Remote logging server

Network Config with a static IPv4 address entered

Bluetooth Config

On Settings → Device configuration → Bluetooth, on nodes with Bluetooth.

Setting Opis
Bluetooth enabled Enable/disable BLE radio
Pairing mode Fixed PIN, Random PIN, or No PIN
Fixed PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Security Config

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

Setting Opis
Javni ključ Your node’s public key (read-only)
Admin Key Keys permitted to administer this node remotely — up to three
Zasebni ključ Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it
Regenerate Private Key Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Serial console Serial console over the Stream API
Debug log API enabled Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth
Managed Mode Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.

diff --git a/main/sq-rAL/user/discovery.html b/main/sq-rAL/user/discovery.html index 8d6bb813d5..3245937bf3 100644 --- a/main/sq-rAL/user/discovery.html +++ b/main/sq-rAL/user/discovery.html @@ -5,4 +5,4 @@ ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) -

Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:.

What to look for What it means
All hops show Good SNR (green) Healthy path — messages flow reliably
One hop shows a poor SNR (orange or red) Weak link — this relay segment is fragile
Many hops (4+) Long path — consider repositioning a node to shorten it
Different path on retry Mesh is adapting — multiple routes exist (this is good!)

💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network.

Troubleshooting with Traceroute

  • No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key.
  • Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa.
  • Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position.
  • Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric.

Neighbor Info

The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh.

Enabling Neighbor Info

  1. Navigate to Settings → Module configuration → Neighbor Info.
  2. Enable the module.
  3. Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
  4. Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air.

Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.

Viewing neighbor data

  • Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors.
  • Each neighbor entry shows the node that was directly heard and its signal quality.
  • Combine neighbor data from multiple nodes to understand the full mesh topology.

ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further.

Node list as a discovery tool

The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively.

Finding new nodes

  • Sort by Last heard to see the most recently active nodes at the top.
  • Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes.

Assessing connectivity

  • Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed.
  • Sort by Distance to find nearby nodes and verify they’re reachable.
  • Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge).

Infrastructure audit

  • Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes.
  • Check their signal quality and last-heard times to verify your infrastructure nodes are healthy.

See Nodes for full details on filtering and sorting options.

Tips for Mesh exploration

  • Start with traceroute — it gives you immediate, actionable information about a specific path.
  • Enable Neighbor Info on key nodes — especially routers and repeaters, to build a picture of the backbone.
  • Check the map — node positions on the Map combined with signal data help you understand why some links are strong and others are weak.
  • Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly.
+

Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:.

What to look for What it means
All hops show Good SNR (green) Healthy path — messages flow reliably
One hop shows a poor SNR (orange or red) Weak link — this relay segment is fragile
Many hops (4+) Long path — consider repositioning a node to shorten it
Different path on retry Mesh is adapting — multiple routes exist (this is good!)

💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network.

Troubleshooting with Traceroute

  • No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key.
  • Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa.
  • Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position.
  • Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric.

Neighbor Info

The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh.

Enabling Neighbor Info

  1. Navigate to Settings → Module configuration → Neighbor Info.
  2. Enable the module.
  3. Set Update Interval. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
  4. Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air.

Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.

Viewing neighbor data

  • Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors.
  • Each neighbor entry shows the node that was directly heard and its signal quality.
  • Combine neighbor data from multiple nodes to understand the full mesh topology.

ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further.

Node list as a discovery tool

The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively.

Finding new nodes

  • Sort by Last heard to see the most recently active nodes at the top.
  • Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes.

Assessing connectivity

  • Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed.
  • Sort by Distance to find nearby nodes and verify they’re reachable.
  • Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge).

Infrastructure audit

  • Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes.
  • Check their signal quality and last-heard times to verify your infrastructure nodes are healthy.

See Nodes for full details on filtering and sorting options.

Tips for Mesh exploration

  • Start with traceroute — it gives you immediate, actionable information about a specific path.
  • Enable Neighbor Info on key nodes — especially routers and repeaters, to build a picture of the backbone.
  • Check the map — node positions on the Map combined with signal data help you understand why some links are strong and others are weak.
  • Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly.
diff --git a/main/sq-rAL/user/mqtt.html b/main/sq-rAL/user/mqtt.html index acb359b31a..8de838ee84 100644 --- a/main/sq-rAL/user/mqtt.html +++ b/main/sq-rAL/user/mqtt.html @@ -1,2 +1,2 @@ MQTT | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Shqip
Meshtastic Docs ↗

🌐 Shqip — Community translation View in English

MQTT

MQTT bridges your Meshtastic mesh network to the internet, enabling long-range communication beyond radio range.

Overview

The MQTT module connects your node to an MQTT broker, allowing:

  • Messages to reach nodes on different physical meshes via the internet
  • Integration with home automation and monitoring systems
  • Publishing node positions to the public Meshtastic map
  • Custom data pipelines for logging and alerting

How It Works 

[Your Node] → Radio → [Gateway Node with Wi-Fi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node]
-

A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh.

Configuration

Enabling MQTT

  1. Navigate to Settings → Module configuration → MQTT.
  2. Enable the MQTT module.
  3. Configure the broker connection:
Setting Përshkrimi Default
Address MQTT broker hostname mqtt.meshtastic.org
Username Broker authentication meshdev
Password Broker authentication large4cats
Root topic Base topic for messages msh, which the radio rewrites to msh/<REGION> once you set a region
Encryption enabled Encrypt MQTT payload Enabled
JSON output enabled Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it Disabled
TLS enabled Secure connection to broker Disabled
Map reporting Report position to public map Disabled
Proxy to client enabled Relay MQTT through the connected phone Disabled

Connection Status and Test Connection

The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here.

Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason.

MQTT Proxy on This Phone

If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection.

ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them.

The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration.

Default Meshtastic Broker

The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing.

When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without).

🔒 Privacy: Messages on the public broker are readable by anyone subscribed. Always use channel encryption for private communications.

Private Broker

For better privacy and control, you can run your own MQTT broker:

  • Mosquitto (lightweight, open-source)
  • HiveMQ
  • EMQX

Configure your node to point to your private broker with appropriate credentials.

Map Reporting

When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.

Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.

Reports appear at meshmap.net and similar community map services.

🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published.

Direction Përshkrimi
Uplink Messages from mesh → MQTT broker
Downlink Messages from MQTT broker → mesh

Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on.

Message Formats

MQTT carries two payload formats:

Format Përshkrimi Use case
Protobuf Binary Meshtastic protobuf encoding Node-to-node mesh bridging
JSON Human-readable JSON on the /2/json/ topic Consumers outside the mesh (dashboards, home automation)

ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads.

Encryption & Privacy

Understanding the layered encryption model:

  1. Channel encryption happens on the mesh before MQTT. If your channel has a PSK, the MQTT payload is already encrypted — the broker and any subscribers see only the ciphertext.
  2. Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard.
  3. TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping.

🔒 Security: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications.

Best Practices

  • Use channel-level encryption (PSK) on channels that bridge to MQTT
  • Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes memory)
  • Use a private broker for sensitive deployments
  • Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh
  • Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back

Troubleshooting

MQTT Not Connecting

  • Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself.
  • Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces.
  • Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443).
  • DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly.

Messages Not Bridging

  • Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway.
  • Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage.
  • Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root.
  • Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway.
  • Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in.
+

A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh.

Configuration

Enabling MQTT

  1. Navigate to Settings → Module configuration → MQTT.
  2. Enable the MQTT module.
  3. Configure the broker connection:
Setting Përshkrimi Default
Address MQTT broker hostname mqtt.meshtastic.org
Username Broker authentication meshdev
Password Broker authentication large4cats
Root topic Base topic for messages msh, which the radio rewrites to msh/<REGION> once you set a region
Encryption enabled Encrypt MQTT payload Enabled
JSON output enabled Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it Disabled
TLS enabled Secure connection to broker Disabled
Map reporting Report position to public map Disabled
Proxy to client enabled Relay MQTT through the connected phone Disabled

Connection Status and Test Connection

The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here.

Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason.

MQTT Proxy on This Phone

If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection.

ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them.

The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration.

Default Meshtastic Broker

The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing.

When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without).

🔒 Privacy: Messages on the public broker are readable by anyone subscribed. Always use channel encryption for private communications.

Private Broker

For better privacy and control, you can run your own MQTT broker:

  • Mosquitto (lightweight, open-source)
  • HiveMQ
  • EMQX

Configure your node to point to your private broker with appropriate credentials.

Map Reporting

When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.

Turning it on opens a consent card. Turn on I agree. and choose a Map Publish Interval of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.

Reports appear at meshmap.net and similar community map services.

🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published.

Direction Përshkrimi
Uplink Messages from mesh → MQTT broker
Downlink Messages from MQTT broker → mesh

Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on.

Message Formats

MQTT carries two payload formats:

Format Përshkrimi Use case
Protobuf Binary Meshtastic protobuf encoding Node-to-node mesh bridging
JSON Human-readable JSON on the /2/json/ topic Consumers outside the mesh (dashboards, home automation)

ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads.

Encryption & Privacy

Understanding the layered encryption model:

  1. Channel encryption happens on the mesh before MQTT. If your channel has a PSK, the MQTT payload is already encrypted — the broker and any subscribers see only the ciphertext.
  2. Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard.
  3. TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping.

🔒 Security: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications.

Best Practices

  • Use channel-level encryption (PSK) on channels that bridge to MQTT
  • Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes memory)
  • Use a private broker for sensitive deployments
  • Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh
  • Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back

Troubleshooting

MQTT Not Connecting

  • Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself.
  • Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces.
  • Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443).
  • DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly.

Messages Not Bridging

  • Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway.
  • Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage.
  • Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root.
  • Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway.
  • Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in.
diff --git a/main/sq-rAL/user/settings-module-admin.html b/main/sq-rAL/user/settings-module-admin.html index 323ecd0fb0..bad978e43d 100644 --- a/main/sq-rAL/user/settings-module-admin.html +++ b/main/sq-rAL/user/settings-module-admin.html @@ -1 +1 @@ - Settings — Modules & Admin | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Shqip
Meshtastic Docs ↗

🌐 Shqip — Community translation View in English

Settings — Modules & Admin

Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.

💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.

Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:

A toggle setting in the on position

A dropdown setting, expanded to show its list of options

A text field setting with a value entered

A module settings card with its title and grouped controls

Konfigurimi i modulit

Every module lives under Settings → Module configuration.

⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes.

MQTT module

Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.

Setting Përshkrimi
MQTT enabled Toggle MQTT bridge
Address MQTT broker address
Username Authentication username
Password Authentication password
Encryption enabled Encrypt MQTT payloads
JSON output enabled Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS enabled Use secure connection
Root topic Base MQTT topic path
Proxy to client enabled Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy on this phone The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT
Map reporting Publish position to the public map — see the Map reporting group that follows

Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:

Setting Përshkrimi
I agree. Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map reporting interval (seconds) How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered

See MQTT for a detailed usage guide including encryption, privacy, and broker setup.

Serial module

Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.

Setting Përshkrimi
Serial enabled Activate serial communication
Echo enabled Echo received serial data back
Serial mode Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX GPIO pins for the serial connection
Serial baud rate Port speed
Koha e skaduar How long to wait before considering an incoming message complete
Override console serial port Take over the port the debug console normally uses

External Notification module

Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.

There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.

Setting Përshkrimi
External notification enabled Master toggle for the module
Alert message LED / buzzer / vibra Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra Which outputs fire on a received bell character
Output LED (GPIO) Pin the LED is wired to
Output LED active high Whether the LED pin is active high or low
Output buzzer (GPIO) Pin the buzzer is wired to
Output vibra (GPIO) Pin the vibration motor is wired to
Use PWM buzzer Drive the buzzer with PWM, which allows tones rather than a single pitch
Use I2S as buzzer Send the alert through an I2S audio output instead
Output duration (milliseconds) How long a single alert lasts
Nag timeout (seconds) Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Ringtone The tone played on a PWM buzzer, in RTTTL. Can be imported from a file

Store & Forward module

Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.

Setting Përshkrimi
Store & Forward enabled Activate store and forward
Heartbeat Periodically announce this node’s store-and-forward capability
Number of records Maximum stored messages
History return max Max messages to replay
History return window Time window for replay
Server Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)

💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.

Range Test module

⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.

Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.

Setting Përshkrimi
Range test enabled Activate range testing
Sender message interval (seconds) Time between test transmissions, chosen from a dropdown of fixed intervals
Save .CSV in storage (ESP32 only) Log received test data to the node’s own filesystem. ESP32 hardware only

Telemetry module

Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).

Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.

Setting Përshkrimi
Send Device Telemetry Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval How often to report battery, uptime and channel utilization
Environment metrics module enabled Report the attached environment sensors
Environment metrics update interval How often to report them
Environment metrics on-screen enabled Also show these readings on the device’s own display
Environment metrics use Fahrenheit Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Air quality metrics module enabled Report particulate and CO₂ sensor data
Air quality metrics update interval How often to report them
Power metrics module enabled Report the per-channel voltage and current readings
Power metrics update interval How often to report them
Power metrics on-screen enabled Also show power readings on the device’s display

See Telemetry & Sensors for supported sensors and configuration recommendations.

Canned Message module

Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.

Setting Përshkrimi
Canned message enabled ⚠️ Deprecated in the protobuf schema
訊息 Newline-separated list of messages
Send bell Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Rotary encoder #1 enabled Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port The three pins the encoder is wired to
Generate input event on Press / CW / CCW Which key event each encoder action produces
Up/Down/Select input enabled A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source ⚠️ Deprecated in the protobuf schema

Audio module

Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.

Setting Përshkrimi
CODEC 2 enabled Activate audio module
CODEC2 sample rate Audio quality/bandwidth tradeoff
PTT pin GPIO pin for the push-to-talk button
I2S word select GPIO pin for I2S WS
I2S data in GPIO pin for I2S DIN
I2S data out GPIO pin for I2S DOUT
I2S clock GPIO pin for the I2S bit clock

ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.

Remote Hardware module

GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.

⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.

Setting Përshkrimi
Remote Hardware enabled Activate remote GPIO access
Allow undefined pin access Allow access to any GPIO pin (security risk)
Available pins Up to 4 GPIO pins this node exposes for remote read/write

Neighbor Info module

Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.

Setting Përshkrimi
Neighbor Info enabled Activate neighbor broadcasting
Update interval (seconds) How often to broadcast neighbor list
Transmit over LoRa Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name

See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.

Ambient Lighting module

Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.

Setting Përshkrimi
LED state Turn the LED on or off
Current LED current limit (0–31)
Red / Green / Blue Individual color channel values (0–255)

Detection Sensor module

Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.

Setting Përshkrimi
Detection Sensor enabled Activate detection sensor
GPIO pin to monitor GPIO pin connected to sensor
Detection trigger type How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Use INPUT_PULLUP mode Enable the pin’s internal pull-up resistor
Minimum broadcast (seconds) Minimum time between alert broadcasts
State broadcast (seconds) Periodic state broadcast interval
Send bell with alert message Include bell character in alerts
Friendly name Custom name for this sensor

Paxcounter module

People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.

Setting Përshkrimi
Paxcounter enabled Activate people counting
Update interval (seconds) How often to report counts
Wi-Fi RSSI threshold Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE RSSI threshold The same cut-off for BLE advertisements (defaults to −80 dBm)

💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.

Status Message module

The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.

Mesh Beacon module

Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.

TAK module

Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.

Administratë

Administratë e Largët

Remotely configure nodes that share your admin key:

  1. Select the target node in the node list.
  2. Navigate to Settings for that node.
  3. Modify configuration.
  4. Tap Save — changes are sent over the mesh.

⚠️ Important: Requires an admin key configured on both your node and the target node.

Device Actions

Settings → Administration holds five one-shot actions, each behind a confirmation dialog:

Action What it does
Set time Sends your phone’s clock to the node
Rindiz Restarts the node
Fik Powers the node down
Përditësim i fabrikës Returns every setting to its factory default
Përditësimi i NodeDB Clears the node database. This dialog carries a Preserve Favorites? switch

⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.

Backup & Restore

Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.

Advanced

Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.

Clean Node Database

Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.

  • Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
  • Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.

The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.

Paneli i debug-ut

Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.

App Settings

The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:

Privacy

  • Allow analytics and crash reporting — opt in or out of diagnostics.
  • Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
  • Homoglyph encoding — how look-alike characters in names are handled.

Appearance

  • Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
  • Theme and Language.
  • Show full message timestamps.

Persistence

  • A cache limit for how much history is kept.
  • Export rangetest packets, Export all packets and Export node database.

On their own

  • Node Layout — how much detail each row of the node list shows.
  • Wi-Fi Provisioning for mPWRD-OS — see Connections.
  • Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
  • System AI — appears only where app functions are available; see App Functions.

A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.

Rreth

Settings → About carries the app’s own identity rather than the node’s:

Three sections:

  • What is Meshtastic? — a short description of the project.
  • Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
  • Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.

The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.

Acknowledgements

Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.

Troubleshooting remote admin

  • “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
  • Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
  • Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
+ Settings — Modules & Admin | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Shqip
Meshtastic Docs ↗

🌐 Shqip — Community translation View in English

Settings — Modules & Admin

Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.

💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.

Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:

A toggle setting in the on position

A dropdown setting, expanded to show its list of options

A text field setting with a value entered

A module settings card with its title and grouped controls

Konfigurimi i modulit

Every module lives under Settings → Module configuration.

⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes.

MQTT module

Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.

Setting Përshkrimi
MQTT enabled Toggle MQTT bridge
Address MQTT broker address
Username Authentication username
Password Authentication password
Encryption enabled Encrypt MQTT payloads
JSON output enabled Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS enabled Use secure connection
Root topic Base MQTT topic path
Proxy to client enabled Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy on this phone The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT
Map reporting Publish position to the public map — see the Map reporting group that follows

Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:

Setting Përshkrimi
I agree. Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered

See MQTT for a detailed usage guide including encryption, privacy, and broker setup.

Serial module

Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.

Setting Përshkrimi
Serial enabled Activate serial communication
Echo enabled Echo received serial data back
Serial mode Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX GPIO pins for the serial connection
Serial baud rate Port speed
Koha e skaduar How long to wait before considering an incoming message complete
Override console serial port Take over the port the debug console normally uses

External Notification module

Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.

There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.

Setting Përshkrimi
External notification enabled Master toggle for the module
Alert message LED / buzzer / vibra Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra Which outputs fire on a received bell character
Output LED (GPIO) Pin the LED is wired to
Output LED active high Whether the LED pin is active high or low
Output buzzer (GPIO) Pin the buzzer is wired to
Output vibra (GPIO) Pin the vibration motor is wired to
Use PWM buzzer Drive the buzzer with PWM, which allows tones rather than a single pitch
Use I2S as buzzer Send the alert through an I2S audio output instead
GPIO Output Duration How long a single alert lasts
Nag Timeout Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Ringtone The tone played on a PWM buzzer, in RTTTL. Can be imported from a file

Store & Forward module

Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.

Setting Përshkrimi
Store & Forward enabled Activate store and forward
Heartbeat Periodically announce this node’s store-and-forward capability
Number of records Maximum stored messages
History return max Max messages to replay
History return window Time window for replay
Server Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)

💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.

Range Test module

⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.

Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.

Setting Përshkrimi
Range test enabled Activate range testing
Sender Interval Time between test transmissions, chosen from a dropdown of fixed intervals
Save .CSV in storage (ESP32 only) Log received test data to the node’s own filesystem. ESP32 hardware only

Telemetry module

Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).

Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.

Setting Përshkrimi
Send Device Telemetry Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval How often to report battery, uptime and channel utilization
Environment metrics module enabled Report the attached environment sensors
Environment metrics update interval How often to report them
Environment metrics on-screen enabled Also show these readings on the device’s own display
Environment metrics use Fahrenheit Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Air quality metrics module enabled Report particulate and CO₂ sensor data
Air quality metrics update interval How often to report them
Power metrics module enabled Report the per-channel voltage and current readings
Power metrics update interval How often to report them
Power metrics on-screen enabled Also show power readings on the device’s display

See Telemetry & Sensors for supported sensors and configuration recommendations.

Canned Message module

Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.

Setting Përshkrimi
Canned message enabled ⚠️ Deprecated in the protobuf schema
訊息 Newline-separated list of messages
Send bell Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Rotary encoder #1 enabled Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port The three pins the encoder is wired to
Generate input event on Press / CW / CCW Which key event each encoder action produces
Up/Down/Select input enabled A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source ⚠️ Deprecated in the protobuf schema

Audio module

Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.

Setting Përshkrimi
CODEC 2 enabled Activate audio module
CODEC2 sample rate Audio quality/bandwidth tradeoff
PTT pin GPIO pin for the push-to-talk button
I2S word select GPIO pin for I2S WS
I2S data in GPIO pin for I2S DIN
I2S data out GPIO pin for I2S DOUT
I2S clock GPIO pin for the I2S bit clock

ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.

Remote Hardware module

GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.

⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.

Setting Përshkrimi
Remote Hardware enabled Activate remote GPIO access
Allow undefined pin access Allow access to any GPIO pin (security risk)
Available pins Up to 4 GPIO pins this node exposes for remote read/write

Neighbor Info module

Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.

Setting Përshkrimi
Neighbor Info enabled Activate neighbor broadcasting
Update Interval How often to broadcast neighbor list
Transmit over LoRa Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name

See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.

Ambient Lighting module

Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.

Setting Përshkrimi
LED state Turn the LED on or off
Current LED current limit (0–31)
Red / Green / Blue Individual color channel values (0–255)

Detection Sensor module

Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.

Setting Përshkrimi
Detection Sensor enabled Activate detection sensor
GPIO pin to monitor GPIO pin connected to sensor
Detection trigger type How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Use INPUT_PULLUP mode Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts Minimum time between alert broadcasts
State Broadcast Interval Periodic state broadcast interval
Send bell with alert message Include bell character in alerts
Friendly name Custom name for this sensor

Paxcounter module

People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.

Setting Përshkrimi
Paxcounter enabled Activate people counting
Update Interval How often to report counts
WiFi Threshold (dBm) Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm) The same cut-off for BLE advertisements (defaults to −80 dBm)

💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.

Status Message module

The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.

Mesh Beacon module

Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.

TAK module

Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.

Administratë

Administratë e Largët

Remotely configure nodes that share your admin key:

  1. Select the target node in the node list.
  2. Navigate to Settings for that node.
  3. Modify configuration.
  4. Tap Save — changes are sent over the mesh.

⚠️ Important: Requires an admin key configured on both your node and the target node.

Device Actions

Settings → Administration holds five one-shot actions, each behind a confirmation dialog:

Action What it does
Set time Sends your phone’s clock to the node
Rindiz Restarts the node
Fik Powers the node down
Përditësim i fabrikës Returns every setting to its factory default
Përditësimi i NodeDB Clears the node database. This dialog carries a Preserve Favorites? switch

⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.

Backup & Restore

Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.

Advanced

Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.

Clean Node Database

Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.

  • Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
  • Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.

The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.

Paneli i debug-ut

Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.

App Settings

The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:

Privacy

  • Allow analytics and crash reporting — opt in or out of diagnostics.
  • Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
  • Homoglyph encoding — how look-alike characters in names are handled.

Appearance

  • Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
  • Theme and Language.
  • Show full message timestamps.

Persistence

  • A cache limit for how much history is kept.
  • Export rangetest packets, Export all packets and Export node database.

On their own

  • Node Layout — how much detail each row of the node list shows.
  • Wi-Fi Provisioning for mPWRD-OS — see Connections.
  • Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
  • System AI — appears only where app functions are available; see App Functions.

A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.

Rreth

Settings → About carries the app’s own identity rather than the node’s:

Three sections:

  • What is Meshtastic? — a short description of the project.
  • Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
  • Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.

The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.

Acknowledgements

Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.

Troubleshooting remote admin

  • “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
  • Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
  • Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
diff --git a/main/sq-rAL/user/settings-radio-user.html b/main/sq-rAL/user/settings-radio-user.html index ae0979bec9..9bb5ddb4c4 100644 --- a/main/sq-rAL/user/settings-radio-user.html +++ b/main/sq-rAL/user/settings-radio-user.html @@ -1 +1 @@ - Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Shqip
Meshtastic Docs ↗

🌐 Shqip — Community translation View in English

Settings — Radio & User

Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How these screens work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Përshkrimi
Long Name Your display name (up to 39 characters)
Short Name 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Unmessageable Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur node (Ham) Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in.

Configuration

Device Config

On Settings → Device configuration → Device.

Setting Përshkrimi Default
Device Role Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Rebroadcast Mode How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Node Info Broadcast Interval How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Double Tap as Button Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Enabled
LED Heartbeat Blink the status LED periodically Enabled
Time Zone POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it —
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to —

LoRa Config

On Settings → LoRa.

Setting Përshkrimi Default
Rajon Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number Unset (must configure)
Presets Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Transmit Power Transmission power (dBm); 0 = max allowed for region 0 (region max)
Frequency Override Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Use Preset On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead From preset
Coding Rate Manual mode only: 5–8. More redundancy costs airtime From preset
Bandwidth Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Frequency Slot Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmit Enabled Turning this off makes the node receive-only On
Override Duty Cycle Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
Ignore MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok to MQTT Allow your packets to be forwarded to MQTT by gateways Off
RX Boosted Gain Extra receive gain on SX126x radios; costs a little current Off
PA fan disabled Turn off the power-amplifier fan on hardware that has one Off

The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set.

Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Speed SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a modem preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Display Config

On Settings → Device configuration → Display. These control the node’s own screen, not the app’s.

Setting Përshkrimi
Screen on for How long the display stays lit before sleeping
Carousel interval How often the node cycles between screens on its own
Display mode Screen layout/density used by the firmware
Display units Metric or Imperial on the node’s screen
Use 12h clock format Show the node’s clock as 12-hour rather than 24-hour
Bold Heading Draw the screen’s heading text in bold
Flip screen Rotate the display 180° for an inverted mounting
OLED type Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED
Wake on tap or motion Light the screen when the node is tapped or moved
Compass orientation Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each
Always point north Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Position Config

On Settings → Device configuration → Position.

Setting Përshkrimi
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the node asks its GPS for a fix
Broadcast Interval How often the position is shared with the mesh
Smart Position Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Fixed Position Use a manually entered latitude, longitude and altitude instead of the GPS
Position Flags A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Power Config

On Settings → Device configuration → Power.

Setting Përshkrimi
Enable power saving mode Let the node sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the node stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC multiplier override ratio The correction factor itself, used only when the override is on
Battery INA_2XX I2C address Address of an external INA-series power sensor, if fitted

Network Config

On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node.

Setting Përshkrimi
Wi-Fi enabled Enable the Wi-Fi node (ESP32 nodes)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Password Network password
Ethernet enabled Use a wired connection on hardware that has one
IPv4 mode DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP server Time synchronization server
rsyslog server Remote logging server

Network Config with a static IPv4 address entered

Bluetooth Config

On Settings → Device configuration → Bluetooth, on nodes with Bluetooth.

Setting Përshkrimi
Bluetooth enabled Enable/disable BLE radio
Pairing mode Fixed PIN, Random PIN, or No PIN
Fixed PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Security Config

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

Setting Përshkrimi
Public Key Your node’s public key (read-only)
Admin Key Keys permitted to administer this node remotely — up to three
Private Key Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it
Regenerate Private Key Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Serial console Serial console over the Stream API
Debug log API enabled Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth
Managed Mode Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.

+ Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Shqip
Meshtastic Docs ↗

🌐 Shqip — Community translation View in English

Settings — Radio & User

Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How these screens work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Përshkrimi
Long Name Your display name (up to 39 characters)
Short Name 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Unmessageable Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur node (Ham) Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in.

Configuration

Device Config

On Settings → Device configuration → Device.

Setting Përshkrimi Default
Device Role Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Rebroadcast Mode How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Node Info Broadcast Interval How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Double Tap as Button Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Enabled
LED Heartbeat Blink the status LED periodically Enabled
Time Zone POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it —
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to —

LoRa Config

On Settings → LoRa.

Setting Përshkrimi Default
Rajon Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number Unset (must configure)
Presets Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Transmit Power (dBm) Transmission power; 0 = max allowed for region 0 (region max)
Frequency Override Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Use Preset On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead From preset
Coding Rate Manual mode only: 5–8. More redundancy costs airtime From preset
Bandwidth Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Frequency Slot Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmit Enabled Turning this off makes the node receive-only On
Override Duty Cycle Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
Ignore MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok to MQTT Allow your packets to be forwarded to MQTT by gateways Off
RX Boosted Gain Extra receive gain on SX126x radios; costs a little current Off
PA fan disabled Turn off the power-amplifier fan on hardware that has one Off

The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set.

Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Speed SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a modem preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Display Config

On Settings → Device configuration → Display. These control the node’s own screen, not the app’s.

Setting Përshkrimi
Screen on for How long the display stays lit before sleeping
Carousel interval How often the node cycles between screens on its own
Display mode Screen layout/density used by the firmware
Display units Metric or Imperial on the node’s screen
Use 12h clock format Show the node’s clock as 12-hour rather than 24-hour
Bold Heading Draw the screen’s heading text in bold
Flip screen Rotate the display 180° for an inverted mounting
OLED type Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED
Wake on tap or motion Light the screen when the node is tapped or moved
Compass orientation Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each
Always point north Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Position Config

On Settings → Device configuration → Position.

Setting Përshkrimi
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the node asks its GPS for a fix
Broadcast Interval How often the position is shared with the mesh
Smart Position Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Fixed Position Use a manually entered latitude, longitude and altitude instead of the GPS
Position Flags A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Power Config

On Settings → Device configuration → Power.

Setting Përshkrimi
Enable power saving mode Let the node sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the node stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC multiplier override ratio The correction factor itself, used only when the override is on
Battery INA_2XX I2C address Address of an external INA-series power sensor, if fitted

Network Config

On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node.

Setting Përshkrimi
Wi-Fi enabled Enable the Wi-Fi node (ESP32 nodes)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Password Network password
Ethernet enabled Use a wired connection on hardware that has one
IPv4 mode DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP server Time synchronization server
rsyslog server Remote logging server

Network Config with a static IPv4 address entered

Bluetooth Config

On Settings → Device configuration → Bluetooth, on nodes with Bluetooth.

Setting Përshkrimi
Bluetooth enabled Enable/disable BLE radio
Pairing mode Fixed PIN, Random PIN, or No PIN
Fixed PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Security Config

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

Setting Përshkrimi
Public Key Your node’s public key (read-only)
Admin Key Keys permitted to administer this node remotely — up to three
Private Key Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it
Regenerate Private Key Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Serial console Serial console over the Stream API
Debug log API enabled Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth
Managed Mode Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.

diff --git a/main/sr-rLatn/user/discovery.html b/main/sr-rLatn/user/discovery.html index f74270fb5d..88b776917d 100644 --- a/main/sr-rLatn/user/discovery.html +++ b/main/sr-rLatn/user/discovery.html @@ -5,4 +5,4 @@ ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) -

Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:.

What to look for What it means
All hops show Good SNR (green) Healthy path — messages flow reliably
One hop shows a poor SNR (orange or red) Weak link — this relay segment is fragile
Many hops (4+) Long path — consider repositioning a node to shorten it
Different path on retry Mesh is adapting — multiple routes exist (this is good!)

💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network.

Troubleshooting with Traceroute

  • No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key.
  • Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa.
  • Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position.
  • Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric.

Neighbor Info

The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh.

Enabling Neighbor Info

  1. Navigate to Settings → Module configuration → Neighbor Info.
  2. Enable the module.
  3. Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
  4. Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air.

Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.

Viewing neighbor data

  • Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors.
  • Each neighbor entry shows the node that was directly heard and its signal quality.
  • Combine neighbor data from multiple nodes to understand the full mesh topology.

ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further.

Node list as a discovery tool

The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively.

Finding new nodes

  • Sort by Last heard to see the most recently active nodes at the top.
  • Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes.

Assessing connectivity

  • Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed.
  • Sort by Distance to find nearby nodes and verify they’re reachable.
  • Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge).

Infrastructure audit

  • Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes.
  • Check their signal quality and last-heard times to verify your infrastructure nodes are healthy.

See Nodes for full details on filtering and sorting options.

Tips for Mesh exploration

  • Start with traceroute — it gives you immediate, actionable information about a specific path.
  • Enable Neighbor Info on key nodes — especially routers and repeaters, to build a picture of the backbone.
  • Check the map — node positions on the Map combined with signal data help you understand why some links are strong and others are weak.
  • Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly.
+

Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:.

What to look for What it means
All hops show Good SNR (green) Healthy path — messages flow reliably
One hop shows a poor SNR (orange or red) Weak link — this relay segment is fragile
Many hops (4+) Long path — consider repositioning a node to shorten it
Different path on retry Mesh is adapting — multiple routes exist (this is good!)

💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network.

Troubleshooting with Traceroute

  • No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key.
  • Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa.
  • Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position.
  • Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric.

Neighbor Info

The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh.

Enabling Neighbor Info

  1. Navigate to Settings → Module configuration → Neighbor Info.
  2. Enable the module.
  3. Set Update Interval. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
  4. Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air.

Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.

Viewing neighbor data

  • Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors.
  • Each neighbor entry shows the node that was directly heard and its signal quality.
  • Combine neighbor data from multiple nodes to understand the full mesh topology.

ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further.

Node list as a discovery tool

The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively.

Finding new nodes

  • Sort by Last heard to see the most recently active nodes at the top.
  • Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes.

Assessing connectivity

  • Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed.
  • Sort by Distance to find nearby nodes and verify they’re reachable.
  • Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge).

Infrastructure audit

  • Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes.
  • Check their signal quality and last-heard times to verify your infrastructure nodes are healthy.

See Nodes for full details on filtering and sorting options.

Tips for Mesh exploration

  • Start with traceroute — it gives you immediate, actionable information about a specific path.
  • Enable Neighbor Info on key nodes — especially routers and repeaters, to build a picture of the backbone.
  • Check the map — node positions on the Map combined with signal data help you understand why some links are strong and others are weak.
  • Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly.
diff --git a/main/sr-rLatn/user/mqtt.html b/main/sr-rLatn/user/mqtt.html index aec5403c4d..e04ed5f165 100644 --- a/main/sr-rLatn/user/mqtt.html +++ b/main/sr-rLatn/user/mqtt.html @@ -1,2 +1,2 @@ MQTT | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Српски (Latinica)
Meshtastic Docs ↗

🌐 Српски (Latinica) — Community translation View in English

MQTT

MQTT bridges your Meshtastic mesh network to the internet, enabling long-range communication beyond radio range.

Overview

The MQTT module connects your node to an MQTT broker, allowing:

  • Messages to reach nodes on different physical meshes via the internet
  • Integration with home automation and monitoring systems
  • Publishing node positions to the public Meshtastic map
  • Custom data pipelines for logging and alerting

How It Works 

[Your Node] → Radio → [Gateway Node with Wi-Fi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node]
-

A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh.

Configuration

Enabling MQTT

  1. Navigate to Settings → Module configuration → MQTT.
  2. Enable the MQTT module.
  3. Configure the broker connection:
Setting Опис Подразумевано
Address MQTT broker hostname mqtt.meshtastic.org
Username Broker authentication meshdev
Password Broker authentication large4cats
Root topic Base topic for messages msh, which the radio rewrites to msh/<REGION> once you set a region
Encryption enabled Encrypt MQTT payload Омогућено
JSON output enabled Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it Онемогућено
TLS enabled Secure connection to broker Онемогућено
Map reporting Report position to public map Онемогућено
Proxy to client enabled Relay MQTT through the connected phone Онемогућено

Connection Status and Test Connection

The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here.

Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason.

MQTT Proxy on This Phone

If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection.

ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them.

The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration.

Default Meshtastic Broker

The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing.

When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without).

🔒 Privacy: Messages on the public broker are readable by anyone subscribed. Always use channel encryption for private communications.

Private Broker

For better privacy and control, you can run your own MQTT broker:

  • Mosquitto (lightweight, open-source)
  • HiveMQ
  • EMQX

Configure your node to point to your private broker with appropriate credentials.

Map Reporting

When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.

Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.

Reports appear at meshmap.net and similar community map services.

🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published.

Direction Опис
Uplink Messages from mesh → MQTT broker
Downlink Messages from MQTT broker → mesh

Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on.

Message Formats

MQTT carries two payload formats:

Format Опис Use case
Protobuf Binary Meshtastic protobuf encoding Node-to-node mesh bridging
JSON Human-readable JSON on the /2/json/ topic Consumers outside the mesh (dashboards, home automation)

ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads.

Encryption & Privacy

Understanding the layered encryption model:

  1. Channel encryption happens on the mesh before MQTT. If your channel has a PSK, the MQTT payload is already encrypted — the broker and any subscribers see only the ciphertext.
  2. Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard.
  3. TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping.

🔒 Security: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications.

Best Practices

  • Use channel-level encryption (PSK) on channels that bridge to MQTT
  • Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes memory)
  • Use a private broker for sensitive deployments
  • Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh
  • Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back

Troubleshooting

MQTT Not Connecting

  • Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself.
  • Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces.
  • Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443).
  • DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly.

Messages Not Bridging

  • Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway.
  • Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage.
  • Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root.
  • Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway.
  • Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in.
+

A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh.

Configuration

Enabling MQTT

  1. Navigate to Settings → Module configuration → MQTT.
  2. Enable the MQTT module.
  3. Configure the broker connection:
Setting Опис Подразумевано
Address MQTT broker hostname mqtt.meshtastic.org
Username Broker authentication meshdev
Password Broker authentication large4cats
Root topic Base topic for messages msh, which the radio rewrites to msh/<REGION> once you set a region
Encryption enabled Encrypt MQTT payload Омогућено
JSON output enabled Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it Онемогућено
TLS enabled Secure connection to broker Онемогућено
Map reporting Report position to public map Онемогућено
Proxy to client enabled Relay MQTT through the connected phone Онемогућено

Connection Status and Test Connection

The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here.

Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason.

MQTT Proxy on This Phone

If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection.

ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them.

The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration.

Default Meshtastic Broker

The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing.

When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without).

🔒 Privacy: Messages on the public broker are readable by anyone subscribed. Always use channel encryption for private communications.

Private Broker

For better privacy and control, you can run your own MQTT broker:

  • Mosquitto (lightweight, open-source)
  • HiveMQ
  • EMQX

Configure your node to point to your private broker with appropriate credentials.

Map Reporting

When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.

Turning it on opens a consent card. Turn on I agree. and choose a Map Publish Interval of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.

Reports appear at meshmap.net and similar community map services.

🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published.

Direction Опис
Uplink Messages from mesh → MQTT broker
Downlink Messages from MQTT broker → mesh

Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on.

Message Formats

MQTT carries two payload formats:

Format Опис Use case
Protobuf Binary Meshtastic protobuf encoding Node-to-node mesh bridging
JSON Human-readable JSON on the /2/json/ topic Consumers outside the mesh (dashboards, home automation)

ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads.

Encryption & Privacy

Understanding the layered encryption model:

  1. Channel encryption happens on the mesh before MQTT. If your channel has a PSK, the MQTT payload is already encrypted — the broker and any subscribers see only the ciphertext.
  2. Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard.
  3. TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping.

🔒 Security: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications.

Best Practices

  • Use channel-level encryption (PSK) on channels that bridge to MQTT
  • Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes memory)
  • Use a private broker for sensitive deployments
  • Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh
  • Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back

Troubleshooting

MQTT Not Connecting

  • Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself.
  • Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces.
  • Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443).
  • DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly.

Messages Not Bridging

  • Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway.
  • Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage.
  • Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root.
  • Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway.
  • Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in.
diff --git a/main/sr-rLatn/user/settings-module-admin.html b/main/sr-rLatn/user/settings-module-admin.html index 4f12e48490..5a24f82823 100644 --- a/main/sr-rLatn/user/settings-module-admin.html +++ b/main/sr-rLatn/user/settings-module-admin.html @@ -1 +1 @@ - Settings — Modules & Admin | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Српски (Latinica)
Meshtastic Docs ↗

🌐 Српски (Latinica) — Community translation View in English

Settings — Modules & Admin

Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.

💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.

Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:

A toggle setting in the on position

A dropdown setting, expanded to show its list of options

A text field setting with a value entered

A module settings card with its title and grouped controls

Конфигурација модула

Every module lives under Settings → Module configuration.

⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes.

MQTT module

Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.

Setting Опис
MQTT enabled Toggle MQTT bridge
Адреса MQTT broker address
Корисничко име Authentication username
Лозинка Authentication password
Encryption enabled Encrypt MQTT payloads
JSON output enabled Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS enabled Use secure connection
Root topic Base MQTT topic path
Proxy to client enabled Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy on this phone The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT
Map reporting Publish position to the public map — see the Map reporting group that follows

Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:

Setting Опис
I agree. Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map reporting interval (seconds) How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered

See MQTT for a detailed usage guide including encryption, privacy, and broker setup.

Serial module

Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.

Setting Опис
Serial enabled Activate serial communication
Echo enabled Echo received serial data back
Serial mode Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX GPIO pins for the serial connection
Serial baud rate Port speed
Isteklo vreme How long to wait before considering an incoming message complete
Override console serial port Take over the port the debug console normally uses

External Notification module

Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.

There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.

Setting Опис
External notification enabled Master toggle for the module
Alert message LED / buzzer / vibra Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra Which outputs fire on a received bell character
Output LED (GPIO) Pin the LED is wired to
Output LED active high Whether the LED pin is active high or low
Output buzzer (GPIO) Pin the buzzer is wired to
Output vibra (GPIO) Pin the vibration motor is wired to
Use PWM buzzer Drive the buzzer with PWM, which allows tones rather than a single pitch
Use I2S as buzzer Send the alert through an I2S audio output instead
Output duration (milliseconds) How long a single alert lasts
Nag timeout (seconds) Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Мелодија звона The tone played on a PWM buzzer, in RTTTL. Can be imported from a file

Store & Forward module

Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.

Setting Опис
Store & Forward enabled Activate store and forward
Heartbeat Periodically announce this node’s store-and-forward capability
Број записа Maximum stored messages
History return max Max messages to replay
History return window Time window for replay
Сервер Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)

💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.

Range Test module

⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.

Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.

Setting Опис
Range test enabled Activate range testing
Sender message interval (seconds) Time between test transmissions, chosen from a dropdown of fixed intervals
Save .CSV in storage (ESP32 only) Log received test data to the node’s own filesystem. ESP32 hardware only

Telemetry module

Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).

Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.

Setting Опис
Send Device Telemetry Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval How often to report battery, uptime and channel utilization
Environment metrics module enabled Report the attached environment sensors
Environment metrics update interval How often to report them
Environment metrics on-screen enabled Also show these readings on the device’s own display
Environment metrics use Fahrenheit Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Air quality metrics module enabled Report particulate and CO₂ sensor data
Air quality metrics update interval How often to report them
Power metrics module enabled Report the per-channel voltage and current readings
Power metrics update interval How often to report them
Power metrics on-screen enabled Also show power readings on the device’s display

See Telemetry & Sensors for supported sensors and configuration recommendations.

Canned Message module

Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.

Setting Опис
Canned message enabled ⚠️ Deprecated in the protobuf schema
Поруке Newline-separated list of messages
Send bell Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Rotary encoder #1 enabled Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port The three pins the encoder is wired to
Generate input event on Press / CW / CCW Which key event each encoder action produces
Up/Down/Select input enabled A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source ⚠️ Deprecated in the protobuf schema

Audio module

Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.

Setting Опис
CODEC 2 enabled Activate audio module
CODEC2 sample rate Audio quality/bandwidth tradeoff
PTT pin GPIO pin for the push-to-talk button
I2S word select GPIO pin for I2S WS
I2S data in GPIO pin for I2S DIN
I2S data out GPIO pin for I2S DOUT
I2S clock GPIO pin for the I2S bit clock

ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.

Remote Hardware module

GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.

⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.

Setting Опис
Remote Hardware enabled Activate remote GPIO access
Allow undefined pin access Allow access to any GPIO pin (security risk)
Available pins Up to 4 GPIO pins this node exposes for remote read/write

Neighbor Info module

Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.

Setting Опис
Neighbor Info enabled Activate neighbor broadcasting
Update interval (seconds) How often to broadcast neighbor list
Transmit over LoRa Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name

See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.

Ambient Lighting module

Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.

Setting Опис
LED state Turn the LED on or off
Струја LED current limit (0–31)
Red / Green / Blue Individual color channel values (0–255)

Detection Sensor module

Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.

Setting Опис
Detection Sensor enabled Activate detection sensor
GPIO pin to monitor GPIO pin connected to sensor
Detection trigger type How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Use INPUT_PULLUP mode Enable the pin’s internal pull-up resistor
Minimum broadcast (seconds) Minimum time between alert broadcasts
State broadcast (seconds) Periodic state broadcast interval
Send bell with alert message Include bell character in alerts
Пријатељски назив Custom name for this sensor

Paxcounter module

People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.

Setting Опис
Paxcounter enabled Activate people counting
Update interval (seconds) How often to report counts
Wi-Fi RSSI threshold Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE RSSI threshold The same cut-off for BLE advertisements (defaults to −80 dBm)

💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.

Status Message module

The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.

Mesh Beacon module

Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.

TAK module

Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.

Administracija

Udaljena administracija

Remotely configure nodes that share your admin key:

  1. Select the target node in the node list.
  2. Navigate to Settings for that node.
  3. Modify configuration.
  4. Tap Save — changes are sent over the mesh.

⚠️ Important: Requires an admin key configured on both your node and the target node.

Device Actions

Settings → Administration holds five one-shot actions, each behind a confirmation dialog:

Action What it does
Set time Sends your phone’s clock to the node
Поново покрени Restarts the node
Искључи Powers the node down
Рестартовање на фабричка подешавања Returns every setting to its factory default
Ресетовање базе чворова Clears the node database. This dialog carries a Preserve Favorites? switch

⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.

Backup & Restore

Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.

Напредно

Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.

Clean Node Database

Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.

  • Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
  • Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.

The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.

Panel za otklanjanje grešaka

Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.

Подешавања апликације

The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:

Privacy

  • Allow analytics and crash reporting — opt in or out of diagnostics.
  • Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
  • Homoglyph encoding — how look-alike characters in names are handled.

Appearance

  • Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
  • Theme and Language.
  • Show full message timestamps.

Persistence

  • A cache limit for how much history is kept.
  • Export rangetest packets, Export all packets and Export node database.

On their own

  • Node Layout — how much detail each row of the node list shows.
  • Wi-Fi Provisioning for mPWRD-OS — see Connections.
  • Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
  • System AI — appears only where app functions are available; see App Functions.

A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.

O nama

Settings → About carries the app’s own identity rather than the node’s:

Three sections:

  • What is Meshtastic? — a short description of the project.
  • Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
  • Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.

The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.

Acknowledgements

Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.

Troubleshooting remote admin

  • “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
  • Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
  • Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
+ Settings — Modules & Admin | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Српски (Latinica)
Meshtastic Docs ↗

🌐 Српски (Latinica) — Community translation View in English

Settings — Modules & Admin

Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.

💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.

Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:

A toggle setting in the on position

A dropdown setting, expanded to show its list of options

A text field setting with a value entered

A module settings card with its title and grouped controls

Конфигурација модула

Every module lives under Settings → Module configuration.

⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes.

MQTT module

Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.

Setting Опис
MQTT enabled Toggle MQTT bridge
Адреса MQTT broker address
Корисничко име Authentication username
Лозинка Authentication password
Encryption enabled Encrypt MQTT payloads
JSON output enabled Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS enabled Use secure connection
Root topic Base MQTT topic path
Proxy to client enabled Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy on this phone The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT
Map reporting Publish position to the public map — see the Map reporting group that follows

Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:

Setting Опис
I agree. Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Интервал објављивања мапе How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered

See MQTT for a detailed usage guide including encryption, privacy, and broker setup.

Serial module

Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.

Setting Опис
Serial enabled Activate serial communication
Echo enabled Echo received serial data back
Serial mode Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX GPIO pins for the serial connection
Serial baud rate Port speed
Isteklo vreme How long to wait before considering an incoming message complete
Override console serial port Take over the port the debug console normally uses

External Notification module

Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.

There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.

Setting Опис
External notification enabled Master toggle for the module
Alert message LED / buzzer / vibra Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra Which outputs fire on a received bell character
Output LED (GPIO) Pin the LED is wired to
Output LED active high Whether the LED pin is active high or low
Output buzzer (GPIO) Pin the buzzer is wired to
Output vibra (GPIO) Pin the vibration motor is wired to
Use PWM buzzer Drive the buzzer with PWM, which allows tones rather than a single pitch
Use I2S as buzzer Send the alert through an I2S audio output instead
Трајање GPIO излаза How long a single alert lasts
Nag Timeout Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Мелодија звона The tone played on a PWM buzzer, in RTTTL. Can be imported from a file

Store & Forward module

Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.

Setting Опис
Store & Forward enabled Activate store and forward
Heartbeat Periodically announce this node’s store-and-forward capability
Број записа Maximum stored messages
History return max Max messages to replay
History return window Time window for replay
Сервер Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)

💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.

Range Test module

⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.

Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.

Setting Опис
Range test enabled Activate range testing
Инерварл пошиљаоца Time between test transmissions, chosen from a dropdown of fixed intervals
Save .CSV in storage (ESP32 only) Log received test data to the node’s own filesystem. ESP32 hardware only

Telemetry module

Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).

Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.

Setting Опис
Send Device Telemetry Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval How often to report battery, uptime and channel utilization
Environment metrics module enabled Report the attached environment sensors
Environment metrics update interval How often to report them
Environment metrics on-screen enabled Also show these readings on the device’s own display
Environment metrics use Fahrenheit Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Air quality metrics module enabled Report particulate and CO₂ sensor data
Air quality metrics update interval How often to report them
Power metrics module enabled Report the per-channel voltage and current readings
Power metrics update interval How often to report them
Power metrics on-screen enabled Also show power readings on the device’s display

See Telemetry & Sensors for supported sensors and configuration recommendations.

Canned Message module

Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.

Setting Опис
Canned message enabled ⚠️ Deprecated in the protobuf schema
Поруке Newline-separated list of messages
Send bell Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Rotary encoder #1 enabled Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port The three pins the encoder is wired to
Generate input event on Press / CW / CCW Which key event each encoder action produces
Up/Down/Select input enabled A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source ⚠️ Deprecated in the protobuf schema

Audio module

Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.

Setting Опис
CODEC 2 enabled Activate audio module
CODEC2 sample rate Audio quality/bandwidth tradeoff
PTT pin GPIO pin for the push-to-talk button
I2S word select GPIO pin for I2S WS
I2S data in GPIO pin for I2S DIN
I2S data out GPIO pin for I2S DOUT
I2S clock GPIO pin for the I2S bit clock

ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.

Remote Hardware module

GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.

⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.

Setting Опис
Remote Hardware enabled Activate remote GPIO access
Allow undefined pin access Allow access to any GPIO pin (security risk)
Available pins Up to 4 GPIO pins this node exposes for remote read/write

Neighbor Info module

Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.

Setting Опис
Neighbor Info enabled Activate neighbor broadcasting
Интервал ажурирања How often to broadcast neighbor list
Transmit over LoRa Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name

See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.

Ambient Lighting module

Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.

Setting Опис
LED state Turn the LED on or off
Струја LED current limit (0–31)
Red / Green / Blue Individual color channel values (0–255)

Detection Sensor module

Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.

Setting Опис
Detection Sensor enabled Activate detection sensor
GPIO pin to monitor GPIO pin connected to sensor
Detection trigger type How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Use INPUT_PULLUP mode Enable the pin’s internal pull-up resistor
Минимално време између емитовања детекције Minimum time between alert broadcasts
Интервал емитовања стања Periodic state broadcast interval
Send bell with alert message Include bell character in alerts
Пријатељски назив Custom name for this sensor

Paxcounter module

People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.

Setting Опис
Paxcounter enabled Activate people counting
Интервал ажурирања How often to report counts
WiFi Threshold (dBm) Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm) The same cut-off for BLE advertisements (defaults to −80 dBm)

💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.

Status Message module

The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.

Mesh Beacon module

Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.

TAK module

Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.

Administracija

Udaljena administracija

Remotely configure nodes that share your admin key:

  1. Select the target node in the node list.
  2. Navigate to Settings for that node.
  3. Modify configuration.
  4. Tap Save — changes are sent over the mesh.

⚠️ Important: Requires an admin key configured on both your node and the target node.

Device Actions

Settings → Administration holds five one-shot actions, each behind a confirmation dialog:

Action What it does
Set time Sends your phone’s clock to the node
Поново покрени Restarts the node
Искључи Powers the node down
Рестартовање на фабричка подешавања Returns every setting to its factory default
Ресетовање базе чворова Clears the node database. This dialog carries a Preserve Favorites? switch

⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.

Backup & Restore

Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.

Напредно

Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.

Clean Node Database

Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.

  • Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
  • Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.

The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.

Panel za otklanjanje grešaka

Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.

Подешавања апликације

The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:

Privacy

  • Allow analytics and crash reporting — opt in or out of diagnostics.
  • Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
  • Homoglyph encoding — how look-alike characters in names are handled.

Appearance

  • Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
  • Theme and Language.
  • Show full message timestamps.

Persistence

  • A cache limit for how much history is kept.
  • Export rangetest packets, Export all packets and Export node database.

On their own

  • Node Layout — how much detail each row of the node list shows.
  • Wi-Fi Provisioning for mPWRD-OS — see Connections.
  • Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
  • System AI — appears only where app functions are available; see App Functions.

A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.

O nama

Settings → About carries the app’s own identity rather than the node’s:

Three sections:

  • What is Meshtastic? — a short description of the project.
  • Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
  • Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.

The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.

Acknowledgements

Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.

Troubleshooting remote admin

  • “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
  • Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
  • Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
diff --git a/main/sr-rLatn/user/settings-radio-user.html b/main/sr-rLatn/user/settings-radio-user.html index 3a9b4c1836..357998b430 100644 --- a/main/sr-rLatn/user/settings-radio-user.html +++ b/main/sr-rLatn/user/settings-radio-user.html @@ -1 +1 @@ - Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Српски (Latinica)
Meshtastic Docs ↗

🌐 Српски (Latinica) — Community translation View in English

Settings — Radio & User

Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How these screens work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Опис
Дуго име Your display name (up to 39 characters)
Кратко име 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Unmessageable Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur node (Ham) Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in.

Configuration

Подешавања уређаја

On Settings → Device configuration → Device.

Setting Опис Подразумевано
Улога уређаја Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Режим реемитовања How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Интервал емитовања информација о чвору How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Двоструки додир као дугме Treat a double tap as a button press Онемогућено
Троструки клик за Ad Hoc пинг Send an ad-hoc position ping on a triple click Омогућено
LED срчани откуцаји Blink the status LED periodically Омогућено
Временска зона POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it —
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to —

LoRA подешавања

On Settings → LoRa.

Setting Опис Подразумевано
Регион Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number Unset (must configure)
Унапред подешено Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Transmit Power Transmission power (dBm); 0 = max allowed for region 0 (region max)
Измена фреквенције Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Користи предефинисано подешавање On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Фактор ширења Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead From preset
Стопа кодирања Manual mode only: 5–8. More redundancy costs airtime From preset
Проток Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Фреквенцијски слот Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Трансмитер укључен Turning this off makes the node receive-only On
Override Duty Cycle Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Искључен
Игнориши MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Позитиван за MQTT Allow your packets to be forwarded to MQTT by gateways Искључен
Појачање пријемника Extra receive gain on SX126x radios; costs a little current Искључен
PA fan disabled Turn off the power-amplifier fan on hardware that has one Искључен

The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set.

Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Брзина SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a modem preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Подешавања приказа

On Settings → Device configuration → Display. These control the node’s own screen, not the app’s.

Setting Опис
Екран укључен за How long the display stays lit before sleeping
Carousel interval How often the node cycles between screens on its own
Display mode Screen layout/density used by the firmware
Display units Metric or Imperial on the node’s screen
Use 12h clock format Show the node’s clock as 12-hour rather than 24-hour
Bold Heading Draw the screen’s heading text in bold
Flip screen Rotate the display 180° for an inverted mounting
OLED type Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED
Wake on tap or motion Light the screen when the node is tapped or moved
Compass orientation Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each
Увек усмеравајте на север Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Подешавања позиције

On Settings → Device configuration → Position.

Setting Опис
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the node asks its GPS for a fix
Интервал емитовања How often the position is shared with the mesh
Паметно позиционирање Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Фиксна локација Use a manually entered latitude, longitude and altitude instead of the GPS
Заставице позиције A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Подешавања напајња

On Settings → Device configuration → Power.

Setting Опис
Enable power saving mode Let the node sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the node stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC multiplier override ratio The correction factor itself, used only when the override is on
Battery INA_2XX I2C address Address of an external INA-series power sensor, if fitted

Конфигурација мреже

On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node.

Setting Опис
Wi-Fi enabled Enable the Wi-Fi node (ESP32 nodes)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Лозинка Network password
Ethernet enabled Use a wired connection on hardware that has one
IPv4 mode DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP server Time synchronization server
rsyslog server Remote logging server

Network Config with a static IPv4 address entered

Блутут подешавања

On Settings → Device configuration → Bluetooth, on nodes with Bluetooth.

Setting Опис
Bluetooth enabled Enable/disable BLE radio
Pairing mode Fixed PIN, Random PIN, or No PIN
Fixed PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Сигурносна подешавања

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

Setting Опис
Javni ključ Your node’s public key (read-only)
Admin Key Keys permitted to administer this node remotely — up to three
Privatni ključ Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it
Regenerate Private Key Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Serial console Serial console over the Stream API
Debug log API enabled Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth
Managed Mode Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.

+ Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Српски (Latinica)
Meshtastic Docs ↗

🌐 Српски (Latinica) — Community translation View in English

Settings — Radio & User

Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How these screens work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Опис
Дуго име Your display name (up to 39 characters)
Кратко име 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Unmessageable Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur node (Ham) Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in.

Configuration

Подешавања уређаја

On Settings → Device configuration → Device.

Setting Опис Подразумевано
Улога уређаја Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Режим реемитовања How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Интервал емитовања информација о чвору How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Двоструки додир као дугме Treat a double tap as a button press Онемогућено
Троструки клик за Ad Hoc пинг Send an ad-hoc position ping on a triple click Омогућено
LED срчани откуцаји Blink the status LED periodically Омогућено
Временска зона POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it —
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to —

LoRA подешавања

On Settings → LoRa.

Setting Опис Подразумевано
Регион Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number Unset (must configure)
Унапред подешено Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Transmit Power (dBm) Transmission power; 0 = max allowed for region 0 (region max)
Измена фреквенције Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Користи предефинисано подешавање On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Фактор ширења Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead From preset
Стопа кодирања Manual mode only: 5–8. More redundancy costs airtime From preset
Проток Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Фреквенцијски слот Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Трансмитер укључен Turning this off makes the node receive-only On
Override Duty Cycle Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Искључен
Игнориши MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Позитиван за MQTT Allow your packets to be forwarded to MQTT by gateways Искључен
Појачање пријемника Extra receive gain on SX126x radios; costs a little current Искључен
PA fan disabled Turn off the power-amplifier fan on hardware that has one Искључен

The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set.

Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Брзина SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a modem preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Подешавања приказа

On Settings → Device configuration → Display. These control the node’s own screen, not the app’s.

Setting Опис
Екран укључен за How long the display stays lit before sleeping
Carousel interval How often the node cycles between screens on its own
Display mode Screen layout/density used by the firmware
Display units Metric or Imperial on the node’s screen
Use 12h clock format Show the node’s clock as 12-hour rather than 24-hour
Bold Heading Draw the screen’s heading text in bold
Flip screen Rotate the display 180° for an inverted mounting
OLED type Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED
Wake on tap or motion Light the screen when the node is tapped or moved
Compass orientation Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each
Увек усмеравајте на север Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Подешавања позиције

On Settings → Device configuration → Position.

Setting Опис
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the node asks its GPS for a fix
Интервал емитовања How often the position is shared with the mesh
Паметно позиционирање Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Фиксна локација Use a manually entered latitude, longitude and altitude instead of the GPS
Заставице позиције A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Подешавања напајња

On Settings → Device configuration → Power.

Setting Опис
Enable power saving mode Let the node sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the node stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC multiplier override ratio The correction factor itself, used only when the override is on
Battery INA_2XX I2C address Address of an external INA-series power sensor, if fitted

Конфигурација мреже

On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node.

Setting Опис
Wi-Fi enabled Enable the Wi-Fi node (ESP32 nodes)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Лозинка Network password
Ethernet enabled Use a wired connection on hardware that has one
IPv4 mode DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP server Time synchronization server
rsyslog server Remote logging server

Network Config with a static IPv4 address entered

Блутут подешавања

On Settings → Device configuration → Bluetooth, on nodes with Bluetooth.

Setting Опис
Bluetooth enabled Enable/disable BLE radio
Pairing mode Fixed PIN, Random PIN, or No PIN
Fixed PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Сигурносна подешавања

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

Setting Опис
Javni ključ Your node’s public key (read-only)
Admin Key Keys permitted to administer this node remotely — up to three
Privatni ključ Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it
Regenerate Private Key Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Serial console Serial console over the Stream API
Debug log API enabled Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth
Managed Mode Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.

diff --git a/main/srp/user/discovery.html b/main/srp/user/discovery.html index 93d4a5f5e5..915bbc4be1 100644 --- a/main/srp/user/discovery.html +++ b/main/srp/user/discovery.html @@ -5,4 +5,4 @@ ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) -

Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:.

What to look for What it means
All hops show Good SNR (green) Healthy path — messages flow reliably
One hop shows a poor SNR (orange or red) Weak link — this relay segment is fragile
Many hops (4+) Long path — consider repositioning a node to shorten it
Different path on retry Mesh is adapting — multiple routes exist (this is good!)

💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network.

Troubleshooting with Traceroute

  • No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key.
  • Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa.
  • Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position.
  • Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric.

Neighbor Info

The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh.

Enabling Neighbor Info

  1. Navigate to Settings → Module configuration → Neighbor Info.
  2. Enable the module.
  3. Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
  4. Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air.

Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.

Viewing neighbor data

  • Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors.
  • Each neighbor entry shows the node that was directly heard and its signal quality.
  • Combine neighbor data from multiple nodes to understand the full mesh topology.

ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further.

Node list as a discovery tool

The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively.

Finding new nodes

  • Sort by Last heard to see the most recently active nodes at the top.
  • Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes.

Assessing connectivity

  • Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed.
  • Sort by Distance to find nearby nodes and verify they’re reachable.
  • Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge).

Infrastructure audit

  • Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes.
  • Check their signal quality and last-heard times to verify your infrastructure nodes are healthy.

See Nodes for full details on filtering and sorting options.

Tips for Mesh exploration

  • Start with traceroute — it gives you immediate, actionable information about a specific path.
  • Enable Neighbor Info on key nodes — especially routers and repeaters, to build a picture of the backbone.
  • Check the map — node positions on the Map combined with signal data help you understand why some links are strong and others are weak.
  • Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly.
+

Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:.

What to look for What it means
All hops show Good SNR (green) Healthy path — messages flow reliably
One hop shows a poor SNR (orange or red) Weak link — this relay segment is fragile
Many hops (4+) Long path — consider repositioning a node to shorten it
Different path on retry Mesh is adapting — multiple routes exist (this is good!)

💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network.

Troubleshooting with Traceroute

  • No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key.
  • Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa.
  • Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position.
  • Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric.

Neighbor Info

The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh.

Enabling Neighbor Info

  1. Navigate to Settings → Module configuration → Neighbor Info.
  2. Enable the module.
  3. Set Update Interval. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
  4. Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air.

Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.

Viewing neighbor data

  • Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors.
  • Each neighbor entry shows the node that was directly heard and its signal quality.
  • Combine neighbor data from multiple nodes to understand the full mesh topology.

ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further.

Node list as a discovery tool

The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively.

Finding new nodes

  • Sort by Last heard to see the most recently active nodes at the top.
  • Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes.

Assessing connectivity

  • Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed.
  • Sort by Distance to find nearby nodes and verify they’re reachable.
  • Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge).

Infrastructure audit

  • Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes.
  • Check their signal quality and last-heard times to verify your infrastructure nodes are healthy.

See Nodes for full details on filtering and sorting options.

Tips for Mesh exploration

  • Start with traceroute — it gives you immediate, actionable information about a specific path.
  • Enable Neighbor Info on key nodes — especially routers and repeaters, to build a picture of the backbone.
  • Check the map — node positions on the Map combined with signal data help you understand why some links are strong and others are weak.
  • Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly.
diff --git a/main/srp/user/mqtt.html b/main/srp/user/mqtt.html index 3362202fbc..78f002ce7c 100644 --- a/main/srp/user/mqtt.html +++ b/main/srp/user/mqtt.html @@ -1,2 +1,2 @@ MQTT | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Српски (Ћирилица)
Meshtastic Docs ↗

🌐 Српски (Ћирилица) — Community translation View in English

MQTT

MQTT bridges your Meshtastic mesh network to the internet, enabling long-range communication beyond radio range.

Overview

The MQTT module connects your node to an MQTT broker, allowing:

  • Messages to reach nodes on different physical meshes via the internet
  • Integration with home automation and monitoring systems
  • Publishing node positions to the public Meshtastic map
  • Custom data pipelines for logging and alerting

How It Works 

[Your Node] → Radio → [Gateway Node with Wi-Fi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node]
-

A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh.

Configuration

Enabling MQTT

  1. Navigate to Settings → Module configuration → MQTT.
  2. Enable the MQTT module.
  3. Configure the broker connection:
Setting Опис Подразумевано
Address MQTT broker hostname mqtt.meshtastic.org
Username Broker authentication meshdev
Password Broker authentication large4cats
Root topic Base topic for messages msh, which the radio rewrites to msh/<REGION> once you set a region
Encryption enabled Encrypt MQTT payload Омогућено
JSON output enabled Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it Онемогућено
TLS enabled Secure connection to broker Онемогућено
Map reporting Report position to public map Онемогућено
Proxy to client enabled Relay MQTT through the connected phone Онемогућено

Connection Status and Test Connection

The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here.

Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason.

MQTT Proxy on This Phone

If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection.

ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them.

The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration.

Default Meshtastic Broker

The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing.

When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without).

🔒 Privacy: Messages on the public broker are readable by anyone subscribed. Always use channel encryption for private communications.

Private Broker

For better privacy and control, you can run your own MQTT broker:

  • Mosquitto (lightweight, open-source)
  • HiveMQ
  • EMQX

Configure your node to point to your private broker with appropriate credentials.

Map Reporting

When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.

Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.

Reports appear at meshmap.net and similar community map services.

🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published.

Direction Опис
Uplink Messages from mesh → MQTT broker
Downlink Messages from MQTT broker → mesh

Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on.

Message Formats

MQTT carries two payload formats:

Format Опис Use case
Protobuf Binary Meshtastic protobuf encoding Node-to-node mesh bridging
JSON Human-readable JSON on the /2/json/ topic Consumers outside the mesh (dashboards, home automation)

ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads.

Encryption & Privacy

Understanding the layered encryption model:

  1. Channel encryption happens on the mesh before MQTT. If your channel has a PSK, the MQTT payload is already encrypted — the broker and any subscribers see only the ciphertext.
  2. Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard.
  3. TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping.

🔒 Security: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications.

Best Practices

  • Use channel-level encryption (PSK) on channels that bridge to MQTT
  • Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes memory)
  • Use a private broker for sensitive deployments
  • Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh
  • Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back

Troubleshooting

MQTT Not Connecting

  • Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself.
  • Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces.
  • Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443).
  • DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly.

Messages Not Bridging

  • Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway.
  • Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage.
  • Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root.
  • Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway.
  • Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in.
+

A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh.

Configuration

Enabling MQTT

  1. Navigate to Settings → Module configuration → MQTT.
  2. Enable the MQTT module.
  3. Configure the broker connection:
Setting Опис Подразумевано
Address MQTT broker hostname mqtt.meshtastic.org
Username Broker authentication meshdev
Password Broker authentication large4cats
Root topic Base topic for messages msh, which the radio rewrites to msh/<REGION> once you set a region
Encryption enabled Encrypt MQTT payload Омогућено
JSON output enabled Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it Онемогућено
TLS enabled Secure connection to broker Онемогућено
Map reporting Report position to public map Онемогућено
Proxy to client enabled Relay MQTT through the connected phone Онемогућено

Connection Status and Test Connection

The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here.

Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason.

MQTT Proxy on This Phone

If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection.

ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them.

The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration.

Default Meshtastic Broker

The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing.

When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without).

🔒 Privacy: Messages on the public broker are readable by anyone subscribed. Always use channel encryption for private communications.

Private Broker

For better privacy and control, you can run your own MQTT broker:

  • Mosquitto (lightweight, open-source)
  • HiveMQ
  • EMQX

Configure your node to point to your private broker with appropriate credentials.

Map Reporting

When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.

Turning it on opens a consent card. Turn on I agree. and choose a Map Publish Interval of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.

Reports appear at meshmap.net and similar community map services.

🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published.

Direction Опис
Uplink Messages from mesh → MQTT broker
Downlink Messages from MQTT broker → mesh

Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on.

Message Formats

MQTT carries two payload formats:

Format Опис Use case
Protobuf Binary Meshtastic protobuf encoding Node-to-node mesh bridging
JSON Human-readable JSON on the /2/json/ topic Consumers outside the mesh (dashboards, home automation)

ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads.

Encryption & Privacy

Understanding the layered encryption model:

  1. Channel encryption happens on the mesh before MQTT. If your channel has a PSK, the MQTT payload is already encrypted — the broker and any subscribers see only the ciphertext.
  2. Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard.
  3. TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping.

🔒 Security: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications.

Best Practices

  • Use channel-level encryption (PSK) on channels that bridge to MQTT
  • Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes memory)
  • Use a private broker for sensitive deployments
  • Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh
  • Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back

Troubleshooting

MQTT Not Connecting

  • Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself.
  • Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces.
  • Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443).
  • DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly.

Messages Not Bridging

  • Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway.
  • Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage.
  • Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root.
  • Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway.
  • Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in.
diff --git a/main/srp/user/settings-module-admin.html b/main/srp/user/settings-module-admin.html index ec11c3b059..c6212e2355 100644 --- a/main/srp/user/settings-module-admin.html +++ b/main/srp/user/settings-module-admin.html @@ -1 +1 @@ - Settings — Modules & Admin | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Српски (Ћирилица)
Meshtastic Docs ↗

🌐 Српски (Ћирилица) — Community translation View in English

Settings — Modules & Admin

Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.

💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.

Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:

A toggle setting in the on position

A dropdown setting, expanded to show its list of options

A text field setting with a value entered

A module settings card with its title and grouped controls

Конфигурација модула

Every module lives under Settings → Module configuration.

⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes.

MQTT module

Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.

Setting Опис
MQTT enabled Toggle MQTT bridge
Адреса MQTT broker address
Корисничко име Authentication username
Лозинка Authentication password
Encryption enabled Encrypt MQTT payloads
JSON output enabled Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS enabled Use secure connection
Root topic Base MQTT topic path
Proxy to client enabled Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy on this phone The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT
Map reporting Publish position to the public map — see the Map reporting group that follows

Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:

Setting Опис
I agree. Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map reporting interval (seconds) How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered

See MQTT for a detailed usage guide including encryption, privacy, and broker setup.

Serial module

Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.

Setting Опис
Serial enabled Activate serial communication
Echo enabled Echo received serial data back
Serial mode Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX GPIO pins for the serial connection
Serial baud rate Port speed
Временско ограничење How long to wait before considering an incoming message complete
Override console serial port Take over the port the debug console normally uses

External Notification module

Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.

There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.

Setting Опис
External notification enabled Master toggle for the module
Alert message LED / buzzer / vibra Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra Which outputs fire on a received bell character
Output LED (GPIO) Pin the LED is wired to
Output LED active high Whether the LED pin is active high or low
Output buzzer (GPIO) Pin the buzzer is wired to
Output vibra (GPIO) Pin the vibration motor is wired to
Use PWM buzzer Drive the buzzer with PWM, which allows tones rather than a single pitch
Use I2S as buzzer Send the alert through an I2S audio output instead
Output duration (milliseconds) How long a single alert lasts
Nag timeout (seconds) Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Мелодија звона The tone played on a PWM buzzer, in RTTTL. Can be imported from a file

Store & Forward module

Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.

Setting Опис
Store & Forward enabled Activate store and forward
Heartbeat Periodically announce this node’s store-and-forward capability
Број записа Maximum stored messages
History return max Max messages to replay
History return window Time window for replay
Сервер Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)

💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.

Range Test module

⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.

Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.

Setting Опис
Range test enabled Activate range testing
Sender message interval (seconds) Time between test transmissions, chosen from a dropdown of fixed intervals
Save .CSV in storage (ESP32 only) Log received test data to the node’s own filesystem. ESP32 hardware only

Telemetry module

Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).

Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.

Setting Опис
Send Device Telemetry Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval How often to report battery, uptime and channel utilization
Environment metrics module enabled Report the attached environment sensors
Environment metrics update interval How often to report them
Environment metrics on-screen enabled Also show these readings on the device’s own display
Environment metrics use Fahrenheit Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Air quality metrics module enabled Report particulate and CO₂ sensor data
Air quality metrics update interval How often to report them
Power metrics module enabled Report the per-channel voltage and current readings
Power metrics update interval How often to report them
Power metrics on-screen enabled Also show power readings on the device’s display

See Telemetry & Sensors for supported sensors and configuration recommendations.

Canned Message module

Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.

Setting Опис
Canned message enabled ⚠️ Deprecated in the protobuf schema
Поруке Newline-separated list of messages
Send bell Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Rotary encoder #1 enabled Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port The three pins the encoder is wired to
Generate input event on Press / CW / CCW Which key event each encoder action produces
Up/Down/Select input enabled A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source ⚠️ Deprecated in the protobuf schema

Audio module

Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.

Setting Опис
CODEC 2 enabled Activate audio module
CODEC2 sample rate Audio quality/bandwidth tradeoff
PTT pin GPIO pin for the push-to-talk button
I2S word select GPIO pin for I2S WS
I2S data in GPIO pin for I2S DIN
I2S data out GPIO pin for I2S DOUT
I2S clock GPIO pin for the I2S bit clock

ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.

Remote Hardware module

GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.

⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.

Setting Опис
Remote Hardware enabled Activate remote GPIO access
Allow undefined pin access Allow access to any GPIO pin (security risk)
Available pins Up to 4 GPIO pins this node exposes for remote read/write

Neighbor Info module

Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.

Setting Опис
Neighbor Info enabled Activate neighbor broadcasting
Update interval (seconds) How often to broadcast neighbor list
Transmit over LoRa Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name

See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.

Ambient Lighting module

Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.

Setting Опис
LED state Turn the LED on or off
Струја LED current limit (0–31)
Red / Green / Blue Individual color channel values (0–255)

Detection Sensor module

Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.

Setting Опис
Detection Sensor enabled Activate detection sensor
GPIO pin to monitor GPIO pin connected to sensor
Detection trigger type How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Use INPUT_PULLUP mode Enable the pin’s internal pull-up resistor
Minimum broadcast (seconds) Minimum time between alert broadcasts
State broadcast (seconds) Periodic state broadcast interval
Send bell with alert message Include bell character in alerts
Пријатељски назив Custom name for this sensor

Paxcounter module

People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.

Setting Опис
Paxcounter enabled Activate people counting
Update interval (seconds) How often to report counts
Wi-Fi RSSI threshold Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE RSSI threshold The same cut-off for BLE advertisements (defaults to −80 dBm)

💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.

Status Message module

The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.

Mesh Beacon module

Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.

TAK module

Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.

Администрација

Удаљена администрација

Remotely configure nodes that share your admin key:

  1. Select the target node in the node list.
  2. Navigate to Settings for that node.
  3. Modify configuration.
  4. Tap Save — changes are sent over the mesh.

⚠️ Important: Requires an admin key configured on both your node and the target node.

Device Actions

Settings → Administration holds five one-shot actions, each behind a confirmation dialog:

Action What it does
Set time Sends your phone’s clock to the node
Поновно покретање Restarts the node
Искључи Powers the node down
Рестартовање на фабричка подешавања Returns every setting to its factory default
Ресетовање базе чворова Clears the node database. This dialog carries a Preserve Favorites? switch

⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.

Backup & Restore

Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.

Напредно

Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.

Clean Node Database

Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.

  • Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
  • Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.

The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.

Панел за отклањање грешака

Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.

Подешавања апликације

The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:

Privacy

  • Allow analytics and crash reporting — opt in or out of diagnostics.
  • Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
  • Homoglyph encoding — how look-alike characters in names are handled.

Appearance

  • Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
  • Theme and Language.
  • Show full message timestamps.

Persistence

  • A cache limit for how much history is kept.
  • Export rangetest packets, Export all packets and Export node database.

On their own

  • Node Layout — how much detail each row of the node list shows.
  • Wi-Fi Provisioning for mPWRD-OS — see Connections.
  • Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
  • System AI — appears only where app functions are available; see App Functions.

A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.

О

Settings → About carries the app’s own identity rather than the node’s:

Three sections:

  • What is Meshtastic? — a short description of the project.
  • Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
  • Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.

The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.

Acknowledgements

Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.

Troubleshooting remote admin

  • “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
  • Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
  • Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
+ Settings — Modules & Admin | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Српски (Ћирилица)
Meshtastic Docs ↗

🌐 Српски (Ћирилица) — Community translation View in English

Settings — Modules & Admin

Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.

💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.

Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:

A toggle setting in the on position

A dropdown setting, expanded to show its list of options

A text field setting with a value entered

A module settings card with its title and grouped controls

Конфигурација модула

Every module lives under Settings → Module configuration.

⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes.

MQTT module

Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.

Setting Опис
MQTT enabled Toggle MQTT bridge
Адреса MQTT broker address
Корисничко име Authentication username
Лозинка Authentication password
Encryption enabled Encrypt MQTT payloads
JSON output enabled Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS enabled Use secure connection
Root topic Base MQTT topic path
Proxy to client enabled Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy on this phone The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT
Map reporting Publish position to the public map — see the Map reporting group that follows

Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:

Setting Опис
I agree. Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Интервал објављивања мапе How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered

See MQTT for a detailed usage guide including encryption, privacy, and broker setup.

Serial module

Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.

Setting Опис
Serial enabled Activate serial communication
Echo enabled Echo received serial data back
Serial mode Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX GPIO pins for the serial connection
Serial baud rate Port speed
Временско ограничење How long to wait before considering an incoming message complete
Override console serial port Take over the port the debug console normally uses

External Notification module

Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.

There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.

Setting Опис
External notification enabled Master toggle for the module
Alert message LED / buzzer / vibra Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra Which outputs fire on a received bell character
Output LED (GPIO) Pin the LED is wired to
Output LED active high Whether the LED pin is active high or low
Output buzzer (GPIO) Pin the buzzer is wired to
Output vibra (GPIO) Pin the vibration motor is wired to
Use PWM buzzer Drive the buzzer with PWM, which allows tones rather than a single pitch
Use I2S as buzzer Send the alert through an I2S audio output instead
Трајање GPIO излаза How long a single alert lasts
Nag Timeout Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Мелодија звона The tone played on a PWM buzzer, in RTTTL. Can be imported from a file

Store & Forward module

Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.

Setting Опис
Store & Forward enabled Activate store and forward
Heartbeat Periodically announce this node’s store-and-forward capability
Број записа Maximum stored messages
History return max Max messages to replay
History return window Time window for replay
Сервер Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)

💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.

Range Test module

⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.

Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.

Setting Опис
Range test enabled Activate range testing
Инерварл пошиљаоца Time between test transmissions, chosen from a dropdown of fixed intervals
Save .CSV in storage (ESP32 only) Log received test data to the node’s own filesystem. ESP32 hardware only

Telemetry module

Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).

Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.

Setting Опис
Send Device Telemetry Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval How often to report battery, uptime and channel utilization
Environment metrics module enabled Report the attached environment sensors
Environment metrics update interval How often to report them
Environment metrics on-screen enabled Also show these readings on the device’s own display
Environment metrics use Fahrenheit Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Air quality metrics module enabled Report particulate and CO₂ sensor data
Air quality metrics update interval How often to report them
Power metrics module enabled Report the per-channel voltage and current readings
Power metrics update interval How often to report them
Power metrics on-screen enabled Also show power readings on the device’s display

See Telemetry & Sensors for supported sensors and configuration recommendations.

Canned Message module

Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.

Setting Опис
Canned message enabled ⚠️ Deprecated in the protobuf schema
Поруке Newline-separated list of messages
Send bell Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Rotary encoder #1 enabled Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port The three pins the encoder is wired to
Generate input event on Press / CW / CCW Which key event each encoder action produces
Up/Down/Select input enabled A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source ⚠️ Deprecated in the protobuf schema

Audio module

Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.

Setting Опис
CODEC 2 enabled Activate audio module
CODEC2 sample rate Audio quality/bandwidth tradeoff
PTT pin GPIO pin for the push-to-talk button
I2S word select GPIO pin for I2S WS
I2S data in GPIO pin for I2S DIN
I2S data out GPIO pin for I2S DOUT
I2S clock GPIO pin for the I2S bit clock

ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.

Remote Hardware module

GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.

⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.

Setting Опис
Remote Hardware enabled Activate remote GPIO access
Allow undefined pin access Allow access to any GPIO pin (security risk)
Available pins Up to 4 GPIO pins this node exposes for remote read/write

Neighbor Info module

Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.

Setting Опис
Neighbor Info enabled Activate neighbor broadcasting
Интервал ажурирања How often to broadcast neighbor list
Transmit over LoRa Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name

See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.

Ambient Lighting module

Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.

Setting Опис
LED state Turn the LED on or off
Струја LED current limit (0–31)
Red / Green / Blue Individual color channel values (0–255)

Detection Sensor module

Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.

Setting Опис
Detection Sensor enabled Activate detection sensor
GPIO pin to monitor GPIO pin connected to sensor
Detection trigger type How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Use INPUT_PULLUP mode Enable the pin’s internal pull-up resistor
Минимално време између емитовања детекције Minimum time between alert broadcasts
Интервал емитовања стања Periodic state broadcast interval
Send bell with alert message Include bell character in alerts
Пријатељски назив Custom name for this sensor

Paxcounter module

People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.

Setting Опис
Paxcounter enabled Activate people counting
Интервал ажурирања How often to report counts
WiFi Threshold (dBm) Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm) The same cut-off for BLE advertisements (defaults to −80 dBm)

💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.

Status Message module

The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.

Mesh Beacon module

Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.

TAK module

Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.

Администрација

Удаљена администрација

Remotely configure nodes that share your admin key:

  1. Select the target node in the node list.
  2. Navigate to Settings for that node.
  3. Modify configuration.
  4. Tap Save — changes are sent over the mesh.

⚠️ Important: Requires an admin key configured on both your node and the target node.

Device Actions

Settings → Administration holds five one-shot actions, each behind a confirmation dialog:

Action What it does
Set time Sends your phone’s clock to the node
Поновно покретање Restarts the node
Искључи Powers the node down
Рестартовање на фабричка подешавања Returns every setting to its factory default
Ресетовање базе чворова Clears the node database. This dialog carries a Preserve Favorites? switch

⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.

Backup & Restore

Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.

Напредно

Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.

Clean Node Database

Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.

  • Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
  • Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.

The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.

Панел за отклањање грешака

Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.

Подешавања апликације

The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:

Privacy

  • Allow analytics and crash reporting — opt in or out of diagnostics.
  • Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
  • Homoglyph encoding — how look-alike characters in names are handled.

Appearance

  • Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
  • Theme and Language.
  • Show full message timestamps.

Persistence

  • A cache limit for how much history is kept.
  • Export rangetest packets, Export all packets and Export node database.

On their own

  • Node Layout — how much detail each row of the node list shows.
  • Wi-Fi Provisioning for mPWRD-OS — see Connections.
  • Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
  • System AI — appears only where app functions are available; see App Functions.

A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.

О

Settings → About carries the app’s own identity rather than the node’s:

Three sections:

  • What is Meshtastic? — a short description of the project.
  • Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
  • Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.

The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.

Acknowledgements

Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.

Troubleshooting remote admin

  • “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
  • Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
  • Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
diff --git a/main/srp/user/settings-radio-user.html b/main/srp/user/settings-radio-user.html index 74d1477030..3eb44dab9c 100644 --- a/main/srp/user/settings-radio-user.html +++ b/main/srp/user/settings-radio-user.html @@ -1 +1 @@ - Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Српски (Ћирилица)
Meshtastic Docs ↗

🌐 Српски (Ћирилица) — Community translation View in English

Settings — Radio & User

Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How these screens work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Опис
Дуго име Your display name (up to 39 characters)
Кратко име 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Unmessageable Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur node (Ham) Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in.

Configuration

Подешавања уређаја

On Settings → Device configuration → Device.

Setting Опис Подразумевано
Улога уређаја Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Режим реемитовања How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Интервал емитовања информација о чвору How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Двоструки додир као дугме Treat a double tap as a button press Онемогућено
Троструки клик за Ad Hoc пинг Send an ad-hoc position ping on a triple click Омогућено
LED срчани откуцаји Blink the status LED periodically Омогућено
Временска зона POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it —
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to —

LoRA подешавања

On Settings → LoRa.

Setting Опис Подразумевано
Регион Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number Unset (must configure)
Унапред подешено Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Transmit Power Transmission power (dBm); 0 = max allowed for region 0 (region max)
Измена фреквенције Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Користи предефинисано подешавање On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Фактор ширења Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead From preset
Стопа кодирања Manual mode only: 5–8. More redundancy costs airtime From preset
Проток Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Фреквенцијски слот Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Трансмитер укључен Turning this off makes the node receive-only On
Override Duty Cycle Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Искључен
Игнориши MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Позитиван за MQTT Allow your packets to be forwarded to MQTT by gateways Искључен
Појачање пријемника Extra receive gain on SX126x radios; costs a little current Искључен
PA fan disabled Turn off the power-amplifier fan on hardware that has one Искључен

The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set.

Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Брзина SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a modem preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Подешавања приказа

On Settings → Device configuration → Display. These control the node’s own screen, not the app’s.

Setting Опис
Екран укључен за How long the display stays lit before sleeping
Carousel interval How often the node cycles between screens on its own
Display mode Screen layout/density used by the firmware
Display units Metric or Imperial on the node’s screen
Use 12h clock format Show the node’s clock as 12-hour rather than 24-hour
Bold Heading Draw the screen’s heading text in bold
Flip screen Rotate the display 180° for an inverted mounting
OLED type Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED
Wake on tap or motion Light the screen when the node is tapped or moved
Compass orientation Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each
Увек усмеравајте на север Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Подешавања позиције

On Settings → Device configuration → Position.

Setting Опис
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the node asks its GPS for a fix
Интервал емитовања How often the position is shared with the mesh
Паметно позиционирање Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Фиксна локација Use a manually entered latitude, longitude and altitude instead of the GPS
Заставице позиције A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Подешавања напајња

On Settings → Device configuration → Power.

Setting Опис
Enable power saving mode Let the node sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the node stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC multiplier override ratio The correction factor itself, used only when the override is on
Battery INA_2XX I2C address Address of an external INA-series power sensor, if fitted

Конфигурација мреже

On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node.

Setting Опис
Wi-Fi enabled Enable the Wi-Fi node (ESP32 nodes)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Лозинка Network password
Ethernet enabled Use a wired connection on hardware that has one
IPv4 mode DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP server Time synchronization server
rsyslog server Remote logging server

Network Config with a static IPv4 address entered

Блутут подешавања

On Settings → Device configuration → Bluetooth, on nodes with Bluetooth.

Setting Опис
Bluetooth enabled Enable/disable BLE radio
Pairing mode Fixed PIN, Random PIN, or No PIN
Fixed PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Сигурносна подешавања

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

Setting Опис
Јавни кључ Your node’s public key (read-only)
Admin Key Keys permitted to administer this node remotely — up to three
Приватни кључ Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it
Regenerate Private Key Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Serial console Serial console over the Stream API
Debug log API enabled Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth
Managed Mode Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.

+ Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Српски (Ћирилица)
Meshtastic Docs ↗

🌐 Српски (Ћирилица) — Community translation View in English

Settings — Radio & User

Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How these screens work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Опис
Дуго име Your display name (up to 39 characters)
Кратко име 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Unmessageable Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur node (Ham) Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in.

Configuration

Подешавања уређаја

On Settings → Device configuration → Device.

Setting Опис Подразумевано
Улога уређаја Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Режим реемитовања How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Интервал емитовања информација о чвору How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Двоструки додир као дугме Treat a double tap as a button press Онемогућено
Троструки клик за Ad Hoc пинг Send an ad-hoc position ping on a triple click Омогућено
LED срчани откуцаји Blink the status LED periodically Омогућено
Временска зона POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it —
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to —

LoRA подешавања

On Settings → LoRa.

Setting Опис Подразумевано
Регион Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number Unset (must configure)
Унапред подешено Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Transmit Power (dBm) Transmission power; 0 = max allowed for region 0 (region max)
Измена фреквенције Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Користи предефинисано подешавање On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Фактор ширења Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead From preset
Стопа кодирања Manual mode only: 5–8. More redundancy costs airtime From preset
Проток Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Фреквенцијски слот Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Трансмитер укључен Turning this off makes the node receive-only On
Override Duty Cycle Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Искључен
Игнориши MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Позитиван за MQTT Allow your packets to be forwarded to MQTT by gateways Искључен
Појачање пријемника Extra receive gain on SX126x radios; costs a little current Искључен
PA fan disabled Turn off the power-amplifier fan on hardware that has one Искључен

The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set.

Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Брзина SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a modem preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Подешавања приказа

On Settings → Device configuration → Display. These control the node’s own screen, not the app’s.

Setting Опис
Екран укључен за How long the display stays lit before sleeping
Carousel interval How often the node cycles between screens on its own
Display mode Screen layout/density used by the firmware
Display units Metric or Imperial on the node’s screen
Use 12h clock format Show the node’s clock as 12-hour rather than 24-hour
Bold Heading Draw the screen’s heading text in bold
Flip screen Rotate the display 180° for an inverted mounting
OLED type Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED
Wake on tap or motion Light the screen when the node is tapped or moved
Compass orientation Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each
Увек усмеравајте на север Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Подешавања позиције

On Settings → Device configuration → Position.

Setting Опис
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the node asks its GPS for a fix
Интервал емитовања How often the position is shared with the mesh
Паметно позиционирање Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Фиксна локација Use a manually entered latitude, longitude and altitude instead of the GPS
Заставице позиције A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Подешавања напајња

On Settings → Device configuration → Power.

Setting Опис
Enable power saving mode Let the node sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the node stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC multiplier override ratio The correction factor itself, used only when the override is on
Battery INA_2XX I2C address Address of an external INA-series power sensor, if fitted

Конфигурација мреже

On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node.

Setting Опис
Wi-Fi enabled Enable the Wi-Fi node (ESP32 nodes)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Лозинка Network password
Ethernet enabled Use a wired connection on hardware that has one
IPv4 mode DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP server Time synchronization server
rsyslog server Remote logging server

Network Config with a static IPv4 address entered

Блутут подешавања

On Settings → Device configuration → Bluetooth, on nodes with Bluetooth.

Setting Опис
Bluetooth enabled Enable/disable BLE radio
Pairing mode Fixed PIN, Random PIN, or No PIN
Fixed PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Сигурносна подешавања

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

Setting Опис
Јавни кључ Your node’s public key (read-only)
Admin Key Keys permitted to administer this node remotely — up to three
Приватни кључ Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it
Regenerate Private Key Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Serial console Serial console over the Stream API
Debug log API enabled Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth
Managed Mode Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.

diff --git a/main/sv-rSE/user/discovery.html b/main/sv-rSE/user/discovery.html index 835e01fefe..43d8800c6c 100644 --- a/main/sv-rSE/user/discovery.html +++ b/main/sv-rSE/user/discovery.html @@ -5,4 +5,4 @@ ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) -

Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:.

What to look for What it means
All hops show Good SNR (green) Healthy path — messages flow reliably
One hop shows a poor SNR (orange or red) Weak link — this relay segment is fragile
Many hops (4+) Long path — consider repositioning a node to shorten it
Different path on retry Mesh is adapting — multiple routes exist (this is good!)

💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network.

Troubleshooting with Traceroute

  • No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key.
  • Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa.
  • Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position.
  • Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric.

Granninformation

The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh.

Enabling Neighbor Info

  1. Navigate to Settings → Module configuration → Neighbor Info.
  2. Enable the module.
  3. Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
  4. Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air.

Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.

Viewing neighbor data

  • Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors.
  • Each neighbor entry shows the node that was directly heard and its signal quality.
  • Combine neighbor data from multiple nodes to understand the full mesh topology.

ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further.

Node list as a discovery tool

The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively.

Finding new nodes

  • Sort by Last heard to see the most recently active nodes at the top.
  • Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes.

Assessing connectivity

  • Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed.
  • Sort by Distance to find nearby nodes and verify they’re reachable.
  • Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge).

Infrastructure audit

  • Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes.
  • Check their signal quality and last-heard times to verify your infrastructure nodes are healthy.

See Nodes for full details on filtering and sorting options.

Tips for Mesh exploration

  • Start with traceroute — it gives you immediate, actionable information about a specific path.
  • Enable Neighbor Info on key nodes — especially routers and repeaters, to build a picture of the backbone.
  • Check the map — node positions on the Map combined with signal data help you understand why some links are strong and others are weak.
  • Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly.
+

Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:.

What to look for What it means
All hops show Good SNR (green) Healthy path — messages flow reliably
One hop shows a poor SNR (orange or red) Weak link — this relay segment is fragile
Many hops (4+) Long path — consider repositioning a node to shorten it
Different path on retry Mesh is adapting — multiple routes exist (this is good!)

💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network.

Troubleshooting with Traceroute

  • No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key.
  • Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa.
  • Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position.
  • Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric.

Granninformation

The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh.

Enabling Neighbor Info

  1. Navigate to Settings → Module configuration → Neighbor Info.
  2. Enable the module.
  3. Set Update Interval. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
  4. Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air.

Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.

Viewing neighbor data

  • Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors.
  • Each neighbor entry shows the node that was directly heard and its signal quality.
  • Combine neighbor data from multiple nodes to understand the full mesh topology.

ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further.

Node list as a discovery tool

The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively.

Finding new nodes

  • Sort by Last heard to see the most recently active nodes at the top.
  • Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes.

Assessing connectivity

  • Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed.
  • Sort by Distance to find nearby nodes and verify they’re reachable.
  • Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge).

Infrastructure audit

  • Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes.
  • Check their signal quality and last-heard times to verify your infrastructure nodes are healthy.

See Nodes for full details on filtering and sorting options.

Tips for Mesh exploration

  • Start with traceroute — it gives you immediate, actionable information about a specific path.
  • Enable Neighbor Info on key nodes — especially routers and repeaters, to build a picture of the backbone.
  • Check the map — node positions on the Map combined with signal data help you understand why some links are strong and others are weak.
  • Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly.
diff --git a/main/sv-rSE/user/mqtt.html b/main/sv-rSE/user/mqtt.html index f67702ebf1..656462fb74 100644 --- a/main/sv-rSE/user/mqtt.html +++ b/main/sv-rSE/user/mqtt.html @@ -1,2 +1,2 @@ MQTT | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Svenska
Meshtastic Docs ↗

🌐 Svenska — Community translation View in English

MQTT

MQTT bridges your Meshtastic mesh network to the internet, enabling long-range communication beyond radio range.

Overview

The MQTT module connects your node to an MQTT broker, allowing:

  • Messages to reach nodes on different physical meshes via the internet
  • Integration with home automation and monitoring systems
  • Publishing node positions to the public Meshtastic map
  • Custom data pipelines for logging and alerting

How It Works 

[Your Node] → Radio → [Gateway Node with Wi-Fi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node]
-

A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh.

Konfiguration

Enabling MQTT

  1. Navigate to Settings → Module configuration → MQTT.
  2. Enable the MQTT module.
  3. Configure the broker connection:
Setting Beskrivning Förvald
Address MQTT broker hostname mqtt.meshtastic.org
Username Broker authentication meshdev
Password Broker authentication large4cats
Root topic Base topic for messages msh, which the radio rewrites to msh/<REGION> once you set a region
Encryption enabled Encrypt MQTT payload Aktiverad
JSON output enabled Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it Disabled
TLS enabled Secure connection to broker Disabled
Map reporting Report position to public map Disabled
Proxy to client enabled Relay MQTT through the connected phone Disabled

Connection Status and Test Connection

The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here.

Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason.

MQTT Proxy on This Phone

If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection.

ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them.

The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration.

Default Meshtastic Broker

The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing.

When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without).

🔒 Privacy: Messages on the public broker are readable by anyone subscribed. Always use channel encryption for private communications.

Private Broker

For better privacy and control, you can run your own MQTT broker:

  • Mosquitto (lightweight, open-source)
  • HiveMQ
  • EMQX

Configure your node to point to your private broker with appropriate credentials.

Map Reporting

When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.

Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.

Reports appear at meshmap.net and similar community map services.

🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published.

Direction Beskrivning
Uplink Messages from mesh → MQTT broker
Downlink Messages from MQTT broker → mesh

Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on.

Message Formats

MQTT carries two payload formats:

Format Beskrivning Use case
Protobuf Binary Meshtastic protobuf encoding Node-to-node mesh bridging
JSON Human-readable JSON on the /2/json/ topic Consumers outside the mesh (dashboards, home automation)

ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads.

Encryption & Privacy

Understanding the layered encryption model:

  1. Channel encryption happens on the mesh before MQTT. If your channel has a PSK, the MQTT payload is already encrypted — the broker and any subscribers see only the ciphertext.
  2. Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard.
  3. TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping.

🔒 Security: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications.

Best Practices

  • Use channel-level encryption (PSK) on channels that bridge to MQTT
  • Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes memory)
  • Use a private broker for sensitive deployments
  • Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh
  • Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back

Felsökning

MQTT Not Connecting

  • Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself.
  • Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces.
  • Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443).
  • DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly.

Messages Not Bridging

  • Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway.
  • Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage.
  • Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root.
  • Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway.
  • Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in.
+

A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh.

Konfiguration

Enabling MQTT

  1. Navigate to Settings → Module configuration → MQTT.
  2. Enable the MQTT module.
  3. Configure the broker connection:
Setting Beskrivning Förvald
Address MQTT broker hostname mqtt.meshtastic.org
Username Broker authentication meshdev
Password Broker authentication large4cats
Root topic Base topic for messages msh, which the radio rewrites to msh/<REGION> once you set a region
Encryption enabled Encrypt MQTT payload Aktiverad
JSON output enabled Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it Disabled
TLS enabled Secure connection to broker Disabled
Map reporting Report position to public map Disabled
Proxy to client enabled Relay MQTT through the connected phone Disabled

Connection Status and Test Connection

The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here.

Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason.

MQTT Proxy on This Phone

If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection.

ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them.

The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration.

Default Meshtastic Broker

The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing.

When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without).

🔒 Privacy: Messages on the public broker are readable by anyone subscribed. Always use channel encryption for private communications.

Private Broker

For better privacy and control, you can run your own MQTT broker:

  • Mosquitto (lightweight, open-source)
  • HiveMQ
  • EMQX

Configure your node to point to your private broker with appropriate credentials.

Map Reporting

When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.

Turning it on opens a consent card. Turn on I agree. and choose a Map Publish Interval of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.

Reports appear at meshmap.net and similar community map services.

🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published.

Direction Beskrivning
Uplink Messages from mesh → MQTT broker
Downlink Messages from MQTT broker → mesh

Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on.

Message Formats

MQTT carries two payload formats:

Format Beskrivning Use case
Protobuf Binary Meshtastic protobuf encoding Node-to-node mesh bridging
JSON Human-readable JSON on the /2/json/ topic Consumers outside the mesh (dashboards, home automation)

ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads.

Encryption & Privacy

Understanding the layered encryption model:

  1. Channel encryption happens on the mesh before MQTT. If your channel has a PSK, the MQTT payload is already encrypted — the broker and any subscribers see only the ciphertext.
  2. Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard.
  3. TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping.

🔒 Security: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications.

Best Practices

  • Use channel-level encryption (PSK) on channels that bridge to MQTT
  • Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes memory)
  • Use a private broker for sensitive deployments
  • Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh
  • Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back

Felsökning

MQTT Not Connecting

  • Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself.
  • Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces.
  • Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443).
  • DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly.

Messages Not Bridging

  • Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway.
  • Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage.
  • Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root.
  • Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway.
  • Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in.
diff --git a/main/sv-rSE/user/settings-module-admin.html b/main/sv-rSE/user/settings-module-admin.html index 77f439d9ae..2f0b44b904 100644 --- a/main/sv-rSE/user/settings-module-admin.html +++ b/main/sv-rSE/user/settings-module-admin.html @@ -1 +1 @@ - Settings — Modules & Admin | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Svenska
Meshtastic Docs ↗

🌐 Svenska — Community translation View in English

Settings — Modules & Admin

Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.

💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.

Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:

A toggle setting in the on position

A dropdown setting, expanded to show its list of options

A text field setting with a value entered

A module settings card with its title and grouped controls

Modul konfiguration

Every module lives under Settings → Module configuration.

⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes.

MQTT module

Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.

Setting Beskrivning
MQTT är aktiverat Toggle MQTT bridge
Adress MQTT broker address
Användarnamn Authentication username
Lösenord Authentication password
Kryptering aktiverad Encrypt MQTT payloads
JSON-utdata aktiverad Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS är aktiverat Use secure connection
Rotämne (root topic) Base MQTT topic path
Proxy till klient aktiverad Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy on this phone The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT
Map reporting Publish position to the public map — see the Map reporting group that follows

Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:

Setting Beskrivning
Jag godkänner. Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map reporting interval (seconds) How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered

See MQTT for a detailed usage guide including encryption, privacy, and broker setup.

Serial module

Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.

Setting Beskrivning
Seriell aktiverad Activate serial communication
Eko aktiverad Echo received serial data back
Seriellt läge Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX GPIO pins for the serial connection
Den seriella kommunikationens hastighet Port speed
Timeout How long to wait before considering an incoming message complete
Override console serial port Take over the port the debug console normally uses

External Notification module

Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.

There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.

Setting Beskrivning
Externa aviseringar aktiverad Master toggle for the module
Alert message LED / buzzer / vibra Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra Which outputs fire on a received bell character
Utmatning LED (GPIO) Pin the LED is wired to
Utmatnings-LED aktiv hög Whether the LED pin is active high or low
Utmatning summer (GPIO) Pin the buzzer is wired to
Utmatning vibration (GPIO) Pin the vibration motor is wired to
Använd PWM-summern Drive the buzzer with PWM, which allows tones rather than a single pitch
Använd I2S som summer Send the alert through an I2S audio output instead
Utmatningstid (millisekunder) How long a single alert lasts
Sluta tjata efter (sekunder) Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Ringsignal The tone played on a PWM buzzer, in RTTTL. Can be imported from a file

Store & Forward module

Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.

Setting Beskrivning
Lagra & vidarebefordra är aktiverad Activate store and forward
Pulsera Periodically announce this node’s store-and-forward capability
Antal poster Maximum stored messages
Maxstorlek för historik Max messages to replay
Returfönstrets storlek för historik Time window for replay
Server Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)

💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.

Range Test module

⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.

Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.

Setting Beskrivning
Räckvidstest aktiverat Activate range testing
Avsändarens meddelandeintervall (sekunder) Time between test transmissions, chosen from a dropdown of fixed intervals
Spara .CSV i enheten (endast ESP32) Log received test data to the node’s own filesystem. ESP32 hardware only

Telemetry module

Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).

Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.

Setting Beskrivning
Skicka enhetstelemetri Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Uppdateringsintervall för enhetsdata How often to report battery, uptime and channel utilization
Mätmodul för miljö aktiverad Report the attached environment sensors
Uppdateringsintervall för miljödata How often to report them
Visning av miljödata på skärm är aktiverad Also show these readings on the device’s own display
Miljömätvärden använder Fahrenheit Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Luftkvalitetsmätarmodul aktiverad Report particulate and CO₂ sensor data
Uppdateringsintervall för luftkvalitet How often to report them
Strömmätarmodul aktiverad Report the per-channel voltage and current readings
Uppdateringsintervall för strömmätare How often to report them
Visning av strömvärden på skärm är aktiverad Also show power readings on the device’s display

See Telemetry & Sensors for supported sensors and configuration recommendations.

Canned Message module

Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.

Setting Beskrivning
Canned message enabled ⚠️ Deprecated in the protobuf schema
Meddelanden Newline-separated list of messages
Skicka ljudavisering Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Rotary encoder #1 enabled Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port The three pins the encoder is wired to
Generate input event on Press / CW / CCW Which key event each encoder action produces
Up/Down/Select input enabled A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source ⚠️ Deprecated in the protobuf schema

Audio module

Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.

Setting Beskrivning
CODEC 2 aktiverat Activate audio module
CODEC2 samplingshastighet Audio quality/bandwidth tradeoff
PTT pin GPIO pin for the push-to-talk button
I2S ordval GPIO pin for I2S WS
I2S-data in GPIO pin for I2S DIN
I2S-data ut GPIO pin for I2S DOUT
I2S-klocka GPIO pin for the I2S bit clock

ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.

Remote Hardware module

GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.

⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.

Setting Beskrivning
Fjärrhårdvara aktiverad Activate remote GPIO access
Allow undefined pin access Allow access to any GPIO pin (security risk)
Tillgängliga pin Up to 4 GPIO pins this node exposes for remote read/write

Neighbor Info module

Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.

Setting Beskrivning
Grannskapsinformation aktiverat Activate neighbor broadcasting
Uppdateringsintervall (sekunder) How often to broadcast neighbor list
Skicka över LoRa Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name

See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.

Ambient Lighting module

Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.

Setting Beskrivning
LED-läge Turn the LED on or off
Ström LED current limit (0–31)
Red / Green / Blue Individual color channel values (0–255)

Detection Sensor module

Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.

Setting Beskrivning
Detektionssensor aktiverad Activate detection sensor
GPIO-pin att övervaka GPIO pin connected to sensor
Detection trigger type How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Använd INPUT_PULLUP-läge Enable the pin’s internal pull-up resistor
Minsta sändningsintervall (sekunder) Minimum time between alert broadcasts
Statussändningsintervall (sekunder) Periodic state broadcast interval
Skicka ljudavisering med larmmeddelande Include bell character in alerts
Visningsnamn Custom name for this sensor

Paxcounter module

People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.

Setting Beskrivning
PAX-räknare aktiverad Activate people counting
Uppdateringsintervall (sekunder) How often to report counts
Wi-Fi RSSI threshold Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE RSSI threshold The same cut-off for BLE advertisements (defaults to −80 dBm)

💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.

Status Message module

The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.

Mesh Beacon module

Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.

TAK module

Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.

Administration

Fjärradministration

Remotely configure nodes that share your admin key:

  1. Select the target node in the node list.
  2. Navigate to Settings for that node.
  3. Modify configuration.
  4. Tap Save — changes are sent over the mesh.

⚠️ Important: Requires an admin key configured on both your node and the target node.

Device Actions

Settings → Administration holds five one-shot actions, each behind a confirmation dialog:

Action What it does
Ställ in tid Sends your phone’s clock to the node
Starta om Restarts the node
Stäng av Powers the node down
Återställ till standardinställningar Returns every setting to its factory default
Nollställ NodeDB Clears the node database. This dialog carries a Preserve Favorites? switch

⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.

Säkerhetskopiering och återställning

Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.

Advancerat

Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.

Rensa noddatabas

Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.

  • Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
  • Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.

The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.

Felsökningspanel

Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.

App Settings

The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:

Privacy

  • Allow analytics and crash reporting — opt in or out of diagnostics.
  • Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
  • Homoglyph encoding — how look-alike characters in names are handled.

Appearance

  • Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
  • Theme and Language.
  • Show full message timestamps.

Persistence

  • A cache limit for how much history is kept.
  • Export rangetest packets, Export all packets and Export node database.

On their own

  • Node Layout — how much detail each row of the node list shows.
  • Wi-Fi Provisioning for mPWRD-OS — see Connections.
  • Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
  • System AI — appears only where app functions are available; see App Functions.

A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.

Om

Settings → About carries the app’s own identity rather than the node’s:

Three sections:

  • What is Meshtastic? — a short description of the project.
  • Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
  • Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.

The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.

Bekräftelser

Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.

Troubleshooting remote admin

  • “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
  • Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
  • Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
+ Settings — Modules & Admin | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Svenska
Meshtastic Docs ↗

🌐 Svenska — Community translation View in English

Settings — Modules & Admin

Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.

💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.

Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:

A toggle setting in the on position

A dropdown setting, expanded to show its list of options

A text field setting with a value entered

A module settings card with its title and grouped controls

Modul konfiguration

Every module lives under Settings → Module configuration.

⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes.

MQTT module

Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.

Setting Beskrivning
MQTT är aktiverat Toggle MQTT bridge
Adress MQTT broker address
Användarnamn Authentication username
Lösenord Authentication password
Kryptering aktiverad Encrypt MQTT payloads
JSON-utdata aktiverad Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS är aktiverat Use secure connection
Rotämne (root topic) Base MQTT topic path
Proxy till klient aktiverad Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy on this phone The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT
Map reporting Publish position to the public map — see the Map reporting group that follows

Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:

Setting Beskrivning
Jag godkänner. Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered

See MQTT for a detailed usage guide including encryption, privacy, and broker setup.

Serial module

Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.

Setting Beskrivning
Seriell aktiverad Activate serial communication
Eko aktiverad Echo received serial data back
Seriellt läge Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX GPIO pins for the serial connection
Den seriella kommunikationens hastighet Port speed
Timeout How long to wait before considering an incoming message complete
Override console serial port Take over the port the debug console normally uses

External Notification module

Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.

There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.

Setting Beskrivning
Externa aviseringar aktiverad Master toggle for the module
Alert message LED / buzzer / vibra Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra Which outputs fire on a received bell character
Utmatning LED (GPIO) Pin the LED is wired to
Utmatnings-LED aktiv hög Whether the LED pin is active high or low
Utmatning summer (GPIO) Pin the buzzer is wired to
Utmatning vibration (GPIO) Pin the vibration motor is wired to
Använd PWM-summern Drive the buzzer with PWM, which allows tones rather than a single pitch
Använd I2S som summer Send the alert through an I2S audio output instead
GPIO Output Duration How long a single alert lasts
Time-out för påminnelse Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Ringsignal The tone played on a PWM buzzer, in RTTTL. Can be imported from a file

Store & Forward module

Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.

Setting Beskrivning
Lagra & vidarebefordra är aktiverad Activate store and forward
Pulsera Periodically announce this node’s store-and-forward capability
Antal poster Maximum stored messages
Maxstorlek för historik Max messages to replay
Returfönstrets storlek för historik Time window for replay
Server Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)

💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.

Range Test module

⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.

Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.

Setting Beskrivning
Räckvidstest aktiverat Activate range testing
Sender Interval Time between test transmissions, chosen from a dropdown of fixed intervals
Spara .CSV i enheten (endast ESP32) Log received test data to the node’s own filesystem. ESP32 hardware only

Telemetry module

Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).

Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.

Setting Beskrivning
Skicka enhetstelemetri Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Uppdateringsintervall för enhetsdata How often to report battery, uptime and channel utilization
Mätmodul för miljö aktiverad Report the attached environment sensors
Uppdateringsintervall för miljödata How often to report them
Visning av miljödata på skärm är aktiverad Also show these readings on the device’s own display
Miljömätvärden använder Fahrenheit Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Luftkvalitetsmätarmodul aktiverad Report particulate and CO₂ sensor data
Uppdateringsintervall för luftkvalitet How often to report them
Strömmätarmodul aktiverad Report the per-channel voltage and current readings
Uppdateringsintervall för strömmätare How often to report them
Visning av strömvärden på skärm är aktiverad Also show power readings on the device’s display

See Telemetry & Sensors for supported sensors and configuration recommendations.

Canned Message module

Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.

Setting Beskrivning
Canned message enabled ⚠️ Deprecated in the protobuf schema
Meddelanden Newline-separated list of messages
Skicka ljudavisering Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Rotary encoder #1 enabled Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port The three pins the encoder is wired to
Generate input event on Press / CW / CCW Which key event each encoder action produces
Up/Down/Select input enabled A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source ⚠️ Deprecated in the protobuf schema

Audio module

Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.

Setting Beskrivning
CODEC 2 aktiverat Activate audio module
CODEC2 samplingshastighet Audio quality/bandwidth tradeoff
PTT pin GPIO pin for the push-to-talk button
I2S ordval GPIO pin for I2S WS
I2S-data in GPIO pin for I2S DIN
I2S-data ut GPIO pin for I2S DOUT
I2S-klocka GPIO pin for the I2S bit clock

ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.

Remote Hardware module

GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.

⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.

Setting Beskrivning
Fjärrhårdvara aktiverad Activate remote GPIO access
Allow undefined pin access Allow access to any GPIO pin (security risk)
Tillgängliga pin Up to 4 GPIO pins this node exposes for remote read/write

Neighbor Info module

Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.

Setting Beskrivning
Grannskapsinformation aktiverat Activate neighbor broadcasting
Intervall för hämtning av GPS-position How often to broadcast neighbor list
Skicka över LoRa Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name

See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.

Ambient Lighting module

Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.

Setting Beskrivning
LED-läge Turn the LED on or off
Ström LED current limit (0–31)
Red / Green / Blue Individual color channel values (0–255)

Detection Sensor module

Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.

Setting Beskrivning
Detektionssensor aktiverad Activate detection sensor
GPIO-pin att övervaka GPIO pin connected to sensor
Detection trigger type How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Använd INPUT_PULLUP-läge Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts Minimum time between alert broadcasts
State Broadcast Interval Periodic state broadcast interval
Skicka ljudavisering med larmmeddelande Include bell character in alerts
Visningsnamn Custom name for this sensor

Paxcounter module

People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.

Setting Beskrivning
PAX-räknare aktiverad Activate people counting
Intervall för hämtning av GPS-position How often to report counts
WiFi Threshold (dBm) Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm) The same cut-off for BLE advertisements (defaults to −80 dBm)

💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.

Status Message module

The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.

Mesh Beacon module

Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.

TAK module

Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.

Administration

Fjärradministration

Remotely configure nodes that share your admin key:

  1. Select the target node in the node list.
  2. Navigate to Settings for that node.
  3. Modify configuration.
  4. Tap Save — changes are sent over the mesh.

⚠️ Important: Requires an admin key configured on both your node and the target node.

Device Actions

Settings → Administration holds five one-shot actions, each behind a confirmation dialog:

Action What it does
Ställ in tid Sends your phone’s clock to the node
Starta om Restarts the node
Stäng av Powers the node down
Återställ till standardinställningar Returns every setting to its factory default
Nollställ NodeDB Clears the node database. This dialog carries a Preserve Favorites? switch

⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.

Säkerhetskopiering och återställning

Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.

Advancerat

Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.

Rensa noddatabas

Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.

  • Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
  • Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.

The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.

Felsökningspanel

Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.

App Settings

The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:

Privacy

  • Allow analytics and crash reporting — opt in or out of diagnostics.
  • Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
  • Homoglyph encoding — how look-alike characters in names are handled.

Appearance

  • Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
  • Theme and Language.
  • Show full message timestamps.

Persistence

  • A cache limit for how much history is kept.
  • Export rangetest packets, Export all packets and Export node database.

On their own

  • Node Layout — how much detail each row of the node list shows.
  • Wi-Fi Provisioning for mPWRD-OS — see Connections.
  • Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
  • System AI — appears only where app functions are available; see App Functions.

A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.

Om

Settings → About carries the app’s own identity rather than the node’s:

Three sections:

  • What is Meshtastic? — a short description of the project.
  • Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
  • Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.

The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.

Bekräftelser

Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.

Troubleshooting remote admin

  • “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
  • Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
  • Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
diff --git a/main/sv-rSE/user/settings-radio-user.html b/main/sv-rSE/user/settings-radio-user.html index 5b0eef20ee..47564333ad 100644 --- a/main/sv-rSE/user/settings-radio-user.html +++ b/main/sv-rSE/user/settings-radio-user.html @@ -1 +1 @@ - Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Svenska
Meshtastic Docs ↗

🌐 Svenska — Community translation View in English

Settings — Radio & User

Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How these screens work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

Användarinställningar

User Profile

On Settings → User.

Setting Beskrivning
Långt namn Your display name (up to 39 characters)
Kort namn 4-character abbreviated name
Statusmeddelande A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Meddelanden läses ej Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur node (Ham) Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in.

Konfiguration

Enhetskonfiguration

On Settings → Device configuration → Device.

Setting Beskrivning Förvald
Enhetens roll Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Återutsändningsläge How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Sändningsintervall för nod-info How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Dubbeltryck som knapptryck Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Aktiverad
LED pulsering Blink the status LED periodically Aktiverad
Tidszon POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it —
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to —

LoRa Config

On Settings → LoRa.

Setting Beskrivning Förvald
Region Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number Unset (must configure)
Förval Speed/range tradeoff LongFast
Antal hopp Maximum retransmit hops 3
Sändningseffekt Transmission power (dBm); 0 = max allowed for region 0 (region max)
Åsidosätt Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Använd förinställning On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spridningsfaktor Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead From preset
Kodningshastighet Manual mode only: 5–8. More redundancy costs airtime From preset
Bandbredd Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Frekvens-slot Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Sändning aktiverad Turning this off makes the node receive-only On
Ersätt gräns för driftsperiod Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Av
Ignorera MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok till MQTT Allow your packets to be forwarded to MQTT by gateways Av
RX förstärkt gain Extra receive gain on SX126x radios; costs a little current Av
PA fan disabled Turn off the power-amplifier fan on hardware that has one Av

The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set.

Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Hastighet SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a modem preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Display Config

On Settings → Device configuration → Display. These control the node’s own screen, not the app’s.

Setting Beskrivning
Håll skärmen tänd How long the display stays lit before sleeping
Carousel interval How often the node cycles between screens on its own
Visningsläge Screen layout/density used by the firmware
Visa enheter Metric or Imperial on the node’s screen
Använd 12-timmarsformat Show the node’s clock as 12-hour rather than 24-hour
Fetstil för rubriktext Draw the screen’s heading text in bold
Vänd skärmen Rotate the display 180° for an inverted mounting
OLED-typ Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED
Vakna vid tryck eller rörelse Light the screen when the node is tapped or moved
Kompassriktning Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each
Peka alltid mot norr Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Position Config

On Settings → Device configuration → Position.

Setting Beskrivning
GPS-läge (fysisk maskinvara) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
Intervall för hämtning av GPS-position How often the node asks its GPS for a fix
Sändningsintervall How often the position is shared with the mesh
Smart position Broadcast based on movement rather than purely on the clock
Smart intervall With Smart Position on, the shortest gap between broadcasts
Smart distans With Smart Position on, how far you must move before broadcasting
Fast plats Use a manually entered latitude, longitude and altitude instead of the GPS
Positionsflaggor A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Ströminställningar

On Settings → Device configuration → Power.

Setting Beskrivning
Aktivera strömsparläge Let the node sleep aggressively between activity
Stäng av vid strömförlust Power the device down after external power disappears
Tid för djup strömsparläge How long the deepest sleep state lasts
Minimum wake time The shortest time the node stays awake once woken
Vänta in Bluetooth (sekunder) How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC multiplier override ratio The correction factor itself, used only when the override is on
Batteriets INA_2XX I2C-adress Address of an external INA-series power sensor, if fitted

Network Config

On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node.

Setting Beskrivning
Wi-Fi enabled Enable the Wi-Fi node (ESP32 nodes)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Lösenord Nätverkslösenord
Ethernet är aktiverat Use a wired connection on hardware that has one
IPv4-läge DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP-server Time synchronization server
rsyslog-server Remote logging server

Network Config with a static IPv4 address entered

Bluetooth-inställningar

On Settings → Device configuration → Bluetooth, on nodes with Bluetooth.

Setting Beskrivning
Bluetooth är aktiverad Enable/disable BLE radio
Parkopplingsläge Fixed PIN, Random PIN, or No PIN
Fast PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Security Config

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

Setting Beskrivning
Publik nyckel Your node’s public key (read-only)
Admin-nyckel Keys permitted to administer this node remotely — up to three
Privat nyckel Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it
Förnya nyckel Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Seriell konsol Serial console over the Stream API
API för debugloggen igång Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth
Hanterat läge Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set
Säkerhetskopiera nycklar Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Skyddsnivå How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.

+ Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Svenska
Meshtastic Docs ↗

🌐 Svenska — Community translation View in English

Settings — Radio & User

Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How these screens work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

Användarinställningar

User Profile

On Settings → User.

Setting Beskrivning
Långt namn Your display name (up to 39 characters)
Kort namn 4-character abbreviated name
Statusmeddelande A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Meddelanden läses ej Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur node (Ham) Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in.

Konfiguration

Enhetskonfiguration

On Settings → Device configuration → Device.

Setting Beskrivning Förvald
Enhetens roll Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Återutsändningsläge How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Sändningsintervall för nod-info How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Dubbeltryck som knapptryck Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Aktiverad
LED pulsering Blink the status LED periodically Aktiverad
Tidszon POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it —
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to —

LoRa Config

On Settings → LoRa.

Setting Beskrivning Förvald
Region Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number Unset (must configure)
Förval Speed/range tradeoff LongFast
Antal hopp Maximum retransmit hops 3
Transmit Power (dBm) Transmission power; 0 = max allowed for region 0 (region max)
Åsidosätt Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Använd förinställning On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spridningsfaktor Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead From preset
Kodningshastighet Manual mode only: 5–8. More redundancy costs airtime From preset
Bandbredd Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Frekvens-slot Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Sändning aktiverad Turning this off makes the node receive-only On
Ersätt gräns för driftsperiod Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Av
Ignorera MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok till MQTT Allow your packets to be forwarded to MQTT by gateways Av
RX förstärkt gain Extra receive gain on SX126x radios; costs a little current Av
PA fan disabled Turn off the power-amplifier fan on hardware that has one Av

The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set.

Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Hastighet SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a modem preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Display Config

On Settings → Device configuration → Display. These control the node’s own screen, not the app’s.

Setting Beskrivning
Håll skärmen tänd How long the display stays lit before sleeping
Carousel interval How often the node cycles between screens on its own
Visningsläge Screen layout/density used by the firmware
Visa enheter Metric or Imperial on the node’s screen
Använd 12-timmarsformat Show the node’s clock as 12-hour rather than 24-hour
Fetstil för rubriktext Draw the screen’s heading text in bold
Vänd skärmen Rotate the display 180° for an inverted mounting
OLED-typ Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED
Vakna vid tryck eller rörelse Light the screen when the node is tapped or moved
Kompassriktning Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each
Peka alltid mot norr Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Position Config

On Settings → Device configuration → Position.

Setting Beskrivning
GPS-läge (fysisk maskinvara) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
Intervall för hämtning av GPS-position How often the node asks its GPS for a fix
Sändningsintervall How often the position is shared with the mesh
Smart position Broadcast based on movement rather than purely on the clock
Smart intervall With Smart Position on, the shortest gap between broadcasts
Smart distans With Smart Position on, how far you must move before broadcasting
Fast plats Use a manually entered latitude, longitude and altitude instead of the GPS
Positionsflaggor A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Ströminställningar

On Settings → Device configuration → Power.

Setting Beskrivning
Aktivera strömsparläge Let the node sleep aggressively between activity
Stäng av vid strömförlust Power the device down after external power disappears
Tid för djup strömsparläge How long the deepest sleep state lasts
Minimum wake time The shortest time the node stays awake once woken
Vänta in Bluetooth (sekunder) How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC multiplier override ratio The correction factor itself, used only when the override is on
Batteriets INA_2XX I2C-adress Address of an external INA-series power sensor, if fitted

Network Config

On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node.

Setting Beskrivning
Wi-Fi enabled Enable the Wi-Fi node (ESP32 nodes)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Lösenord Nätverkslösenord
Ethernet är aktiverat Use a wired connection on hardware that has one
IPv4-läge DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP-server Time synchronization server
rsyslog-server Remote logging server

Network Config with a static IPv4 address entered

Bluetooth-inställningar

On Settings → Device configuration → Bluetooth, on nodes with Bluetooth.

Setting Beskrivning
Bluetooth är aktiverad Enable/disable BLE radio
Parkopplingsläge Fixed PIN, Random PIN, or No PIN
Fast PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Security Config

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

Setting Beskrivning
Publik nyckel Your node’s public key (read-only)
Admin-nyckel Keys permitted to administer this node remotely — up to three
Privat nyckel Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it
Förnya nyckel Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Seriell konsol Serial console over the Stream API
API för debugloggen igång Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth
Hanterat läge Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set
Säkerhetskopiera nycklar Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Skyddsnivå How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.

diff --git a/main/tr-rTR/user/discovery.html b/main/tr-rTR/user/discovery.html index 36df8fea1f..48242c3a07 100644 --- a/main/tr-rTR/user/discovery.html +++ b/main/tr-rTR/user/discovery.html @@ -5,4 +5,4 @@ ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) -

Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:.

What to look for What it means
All hops show Good SNR (green) Healthy path — messages flow reliably
One hop shows a poor SNR (orange or red) Weak link — this relay segment is fragile
Many hops (4+) Long path — consider repositioning a node to shorten it
Different path on retry Mesh is adapting — multiple routes exist (this is good!)

💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network.

Troubleshooting with Traceroute

  • No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key.
  • Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa.
  • Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position.
  • Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric.

Komşu Bilgisi

The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh.

Enabling Neighbor Info

  1. Navigate to Settings → Module configuration → Neighbor Info.
  2. Enable the module.
  3. Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
  4. Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air.

Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.

Viewing neighbor data

  • Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors.
  • Each neighbor entry shows the node that was directly heard and its signal quality.
  • Combine neighbor data from multiple nodes to understand the full mesh topology.

ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further.

Node list as a discovery tool

The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively.

Finding new nodes

  • Sort by Last heard to see the most recently active nodes at the top.
  • Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes.

Assessing connectivity

  • Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed.
  • Sort by Distance to find nearby nodes and verify they’re reachable.
  • Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge).

Infrastructure audit

  • Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes.
  • Check their signal quality and last-heard times to verify your infrastructure nodes are healthy.

See Nodes for full details on filtering and sorting options.

Tips for Mesh exploration

  • Start with traceroute — it gives you immediate, actionable information about a specific path.
  • Enable Neighbor Info on key nodes — especially routers and repeaters, to build a picture of the backbone.
  • Check the map — node positions on the Map combined with signal data help you understand why some links are strong and others are weak.
  • Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly.
+

Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:.

What to look for What it means
All hops show Good SNR (green) Healthy path — messages flow reliably
One hop shows a poor SNR (orange or red) Weak link — this relay segment is fragile
Many hops (4+) Long path — consider repositioning a node to shorten it
Different path on retry Mesh is adapting — multiple routes exist (this is good!)

💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network.

Troubleshooting with Traceroute

  • No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key.
  • Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa.
  • Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position.
  • Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric.

Komşu Bilgisi

The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh.

Enabling Neighbor Info

  1. Navigate to Settings → Module configuration → Neighbor Info.
  2. Enable the module.
  3. Set Update Interval. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
  4. Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air.

Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.

Viewing neighbor data

  • Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors.
  • Each neighbor entry shows the node that was directly heard and its signal quality.
  • Combine neighbor data from multiple nodes to understand the full mesh topology.

ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further.

Node list as a discovery tool

The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively.

Finding new nodes

  • Sort by Last heard to see the most recently active nodes at the top.
  • Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes.

Assessing connectivity

  • Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed.
  • Sort by Distance to find nearby nodes and verify they’re reachable.
  • Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge).

Infrastructure audit

  • Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes.
  • Check their signal quality and last-heard times to verify your infrastructure nodes are healthy.

See Nodes for full details on filtering and sorting options.

Tips for Mesh exploration

  • Start with traceroute — it gives you immediate, actionable information about a specific path.
  • Enable Neighbor Info on key nodes — especially routers and repeaters, to build a picture of the backbone.
  • Check the map — node positions on the Map combined with signal data help you understand why some links are strong and others are weak.
  • Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly.
diff --git a/main/tr-rTR/user/mqtt.html b/main/tr-rTR/user/mqtt.html index 7a4608bf26..d5b664873b 100644 --- a/main/tr-rTR/user/mqtt.html +++ b/main/tr-rTR/user/mqtt.html @@ -1,2 +1,2 @@ MQTT | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Türkçe
Meshtastic Docs ↗

🌐 Türkçe — Community translation View in English

MQTT

MQTT bridges your Meshtastic mesh network to the internet, enabling long-range communication beyond radio range.

Genel Bakış

The MQTT module connects your node to an MQTT broker, allowing:

  • Messages to reach nodes on different physical meshes via the internet
  • Integration with home automation and monitoring systems
  • Publishing node positions to the public Meshtastic map
  • Custom data pipelines for logging and alerting

How It Works 

[Your Node] → Radio → [Gateway Node with Wi-Fi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node]
-

A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh.

Yapılandırma

Enabling MQTT

  1. Navigate to Settings → Module configuration → MQTT.
  2. Enable the MQTT module.
  3. Configure the broker connection:
Setting Açıklaması Varsayılan
Address MQTT broker hostname mqtt.meshtastic.org
Username Broker authentication meshdev
Password Broker authentication large4cats
Root topic Base topic for messages msh, which the radio rewrites to msh/<REGION> once you set a region
Encryption enabled Encrypt MQTT payload Açık
JSON output enabled Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it Disabled
TLS enabled Secure connection to broker Disabled
Map reporting Report position to public map Disabled
Proxy to client enabled Relay MQTT through the connected phone Disabled

Connection Status and Test Connection

The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here.

Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason.

MQTT Proxy on This Phone

If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection.

ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them.

The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration.

Default Meshtastic Broker

The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing.

When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without).

🔒 Privacy: Messages on the public broker are readable by anyone subscribed. Always use channel encryption for private communications.

Private Broker

For better privacy and control, you can run your own MQTT broker:

  • Mosquitto (lightweight, open-source)
  • HiveMQ
  • EMQX

Configure your node to point to your private broker with appropriate credentials.

Map Reporting

When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.

Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.

Reports appear at meshmap.net and similar community map services.

🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published.

Direction Açıklaması
Uplink Messages from mesh → MQTT broker
Downlink Messages from MQTT broker → mesh

Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on.

Message Formats

MQTT carries two payload formats:

Format Açıklaması Use case
Protobuf Binary Meshtastic protobuf encoding Node-to-node mesh bridging
JSON Human-readable JSON on the /2/json/ topic Consumers outside the mesh (dashboards, home automation)

ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads.

Encryption & Privacy

Understanding the layered encryption model:

  1. Channel encryption happens on the mesh before MQTT. If your channel has a PSK, the MQTT payload is already encrypted — the broker and any subscribers see only the ciphertext.
  2. Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard.
  3. TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping.

🔒 Security: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications.

Best Practices

  • Use channel-level encryption (PSK) on channels that bridge to MQTT
  • Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes memory)
  • Use a private broker for sensitive deployments
  • Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh
  • Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back

Troubleshooting

MQTT Not Connecting

  • Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself.
  • Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces.
  • Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443).
  • DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly.

Messages Not Bridging

  • Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway.
  • Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage.
  • Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root.
  • Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway.
  • Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in.
+

A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh.

Yapılandırma

Enabling MQTT

  1. Navigate to Settings → Module configuration → MQTT.
  2. Enable the MQTT module.
  3. Configure the broker connection:
Setting Açıklaması Varsayılan
Address MQTT broker hostname mqtt.meshtastic.org
Username Broker authentication meshdev
Password Broker authentication large4cats
Root topic Base topic for messages msh, which the radio rewrites to msh/<REGION> once you set a region
Encryption enabled Encrypt MQTT payload Açık
JSON output enabled Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it Disabled
TLS enabled Secure connection to broker Disabled
Map reporting Report position to public map Disabled
Proxy to client enabled Relay MQTT through the connected phone Disabled

Connection Status and Test Connection

The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here.

Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason.

MQTT Proxy on This Phone

If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection.

ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them.

The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration.

Default Meshtastic Broker

The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing.

When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without).

🔒 Privacy: Messages on the public broker are readable by anyone subscribed. Always use channel encryption for private communications.

Private Broker

For better privacy and control, you can run your own MQTT broker:

  • Mosquitto (lightweight, open-source)
  • HiveMQ
  • EMQX

Configure your node to point to your private broker with appropriate credentials.

Map Reporting

When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.

Turning it on opens a consent card. Turn on I agree. and choose a Map Publish Interval of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.

Reports appear at meshmap.net and similar community map services.

🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published.

Direction Açıklaması
Uplink Messages from mesh → MQTT broker
Downlink Messages from MQTT broker → mesh

Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on.

Message Formats

MQTT carries two payload formats:

Format Açıklaması Use case
Protobuf Binary Meshtastic protobuf encoding Node-to-node mesh bridging
JSON Human-readable JSON on the /2/json/ topic Consumers outside the mesh (dashboards, home automation)

ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads.

Encryption & Privacy

Understanding the layered encryption model:

  1. Channel encryption happens on the mesh before MQTT. If your channel has a PSK, the MQTT payload is already encrypted — the broker and any subscribers see only the ciphertext.
  2. Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard.
  3. TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping.

🔒 Security: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications.

Best Practices

  • Use channel-level encryption (PSK) on channels that bridge to MQTT
  • Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes memory)
  • Use a private broker for sensitive deployments
  • Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh
  • Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back

Troubleshooting

MQTT Not Connecting

  • Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself.
  • Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces.
  • Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443).
  • DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly.

Messages Not Bridging

  • Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway.
  • Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage.
  • Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root.
  • Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway.
  • Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in.
diff --git a/main/tr-rTR/user/settings-module-admin.html b/main/tr-rTR/user/settings-module-admin.html index d038e582fb..10c9bfec06 100644 --- a/main/tr-rTR/user/settings-module-admin.html +++ b/main/tr-rTR/user/settings-module-admin.html @@ -1 +1 @@ - Settings — Modules & Admin | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Türkçe
Meshtastic Docs ↗

🌐 Türkçe — Community translation View in English

Settings — Modules & Admin

Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.

💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.

Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:

A toggle setting in the on position

A dropdown setting, expanded to show its list of options

A text field setting with a value entered

A module settings card with its title and grouped controls

Modül ayarları

Every module lives under Settings → Module configuration.

⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes.

MQTT module

Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.

Setting Açıklaması
MQTT etkin Toggle MQTT bridge
Adres MQTT broker address
Kullanıcı adı Authentication username
Şifre Authentication password
Şifreleme etkin Encrypt MQTT payloads
JSON çıktısı etkin Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS etkin Use secure connection
Ana konu Base MQTT topic path
Vekilden istemciye etkin Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy on this phone The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT
Harita raporlama Publish position to the public map — see the Map reporting group that follows

Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:

Setting Açıklaması
Katılıyorum. Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Harita raporlama aralığı (saniye) How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered

See MQTT for a detailed usage guide including encryption, privacy, and broker setup.

Serial module

Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.

Setting Açıklaması
Seri etkin Activate serial communication
Eko etkin Echo received serial data back
Seri modu Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX GPIO pins for the serial connection
Seri baud hızı Port speed
Zaman Aşımı How long to wait before considering an incoming message complete
Konsol seri portunu geçersiz kıl Take over the port the debug console normally uses

External Notification module

Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.

There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.

Setting Açıklaması
Harici bildirim etkin Master toggle for the module
Alert message LED / buzzer / vibra Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra Which outputs fire on a received bell character
Çıktı LED (GPIO) Pin the LED is wired to
Çıktı LED aktif yüksek Whether the LED pin is active high or low
Çıktı zırnı (GPIO) Pin the buzzer is wired to
Çıktı titreşim (GPIO) Pin the vibration motor is wired to
PWM zırnı kullan Drive the buzzer with PWM, which allows tones rather than a single pitch
I2S’yi zırnı olarak kullan Send the alert through an I2S audio output instead
Çıktı süresi (milisaniye) How long a single alert lasts
Nag zaman aşımı (saniye) Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Zil tipi The tone played on a PWM buzzer, in RTTTL. Can be imported from a file

Store & Forward module

Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.

Setting Açıklaması
Kaydet & Yönlendir etkin Activate store and forward
Kalp atışı Periodically announce this node’s store-and-forward capability
Kayıt sayısı Maximum stored messages
Geçmiş geri dönüş maksimum Max messages to replay
Geçmiş geri dönüş penceresi Time window for replay
Sunucu Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)

💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.

Range Test module

⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.

Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.

Setting Açıklaması
Menzi testi etkin Activate range testing
Gönderen mesaj aralığı (saniye) Time between test transmissions, chosen from a dropdown of fixed intervals
.CSV’yi depolamada kaydet (sadece ESP32) Log received test data to the node’s own filesystem. ESP32 hardware only

Telemetry module

Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).

Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.

Setting Açıklaması
Send Device Telemetry Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval How often to report battery, uptime and channel utilization
Çevre metrikleri modülü etkin Report the attached environment sensors
Environment metrics update interval How often to report them
Çevre metrikleri ekran üzerinde etkin Also show these readings on the device’s own display
Çevre metrikleri Fahrenheit kullan Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Hava kalitesi metrikleri modülü etkin Report particulate and CO₂ sensor data
Air quality metrics update interval How often to report them
Güç metrikleri modülü etkin Report the per-channel voltage and current readings
Power metrics update interval How often to report them
Güç metrikleri ekran üzerinde etkin Also show power readings on the device’s display

See Telemetry & Sensors for supported sensors and configuration recommendations.

Canned Message module

Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.

Setting Açıklaması
Canned message enabled ⚠️ Deprecated in the protobuf schema
Mesajlar Newline-separated list of messages
Zil gönder Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Dönen kodlayıcı #1 etkinleştirildi Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port The three pins the encoder is wired to
Generate input event on Press / CW / CCW Which key event each encoder action produces
Yukarı/Aşağı/Seçme girişi etkinleştirildi A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source ⚠️ Deprecated in the protobuf schema

Audio module

Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.

Setting Açıklaması
CODEC 2 etkinleştirildi Activate audio module
CODEC2 örnekleme hızı Audio quality/bandwidth tradeoff
PTT pini GPIO pin for the push-to-talk button
I2S kelime seçimi GPIO pin for I2S WS
I2S veri girişi GPIO pin for I2S DIN
I2S veri çıkışı GPIO pin for I2S DOUT
I2S saati GPIO pin for the I2S bit clock

ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.

Remote Hardware module

GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.

⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.

Setting Açıklaması
Uzak Donanım etkin Activate remote GPIO access
Tanımlanmamış pin erişimine izin ver Allow access to any GPIO pin (security risk)
Mevcut pinler Up to 4 GPIO pins this node exposes for remote read/write

Neighbor Info module

Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.

Setting Açıklaması
Komşu Bilgisi etkin Activate neighbor broadcasting
Güncelleme aralığı (saniye) How often to broadcast neighbor list
LoRa üzerinden ilet Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name

See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.

Ambient Lighting module

Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.

Setting Açıklaması
LED durumu Turn the LED on or off
Akım LED current limit (0–31)
Red / Green / Blue Individual color channel values (0–255)

Detection Sensor module

Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.

Setting Açıklaması
Algılama Sensörü etkinleştirildi Activate detection sensor
İzlenecek GPIO pini GPIO pin connected to sensor
Algılama tetikleme türü How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
INPUT_PULLUP modu kullan Enable the pin’s internal pull-up resistor
Minimum yayın (saniye) Minimum time between alert broadcasts
Durum yayını (saniye) Periodic state broadcast interval
Uyarı mesajı ile zil gönder Include bell character in alerts
Arkadaşça isim Custom name for this sensor

Paxcounter module

People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.

Setting Açıklaması
Pax sayacı etkin Activate people counting
Güncelleme aralığı (saniye) How often to report counts
Wi-Fi RSSI threshold Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE RSSI threshold The same cut-off for BLE advertisements (defaults to −80 dBm)

💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.

Status Message module

The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.

Mesh Beacon module

Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.

TAK module

Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.

Yönetim

Uzaktan Yönetim

Remotely configure nodes that share your admin key:

  1. Select the target node in the node list.
  2. Navigate to Settings for that node.
  3. Modify configuration.
  4. Tap Save — changes are sent over the mesh.

⚠️ Important: Requires an admin key configured on both your node and the target node.

Device Actions

Settings → Administration holds five one-shot actions, each behind a confirmation dialog:

Action What it does
Set time Sends your phone’s clock to the node
Yeniden başlat Restarts the node
Kapat Powers the node down
Fabrika ayarları Returns every setting to its factory default
NodeDB sıfırla Clears the node database. This dialog carries a Preserve Favorites? switch

⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.

Yedekleme & Geri yükleme

Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.

Gelişmiş

Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.

Clean Node Database

Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.

  • Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
  • Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.

The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.

Hata Ayıklama Paneli

Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.

App Settings

The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:

Privacy

  • Allow analytics and crash reporting — opt in or out of diagnostics.
  • Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
  • Homoglyph encoding — how look-alike characters in names are handled.

Appearance

  • Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
  • Theme and Language.
  • Show full message timestamps.

Persistence

  • A cache limit for how much history is kept.
  • Export rangetest packets, Export all packets and Export node database.

On their own

  • Node Layout — how much detail each row of the node list shows.
  • Wi-Fi Provisioning for mPWRD-OS — see Connections.
  • Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
  • System AI — appears only where app functions are available; see App Functions.

A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.

Hakkında

Settings → About carries the app’s own identity rather than the node’s:

Three sections:

  • What is Meshtastic? — a short description of the project.
  • Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
  • Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.

The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.

Acknowledgements

Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.

Troubleshooting remote admin

  • “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
  • Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
  • Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
+ Settings — Modules & Admin | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Türkçe
Meshtastic Docs ↗

🌐 Türkçe — Community translation View in English

Settings — Modules & Admin

Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.

💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.

Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:

A toggle setting in the on position

A dropdown setting, expanded to show its list of options

A text field setting with a value entered

A module settings card with its title and grouped controls

Modül ayarları

Every module lives under Settings → Module configuration.

⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes.

MQTT module

Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.

Setting Açıklaması
MQTT etkin Toggle MQTT bridge
Adres MQTT broker address
Kullanıcı adı Authentication username
Şifre Authentication password
Şifreleme etkin Encrypt MQTT payloads
JSON çıktısı etkin Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS etkin Use secure connection
Ana konu Base MQTT topic path
Vekilden istemciye etkin Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy on this phone The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT
Harita raporlama Publish position to the public map — see the Map reporting group that follows

Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:

Setting Açıklaması
Katılıyorum. Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered

See MQTT for a detailed usage guide including encryption, privacy, and broker setup.

Serial module

Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.

Setting Açıklaması
Seri etkin Activate serial communication
Eko etkin Echo received serial data back
Seri modu Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX GPIO pins for the serial connection
Seri baud hızı Port speed
Zaman Aşımı How long to wait before considering an incoming message complete
Konsol seri portunu geçersiz kıl Take over the port the debug console normally uses

External Notification module

Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.

There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.

Setting Açıklaması
Harici bildirim etkin Master toggle for the module
Alert message LED / buzzer / vibra Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra Which outputs fire on a received bell character
Çıktı LED (GPIO) Pin the LED is wired to
Çıktı LED aktif yüksek Whether the LED pin is active high or low
Çıktı zırnı (GPIO) Pin the buzzer is wired to
Çıktı titreşim (GPIO) Pin the vibration motor is wired to
PWM zırnı kullan Drive the buzzer with PWM, which allows tones rather than a single pitch
I2S’yi zırnı olarak kullan Send the alert through an I2S audio output instead
GPIO Output Duration How long a single alert lasts
Nag Timeout Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Zil tipi The tone played on a PWM buzzer, in RTTTL. Can be imported from a file

Store & Forward module

Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.

Setting Açıklaması
Kaydet & Yönlendir etkin Activate store and forward
Kalp atışı Periodically announce this node’s store-and-forward capability
Kayıt sayısı Maximum stored messages
Geçmiş geri dönüş maksimum Max messages to replay
Geçmiş geri dönüş penceresi Time window for replay
Sunucu Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)

💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.

Range Test module

⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.

Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.

Setting Açıklaması
Menzi testi etkin Activate range testing
Sender Interval Time between test transmissions, chosen from a dropdown of fixed intervals
.CSV’yi depolamada kaydet (sadece ESP32) Log received test data to the node’s own filesystem. ESP32 hardware only

Telemetry module

Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).

Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.

Setting Açıklaması
Send Device Telemetry Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval How often to report battery, uptime and channel utilization
Çevre metrikleri modülü etkin Report the attached environment sensors
Environment metrics update interval How often to report them
Çevre metrikleri ekran üzerinde etkin Also show these readings on the device’s own display
Çevre metrikleri Fahrenheit kullan Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Hava kalitesi metrikleri modülü etkin Report particulate and CO₂ sensor data
Air quality metrics update interval How often to report them
Güç metrikleri modülü etkin Report the per-channel voltage and current readings
Power metrics update interval How often to report them
Güç metrikleri ekran üzerinde etkin Also show power readings on the device’s display

See Telemetry & Sensors for supported sensors and configuration recommendations.

Canned Message module

Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.

Setting Açıklaması
Canned message enabled ⚠️ Deprecated in the protobuf schema
Mesajlar Newline-separated list of messages
Zil gönder Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Dönen kodlayıcı #1 etkinleştirildi Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port The three pins the encoder is wired to
Generate input event on Press / CW / CCW Which key event each encoder action produces
Yukarı/Aşağı/Seçme girişi etkinleştirildi A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source ⚠️ Deprecated in the protobuf schema

Audio module

Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.

Setting Açıklaması
CODEC 2 etkinleştirildi Activate audio module
CODEC2 örnekleme hızı Audio quality/bandwidth tradeoff
PTT pini GPIO pin for the push-to-talk button
I2S kelime seçimi GPIO pin for I2S WS
I2S veri girişi GPIO pin for I2S DIN
I2S veri çıkışı GPIO pin for I2S DOUT
I2S saati GPIO pin for the I2S bit clock

ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.

Remote Hardware module

GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.

⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.

Setting Açıklaması
Uzak Donanım etkin Activate remote GPIO access
Tanımlanmamış pin erişimine izin ver Allow access to any GPIO pin (security risk)
Mevcut pinler Up to 4 GPIO pins this node exposes for remote read/write

Neighbor Info module

Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.

Setting Açıklaması
Komşu Bilgisi etkin Activate neighbor broadcasting
Update Interval How often to broadcast neighbor list
LoRa üzerinden ilet Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name

See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.

Ambient Lighting module

Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.

Setting Açıklaması
LED durumu Turn the LED on or off
Akım LED current limit (0–31)
Red / Green / Blue Individual color channel values (0–255)

Detection Sensor module

Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.

Setting Açıklaması
Algılama Sensörü etkinleştirildi Activate detection sensor
İzlenecek GPIO pini GPIO pin connected to sensor
Algılama tetikleme türü How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
INPUT_PULLUP modu kullan Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts Minimum time between alert broadcasts
State Broadcast Interval Periodic state broadcast interval
Uyarı mesajı ile zil gönder Include bell character in alerts
Arkadaşça isim Custom name for this sensor

Paxcounter module

People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.

Setting Açıklaması
Pax sayacı etkin Activate people counting
Update Interval How often to report counts
WiFi Threshold (dBm) Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm) The same cut-off for BLE advertisements (defaults to −80 dBm)

💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.

Status Message module

The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.

Mesh Beacon module

Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.

TAK module

Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.

Yönetim

Uzaktan Yönetim

Remotely configure nodes that share your admin key:

  1. Select the target node in the node list.
  2. Navigate to Settings for that node.
  3. Modify configuration.
  4. Tap Save — changes are sent over the mesh.

⚠️ Important: Requires an admin key configured on both your node and the target node.

Device Actions

Settings → Administration holds five one-shot actions, each behind a confirmation dialog:

Action What it does
Set time Sends your phone’s clock to the node
Yeniden başlat Restarts the node
Kapat Powers the node down
Fabrika ayarları Returns every setting to its factory default
NodeDB sıfırla Clears the node database. This dialog carries a Preserve Favorites? switch

⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.

Yedekleme & Geri yükleme

Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.

Gelişmiş

Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.

Clean Node Database

Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.

  • Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
  • Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.

The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.

Hata Ayıklama Paneli

Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.

App Settings

The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:

Privacy

  • Allow analytics and crash reporting — opt in or out of diagnostics.
  • Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
  • Homoglyph encoding — how look-alike characters in names are handled.

Appearance

  • Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
  • Theme and Language.
  • Show full message timestamps.

Persistence

  • A cache limit for how much history is kept.
  • Export rangetest packets, Export all packets and Export node database.

On their own

  • Node Layout — how much detail each row of the node list shows.
  • Wi-Fi Provisioning for mPWRD-OS — see Connections.
  • Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
  • System AI — appears only where app functions are available; see App Functions.

A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.

Hakkında

Settings → About carries the app’s own identity rather than the node’s:

Three sections:

  • What is Meshtastic? — a short description of the project.
  • Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
  • Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.

The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.

Acknowledgements

Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.

Troubleshooting remote admin

  • “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
  • Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
  • Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
diff --git a/main/tr-rTR/user/settings-radio-user.html b/main/tr-rTR/user/settings-radio-user.html index b42c5193ba..b805f35dea 100644 --- a/main/tr-rTR/user/settings-radio-user.html +++ b/main/tr-rTR/user/settings-radio-user.html @@ -1 +1 @@ - Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Türkçe
Meshtastic Docs ↗

🌐 Türkçe — Community translation View in English

Settings — Radio & User

Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How these screens work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Açıklaması
Uzun Ad Your display name (up to 39 characters)
Kısa Ad 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Mesaj gönderilemez Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur node (Ham) Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in.

Yapılandırma

Cihaz Ayarı

On Settings → Device configuration → Device.

Setting Açıklaması Varsayılan
Device Role Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Rebroadcast Mode How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Node Bilgisi Yayın Aralığı How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Double Tap as Button Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Açık
LED Heartbeat Blink the status LED periodically Açık
Time Zone POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it —
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to —

LoRa Ayarı

On Settings → LoRa.

Setting Açıklaması Varsayılan
Bölge Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number Unset (must configure)
Presets Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Transmit Power Transmission power (dBm); 0 = max allowed for region 0 (region max)
Frequency Override Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Use Preset On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead From preset
Coding Rate Manual mode only: 5–8. More redundancy costs airtime From preset
Bant genişliği Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Frequency Slot Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmit Enabled Turning this off makes the node receive-only On
Görev Döngüsünü Geçersiz Kıl Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
MQTT’yi Yoksay Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok to MQTT Allow your packets to be forwarded to MQTT by gateways Off
RX Boosted Gain Extra receive gain on SX126x radios; costs a little current Off
PA fanı devre dışı Turn off the power-amplifier fan on hardware that has one Off

The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set.

Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Speed SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a modem preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Akran Ayarı

On Settings → Device configuration → Display. These control the node’s own screen, not the app’s.

Setting Açıklaması
Screen on for How long the display stays lit before sleeping
Carousel interval How often the node cycles between screens on its own
Görüntü Modu Screen layout/density used by the firmware
Görüntü Birimleri Metric or Imperial on the node’s screen
12h saat formatını kullan Show the node’s clock as 12-hour rather than 24-hour
Bold Heading Draw the screen’s heading text in bold
Ekranı Çevir Rotate the display 180° for an inverted mounting
OLED type Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED
Wake on tap or motion Light the screen when the node is tapped or moved
Pusula yönü Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each
Always point north Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Konum Ayarı

On Settings → Device configuration → Position.

Setting Açıklaması
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the node asks its GPS for a fix
Broadcast Interval How often the position is shared with the mesh
Smart Position Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Fixed Position Use a manually entered latitude, longitude and altitude instead of the GPS
Position Flags A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Güç Ayarı

On Settings → Device configuration → Power.

Setting Açıklaması
Güç tasarrufu modunu etkinleştir Let the node sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the node stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC çarpanını geçersiz kılma oranı The correction factor itself, used only when the override is on
Pilin INA_2XX I2C adresi Address of an external INA-series power sensor, if fitted

Ağ Ayarı

On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node.

Setting Açıklaması
Wi-Fi enabled Enable the Wi-Fi node (ESP32 nodes)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Şifre Ağ şifresi
Ethernet etkin Use a wired connection on hardware that has one
IPv4 modu DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP sunucusu Time synchronization server
rsyslog sunucusu Remote logging server

Network Config with a static IPv4 address entered

Bluetooth Ayarı

On Settings → Device configuration → Bluetooth, on nodes with Bluetooth.

Setting Açıklaması
Bluetooth Etkin Enable/disable BLE radio
Eşleştirme Modu Fixed PIN, Random PIN, or No PIN
Sabit PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Güvenlik Ayarı

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

Setting Açıklaması
Genel Anahtar Your node’s public key (read-only)
Yönetici Anahtarı Keys permitted to administer this node remotely — up to three
Özel Anahtar Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it
Regenerate Private Key Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Seri konsol Serial console over the Stream API
Hata ayıklama kaydı API’si etkin Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth
Yönetilen Mod Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set
Anahtarları Yedekle Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.

+ Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Türkçe
Meshtastic Docs ↗

🌐 Türkçe — Community translation View in English

Settings — Radio & User

Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How these screens work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Açıklaması
Uzun Ad Your display name (up to 39 characters)
Kısa Ad 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Mesaj gönderilemez Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur node (Ham) Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in.

Yapılandırma

Cihaz Ayarı

On Settings → Device configuration → Device.

Setting Açıklaması Varsayılan
Device Role Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Rebroadcast Mode How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Node Bilgisi Yayın Aralığı How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Double Tap as Button Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Açık
LED Heartbeat Blink the status LED periodically Açık
Time Zone POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it —
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to —

LoRa Ayarı

On Settings → LoRa.

Setting Açıklaması Varsayılan
Bölge Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number Unset (must configure)
Presets Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Transmit Power (dBm) Transmission power; 0 = max allowed for region 0 (region max)
Frequency Override Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Use Preset On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead From preset
Coding Rate Manual mode only: 5–8. More redundancy costs airtime From preset
Bant genişliği Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Frequency Slot Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmit Enabled Turning this off makes the node receive-only On
Görev Döngüsünü Geçersiz Kıl Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
MQTT’yi Yoksay Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok to MQTT Allow your packets to be forwarded to MQTT by gateways Off
RX Boosted Gain Extra receive gain on SX126x radios; costs a little current Off
PA fanı devre dışı Turn off the power-amplifier fan on hardware that has one Off

The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set.

Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Speed SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a modem preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Akran Ayarı

On Settings → Device configuration → Display. These control the node’s own screen, not the app’s.

Setting Açıklaması
Screen on for How long the display stays lit before sleeping
Carousel interval How often the node cycles between screens on its own
Görüntü Modu Screen layout/density used by the firmware
Görüntü Birimleri Metric or Imperial on the node’s screen
12h saat formatını kullan Show the node’s clock as 12-hour rather than 24-hour
Bold Heading Draw the screen’s heading text in bold
Ekranı Çevir Rotate the display 180° for an inverted mounting
OLED type Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED
Wake on tap or motion Light the screen when the node is tapped or moved
Pusula yönü Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each
Always point north Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Konum Ayarı

On Settings → Device configuration → Position.

Setting Açıklaması
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the node asks its GPS for a fix
Broadcast Interval How often the position is shared with the mesh
Smart Position Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Fixed Position Use a manually entered latitude, longitude and altitude instead of the GPS
Position Flags A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Güç Ayarı

On Settings → Device configuration → Power.

Setting Açıklaması
Güç tasarrufu modunu etkinleştir Let the node sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the node stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC çarpanını geçersiz kılma oranı The correction factor itself, used only when the override is on
Pilin INA_2XX I2C adresi Address of an external INA-series power sensor, if fitted

Ağ Ayarı

On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node.

Setting Açıklaması
Wi-Fi enabled Enable the Wi-Fi node (ESP32 nodes)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Şifre Ağ şifresi
Ethernet etkin Use a wired connection on hardware that has one
IPv4 modu DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP sunucusu Time synchronization server
rsyslog sunucusu Remote logging server

Network Config with a static IPv4 address entered

Bluetooth Ayarı

On Settings → Device configuration → Bluetooth, on nodes with Bluetooth.

Setting Açıklaması
Bluetooth Etkin Enable/disable BLE radio
Eşleştirme Modu Fixed PIN, Random PIN, or No PIN
Sabit PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Güvenlik Ayarı

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

Setting Açıklaması
Genel Anahtar Your node’s public key (read-only)
Yönetici Anahtarı Keys permitted to administer this node remotely — up to three
Özel Anahtar Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it
Regenerate Private Key Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Seri konsol Serial console over the Stream API
Hata ayıklama kaydı API’si etkin Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth
Yönetilen Mod Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set
Anahtarları Yedekle Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.

diff --git a/main/uk-rUA/user/discovery.html b/main/uk-rUA/user/discovery.html index 26f741ccdc..a7eef2b77d 100644 --- a/main/uk-rUA/user/discovery.html +++ b/main/uk-rUA/user/discovery.html @@ -5,4 +5,4 @@ ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) -

Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:.

What to look for What it means
All hops show Good SNR (green) Healthy path — messages flow reliably
One hop shows a poor SNR (orange or red) Weak link — this relay segment is fragile
Many hops (4+) Long path — consider repositioning a node to shorten it
Different path on retry Mesh is adapting — multiple routes exist (this is good!)

💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network.

Troubleshooting with Traceroute

  • No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key.
  • Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa.
  • Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position.
  • Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric.

Інформація про сусідів

The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh.

Enabling Neighbor Info

  1. Navigate to Settings → Module configuration → Neighbor Info.
  2. Enable the module.
  3. Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
  4. Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air.

Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.

Viewing neighbor data

  • Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors.
  • Each neighbor entry shows the node that was directly heard and its signal quality.
  • Combine neighbor data from multiple nodes to understand the full mesh topology.

ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further.

Node list as a discovery tool

The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively.

Finding new nodes

  • Sort by Last heard to see the most recently active nodes at the top.
  • Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes.

Assessing connectivity

  • Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed.
  • Sort by Distance to find nearby nodes and verify they’re reachable.
  • Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge).

Infrastructure audit

  • Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes.
  • Check their signal quality and last-heard times to verify your infrastructure nodes are healthy.

See Nodes for full details on filtering and sorting options.

Tips for Mesh exploration

  • Start with traceroute — it gives you immediate, actionable information about a specific path.
  • Enable Neighbor Info on key nodes — especially routers and repeaters, to build a picture of the backbone.
  • Check the map — node positions on the Map combined with signal data help you understand why some links are strong and others are weak.
  • Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly.
+

Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:.

What to look for What it means
All hops show Good SNR (green) Healthy path — messages flow reliably
One hop shows a poor SNR (orange or red) Weak link — this relay segment is fragile
Many hops (4+) Long path — consider repositioning a node to shorten it
Different path on retry Mesh is adapting — multiple routes exist (this is good!)

💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network.

Troubleshooting with Traceroute

  • No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key.
  • Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa.
  • Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position.
  • Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric.

Інформація про сусідів

The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh.

Enabling Neighbor Info

  1. Navigate to Settings → Module configuration → Neighbor Info.
  2. Enable the module.
  3. Set Update Interval. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
  4. Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air.

Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.

Viewing neighbor data

  • Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors.
  • Each neighbor entry shows the node that was directly heard and its signal quality.
  • Combine neighbor data from multiple nodes to understand the full mesh topology.

ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further.

Node list as a discovery tool

The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively.

Finding new nodes

  • Sort by Last heard to see the most recently active nodes at the top.
  • Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes.

Assessing connectivity

  • Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed.
  • Sort by Distance to find nearby nodes and verify they’re reachable.
  • Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge).

Infrastructure audit

  • Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes.
  • Check their signal quality and last-heard times to verify your infrastructure nodes are healthy.

See Nodes for full details on filtering and sorting options.

Tips for Mesh exploration

  • Start with traceroute — it gives you immediate, actionable information about a specific path.
  • Enable Neighbor Info on key nodes — especially routers and repeaters, to build a picture of the backbone.
  • Check the map — node positions on the Map combined with signal data help you understand why some links are strong and others are weak.
  • Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly.
diff --git a/main/uk-rUA/user/mqtt.html b/main/uk-rUA/user/mqtt.html index 95bbf01891..e697dd61c3 100644 --- a/main/uk-rUA/user/mqtt.html +++ b/main/uk-rUA/user/mqtt.html @@ -1,2 +1,2 @@ MQTT | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Українська
Meshtastic Docs ↗

🌐 Українська — Community translation View in English

MQTT

MQTT bridges your Meshtastic mesh network to the internet, enabling long-range communication beyond radio range.

Overview

The MQTT module connects your node to an MQTT broker, allowing:

  • Messages to reach nodes on different physical meshes via the internet
  • Integration with home automation and monitoring systems
  • Publishing node positions to the public Meshtastic map
  • Custom data pipelines for logging and alerting

How It Works 

[Your Node] → Radio → [Gateway Node with Wi-Fi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node]
-

A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh.

Налаштування

Enabling MQTT

  1. Navigate to Settings → Module configuration → MQTT.
  2. Enable the MQTT module.
  3. Configure the broker connection:
Setting Опис За замовчуванням
Address MQTT broker hostname mqtt.meshtastic.org
Username Broker authentication meshdev
Password Broker authentication large4cats
Root topic Base topic for messages msh, which the radio rewrites to msh/<REGION> once you set a region
Encryption enabled Encrypt MQTT payload Увімкнено
JSON output enabled Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it Disabled
TLS enabled Secure connection to broker Disabled
Map reporting Report position to public map Disabled
Proxy to client enabled Relay MQTT through the connected phone Disabled

Connection Status and Test Connection

The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here.

Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason.

MQTT Proxy on This Phone

If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection.

ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them.

The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration.

Default Meshtastic Broker

The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing.

When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without).

🔒 Privacy: Messages on the public broker are readable by anyone subscribed. Always use channel encryption for private communications.

Private Broker

For better privacy and control, you can run your own MQTT broker:

  • Mosquitto (lightweight, open-source)
  • HiveMQ
  • EMQX

Configure your node to point to your private broker with appropriate credentials.

Map Reporting

When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.

Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.

Reports appear at meshmap.net and similar community map services.

🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published.

Direction Опис
Uplink Messages from mesh → MQTT broker
Downlink Messages from MQTT broker → mesh

Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on.

Message Formats

MQTT carries two payload formats:

Format Опис Use case
Protobuf Binary Meshtastic protobuf encoding Node-to-node mesh bridging
JSON Human-readable JSON on the /2/json/ topic Consumers outside the mesh (dashboards, home automation)

ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads.

Encryption & Privacy

Understanding the layered encryption model:

  1. Channel encryption happens on the mesh before MQTT. If your channel has a PSK, the MQTT payload is already encrypted — the broker and any subscribers see only the ciphertext.
  2. Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard.
  3. TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping.

🔒 Security: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications.

Best Practices

  • Use channel-level encryption (PSK) on channels that bridge to MQTT
  • Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes memory)
  • Use a private broker for sensitive deployments
  • Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh
  • Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back

Troubleshooting

MQTT Not Connecting

  • Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself.
  • Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces.
  • Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443).
  • DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly.

Messages Not Bridging

  • Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway.
  • Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage.
  • Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root.
  • Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway.
  • Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in.
+

A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh.

Налаштування

Enabling MQTT

  1. Navigate to Settings → Module configuration → MQTT.
  2. Enable the MQTT module.
  3. Configure the broker connection:
Setting Опис За замовчуванням
Address MQTT broker hostname mqtt.meshtastic.org
Username Broker authentication meshdev
Password Broker authentication large4cats
Root topic Base topic for messages msh, which the radio rewrites to msh/<REGION> once you set a region
Encryption enabled Encrypt MQTT payload Увімкнено
JSON output enabled Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it Disabled
TLS enabled Secure connection to broker Disabled
Map reporting Report position to public map Disabled
Proxy to client enabled Relay MQTT through the connected phone Disabled

Connection Status and Test Connection

The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here.

Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason.

MQTT Proxy on This Phone

If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection.

ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them.

The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration.

Default Meshtastic Broker

The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing.

When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without).

🔒 Privacy: Messages on the public broker are readable by anyone subscribed. Always use channel encryption for private communications.

Private Broker

For better privacy and control, you can run your own MQTT broker:

  • Mosquitto (lightweight, open-source)
  • HiveMQ
  • EMQX

Configure your node to point to your private broker with appropriate credentials.

Map Reporting

When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.

Turning it on opens a consent card. Turn on I agree. and choose a Map Publish Interval of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.

Reports appear at meshmap.net and similar community map services.

🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published.

Direction Опис
Uplink Messages from mesh → MQTT broker
Downlink Messages from MQTT broker → mesh

Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on.

Message Formats

MQTT carries two payload formats:

Format Опис Use case
Protobuf Binary Meshtastic protobuf encoding Node-to-node mesh bridging
JSON Human-readable JSON on the /2/json/ topic Consumers outside the mesh (dashboards, home automation)

ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads.

Encryption & Privacy

Understanding the layered encryption model:

  1. Channel encryption happens on the mesh before MQTT. If your channel has a PSK, the MQTT payload is already encrypted — the broker and any subscribers see only the ciphertext.
  2. Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard.
  3. TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping.

🔒 Security: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications.

Best Practices

  • Use channel-level encryption (PSK) on channels that bridge to MQTT
  • Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes memory)
  • Use a private broker for sensitive deployments
  • Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh
  • Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back

Troubleshooting

MQTT Not Connecting

  • Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself.
  • Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces.
  • Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443).
  • DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly.

Messages Not Bridging

  • Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway.
  • Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage.
  • Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root.
  • Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway.
  • Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in.
diff --git a/main/uk-rUA/user/settings-module-admin.html b/main/uk-rUA/user/settings-module-admin.html index a0bf2d9d13..6c0c062b65 100644 --- a/main/uk-rUA/user/settings-module-admin.html +++ b/main/uk-rUA/user/settings-module-admin.html @@ -1 +1 @@ - Settings — Modules & Admin | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Українська
Meshtastic Docs ↗

🌐 Українська — Community translation View in English

Settings — Modules & Admin

Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.

💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.

Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:

A toggle setting in the on position

A dropdown setting, expanded to show its list of options

A text field setting with a value entered

A module settings card with its title and grouped controls

Налаштування модуля

Every module lives under Settings → Module configuration.

⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes.

MQTT module

Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.

Setting Опис
MQTT увімкнений Toggle MQTT bridge
Адреса MQTT broker address
Ім’я користувача Authentication username
Пароль Authentication password
Шифрування увімкнено Encrypt MQTT payloads
Вивід JSON увімкнено Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS увімкнений Use secure connection
Кореневий чат Base MQTT topic path
Проксі для клієнта увімкнуто Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT проксі на цьому телефоні The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT
Відображення на мапі Publish position to the public map — see the Map reporting group that follows

Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:

Setting Опис
Погоджуюся. Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Інтервал звітування на мапі (секунди) How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered

See MQTT for a detailed usage guide including encryption, privacy, and broker setup.

Serial module

Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.

Setting Опис
Послідовний порт увімкнено Activate serial communication
Відлуння активоване Echo received serial data back
Послідовний режим Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX GPIO pins for the serial connection
Швидкість послідовного порту Port speed
Таймаут How long to wait before considering an incoming message complete
Перевизначити послідовний порт Take over the port the debug console normally uses

External Notification module

Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.

There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.

Setting Опис
Зовнішні сповіщення увімкнено Master toggle for the module
Alert message LED / buzzer / vibra Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra Which outputs fire on a received bell character
Вихідний LED (GPIO) Pin the LED is wired to
Активний високий рівень світлодіода Whether the LED pin is active high or low
Вихідний гудок (GPIO) Pin the buzzer is wired to
Вихід вібросигналу (GPIO) Pin the vibration motor is wired to
Використовувати зумер із ШІМ-керуванням Drive the buzzer with PWM, which allows tones rather than a single pitch
Використовувати I2S як гудок Send the alert through an I2S audio output instead
Тривалість виводу (мілісекунд) How long a single alert lasts
Інтервал нагадувань (секунди) Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Мелодія The tone played on a PWM buzzer, in RTTTL. Can be imported from a file

Store & Forward module

Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.

Setting Опис
Збереження та перенаправлення увімкнено Activate store and forward
Пульсація Periodically announce this node’s store-and-forward capability
Кількість записів Maximum stored messages
Максимальний обсяг історії Max messages to replay
Максимальне вікно історії Time window for replay
Сервер Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)

💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.

Range Test module

⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.

Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.

Setting Опис
Тест на відстань увімкнений Activate range testing
Інтервал надсилання повідомлень (секунди) Time between test transmissions, chosen from a dropdown of fixed intervals
Зберегти .CSV у сховищі (лише ESP32) Log received test data to the node’s own filesystem. ESP32 hardware only

Telemetry module

Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).

Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.

Setting Опис
Надсилати телеметрію пристрою Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Інтервал оновлення показників пристрою How often to report battery, uptime and channel utilization
Модуль екологічних показників увімкнено Report the attached environment sensors
Інтервал оновлення екологічних показників How often to report them
Екологічні показники на екрані увімкнено Also show these readings on the device’s own display
Екологічні показники використовують шкалу Фаренгейта Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Модуль показників якості повітря увімкнено Report particulate and CO₂ sensor data
Інтервал оновлення показників якості повітря How often to report them
Модуль показників потужності ввімкнено Report the per-channel voltage and current readings
Інтервал оновлення показників потужності How often to report them
Показники потужності на екрані ввімкнено Also show power readings on the device’s display

See Telemetry & Sensors for supported sensors and configuration recommendations.

Canned Message module

Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.

Setting Опис
Canned message enabled ⚠️ Deprecated in the protobuf schema
Повідомлення Newline-separated list of messages
Надіслати дзвіночок Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Енкодер #1 активований Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port The three pins the encoder is wired to
Generate input event on Press / CW / CCW Which key event each encoder action produces
Увімкнути керування Вгору/Вниз/Вибір A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source ⚠️ Deprecated in the protobuf schema

Audio module

Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.

Setting Опис
CODEC 2 увімкнено Activate audio module
Частота дискретизації CODEC2 Audio quality/bandwidth tradeoff
PTT контакт GPIO pin for the push-to-talk button
Вибір слова I2S GPIO pin for I2S WS
Вибір входу I2S GPIO pin for I2S DIN
Вибір виходу I2S GPIO pin for I2S DOUT
I2S тактування GPIO pin for the I2S bit clock

ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.

Remote Hardware module

GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.

⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.

Setting Опис
Конфігурація віддаленого пристрою активована Activate remote GPIO access
Дозволити доступ до невизначених пінів Allow access to any GPIO pin (security risk)
Доступні піни Up to 4 GPIO pins this node exposes for remote read/write

Neighbor Info module

Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.

Setting Опис
Інформацію про сусідів увімкнено Activate neighbor broadcasting
Інтервал оновлення (секунд) How often to broadcast neighbor list
Передавати через LoRa Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name

See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.

Ambient Lighting module

Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.

Setting Опис
Стан світлодіоду Turn the LED on or off
Поточний LED current limit (0–31)
Red / Green / Blue Individual color channel values (0–255)

Detection Sensor module

Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.

Setting Опис
Датчик виявлення увімкнено Activate detection sensor
GPIO контакт для моніторингу GPIO pin connected to sensor
Тип тригера виявлення How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Використовувати режим INPUT_PULLUP Enable the pin’s internal pull-up resistor
Мінімальний період розсилки (секунди) Minimum time between alert broadcasts
Інтервал трансляції стану (секунди) Periodic state broadcast interval
Надсилати дзвіночок з тривожним повідомленням Include bell character in alerts
Дружня назва Custom name for this sensor

Paxcounter module

People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.

Setting Опис
Лічильник пристроїв активований Activate people counting
Інтервал оновлення (секунд) How often to report counts
Wi-Fi RSSI threshold Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE RSSI threshold The same cut-off for BLE advertisements (defaults to −80 dBm)

💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.

Status Message module

The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.

Mesh Beacon module

Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.

TAK module

Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.

Адміністрування

Віддалене керування

Remotely configure nodes that share your admin key:

  1. Select the target node in the node list.
  2. Navigate to Settings for that node.
  3. Modify configuration.
  4. Tap Save — changes are sent over the mesh.

⚠️ Important: Requires an admin key configured on both your node and the target node.

Device Actions

Settings → Administration holds five one-shot actions, each behind a confirmation dialog:

Action What it does
Встановити час Sends your phone’s clock to the node
Перевантажити Restarts the node
Вимкнути Powers the node down
Скинути до заводських налаштувань Returns every setting to its factory default
Очищення бази вузлів Clears the node database. This dialog carries a Preserve Favorites? switch

⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.

Резервна копія & Відновлення

Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.

Розширені

Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.

Очистити базу даних вузлів

Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.

  • Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
  • Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.

The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.

Панель налагодження

Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.

App Settings

The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:

Privacy

  • Allow analytics and crash reporting — opt in or out of diagnostics.
  • Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
  • Homoglyph encoding — how look-alike characters in names are handled.

Appearance

  • Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
  • Theme and Language.
  • Show full message timestamps.

Persistence

  • A cache limit for how much history is kept.
  • Export rangetest packets, Export all packets and Export node database.

On their own

  • Node Layout — how much detail each row of the node list shows.
  • Wi-Fi Provisioning for mPWRD-OS — see Connections.
  • Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
  • System AI — appears only where app functions are available; see App Functions.

A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.

Про

Settings → About carries the app’s own identity rather than the node’s:

Three sections:

  • What is Meshtastic? — a short description of the project.
  • Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
  • Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.

The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.

Подяки

Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.

Troubleshooting remote admin

  • “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
  • Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
  • Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
+ Settings — Modules & Admin | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Українська
Meshtastic Docs ↗

🌐 Українська — Community translation View in English

Settings — Modules & Admin

Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.

💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.

Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:

A toggle setting in the on position

A dropdown setting, expanded to show its list of options

A text field setting with a value entered

A module settings card with its title and grouped controls

Налаштування модуля

Every module lives under Settings → Module configuration.

⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes.

MQTT module

Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.

Setting Опис
MQTT увімкнений Toggle MQTT bridge
Адреса MQTT broker address
Ім’я користувача Authentication username
Пароль Authentication password
Шифрування увімкнено Encrypt MQTT payloads
Вивід JSON увімкнено Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS увімкнений Use secure connection
Кореневий чат Base MQTT topic path
Проксі для клієнта увімкнуто Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT проксі на цьому телефоні The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT
Відображення на мапі Publish position to the public map — see the Map reporting group that follows

Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:

Setting Опис
Погоджуюся. Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered

See MQTT for a detailed usage guide including encryption, privacy, and broker setup.

Serial module

Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.

Setting Опис
Послідовний порт увімкнено Activate serial communication
Відлуння активоване Echo received serial data back
Послідовний режим Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX GPIO pins for the serial connection
Швидкість послідовного порту Port speed
Таймаут How long to wait before considering an incoming message complete
Перевизначити послідовний порт Take over the port the debug console normally uses

External Notification module

Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.

There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.

Setting Опис
Зовнішні сповіщення увімкнено Master toggle for the module
Alert message LED / buzzer / vibra Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra Which outputs fire on a received bell character
Вихідний LED (GPIO) Pin the LED is wired to
Активний високий рівень світлодіода Whether the LED pin is active high or low
Вихідний гудок (GPIO) Pin the buzzer is wired to
Вихід вібросигналу (GPIO) Pin the vibration motor is wired to
Використовувати зумер із ШІМ-керуванням Drive the buzzer with PWM, which allows tones rather than a single pitch
Використовувати I2S як гудок Send the alert through an I2S audio output instead
GPIO Output Duration How long a single alert lasts
Nag Timeout Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Мелодія The tone played on a PWM buzzer, in RTTTL. Can be imported from a file

Store & Forward module

Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.

Setting Опис
Збереження та перенаправлення увімкнено Activate store and forward
Пульсація Periodically announce this node’s store-and-forward capability
Кількість записів Maximum stored messages
Максимальний обсяг історії Max messages to replay
Максимальне вікно історії Time window for replay
Сервер Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)

💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.

Range Test module

⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.

Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.

Setting Опис
Тест на відстань увімкнений Activate range testing
Sender Interval Time between test transmissions, chosen from a dropdown of fixed intervals
Зберегти .CSV у сховищі (лише ESP32) Log received test data to the node’s own filesystem. ESP32 hardware only

Telemetry module

Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).

Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.

Setting Опис
Надсилати телеметрію пристрою Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Інтервал оновлення показників пристрою How often to report battery, uptime and channel utilization
Модуль екологічних показників увімкнено Report the attached environment sensors
Інтервал оновлення екологічних показників How often to report them
Екологічні показники на екрані увімкнено Also show these readings on the device’s own display
Екологічні показники використовують шкалу Фаренгейта Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Модуль показників якості повітря увімкнено Report particulate and CO₂ sensor data
Інтервал оновлення показників якості повітря How often to report them
Модуль показників потужності ввімкнено Report the per-channel voltage and current readings
Інтервал оновлення показників потужності How often to report them
Показники потужності на екрані ввімкнено Also show power readings on the device’s display

See Telemetry & Sensors for supported sensors and configuration recommendations.

Canned Message module

Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.

Setting Опис
Canned message enabled ⚠️ Deprecated in the protobuf schema
Повідомлення Newline-separated list of messages
Надіслати дзвіночок Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Енкодер #1 активований Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port The three pins the encoder is wired to
Generate input event on Press / CW / CCW Which key event each encoder action produces
Увімкнути керування Вгору/Вниз/Вибір A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source ⚠️ Deprecated in the protobuf schema

Audio module

Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.

Setting Опис
CODEC 2 увімкнено Activate audio module
Частота дискретизації CODEC2 Audio quality/bandwidth tradeoff
PTT контакт GPIO pin for the push-to-talk button
Вибір слова I2S GPIO pin for I2S WS
Вибір входу I2S GPIO pin for I2S DIN
Вибір виходу I2S GPIO pin for I2S DOUT
I2S тактування GPIO pin for the I2S bit clock

ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.

Remote Hardware module

GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.

⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.

Setting Опис
Конфігурація віддаленого пристрою активована Activate remote GPIO access
Дозволити доступ до невизначених пінів Allow access to any GPIO pin (security risk)
Доступні піни Up to 4 GPIO pins this node exposes for remote read/write

Neighbor Info module

Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.

Setting Опис
Інформацію про сусідів увімкнено Activate neighbor broadcasting
Інтервал опитування GPS How often to broadcast neighbor list
Передавати через LoRa Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name

See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.

Ambient Lighting module

Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.

Setting Опис
Стан світлодіоду Turn the LED on or off
Поточний LED current limit (0–31)
Red / Green / Blue Individual color channel values (0–255)

Detection Sensor module

Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.

Setting Опис
Датчик виявлення увімкнено Activate detection sensor
GPIO контакт для моніторингу GPIO pin connected to sensor
Тип тригера виявлення How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Використовувати режим INPUT_PULLUP Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts Minimum time between alert broadcasts
State Broadcast Interval Periodic state broadcast interval
Надсилати дзвіночок з тривожним повідомленням Include bell character in alerts
Дружня назва Custom name for this sensor

Paxcounter module

People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.

Setting Опис
Лічильник пристроїв активований Activate people counting
Інтервал опитування GPS How often to report counts
WiFi Threshold (dBm) Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm) The same cut-off for BLE advertisements (defaults to −80 dBm)

💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.

Status Message module

The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.

Mesh Beacon module

Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.

TAK module

Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.

Адміністрування

Віддалене керування

Remotely configure nodes that share your admin key:

  1. Select the target node in the node list.
  2. Navigate to Settings for that node.
  3. Modify configuration.
  4. Tap Save — changes are sent over the mesh.

⚠️ Important: Requires an admin key configured on both your node and the target node.

Device Actions

Settings → Administration holds five one-shot actions, each behind a confirmation dialog:

Action What it does
Встановити час Sends your phone’s clock to the node
Перевантажити Restarts the node
Вимкнути Powers the node down
Скинути до заводських налаштувань Returns every setting to its factory default
Очищення бази вузлів Clears the node database. This dialog carries a Preserve Favorites? switch

⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.

Резервна копія & Відновлення

Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.

Розширені

Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.

Очистити базу даних вузлів

Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.

  • Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
  • Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.

The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.

Панель налагодження

Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.

App Settings

The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:

Privacy

  • Allow analytics and crash reporting — opt in or out of diagnostics.
  • Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
  • Homoglyph encoding — how look-alike characters in names are handled.

Appearance

  • Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
  • Theme and Language.
  • Show full message timestamps.

Persistence

  • A cache limit for how much history is kept.
  • Export rangetest packets, Export all packets and Export node database.

On their own

  • Node Layout — how much detail each row of the node list shows.
  • Wi-Fi Provisioning for mPWRD-OS — see Connections.
  • Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
  • System AI — appears only where app functions are available; see App Functions.

A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.

Про

Settings → About carries the app’s own identity rather than the node’s:

Three sections:

  • What is Meshtastic? — a short description of the project.
  • Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
  • Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.

The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.

Подяки

Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.

Troubleshooting remote admin

  • “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
  • Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
  • Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
diff --git a/main/uk-rUA/user/settings-radio-user.html b/main/uk-rUA/user/settings-radio-user.html index 06374b99cf..2d58872fed 100644 --- a/main/uk-rUA/user/settings-radio-user.html +++ b/main/uk-rUA/user/settings-radio-user.html @@ -1 +1 @@ - Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Українська
Meshtastic Docs ↗

🌐 Українська — Community translation View in English

Settings — Radio & User

Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How these screens work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Опис
Довга назва Your display name (up to 39 characters)
Коротка назва 4-character abbreviated name
Статус повідомлення A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Недоступний для повідомлень Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur node (Ham) Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in.

Налаштування

Налаштування пристрою

On Settings → Device configuration → Device.

Setting Опис За замовчуванням
Роль пристрою Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Режим ретрансляції How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Інтервал розсилки даних про вузол How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Подвійний дотик як натискання кнопки Treat a double tap as a button press Disabled
Швидка перевірка зв’язку потрійним натисканням Send an ad-hoc position ping on a triple click Увімкнено
Частота мигання світлодіоду Blink the status LED periodically Увімкнено
Часовий пояс POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it —
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to —

Налаштування LoRa

On Settings → LoRa.

Setting Опис За замовчуванням
Регіон Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number Unset (must configure)
Пресети Speed/range tradeoff LongFast
К-ть стрибків Maximum retransmit hops 3
Потужність передачі Transmission power (dBm); 0 = max allowed for region 0 (region max)
Перевизначити частоту Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Використовувати пресет On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Показник розширення сигналу Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead From preset
Швидкість кодування Manual mode only: 5–8. More redundancy costs airtime From preset
Ширина смуги пропускання Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Слот частоти Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Передача активована Turning this off makes the node receive-only On
Ігнорувати обмеження завантаженості каналу Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
Ігнорувати MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
MQTT: Готово Allow your packets to be forwarded to MQTT by gateways Off
Підсилення передачі Extra receive gain on SX126x radios; costs a little current Off
Вентилятор вимкнений Turn off the power-amplifier fan on hardware that has one Off

The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set.

Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Швидкість SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a modem preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Налаштування дисплею

On Settings → Device configuration → Display. These control the node’s own screen, not the app’s.

Setting Опис
Екран включено для How long the display stays lit before sleeping
Інтервал гортання каруселі How often the node cycles between screens on its own
Режим екрану Screen layout/density used by the firmware
Одиниці виміру Metric or Imperial on the node’s screen
Використовувати 12-г формат часу Show the node’s clock as 12-hour rather than 24-hour
Жирні заголовки Draw the screen’s heading text in bold
Перевернути екран Rotate the display 180° for an inverted mounting
Тип OLED Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED
Прокидання дотиком або рухом Light the screen when the node is tapped or moved
Орієнтація компаса Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each
Завжди вказувати на північ Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Position Config

On Settings → Device configuration → Position.

Setting Опис
Режим GPS (Фізичний пристрій) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
Інтервал опитування GPS How often the node asks its GPS for a fix
Інтервал трансляції How often the position is shared with the mesh
Інтелектуальне передавання позиції Broadcast based on movement rather than purely on the clock
Інтелектуальний інтервал With Smart Position on, the shortest gap between broadcasts
Інтелектуальна дистанція With Smart Position on, how far you must move before broadcasting
Фіксована позиція Use a manually entered latitude, longitude and altitude instead of the GPS
Прапорці місцеположення A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Налаштування живлення

On Settings → Device configuration → Power.

Setting Опис
Увімкнути енергоощадний режим Let the node sleep aggressively between activity
Вимкнути при втраті живлення Power the device down after external power disappears
Тривалість глибокого сну How long the deepest sleep state lasts
Мінімальний час в робочому режимі The shortest time the node stays awake once woken
Тривалість очікування Bluetooth How long to wait for a phone to connect before sleeping
Корекція множника напруги Turn on a manual correction for battery-voltage readings
Множник корекції напруги The correction factor itself, used only when the override is on
I2C адреса INA_2XX батареї Address of an external INA-series power sensor, if fitted

Налаштування мережі

On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node.

Setting Опис
Wi-Fi enabled Enable the Wi-Fi node (ESP32 nodes)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Пароль Network password
Ethernet увімкнено Use a wired connection on hardware that has one
Режим IPv4 DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP-сервер Time synchronization server
rsyslog-сервер Remote logging server

Network Config with a static IPv4 address entered

Налаштування Bluetooth

On Settings → Device configuration → Bluetooth, on nodes with Bluetooth.

Setting Опис
Bluetooth увімкнено Enable/disable BLE radio
Режим створення пари Fixed PIN, Random PIN, or No PIN
Фіксований PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Налаштування безпеки

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

Setting Опис
Відкритий ключ Your node’s public key (read-only)
Ключ адміністратора Keys permitted to administer this node remotely — up to three
Приватний ключ Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it
Згенерувати закритий ключ Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Серійна консоль Serial console over the Stream API
API журналу відладки увімкнено Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth
Керований режим Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set
Резервні ключі Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.

+ Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 Українська
Meshtastic Docs ↗

🌐 Українська — Community translation View in English

Settings — Radio & User

Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How these screens work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Опис
Довга назва Your display name (up to 39 characters)
Коротка назва 4-character abbreviated name
Статус повідомлення A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Недоступний для повідомлень Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur node (Ham) Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in.

Налаштування

Налаштування пристрою

On Settings → Device configuration → Device.

Setting Опис За замовчуванням
Роль пристрою Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Режим ретрансляції How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Інтервал розсилки даних про вузол How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Подвійний дотик як натискання кнопки Treat a double tap as a button press Disabled
Швидка перевірка зв’язку потрійним натисканням Send an ad-hoc position ping on a triple click Увімкнено
Частота мигання світлодіоду Blink the status LED periodically Увімкнено
Часовий пояс POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it —
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to —

Налаштування LoRa

On Settings → LoRa.

Setting Опис За замовчуванням
Регіон Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number Unset (must configure)
Пресети Speed/range tradeoff LongFast
К-ть стрибків Maximum retransmit hops 3
Transmit Power (dBm) Transmission power; 0 = max allowed for region 0 (region max)
Перевизначити частоту Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Використовувати пресет On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Показник розширення сигналу Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead From preset
Швидкість кодування Manual mode only: 5–8. More redundancy costs airtime From preset
Ширина смуги пропускання Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Слот частоти Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Передача активована Turning this off makes the node receive-only On
Ігнорувати обмеження завантаженості каналу Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
Ігнорувати MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
MQTT: Готово Allow your packets to be forwarded to MQTT by gateways Off
Підсилення передачі Extra receive gain on SX126x radios; costs a little current Off
Вентилятор вимкнений Turn off the power-amplifier fan on hardware that has one Off

The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set.

Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Швидкість SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a modem preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Налаштування дисплею

On Settings → Device configuration → Display. These control the node’s own screen, not the app’s.

Setting Опис
Екран включено для How long the display stays lit before sleeping
Інтервал гортання каруселі How often the node cycles between screens on its own
Режим екрану Screen layout/density used by the firmware
Одиниці виміру Metric or Imperial on the node’s screen
Використовувати 12-г формат часу Show the node’s clock as 12-hour rather than 24-hour
Жирні заголовки Draw the screen’s heading text in bold
Перевернути екран Rotate the display 180° for an inverted mounting
Тип OLED Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED
Прокидання дотиком або рухом Light the screen when the node is tapped or moved
Орієнтація компаса Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each
Завжди вказувати на північ Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Position Config

On Settings → Device configuration → Position.

Setting Опис
Режим GPS (Фізичний пристрій) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
Інтервал опитування GPS How often the node asks its GPS for a fix
Інтервал трансляції How often the position is shared with the mesh
Інтелектуальне передавання позиції Broadcast based on movement rather than purely on the clock
Інтелектуальний інтервал With Smart Position on, the shortest gap between broadcasts
Інтелектуальна дистанція With Smart Position on, how far you must move before broadcasting
Фіксована позиція Use a manually entered latitude, longitude and altitude instead of the GPS
Прапорці місцеположення A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Налаштування живлення

On Settings → Device configuration → Power.

Setting Опис
Увімкнути енергоощадний режим Let the node sleep aggressively between activity
Вимкнути при втраті живлення Power the device down after external power disappears
Тривалість глибокого сну How long the deepest sleep state lasts
Мінімальний час в робочому режимі The shortest time the node stays awake once woken
Тривалість очікування Bluetooth How long to wait for a phone to connect before sleeping
Корекція множника напруги Turn on a manual correction for battery-voltage readings
Множник корекції напруги The correction factor itself, used only when the override is on
I2C адреса INA_2XX батареї Address of an external INA-series power sensor, if fitted

Налаштування мережі

On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node.

Setting Опис
Wi-Fi enabled Enable the Wi-Fi node (ESP32 nodes)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Пароль Network password
Ethernet увімкнено Use a wired connection on hardware that has one
Режим IPv4 DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP-сервер Time synchronization server
rsyslog-сервер Remote logging server

Network Config with a static IPv4 address entered

Налаштування Bluetooth

On Settings → Device configuration → Bluetooth, on nodes with Bluetooth.

Setting Опис
Bluetooth увімкнено Enable/disable BLE radio
Режим створення пари Fixed PIN, Random PIN, or No PIN
Фіксований PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Налаштування безпеки

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

Setting Опис
Відкритий ключ Your node’s public key (read-only)
Ключ адміністратора Keys permitted to administer this node remotely — up to three
Приватний ключ Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it
Згенерувати закритий ключ Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Серійна консоль Serial console over the Stream API
API журналу відладки увімкнено Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth
Керований режим Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set
Резервні ключі Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.

diff --git a/main/zh-rCN/user/discovery.html b/main/zh-rCN/user/discovery.html index 494cd2a3da..f08cfbd986 100644 --- a/main/zh-rCN/user/discovery.html +++ b/main/zh-rCN/user/discovery.html @@ -5,4 +5,4 @@ ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) -

Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:.

What to look for What it means
All hops show Good SNR (green) Healthy path — messages flow reliably
One hop shows a poor SNR (orange or red) Weak link — this relay segment is fragile
Many hops (4+) Long path — consider repositioning a node to shorten it
Different path on retry Mesh is adapting — multiple routes exist (this is good!)

💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network.

Troubleshooting with Traceroute

  • No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key.
  • Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa.
  • Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position.
  • Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric.

邻居信息

The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh.

Enabling Neighbor Info

  1. Navigate to Settings → Module configuration → Neighbor Info.
  2. Enable the module.
  3. Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
  4. Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air.

Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.

Viewing neighbor data

  • Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors.
  • Each neighbor entry shows the node that was directly heard and its signal quality.
  • Combine neighbor data from multiple nodes to understand the full mesh topology.

ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further.

Node list as a discovery tool

The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively.

Finding new nodes

  • Sort by Last heard to see the most recently active nodes at the top.
  • Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes.

Assessing connectivity

  • Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed.
  • Sort by Distance to find nearby nodes and verify they’re reachable.
  • Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge).

Infrastructure audit

  • Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes.
  • Check their signal quality and last-heard times to verify your infrastructure nodes are healthy.

See Nodes for full details on filtering and sorting options.

Tips for Mesh exploration

  • Start with traceroute — it gives you immediate, actionable information about a specific path.
  • Enable Neighbor Info on key nodes — especially routers and repeaters, to build a picture of the backbone.
  • Check the map — node positions on the Map combined with signal data help you understand why some links are strong and others are weak.
  • Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly.
+

Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:.

What to look for What it means
All hops show Good SNR (green) Healthy path — messages flow reliably
One hop shows a poor SNR (orange or red) Weak link — this relay segment is fragile
Many hops (4+) Long path — consider repositioning a node to shorten it
Different path on retry Mesh is adapting — multiple routes exist (this is good!)

💡 Tip: Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network.

Troubleshooting with Traceroute

  • No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key.
  • Traceroute times out — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in Settings → LoRa.
  • Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position.
  • Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric.

邻居信息

The Neighbor Info module lets each node broadcast a list of the nodes it can directly hear (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh.

Enabling Neighbor Info

  1. Navigate to Settings → Module configuration → Neighbor Info.
  2. Enable the module.
  3. Set Update Interval. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
  4. Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air.

Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.

Viewing neighbor data

  • Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors.
  • Each neighbor entry shows the node that was directly heard and its signal quality.
  • Combine neighbor data from multiple nodes to understand the full mesh topology.

ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further.

Node list as a discovery tool

The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively.

Finding new nodes

  • Sort by Last heard to see the most recently active nodes at the top.
  • Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes.

Assessing connectivity

  • Sort by Hops away to see which nodes are directly reachable (0 hops) versus relayed.
  • Sort by Distance to find nearby nodes and verify they’re reachable.
  • Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge).

Infrastructure audit

  • Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes.
  • Check their signal quality and last-heard times to verify your infrastructure nodes are healthy.

See Nodes for full details on filtering and sorting options.

Tips for Mesh exploration

  • Start with traceroute — it gives you immediate, actionable information about a specific path.
  • Enable Neighbor Info on key nodes — especially routers and repeaters, to build a picture of the backbone.
  • Check the map — node positions on the Map combined with signal data help you understand why some links are strong and others are weak.
  • Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly.
diff --git a/main/zh-rCN/user/mqtt.html b/main/zh-rCN/user/mqtt.html index d20ddfe59f..cbe2f002aa 100644 --- a/main/zh-rCN/user/mqtt.html +++ b/main/zh-rCN/user/mqtt.html @@ -1,2 +1,2 @@ MQTT | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 中文 (简体)
Meshtastic Docs ↗

🌐 中文 (简体) — Community translation View in English

MQTT

MQTT bridges your Meshtastic mesh network to the internet, enabling long-range communication beyond radio range.

总览

The MQTT module connects your node to an MQTT broker, allowing:

  • Messages to reach nodes on different physical meshes via the internet
  • Integration with home automation and monitoring systems
  • Publishing node positions to the public Meshtastic map
  • Custom data pipelines for logging and alerting

How It Works 

[Your Node] → Radio → [Gateway Node with Wi-Fi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node]
-

A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh.

Configuration

Enabling MQTT

  1. Navigate to Settings → Module configuration → MQTT.
  2. Enable the MQTT module.
  3. Configure the broker connection:
Setting 说明 默认
Address MQTT broker hostname mqtt.meshtastic.org
Username Broker authentication meshdev
Password Broker authentication large4cats
Root topic Base topic for messages msh, which the radio rewrites to msh/<REGION> once you set a region
Encryption enabled Encrypt MQTT payload Enabled
JSON output enabled Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it 禁用
TLS enabled Secure connection to broker 禁用
Map reporting Report position to public map 禁用
Proxy to client enabled Relay MQTT through the connected phone 禁用

Connection Status and Test Connection

The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here.

Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason.

MQTT Proxy on This Phone

If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection.

ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them.

The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration.

Default Meshtastic Broker

The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing.

When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without).

🔒 Privacy: Messages on the public broker are readable by anyone subscribed. Always use channel encryption for private communications.

Private Broker

For better privacy and control, you can run your own MQTT broker:

  • Mosquitto (lightweight, open-source)
  • HiveMQ
  • EMQX

Configure your node to point to your private broker with appropriate credentials.

Map Reporting

When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.

Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.

Reports appear at meshmap.net and similar community map services.

🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published.

Direction 说明
Uplink Messages from mesh → MQTT broker
Downlink Messages from MQTT broker → mesh

Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on.

Message Formats

MQTT carries two payload formats:

Format 说明 Use case
Protobuf Binary Meshtastic protobuf encoding Node-to-node mesh bridging
JSON Human-readable JSON on the /2/json/ topic Consumers outside the mesh (dashboards, home automation)

ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads.

Encryption & Privacy

Understanding the layered encryption model:

  1. Channel encryption happens on the mesh before MQTT. If your channel has a PSK, the MQTT payload is already encrypted — the broker and any subscribers see only the ciphertext.
  2. Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard.
  3. TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping.

🔒 Security: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications.

Best Practices

  • Use channel-level encryption (PSK) on channels that bridge to MQTT
  • Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes memory)
  • Use a private broker for sensitive deployments
  • Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh
  • Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back

问题排查

MQTT Not Connecting

  • Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself.
  • Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces.
  • Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443).
  • DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly.

Messages Not Bridging

  • Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway.
  • Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage.
  • Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root.
  • Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway.
  • Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in.
+

A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh.

Configuration

Enabling MQTT

  1. Navigate to Settings → Module configuration → MQTT.
  2. Enable the MQTT module.
  3. Configure the broker connection:
Setting 说明 默认
Address MQTT broker hostname mqtt.meshtastic.org
Username Broker authentication meshdev
Password Broker authentication large4cats
Root topic Base topic for messages msh, which the radio rewrites to msh/<REGION> once you set a region
Encryption enabled Encrypt MQTT payload Enabled
JSON output enabled Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it 禁用
TLS enabled Secure connection to broker 禁用
Map reporting Report position to public map 禁用
Proxy to client enabled Relay MQTT through the connected phone 禁用

Connection Status and Test Connection

The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here.

Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason.

MQTT Proxy on This Phone

If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection.

ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them.

The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration.

Default Meshtastic Broker

The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing.

When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without).

🔒 Privacy: Messages on the public broker are readable by anyone subscribed. Always use channel encryption for private communications.

Private Broker

For better privacy and control, you can run your own MQTT broker:

  • Mosquitto (lightweight, open-source)
  • HiveMQ
  • EMQX

Configure your node to point to your private broker with appropriate credentials.

Map Reporting

When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.

Turning it on opens a consent card. Turn on I agree. and choose a Map Publish Interval of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.

Reports appear at meshmap.net and similar community map services.

🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published.

Direction 说明
Uplink Messages from mesh → MQTT broker
Downlink Messages from MQTT broker → mesh

Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on.

Message Formats

MQTT carries two payload formats:

Format 说明 Use case
Protobuf Binary Meshtastic protobuf encoding Node-to-node mesh bridging
JSON Human-readable JSON on the /2/json/ topic Consumers outside the mesh (dashboards, home automation)

ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads.

Encryption & Privacy

Understanding the layered encryption model:

  1. Channel encryption happens on the mesh before MQTT. If your channel has a PSK, the MQTT payload is already encrypted — the broker and any subscribers see only the ciphertext.
  2. Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard.
  3. TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping.

🔒 Security: The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively unencrypted — anyone can decode them. Always use a custom PSK for private communications.

Best Practices

  • Use channel-level encryption (PSK) on channels that bridge to MQTT
  • Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes memory)
  • Use a private broker for sensitive deployments
  • Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh
  • Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back

问题排查

MQTT Not Connecting

  • Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself.
  • Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces.
  • Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443).
  • DNS resolution — if using a custom broker hostname, verify the node can resolve it. Try the broker’s IP address directly.

Messages Not Bridging

  • Check uplink/downlink settings — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway.
  • Channel mismatch — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage.
  • Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root.
  • Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway.
  • Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in.
diff --git a/main/zh-rCN/user/settings-module-admin.html b/main/zh-rCN/user/settings-module-admin.html index b8f2408ccc..bfbad3d60e 100644 --- a/main/zh-rCN/user/settings-module-admin.html +++ b/main/zh-rCN/user/settings-module-admin.html @@ -1 +1 @@ - Settings — Modules & Admin | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 中文 (简体)
Meshtastic Docs ↗

🌐 中文 (简体) — Community translation View in English

Settings — Modules & Admin

Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.

💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.

Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:

A toggle setting in the on position

A dropdown setting, expanded to show its list of options

A text field setting with a value entered

A module settings card with its title and grouped controls

模块设定

Every module lives under Settings → Module configuration.

⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes.

MQTT module

Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.

Setting 说明
启用MQTT Toggle MQTT bridge
地址 MQTT broker address
用户名称 Authentication username
密码 Authentication password
启用加密 Encrypt MQTT payloads
启用JSON输出 Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
启用TLS Use secure connection
根主题 Base MQTT topic path
启用客户端代理 Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself
在此手机上开启 MQTT 代理 The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT
地图报告 Publish position to the public map — see the Map reporting group that follows

Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:

Setting 说明
我同意。 Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
地图报告间隔 (秒) How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered

See MQTT for a detailed usage guide including encryption, privacy, and broker setup.

Serial module

Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.

Setting 说明
启用串口 Activate serial communication
启用Echo Echo received serial data back
串口模式 Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX GPIO pins for the serial connection
串口波特率 Port speed
超时 How long to wait before considering an incoming message complete
覆盖控制台串口端口 Take over the port the debug console normally uses

External Notification module

Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.

There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.

Setting 说明
启用外部通知 Master toggle for the module
Alert message LED / buzzer / vibra Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra Which outputs fire on a received bell character
输出 LED (GPIO) Pin the LED is wired to
输出 LED 活动高 Whether the LED pin is active high or low
输出震动(GPIO) Pin the buzzer is wired to
输出振动 (GPIO) Pin the vibration motor is wired to
使用 PWM 蜂鸣器 Drive the buzzer with PWM, which allows tones rather than a single pitch
使用 I2S 作为蜂鸣器 Send the alert through an I2S audio output instead
输出持续时间 (毫秒) How long a single alert lasts
屏幕超时(秒) Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
铃声 The tone played on a PWM buzzer, in RTTTL. Can be imported from a file

Store & Forward module

Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.

Setting 说明
启用存储和转发 Activate store and forward
Heartbeat Periodically announce this node’s store-and-forward capability
记录数 Maximum stored messages
历史记录最大返回值 Max messages to replay
历史记录返回窗口 Time window for replay
服务器 Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)

💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.

Range Test module

⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.

Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.

Setting 说明
启用范围测试 Activate range testing
发件人消息间隔(秒) Time between test transmissions, chosen from a dropdown of fixed intervals
保存 CSV 到存储 (仅ESP32) Log received test data to the node’s own filesystem. ESP32 hardware only

Telemetry module

Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).

Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.

Setting 说明
发送设备远程数据 Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
设备计量更新间隔 How often to report battery, uptime and channel utilization
启用环境计量模块 Report the attached environment sensors
环境计量更新间隔 How often to report them
屏幕显示环境指标 Also show these readings on the device’s own display
环境测量值使用华氏度 Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
启用空气质量计量模块 Report particulate and CO₂ sensor data
空气质量计量更新间隔 How often to report them
启用电源计量模块 Report the per-channel voltage and current readings
电量计更新间隔 How often to report them
在屏幕上启用电源指标 Also show power readings on the device’s display

See Telemetry & Sensors for supported sensors and configuration recommendations.

Canned Message module

Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.

Setting 说明
Canned message enabled ⚠️ Deprecated in the protobuf schema
消息 Newline-separated list of messages
发送响铃 Send a bell character alongside the message, so a receiving node’s External Notification module can sound
启用旋转编码器 #1 Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port The three pins the encoder is wired to
Generate input event on Press / CW / CCW Which key event each encoder action produces
启用Up/Down/select 输入 A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source ⚠️ Deprecated in the protobuf schema

Audio module

Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.

Setting 说明
启用CODEC2 Activate audio module
CODEC2 采样率 Audio quality/bandwidth tradeoff
PTT 引脚 GPIO pin for the push-to-talk button
I2S 字选择 GPIO pin for I2S WS
I2S 数据 IN GPIO pin for I2S DIN
I2S 数据 OUT GPIO pin for I2S DOUT
I2S 时钟 GPIO pin for the I2S bit clock

ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.

Remote Hardware module

GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.

⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.

Setting 说明
启用远程硬件 Activate remote GPIO access
允许未定义的引脚访问 Allow access to any GPIO pin (security risk)
可用引脚 Up to 4 GPIO pins this node exposes for remote read/write

Neighbor Info module

Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.

Setting 说明
启用邻居信息 Activate neighbor broadcasting
更新间隔（秒） How often to broadcast neighbor list
通过 LoRa 传输 Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name

See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.

Ambient Lighting module

Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.

Setting 说明
LED 状态 Turn the LED on or off
电流 LED current limit (0–31)
Red / Green / Blue Individual color channel values (0–255)

Detection Sensor module

Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.

Setting 说明
启用检测传感器 Activate detection sensor
显示器的 GPIO 引脚 GPIO pin connected to sensor
检测触发器类型 How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
使用 输入上拉 模式 Enable the pin’s internal pull-up resistor
最小广播时间(秒) Minimum time between alert broadcasts
状态广播(秒) Periodic state broadcast interval
发送带有警报消息的响铃声 Include bell character in alerts
友好名称 Custom name for this sensor

Paxcounter module

People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.

Setting 说明
启用 Paxcount Activate people counting
更新间隔（秒） How often to report counts
Wi-Fi RSSI threshold Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE RSSI threshold The same cut-off for BLE advertisements (defaults to −80 dBm)

💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.

Status Message module

The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.

Mesh Beacon module

Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.

TAK module

Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.

管理员

远程管理

Remotely configure nodes that share your admin key:

  1. Select the target node in the node list.
  2. Navigate to Settings for that node.
  3. Modify configuration.
  4. Tap Save — changes are sent over the mesh.

⚠️ Important: Requires an admin key configured on both your node and the target node.

Device Actions

Settings → Administration holds five one-shot actions, each behind a confirmation dialog:

Action What it does
设置时间 Sends your phone’s clock to the node
重启 Restarts the node
关机 Powers the node down
恢复出厂设置 Returns every setting to its factory default
重置节点数据库 Clears the node database. This dialog carries a Preserve Favorites? switch

⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.

备份与恢复

Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.

高级

Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.

清理节点数据库

Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.

  • Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
  • Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.

The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.

调试面板

Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.

App 设置

The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:

Privacy

  • Allow analytics and crash reporting — opt in or out of diagnostics.
  • Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
  • Homoglyph encoding — how look-alike characters in names are handled.

Appearance

  • Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
  • Theme and Language.
  • Show full message timestamps.

Persistence

  • A cache limit for how much history is kept.
  • Export rangetest packets, Export all packets and Export node database.

On their own

  • Node Layout — how much detail each row of the node list shows.
  • Wi-Fi Provisioning for mPWRD-OS — see Connections.
  • Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
  • System AI — appears only where app functions are available; see App Functions.

A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.

关于

Settings → About carries the app’s own identity rather than the node’s:

Three sections:

  • What is Meshtastic? — a short description of the project.
  • Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
  • Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.

The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.

开源

Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.

Troubleshooting remote admin

  • “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
  • Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
  • Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
+ Settings — Modules & Admin | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 中文 (简体)
Meshtastic Docs ↗

🌐 中文 (简体) — Community translation View in English

Settings — Modules & Admin

Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.

💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.

Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:

A toggle setting in the on position

A dropdown setting, expanded to show its list of options

A text field setting with a value entered

A module settings card with its title and grouped controls

模块设定

Every module lives under Settings → Module configuration.

⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes.

MQTT module

Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.

Setting 说明
启用MQTT Toggle MQTT bridge
地址 MQTT broker address
用户名称 Authentication username
密码 Authentication password
启用加密 Encrypt MQTT payloads
启用JSON输出 Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
启用TLS Use secure connection
根主题 Base MQTT topic path
启用客户端代理 Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself
在此手机上开启 MQTT 代理 The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT
地图报告 Publish position to the public map — see the Map reporting group that follows

Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:

Setting 说明
我同意。 Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
地图发布间隔 How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered

See MQTT for a detailed usage guide including encryption, privacy, and broker setup.

Serial module

Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.

Setting 说明
启用串口 Activate serial communication
启用Echo Echo received serial data back
串口模式 Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX GPIO pins for the serial connection
串口波特率 Port speed
超时 How long to wait before considering an incoming message complete
覆盖控制台串口端口 Take over the port the debug console normally uses

External Notification module

Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.

There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.

Setting 说明
启用外部通知 Master toggle for the module
Alert message LED / buzzer / vibra Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra Which outputs fire on a received bell character
输出 LED (GPIO) Pin the LED is wired to
输出 LED 活动高 Whether the LED pin is active high or low
输出震动(GPIO) Pin the buzzer is wired to
输出振动 (GPIO) Pin the vibration motor is wired to
使用 PWM 蜂鸣器 Drive the buzzer with PWM, which allows tones rather than a single pitch
使用 I2S 作为蜂鸣器 Send the alert through an I2S audio output instead
GPIO Output Duration How long a single alert lasts
超时提醒 Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
铃声 The tone played on a PWM buzzer, in RTTTL. Can be imported from a file

Store & Forward module

Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.

Setting 说明
启用存储和转发 Activate store and forward
Heartbeat Periodically announce this node’s store-and-forward capability
记录数 Maximum stored messages
历史记录最大返回值 Max messages to replay
历史记录返回窗口 Time window for replay
服务器 Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)

💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.

Range Test module

⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.

Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.

Setting 说明
启用范围测试 Activate range testing
发送间隔 Time between test transmissions, chosen from a dropdown of fixed intervals
保存 CSV 到存储 (仅ESP32) Log received test data to the node’s own filesystem. ESP32 hardware only

Telemetry module

Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).

Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.

Setting 说明
发送设备远程数据 Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
设备计量更新间隔 How often to report battery, uptime and channel utilization
启用环境计量模块 Report the attached environment sensors
环境计量更新间隔 How often to report them
屏幕显示环境指标 Also show these readings on the device’s own display
环境测量值使用华氏度 Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
启用空气质量计量模块 Report particulate and CO₂ sensor data
空气质量计量更新间隔 How often to report them
启用电源计量模块 Report the per-channel voltage and current readings
电量计更新间隔 How often to report them
在屏幕上启用电源指标 Also show power readings on the device’s display

See Telemetry & Sensors for supported sensors and configuration recommendations.

Canned Message module

Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.

Setting 说明
Canned message enabled ⚠️ Deprecated in the protobuf schema
消息 Newline-separated list of messages
发送响铃 Send a bell character alongside the message, so a receiving node’s External Notification module can sound
启用旋转编码器 #1 Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port The three pins the encoder is wired to
Generate input event on Press / CW / CCW Which key event each encoder action produces
启用Up/Down/select 输入 A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source ⚠️ Deprecated in the protobuf schema

Audio module

Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.

Setting 说明
启用CODEC2 Activate audio module
CODEC2 采样率 Audio quality/bandwidth tradeoff
PTT 引脚 GPIO pin for the push-to-talk button
I2S 字选择 GPIO pin for I2S WS
I2S 数据 IN GPIO pin for I2S DIN
I2S 数据 OUT GPIO pin for I2S DOUT
I2S 时钟 GPIO pin for the I2S bit clock

ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.

Remote Hardware module

GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.

⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.

Setting 说明
启用远程硬件 Activate remote GPIO access
允许未定义的引脚访问 Allow access to any GPIO pin (security risk)
可用引脚 Up to 4 GPIO pins this node exposes for remote read/write

Neighbor Info module

Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.

Setting 说明
启用邻居信息 Activate neighbor broadcasting
GPS 轮询间隔 How often to broadcast neighbor list
通过 LoRa 传输 Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name

See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.

Ambient Lighting module

Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.

Setting 说明
LED 状态 Turn the LED on or off
电流 LED current limit (0–31)
Red / Green / Blue Individual color channel values (0–255)

Detection Sensor module

Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.

Setting 说明
启用检测传感器 Activate detection sensor
显示器的 GPIO 引脚 GPIO pin connected to sensor
检测触发器类型 How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
使用 输入上拉 模式 Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts Minimum time between alert broadcasts
State Broadcast Interval Periodic state broadcast interval
发送带有警报消息的响铃声 Include bell character in alerts
友好名称 Custom name for this sensor

Paxcounter module

People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.

Setting 说明
启用 Paxcount Activate people counting
GPS 轮询间隔 How often to report counts
WiFi Threshold (dBm) Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm) The same cut-off for BLE advertisements (defaults to −80 dBm)

💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.

Status Message module

The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.

Mesh Beacon module

Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.

TAK module

Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.

管理员

远程管理

Remotely configure nodes that share your admin key:

  1. Select the target node in the node list.
  2. Navigate to Settings for that node.
  3. Modify configuration.
  4. Tap Save — changes are sent over the mesh.

⚠️ Important: Requires an admin key configured on both your node and the target node.

Device Actions

Settings → Administration holds five one-shot actions, each behind a confirmation dialog:

Action What it does
设置时间 Sends your phone’s clock to the node
重启 Restarts the node
关机 Powers the node down
恢复出厂设置 Returns every setting to its factory default
重置节点数据库 Clears the node database. This dialog carries a Preserve Favorites? switch

⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.

备份与恢复

Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.

高级

Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.

清理节点数据库

Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.

  • Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
  • Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.

The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.

调试面板

Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.

App 设置

The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:

Privacy

  • Allow analytics and crash reporting — opt in or out of diagnostics.
  • Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
  • Homoglyph encoding — how look-alike characters in names are handled.

Appearance

  • Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
  • Theme and Language.
  • Show full message timestamps.

Persistence

  • A cache limit for how much history is kept.
  • Export rangetest packets, Export all packets and Export node database.

On their own

  • Node Layout — how much detail each row of the node list shows.
  • Wi-Fi Provisioning for mPWRD-OS — see Connections.
  • Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
  • System AI — appears only where app functions are available; see App Functions.

A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.

关于

Settings → About carries the app’s own identity rather than the node’s:

Three sections:

  • What is Meshtastic? — a short description of the project.
  • Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
  • Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.

The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.

开源

Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.

Troubleshooting remote admin

  • “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
  • Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
  • Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
diff --git a/main/zh-rCN/user/settings-radio-user.html b/main/zh-rCN/user/settings-radio-user.html index 3079252b2e..63418235b1 100644 --- a/main/zh-rCN/user/settings-radio-user.html +++ b/main/zh-rCN/user/settings-radio-user.html @@ -1 +1 @@ - Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 中文 (简体)
Meshtastic Docs ↗

🌐 中文 (简体) — Community translation View in English

Settings — Radio & User

Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How these screens work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

用户设置

User Profile

On Settings → User.

Setting 说明
长名称 Your display name (up to 39 characters)
短名称 4-character abbreviated name
状态消息 A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
无法发送消息 Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur node (Ham) Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in.

Configuration

设备配置

On Settings → Device configuration → Device.

Setting 说明 默认
设备角色 Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
转播模式 How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
节点信息广播间隔 How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
双击作为按钮 Treat a double tap as a button press 禁用
快速按3下 向所有节点发送紧急广播 Send an ad-hoc position ping on a triple click Enabled
LED 心跳 Blink the status LED periodically Enabled
时区 POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it —
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to —

LoRa 配置

On Settings → LoRa.

Setting 说明 默认
区域 Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number Unset (must configure)
预设 Speed/range tradeoff LongFast
节点数 Maximum retransmit hops 3
发送强度 Transmission power (dBm); 0 = max allowed for region 0 (region max)
频率覆盖 Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
使用预设 On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
扩散因子 Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead From preset
编码率 Manual mode only: 5–8. More redundancy costs airtime From preset
带宽 Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one From preset
频率时隙 Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
启用传输 Turning this off makes the node receive-only On
覆盖占空比 Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits 关闭
忽略 MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
使用MQTT Allow your packets to be forwarded to MQTT by gateways 关闭
RX 增益 Extra receive gain on SX126x radios; costs a little current 关闭
PA风扇已禁用 Turn off the power-amplifier fan on hardware that has one 关闭

The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set.

Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range 速度 SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a modem preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

屏幕配置

On Settings → Device configuration → Display. These control the node’s own screen, not the app’s.

Setting 说明
开启屏幕 How long the display stays lit before sleeping
轮播间隔 How often the node cycles between screens on its own
显示模式 Screen layout/density used by the firmware
显示单位 Metric or Imperial on the node’s screen
使用 12 小时制格式 Show the node’s clock as 12-hour rather than 24-hour
加粗标题 Draw the screen’s heading text in bold
翻转屏幕 Rotate the display 180° for an inverted mounting
OLED 类型 Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED
点击或移动时唤醒屏幕 Light the screen when the node is tapped or moved
罗盘方向 Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each
总是朝北 Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

定位配置

On Settings → Device configuration → Position.

Setting 说明
GPS 模式 (物理硬件) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS 轮询间隔 How often the node asks its GPS for a fix
广播间隔 How often the position is shared with the mesh
智能位置 Broadcast based on movement rather than purely on the clock
自动时间间隔 With Smart Position on, the shortest gap between broadcasts
自动距离大小 With Smart Position on, how far you must move before broadcasting
固定位置 Use a manually entered latitude, longitude and altitude instead of the GPS
位置信息数据包 A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

电源配置

On Settings → Device configuration → Power.

Setting 说明
启用节能模式 Let the node sleep aggressively between activity
断电时关机 Power the device down after external power disappears
深度睡眠时间 How long the deepest sleep state lasts
最小唤醒时间 The shortest time the node stays awake once woken
等待蓝牙持续时间 How long to wait for a phone to connect before sleeping
ADC 倍数覆盖 Turn on a manual correction for battery-voltage readings
ADC乘数修正比率 The correction factor itself, used only when the override is on
电池INA_2XX I2C 地址 Address of an external INA-series power sensor, if fitted

网络配置

On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node.

Setting 说明
Wi-Fi enabled Enable the Wi-Fi node (ESP32 nodes)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
密码 网络密码
启用以太网 Use a wired connection on hardware that has one
IPv4模式 DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP 广播 Share mesh traffic with other nodes over the local network
NTP 服务器 Time synchronization server
rsyslog 服务器 Remote logging server

Network Config with a static IPv4 address entered

蓝牙配置

On Settings → Device configuration → Bluetooth, on nodes with Bluetooth.

Setting 说明
启用蓝牙 Enable/disable BLE radio
配对模式 Fixed PIN, Random PIN, or No PIN
固定PIN码 PIN code for pairing. Must be exactly six digits — the field rejects anything else

安全配置

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

Setting 说明
公钥 Your node’s public key (read-only)
管理员密钥 Keys permitted to administer this node remotely — up to three
私钥 Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it
重新生成私钥 Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
串口控制 Serial console over the Stream API
启用调试日志 API Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth
管理模式 Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set
备份密钥 Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
恢复密钥 Write the backed-up keys back to the node (available once a backup exists)
删除密钥备份 Remove the stored key backup from this phone
安全等级 How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
剩余启动次数 How many device boots the unlocked state survives
距离失效还有多少小时 Wall-clock lifetime of the unlocked state
会话上限 (分钟) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.

+ Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 中文 (简体)
Meshtastic Docs ↗

🌐 中文 (简体) — Community translation View in English

Settings — Radio & User

Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How these screens work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

用户设置

User Profile

On Settings → User.

Setting 说明
长名称 Your display name (up to 39 characters)
短名称 4-character abbreviated name
状态消息 A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
无法发送消息 Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur node (Ham) Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in.

Configuration

设备配置

On Settings → Device configuration → Device.

Setting 说明 默认
设备角色 Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
转播模式 How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
节点信息广播间隔 How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
双击作为按钮 Treat a double tap as a button press 禁用
快速按3下 向所有节点发送紧急广播 Send an ad-hoc position ping on a triple click Enabled
LED 心跳 Blink the status LED periodically Enabled
时区 POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it —
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to —

LoRa 配置

On Settings → LoRa.

Setting 说明 默认
区域 Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number Unset (must configure)
预设 Speed/range tradeoff LongFast
节点数 Maximum retransmit hops 3
Transmit Power (dBm) Transmission power; 0 = max allowed for region 0 (region max)
频率覆盖 Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
使用预设 On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
扩散因子 Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead From preset
编码率 Manual mode only: 5–8. More redundancy costs airtime From preset
带宽 Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one From preset
频率时隙 Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
启用传输 Turning this off makes the node receive-only On
覆盖占空比 Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits 关闭
忽略 MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
使用MQTT Allow your packets to be forwarded to MQTT by gateways 关闭
RX 增益 Extra receive gain on SX126x radios; costs a little current 关闭
PA风扇已禁用 Turn off the power-amplifier fan on hardware that has one 关闭

The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set.

Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range 速度 SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a modem preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

屏幕配置

On Settings → Device configuration → Display. These control the node’s own screen, not the app’s.

Setting 说明
开启屏幕 How long the display stays lit before sleeping
轮播间隔 How often the node cycles between screens on its own
显示模式 Screen layout/density used by the firmware
显示单位 Metric or Imperial on the node’s screen
使用 12 小时制格式 Show the node’s clock as 12-hour rather than 24-hour
加粗标题 Draw the screen’s heading text in bold
翻转屏幕 Rotate the display 180° for an inverted mounting
OLED 类型 Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED
点击或移动时唤醒屏幕 Light the screen when the node is tapped or moved
罗盘方向 Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each
总是朝北 Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

定位配置

On Settings → Device configuration → Position.

Setting 说明
GPS 模式 (物理硬件) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS 轮询间隔 How often the node asks its GPS for a fix
广播间隔 How often the position is shared with the mesh
智能位置 Broadcast based on movement rather than purely on the clock
自动时间间隔 With Smart Position on, the shortest gap between broadcasts
自动距离大小 With Smart Position on, how far you must move before broadcasting
固定位置 Use a manually entered latitude, longitude and altitude instead of the GPS
位置信息数据包 A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

电源配置

On Settings → Device configuration → Power.

Setting 说明
启用节能模式 Let the node sleep aggressively between activity
断电时关机 Power the device down after external power disappears
深度睡眠时间 How long the deepest sleep state lasts
最小唤醒时间 The shortest time the node stays awake once woken
等待蓝牙持续时间 How long to wait for a phone to connect before sleeping
ADC 倍数覆盖 Turn on a manual correction for battery-voltage readings
ADC乘数修正比率 The correction factor itself, used only when the override is on
电池INA_2XX I2C 地址 Address of an external INA-series power sensor, if fitted

网络配置

On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node.

Setting 说明
Wi-Fi enabled Enable the Wi-Fi node (ESP32 nodes)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
密码 网络密码
启用以太网 Use a wired connection on hardware that has one
IPv4模式 DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP 广播 Share mesh traffic with other nodes over the local network
NTP 服务器 Time synchronization server
rsyslog 服务器 Remote logging server

Network Config with a static IPv4 address entered

蓝牙配置

On Settings → Device configuration → Bluetooth, on nodes with Bluetooth.

Setting 说明
启用蓝牙 Enable/disable BLE radio
配对模式 Fixed PIN, Random PIN, or No PIN
固定PIN码 PIN code for pairing. Must be exactly six digits — the field rejects anything else

安全配置

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

Setting 说明
公钥 Your node’s public key (read-only)
管理员密钥 Keys permitted to administer this node remotely — up to three
私钥 Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it
重新生成私钥 Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
串口控制 Serial console over the Stream API
启用调试日志 API Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth
管理模式 Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set
备份密钥 Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
恢复密钥 Write the backed-up keys back to the node (available once a backup exists)
删除密钥备份 Remove the stored key backup from this phone
安全等级 How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
剩余启动次数 How many device boots the unlocked state survives
距离失效还有多少小时 Wall-clock lifetime of the unlocked state
会话上限 (分钟) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.

diff --git a/main/zh-rTW/user/discovery.html b/main/zh-rTW/user/discovery.html index b327bec2fa..b256c4b432 100644 --- a/main/zh-rTW/user/discovery.html +++ b/main/zh-rTW/user/discovery.html @@ -5,4 +5,4 @@ ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) -

Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:.

判讀重點 代表意義
All hops show Good SNR (green) 路徑狀況良好 — 訊息可穩定傳送
One hop shows a poor SNR (orange or red) 訊號薄弱 — 此中繼路段不穩定
跳躍點過多（4 個以上） 路徑過長 — 建議調整節點位置以縮短路徑
重試時走不同路徑 Mesh 網路正在自動調整 — 存在多條路由（這是好現象！）

💡 提示：請在幾分鐘內多次執行路由追蹤。若路徑發生變化，代表您的 mesh 網路具備備援路由 — 這是網路連線良好的象徵。

使用路由追蹤進行疑難排解

  • No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. 請確認兩個節點至少共用一個使用相同加密金鑰的頻道。
  • 「路由追蹤逾時」— 路徑可能過長（超過跳躍限制），或某中繼節點發生壅塞。 Try increasing the hop limit in Settings → LoRa.
  • Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position.
  • 非對稱路徑 — 從 A → B 的路由追蹤路徑，可能與 B → A 不同。 This is normal — radio propagation isn’t always symmetric.

鄰近節點資訊

鄰近節點資訊模組可讓每個節點廣播其可直接收到訊號的節點清單（單跳躍）。當多個節點共享各自的鄰近節點清單時，您便可拼湊出整個 mesh 網路的拓撲圖。

啟用鄰近節點資訊

  1. Navigate to Settings → Module configuration → Neighbor Info.
  2. 啟用此模組。
  3. Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
  4. Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air.

Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. 其他已啟用鄰近節點資訊的節點也會執行相同動作。

Viewing neighbor data

  • Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors.
  • 每筆鄰近節點記錄會顯示可直接收到訊號的節點及其訊號品質。
  • 結合多個節點的鄰近節點資料，以了解完整的 mesh 網路拓撲。

ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further.

Node list as a discovery tool

善用節點清單的篩選與排序功能，即可將其作為強大的探索工具。

Finding new nodes

  • 依「最後收到訊號」排序，可將最近有活動的節點顯示於頂部。
  • Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes.

Assessing connectivity

  • 依「跳躍距離」排序，可區分可直接到達的節點（0 個跳躍點）與需中繼轉送的節點。
  • 依「距離」排序，可找出附近的節點並確認是否可到達。
  • Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge).

Infrastructure audit

  • Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes.
  • 檢查其訊號品質與最後收到訊號的時間，以確認基礎架構節點運作正常。

請參閱〔節點〕(nodes) 以了解完整的篩選與排序選項說明。

Tips for Mesh exploration

  • 從路由追蹤開始 — 可立即取得特定路徑的具體可行資訊。
  • 在關鍵節點上啟用鄰近節點資訊 — 尤其是路由器與中繼器，以建立骨幹網路的整體概況。
  • 查看地圖 —〔地圖〕(map-and-waypoints) 上的節點位置結合訊號資料，有助於了解為何某些連結訊號強，而其他連結訊號弱。
  • 比較訊號變化趨勢 — 請參閱〔訊號儀表〕(signal-meter) 指南，以正確解讀 SNR 與 RSSI 數值。

相關主題

+

Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:.

判讀重點 代表意義
All hops show Good SNR (green) 路徑狀況良好 — 訊息可穩定傳送
One hop shows a poor SNR (orange or red) 訊號薄弱 — 此中繼路段不穩定
跳躍點過多（4 個以上） 路徑過長 — 建議調整節點位置以縮短路徑
重試時走不同路徑 Mesh 網路正在自動調整 — 存在多條路由（這是好現象！）

💡 提示：請在幾分鐘內多次執行路由追蹤。若路徑發生變化，代表您的 mesh 網路具備備援路由 — 這是網路連線良好的象徵。

使用路由追蹤進行疑難排解

  • No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. 請確認兩個節點至少共用一個使用相同加密金鑰的頻道。
  • 「路由追蹤逾時」— 路徑可能過長（超過跳躍限制），或某中繼節點發生壅塞。 Try increasing the hop limit in Settings → LoRa.
  • Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position.
  • 非對稱路徑 — 從 A → B 的路由追蹤路徑，可能與 B → A 不同。 This is normal — radio propagation isn’t always symmetric.

鄰近節點資訊

鄰近節點資訊模組可讓每個節點廣播其可直接收到訊號的節點清單（單跳躍）。當多個節點共享各自的鄰近節點清單時，您便可拼湊出整個 mesh 網路的拓撲圖。

啟用鄰近節點資訊

  1. Navigate to Settings → Module configuration → Neighbor Info.
  2. 啟用此模組。
  3. Set Update Interval. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
  4. Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air.

Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. 其他已啟用鄰近節點資訊的節點也會執行相同動作。

Viewing neighbor data

  • Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors.
  • 每筆鄰近節點記錄會顯示可直接收到訊號的節點及其訊號品質。
  • 結合多個節點的鄰近節點資料，以了解完整的 mesh 網路拓撲。

ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further.

Node list as a discovery tool

善用節點清單的篩選與排序功能，即可將其作為強大的探索工具。

Finding new nodes

  • 依「最後收到訊號」排序，可將最近有活動的節點顯示於頂部。
  • Enable Include unknown to see nodes that have appeared on the mesh but haven’t sent user info yet — these are often newly powered-on nodes.

Assessing connectivity

  • 依「跳躍距離」排序，可區分可直接到達的節點（0 個跳躍點）與需中繼轉送的節點。
  • 依「距離」排序，可找出附近的節點並確認是否可到達。
  • Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge).

Infrastructure audit

  • Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes.
  • 檢查其訊號品質與最後收到訊號的時間，以確認基礎架構節點運作正常。

請參閱〔節點〕(nodes) 以了解完整的篩選與排序選項說明。

Tips for Mesh exploration

  • 從路由追蹤開始 — 可立即取得特定路徑的具體可行資訊。
  • 在關鍵節點上啟用鄰近節點資訊 — 尤其是路由器與中繼器，以建立骨幹網路的整體概況。
  • 查看地圖 —〔地圖〕(map-and-waypoints) 上的節點位置結合訊號資料，有助於了解為何某些連結訊號強，而其他連結訊號弱。
  • 比較訊號變化趨勢 — 請參閱〔訊號儀表〕(signal-meter) 指南，以正確解讀 SNR 與 RSSI 數值。

相關主題

diff --git a/main/zh-rTW/user/mqtt.html b/main/zh-rTW/user/mqtt.html index 79a6cae8cf..c15a5db901 100644 --- a/main/zh-rTW/user/mqtt.html +++ b/main/zh-rTW/user/mqtt.html @@ -1,2 +1,2 @@ MQTT | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 中文 (繁體)
Meshtastic Docs ↗

🌐 中文 (繁體) — Community translation View in English

MQTT

MQTT 將您的 Meshtastic mesh 網路橋接至網際網路，實現超越無線電範圍的長距離通訊。

概觀

MQTT 模組可將您的節點連接至 MQTT 代理伺服器，實現以下功能：

  • 透過網際網路傳送訊息至不同實體 mesh 網路上的節點
  • 與智慧家庭自動化及監控系統整合
  • 將節點位置發布至公開的 Meshtastic 地圖
  • 自訂資料管線，用於記錄與警示通知

運作方式 

[Your Node] → Radio → [Gateway Node with Wi-Fi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node]
-

A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. 訂閱相同主題的遠端閘道，將這些訊息注入其本地 mesh 網路。

設定

啟用 MQTT

  1. Navigate to Settings → Module configuration → MQTT.
  2. 啟用 MQTT 模組。
  3. 設定代理伺服器連線：
設定 描述說明 默認
Address MQTT 代理伺服器主機名稱 mqtt.meshtastic.org
Username 代理伺服器驗證 meshdev
Password 代理伺服器驗證 large4cats
Root topic 訊息的基礎主題 msh, which the radio rewrites to msh/<REGION> once you set a region
Encryption enabled 加密 MQTT 承載內容 已啟用
JSON output enabled Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it 已停用
TLS enabled 與代理伺服器的安全連線 已停用
Map reporting 將位置回報至公開地圖 已停用
Proxy to client enabled Relay MQTT through the connected phone 已停用

Connection Status and Test Connection

The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here.

Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason.

MQTT Proxy on This Phone

If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection.

ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them.

The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration.

預設 Meshtastic 代理伺服器

社群在 mqtt.meshtastic.org 維護一個公開的代理伺服器。此伺服器供一般使用與測試之用。

When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without).

🔒 隱私：公開代理伺服器上的訊息，任何訂閱者均可讀取。私人通訊請務必啟用頻道加密。

私有代理伺服器

為了獲得更好的隱私保護與控制權，您可以自行架設 MQTT 代理伺服器：

  • Mosquitto（輕量、開放原始碼）
  • HiveMQ
  • EMQX

請將您的節點設定為指向私有代理伺服器，並輸入相應的登入憑證。

地圖回報

When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.

Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.

Reports appear at meshmap.net and similar community map services.

🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published.

上行 vs 下行

方向 描述說明
上行 訊息從 mesh 網路 → MQTT 代理伺服器
下行 訊息從 MQTT 代理伺服器 → mesh 網路

Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on.

訊息格式

MQTT carries two payload formats:

格式 描述說明 使用情境
Protobuf 二進位 Meshtastic protobuf 編碼 節點間 mesh 橋接
JSON Human-readable JSON on the /2/json/ topic Consumers outside the mesh (dashboards, home automation)

ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads.

加密與隱私

了解分層加密模型：

  1. 頻道加密在 mesh 網路上進行，發生於 MQTT 傳輸之前。若您的頻道已設定 PSK，MQTT 承載內容將已加密——代理伺服器及任何訂閱者只能看到密文。
  2. Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard.
  3. TLS 對連接至代理伺服器的 TCP 連線進行加密，防止網路層級的竊聽。

🔒 Security: The default public channel has a well-known key. 透過 MQTT 傳送的預設頻道訊息實際上等同於未加密 — 任何人均可解碼。私人通訊請務必使用自訂 PSK。

最佳實踐

  • 在橋接至 MQTT 的頻道上使用頻道層級加密（PSK）
  • Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes memory)
  • 敏感部署環境請使用私有代理伺服器
  • 從繁忙的 MQTT 主題下行訊息時，請留意無線電佔用時間——每則下行訊息都會消耗本地 mesh 網路的無線電佔用時間
  • 若僅需遠端監控 mesh 網路而不需注入訊息，建議僅啟用上行模式

故障排除

MQTT 無法連線

  • Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT 無法直接透過 LoRa 無線電連結運作。
  • Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces.
  • Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443).
  • DNS 解析 — 若使用自訂代理伺服器主機名稱，請確認節點能夠正確解析該名稱。請嘗試直接使用代理伺服器的 IP 位址進行連線。

訊息未正常橋接

  • 檢查上行／下行設定 — 若僅啟用上行，訊息只會從 mesh 網路流向 MQTT，不會反向傳送。請在接收端閘道上啟用下行功能。
  • 頻道不符 — 兩個閘道必須使用相同頻道且具備相同的 PSK。不符時，訊息將以不同金鑰加密，導致對方收到的內容為亂碼。
  • Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root.
  • Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway.
  • Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in.

相關主題

  • 〔設定 — 模組與管理〕(settings-module-admin) — MQTT 模組設定參考
  • 〔訊息與頻道〕(messages-and-channels) — 頻道加密與 PSK 設定
  • 〔MQTT 整合指南〕(https://meshtastic.org/docs/software/integrations/mqtt) — meshtastic.org 上的完整 MQTT 說明文件
+

A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. 訂閱相同主題的遠端閘道，將這些訊息注入其本地 mesh 網路。

設定

啟用 MQTT

  1. Navigate to Settings → Module configuration → MQTT.
  2. 啟用 MQTT 模組。
  3. 設定代理伺服器連線：
設定 描述說明 默認
Address MQTT 代理伺服器主機名稱 mqtt.meshtastic.org
Username 代理伺服器驗證 meshdev
Password 代理伺服器驗證 large4cats
Root topic 訊息的基礎主題 msh, which the radio rewrites to msh/<REGION> once you set a region
Encryption enabled 加密 MQTT 承載內容 已啟用
JSON output enabled Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it 已停用
TLS enabled 與代理伺服器的安全連線 已停用
Map reporting 將位置回報至公開地圖 已停用
Proxy to client enabled Relay MQTT through the connected phone 已停用

Connection Status and Test Connection

The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here.

Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason.

MQTT Proxy on This Phone

If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection.

ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them.

The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration.

預設 Meshtastic 代理伺服器

社群在 mqtt.meshtastic.org 維護一個公開的代理伺服器。此伺服器供一般使用與測試之用。

When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without).

🔒 隱私：公開代理伺服器上的訊息，任何訂閱者均可讀取。私人通訊請務必啟用頻道加密。

私有代理伺服器

為了獲得更好的隱私保護與控制權，您可以自行架設 MQTT 代理伺服器：

  • Mosquitto（輕量、開放原始碼）
  • HiveMQ
  • EMQX

請將您的節點設定為指向私有代理伺服器，並輸入相應的登入憑證。

地圖回報

When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.

Turning it on opens a consent card. Turn on I agree. and choose a Map Publish Interval of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.

Reports appear at meshmap.net and similar community map services.

🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published.

上行 vs 下行

方向 描述說明
上行 訊息從 mesh 網路 → MQTT 代理伺服器
下行 訊息從 MQTT 代理伺服器 → mesh 網路

Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on.

訊息格式

MQTT carries two payload formats:

格式 描述說明 使用情境
Protobuf 二進位 Meshtastic protobuf 編碼 節點間 mesh 橋接
JSON Human-readable JSON on the /2/json/ topic Consumers outside the mesh (dashboards, home automation)

ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads.

加密與隱私

了解分層加密模型：

  1. 頻道加密在 mesh 網路上進行，發生於 MQTT 傳輸之前。若您的頻道已設定 PSK，MQTT 承載內容將已加密——代理伺服器及任何訂閱者只能看到密文。
  2. Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard.
  3. TLS 對連接至代理伺服器的 TCP 連線進行加密，防止網路層級的竊聽。

🔒 Security: The default public channel has a well-known key. 透過 MQTT 傳送的預設頻道訊息實際上等同於未加密 — 任何人均可解碼。私人通訊請務必使用自訂 PSK。

最佳實踐

  • 在橋接至 MQTT 的頻道上使用頻道層級加密（PSK）
  • Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes memory)
  • 敏感部署環境請使用私有代理伺服器
  • 從繁忙的 MQTT 主題下行訊息時，請留意無線電佔用時間——每則下行訊息都會消耗本地 mesh 網路的無線電佔用時間
  • 若僅需遠端監控 mesh 網路而不需注入訊息，建議僅啟用上行模式

故障排除

MQTT 無法連線

  • Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT 無法直接透過 LoRa 無線電連結運作。
  • Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces.
  • Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443).
  • DNS 解析 — 若使用自訂代理伺服器主機名稱，請確認節點能夠正確解析該名稱。請嘗試直接使用代理伺服器的 IP 位址進行連線。

訊息未正常橋接

  • 檢查上行／下行設定 — 若僅啟用上行，訊息只會從 mesh 網路流向 MQTT，不會反向傳送。請在接收端閘道上啟用下行功能。
  • 頻道不符 — 兩個閘道必須使用相同頻道且具備相同的 PSK。不符時，訊息將以不同金鑰加密，導致對方收到的內容為亂碼。
  • Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root.
  • Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway.
  • Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in.

相關主題

  • 〔設定 — 模組與管理〕(settings-module-admin) — MQTT 模組設定參考
  • 〔訊息與頻道〕(messages-and-channels) — 頻道加密與 PSK 設定
  • 〔MQTT 整合指南〕(https://meshtastic.org/docs/software/integrations/mqtt) — meshtastic.org 上的完整 MQTT 說明文件
diff --git a/main/zh-rTW/user/settings-module-admin.html b/main/zh-rTW/user/settings-module-admin.html index 36f2564d4f..b65a6ffdf9 100644 --- a/main/zh-rTW/user/settings-module-admin.html +++ b/main/zh-rTW/user/settings-module-admin.html @@ -1 +1 @@ - Settings — Modules & Admin | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 中文 (繁體)
Meshtastic Docs ↗

🌐 中文 (繁體) — Community translation View in English

Settings — Modules & Admin

Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.

💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.

Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:

A toggle setting in the on position

A dropdown setting, expanded to show its list of options

A text field setting with a value entered

A module settings card with its title and grouped controls

模組設定

Every module lives under Settings → Module configuration.

⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes.

MQTT module

Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.

設定 描述說明
啟用MQTT服務器 Toggle MQTT bridge
地址 MQTT broker address
使用者名稱 Authentication username
密碼 Authentication password
加密已啟用 Encrypt MQTT payloads
JSON輸出已啟用 Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS已啟用 Use secure connection
根話題 Base MQTT topic path
啟用對客戶端的代理 Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy on this phone The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT
地圖報告 Publish position to the public map — see the Map reporting group that follows

Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:

設定 描述說明
我同意。 Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
地圖報告間隔（秒） How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered

See MQTT for a detailed usage guide including encryption, privacy, and broker setup.

Serial module

Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.

設定 描述說明
啟用序列埠 Activate serial communication
啟用 Echo Echo received serial data back
序列埠模式 Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX GPIO pins for the serial connection
序列埠鮑率 Port speed
Timeout - 超時 How long to wait before considering an incoming message complete
覆蓋控制台序列埠 Take over the port the debug console normally uses

External Notification module

Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.

There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.

設定 描述說明
啟用外部通知 Master toggle for the module
Alert message LED / buzzer / vibra Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra Which outputs fire on a received bell character
輸出LED（GPIO） Pin the LED is wired to
輸出LED 高電平觸發 Whether the LED pin is active high or low
輸出蜂鳴（GPIO） Pin the buzzer is wired to
輸出振動（GPIO） Pin the vibration motor is wired to
使用PWM調製的蜂鳴 Drive the buzzer with PWM, which allows tones rather than a single pitch
使用 I2S 控制蜂鳴器 Send the alert through an I2S audio output instead
輸出持續時間（毫秒） How long a single alert lasts
通知逾時時間（秒） Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
鈴聲 The tone played on a PWM buzzer, in RTTTL. Can be imported from a file

Store & Forward module

Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.

設定 描述說明
啟用儲存並轉發 Activate store and forward
心跳 Periodically announce this node’s store-and-forward capability
紀錄數目 Maximum stored messages
歴史紀錄最大返回值 Max messages to replay
歴史紀錄返回視窗 Time window for replay
伺服器 Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)

💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.

Range Test module

⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.

Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.

設定 描述說明
啟用範圍測試 Activate range testing
訊息發送間隔(秒) Time between test transmissions, chosen from a dropdown of fixed intervals
將 .CSV 保存到內部儲存空間(僅限ESP32) Log received test data to the node’s own filesystem. ESP32 hardware only

Telemetry module

Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).

Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.

設定 描述說明
傳送裝置遙測資料 Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
裝置資訊更新間隔 How often to report battery, uptime and channel utilization
啟用環境資訊模組 Report the attached environment sensors
環境資訊更新間隔 How often to report them
在螢幕上顯示環境資訊 Also show these readings on the device’s own display
環境指標以華氏溫度顯示 Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
啟用空氣品質模組 Report particulate and CO₂ sensor data
空氣品質資訊更新間隔 How often to report them
啟用電池資訊模組 Report the per-channel voltage and current readings
電源資訊更新間隔 How often to report them
在螢幕上顯示電量資訊 Also show power readings on the device’s display

See Telemetry & Sensors for supported sensors and configuration recommendations.

Canned Message module

Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.

設定 描述說明
Canned message enabled ⚠️ Deprecated in the protobuf schema
訊息 Newline-separated list of messages
發送振鈴 Send a bell character alongside the message, so a receiving node’s External Notification module can sound
啟用旋轉編碼器#1 Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port The three pins the encoder is wired to
Generate input event on Press / CW / CCW Which key event each encoder action produces
啟用上下選擇輸入 A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source ⚠️ Deprecated in the protobuf schema

Audio module

Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.

設定 描述說明
啟用 CODEC 2 Activate audio module
CODEC2 取樣率 Audio quality/bandwidth tradeoff
PTT針腳 GPIO pin for the push-to-talk button
I2S WS 訊號選擇 GPIO pin for I2S WS
I2S 數據輸入 GPIO pin for I2S DIN
I2S 數據輸出 GPIO pin for I2S DOUT
I2S 時鐘 GPIO pin for the I2S bit clock

ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.

Remote Hardware module

GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.

⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.

設定 描述說明
啟動遠端硬體 Activate remote GPIO access
允許未定義腳位連接 Allow access to any GPIO pin (security risk)
可用腳位 Up to 4 GPIO pins this node exposes for remote read/write

Neighbor Info module

Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.

設定 描述說明
啟用鄰居資訊 Activate neighbor broadcasting
更新間隔（秒） How often to broadcast neighbor list
通過Lora無線電傳輸 Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name

See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.

Ambient Lighting module

Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.

設定 描述說明
LED狀態 Turn the LED on or off
目前 LED current limit (0–31)
Red / Green / Blue Individual color channel values (0–255)

Detection Sensor module

Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.

設定 描述說明
啟用偵測感測器 Activate detection sensor
螢幕的 GPIO 腳位 GPIO pin connected to sensor
偵測觸發類型 How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
使用輸入上拉模式 Enable the pin’s internal pull-up resistor
最短廣播間隔 (秒) Minimum time between alert broadcasts
狀態廣播間隔 (秒) Periodic state broadcast interval
告警訊息發送提示音 Include bell character in alerts
顯示名稱 Custom name for this sensor

Paxcounter module

People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.

設定 描述說明
已啟用人流計數（Paxcount） Activate people counting
更新間隔（秒） How often to report counts
Wi-Fi RSSI threshold Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE RSSI threshold The same cut-off for BLE advertisements (defaults to −80 dBm)

💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.

Status Message module

The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.

Mesh Beacon module

Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.

TAK module

Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.

管理

遠端管理

Remotely configure nodes that share your admin key:

  1. Select the target node in the node list.
  2. Navigate to Settings for that node.
  3. Modify configuration.
  4. Tap Save — changes are sent over the mesh.

⚠️ Important: Requires an admin key configured on both your node and the target node.

Device Actions

Settings → Administration holds five one-shot actions, each behind a confirmation dialog:

動作 What it does
Set time Sends your phone’s clock to the node
重新開機 Restarts the node
關機 Powers the node down
恢復出廠設置 Returns every setting to its factory default
重設節點資料庫 Clears the node database. This dialog carries a Preserve Favorites? switch

⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.

備份與還原

Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.

進階

Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.

清除節點資料庫

Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.

  • Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
  • Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.

The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.

偵錯面板

Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.

App Settings 應用程式設定

The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:

Privacy

  • Allow analytics and crash reporting — opt in or out of diagnostics.
  • Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
  • Homoglyph encoding — how look-alike characters in names are handled.

Appearance

  • Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
  • Theme and Language.
  • Show full message timestamps.

Persistence

  • A cache limit for how much history is kept.
  • Export rangetest packets, Export all packets and Export node database.

On their own

  • Node Layout — how much detail each row of the node list shows.
  • Wi-Fi Provisioning for mPWRD-OS — see Connections.
  • Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
  • System AI — appears only where app functions are available; see App Functions.

A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.

About（關於）

Settings → About carries the app’s own identity rather than the node’s:

Three sections:

  • What is Meshtastic? — a short description of the project.
  • Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
  • Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.

The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.

致謝

Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.

Troubleshooting remote admin

  • “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
  • Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
  • Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
+ Settings — Modules & Admin | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 中文 (繁體)
Meshtastic Docs ↗

🌐 中文 (繁體) — Community translation View in English

Settings — Modules & Admin

Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.

💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.

Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:

A toggle setting in the on position

A dropdown setting, expanded to show its list of options

A text field setting with a value entered

A module settings card with its title and grouped controls

模組設定

Every module lives under Settings → Module configuration.

⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes.

MQTT module

Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.

設定 描述說明
啟用MQTT服務器 Toggle MQTT bridge
地址 MQTT broker address
使用者名稱 Authentication username
密碼 Authentication password
加密已啟用 Encrypt MQTT payloads
JSON輸出已啟用 Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS已啟用 Use secure connection
根話題 Base MQTT topic path
啟用對客戶端的代理 Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy on this phone The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT
地圖報告 Publish position to the public map — see the Map reporting group that follows

Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:

設定 描述說明
我同意。 Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered

See MQTT for a detailed usage guide including encryption, privacy, and broker setup.

Serial module

Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.

設定 描述說明
啟用序列埠 Activate serial communication
啟用 Echo Echo received serial data back
序列埠模式 Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX GPIO pins for the serial connection
序列埠鮑率 Port speed
Timeout - 超時 How long to wait before considering an incoming message complete
覆蓋控制台序列埠 Take over the port the debug console normally uses

External Notification module

Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.

There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.

設定 描述說明
啟用外部通知 Master toggle for the module
Alert message LED / buzzer / vibra Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra Which outputs fire on a received bell character
輸出LED（GPIO） Pin the LED is wired to
輸出LED 高電平觸發 Whether the LED pin is active high or low
輸出蜂鳴（GPIO） Pin the buzzer is wired to
輸出振動（GPIO） Pin the vibration motor is wired to
使用PWM調製的蜂鳴 Drive the buzzer with PWM, which allows tones rather than a single pitch
使用 I2S 控制蜂鳴器 Send the alert through an I2S audio output instead
GPIO Output Duration How long a single alert lasts
持續提醒逾時 Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
鈴聲 The tone played on a PWM buzzer, in RTTTL. Can be imported from a file

Store & Forward module

Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.

設定 描述說明
啟用儲存並轉發 Activate store and forward
心跳 Periodically announce this node’s store-and-forward capability
紀錄數目 Maximum stored messages
歴史紀錄最大返回值 Max messages to replay
歴史紀錄返回視窗 Time window for replay
伺服器 Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)

💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.

Range Test module

⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.

Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.

設定 描述說明
啟用範圍測試 Activate range testing
傳送間隔 Time between test transmissions, chosen from a dropdown of fixed intervals
將 .CSV 保存到內部儲存空間(僅限ESP32) Log received test data to the node’s own filesystem. ESP32 hardware only

Telemetry module

Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).

Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.

設定 描述說明
傳送裝置遙測資料 Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
裝置資訊更新間隔 How often to report battery, uptime and channel utilization
啟用環境資訊模組 Report the attached environment sensors
環境資訊更新間隔 How often to report them
在螢幕上顯示環境資訊 Also show these readings on the device’s own display
環境指標以華氏溫度顯示 Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
啟用空氣品質模組 Report particulate and CO₂ sensor data
空氣品質資訊更新間隔 How often to report them
啟用電池資訊模組 Report the per-channel voltage and current readings
電源資訊更新間隔 How often to report them
在螢幕上顯示電量資訊 Also show power readings on the device’s display

See Telemetry & Sensors for supported sensors and configuration recommendations.

Canned Message module

Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.

設定 描述說明
Canned message enabled ⚠️ Deprecated in the protobuf schema
訊息 Newline-separated list of messages
發送振鈴 Send a bell character alongside the message, so a receiving node’s External Notification module can sound
啟用旋轉編碼器#1 Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port The three pins the encoder is wired to
Generate input event on Press / CW / CCW Which key event each encoder action produces
啟用上下選擇輸入 A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source ⚠️ Deprecated in the protobuf schema

Audio module

Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.

設定 描述說明
啟用 CODEC 2 Activate audio module
CODEC2 取樣率 Audio quality/bandwidth tradeoff
PTT針腳 GPIO pin for the push-to-talk button
I2S WS 訊號選擇 GPIO pin for I2S WS
I2S 數據輸入 GPIO pin for I2S DIN
I2S 數據輸出 GPIO pin for I2S DOUT
I2S 時鐘 GPIO pin for the I2S bit clock

ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.

Remote Hardware module

GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.

⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.

設定 描述說明
啟動遠端硬體 Activate remote GPIO access
允許未定義腳位連接 Allow access to any GPIO pin (security risk)
可用腳位 Up to 4 GPIO pins this node exposes for remote read/write

Neighbor Info module

Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.

設定 描述說明
啟用鄰居資訊 Activate neighbor broadcasting
GPS 輪詢間隔 How often to broadcast neighbor list
通過Lora無線電傳輸 Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name

See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.

Ambient Lighting module

Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.

設定 描述說明
LED狀態 Turn the LED on or off
目前 LED current limit (0–31)
Red / Green / Blue Individual color channel values (0–255)

Detection Sensor module

Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.

設定 描述說明
啟用偵測感測器 Activate detection sensor
螢幕的 GPIO 腳位 GPIO pin connected to sensor
偵測觸發類型 How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
使用輸入上拉模式 Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts Minimum time between alert broadcasts
狀態廣播間隔 Periodic state broadcast interval
告警訊息發送提示音 Include bell character in alerts
顯示名稱 Custom name for this sensor

Paxcounter module

People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.

設定 描述說明
已啟用人流計數（Paxcount） Activate people counting
GPS 輪詢間隔 How often to report counts
WiFi Threshold (dBm) Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm) The same cut-off for BLE advertisements (defaults to −80 dBm)

💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.

Status Message module

The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.

Mesh Beacon module

Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.

TAK module

Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.

管理

遠端管理

Remotely configure nodes that share your admin key:

  1. Select the target node in the node list.
  2. Navigate to Settings for that node.
  3. Modify configuration.
  4. Tap Save — changes are sent over the mesh.

⚠️ Important: Requires an admin key configured on both your node and the target node.

Device Actions

Settings → Administration holds five one-shot actions, each behind a confirmation dialog:

動作 What it does
Set time Sends your phone’s clock to the node
重新開機 Restarts the node
關機 Powers the node down
恢復出廠設置 Returns every setting to its factory default
重設節點資料庫 Clears the node database. This dialog carries a Preserve Favorites? switch

⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.

備份與還原

Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.

進階

Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.

清除節點資料庫

Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.

  • Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
  • Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.

The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.

偵錯面板

Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.

App Settings 應用程式設定

The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:

Privacy

  • Allow analytics and crash reporting — opt in or out of diagnostics.
  • Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
  • Homoglyph encoding — how look-alike characters in names are handled.

Appearance

  • Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
  • Theme and Language.
  • Show full message timestamps.

Persistence

  • A cache limit for how much history is kept.
  • Export rangetest packets, Export all packets and Export node database.

On their own

  • Node Layout — how much detail each row of the node list shows.
  • Wi-Fi Provisioning for mPWRD-OS — see Connections.
  • Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
  • System AI — appears only where app functions are available; see App Functions.

A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.

About（關於）

Settings → About carries the app’s own identity rather than the node’s:

Three sections:

  • What is Meshtastic? — a short description of the project.
  • Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
  • Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.

The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.

致謝

Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.

Troubleshooting remote admin

  • “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
  • Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
  • Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
diff --git a/main/zh-rTW/user/settings-radio-user.html b/main/zh-rTW/user/settings-radio-user.html index 7382714ca5..2a3dbfbfc3 100644 --- a/main/zh-rTW/user/settings-radio-user.html +++ b/main/zh-rTW/user/settings-radio-user.html @@ -1 +1 @@ - Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 中文 (繁體)
Meshtastic Docs ↗

🌐 中文 (繁體) — Community translation View in English

Settings — Radio & User

Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How these screens work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control 螢幕截圖
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

使用者設定

User Profile

On Settings → User.

設定 描述說明
長名稱 Your display name (up to 39 characters)
簡短名稱 4-character abbreviated name
狀態訊息 A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
不接收訊息 Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur node (Ham) Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in.

設定

設備設置

On Settings → Device configuration → Device.

設定 描述說明 默認
裝置角色 Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
## Rebroadcast Mode轉發廣播模式 How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
節點資訊廣播間隔 How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
雙擊觸發按鈕功能 Treat a double tap as a button press Disabled
三擊執行 Ad Hoc Ping Send an ad-hoc position ping on a triple click 已啟用
LED 心跳指示 Blink the status LED periodically 已啟用
時區 POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it —
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to —

LoRa規劃

On Settings → LoRa.

設定 描述說明 默認
地區 Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number Unset (must configure)
預設配置 Speed/range tradeoff LongFast
中繼次數 Maximum retransmit hops 3
傳輸功率 Transmission power (dBm); 0 = max allowed for region 0 (region max)
手動設定頻率 Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
使用預設值 On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
擴頻因子 Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead From preset
編碼率 Manual mode only: 5–8. More redundancy costs airtime From preset
頻寬 Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one From preset
頻率槽 Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
已啟用發射 Turning this off makes the node receive-only On
覆蓋工作週期/佔空比 Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
忽略 MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
允許轉發至 MQTT Allow your packets to be forwarded to MQTT by gateways Off
接收增益提升 Extra receive gain on SX126x radios; costs a little current Off
停用PA風扇 Turn off the power-amplifier fan on hardware that has one Off

The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set.

Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset 範圍 速度 SNR Limit Best For
短 Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
短 快 ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
短 慢 ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
中等快 ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
中等慢 ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
長度中等的 ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a modem preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

顯示設置

On Settings → Device configuration → Display. These control the node’s own screen, not the app’s.

設定 描述說明
螢幕開啟持續時間 How long the display stays lit before sleeping
輪播間隔 How often the node cycles between screens on its own
顯示模式 Screen layout/density used by the firmware
顯示單位 Metric or Imperial on the node’s screen
使用12小時制 Show the node’s clock as 12-hour rather than 24-hour
粗體字 Draw the screen’s heading text in bold
翻轉畫面 Rotate the display 180° for an inverted mounting
OLED 類型 Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED
輕觸或移動喚醒 Light the screen when the node is tapped or moved
羅盤朝向 Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each
始終指向北方 Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

位置設定

On Settings → Device configuration → Position.

設定 描述說明
GPS 模式（實體硬體） Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS 輪詢間隔 How often the node asks its GPS for a fix
廣播間隔 How often the position is shared with the mesh
智慧定位 Broadcast based on movement rather than purely on the clock
智慧間隔 With Smart Position on, the shortest gap between broadcasts
智慧距離 With Smart Position on, how far you must move before broadcasting
固定位置 Use a manually entered latitude, longitude and altitude instead of the GPS
位置旗標 A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

電源設定

On Settings → Device configuration → Power.

設定 描述說明
啟用省電模式 Let the node sleep aggressively between activity
電源中斷時關機 Power the device down after external power disappears
超深度睡眠時長 How long the deepest sleep state lasts
最小喚醒時間 The shortest time the node stays awake once woken
藍牙等待持續時間 How long to wait for a phone to connect before sleeping
ADC 校正係數 Turn on a manual correction for battery-voltage readings
ADC乘數修正比率 The correction factor itself, used only when the override is on
電池 INA_2XX I2C 地址 Address of an external INA-series power sensor, if fitted

網路配置

On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node.

設定 描述說明
Wi-Fi enabled Enable the Wi-Fi node (ESP32 nodes)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
密碼 網路密碼
啟用以太網 Use a wired connection on hardware that has one
第四代IP模式 DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP 廣播 Share mesh traffic with other nodes over the local network
時間伺服器 Time synchronization server
rsyslog伺服器 Remote logging server

Network Config with a static IPv4 address entered

藍牙配置

On Settings → Device configuration → Bluetooth, on nodes with Bluetooth.

設定 描述說明
藍牙已啟用 Enable/disable BLE radio
配對模式 Fixed PIN, Random PIN, or No PIN
固定 PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

安全性設定

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

設定 描述說明
公鑰 Your node’s public key (read-only)
管理金鑰 Keys permitted to administer this node remotely — up to three
私鑰 Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it
重新產生私鑰 Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
序列控制台 Serial console over the Stream API
啟用除錯日誌 API Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth
管理模式 Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set
備份金鑰 Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.

+ Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Meshtastic Android
This site uses Just the Docs, a documentation theme for Jekyll.
🌐 中文 (繁體)
Meshtastic Docs ↗

🌐 中文 (繁體) — Community translation View in English

Settings — Radio & User

Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How these screens work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control 螢幕截圖
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

使用者設定

User Profile

On Settings → User.

設定 描述說明
長名稱 Your display name (up to 39 characters)
簡短名稱 4-character abbreviated name
狀態訊息 A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
不接收訊息 Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur node (Ham) Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in.

設定

設備設置

On Settings → Device configuration → Device.

設定 描述說明 默認
裝置角色 Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
## Rebroadcast Mode轉發廣播模式 How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
節點資訊廣播間隔 How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
雙擊觸發按鈕功能 Treat a double tap as a button press Disabled
三擊執行 Ad Hoc Ping Send an ad-hoc position ping on a triple click 已啟用
LED 心跳指示 Blink the status LED periodically 已啟用
時區 POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it —
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to —

LoRa規劃

On Settings → LoRa.

設定 描述說明 默認
地區 Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number Unset (must configure)
預設配置 Speed/range tradeoff LongFast
中繼次數 Maximum retransmit hops 3
Transmit Power (dBm) Transmission power; 0 = max allowed for region 0 (region max)
手動設定頻率 Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
使用預設值 On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
擴頻因子 Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead From preset
編碼率 Manual mode only: 5–8. More redundancy costs airtime From preset
頻寬 Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one From preset
頻率槽 Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
已啟用發射 Turning this off makes the node receive-only On
覆蓋工作週期/佔空比 Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
忽略 MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
允許轉發至 MQTT Allow your packets to be forwarded to MQTT by gateways Off
接收增益提升 Extra receive gain on SX126x radios; costs a little current Off
停用PA風扇 Turn off the power-amplifier fan on hardware that has one Off

The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set.

Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset 範圍 速度 SNR Limit Best For
短 Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
短 快 ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
短 慢 ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
中等快 ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
中等慢 ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
長度中等的 ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a modem preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

顯示設置

On Settings → Device configuration → Display. These control the node’s own screen, not the app’s.

設定 描述說明
螢幕開啟持續時間 How long the display stays lit before sleeping
輪播間隔 How often the node cycles between screens on its own
顯示模式 Screen layout/density used by the firmware
顯示單位 Metric or Imperial on the node’s screen
使用12小時制 Show the node’s clock as 12-hour rather than 24-hour
粗體字 Draw the screen’s heading text in bold
翻轉畫面 Rotate the display 180° for an inverted mounting
OLED 類型 Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED
輕觸或移動喚醒 Light the screen when the node is tapped or moved
羅盤朝向 Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each
始終指向北方 Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

位置設定

On Settings → Device configuration → Position.

設定 描述說明
GPS 模式（實體硬體） Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS 輪詢間隔 How often the node asks its GPS for a fix
廣播間隔 How often the position is shared with the mesh
智慧定位 Broadcast based on movement rather than purely on the clock
智慧間隔 With Smart Position on, the shortest gap between broadcasts
智慧距離 With Smart Position on, how far you must move before broadcasting
固定位置 Use a manually entered latitude, longitude and altitude instead of the GPS
位置旗標 A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

電源設定

On Settings → Device configuration → Power.

設定 描述說明
啟用省電模式 Let the node sleep aggressively between activity
電源中斷時關機 Power the device down after external power disappears
超深度睡眠時長 How long the deepest sleep state lasts
最小喚醒時間 The shortest time the node stays awake once woken
藍牙等待持續時間 How long to wait for a phone to connect before sleeping
ADC 校正係數 Turn on a manual correction for battery-voltage readings
ADC乘數修正比率 The correction factor itself, used only when the override is on
電池 INA_2XX I2C 地址 Address of an external INA-series power sensor, if fitted

網路配置

On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node.

設定 描述說明
Wi-Fi enabled Enable the Wi-Fi node (ESP32 nodes)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
密碼 網路密碼
啟用以太網 Use a wired connection on hardware that has one
第四代IP模式 DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP 廣播 Share mesh traffic with other nodes over the local network
時間伺服器 Time synchronization server
rsyslog伺服器 Remote logging server

Network Config with a static IPv4 address entered

藍牙配置

On Settings → Device configuration → Bluetooth, on nodes with Bluetooth.

設定 描述說明
藍牙已啟用 Enable/disable BLE radio
配對模式 Fixed PIN, Random PIN, or No PIN
固定 PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

安全性設定

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

設定 描述說明
公鑰 Your node’s public key (read-only)
管理金鑰 Keys permitted to administer this node remotely — up to three
私鑰 Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it
重新產生私鑰 Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
序列控制台 Serial console over the Stream API
啟用除錯日誌 API Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth
管理模式 Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set
備份金鑰 Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.